Hello,
I use sysidcfg to configure my zone. However, during configuration, the root
password gives a syntax error. The password I use in the sysidcfg is the
encrypted version of abc123. I don't know why it doesn't like it. Let me walk
you through my zone creation process. Maybe somebody
It didn't work. It is still giving the same syntax error...
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
v wrote:
SunOS Release 5.11 Version snv_111b 32-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hostname: zone1
Reading ZFS config: done.
Mounting ZFS filesystems: (6/6)
root_password=fto/dU8MKwQR
Is this encrypted string missing a
I don't think so... It looks like it works:
http://blogs.sun.com/observatory/en_US/entry/zones_and_crossbow1
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
I wonder if there is an extra space at the end of the line or some other non
visible character.
On Wed, Aug 26, 2009 at 1:44 PM, v varolkay...@gmail.com wrote:
I don't think so... It looks like it works:
http://blogs.sun.com/observatory/en_US/entry/zones_and_crossbow1
--
This message posted
Well, I typed it myself instead of copying and pasting it. It still gives the
same error. In the error, it says the error is in position 15, which is the
character f right after the equal sign. I tried putting quotation marks, but
it still didn't like it.
--
This message posted from
v wrote:
I don't think so... It looks like it works:
http://blogs.sun.com/observatory/en_US/entry/zones_and_crossbow1
I would validate with that blogger if that sysidcfg had actually
been validated. If you look a little lower in the blog, the sysidcfg
file failed to get get consumed by
are you running opensolaris?
if so, i'm guessing that the problem is the format of the hashed
password. by default, solaris version = 10 and nevada use crypt for
hashing passwords, but opensolaris uses SHA256. these settings seem to
be controlled via /etc/security/policy.conf. just search for
