After I suggested copying / into another partition called "/sysback",
and copying /usr into another partition called "/usrback", so that he
could boot using the backed up partitions for his system, on Thu, 1 Aug
2002, vvor wrote:
> so, if i restore, using your example, with root=/sysback, and boot my system
> using /sysback as my root...
>
> then, the first time i do this, the original /usr will be used, i.e., until
> i edit /sysback's fstab, correct? will this cause any errors? and, assuming
> no, once i do this, i can then boot the "mirror" and it will behave
> precisely like the original, barring any physical diffs between the hdd's?
If you don't change /sysback/etc/fstab, the same physical disk
partition that contains /usr will be mounted at the mirror's /usr, and it
will behave precisely like the original because it is the original. And
if you copy /usr into /usrback, and change /sysback/etc/fstab to
mount the copied partition at the mirror's /usr, that should work, too.
But unless you do something about it, /sysback/etc/fstab will still
specify the old partition for / even when you boot with the mirror as
root. I don't think that will cause trouble, but I could be wrong. So if
I were you, I'd change /sysback/etc/fstab so that it says "/" is the
physical disk partition that's now called "/sysback".
You shouldn't be especially afraid to try it out. If you haven't
changed anything in your current / and /usr, and the mirrors don't work,
you can always reboot without using what you now call /sysback as the
root.
>
> if i copy "/" into "/sysback", does copy copy everything, even the copy
> program itself? are there things that cannot be copied?
>
I guess by now you've done this and seen that not everything is
copied. But probably everything that isn't reconstructed at boot time
is copied, including the program you used to do the copy (I assume tar).
> thanks again!
>
> p.s., i deleted a bunch of stuff while using gnome. the trash apparently is
> in "/". the trash reported that i had no more space and started prompting me
> for each deletion, but after a few attempts, i realized that it was not
> going to permit any more trash. so i cancelled.
>
> then i logged out, tried to log back into kde. i couldn't. i restarted, and
> was told "not enough space in /tmp". x,lpd, mysql, xfs would not start,
> email died. everything died! my "/" was 100% filled! i tried to find out
> what was taking up all this space (almost 2gb free on "/" now missing) and
> could not find it (tried du many ways). finally, i found the hidden
> .gnome-desktop directory, found Trash.gmc, and found all the files that i
> was trying to delete. i tried to rm them, but "rm -r *" would not rm them! i
> had to mv them to another drive, reboot, and then in kde delete them again
> (not move them to trash).
>
> i'm not using gnome for file operations ever again!
I always delete with the "rm" command. I guess you're talking about
dragging things into a trash can icon? I've never tried that with linux,
but I'll bet putting files in the trash doesn't really eliminate them.
Instead, judging from what you said, the files are moved to /tmp until you
do whatever is needed with the mouse to empty the trash.
--
Steven Yellin
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
