On Thursday 29 June 2006 13:35, [EMAIL PROTECTED] wrote:
> Probably net.eth0 starting has beem somehow moved into boot-runlevel.
> AFAIK it should be in defeult-runlevel, so try to move it there:
>
> rc-update del net.eth0 boot
> rc-update add net.eth0 default
No, it's correctly in default runlevel (spaced for better readability):
[Thu Jun 29 14:59:18 [EMAIL PROTECTED] ~]# rc-update show
* Invalid runlevel entry: /etc/runlevels/boot/.keep
* Invalid runlevel entry: /etc/runlevels/default/.keep
* Invalid runlevel entry: /etc/runlevels/nonetwork/.keep
* Invalid runlevel entry: /etc/runlevels/single/.keep
acpid | default
bootmisc | boot
checkfs | boot
checkroot | boot
clock | boot
consolefont | boot
cupsd | default
domainname | default
famd | default
hostname | boot
hotplug | boot
iptables | default
keymaps | boot
local | default nonetwork
localmount | boot
modules | boot
net.eth0 | default
net.lo | boot
netmount | default
rmnologin | boot
serial | boot
spamd | default
sshd | default
sysklogd | default
urandom | boot
vixie-cron | default
xfs | default
[Thu Jun 29 14:59:25 [EMAIL PROTECTED] ~]# ls /etc/runlevels/boot/
bootmisc checkroot consolefont hotplug localmount net.lo serial
checkfs clock hostname keymaps modules rmnologin urandom
[Thu Jun 29 14:59:37 [EMAIL PROTECTED] ~]# ls -l /etc/runlevels/default
acpid domainname iptables net.eth0 spamd sysklogd xfs
cupsd famd local netmount sshd vixie-cron
Typing the first command showed also the "Invalid runlevel
entry: /etc/runlevels/boot/.keep" errors that I did not notice before.
Seems that the new baselayout has introduced some changes. I'll
investigate further.
Thanks for the reply.
--
[email protected] mailing list
