Exactly Philip !!

Separate /home, /usr, /var etc.... make sense in a networked environment.
For example, consider a case where we have swap, /, /usr/, /home, /var.

Now i as a network admin will take great care about backing up /home (more
care than other backups :-) anyway). Infact i could have it on a different
harddisk (if i have so many users) or even another computer. I will mount
this /home everytime.

Now if i screw up my system (somehow) or i want to to a complete reinstall,
i unmount /home, replace my system and remount it again. Done !!

I saw a post telling to mount / as readonly from your prompt. I dont think
it is possible. Because, things are being written to /proc, /var/logs,
wtmp, utmp all the time. You will have to boot linux from a floppy and
mount the / partition on the harddisk as readonly to be able to do an fsck.

<joke>
Another way to run fsck is to crash your system by just pressing the reset
switch which we are used to in windoze. Guaranteed fsck done !!!! ;-)
</joke>




Philip Tellis <[EMAIL PROTECTED]> on 12/20/99 07:51:38 PM

Please respond to [EMAIL PROTECTED]
                                                              
                                                              
                                                              
 To:      [EMAIL PROTECTED]                               
                                                              
 cc:      (bcc: Amit Kucheria/LTITLVSH)                       
                                                              
                                                              
                                                              
 Subject: Re: [ILUG-BOM] Fsck                                 
                                                              








It's pretty much a fact what Amit has said that most people only create
two partitions.  That's the way I started out.  It makes sense to first do
a very simple installation to find out how things work.  Once your
confident enough, you should format and reinstall.  Of course, backup
whatever you have done in that short time.

I was kinda forced into reinstalling cause some wise guy in the office
kept switching off the machine without a proper shutdown.  It finally came
to a point where the system would no keep running a fsck on every boot,
and I could not unmount properly.

I tarred/gzipped all files that I had changed, and ftp'ed the file to
another machine.  Then deleted the / and swap partns and reinstalled.

I now have partitions for:
/, /boot, /home, /tmp, /usr, /usr/src, /var

Works pretty well, and I can keep certain partitions read only until I
actually have to change files there.

Finally, I restored my backups.  That's where my next problem started.

I unknowingly restored my old fstab, so the next time I booted, I couldn't
do anything because my partition table did not reflect what was entered
into fstab.  I could not change fstab because / was mounted read only, and
I couldn't remount it because the partition entries in fstab did not match
the partition table.

I could not figure out any solution after two days, and decided to
reinstall again.  This time I restored correctly.

I have never lost any information because I always take backups and keep
them in varied locations that are really far apart.

Hope my experience will help anyone who wants to set up a new system.
Keep it simple to start with, get confident and then reinstall.  Then
recompile the kernel.

Philip


To subscribe / unsubscribe goto the site www.ilug-bom.org ., click on the
mailing list button and fill the appropriate information
and submit. For any other queries contact the ML maintener




To subscribe / unsubscribe goto the site www.ilug-bom.org ., click on the mailing list 
button and fill the appropriate information 
and submit. For any other queries contact the ML maintener

Reply via email to