Re: [OpenIndiana-discuss] Virtualbox on OpenIndiana

2012-03-19 Thread Gary
On Sun, Mar 18, 2012 at 10:34 PM, Geoff Nordli wrote: I noticed some comments from Bayard on the list about how vbox was completely unusable for development. Are there other people having success using it on servers or have I just been lucky? This is entirely an assumption on my part but I

Re: [OpenIndiana-discuss] Virtualbox on OpenIndiana

2012-03-19 Thread Sašo Kiselkov
On 03/19/2012 06:34 AM, Geoff Nordli wrote: I have been using vbox 4.1.x on OI 151 for about 5 months now running some server-based VMs with good success. I noticed some comments from Bayard on the list about how vbox was completely unusable for development. Are there other people having

[OpenIndiana-discuss] Spontaneous server reboots

2012-03-19 Thread Martyn Klassen
I have an OI server running oi_151a2 that is experiencing random reboots. I cannot seem to find any indication of why they are occurring in any of the logs, and there are no core dumps even though I have core dumps enabled. # coreadm global core file pattern: /var/cores/cor.%f.%p

Re: [OpenIndiana-discuss] Spontaneous server reboots

2012-03-19 Thread James Carlson
Martyn Klassen wrote: I have an OI server running oi_151a2 that is experiencing random reboots. I cannot seem to find any indication of why they are occurring in any of the logs, and there are no core dumps even though I have core dumps enabled. # coreadm Core dumps are related to faults

Re: [OpenIndiana-discuss] Virtualbox on OpenIndiana

2012-03-19 Thread Jan Owoc
On Sun, Mar 18, 2012 at 11:34 PM, Geoff Nordli geo...@gnaa.net wrote: I have been using vbox 4.1.x on OI 151 for about 5 months now running some server-based VMs with good success. I noticed some comments from Bayard on the list about how vbox was completely unusable for development.

[OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread Reginald Beardsley
I'm trying to access the /etc files from another system on which I installed OI 148. I can import the pool as fpool and can access /mnt/fpool /mnt/export. But for the life of me I can't figure out how to get to the /etc filesystem in fpool. All the examples google turns up point to things I

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread Jeppe Toustrup
On Mon, Mar 19, 2012 at 17:45, Reginald Beardsley pulask...@yahoo.com wrote: I'm trying to access the /etc files from another system on which I installed OI 148.  I can import the pool as fpool and can access /mnt/fpool /mnt/export. But for the life of me I can't figure out how to get to

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread James Carlson
Reginald Beardsley wrote: I'm trying to access the /etc files from another system on which I installed OI 148. I can import the pool as fpool and can access /mnt/fpool /mnt/export. But for the life of me I can't figure out how to get to the /etc filesystem in fpool. All the examples

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread Steve Gonczi
I am reading you mail as I connect the disk array from a dismantled OI 148 system to another computer and... /etc is typically on your root pool (ie. rpool). Note that the rpool is often on a different device, perhaps a flash drive. You may, or may not have connected this to the new

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread Reginald Beardsley
This is in response to all. rhb@openindiana:~# zfs list -r fpool NAME USED AVAIL REFER MOUNTPOINT fpool 6.97G 105G45K /mnt/fpool fpool/ROOT 3.72G 105G31K legacy fpool/ROOT/openindiana 3.72G 105G 3.60G /mnt fpool/dump

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread Reginald Beardsley
A bit more info following up on beadm. rhb@openindiana:~# beadm list -a BE/Dataset/Snapshot Active Mountpoint Space Policy Created oi_151 rpool/ROOT/oi_151 NR / 11.2 static 2011-12-06 23:40 rpool/ROOT/oi_151@0 -

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread James Carlson
Reginald Beardsley wrote: This is in response to all. rhb@openindiana:~# zfs list -r fpool NAME USED AVAIL REFER MOUNTPOINT fpool 6.97G 105G45K /mnt/fpool fpool/ROOT 3.72G 105G31K legacy fpool/ROOT/openindiana 3.72G

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread Reginald Beardsley
I would expect /mnt to contain /mnt/etc also. rhb@openindiana:~# df /mnt / (rpool/ROOT/oi_151 ):360070851 blocks 360070851 files rhb@openindiana:~# There's nothing particularly odd about the /mnt/fpool. This is the zfs list entry for /rpool rpool

Re: [OpenIndiana-discuss] Hi everyone

2012-03-19 Thread Bayard Bell
Ooh, tasty. Please register kit that can be made accessible here: https://www.illumos.org/projects/illumos-gate/wiki/SPARC_resources On Sun, Mar 18, 2012 at 11:05 AM, Jeppe Toustrup openindi...@tenzer.dk wrote: On Sat, Mar 17, 2012 at 14:09, Bayard Bell buffer.g.overf...@gmail.com wrote:

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread Reginald Beardsley
beadm proved to be the key to the puzzle. I got the root filesystem from the disk mounted. However, because of the convoluted process, I want to repeat the process before I write up an explanation. The thing that *appeared* to solve the problem was to rename the openindiana BE on rpool to

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread James Carlson
On 03/19/12 17:16, Reginald Beardsley wrote: I would expect /mnt to contain /mnt/etc also. rhb@openindiana:~# df /mnt / (rpool/ROOT/oi_151 ):360070851 blocks 360070851 files rhb@openindiana:~# Well, there's your problem. /mnt isn't mounted. All you're looking at is your

Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?

2012-03-19 Thread Reginald Beardsley
Well, not quite. Look at my more recent post. I'm not yet 100% sure of the details, but it revolves around how zfs be interact. And most likely the namespace collision between rpool fpool. However, you can see manipulate things w/ beadm that you can't access w/ zfs. There are doubtless