Re: [expert] emergency
On Mon, 9 Jun 2003 03:07 am, Aleksey Naumov sent this :- Also there is no init.d, so all start/stop scripts are gone. Wonder how that could have happened??? Unfortunately a reinstall is about all you can do. the second choice of checking the system with the data loss warning remove much of what is required for a boot it seems. I have had this problem on a test machine. If on the second option to check the file system is refused and whatever is suggested be applied. n reboot the system Ctrl-d it boots up again without any data loss other than what might have been on the monitor. -- Due to circumstances beyond my control, I am master of my fate and captain of my soul. Ashley Brillaint This email is guaranteed to be wholly Linux Mandrake 9.0, Kmail v1.4.3 and OpenOffice.org1.0.3 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
On Mon, 2003-06-09 at 11:41, charlie wrote: On Mon, 9 Jun 2003 03:07 am, Aleksey Naumov sent this :- Also there is no init.d, so all start/stop scripts are gone. Wonder how that could have happened??? Unfortunately a reinstall is about all you can do. the second choice of checking the system with the data loss warning remove much of what is required for a boot it seems. I have had this problem on a test machine. If on the second option to check the file system is refused and whatever is suggested be applied. n reboot the system Ctrl-d it boots up again without any data loss other than what might have been on the monitor. Ok,, Since the box is somewhat hosed anyway.. I'd do this. Don't re-install. Do an upgrade. It will fill in the blanks and hopefully give you back a box that is close enough to be easily repairable. James Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
On Mon, 9 Jun 2003 09:43 am, Steven Broos sent this :- So IMHO ext3 is just preferable above ext2. If I'm wrong, correct me please :-) Steven Having used both, I tend to agree that ext3 is superior to ext2. -- In a grove of tall bamboos Beside an ancient temple Steam rolls from the brazier In fragrant white clouds; I show you the path of Sages Beyond this floating world, But will you understand The lasting taste of spring? - Baisao (1675-1763) This email is guaranteed to be wholly Linux Mandrake 9.0, Kmail v1.4.3 and OpenOffice.org1.0.3 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
On Sun, 8 Jun 2003 04:09 am, Aleksey Naumov sent this :- 3. I did hard reboot. Selected y for System Integrity check. Problems were reported on /dev/hda6 (that's my / as I recalled later). System offered to fix problems (data may be lost), I said n hoping first to boot and save my today's work. It seems I should have said y! More messages about problems on /dev/hda6 with offers to fix. At this point I decided to reboot and answer y to 'fix problems?' question. Don't say yes on the second option. Just do, I think, Ctrl-d and that will restart it as normal and all will be well. It will give you the keystrokes in the error message when you say no. Maybe even before. But as your system is down, just insert your #1 CD Mandrake 9.1 and repair it. Charlie -- Standing on a cliff, Among the pines and oaks; Spring has come Clothed in mist. - Ryokan (1758-1831) This email is guaranteed to be wholly Linux Mandrake 9.0, Kmail v1.4.3 and OpenOffice.org1.0.3 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
On Mon, 2003-06-09 at 06:40, Rob Blomquist wrote: I say watch out for ext3. It may give headaches to some of us. ext3 is the same filesystem as ext2, only with a journaling mode. If ext3 goes mad on you, mount it as ext2 and it will work just fine. There are commands to fix the journaling-files too. So IMHO ext3 is just preferable above ext2. If I'm wrong, correct me please :-) Steven Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
On Sun, 2003-06-08 at 23:33, Rolf Pedersen wrote: Aleksey Naumov wrote: Thanks to all (Rob, Rolf, Steven) for good suggestions! No linux-nonfb and failsafe do not for me giving the same INIT messages. I was able to make some progress by booting with MDK 9.1 CD into rescue, then going to console: (a) Ran fsck.ext2 on my / and it complained that the superblock is bad. Ran it again with the alternate superblock (8193) and fixed a whole lot of problems (incorrect ref counts, etc.). Still no booting, get the same INIT messages (b) Then I noticed that in my /etc there is no rc.d at all, no wonder init complaines that it cannot execute /etc/rc.d/rc.sysinit and there are no more processes at a runlevel. Also there is no init.d, so all start/stop scripts are gone. Wonder how that could have happened??? More importantly, what could I do now short of reinstalling? I don't have rc.d backed up anywhere. Is it possible to get rc.d by installing an rpm, which one then? Or do these scripts get generated somehow during an install? Any ideas are welcome... Thank you, Aleksey $ urpmf /etc/rc.d initscripts:/etc/rc.d initscripts:/etc/rc.d/init.d initscripts:/etc/rc.d/init.d/alsa initscripts:/etc/rc.d/init.d/dm initscripts:/etc/rc.d/init.d/functions initscripts:/etc/rc.d/init.d/halt initscripts:/etc/rc.d/init.d/kheader initscripts:/etc/rc.d/init.d/killall initscripts:/etc/rc.d/init.d/mandrake_consmap initscripts:/etc/rc.d/init.d/mandrake_everytime initscripts:/etc/rc.d/init.d/mandrake_firstime initscripts:/etc/rc.d/init.d/netfs initscripts:/etc/rc.d/init.d/network initscripts:/etc/rc.d/init.d/partmon initscripts:/etc/rc.d/init.d/random initscripts:/etc/rc.d/init.d/rawdevices initscripts:/etc/rc.d/init.d/single initscripts:/etc/rc.d/init.d/sound initscripts:/etc/rc.d/init.d/usb initscripts:/etc/rc.d/rc initscripts:/etc/rc.d/rc.local initscripts:/etc/rc.d/rc.modules initscripts:/etc/rc.d/rc.sysinit initscripts:/etc/rc.d/rc0.d initscripts:/etc/rc.d/rc0.d/S00killall initscripts:/etc/rc.d/rc0.d/S01halt initscripts:/etc/rc.d/rc1.d initscripts:/etc/rc.d/rc1.d/S00single initscripts:/etc/rc.d/rc2.d initscripts:/etc/rc.d/rc2.d/S99local initscripts:/etc/rc.d/rc3.d initscripts:/etc/rc.d/rc3.d/S99local initscripts:/etc/rc.d/rc4.d initscripts:/etc/rc.d/rc4.d/S99local initscripts:/etc/rc.d/rc5.d initscripts:/etc/rc.d/rc5.d/S99local initscripts:/etc/rc.d/rc6.d initscripts:/etc/rc.d/rc6.d/S00killall initscripts:/etc/rc.d/rc6.d/S01reboot console-tools:/etc/rc.d/init.d/keytable sysklogd:/etc/rc.d/init.d/syslog vixie-cron:/etc/rc.d/init.d/crond xinetd:/etc/rc.d/init.d/xinetd portmap:/etc/rc.d/init.d/portmap XFree86-xfs:/etc/rc.d/init.d/xfs apache-conf:/etc/rc.d/init.d apache-conf:/etc/rc.d/init.d/httpd [..] A lot more packages have files/directories in /etc/rc.d/././. Is your /home a separate partition? Can you mount and read it from a rescue session? Or, don't you say that 'failsafe' will boot for you? If so, you can do the work from there. You might need to run fsck again. Be careful. Think about saving /home before you do something radical. If you mount your installation on /mnt and chroot /mnt in the rescue session, you might be able to call man fsck to get some info. Also, I thought there was an option to upgrade/repair an existing Mandrake installation when you booted CD1. Can't say from experience but such a process might work in this case. It would be better to copy the valuable things in /home somewhere safe, first. I would recommend installing on reiserfs if you have to do a complete install again. There are other journalling filesystems but I have had a good history with reiserfs. Rolf might help if was root when looking for stuff in /etc __ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency [resolved]
Thanks to all for valuable suggestions! I ended up taring /home to a FAT32 partition, then reinstalling from scratch and restoring /home. This time I set / and /home to ReiserFS (Rolf, Rob -- thanks for the advise). Funny, after all this work -- in the new installation trying to access Zip in KDE locks up the panel again (this is where my problem started in the first place: trying to kill X at this point with Ctrl-Alt-Backspace), only this time I just waited :-) ... it does open up after a minute. Somewhat dissappointing that it is so sluggish, maybe I'll disable supermount on it... Again, thank you all for helping! Aleksey Aleksey Naumov wrote: Thanks to all (Rob, Rolf, Steven) for good suggestions! No linux-nonfb and failsafe do not for me giving the same INIT messages. I was able to make some progress by booting with MDK 9.1 CD into rescue, then going to console: (a) Ran fsck.ext2 on my / and it complained that the superblock is bad. Ran it again with the alternate superblock (8193) and fixed a whole lot of problems (incorrect ref counts, etc.). Still no booting, get the same INIT messages (b) Then I noticed that in my /etc there is no rc.d at all, no wonder init complaines that it cannot execute /etc/rc.d/rc.sysinit and there are no more processes at a runlevel. Also there is no init.d, so all start/stop scripts are gone. Wonder how that could have happened??? More importantly, what could I do now short of reinstalling? I don't have rc.d backed up anywhere. Is it possible to get rc.d by installing an rpm, which one then? Or do these scripts get generated somehow during an install? Any ideas are welcome... Thank you, Aleksey $ urpmf /etc/rc.d initscripts:/etc/rc.d initscripts:/etc/rc.d/init.d initscripts:/etc/rc.d/init.d/alsa initscripts:/etc/rc.d/init.d/dm initscripts:/etc/rc.d/init.d/functions initscripts:/etc/rc.d/init.d/halt initscripts:/etc/rc.d/init.d/kheader initscripts:/etc/rc.d/init.d/killall initscripts:/etc/rc.d/init.d/mandrake_consmap initscripts:/etc/rc.d/init.d/mandrake_everytime initscripts:/etc/rc.d/init.d/mandrake_firstime initscripts:/etc/rc.d/init.d/netfs initscripts:/etc/rc.d/init.d/network initscripts:/etc/rc.d/init.d/partmon initscripts:/etc/rc.d/init.d/random initscripts:/etc/rc.d/init.d/rawdevices initscripts:/etc/rc.d/init.d/single initscripts:/etc/rc.d/init.d/sound initscripts:/etc/rc.d/init.d/usb initscripts:/etc/rc.d/rc initscripts:/etc/rc.d/rc.local initscripts:/etc/rc.d/rc.modules initscripts:/etc/rc.d/rc.sysinit initscripts:/etc/rc.d/rc0.d initscripts:/etc/rc.d/rc0.d/S00killall initscripts:/etc/rc.d/rc0.d/S01halt initscripts:/etc/rc.d/rc1.d initscripts:/etc/rc.d/rc1.d/S00single initscripts:/etc/rc.d/rc2.d initscripts:/etc/rc.d/rc2.d/S99local initscripts:/etc/rc.d/rc3.d initscripts:/etc/rc.d/rc3.d/S99local initscripts:/etc/rc.d/rc4.d initscripts:/etc/rc.d/rc4.d/S99local initscripts:/etc/rc.d/rc5.d initscripts:/etc/rc.d/rc5.d/S99local initscripts:/etc/rc.d/rc6.d initscripts:/etc/rc.d/rc6.d/S00killall initscripts:/etc/rc.d/rc6.d/S01reboot console-tools:/etc/rc.d/init.d/keytable sysklogd:/etc/rc.d/init.d/syslog vixie-cron:/etc/rc.d/init.d/crond xinetd:/etc/rc.d/init.d/xinetd portmap:/etc/rc.d/init.d/portmap XFree86-xfs:/etc/rc.d/init.d/xfs apache-conf:/etc/rc.d/init.d apache-conf:/etc/rc.d/init.d/httpd [..] A lot more packages have files/directories in /etc/rc.d/././. Is your /home a separate partition? Can you mount and read it from a rescue session? Or, don't you say that 'failsafe' will boot for you? If so, you can do the work from there. You might need to run fsck again. Be careful. Think about saving /home before you do something radical. If you mount your installation on /mnt and chroot /mnt in the rescue session, you might be able to call man fsck to get some info. Also, I thought there was an option to upgrade/repair an existing Mandrake installation when you booted CD1. Can't say from experience but such a process might work in this case. It would be better to copy the valuable things in /home somewhere safe, first. I would recommend installing on reiserfs if you have to do a complete install again. There are other journalling filesystems but I have had a good history with reiserfs. Rolf -- Aleksey Naumov GIS Analyst Center for Health and Social Research Buffalo State College Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[expert] emergency
Ok, I have a severe problem with MDK 9.1, can't even boot anymore. Can anyone help? Here is what happened: 1. In KDE I selected Removable Media/Zip to mount/open in Konq a zip disk 2. KDE panel lockup. This happened to me before, I guess because of problems with automount. Previously I 'fixed' it by Ctrl-Alt-Backspace to kill X and log in again (couldn't find anything better). Didn't work this time, got system lockup. 3. I did hard reboot. Selected y for System Integrity check. Problems were reported on /dev/hda6 (that's my / as I recalled later). System offered to fix problems (data may be lost), I said n hoping first to boot and save my today's work. It seems I should have said y! More messages about problems on /dev/hda6 with offers to fix. At this point I decided to reboot and answer y to 'fix problems?' question. 4. Hard reboot. Even worse now, got these messages right away: INIT: cannot execute /etc/rc.d/rc.sysinit INIT: entering runlevel: 5 INIT: cannot execute /etc/rc.d/rc INIT: Id 1 respawning too fast: disabled for 5 minutes (Same message repeated for Id 2 - 6) INIT: no more processes left in this runlevel 5. Ok, tried to boot from my MDK 9.1 boot disk (made during the installation), got: SYSLINUX 1.67 Could not find kernel image: linux boot: What do I do now? 6. Tried booting from MDK 9.1 install CD and going into rescue, but that stuff is just way over my head... --- Ok, it seems I made a bad decision when I said n to fixing / problems :-( Do I have any choices at this point (feasible for someone who is a day-to-day user but not an expert), short of reinstalling 9.1 (at least the /usr, so I don't lose /home, etc.)? Thank you! Sleep time now :-) Aleksey Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
4. Hard reboot. Even worse now, got these messages right away: INIT: cannot execute /etc/rc.d/rc.sysinit INIT: entering runlevel: 5 INIT: cannot execute /etc/rc.d/rc INIT: Id 1 respawning too fast: disabled for 5 minutes (Same message repeated for Id 2 - 6) INIT: no more processes left in this runlevel 5. Ok, tried to boot from my MDK 9.1 boot disk (made during the installation), got: SYSLINUX 1.67 Could not find kernel image: linux boot: What do I do now? 6. Tried booting from MDK 9.1 install CD and going into rescue, but that stuff is just way over my head... My guess is that the kernel got munched in the crash, so you can't boot. You should try Mandrake's other boot choices: linux-nonfb or failsafe at the boot: prompt. You are on the right path to boot into your machine with the install CD. I agree it is harder to navigate, and the real bummer it is read-only on the disk. If these fail, you can try to copy important stuff off the disk, and then reinstall. -- Linux: For the people, by the people. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
Aleksey Naumov wrote: Ok, I have a severe problem with MDK 9.1, can't even boot anymore. Can anyone help? [..] 6. Tried booting from MDK 9.1 install CD and going into rescue, but that stuff is just way over my head... There are some good, basic instructions for using the rescue mode at MUO Docs: http://www.mandrakeuser.org/docs/admin/index.html#er Rolf Thank you! Sleep time now :-) Aleksey Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
Thanks to all (Rob, Rolf, Steven) for good suggestions! No linux-nonfb and failsafe do not for me giving the same INIT messages. I was able to make some progress by booting with MDK 9.1 CD into rescue, then going to console: (a) Ran fsck.ext2 on my / and it complained that the superblock is bad. Ran it again with the alternate superblock (8193) and fixed a whole lot of problems (incorrect ref counts, etc.). Still no booting, get the same INIT messages (b) Then I noticed that in my /etc there is no rc.d at all, no wonder init complaines that it cannot execute /etc/rc.d/rc.sysinit and there are no more processes at a runlevel. Also there is no init.d, so all start/stop scripts are gone. Wonder how that could have happened??? More importantly, what could I do now short of reinstalling? I don't have rc.d backed up anywhere. Is it possible to get rc.d by installing an rpm, which one then? Or do these scripts get generated somehow during an install? Any ideas are welcome... Thank you, Aleksey Steven Broos wrote: I had a comparable problem a couple days ago. Same errors... Turned out to be my fault (ofcourse): I changed something in /etc/security/console.perms. Because of that reason, my harddrives weren't listed in /dev/, could not be load, etc... It gave a suggestion maybe your MBR is bad, try this e2fsck I booted in linux-failsave mode (which was working) and edited the file console.perms. (I forgot to comment a line :-)) Maybe you can learn some more by watching the booting-errors above the suggestions closely ? (you can scroll up by pressing shift-pgup) Steven On Sun, 2003-06-08 at 06:09, Aleksey Naumov wrote: Ok, I have a severe problem with MDK 9.1, can't even boot anymore. Can anyone help? Here is what happened: 1. In KDE I selected Removable Media/Zip to mount/open in Konq a zip disk 2. KDE panel lockup. This happened to me before, I guess because of problems with automount. Previously I 'fixed' it by Ctrl-Alt-Backspace to kill X and log in again (couldn't find anything better). Didn't work this time, got system lockup. 3. I did hard reboot. Selected y for System Integrity check. Problems were reported on /dev/hda6 (that's my / as I recalled later). System offered to fix problems (data may be lost), I said n hoping first to boot and save my today's work. It seems I should have said y! More messages about problems on /dev/hda6 with offers to fix. At this point I decided to reboot and answer y to 'fix problems?' question. 4. Hard reboot. Even worse now, got these messages right away: INIT: cannot execute /etc/rc.d/rc.sysinit INIT: entering runlevel: 5 INIT: cannot execute /etc/rc.d/rc INIT: Id 1 respawning too fast: disabled for 5 minutes (Same message repeated for Id 2 - 6) INIT: no more processes left in this runlevel 5. Ok, tried to boot from my MDK 9.1 boot disk (made during the installation), got: SYSLINUX 1.67 Could not find kernel image: linux boot: What do I do now? 6. Tried booting from MDK 9.1 install CD and going into rescue, but that stuff is just way over my head... --- Ok, it seems I made a bad decision when I said n to fixing / problems :-( Do I have any choices at this point (feasible for someone who is a day-to-day user but not an expert), short of reinstalling 9.1 (at least the /usr, so I don't lose /home, etc.)? Thank you! Sleep time now :-) Aleksey __ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
Aleksey Naumov wrote: Thanks to all (Rob, Rolf, Steven) for good suggestions! No linux-nonfb and failsafe do not for me giving the same INIT messages. I was able to make some progress by booting with MDK 9.1 CD into rescue, then going to console: (a) Ran fsck.ext2 on my / and it complained that the superblock is bad. Ran it again with the alternate superblock (8193) and fixed a whole lot of problems (incorrect ref counts, etc.). Still no booting, get the same INIT messages (b) Then I noticed that in my /etc there is no rc.d at all, no wonder init complaines that it cannot execute /etc/rc.d/rc.sysinit and there are no more processes at a runlevel. Also there is no init.d, so all start/stop scripts are gone. Wonder how that could have happened??? More importantly, what could I do now short of reinstalling? I don't have rc.d backed up anywhere. Is it possible to get rc.d by installing an rpm, which one then? Or do these scripts get generated somehow during an install? Any ideas are welcome... Thank you, Aleksey $ urpmf /etc/rc.d initscripts:/etc/rc.d initscripts:/etc/rc.d/init.d initscripts:/etc/rc.d/init.d/alsa initscripts:/etc/rc.d/init.d/dm initscripts:/etc/rc.d/init.d/functions initscripts:/etc/rc.d/init.d/halt initscripts:/etc/rc.d/init.d/kheader initscripts:/etc/rc.d/init.d/killall initscripts:/etc/rc.d/init.d/mandrake_consmap initscripts:/etc/rc.d/init.d/mandrake_everytime initscripts:/etc/rc.d/init.d/mandrake_firstime initscripts:/etc/rc.d/init.d/netfs initscripts:/etc/rc.d/init.d/network initscripts:/etc/rc.d/init.d/partmon initscripts:/etc/rc.d/init.d/random initscripts:/etc/rc.d/init.d/rawdevices initscripts:/etc/rc.d/init.d/single initscripts:/etc/rc.d/init.d/sound initscripts:/etc/rc.d/init.d/usb initscripts:/etc/rc.d/rc initscripts:/etc/rc.d/rc.local initscripts:/etc/rc.d/rc.modules initscripts:/etc/rc.d/rc.sysinit initscripts:/etc/rc.d/rc0.d initscripts:/etc/rc.d/rc0.d/S00killall initscripts:/etc/rc.d/rc0.d/S01halt initscripts:/etc/rc.d/rc1.d initscripts:/etc/rc.d/rc1.d/S00single initscripts:/etc/rc.d/rc2.d initscripts:/etc/rc.d/rc2.d/S99local initscripts:/etc/rc.d/rc3.d initscripts:/etc/rc.d/rc3.d/S99local initscripts:/etc/rc.d/rc4.d initscripts:/etc/rc.d/rc4.d/S99local initscripts:/etc/rc.d/rc5.d initscripts:/etc/rc.d/rc5.d/S99local initscripts:/etc/rc.d/rc6.d initscripts:/etc/rc.d/rc6.d/S00killall initscripts:/etc/rc.d/rc6.d/S01reboot console-tools:/etc/rc.d/init.d/keytable sysklogd:/etc/rc.d/init.d/syslog vixie-cron:/etc/rc.d/init.d/crond xinetd:/etc/rc.d/init.d/xinetd portmap:/etc/rc.d/init.d/portmap XFree86-xfs:/etc/rc.d/init.d/xfs apache-conf:/etc/rc.d/init.d apache-conf:/etc/rc.d/init.d/httpd [..] A lot more packages have files/directories in /etc/rc.d/././. Is your /home a separate partition? Can you mount and read it from a rescue session? Or, don't you say that 'failsafe' will boot for you? If so, you can do the work from there. You might need to run fsck again. Be careful. Think about saving /home before you do something radical. If you mount your installation on /mnt and chroot /mnt in the rescue session, you might be able to call man fsck to get some info. Also, I thought there was an option to upgrade/repair an existing Mandrake installation when you booted CD1. Can't say from experience but such a process might work in this case. It would be better to copy the valuable things in /home somewhere safe, first. I would recommend installing on reiserfs if you have to do a complete install again. There are other journalling filesystems but I have had a good history with reiserfs. Rolf Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] emergency
(a) Ran fsck.ext2 on my / and it complained that the superblock is bad. Ran it again with the alternate superblock (8193) and fixed a whole lot of problems (incorrect ref counts, etc.). Still no booting, get the same INIT messages I had the same problem over and over again with the default ext3 format. I even went so far as to buy a new HD. Then it happened with that one. So I reformatted my drives with a mixture of XFS, ext2, and ReiserFS, and I have not had a problem yet. I say watch out for ext3. It may give headaches to some of us. Rob -- Linux: For the people, by the people. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Emergency exit ??
Thierry Vignaud wrote: Andrea Celli wrote: What can I do in such a situation? Is it possible to configure something in order to allow the "reset button" of PC to reboot safely the system? In /etc/inittab the sequence cntl-Alt-Del is mapped in a similar way ... false. the init (in fact the process 0) exec the halt bin when you press alt ctrl del) but reset cannot be detected, when pressed, it cut down and up fast the alim in order to reboot. OK. This was an hope... I'll pay more attention in installing/uninstalling programs. Thank for all answers! but there is a solution : the magic key : altgr+scre=nnprint+sn then u then b (wait a few seconds betwenn s, u and b) whixh 'll Sync the disk and the cache, Umount the fs and reBoot Great, but I didn't understood thoroughly: - Does it read altgr+screenprint+s...u...b ? - Is it valid only for Mandrake or for all Linux distributions? ciao, andrea
Re: [expert] Emergency exit ??
Great, but I didn't understood thoroughly: - Does it read altgr+screenprint+s...u...b ? - Is it valid only for Mandrake or for all Linux distributions? ciao, andrea this is an option when you compile a (new) kernel, I think it's compiled in the supplied Mandrake kernel. Don't know for sure, I always compile a new one. marc
Re: [expert] Emergency exit ??
Andrea Celli wrote: In the next days I had a trouble with my Linux-Mndk-6.0. I done something wrong (may be installing vmware). As result, when I tried to mount cdrom, keyboard and mouse freeze completely and suddenly. I was no able to switch console (cntl-alt-Fn), stop process (cntl-C, cntl-D, cntl-z,...), reboot via cntl-Alt-Del, ... I waited some hours then I had to switch off the power. What can I do in such a situation? Is it possible to configure something in order to allow the "reset button" of PC to reboot safely the system? In /etc/inittab the sequence cntl-Alt-Del is mapped in a similar way ... false. the init (in fact the process 0) exec the halt bin when you press alt ctrl del) but reset cannot be detected, when pressed, it cut down and up fast the alim in order to reboot. but there is a solution : the magic key : altgr+scre=nnprint+sn then u then b (wait a few seconds betwenn s, u and b) whixh 'll Sync the disk and the cache, Umount the fs and reBoot -- MandrakeSoft http://www.mandrakesoft.com/ somewhere between the playstation and the super cray --Thierry
Re: [expert] Emergency exit ??
On Thu, 12 Aug 1999, Andrea Celli wrote: In the next days I had a trouble with my Linux-Mndk-6.0. I done something wrong (may be installing vmware). As result, when I tried to mount cdrom, keyboard and mouse freeze completely and suddenly. I was no able to switch console (cntl-alt-Fn), stop process (cntl-C, cntl-D, cntl-z,...), reboot via cntl-Alt-Del, ... I waited some hours then I had to switch off the power. What can I do in such a situation? Is it possible to configure something in order to allow the "reset button" of PC to reboot safely the system? In /etc/inittab the sequence cntl-Alt-Del is mapped in a similar way ... bye, Andrea in PCs, the Reset Button is a hardware switch. It is connected to your MOBO. Its a hardware setting, like temporaily disconnecting power to the system [I donnu how it works exactly but that's an rough approximation]. Not a software one. The 3-Fingered Salute [CTR-ALT-DEL] combination is a software reset. The OS [Win9x/NT/OS2/LINUX/BSD] reads it and does the appopiate action. Although is is theortically possible to use the RESET button as a shutdown, it would require A] a homemade adapter or B] Solidering on the MOBO. Personally, those aren't good choices. I pretty much recommend in your case a Clean install of LINUX.
