On Sun, Jan 02, 2011 at 04:53:49PM -0500, Felix Miata wrote: > > First error: > bash: ./S50bluetooth: No such file or directory symlink -d /etc/rc.d/rc?.d/ > There should be no bluetooth configured, as there is no such hardware on this > 7 year old system. You should have cleaned that up (as above). You should also possibly do: cd /etc/rc.d/init.d && \ for f in *; do /sbin/chkconfig $f resetpriorities; done > Hmmm, no more errors through 99rc-local, and all exited. So something else is blocking you although this looks somewhat puzzling. Maybe systemd is indeed a culprit? Maybe something else? Missing getty processes? You can try to use SysRq key (check Google for docs if you do not know what I am talking about) but before attempting that you need to set kernel.sysrq = 1 in /etc/sysctl.conf before a boot attempt. > Hmmm again. After some time: > [900.089897] systemd[1]: systemd-tmpfiles-clean.service: main process exited, > code=exited, status=1 [900.094000] systemd[1]: Unit > systemd-tmpfiles-clean.service entered failed state. That is https://bugzilla.redhat.com/show_bug.cgi?id=662490 and it should not really affect what you doing beyond making a noise. > After running all that, runlevel still shows S. What did I miss? That running various services does not change a boot level. Check 'man telinit' (and "SEE ALSO" section there). > How & when do I get into interactive startup, See the previous replies but remember to put "3" into a boot line instead of "rhgb quiet". Michal -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
