Hi,
pkg set-publisher --non-sticky openindiana.org
pkg set-publisher-g http://pkg.opensolaris.cz:1/
--search-before=openindiana.org jds.openindiana.org
pkg set-publisher --non-sticky sfe
pkg set-publisher --non-sticky sfe-encumbered
Best regards,
Milan
On st, 2014-02-19 at 20:55 +0100, H
Milan,
I've so far NOT added your jds repo to my config; I can't make head or
tails of how to do that, please elucidate!
My publishers are currently set up as:
PUBLISHER TYPE STATUS URI
openindiana.orgorigin online
http://pkg.openin
In regard to: [OpenIndiana-discuss] OI-151a9, Marc Lobelle said (at 7:11pm...:
I see that a new version 0I-151a9 is available, but the version to
download at http://openindiana.org/download/ is still 151a8. Where can I
find the ISO for 151a9 ? Is it smoother that 151a8 that had many small
inconv
Hello,
I see that a new version 0I-151a9 is available, but the version to
download at http://openindiana.org/download/ is still 151a8. Where can I
find the ISO for 151a9 ? Is it smoother that 151a8 that had many small
inconvenients (gnome unusual behaviours etc.).
Thanks
Marc
_
Hi,
could you describe your system configuration? What is in your
~/.xsession-errors ?
If you do pkg verify then is your system OK?
If you check output of pkg list, are all your packages on the latest
versions? It means all components from system repository are on versions
ending with -0.151.1.9
OpenHoosiers,
Something else which can complicate updating from 151a7 is hipster. If you
have "gone hipster" on a 151a7 installation, then your work is more
complicated. I have successfully upgraded a hipster 151a7 installation through
a8 dev to a9 dev. I would not be able to retrace my steps
Le 2014/02/19 16:09 +0100, Hans J. Albertsson a écrit:
This is basically my7 experience, too.
And noone seems to have any idea about why these Gnome problems ACTUALLY
occur.
GNOME has always been a little picky on upgrades, that's why there is a
gnome-cleanup tool in Solaris, and I believe, i
On 19/02/2014 15:09, Dmitry Kozhinov wrote:
.
There was an advice to reinstall gvfs. Tried in a test virtualbox setup.
This worked in reverse! In /virtualbox/, 151a7 /successfully/ upgraded
to 151a9. Though in vbox the upgrade went successfully, I have tried if
reinstalling gvfs is safe (befo
This is basically my7 experience, too.
And noone seems to have any idea about why these Gnome problems ACTUALLY
occur.
On 2014-02-19 15:09, Dmitry Kozhinov wrote:
Not to blame anyone, but IMO every next OI release becomes less stable
than previous...
The latest release which works stable f
Not to blame anyone, but IMO every next OI release becomes less stable
than previous...
The latest release which works stable for me is 151a7. 151a8 also
worked, though I could not configure network interface using GUI tool in
it (after disabling "nwam" and enabling "default").
Then 151a9 wa
On 02/19/2014 06:50 AM, Jim Klimov wrote:
On 2014-02-17 23:54, alka wrote:
I would prefer a mainboard based on an Intel serverchipset
with 4 better 8 GB ECC RAM together with an i3 (Xeon as an option
then for napp-in-one)
If you look at
http://www.supermicro.nl/products/motherboard/Xeon3000/
On 2014-02-19 13:27, Peter Tribble wrote:
However, every now and then I need to install some package into
all zones. While I can parse the "zoneadm list" output and find
zoneroots and ask pkg(5) to install into the altroots,
Would running pkg via zlogin be better?
It would be roughly equivalen
On Wed, Feb 19, 2014 at 11:18 AM, Jim Klimov wrote:
> One of nice features about legacy (SVR4) zones was that one could
> use pkgadd to install or update packages to the same version in
> all installed or running zones.
>
> One of nice features about ipkg zones is that every operating
> environme
On 2014-02-17 23:54, alka wrote:
I would prefer a mainboard based on an Intel serverchipset
with 4 better 8 GB ECC RAM together with an i3 (Xeon as an option then for
napp-in-one)
If you look at http://www.supermicro.nl/products/motherboard/Xeon3000/#1150
you get such boards that are perfect fo
On 2014-02-19 11:13, Hans J. Albertsson wrote:
Precisely.
The only remaining question is why HP disabled these bits; Do they know
something that makes their decision technically well-motivated, or are
they just playing a marketing game?
I'd say marketing - the boxes are too good otherwise and
I think it is just marketing.
--Original Message--
From: Hans J. Albertsson
To: Discussion list for OpenIndiana
ReplyTo: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] Three specific N54L microserver related
questions. Sort of Re: low low end server...
Sent: Feb 19, 20
One of nice features about legacy (SVR4) zones was that one could
use pkgadd to install or update packages to the same version in
all installed or running zones.
One of nice features about ipkg zones is that every operating
environment is pretty much individual and changes in one do not
necessari
Precisely.
The only remaining question is why HP disabled these bits; Do they know
something that makes their decision technically well-motivated, or are
they just playing a marketing game?
On 2014-02-18 23:35, Volker A. Brandt wrote:
Reginald Beardsley writes:
I particularly didn't like t
18 matches
Mail list logo
