Fri, Jun 07, 2002 at 08:59:39PM -0700 wrote: > On Fri, Jun 07, 2002 at 06:51:35PM +0200, Eduard Bloch wrote: > > > In the module installation submenu, the line item "drivers that > > > allow many different filesystems" returns a codepage selection menu > > > instead. Shux, I wanted to be able to read files from an MSDOS > > > > Well, what is the problem? You enter the filesystems menu, there is nfs, > > ntfs and minix among helper modules to use different charsets correctly. > > > > > FAT-16 partition on this system. At least that was what I thought > > > this was going to offer (amongst other filesystem options). > > > > Why do you not just MOUNT the filesystem? AFAIK, the driver is already > > built-in into the kernel and does not have to be loaded manually. > > This kind of thing keeps coming up. How would I go about documenting > what's already 'in there' for people? I know we have the dialog that > says stuff might already be in there, but I mean producing a list of > what people are used to seeing as modules which are built-in for each > kernel we supply. Can I get this by grepping config files?
perhaps we should just include a note telling people to look in the config files, they are available in th same dir as the disk images. We could also hint what CONFIG_FOO=y|m means. As a bonus that will help people know if their ethernet driver, etc. is included. -David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
