Date: Thu, 24 Jan 2002 04:02:38 +0100 From: Cliff Sarginson <cliff@raggedclown.net> To: FreeBSD List <freebsd-questions@FreeBSD.ORG> Subject: Re: Reversing Linux and FreeBSD running on same system without mutual self-destruction Message-ID: <20020124030238.GA1042@raggedclown.net> In-Reply-To: <ogr8oga800.8og@localhost.localdomain> References: <20020123051538.GA3234@raggedclown.net> <ogr8oga800.8og@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 23, 2002 at 04:49:03PM -0800, Gary W. Swearingen wrote: > Cliff Sarginson <cliff@raggedclown.net> writes: > > > Here is a challenge. > > You provided a lot of info, but maybe not enough. I'm not promising any > great ideas, but I was wishing you'd have given approximate disk/ > partition sizes at least. Amount of unused space for tmp xfr. How many > CDs you consider reasonable to write and verify. > Yes, I was not really wanting to burden anyone with the mathematics of it :). > I couldn't get reliable mounts of Linux from FreeBSD and vice versa, so This is the bummer, me neither. > I tar'd directly into a raw FreeBSD partition from Linux and then from > FreeBSD, untar'd it. I know that doesn't address some of your problems. > > You might best use a scheme which involves putting everything on CD so > that you get a free backup in the process. If you've got room, do > "dump ... | gzip | split ..." on your partitions and burn them. You'd > need a big space to unsplit them to before "zcat ... | restore ...". > > (I wish I knew how to make a pipe work like a tape drive with > end-of-file thingy so you could treat CDs like tapes with dump and > restore, and embed a gzip. It should be doable. It probably should > even be possible to make it work like a disk drive with 650 MB blocks.) > I have looked at the problem again, and it boils down to this now. I can move the whole of the Linux stuff, with a bit of tidying up, and some fairly careful fiddling with configurations, from it's current location on the SCSI disk to various places on the AT ones. I can do that without having to touch the FreeBSD stuff..so that is cool. So that will solve that problem, I then have a SCSI disk with only a boot partition .. very small..that I will keep anyway, I get on better with Lilo than with the FreeBSD boot manager, and I am very familiar with it. So I then have a SCSI disk which I can repartition/slice (I am still not used to slices, everytime I use the word I start thinking about cakes) how I like apart from the first one on the disk. Having done that I guess I can boot the existing BSD system single user and tar over the existing AT BSD file systems to the SCSI one. I can adjust Lilo to reflect the new boot possibilities, I can adjust fstab for the SCSI BSD..with me so far ? Now this is where I reach the edge of the desert. I need then a kernel on the SCSI BSD system that will boot it. And this is where I need some expert advice, will the installation of a generic kernel from the existing AT system onto the root of the new SCSI FreeBSD system work ? What are the gotcha's in this scenario ? Apart from the possible devastation of a typing mistake (I just found quite a novel one in the existing installation, which strangely has never had a bad effect..but that is a mere detail :) Thanks for giving it some thought for me :) -- Regards Cliff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020124030238.GA1042>