wow you got that info in 1 minute..
thxs
OerHeks, easy to learn. easy to master. easy to master? C-c, no master.
heh...
and easy to put an end to.
:-)
it is "easy" to break a linux system, and then is easy to fix it.
but a standard user with his basic ideas can do it too.
OerHeks, I've had my share of experience dealing with "broken" windows machines and the short answer was: UNINSTALL is my favorite mantra. All the other fixes I've had to know how to fix it. ubuntu? common
i have no recent experience on windows, it must be a long time, i might have solved it by myself before, but is interesting to see
cfhowlett: i could imagine that it might be harder to fix broken windows than uninstalled ubuntu.
tomreyn, thus the reason I avoid it...
tomreyn: can you give me an overview about how do I find out what would be the correct recovery mode to enter?
FMan: none, since this is the chanel about grub
but you suggested to me to use a different kernel, so it is in the grub menu
FMan: you should only do so if the system can boot
FMan, just because you see it listed doesn't mean you should. just reboot.
otherwise, just reboot
I see "normal mode", "recovery mode", "root shell", "memtest" in the list
tomreyn: okay, so I'm rebooting
FMan: yes, so you'd have to determine this beforehand. but in case this doesn't work, boot from grub recovery menu entry and pass init=/bin/sh as kernel parameter, then look for initrd.lz and initramfs files which can be
Related links: