Re: same debian, new hardware?
Quoting Krzys Majewski ([EMAIL PROTECTED]): 3) Make binary images of the old hard drives, automagically paste these onto the new hard drive. Unfortunately I'm pretty sure this is impossible. You mention SCSI in the old box, but don't say what's the hardware in the new box. If IDE, you could install the new disk in the old machine, partition it (think about that, of course), mount it on /mnt and copy the files onto it with cd old-directory-root find -xdev | cpio -damp /mnt Then create a boot floppy, rdev the kernel to the future correct device, put the new disk in the new machine, boot it with the floppy and run lilo. OK, that sounds good. I think my new drive will be IDE, but why does it matter? I was under the impression that the whole point of SCSI was to allow easy addition of devices...the old machine was sort of a hand-me-down, I didn't buy the scsi controller, which is my excuse for not knowing a whole lot about how it works.. Yes. SCSI does allow for easy connection of devices. But it takes a little more care when setting up the booting strategy because the PC BIOS was designed long before SCSI disks were used in PCs, or even having four IDE drives. By the way, I don't suppose a similar procedure will work for moving the Windows partition, or does anyone know? I think not. There are people who clone disks with *precisely* the same hardware (in the same slots etc.). I've not even managed it with functionally the same hardware. 4) Physically install the old hard drives in the new machine. Make a boot floppy, move the drives, boot with the floppy, copy in the same way as above, rdev the floppy (or a copy), boot again, this time into the new drive, run lilo. OK this sounds just like the previous step, except putting the old drives in the new machine rather than putting the new drive in the old machine, copying, and then putting it back in the new machine, am I right? Yes. But the old machine may (or may not; I can't remember the size) handle a new IDE drive, whereas the new machine won't, I assume, contain a SCSI card. OK, moving that may be straightforward. OTOH it may produce a resource conflict if the new machine is well endowed. I can't predict. On the subject of drives, is my existing scsi setup a valuable thing to have or should should I just dump the whole thing in the lane and never look back? Someone told me scsi is faster than non-scsi, can I capitalize on this somehow? It all depends. IDE has become very fast, but the latest variants require good cabling to perform to spec. SCSI has always been a bit of a pain with cabling and termination, but it's great for adding external drives like jaz, CD-RW, etc. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: same debian, new hardware?
Krzys Majewski wrote: Again on the subject of buying new hardware, I'm looking for a good way to copy my existing setup to the new machine. So far I can think of three main types of options. In order of decreasing popularity, they are: first three snipped 4) Physically install the old hard drives in the new machine. I recently went from a Pentium 166 to a PII 300, and the route I took was number 4. My hard drives are both IDE, but I do have a SCSI CDROM drive. Everything went just fine. I did later recompile the kernel for the PII, but I doubt it was really necessary. However, in the process of recompiling the kernel I redid some of the other peripherals to get them working better, or in the case of the sound card to get it working at all. -- Mike Werner KA8YSD | He that is slow to believe anything and | everything is of great understanding, '91 GS500E| for belief in one false principle is the Morgantown WV | beginning of all unwisdom.
Re: same debian, new hardware?
On Thu, Jul 27, 2000 at 06:03:41PM -0700, Krzys Majewski wrote: 4) Physically install the old hard drives in the new machine. 4) This would be nice, but can it be done? My hard drives are old and small. Sure. Also they are sitting on a SCSI card, is this a good thing or a bad thing? The SCSI card is probably ISA, can I stick it in a new machine and hope it will work? If someone can suggest how to make this work then I would It should. The main thing I can think of that would stop it would be resource conflicts, but you should be able to reconfigure to avoid them. An approach you didn't mention would be to keep both machines running and network them then copy and share things over the network. I know this is a linux forum, but I'm also interested in moving Windows to the new machine. Presumably this means I have to reinstall it? That's probably easiest and safest thing to do. -- Mark Brown mailto:[EMAIL PROTECTED] (Trying to avoid grumpiness) http://www.tardis.ed.ac.uk/~broonie/ EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/ pgpfDzkDsa9LQ.pgp Description: PGP signature
Re: same debian, new hardware?
Quoting Krzys Majewski ([EMAIL PROTECTED]): Again on the subject of buying new hardware, I'm looking for a good way to copy my existing setup to the new machine. So far I can think of three main types of options. In order of decreasing popularity, they are: 1) Reinstall everything from scratch, then copy my home directory and some conf files from the old machine to the new machine. Not a bad idea if, say, you're still on slink and are moving to potato. 3) Make binary images of the old hard drives, automagically paste these onto the new hard drive. Unfortunately I'm pretty sure this is impossible. You mention SCSI in the old box, but don't say what's the hardware in the new box. If IDE, you could install the new disk in the old machine, partition it (think about that, of course), mount it on /mnt and copy the files onto it with cd old-directory-root find -xdev | cpio -damp /mnt Then create a boot floppy, rdev the kernel to the future correct device, put the new disk in the new machine, boot it with the floppy and run lilo. 4) Physically install the old hard drives in the new machine. Make a boot floppy, move the drives, boot with the floppy, copy in the same way as above, rdev the floppy (or a copy), boot again, this time into the new drive, run lilo. Note that the rdev'ing is no longer necessary with potato because it produces a syslinux boot floppy instead of a kernel image. Therefore you can give it parameters like root=/dev/hda1 single which was not possible before. (Of course, with slink and previous, one could copy the kernel onto a rescue disk to get the same effect.) Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: same debian, new hardware?
3) Make binary images of the old hard drives, automagically paste these onto the new hard drive. Unfortunately I'm pretty sure this is impossible. You mention SCSI in the old box, but don't say what's the hardware in the new box. If IDE, you could install the new disk in the old machine, partition it (think about that, of course), mount it on /mnt and copy the files onto it with cd old-directory-root find -xdev | cpio -damp /mnt Then create a boot floppy, rdev the kernel to the future correct device, put the new disk in the new machine, boot it with the floppy and run lilo. OK, that sounds good. I think my new drive will be IDE, but why does it matter? I was under the impression that the whole point of SCSI was to allow easy addition of devices...the old machine was sort of a hand-me-down, I didn't buy the scsi controller, which is my excuse for not knowing a whole lot about how it works.. By the way, I don't suppose a similar procedure will work for moving the Windows partition, or does anyone know? 4) Physically install the old hard drives in the new machine. Make a boot floppy, move the drives, boot with the floppy, copy in the same way as above, rdev the floppy (or a copy), boot again, this time into the new drive, run lilo. OK this sounds just like the previous step, except putting the old drives in the new machine rather than putting the new drive in the old machine, copying, and then putting it back in the new machine, am I right? On the subject of drives, is my existing scsi setup a valuable thing to have or should should I just dump the whole thing in the lane and never look back? Someone told me scsi is faster than non-scsi, can I capitalize on this somehow? Thanks for all the responses, this is great -chris
same debian, new hardware?
Again on the subject of buying new hardware, I'm looking for a good way to copy my existing setup to the new machine. So far I can think of three main types of options. In order of decreasing popularity, they are: 1) Reinstall everything from scratch, then copy my home directory and some conf files from the old machine to the new machine. 2) Install a minimal system on the new machine, then copy everything from the old machine to the new machine. 3) Make binary images of the old hard drives, automagically paste these onto the new hard drive. Unfortunately I'm pretty sure this is impossible. 4) Physically install the old hard drives in the new machine. Here are my comments on these: 1) This strikes me as completely wasted. Also difficult because I'll have a home dir and an /etc on the new machine, so I'll have to think carefully about which files from the old machine should overwrite the new files, which files shouldn't be copied, blah blah. The main reason I would like to avoid this is because I like my software, it's the hardware I want to upgrade. 2) I've done this once before, it works with linux fairly well. I just copy everything, but I ask cp to prompt me if the file already exists on the new machine. Unfortunately I don't know if I can do this with Windows. I suspect I can't, and it is nice to have Windows around for various reasons. 3) This is what I want, but as described it can't be done, since different drives have different geometries and so on. However, I know that it is possible to make a fairly generic kernel that will run on different machines (viz. root/boot floppies), so the linux itself should be portable at least for the first little bit until I recompile the kernel. 4) This would be nice, but can it be done? My hard drives are old and small. Also they are sitting on a SCSI card, is this a good thing or a bad thing? The SCSI card is probably ISA, can I stick it in a new machine and hope it will work? If someone can suggest how to make this work then I would gradually migrate stuff to the new big hard drive on the new fast expensive machine. I know this is a linux forum, but I'm also interested in moving Windows to the new machine. Presumably this means I have to reinstall it? Can I do some variation of item #2) on my windows partition? I'd be grateful for any comments or stories you may have, chris
Re: same debian, new hardware?
[snip] I have once done a move to completely new hardware(486-Pentium). The only thing I found necessary to do is recompile kernel. All the binaries ran perfect after I recompiled kernel. But I took an old drive and put it into new machine. I guess you would need to install a minimal system, and put your drives into new system and copy stuff off them. It should work just fine. Andrei First there was Explorer. Then came Expedition. This summer coming to a street near you.. Ford Exterminator. - Andrei S. Ivanov [EMAIL PROTECTED] http://arshes.dyndns.org UIN 12402354 For GPG key, go to above URL/GnuPG -
