I would load X, start a kernel compile a couple of find / -name's and then
hit the power button. This usually messes up a couple of things...
On Wed, 15 Apr 1998, Bruce Tong wrote:
> I want to damage my file system. Not irreparably, but bad enough such that
> it doesn't automatically get fixed when the system is starting up. I know
> there's a level of damage where it stops and makes you run fsck yourself
> and that's what I need to do.
>
> Why?
>
> I'm writing some documentation for some of my customers which describes
> how to use fsck and I want to go through the motions so I can write an
> accurate list of steps. The "problem" is my Linux system is stable and I
> haven't seen or done this procedure since a power failure happened a year
> ago.
>
> I really don't want to clobber my system, just go through the motions of
> putting it back together. I do have a spare machine I can use on which
> nothing/nobody depends. I can clobber it if needed.
>
>
> Bruce Tong
> Systems Programmer
> Electronic Vision / FITNE
>
> mailto: [EMAIL PROTECTED]
> http://www.ev.net/fitne
>
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe" as the Subject.
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
