Hi, On Sun, 05 Nov 2006 at 20:14 +0100, Dirk Nehring wrote: > On Sun, Nov 05, 2006 at 06:26:51PM +0100, [EMAIL PROTECTED] wrote: > > Author: wbx > > Date: 2006-11-05 18:26:50 +0100 (Sun, 05 Nov 2006) > > New Revision: 1067 > > > > Modified: > > branches/freewrt_1_0/mk/modules-2.4.mk > > > > branches/freewrt_1_0/target/linux/brcm-2.4/squashfs-overlay/config/config.squashfs_overlay > > Log: > > enable nls modules and some filesystems in kernel config, create > > kmod-nls-cp437 package, start for the nls/fs module cleanup > [...] > > > > Modified: > > branches/freewrt_1_0/target/linux/brcm-2.4/squashfs-overlay/config/config.squashfs_overlay > > =================================================================== > > --- > > branches/freewrt_1_0/target/linux/brcm-2.4/squashfs-overlay/config/config.squashfs_overlay > > 2006-11-05 15:33:04 UTC (rev 1066) > > +++ > > branches/freewrt_1_0/target/linux/brcm-2.4/squashfs-overlay/config/config.squashfs_overlay > > 2006-11-05 17:26:50 UTC (rev 1067) > > @@ -1,5 +1,5 @@ > > # > > -# Automatically generated make config: don't edit > > +# Automatically generated by make menuconfig: don't edit > > OK, only a suggestion: we should use the same method to generate the > config file. As you see, your diff is rather long since I use "make > config" and you "make menuconfig". "make config" make nicer comments, > could all agree with this?
Hmm. make config is asking for everything, so it takes very long to just enable one or two options. Is it really necessary to always generate with the same method? I see no functional change. > [...]a > > -# CONFIG_NTFS_RW is not set > > +CONFIG_NTFS_FS=m > > +CONFIG_NTFS_RW=y > > Mmh, NTFS per default. it is quite unstable under 2.4 and uses some > space. In which situation do you need native ntfs support? It is not default. It just compiles a module. There is even no package for it. I would like to try if a external usb disk with ntfs is usable on a Asus Router. So it just adds some seconds compile time, without any other consequences. > > -# CONFIG_NFSD is not set > > -# CONFIG_NFSD_V3 is not set > > +CONFIG_NFSD=m > > +CONFIG_NFSD_V3=y > > Is NFSD always needed per Default? The same as above. +CONFIG_NFSD_V3 is an option for NFSD. If i package a nfsd kernel module it will contain NFSv3 support. It does not mean, that our default kernel contain NFSD support by default. bye Waldemar -- don't open your wrt, free it http://www.freewrt.org _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
