[Way OT] dieresis

Platinium? Lanthanium? Molybdenium? Tantalium?

Tim

Aluminium was the third spelling, while the second was Aluminum.

Pardon me, New Yorker always adds dieresis (pre:existing, co:operate, etc). I assume it's the New Yorker style guide, because the authors who also publish elsewhere do not show this in their other work (e.g. Malcolm Gladwell).

Now if y'all could just move this to alt.anal-retentive, the newsgroup would be good again.

cp -R * won't transfer the boot sector, partition table, etc.

Just use "dd if=/dev/hda of=/dev/hdc" with the target drive on the second IDE. Then go to bed. It'll be finished in the morning :-)

Don't do it with mounted drives. Boot with a startup floppy or CD with a copy of dd and parted on it. Don't worry about BIOS settings. Linux doesn't use them for I/O. I've actually run a 40 gig HDD on a machine with an 8 gig BIOS limit, (with a 1024 cylinder boot partition to fool it).

You'll find all your original partitions recreated on your new drive, with empty space left if it's bigger. It'll boot, too.

Then use parted to stretch the created partition to the size of the new (bigger) HDD. Go for breakfast whilst that's running.

Thanks for the offer of the monitors. I have quite a few spare already.

bs= is often a worthwhile speedup.

Clonezilla is your friend.

the

My typical usage is to partition the new disk the way i want and copy the= =20 source tree to target partition the way i want it to be.

second

And the sizes of the new partitions mirror the old ones. I don't seem to= =20 have come across a version of parted that will just do as i ask, instead=20 of second guessing me.

=46er instance; stretch the extended partition to the end of the disk, = move=20 the internal partitions to the end, move the beginning of the extended=20 partition, modify existing primary partitions. Most bitch about the = first=20 change and only one so far did the second. All versions i have tried = refused=20 to do the third task. Rather non-*nix like i say.

Always. After making backups. I have 2 or 3 largish unused hard disks = handy.

with

with

Yep, i have done that, once. Still creeps me a bit.

That is where parted usually tells me NO.

Oh well, I just hate to trash good working stuff though.

I've never used extended partitions. Four primary to a drive is enough for me. In fact three primary partitions are all I have, now: boot - swap - root, with the boot partition (/dev/hda1) mounted on /boot in /etc/fstab at startup.

I've never had any trouble with parted not doing what I wanted. I'll dig the manual out and refresh my memory on what it will/won't do. My version is old (1.6.3)

I don't run Linux so keep that in mind...

Can't you (or, *don't* you?) build slices *within* a "partition"? E.g., I can set up an x86 PC to use one of the (4) partitions for DOS, another for some variant of Windows a third for NetBSD 3.1 and the fourth for NetBSD 5.0.

DOS and Windows are happy -- since they deal with "partitions".

Within each of the NetBSD partitions, I create many (4, 8, 10?) "slices" (think: partition : disk :: slice : partition) and each of those is (potentially) a filesystem mounted someplace in the (NetBSD) hierarchy.

E.g., /, /var, /usr, /usr/local, /usr/pkg, /home ...

I don't run DOS or Windows. Strictly Microsoft-free zone here. Just Linux.

I don't know anything about NetBSD filesystems. Linux fdisk will make NetBSD partitions, but I don't know whether there's an mkfs for NetBSD.

I used to have /usr and /home on a separate physical drive, once, when all I had were smallish drives. I can't see any point in having lots of separate partitions otherwise. My boot partition is a relic of the days of BIOS that would only boot from the first 1024 cylinders.