BTW, I took a break from the server last night, and set up ntp and DNS
just before supper. To see if my old config files were OK, I ran:
svcs -xv
root:media was trying to start up again, and complaining about .volsetid
again. I disabled the service as per below. root:default was already
enable
On 13-11-24 11:12 PM, David Thistlethwaite wrote:
Hello folks
I am a newbie to openindiana.
I am considering using the 151a8 version as a production server, the
server will perform the following
1) Server files via samba and NFS
2) Run around 10 virtual machines using virt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/2013 6:12 PM, Jim Klimov wrote:
> Hello James,
>
> There are so many well-phrased sentences that I just can't snip
> out the few I'd respond to ;) And thanks for the historical
> insights and rationales, that is much appreciated too :)
>
>>
Hello James,
There are so many well-phrased sentences that I just can't snip out
the few I'd respond to ;) And thanks for the historical insights and
rationales, that is much appreciated too :)
You can't buy disk drives small enough to make sense out of a
> split /usr.
Yes you can =)
Regardi
On 27 November 2013 00:34, Lionel Cons wrote:
> On 26 November 2013 19:23, Irek Szczesniak wrote:
>> On Tue, Nov 26, 2013 at 7:07 PM, Jim Klimov wrote:
>>> On 2013-11-26 17:25, Jim Klimov wrote:
On 2013-11-17 03:50, Jim Klimov wrote:
>
>For years I've mentioned "split-root"
I never used Linux, so no.
R
On 11/27/2013 6:24 AM, Gregory Youngblood wrote:
Is it possible the hosts file originated from a Linux host? Not sure about *bsd
and others but I know some linux flavors used to automatically include the
hostname with 127.0.0.1 in /etc/hosts.
Greg
Sent from my
Hello everyone,
it's already some time since I tried OpenIndiana.
I would like to know the status of WPA2 support?
Back then (beginning of this year) there was no way to connect to a
WPA2-Passphrase secured wireless network. Did something change since then?
It would be nice if someone could giv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/26/2013 5:51 PM, Peter Tribble wrote:
> The miniroot for any live or network boot already has a chunk of
> /usr. There's a real problem here in that there simply isn't a
> clean separation of root vs usr any more. If you really want to
> have a s
On 27 November 2013 15:59, Jim Klimov wrote:
> On 2013-11-27 15:15, Peter Tribble wrote:
>>
>> NIC drivers can't live in /usr at all. That part
>> isn't an interesting problem to solve.
>
>
> Good to know. Then we don't declare that networking should restart
> after the devfsadm re-run for the pos
On 27 November 2013 01:51, Jim Klimov wrote:
> On 2013-11-26 17:25, Jim Klimov wrote:
>>
>> On 2013-11-17 03:50, Jim Klimov wrote:
>>>
>>>For years I've mentioned "split-root" installations of Solaris-like
>>> systems in such a way that the root filesystem (the BE) is represented
>>> by severa
On 27 November 2013 13:15, Jim Klimov wrote:
> On 2013-11-27 12:16, Jim Klimov wrote:
>>>
>>> restart = disable and enable. If your /usr is nfs mounted,
>>> what happens when you disable networking?
>>
>>
>> I see a good point here, thanks :)
>>
>> So this trick with restarts should take place onl
You sir are a lifesaver. That's all it was. Kind of scary, still.
Thanks,
Francois
On Wed, Nov 27, 2013 at 10:03 AM, Jonathan Adams wrote:
> are you sure that Windows 7 hasn't just set the active partition to be
> itself?
>
> you might well be able to get the system to boot with a
> http://www.s
Hi
If windows 7 is using the old fashioned boot loader just dd off the first 512
bytes of a *nix disk, place the file in the root of the windows partition and
put an entry pointing to it in the boot.ini file, then you can use the windows
boot loader to boot into a different os. I know this is no
are you sure that Windows 7 hasn't just set the active partition to be
itself?
you might well be able to get the system to boot with a
http://www.supergrubdisk.org/super-grub2-disk/ cdrom, or setting the active
partition with something that isn't windows ...
Jon
On 27 November 2013 14:52, Franc
On 2013-11-27 15:15, Peter Tribble wrote:
NIC drivers can't live in /usr at all. That part
isn't an interesting problem to solve.
Good to know. Then we don't declare that networking should restart
after the devfsadm re-run for the possibly newly mounted /usr might
find new drivers.
We do it on
I have multi boot OI and win7 and it has been working great for over a
year. Not sure exactly how that happened but it appears that windows
decided to overwrite my bootloader. How do I restore it?
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@o
Is it possible the hosts file originated from a Linux host? Not sure about *bsd
and others but I know some linux flavors used to automatically include the
hostname with 127.0.0.1 in /etc/hosts.
Greg
Sent from my HTC One on the Verizon Wireless 4G LTE network
___
On Wed, Nov 27, 2013 at 11:16 AM, Jim Klimov wrote:
> First of all, thank you for sharing your advice.
> Coming from a distro maintainer, it is very valuable :)
Building a distro (largely from scratch, in my case) teaches you
an awful lot about how the system really works. Far more than I
ever
Typo fix:
+if [ x"$_USR_WAS_AVAILABLE" = no ]; then
+if [ x"$_USR_WAS_AVAILABLE" = xno ]; then
+ for _SVC in $NET_PHYS_FMRI $NET_NWAM_FMRI $NET_IPTUN_FMRI; do
+ _STATE="`$SVCS -H -o state $_SVC`"
+ [ x"$debug_mnt" = x1 ] && echo "fs-root: $_SVC: $_STATE"
> /
On 2013-11-27 12:16, Jim Klimov wrote:
restart = disable and enable. If your /usr is nfs mounted,
what happens when you disable networking?
I see a good point here, thanks :)
So this trick with restarts should take place only in case that
I am testing - with the locally mounted /usr filesystem
On 2013-11-27 12:21, Rainer Heilke wrote:
and the /etc/hosts included:
127.0.0.1 localhost loghost extname
Correct.
This would indeed not work, because (if the /etc/hostname.* file
does not contain a numeric IP address explicitly), the name for
the interface is matched to the hosts name dat
On 11/27/2013 2:08 AM, Jim Klimov wrote:
On 2013-11-27 08:09, Rainer Heilke wrote:
I had a few minutes to poke around, and I found the problem (at last!).
The log never really showed anything, but it finally made me question
something.
The /etc/hosts file that I've used since 151a1 needed chan
First of all, thank you for sharing your advice.
Coming from a distro maintainer, it is very valuable :)
On 2013-11-27 11:03, Peter Tribble wrote:
On Wed, Nov 27, 2013 at 12:51 AM, Jim Klimov wrote:
So far the best shot, both compact and effective, was fixing the
filesystem/root service like i
On 2013-11-27 08:09, Rainer Heilke wrote:
I had a few minutes to poke around, and I found the problem (at last!).
The log never really showed anything, but it finally made me question
something.
The /etc/hosts file that I've used since 151a1 needed changing. It seems
rules have tightened up. Qui
On Wed, Nov 27, 2013 at 12:51 AM, Jim Klimov wrote:
> On 2013-11-26 17:25, Jim Klimov wrote:
>
>> On 2013-11-17 03:50, Jim Klimov wrote:
>>
>>>For years I've mentioned "split-root" installations of Solaris-like
>>> systems in such a way that the root filesystem (the BE) is represented
>>> by
25 matches
Mail list logo
