On Wed, Apr 21, 2010 at 12:12 PM, chris (fool) mccraw <[email protected]> wrote: > On Wed, Apr 21, 2010 at 07:04, Robert Citek <[email protected]> wrote: >> On Wed, Apr 21, 2010 at 9:24 AM, Michael Rasmussen <[email protected]> >> wrote: >>> Do whatever to corrupt your disk so you need to run fsck in single user >>> mode at boot. >> >> Here is what I did and was unsuccessful at creating a problem. On my >> system, /dev/sda1 contains the root '/' filesystem, so I tried this: >> >> 1) booted with a LiveCD >> 2) typed this in a terminal: >> >> $ sudo dd if=/dev/zero count=200 bs=1 \ >> of=/dev/sda1 seek=50000 conv=notrunc > > yikes, that's dangerous! you just overwrote 200 bytes in a random > place on your disk. some file is corrupted somewhere--hope it's not > your magnum opus or a config file you changed.
Nope, nothing important. The joys of running in a virtual environment. > if you notice a random program crashing, you've won. The goal was not to crash a random program. The goal was to create an "... [issue] at boot [so that] the system is in run level one prompting for a root password to do (for example) file system maintenance" in Ubuntu. If someone knows how to create such an issue, I'm curious to hear about it. Regards, - Robert _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
