In That case OI will use its defaults.
OI Mounts per default as nfs4 so if you didnt specify -o vers=3 the shares got
mounted as nfs4.
Have a look at the output of the command mount in OI when the home is
automounted and when the home is mounted manually.
mount shows you the options the nfscli
On 02/18/2015 21:31, Aurélien Larcher wrote:
Maybe worth documenting on a Wiki page ("Hipster 2015 upgrade notes" ?)
if/when people upgrade to Hipster 2015 ?
Best regards
Of course. For now added to changelog
--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal Univers
Maybe worth documenting on a Wiki page ("Hipster 2015 upgrade notes" ?)
if/when people upgrade to Hipster 2015 ?
Best regards
Aurelien
On Wed, Feb 18, 2015 at 6:44 PM, Jim Klimov wrote:
>
> And FYI and FWIW, upgrading the guest additions (as well as the host) to
> 4.3.22 did help, I have a GUI
shame I'm bare-metal on this laptop then :(
On 18 February 2015 at 17:44, Jim Klimov wrote:
>
> And FYI and FWIW, upgrading the guest additions (as well as the host) to
> 4.3.22 did help, I have a GUI in updated Hipster again ;)
>
>
>
>
> And just to tease Nikola ;) here is a screenshot of the
And FYI and FWIW, upgrading the guest additions (as well as the host) to
4.3.22 did help, I have a GUI in updated Hipster again ;)
And just to tease Nikola ;) here is a screenshot of the update script for the
split-roots in action (verifying that indeed there are no newer updates, in
this
Like others, I've updated Hipster on my notebook where it runs as a VM under
VirtualBox, and lost GUI ;)
Currently, I believe the issue boils down to this end of the XOrg log:
[ 69670.527] (II) LoadModule: "vboxvideo"
[ 69670.528] (II) Loading /usr/lib/xorg/modules/drivers/amd64/vboxvide
ignore me, being thick.
oi-27 has updated to the latest incorporation.
On 18 February 2015 at 16:03, Jonathan Adams wrote:
> root@jadlaptop:~# pkg list -af | grep xorg-video-intel
> x11/server/xorg/driver/xorg-video-intel (openindiana.org)
> 2.99.917-2015.0.0.0---
> x11/server/xorg/driv
root@jadlaptop:~# pkg list -af | grep xorg-video-intel
x11/server/xorg/driver/xorg-video-intel (openindiana.org)
2.99.917-2015.0.0.0---
x11/server/xorg/driver/xorg-video-intel (openindiana.org)
2.18.0-2015.0.0.0 ---
x11/server/xorg/driver/xorg-video-intel (openindiana.org)
2.18.0-2
On 02/18/2015 18:30, Jonathan Adams wrote:
I was booted into oihipster-26 ...
I ran a "Xorg -configure" on oi-26, added the following options:
Option "DRI" "on"
Option "AccelMethod" "uxa"
and it killed graphical display in oihipster-26
[ 558.837] (II) intel: Drive
I was booted into oihipster-26 ...
I ran a "Xorg -configure" on oi-26, added the following options:
Option "DRI" "on"
Option "AccelMethod" "uxa"
and it killed graphical display in oihipster-26
transferred to oi-27 and got no graphical display, Xorg log attached.
shame it
On 02/18/2015 17:41, Jonathan Adams wrote:
It'll take a reboot ... I'll try it now
No need in reboot, just killing gdm from root role ("pfexec pkill gdm")
should be enough.
2015-02-18 14:34 GMT+00:00 Alexander Pyhalov :
On 02/18/2015 17:25, Jonathan Adams wrote:
Attached
What happen
It'll take a reboot ... I'll try it now
2015-02-18 14:34 GMT+00:00 Alexander Pyhalov :
> On 02/18/2015 17:25, Jonathan Adams wrote:
>
>> Attached
>>
>>
> What happens if you force Intel driver in xorg.conf?
>
> Something like
>
> Section "Device"
> ... #Other directives here
>
Attached
On 18 February 2015 at 14:20, Alexander Pyhalov wrote:
> On 02/18/2015 17:13, Jonathan Adams wrote:
>
>> I upgraded hipster on my laptop this morning and the graphics display on
>> my
>> intel graphics card could not work above a 1024x768 resolution ...
>>
>> I previously updated on 15-
I upgraded hipster on my laptop this morning and the graphics display on my
intel graphics card could not work above a 1024x768 resolution ...
I previously updated on 15-jan-2015 (after the change of publisher)
I've attached the "update log" from when I upgraded ...
I'm not sure if it has anythi
no real options specified ...
jadams@jadlaptop:~$ grep -v '^#' /etc/auto_master
+auto_master
/net-hosts-nosuid,nobrowse
/homeauto_home-nobrowse
jadams@jadlaptop:~$ more auto_master.ldif
version: 1
DN: nisMapName=auto_master,dc=domain,dc=com
objectClass: top
objectClass
Hi,
not sure if it is relevant, but in Solaris user home dirs were on /export/home
while /home was reserved for automounter.
Not knowing FreeNAS (but some Linux systems), /home is location of user home
dirs.
Maybe problem solution can be looked in that direction?
Regards.
On 02/18/15 01:12 P
This sounds like the NFS Settings in the LDAP differ from those you used to
mount the share manually.
NFS version 4's LDAP Access and NFS version 3's rootsquash option can prevent
root from having access to other Users Homes.
FreeNas has some security Settings inplace to forbid root to access ot
I have an OpenIndiana laptop, it's running a copy of OpenLDAP as a replica
of an OpenLDAP on our work server (syncs whenever it connects) ... and it
uses this OpenLDAP database to power it's automount. (not sure if this is
of any relevance, but included for completeness)
I've been using this syste
18 matches
Mail list logo