[OpenIndiana-discuss] Hipster 2020.10 text installer ISO Wow!!!!

[Toomas Soome]

> On 3. Mar 2021, at 18:13, Reginald Beardsley via openindiana-discuss <openindiana-discuss at openindiana.org> wrote:
> 
> Categorically does *not* work on my 4 slot Z400. It kernel panics before it reaches the single user milestone using the device specified in the prtconf -v output from my system. With the"2822" device Gary specified the boot fails. So it is not as simple as has been presented.
> 

it Iis a bit more complicated, I’m afraid. I guess, if you boot -k, you will see it will complain about being unable to mount rootfs. *if* that is the case, you would need to boot from cd/usb, use update_drv to bind ahci driver, then import rpool, beadm mount your be and use devfsadm -r and bootadm update-archive -R



> BTW I've consistently been unable to login to single user mode on the GUI disk. It does not accept jack/jack, root/root or root/<null>. Is there something it *does* accept? In any case this should be fixed. It provides no security at all. At milestone all "sudo /bin/su" provides full control.
> 
> Whoever decided that the root password entered at install time should be expired on first login should be hung by their thumbs. That is *very* annoying.

root/openindiana



> 
> But not using all of a 5 TB disk in the GUI "full disk" install is simply brain dead. If a new user sees that they are not going to be favorably impressed. Even if the "new user" has the chops to fix it via the other, "not the same as the other" text installer.
> 

MBR partitioning only does allow to address up to 2TB disks. Please use GPT/EFI partitioning instead.

https://www.howtogeek.com/193669/whats-the-difference-between-gpt-and-mbr-when-partitioning-a-drive/

rgds,
toomas

> Reg
>     On Wednesday, March 3, 2021, 07:59:09 AM CST, Gary Mills <gary_mills at fastmail.fm> wrote:  
> 
> On Tue, Mar 02, 2021 at 08:40:51PM -0800, Joshua M. Clulow via openindiana-discuss wrote:
>> 
>> If ahci(7D) does indeed support this controller, and it's just that
>> the association with the specific PCI ID is missing, that's incredibly
>> easy to fix in illumos and then nobody needs to do the manual
>> update_drv dance ever again.  At present, it's just attaching to the
>> AHCI 1.0 PCI device class, 01:06:01:
>> 
>>     http://src.illumos.org/source/xref/illumos-gate/usr/src/pkg/manifests/driver-storage-ahci.mf?r=fd6d41c5#46-47
> 
> The only permanent change to OI on my Z400 is this addition to
> /etc/driver_aliases:
> 
>     ahci "pci8086,2822.103c.1309.0"
> 
> I've since done many OS upgrades to the system, but never needed
> to make that change again.  Mostly, I forgot that I had done it.
> 
>> But if we need to bind it to more specific devices that do not
>> advertise the class, it would just mean more aliases in the package
>> manifest.  It'd help to collect the data from prtconf and file a bug
>> report to start with, and then making the actual change is not likely
>> to be a great deal more work after that.
>> 
>> It's always best to file and fix the underlying bug where we can,
>> rather than propagate workarounds like this.
> 
> I looked around for my notes on the first install of OI on my Z400,
> but couldn't find anything.  Maybe it was that easy that I didn't
> bother making notes.  I do recall that only needed to follow the first
> part of the instructions.  The main thing is the add_drv and rebuilding
> the boot archive.  There was only one BE, of course.
> 
> 
> -- 
> -Gary Mills-        -refurb-        -Winnipeg, Manitoba, Canada-
> 
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss