Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 May 2002 23:44:51 -0700
From:      rob <rob@pythonemproject.com>
To:        freebsd-stable@FreeBSD.ORG
Cc:        freebsd-stable@FreeBSD.ORG
Subject:   Re: Can Sysinstall now deal with 2 FBSD partitions?
Message-ID:  <3CE749E2.5AD3128F@pythonemproject.com>
References:  <200205172323.TAA68809@mmm1902.dulles19-verio.com> <20020518191332.K1494@shell.gsinet.sittig.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the info.  I have just about given up installing current.  I
got one of the bi-weekly iso images and it panics on my Viao.  The
developer release iso won't recognize my CDROM.

If I get a chance I will look at the sysinstall code.  It seems that
something very simple is severely lacking in its functionality.  Maybe I
can be the hero and patch it.  But I have other pressing coding
projects, so I can't guarantee anything.  Rob.


Gerhard Sittig wrote:
> 
> On Fri, May 17, 2002 at 23:23 +0000, rob@pythonemproject.com wrote:
> >
> > First slice on the drive is Win2K. My first FBSD slice has ad0s2a /, ad0s2b swap, ad0s2d /var ad0s2e /tmp ad0s2f /home and ad0s2g /usr  (I'm doing this from memory since I'm at work)
> >
> > In sysinstall, I created a new slice and made the exact same partitions, only they were ad0s3*.  I assigned all the mount points.  I left the original ad0s2 mount points as "*".  Then I used the developer release CD as the installation medium.
> >
> > And to my surprise, when I booted up, I had -current on ad0s2, and ad0s3 did not exist.
> 
> Since I have a similar setup (along the lines of: ad0s2
> -RELEASE /, ad0s3 -STABLE /, ad0s4 swap + -RELEASE /tmp +
> -RELEASE /var + -RELEASE /usr + -STABLE /tmp + -STABLE /var +
> -STABLE /usr + common /home) I ran into a similar problem.
> IIRC sysinstall already stopped me in creating or mounting
> another root partition if there already was one.
> 
> Should sysinstall still lack support for this setup (I didn't
> check back since then), you can circumvent the problem by
> changing the (BIOS) partition tag or the (BSD) partition name
> of the existing installation's root partition when installing
> the second system and restoring its name afterwards.  Later on
> booting one of two ad?s?a partitions hasn't been a problem.
> 
> See the archives, the question has been asked before.  From my
> sent folder I got these handles to my message, so you should
> be able to find the thread.
> 
>   Date: Sun, 11 Nov 2001 20:10:07 +0100
>   From: Gerhard Sittig <Gerhard.Sittig@gmx.net>
>   To: freebsd-mobile@FreeBSD.ORG
>   Subject: Re: Two FreeBSDs on same disk, booting secondary slice?
>   Message-ID: <20011111201007.F39804@shell.gsinet.sittig.org>
> 
> virtually yours   82D1 9B9C 01DC 4FB4 D7B4  61BE 3F49 4F77 72DE DA76
> Gerhard Sittig   true | mail -s "get gpg key" Gerhard.Sittig@gmx.net
> --
>      If you don't understand or are scared by any of the above
>              ask your parents or an adult to help you.
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

-- 
-----------------------------
The Numeric Python EM Project

www.pythonemproject.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CE749E2.5AD3128F>