Re: Spontaneously aborting X startup during Linux boot process
On Sunday 19 December 2010 23:18:19 Bob Proulx wrote: I wouldn't transition to single user mode from multiuser mode directly myself. I have never had any problems with init 1, wherever I used it from, other than that KDE doesn't shut down very cleanly in the sense that it does not save everything I am working on.Ditto init 0 and init 6. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101011136.14959.lisi.re...@gmail.com
Re: Spontaneously aborting X startup during Linux boot process
Dne, 01. 01. 2011 12:36:14 je Lisi napisal(a): On Sunday 19 December 2010 23:18:19 Bob Proulx wrote: I wouldn't transition to single user mode from multiuser mode directly myself. I have never had any problems with init 1, wherever I used it from, other than that KDE doesn't shut down very cleanly in the sense that it does not save everything I am working on.Ditto init 0 and init 6. Lisi I've seen init 1 recommended as the procedure to use when doing maintenance tasks that can't be done with X running. On my two Gnome systems it shuts down the desktop environment quite cleanly, as far as I can tell. -- Cheerio, Klistvud http://bufferoverflow.tiddlyspot.com Certifiable Loonix User #481801 Please reply to the list, not to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1293882658.3253...@compax
Re: Spontaneously aborting X startup during Linux boot process
On Thursday 16 December 2010 18:31:46 Bob Proulx wrote: Juan Ignacio Gaudio wrote: I just need to be able to change to a console tty and restore the previous xorg.conf. But as X starts automatically I can't manage to do that before X crashes and I lose the keyboard again... do you know of a way of changing the runlevel to just console (no X) or aborting X startup during Linux boot process (some key combination or anything). I searched it and turned up to be pretty simple. It's just needed to append the runlevel number to the kernel line, something like this example: kernel /boot/vmlinuz-2.6.30 root=/dev/sda2 ro 3 Note that the above isn't going to boot without X on a default Debian Lenny system unless you have changed it. By default on Debian all runlevels are configured the same. There isn't anything magical about runlevel 2 or 3 or 4 or 5. By default they are all the same. You can as a local admin configure them to be different but unless you have done so then booting runlevel 3 won't be any different than booting the default runlevel 2. X will start the same. The traditional solution would be to boot single user mode with S or 'single' and make corrections from there. Alternatively you can disable gdm/kdm/xdm temporarily and then reboot to the full system which will then be a text console. Once we are thinking in terms of run-level by number, why not just use 1 (without the quotation marks!) which on a Debian system is the CLI? Or, of course, choose single user in GRUB. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201012191553.41467.lisi.re...@gmail.com
Re: Spontaneously aborting X startup during Linux boot process
Lisi wrote: Bob Proulx wrote: The traditional solution would be to boot single user mode with S or 'single' and make corrections from there. Alternatively you can disable gdm/kdm/xdm temporarily and then reboot to the full system which will then be a text console. Once we are thinking in terms of run-level by number, why not just use 1 (without the quotation marks!) which on a Debian system is the CLI? Or, of course, choose single user in GRUB. Runlevel 1 is almost universially used to implement single user mode. When you ask why not use 1 instead of single the answer is that there isn't any reason. I just think it more clear to ask for single user mode directly and not jump to the runlevel that you know implements it. But you can if you know that information. No reason not to. To see Debian's documentation on runlevels look here: /usr/share/doc/sysv-rc/README.runlevels.gz To look to see how different systems have implemented runlevels see this Wikipedia page. I think it does a good job of capturing the differences. I consider this information must know info for talking about runlevels. Make sure you look at the Unix System V table because that is the grandfather of all of the present systems. http://en.wikipedia.org/wiki/Runlevel Bob P.S. The confusion that results from people looking today (as opposed to twenty years ago) at runlevels is one of the reasons people want to move to the new parallel boot process. Every system has implemented these numbers slightly differently. There isn't consistency across vendors. And I wouldn't want there to be! Because Debian has the better system in this case and I wouldn't want it to be forced to change to something worse such as one of the other vendor's offerings. Which is what would happen if it were standardized. The new parallel boot process sidesteps the issue entirely by moving to something completely different. signature.asc Description: Digital signature
Re: Spontaneously aborting X startup during Linux boot process
On Sunday 19 December 2010 18:46:18 Bob Proulx wrote: Runlevel 1 is almost universially used to implement single user mode. When you ask why not use 1 instead of single the answer is that there isn't any reason. I just think it more clear to ask for single user mode directly and not jump to the runlevel that you know implements it. But you can if you know that information. No reason not to. If I want to boot into single user from a cold start, I do it via GRUB. But if I am in a GUI and I want to actually change (rather than just bring up a tty) I use init 1. I don't think that init s would work - but you are probably about to tell me that it would. ;-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201012191902.11285.lisi.re...@gmail.com
Re: Spontaneously aborting X startup during Linux boot process
Lisi wrote: If I want to boot into single user from a cold start, I do it via GRUB. But if I am in a GUI and I want to actually change (rather than just bring up a tty) I use init 1. I don't think that init s would work - but you are probably about to tell me that it would. ;-) Yes. I am going to say, It should work. :-) Personally I wouldn't move from multiuser to single user directly. I would always reboot first and then boot into single user mode. Then when leaving single user mode reboot into multiple user mode. That way is very well tested. Doing other things /should/ work but I wouldn't be surprised to find interesting corner cases. It is definitely the road less well traveled. Bob signature.asc Description: Digital signature
Re: Spontaneously aborting X startup during Linux boot process
On 12/19/2010 02:09 PM, Bob Proulx wrote: tty) I use init 1. I don't think that init s would work - but you are probably about to tell me that it would. ;-) Yes. I am going to say, It should work. :-) Personally I wouldn't move from multiuser to single user directly. I would always reboot first and then boot into single user mode. Then when leaving single user mode reboot into multiple user mode. That way is very well tested. Doing other things /should/ work but I wouldn't be surprised to find interesting corner cases. It is definitely the road less well traveled. man init: /sbin/init [ -a ] [ -s ] [ -b ] [ -z xxx ] [ 0123456Ss ] /sbin/telinit [ -t SECONDS ] [ 0123456sSQqabcUu ] RUNLEVELS A runlevel is a software configuration of the system which allows only a selected group of processes to exist. The processes spawned by init for each of these runlevels are defined in the /etc/inittab file. Init can be in one of eight runlevels: 0-6 and S (a.k.a. s). The runlevel Runlevels S, 0, 1, and 6 are reserved. Runlevel S is used to initial- ize the system on boot. When starting runlevel S (on boot) or runlevel 1 (switching from a multi-user runlevel) the system is entering ``single-user mode'', after which the current runlevel is S. Runlevel 0 is used to halt the system; runlevel 6 is used to reboot the system. After booting through S the system automatically enters one of the multi-user runlevels 2 through 5, unless there was some problem that needs to be fixed by the administrator in single-user mode. Normally after entering single-user mode the administrator performs maintenance and then reboots the system. -- Paul Cartwright Registered Linux user # 367800 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d0e612a.6000...@pcartwright.com
Re: Spontaneously aborting X startup during Linux boot process
On Sunday 19 December 2010 19:09:46 Bob Proulx wrote: I don't think that init s would work - but you are probably about to tell me that it would. ;-) Yes. I am going to say, It should work. :-) My curtiosity being even more 'satiable than the elephant's child, I tried. The short answer is it doesn't work. The longer answer is that it threw the computer I was trying it on into a fit of the sulks: the konsole kept going with a root command prompt until there were enough to fill the screen. At that point it froze (still in the GUI) and the keyboard stopped working completely. I finally managed to sort it out by changing keyboard 3 times (2 x ps2 and 1 x USB), and rebooting twice, when the mouse at least (and at last) decided to wake up and I could do anything at all. I was about to resort to the on/off button (a very extreme solution!). After the first reboot the status had barely changed, but a second reboot returned (or seems to have returned) the system to normality. The messing around with keyboards probably did nothing more than prevent me from using the off button on the front of the computer, by giving me the illusion that I was doing something. So - Oh my friends be warned by me! init 1 is fine. init s is not. Paul has given a very clear exposition of the facts either above of below, depending on how you thread your emails. Oh - and I ought to have learned from the elephant's child that 'satiable curtiosity is sometimes highly undesirable. But it is probably a bit late now for me to learn. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201012192302.29029.lisi.re...@gmail.com
Re: Spontaneously aborting X startup during Linux boot process
Lisi wrote: Bob Proulx wrote: probably about to tell me that it would. ;-) Yes. I am going to say, It should work. :-) My curtiosity being even more 'satiable than the elephant's child, I tried. The short answer is it doesn't work. Note that I didn't say that it /did/ work. I said it /should/ work. I said there might be interesting corner cases. The longer answer is that it threw the computer I was trying it on into a fit of the sulks: the konsole kept going with a root command prompt until there were enough to fill the screen. You did it from an X11 session running KDE and a Konsole? A brave soul indeed! Because surely you realize that all of those processes will be (or at least should be) killed when transitioning to single user mode. In single user mode only the minimum system should be running. All that you should be left with should be a text console. Everything else should have been killed during the transition. Therefore to prevent disruption you would want to transition using the text console. Because otherwise your interface will be killed. At that point it froze (still in the GUI) and the keyboard stopped working completely. I finally managed to sort it out by changing keyboard 3 times (2 x ps2 and 1 x USB), and rebooting twice, when the mouse at least (and at last) decided to wake up and I could do anything at all. I was about to resort to the on/off button (a very extreme solution!). After the first reboot the status had barely changed, but a second reboot returned (or seems to have returned) the system to normality. Note also that I did say I would only go into single user mode from a reboot and not from multiuser mode directly. I wouldn't transition to single user mode from multiuser mode directly myself. I recommended against it. But you had to try it! Okay. But you are cutting your own path then! :-) Stay on the well traveled path unless you want to be a trailblazer. So - Oh my friends be warned by me! init 1 is fine. init s is not. Paul has given a very clear exposition of the facts either above of below, depending on how you thread your emails. Oh - and I ought to have learned from the elephant's child that 'satiable curtiosity is sometimes highly undesirable. But it is probably a bit late now for me to learn. Too funny! Sometimes curiousity kills the cat but if the cat survives then it is a smarter cat. :-) Bob signature.asc Description: Digital signature
Re: Spontaneously aborting X startup during Linux boot process
On 12/19/2010 06:02 PM, Lisi wrote: So - Oh my friends be warned by me! init 1 is fine. init s is not. Paul has given a very clear exposition of the facts either above of below, depending on how you thread your emails. I guess ( after reading Bob's reply) I forgot to mention, NORMALLY you do those from the ATL-F1 text login screen, where you login as ROOT... NOT from the X_windows ( gnome, kde...) my usual init commands are: # init 6 ( thats just a reboot) # init 0 ( turn the sucker OFF) # init 1 ( bring me down to single user mode!) # init 2 ( start the X-windows all the rest of the normal services) I used to use init S/s back in the UNIX days, and it used to mean something, probably not the same anymore.. It used to bring it down to single user umount all file systems EXCEPT root.. but I see from the man init : -s, S, single Single user mode boot. In this mode /etc/inittab is examined and the bootup rc scripts are usually run before the single user mode shell is started. now they have -b -b, emergency Boot directly into a single user shell without running any other startup scripts. so, there are still multiple ways to get booted, even in single user mode.. YMMV :) Oh - and I ought to have learned from the elephant's child that 'satiable curtiosity is sometimes highly undesirable. But it is probably a bit late now for me to learn. but you really didn't HURT anything, right? -- Paul Cartwright Registered Linux user # 367800 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d0e9e5b.6000...@pcartwright.com
Re: Spontaneously aborting X startup during Linux boot process
On Thu, 16 Dec 2010 12:06:31 +0100, Juan Ignacio Gaudio wrote: I broke my X (again) trying to install a graphics device driver on my Vostro 1000, so now I don't have video and the keyboard does not respond. I just need to be able to change to a console tty and restore the previous xorg.conf. But as X starts automatically I can't manage to do that before X crashes and I lose the keyboard again... do you know of a way of changing the runlevel to just console (no X) or aborting X startup during Linux boot process (some key combination or anything). I'm running Debian Lenny. In addition to all the good advice you got, remember that you could also login into the machine via SSH (should you have it enabled) and make the changes from there. X is crashing, not the whole system ;-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.17.10.05...@gmail.com
Re: Spontaneously aborting X startup during Linux boot process
Hello, As Bob suggested, I was able to boot in single user mode and restore X config file from there. Thanks for your help! Juan. 2010/12/17 Camaleón noela...@gmail.com On Thu, 16 Dec 2010 12:06:31 +0100, Juan Ignacio Gaudio wrote: I broke my X (again) trying to install a graphics device driver on my Vostro 1000, so now I don't have video and the keyboard does not respond. I just need to be able to change to a console tty and restore the previous xorg.conf. But as X starts automatically I can't manage to do that before X crashes and I lose the keyboard again... do you know of a way of changing the runlevel to just console (no X) or aborting X startup during Linux boot process (some key combination or anything). I'm running Debian Lenny. In addition to all the good advice you got, remember that you could also login into the machine via SSH (should you have it enabled) and make the changes from there. X is crashing, not the whole system ;-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.17.10.05...@gmail.com
Spontaneously aborting X startup during Linux boot process
Hello, I broke my X (again) trying to install a graphics device driver on my Vostro 1000, so now I don't have video and the keyboard does not respond. I just need to be able to change to a console tty and restore the previous xorg.conf. But as X starts automatically I can't manage to do that before X crashes and I lose the keyboard again... do you know of a way of changing the runlevel to just console (no X) or aborting X startup during Linux boot process (some key combination or anything). I'm running Debian Lenny. Thanks!
Re: Spontaneously aborting X startup during Linux boot process
You can instruct the OS to boot into a diffrent run level by editing the kernel line before you boot it in grub. It will affect only that boot. I don't have the comand syntex infront of me, but a google for it should produce the info. -Original Message- From: Juan Ignacio Gaudio jgau...@gmail.com Date: Thu, 16 Dec 2010 12:06:31 To: debian-user@lists.debian.org Subject: Spontaneously aborting X startup during Linux boot process Hello, I broke my X (again) trying to install a graphics device driver on my Vostro 1000, so now I don't have video and the keyboard does not respond. I just need to be able to change to a console tty and restore the previous xorg.conf. But as X starts automatically I can't manage to do that before X crashes and I lose the keyboard again... do you know of a way of changing the runlevel to just console (no X) or aborting X startup during Linux boot process (some key combination or anything). I'm running Debian Lenny. Thanks!
Re: Spontaneously aborting X startup during Linux boot process
Hello, I searched it and turned up to be pretty simple. It's just needed to append the runlevel number to the kernel line, something like this example: kernel /boot/vmlinuz-2.6.30 root=/dev/sda2 ro 3 Thanks, Juan 2010/12/16 teddi...@tmo.blackberry.net You can instruct the OS to boot into a diffrent run level by editing the kernel line before you boot it in grub. It will affect only that boot. I don't have the comand syntex infront of me, but a google for it should produce the info. -- *From: * Juan Ignacio Gaudio jgau...@gmail.com *Date: *Thu, 16 Dec 2010 12:06:31 +0100 *To: *debian-user@lists.debian.org *Subject: *Spontaneously aborting X startup during Linux boot process Hello, I broke my X (again) trying to install a graphics device driver on my Vostro 1000, so now I don't have video and the keyboard does not respond. I just need to be able to change to a console tty and restore the previous xorg.conf. But as X starts automatically I can't manage to do that before X crashes and I lose the keyboard again... do you know of a way of changing the runlevel to just console (no X) or aborting X startup during Linux boot process (some key combination or anything). I'm running Debian Lenny. Thanks!
Re: Spontaneously aborting X startup during Linux boot process
Juan Ignacio Gaudio wrote: I just need to be able to change to a console tty and restore the previous xorg.conf. But as X starts automatically I can't manage to do that before X crashes and I lose the keyboard again... do you know of a way of changing the runlevel to just console (no X) or aborting X startup during Linux boot process (some key combination or anything). I searched it and turned up to be pretty simple. It's just needed to append the runlevel number to the kernel line, something like this example: kernel /boot/vmlinuz-2.6.30 root=/dev/sda2 ro 3 Note that the above isn't going to boot without X on a default Debian Lenny system unless you have changed it. By default on Debian all runlevels are configured the same. There isn't anything magical about runlevel 2 or 3 or 4 or 5. By default they are all the same. You can as a local admin configure them to be different but unless you have done so then booting runlevel 3 won't be any different than booting the default runlevel 2. X will start the same. The traditional solution would be to boot single user mode with S or 'single' and make corrections from there. Alternatively you can disable gdm/kdm/xdm temporarily and then reboot to the full system which will then be a text console. Bob signature.asc Description: Digital signature
