Re: (solved) Re: new drive = new install?

* David A. <[EMAIL PROTECTED]> 2007-08-29 > > > What is common practice when migrating a system from one drive to > > > another. Should I reinstall from scratch or partition the new drive > > > and "copy everything" from the old one? > > > > Reinstallation is not necessary. There are plenty of HOWT

(solved) Re: new drive = new install?

> > What is common practice when migrating a system from one drive to > > another. Should I reinstall from scratch or partition the new drive > > and "copy everything" from the old one? > > Reinstallation is not necessary. There are plenty of HOWTOs available, > one being

Re: new drive = new install?

David A.: > > What is common practice when migrating a system from one drive to > another. Should I reinstall from scratch or partition the new drive > and "copy everything" from the old one? Reinstallation is not necessary. There are plenty of HOWTOs available, one being

Re: New drive, problems with old drive

On Thu, 2004-12-30 at 15:21 -0500, Scott Mohnkern wrote: > Critical info: > > Debian with 2.22 Kernel > I386 infrastructure > 2 120 GB hard drives Out of curiosity: why install Woody, when you could install Sarge? > > We were having problems with the old drive, to the point it was getting > m

Re: New drive ready to partition. Just what some recommendations and suggestions.

A long time ago, in a galaxy far, far way, someone said... > Hi, > > On Wed, 19 Jan, 2000 ? 10:17:54AM +1100, Peter Ross wrote: > > well. AFAIK the only directories that need to be on the / partition are > > /bin, /sbin, and /etc. > > > Are you sure you don't need /lib and /dev ? You're right;

Re: New drive ready to partition. Just what some recommendations and suggestions.

Hi, On Wed, 19 Jan, 2000 à 10:17:54AM +1100, Peter Ross wrote: > well. AFAIK the only directories that need to be on the / partition are > /bin, /sbin, and /etc. > Are you sure you don't need /lib and /dev ? -- ( >- Laurent PICOULEAU -< ) /~\ [EMA

Re: New drive ready to partition. Just what some recommendations and suggestions.

Hmmm, does incremental backups sound good in this situation? Anyone? Regards, Onno At 07:44 PM 1/18/00 +, John Gay wrote: > > >I've got some good suggestions, and apparently raised a few questions as well. >Let me outline my reasons for asking and what I hope to do: > >I've got a CD-RW. I pl

Re: New drive ready to partition. Just what some recommendations and suggestions.

On 18-Jan-2000, Ron Rademaker <[EMAIL PROTECTED]> wrote: > On Wed, 19 Jan 2000, Peter Ross wrote: > > > Currently I have two partitions. > > > > 1. / > > 2. /mnt/wally/hdc2 which contains my /usr/local and /home setup by using > >symlinks. > > > > The advantage for me, is that I can trash t

Re: New drive ready to partition. Just what some recommendations and suggestions.

another read of the FHS documents and a good think. aphro <[EMAIL PROTECTED]> on 18/01/2000 17:11:52 Sent by: aphro <[EMAIL PROTECTED]> To: Onno Ebbinge <[EMAIL PROTECTED]> cc: Ron Rademaker <[EMAIL PROTECTED]>, John Gay/IE/[EMAIL PROTECTED], debian-user@lists.

Re: New drive ready to partition. Just what some recommendations and suggestions.

i do stuff along those lines as well ..i dont understand when i installed freebsd it reccomended a 20MB /var partition/slice even though i gave it 6.1GB of space. it doesnt make sense to have such small partitions even if there is nothing on them to me anyways. nate On Tue, 18 Jan 2000, Onno Ebbi

Re: New drive ready to partition. Just what some recommendations and suggestions.

On Tue, Jan 18, 2000 at 02:01:07PM +0100, Onno Ebbinge wrote: > Sometimes I don't understand the stratagies used in disk partitioning. Me neither, why are we making things so complicated and inflexible? My partition scheme is as follows: 1.5 GB / Rest/vol/0 /home is a link to /vol/0/_home.

Re: New drive ready to partition. Just what some recommendations and suggestions.

On Wed, 19 Jan 2000, Peter Ross wrote: > Currently I have two partitions. > > 1. / > 2. /mnt/wally/hdc2 which contains my /usr/local and /home setup by using >symlinks. > > The advantage for me, is that I can trash the root partition any time I > want and still have all my important stuff.

Re: New drive ready to partition. Just what some recommendations and suggestions.

Currently I have two partitions. 1. / 2. /mnt/wally/hdc2 which contains my /usr/local and /home setup by using symlinks. The advantage for me, is that I can trash the root partition any time I want and still have all my important stuff. Pete

Re: New drive ready to partition. Just what some recommendations and suggestions.

Sometimes I don't understand the stratagies used in disk partitioning. Please correct me if I'm wrong but I always thought that you split the partitions by long term usage: 1- 2 GB / 1- 2 GB /var 1- 4 GB /var/spool rest on /home Then I link /tmp

Re: New drive ready to partition. Just what some recommendations and suggestions.

> I recently got a new 13G hard drive. I've installed it as hdb, and moved my > CD-RW to hdc. At the moment I've got a 6G drive with 2G for WindowsNT, 100M > for > /, 1G for /home and 2G for /usr. I really need more room for both /home AND > /usr, but I also need more space for /var and /opt and

Re: New drive

Stephan A Suerken wrote: > > Nils Rennebarth <[EMAIL PROTECTED]> writes: > > > You should not 'copy the partitions'. Don't know what ghost is, but I doubt > > it supports the ext2 filesystem. > > With GNU cp, copying whole partitions is ok via "cp -a", so tar > is not needed (if one can mount b

Re: New drive

Nils Rennebarth <[EMAIL PROTECTED]> writes: > You should not 'copy the partitions'. Don't know what ghost is, but I doubt > it supports the ext2 filesystem. With GNU cp, copying whole partitions is ok via "cp -a", so tar is not needed (if one can mount both partitions simultaneously). There i

Re: New drive

"Ghost" is a drive imaging software. What it does, it copies your disk or partition byte for byte, formatting it on-the-fly. It works with ext2 filesystem, the only limitation is that, compared to the other filesystems, it won't resize the image, meaning that you can't take a partition created

Re: New drive

On Wed, Jun 30, 1999 at 12:51:50PM +0200, Rudy Broersma wrote: > At the moment I have a 810 MB harddisk in my Linux box. I'm going to replace > it with a 12 GB Bigfoot. Can I just 'copy' the partitions? (Using ghost). Or > do I need to reinstall Linux (hate that. When I reinstall something I always

Re: New drive--->lilo warning

> Re-arrange your drives like this and let me know if it fixes the situation: > > HDA - ok > HDC - Set as HDB > HDB - Set as HDC (Linux does not care where additional partitions are) I did almost this, except instead of swapping hdb and hdc, I simply detached hdb temporarily. Low and behold it

Re: New drive--->lilo warning

Mark Phillips writes: [snip] > > Why have two "DOS" bootable drives? In my experience, "DOS" only likes to > > see > > one main bootable drive. [snip] One other item which I did not mention: The bootable "DOS" drive _must_ be the first one detectable by "DOS". > > This is the setup of my three

Re: New drive--->lilo warning

On Thu, Apr 16, 1998 at 11:01:34AM +0930, Mark Phillips wrote: > > > > I have just installed a third IDE hard drive (my board supports up > > > to 4). I have configured the BIOS. Now I want to use lilo to make it > > > possible to boot from it (it currently has DOS on it), but when I try, > > >

Re: New drive--->lilo warning

On Wed, 15 Apr 1998 [EMAIL PROTECTED] wrote: > Mark Phillips writes: > [snip] > > I tried booting anyway but it failed, complaining that it wasn't a system > > disk. However my Dad (whose disk it was before giving it to me) swears it > > was bootable. > > > > So what's wrong? On my father's com

Re: New drive--->lilo warning

Mark Phillips writes: [snip] > I tried booting anyway but it failed, complaining that it wasn't a system > disk. However my Dad (whose disk it was before giving it to me) swears it > was bootable. > > So what's wrong? On my father's computer the disk was disk C: where as > now it is /dev/hdc (th

Re: New drive--->lilo warning

> > I have just installed a third IDE hard drive (my board supports up > > to 4). I have configured the BIOS. Now I want to use lilo to make it > > possible to boot from it (it currently has DOS on it), but when I try, > > it comes up with: > > > > # lilo > > Added linux * > > Added dos > > ide

Re: New drive--->lilo warning

Mark Phillips writes: > > > Hi, > > I have just installed a third IDE hard drive (my board supports up to 4). > I have configured the BIOS. Now I want to use lilo to make it possible to > boot from it (it currently has DOS on it), but when I try, it comes up > with: > > # lilo > Added linux