forgot to CC the bug report. ---------- Forwarded message ---------- From: Rik Theys <rik.th...@gmail.com> Date: Mon, Oct 5, 2009 at 11:11 PM Subject: Re: Bug#549260: insserv: no longer unmounts (root) filesystem on shutdown/reboot To: Petter Reinholdtsen <p...@hungry.com>
On Sun, Oct 4, 2009 at 7:51 AM, Petter Reinholdtsen <p...@hungry.com> wrote: > > Where did you read > that you should run insserv manually? I ask because I want to track > down and update any inaccurate documentation. > > I didn't read this anywhere, I just tried it after reading the insserv man page. I also couldn't find any info in /usr/share/doc/insserv. > I've now run dpkg-reconfigure -plow sysv-rc and it has activated > dependency > > based boot and renamed the links in rc0.d > > Good. > > > The issue with X/kdm remains: it is started on boot and I see the > > nvidia logo appear but then I get the console again and X is no > > longer running. If I login and restart kdm, X comes up and stays up. > > > > Any ideas? > > I would guess some related init.d script is missing start > dependencies, but it is hard to give a more concrete proposal without > the output from 'ls /etc/rcS.d /etc/rc2.d'. > > Here's the output from the ls command: /etc/rc2.d: README S01nvidia-glx S02anacron S02irqbalance S02rsync S03hal S04mysql S06rc.local S01acpi-support S01nvidia-kernel S02apmd S02mcelog S02ssh S03mysql-ndb S04network-manager S06rmnologin S01dirmngr S01rsyslog S02atd S02mysql-ndb-mgm S02stunnel4 S03pulseaudio S04saned S06stop-bootlogd S01joystick S01sudo S02cpufrequtils S02ntp S02sysstat S04cups S05bootlogs S01kvm S01uml-utilities S02cron S02openbsd-inetd S03avahi-daemon S04kdm S05postfix S01loadcpufreq S02acpid S02dbus S02openvpn S03bluetooth S04libvirt-bin S06laptop-mode /etc/rcS.d: README S07hdparm S10ifupdown-clean S13ifupdown S16pppd-dns S21alsa-utils S01mountkernfs.sh S07hostname.sh S10lvm2 S13mountall.sh S16procps S21bootmisc.sh S02udev S07hwclockfirst.sh S10module-init-tools S14mountall-bootclean.sh S16x11-common S21fuse S03mountdevsubfs.sh S07pcmciautils S10mtab.sh S15mountoverflowtmp S17mountnfs.sh S21screen-cleanup S04bootlogd S08checkroot.sh S10udev-mtab S16auditd S18mountnfs-bootclean.sh S21urandom S05keymap.sh S09cryptdisks-early S11cryptdisks S16networking S19console-screen.sh S22stop-bootlogd-single S06keyboard-setup S10hwclock.sh S12checkfs.sh S16policykit S20console-setup Looking at the X log file, the log file from the failed startup stops where the working X log continues to process input devices from HAL. Although hal is started before kdm. Maybe it doesn't start fast enough? Regards, Rik -- Greetings, Rik
