Re: Bug#98439: dhcp support broken
On Thu, May 24, 2001 at 01:57:17AM -0400, Adam Di Carlo wrote: Please file serious bugs against these kernels. They need CONFIG_FILTER. The following bugs have been filed against the appropriate kernel-image. 98589: sun4u 98591: powerpc-chrp 98592: powerpc-prep 98593: mac (m68k) 98595: atari (m68k) 98596: amiga (m68k) I didn't find kernel-images for mips at http.us, but I did find them at ftp.rfc822.org. Both mips and mipsel are missing CONFIG_FILTER=y. Should I just put a note on their list? I didn't find kernel-images for ia64 or hppa, perhaps due to the status of the ports. Should I put a note on their lists or just wait until they are further along? Thanks, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#98439: dhcp support broken
On Thu, May 24, 2001 at 10:33:55AM -0500, Stephen R Marenka wrote: I didn't find kernel-images for ia64 or hppa, perhaps due to the status of the ports. Should I put a note on their lists or just wait until they are further along? I'm working on the .config for hppa, and I have CONFIG_FILTER=y. Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#98439: dhcp support broken
Stephen R Marenka [EMAIL PROTECTED] writes: We shouldn't need /var/dhcp because we're using the -lf switch to redirect the leases file to /tmp/dhcp.leases. I tested this switch on i386 and powermac and it worked fine. Perhaps this is related to the CONFIG_ issue? Adding the directory, though, probably shouldn't hurt anything? I don't think this is a real issue at all... We also need to verify that other archs have the necessary configs. CONFIG_PACKET=m CONFIG_FILTER=y All i386. powerpc-apus Yes -- this is the case I'm seeing now. I don't see /lib/modules/misc on the root disk, but it should be. This should in fact work. Something is broken. I'm researching rootdisk.sh now. CONFIG_PACKET=y CONFIG_FILTER=n sun4u powerpc-chrp CONFIG_PACKET=m CONFIG_FILTER=n powerpc-prep Please file serious bugs against these kernels. They need CONFIG_FILTER. I guest that leaves alpha and m68k. So much for consistency. Revert to pump on all/certain platforms? Change the kernels? What's the best course? Change the kernels so they all have CONFIG_FILTER and at least a module for CONFIG_PACKET, and fix rootdisk.sh. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#98439: dhcp support broken
On Tue, May 22, 2001 at 02:54:43PM -0700, David Whedon wrote: Package: boot-floppies Version: N/A; reported 2001-05-22 Severity: grave The the replacement of pump with dhcp-client has broken dhcp support on boot-floppies. I'm batting 1000 -- nothing like ojt. [snip] We need to make sure af_packet.o is included on the root filesystem and do a modprobe af_packet.o before trying to do dhcp. We also need to create /var/dhcp. We shouldn't need /var/dhcp because we're using the -lf switch to redirect the leases file to /tmp/dhcp.leases. I tested this switch on i386 and powermac and it worked fine. Perhaps this is related to the CONFIG_ issue? Adding the directory, though, probably shouldn't hurt anything? We also need to verify that other archs have the necessary configs. CONFIG_PACKET=y CONFIG_FILTER=y sun4cdm sun4dm-pci powerpc-pmac CONFIG_PACKET=m CONFIG_FILTER=y All i386. powerpc-apus CONFIG_PACKET=y CONFIG_FILTER=n sun4u powerpc-chrp CONFIG_PACKET=m CONFIG_FILTER=n powerpc-prep I guest that leaves alpha and m68k. So much for consistency. Revert to pump on all/certain platforms? Change the kernels? What's the best course? [snip] expr: not found [: 2: unexpected operator I got these errors too, but everything worked fine (acquired address consistently). Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
