Summary: | baselayout 1.12.0_pre1-r1 broke my system (dhcp?) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kurt Guenther <kurtg> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | a, bugs-gentoo, ginsu.squirrel, Heinz.Hombergs, joao_rita, jrmalaq, patrick, polar88bear, radek, ts77, uberlord |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kurt Guenther
2005-07-20 09:19:51 UTC
Hi, Same here, IMHO the problem is with "/etc/conf.d/rc" file as it's the only one (beside two .example files) which was changed while doing "etc-update" and again later when going back to baselayout-1.11.13. Thanks. Rumen Same problem here Same problem here. And with the new baselayout the start order of the init.d scripts has changed. With the old version the start order was: syslogkd net.eth0 named with the new version the start order is: hdparam named neth.eth0 Ditto. Init order is totally borked. (There are also some init scripts running I never added) Not able to login. Speechd fails to start. same problem here. most visible one is net.eth0 failing because of missing dhcp. so, back to windows to get the gentoo-install cds ;). For me booting in single user mode and emerge "=sys-apps/baselayout-1.11.13" started the machine again. I have this issue also on both x86/amd64. Work around: If using grub, you can add "init 1" on the end of the grub kernel line like this. title Gentoo Linux 2.6.12 (r6-init 1) root (hd0,4) kernel (hd0,4)/kernel-2.6.12-gentoo-r6 root=/dev/hda6 init 1 To mask the package, do this: # echo ">=sys-apps/baselayout-1.12.0_pre1-r1" >> /etc/portage/package.mask If you have the package in /usr/portage/distfiles, you can then emerge it. First, verify that you'll back-level baselayout: # emerge -p baselayout Calculating dependencies ...done! [ebuild UD ] sys-apps/baselayout-1.11.13 [1.12.0_pre1-r1] and then: # emerge baselayout # etc-update # reboot You can do the same with a Live CD, but it takes more effort. However, this is useful if you already removed the baselayout-1.11.13 from your distfiles as you'll have access to the network, so you can retrieve it. Same problems here with the new baselayout. What I found out: Booting with init 1 works. Typing init 3 brings up network and boots the system like normal. I've got the problem at the moment on two pc's: Both running ~x86. I just use RC_AUTO_INTERFACE="no" in my /etc/conf.d/net as said in the new net.example so it don't try dhcp and all the thing goes well (as I dont have DHCP). What version of dhcpcd do you guys have installed? I didn't use DHCP. I use IP adress in /etc/conf.d/net. I tried it with config_eth0 = ("IP/24"), config_etho0 = ("IP netmask 255.255.255.0") and with a broadcast IP in both statements. But I get the same results for the borked start of the daemons with baselayout 1.12.0_pre1-r1 Here's mine. My laptop is ~x86. * net-misc/dhcpcd Latest version available: 1.3.22_p4-r12 Latest version installed: 1.3.22_p4-r5 Size of downloaded files: 148 kB Homepage: http://www.phystech.com/download/ Description: A dhcp client only License: GPL-2 Guys - unstable baselayout requires unstable dhcp packages for dhcpcd and/or pump (depending on your flavour) - udhcpc and dhclient work with stable packages. All four should work with stable baselayout. Ummm, I don't think so. Can't tell you the exact versions (downgraded back) but it was still broken with both latest (unstable) versions of baselayout and dhcpcd (not udh...) Sure you're error isn't related to bug #99663 instead? Well, I didn't have time to exploit it but I think it was only dhcp-module related... baselayout-1.12.0_pre3-r2 should resolve this issue Re-open if you disagree I've got a problem, guys.... While my system works, the order in which services are started is all messed up. net.eth0 is started last thereby screwing up nfs and ntp and a bunch of other services. The only reason I emerged baselayout-1.12.0_pre11-r3 was because it's required by sys-fs/udev-077-r4, which is depended on by sys-apps/hal-0.5.5.1, which is depended on by gnome-base/gnome-vfs-2.10.1-r1, which is depended on by lots of stuff that I depend on. Namely famd(gamin) updating of directory contents in real-time. Is there any way I can just change the order that services are started? Totally different bug which has already been fixed. Simply run rc-status -all and repair anything marked "broken" by removing and re-adding the guilty service. |