Re: [PATCH 1/2] eCryptfs: Public key; transport mechanism

On Sat, 9 Dec 2006 11:04:16 -0800
Randy Dunlap <[email protected]> wrote:

> > ecryptfs now has a dependency upon netlink.  There's no CONFIG_NETLINK.  If
> > CONFIG_NET=n && CONFIG_ECRYPTFS=y is possible, it won't build.
> 
> Then shouldn't ECRYPTFS depend on CONFIG_NET ?

yup, that's what I meant..
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH 1/2] eCryptfs: Public key; transport mechanism
  - From: Michael Halcrow <[email protected]>
- Re: [PATCH 1/2] eCryptfs: Public key; transport mechanism
  - From: Randy Dunlap <[email protected]>

References:
- [PATCH 1/2] eCryptfs: Public key; transport mechanism
  - From: Michael Halcrow <[email protected]>
- Re: [PATCH 1/2] eCryptfs: Public key; transport mechanism
  - From: Andrew Morton <[email protected]>
- Re: [PATCH 1/2] eCryptfs: Public key; transport mechanism
  - From: Randy Dunlap <[email protected]>

Prev by Date: Systrace 2.6.19 patch -- need comments
Next by Date: noexec=on doesn't work
Previous by thread: Re: [PATCH 1/2] eCryptfs: Public key; transport mechanism
Next by thread: Re: [PATCH 1/2] eCryptfs: Public key; transport mechanism
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]