On Tue, Feb 26, 2008 at 7:22 AM, Uwe Dippel [EMAIL PROTECTED] wrote:
Thanks, Dave, for your confirmation of my intentions and assumptions, at
least in general:
1. The limitation in handling multiple Solaris fdisk partitions is a
function of the disk target driver. This is what I was
Uwe Dippel [EMAIL PROTECTED] wrote:
[i]I thought I read somewhere that the fdisk spec says that there can only
be one fdisk partition of a particular type, thus your experiment in
creating two Solaris2 fdisk partitions is invalid and that is perhaps
why Solaris does not behave correctly.[/i]
Joerg Schilling wrote:
Uwe Dippel [EMAIL PROTECTED] wrote:
[i]I thought I read somewhere that the fdisk spec says that there can only
be one fdisk partition of a particular type, thus your experiment in
creating two Solaris2 fdisk partitions is invalid and that is perhaps
why Solaris
Kyle McDonald [EMAIL PROTECTED] wrote:
I mentioned already:
- Multiboot is a term introduced by GRUB and unrelated to your problem
- Solaris x86 supports up to 16 slices in a primary fdisk partition.
14 of them are usable for your wishes. You don't get less partitions
Kyle McDonald wrote:
Joerg Schilling wrote:
Uwe Dippel [EMAIL PROTECTED] wrote:
[i]I thought I read somewhere that the fdisk spec says that there can only
be one fdisk partition of a particular type, thus your experiment in
creating two Solaris2 fdisk partitions is invalid and that is
Thanks, Dave, for your confirmation of my intentions and assumptions, at least
in general:
1. The limitation in handling multiple Solaris fdisk partitions is a
function of the disk target driver. This is what I was thinking: In order to
handle a slice, you pick it up using the disk target
Joseph Mocker [EMAIL PROTECTED] wrote:
I thought I read somewhere that the fdisk spec says that there can only
be one fdisk partition of a particular type, thus your experiment in
creating two Solaris2 fdisk partitions is invalid and that is perhaps
why Solaris does not behave correctly.
Joerg Schilling wrote:
Joseph Mocker [EMAIL PROTECTED] wrote:
I thought I read somewhere that the fdisk spec says that there can only
be one fdisk partition of a particular type, thus your experiment in
creating two Solaris2 fdisk partitions is invalid and that is perhaps
why Solaris
[i]I thought I read somewhere that the fdisk spec says that there can only
be one fdisk partition of a particular type, thus your experiment in
creating two Solaris2 fdisk partitions is invalid and that is perhaps
why Solaris does not behave correctly.[/i]
This might be so, but if you read my
After my positive (overwhelming) experience with SXDE 09/07 I tried Indiana
Preview 1.
Since it was not useable, I filed the bugs I found and wiped it. Now I receive
detail requests about those bugs, months later.
In a nutshell: with the current size of hard drives, why is Solaris still not
Uwe Dippel [EMAIL PROTECTED] wrote:
After my positive (overwhelming) experience with SXDE 09/07 I tried Indiana
Preview 1.
Since it was not useable, I filed the bugs I found and wiped it. Now I
receive detail requests about those bugs, months later.
In a nutshell: with the current size of
On Sat, Feb 23, 2008 at 2:08 PM, Joerg Schilling
[EMAIL PROTECTED] wrote:
Uwe Dippel [EMAIL PROTECTED] wrote:
After my positive (overwhelming) experience with SXDE 09/07 I tried
Indiana Preview 1.
Since it was not useable, I filed the bugs I found and wiped it. Now I
receive detail
I think you understand very well what I meant.
My mistake was the why is Solaris still not multiboot-compliant? Though it
might be, along to the lines of the standard, it can't live with another
partition containing another Solaris on the same drive. If I am wrong, correct
me, please.
I tried
Ignacio Marambio Catán [EMAIL PROTECTED] wrote:
After my positive (overwhelming) experience with SXDE 09/07 I tried
Indiana Preview 1.
Since it was not useable, I filed the bugs I found and wiped it. Now I
receive detail requests about those bugs, months later.
In a nutshell:
You should submit a RFE, I believe the installer only assumes one Solaris2
fdisk partition
Other wise use lucreate/luupgrade to manage the slices first bootup disk Slice
0 is root BE, Slice 1 is defined as swap (default install uses s1 as swap)
Slice 3 can be your second ABE, or your second
On Sat, Feb 23, 2008 at 9:21 AM, Uwe Dippel [EMAIL PROTECTED] wrote:
After my positive (overwhelming) experience with SXDE 09/07 I tried Indiana
Preview 1.
Since it was not useable, I filed the bugs I found and wiped it. Now I
receive detail requests about those bugs, months later.
In a
jabrewer, thanks.
In my original post I talked about installing another Solaris, not an upgrade.
Like Indiana, Sol10, you name it.
A current default layout offers one free slice, second_root. That might not be
enough for all.
I might not want to share /export/home.
One could say: Back to the
On Sat, Feb 23, 2008 at 7:07 PM, Uwe Dippel [EMAIL PROTECTED] wrote:
jabrewer, thanks.
In my original post I talked about installing another Solaris, not an
upgrade. Like Indiana, Sol10, you name it.
A current default layout offers one free slice, second_root. That might not
be enough for
[i]I believe the installer only assumes one Solaris2 fdisk partition[/i]
If it was like this, the matter might be more difficult. But it isn't. fdisk
another bf to your drive, and the new installer is absolutely happy at
installing in there. At reboot, grub is absolutely happy at loading the
Uwe Dippel wrote:
[i]I believe the installer only assumes one Solaris2 fdisk partition[/i]
[snip]
I did try this before, and it worked pretty well, except that it required a
very hackish way at boot:
Partition Status Type Start End Length %
= == = === ==
20 matches
Mail list logo
