Gentoo Archives: gentoo-user

From: Chen Huan <chenhuan0@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Problem about rc-update
Date: Wed, 04 Aug 2010 15:24:25
Message-Id: AANLkTik3oUYU8sKzTaDcZoOc1UwjbM2jxi0LiS0TSha_@mail.gmail.com
In Reply to: Re: [gentoo-user] Problem about rc-update by Bill Longman
1 Thanks
2
3 I tried many times rc-update del the service and add them back in, it isn't
4 work.......
5
6 here is the output of rc-update -s -v, I cannot find out there is anything
7 error...
8
9 fuse |
10 crypto-loop |
11 numlock |
12 procfs | boot
13 pydoc-3.1 |
14 avahi-daemon |
15 acpid |
16 device-mapper |
17 modules | boot
18 local | nonetwork default
19 net.lo | boot
20 alsasound | boot
21 lvm-monitoring |
22 swclock |
23 xdm | default
24 dmeventd |
25 swap | boot
26 sshd |
27 udev | sysinit
28 staticroute |
29 fbcondecor |
30 savecache | shutdown
31 mount-ro | shutdown
32 net.eth0 |
33 termencoding | boot
34 udev-dev-tarball |
35 netmount | default
36 dmesg | sysinit
37 network |
38 consolekit | default
39 devfs | sysinit
40 root | boot
41 urandom | boot
42 xdm-setup |
43 gpm |
44 atieventsd |
45 rsyncd |
46 udev-postmount | default
47 consolefont | boot
48 hostname | boot
49 sysfs |
50 pciparm |
51 NetworkManager | default
52 pydoc-2.6 |
53 esound |
54 vixie-cron | default
55 fsck | boot
56 syslog-ng | default
57 sysctl | boot
58 mtab | boot
59 dbus |
60 ntpd |
61 avahi-dnsconfd |
62 bootmisc | boot
63 killprocs | shutdown
64 dhcpcd |
65 ntp-client |
66 udev-mount |
67 localmount | boot
68 hwclock | boot
69 lvm |
70 nscd |
71 keymaps | boot
72 ch-laptop ch # rc-update show
73 procfs | boot
74 modules | boot
75 local | nonetwork default
76 net.lo | boot
77 alsasound | boot
78 xdm | default
79 swap | boot
80 udev | sysinit
81 savecache | shutdown
82 mount-ro | shutdown
83 termencoding | boot
84 netmount | default
85 dmesg | sysinit
86 consolekit | default
87 devfs | sysinit
88 root | boot
89 urandom | boot
90 udev-postmount | default
91 consolefont | boot
92 hostname | boot
93 NetworkManager | default
94 vixie-cron | default
95 fsck | boot
96 syslog-ng | default
97 sysctl | boot
98 mtab | boot
99 bootmisc | boot
100 killprocs | shutdown
101 localmount | boot
102 hwclock | boot
103 keymaps | boot
104
105
106
107
108 2010/8/4 Bill Longman <bill.longman@×××××.com>
109
110 > On 08/04/2010 12:15 AM, Chen Huan wrote:
111 > > Hi,everybody, I got a very very strange problems.
112 > >
113 > > I have install gnome, and when I try to add xdm to default runlevel, use
114 > > command "rc-update add xdm default", it is normal
115 > >
116 > > and output of rc-update show is right
117 > >
118 > > but when I restart computer, the xdm doesn't auto start, when I log in
119 > the
120 > > system, and exec "/etc/init.d/xdm start", it is started normally
121 > >
122 > > There is no any information about xdm when the system starting......It is
123 > > very strange...Could somebody help me...
124 > >
125 > > And NetworkManager and alsasound have the same problem.....
126 > >
127 > > here is the ouput of rc-update show:
128 > >
129 > > procfs | boot
130 > > modules | boot
131 > > local | nonetwork default
132 > > net.lo | boot
133 > > alsasound | boot
134 > > xdm | default
135 > > swap | boot
136 > > udev | sysinit
137 > > savecache | shutdown
138 > > mount-ro | shutdown
139 > > termencoding | boot
140 > > netmount | default
141 > > dmesg | sysinit
142 > > consolekit | default
143 > > devfs | sysinit
144 > > root | boot
145 > > urandom | boot
146 > > udev-postmount | default
147 > > consolefont | boot
148 > > hostname | boot
149 > > NetworkManager | default
150 > > vixie-cron | default
151 > > fsck | boot
152 > > syslog-ng | default
153 > > sysctl | boot
154 > > mtab | boot
155 > > bootmisc | boot
156 > > killprocs | shutdown
157 > > localmount | boot
158 > > hwclock | boot
159 > > keymaps | boot
160 > >
161 > > And I am using operc-0.6.1-r1 and baselayout-2.0.1
162 >
163 > That is strange. I don't have the answer, but I could offer a
164 > suggestion. You might want to try "rc-update del" the services that are
165 > having trouble and then adding them back in. You might want to use
166 > "rc-update -s -v" for your runlevels and see if there's anything broken.
167 > They'll be reported at the top of the list. Good luck.
168 >
169 >
170 >