> I just got the ZFS stuff working. I was just > confused on the device notation and the need to run > "/usr/sbin/disks" to get the device nodes created > after I added a new drive. > Perhaps I'm lazy, but a 'df -h' is usually all I need to see the disk labels.
> As far as the e1000g, in my case the ethernet chip is > embedded on the motherboard, and uses Intel's CSA > port on the 865G northbridge to avoid congesting the > PCI bus / ICH5 southbridge with network traffic. I > would expect that variation to be fairly common (i.e. > well tested) in higher end motherboards since CSA was > supposed to be a real win for gigabit ethernet, but > maybe I'm wrong. > > Perhaps I should try moving the SATA controller to a > different PCI slot just in case there is an IRQ issue > of some sort (gawd, sounds like the old ISA bus > days). > Perhaps...or just select the reset PCI configuration switch that is common in many BIOSes. > And my hostname *is* screwed up (i.e. assigned as > "unknown") due to an apparent expectation that the > DHCP server would be tell it what the hostname should > be, rather than having the hostname hardcoded. So my > /etc/hosts has this entry at the end: > > 192.168.1.120 unknown # Added by DHCP > > And my /etc/hostname.e1000g0 is empty. > It should be for DHCP. > The command-line installation process never prompted > me for a hostname, so maybe I just need to tweak one > file or so, but I haven't research how DHCP is > managed by Solaris yet. I should probably just > disable DHCP, since that probably isn't the best idea > for a NAS. > See Rich Teer's writeup on the DHCP hostname issue...a common problem for new Solaris users: http://www.rite-group.com/consulting/solaris_dhcp.html#unknown > Thanks again for your ideas, and any others that this > might spur. > > --Mark No problem Mark. Enjoy Solairs! This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list [email protected]
