Kevin Monceaux wrote:
> Indiana Fans,
>
> On Mon, 14 Jul 2008, Dave Miner wrote:
>
>   
>> At this point, you'd have to do manual hacking because that's not a 
>> scenario the installer is designed to support.  The basic idea to work 
>> around it would be to install to some other disk, such as a USB drive, 
>> set up the disk the way you want it, mirror the root pool to the desired 
>> location, and do an installgrub to make it bootable.
>>     
>
> I think I've discovered a simpler solution.  Someone somewhere in this 
> thread said I should use slices to create zpools.  Well, by ignoring that 
> advice I've just achieved my goal while working around the Indiana 
> installer's limitations without too much trouble.
>
> My Goal - I have two harddrives in my desktop box.  I wanted to use part 
> of the space on my first harddrive for my root pool, and use the remainder 
> of the space on that drive and all of the space on the second drive to 
> create a non-root pool.  At the moment, my disks are known as c6d0 and 
> c6d1.  On some installs, they've been known as c5d0 and c5d1.  So, here's 
> what I did:
>
> 1.  I fired up the installer and chose to partition my first disk.
>      What's a good size for a root pool?  I erred on the side of caution
>      and probably created a much larger pool than I needed.  I told the
>      installer to create a 25GB Solaris partition, and left the remainder
>      of the drive's space unallocated.
>
> 2.  After installing, I used format to create a second partition on my
>      first harddrive of type other.
>
> 3.  I created my non-root pool with:
>
>      # pfexec zpool create sys1 c6d0p2 c6d1
>
>      I'm from the IBM mainframe world.  If the installed had let me choose
>      the name of my root pool I would have named it sys1 and named my
>      non-root pool sys2.
>
> 4.  I moved /export/home to my new non-root pool and created a few other
>      filesystems such as /pub, /priv, etc.
>
> Tada!!!!!  I now have a layout that makes good use of all my available 
> drive space.
>
>
> Kevin
> http://www.RawFedDogs.net
> http://www.WacoAgilityGroup.org
> Bruceville, TX
>
> Si hoc legere scis nimium eruditionis habes.
> Longum iter est per praecepta, breve et efficax per exempla!!!
>
> _______________________________________________
> indiana-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>   
For indiana this will be a dealbreaker to some since one of its primary 
features is having the WHOLE system backed up through automatic 
snapshots, but I suppose this is a reasonable workaround.  For the 
majority of purposes this will suffice but it'd be better for the Caiman 
team to make it more transparent and work without forcing you to do 
something that makes less sense.  I'll give Indiana another spin on my 
desktop when they actually respin the media, I've already wasted a fair 
amount of time with the original update bug, but they say you can pretty 
easily get the system to B91+ now.  Too much time wasted to have to wait 
more to download more, when I can have a working system, download what I 
need while I work and upgrade the bits that I see fit to be updated.

James
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to