Lance Hoffmeyer <[EMAIL PROTECTED]> writes: LH> I installed a a base fileserver this morning using Potato Reiser boot LH> floppies.
Huh? (Potato's initial release long predates the reiserfs fad; potato doesn't natively support the 2.4 kernel, so you either need a moderately-patched system or a patched kernel to use reiserfs with potato, and both of these seem like bad ideas for a Debian "stable" release.) LH> The problem is that the 2.2.19 kernel would not recognize the LH> Reiser FS? Maybe a newer reiserfsprogs that causes problems with LH> 2.2.19 kernel (Just guessing?) It looks like reiserfs didn't enter the mainline Linux kernel until 2.4.1pre8. So a 2.2.x kernel is probably right out (unless you can find a reiserfs patch for it); any sufficiently modern 2.4 kernel (e.g. not 2.4.0) will work as well. LH> So, I compiled a 2.4.14 kernel with Reiser support. The only network LH> options I added was the Intel NIC I was using. The kernel compiled, LH> I rebooted and I was able to mount the Reiser partitions I had created LH> earlier. BUT, DHCP quit working. I ran ifconfig and no IP addr had LH> been assigned. I could ping localhost but nothing else. LH> LH> Are there any options I need to pick in the networking or network LH> devices section to get DHCP working on a compiled kerenl or should LH> it DHCP work "out of the box" without modifying any make menuconfig LH> options? See /usr/share/doc/dhcp-client/README.html; it mentions that you need to enable the "packet socket" and "socket filtering" networking options. I'd assume this is true for all Linux DHCP clients. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ "Theoretical politics is interesting. Politicking should be illegal." -- Abra Mitchell
