Re: [OpenIndiana-discuss] Hi everyone
On Mon, Mar 19, 2012 at 23:50, Bayard Bell buffer.g.overf...@gmail.com wrote: Ooh, tasty. Please register kit that can be made accessible here: https://www.illumos.org/projects/illumos-gate/wiki/SPARC_resources Done. -- Venlig hilsen / Kind regards Jeppe Toustrup (aka. Tenzer) ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?
Reginald Beardsley wrote: 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 sound reasons for this hidden in the implementation details. fpool was mounted under /mnt, it just wasn't the portion of fpool I wanted to access. My observation of df over the past few years is that it doesn't quite grok zfs yet. I find myself using zfs list quite a bit. In any event, the confluence of comments got me to the solution. Which is what matters. None of that rings true to me, but if it's working for you, that's great. -- James Carlson 42.703N 71.076W carls...@workingcode.com ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Bump Nvidia driver to 295.20
Hello, Ref: ftp://download.nvidia.com/solaris/295.20/NVIDIA-Solaris-x86-295.20.run There was some thought into bumping the Nvidia video driver to 295.20 during the prestable releases. This helps many laptop users mainly when installing and using the OI distro. The current Nvidia video driver, 280.13, used in the oi_dev repo has no major bugs reported so the priority of this is low. Since it is the main video driver we use for desktop graphics, just consider it. ~ Ken Mays ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?
beadm is missing a qualifier on mount to specify the pool name under which the named BE is located, so it mounts the first BE it finds with the name you specify. Since you had the same BE name present in your existing root pool, that gets in the way. Your workaround removed the conflict and that's why it worked. Dave On 03/19/12 23:18, Reginald Beardsley wrote: 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 sound reasons for this hidden in the implementation details. fpool was mounted under /mnt, it just wasn't the portion of fpool I wanted to access. My observation of df over the past few years is that it doesn't quite grok zfs yet. I find myself using zfs list quite a bit. In any event, the confluence of comments got me to the solution. Which is what matters. So thanks again to all. Have Fun! Reg --- On Mon, 3/19/12, James Carlsoncarls...@workingcode.com wrote: From: James Carlsoncarls...@workingcode.com Subject: Re: [OpenIndiana-discuss] Access to /etc on a pool from another system? To: openindiana-discuss@openindiana.org Date: Monday, March 19, 2012, 8:15 PM 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 native rpool root file system, not the one in fpool. Now that I think about it, the problems seemed to revolve around the special way that zfs and beadm treat /. Other than being canmount=no, it's not too special.� Just look at the ZFS attributes; they tell you everything you might want to know. zfs get -o all all fpool/ROOT/opensolaris -- James Carlson� � � ���42.703N 71.076W� � � ���carls...@workingcode.com ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Access to /etc on a pool from another system?
--- On Tue, 3/20/12, Dave Miner dmi...@opensolaris.org wrote: From: Dave Miner dmi...@opensolaris.org Subject: Re: [OpenIndiana-discuss] Access to /etc on a pool from another system? To: openindiana-discuss@openindiana.org Date: Tuesday, March 20, 2012, 9:31 AM beadm is missing a qualifier on mount to specify the pool name under which the named BE is located, so it mounts the first BE it finds with the name you specify. Since you had the same BE name present in your existing root pool, that gets in the way. Your workaround removed the conflict and that's why it worked. Dave That's what I concluded, but glad to have the confirmation. Just wish there was a way to rename an unmounted pool so I could make it rpool again. At the moment it's not bootable, though I think I understand how to fix that. Since it's just a test image I doesn't matter if I fail or trash it so I plan to try. Ironically, the config file I was after was of no use. But I learned quite a bit about beadm zfs, so it was well worth while. At least if I can remember it all when I need it next. I'd rolled up facilities to provide the function of beadm on my 3/60 1+, but not as elegant. On the 3/60 I used the diag switch to select the active be and had miniroot installed in that. Full system be was lots more work to setup. Have Fun! Reg ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
