the illumos 151 tree and whether OI has
> packaged that.
>
>
>
> On Wednesday, December 14, 2011 08:18 AM, Patrick O'Sullivan wrote:
>> Question for the group at large:
>>
>> Was true Kerberos support for CIFS ever added? It's tough to tell because
Question for the group at large:
Was true Kerberos support for CIFS ever added? It's tough to tell because the
old OpenSolaris documentation/bug tracking has been largely taken down.
Here's one of the old references I can find:
http://arc.opensolaris.org/caselog/PSARC/2009/673/20091209_natalie.
That list is not relevant. Joyent targeted their port strictly for Intel
chips with VT-x and EPT.
Basically this means you need a Nehalem or later (Westmere, Sandy Bridge)
processor.
On Friday, November 4, 2011, carlopmart wrote:
> On 11/04/2011 01:33 PM, alessio wrote:
>>
>> I'm very interested
Forgot to post this earlier. Here are my personal notes for getting
auth to AD working:
(1) Add hostname/IP in DHCP (if applicable) and DNS
(2) Configure NTP on host (need /etc/inet/ntp.conf, copy from
/etc/inet/ntp.client)
(3) pkg install pkg:/system/security/kerberos-5
(4) kclient
(5) Enable st
Next gen spec sheets suggest the X25-E will get a "Power Safe Write
Cache," something it does not have today.
See:
http://www.anandtech.com/Show/Index/3965?cPage=5&all=False&sort=0&page=1&slug=intels-3rd-generation-x25m-ssd-specs-revealed
(Article is about X25-M, scroll down for X25-E info.)
On
# pkg install pkg:/system/security/kerberos-5
# kclient
It's a wizard that supports setting up joining to an AD domain. That
will get you started. I have a cheat sheet that I can send from home
later if you need it. I wrote down what I did because it took a while
to get it all working well.
On Mo
tart
> This should produce no output if it's working correctly.
>
> -Albert
>
> On Sat, Dec 18, 2010 at 6:48 PM, Patrick O'Sullivan
> wrote:
>> Should the fix automatically work if the global zone and any
>> non-global zones have been updated from oi147 to oi1
Should the fix automatically work if the global zone and any
non-global zones have been updated from oi147 to oi148?
Mine are upgraded and I'm still seeing the error.
Thanks for the help!
On Dec 18, 2010, at 17:08, Jeppe Toustrup wrote:
> 2010/12/18 Patrick O'Sullivan :
>>
Anyone else seeing similar messages when booting a zone? I've seen
this now on two test systems, one a VM, and the other bare metal,
first running oi147 and now oi148.
Dec 18 12:43:55 svc.startd[1207]: svc:/system/auditset:default: Method
"/lib/svc/method/svc-auditset" failed with exit status 1.
D
xvm is a Xen based virtualization tool.
lvm is the linux volume management tool (that pains me even to speak of).
On Sat, Dec 18, 2010 at 10:12 AM, Roelof van der Wal wrote:
> What is the benefit of using lvm dom0 on zfs? I am not familiar with lvm dom0
> but after reading some info about it loo
svcadm disable svc:/network/physical:nwam
svcadm enable svc:/network/physical:default
Configure as normal.
On Dec 1, 2010, at 15:58, Harry Putnam wrote:
I wonder why it appears to be so difficult under openindiana and its
predecessors to simply and quickly setup a static network.
Virtually all
g is working on reboot.
Thanks for your help, everyone!
On Thu, Nov 18, 2010 at 10:55 AM, Patrick O'Sullivan
wrote:
> I will give my nsswitch.conf file a bit more scrutiny and see if I can
> get this to work as well.
>
> Still curious that ldap/client doesn't start on boot,
en real goosed over the upgrade to 147.
>
> Jon
>
> On 18 November 2010 14:56, Chris Ridd wrote:
>>
>> On 18 Nov 2010, at 14:46, Patrick O'Sullivan wrote:
>>
>>> /var/ldap/ldap_client_file is populated correctly. Further, it's
>>> identical t
/var/ldap/ldap_client_file is populated correctly. Further, it's
identical to the version that ldapclient backs up in the restore
directory.
/etc/nsswitch.conf looks good too.
On Nov 18, 2010, at 1:55, Chris Ridd wrote:
>
> On 18 Nov 2010, at 02:41, Patrick O'Sullivan wrote:
&g
ldap_client_file definitely isn't getting zeroed. Does your suspicion
still apply in that case?
On Nov 18, 2010, at 5:27, Tom Kranz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On 18 Nov 2010, at 02:41, Patrick O'Sullivan wrote:
>
>> I'
wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>
>> On 18 Nov 2010, at 02:41, Patrick O'Sullivan wrote:
>>
>>> I've gotten a config working where I have Kerberos auth to AD and
>>> passwd lookups via LDAP to AD. I enable
I've gotten a config working where I have Kerberos auth to AD and
passwd lookups via LDAP to AD. I enable it, and it works fine, but on
a reboot, it stops working. Please let me know if you have any
thoughts as to why this happens. (This behavior is common to both
oi147 and Solaris 11 Express.)
Co
Hello all,
I successfully have gotten authentication to an AD Kerberos server
working along with uid/gid resolution from AD LDAP. However, I am
getting a strange PAM error and the only reference I can find for it
is in the OpenSolaris PAM source code.
r...@oitest1:~# uname -a
SunOS oitest1 5.11 o
18 matches
Mail list logo
