Below are links to the latest batch of overview reports (rollups).
They also appear on the following...
Web page: http://del.icio.us/bootblog/oss:rollups
RSS Feed: http://del.icio.us/rss/bootblog/oss:rollups
zfs-discuss, 05/01 - 05/15
http://mail.opensolaris.org/pipermail/zfs-discuss/2006-May/00
I'm running OpenSolaris on a few different systems.
I have a HP DL360 running Open Solaris with ZFS. It is used as an IDS server,
with Snort logging to a MySQL database with BASE.
I also have a V880 running Solaris Nevada Build 36. I'm currently using Veritas
VxVM/FS 4.1 instead of ZFS. This ru
Dave Marquardt writes:
> "Larry" == Larry Becke <[EMAIL PROTECTED]> writes:
>
> Larry> I would still consider it to be a sub-process change to the
> Larry> environment (in this case the visual environment) and I would
> Larry> NOT want it to come back to the parent process. ie - resize
> Larry> d
On Thu, 18 May 2006, Dave Marquardt wrote:
> I'd find it strange if, for some reason, I shrunk the window for some
> reason when in a subshell, and when I returned vi used the terminal
> size settings from before the resize. So now I'd have some of my text
> off the edge of the screen or somethin
"Larry" == Larry Becke <[EMAIL PROTECTED]> writes:
Larry> I would still consider it to be a sub-process change to the
Larry> environment (in this case the visual environment) and I would
Larry> NOT want it to come back to the parent process. ie - resize
Larry> during child operation, go back to o
On Thu, 2006-05-18 at 13:39, Larry Becke wrote:
> I would still consider it to be a sub-process change to the
> environment (in this case the visual environment) and I would NOT want
> it to come back to the parent process.
we're not talking about a window size which is under the control of an
app
I would still consider it to be a sub-process change to the environment (in
this case the visual environment) and I would NOT want it to come back to the
parent process.
ie - resize during child operation, go back to original size (or use original
sizing) when returned to parent.
This messa
Alan Coopersmith writes:
> > The distinction is that window size isn't an environment string. It's
> > a property known to the tty subsystem. Since this is shared between
> > the job that's stuck in wait(2) (i.e., vi) and the job that's running,
> > it's at least feasible to have vi check for cha
James Carlson wrote:
Larry Becke writes:
Resize the window while in vi, before you run the sub-shell
The distinction is that window size isn't an environment string. It's
a property known to the tty subsystem. Since this is shared between
the job that's stuck in wait(2) (i.e., vi) and th
Larry Becke writes:
> Resize the window while in vi, before you run the sub-shell
The distinction is that window size isn't an environment string. It's
a property known to the tty subsystem. Since this is shared between
the job that's stuck in wait(2) (i.e., vi) and the job that's running,
i
The difference between the support for a home grown collection of scripts vs
trying to support a commercial application on your own is huge.
Typically, when you write scripts, you know how and why they work. When they
break, you can follow them fairly easily, because you wrote them.
With someo
On Thu, 18 May 2006, Bernhard Neuhauser wrote:
- licence not for production or im wrong?
Would this already prohibit a company to use SE for internal file server for
example?
Solaris Express you can think of as a "Beta Version" of Solaris. Someone
will correct me if I am wrong but you can
When you *escape* to a shell, you are running a subshell. Any changes to the
environment while running a sub-shell are lost - ie not passed back to the
parent when you exit.
It would be like running a sub-shell that changes IFS, then expecting the
changed IFS to apply to the parent shell..
Re
Thx for your feedback :o)
I think the only open question would be nexenta vs solaris express.
Solaris Express:
+ i guess it should be more stable / mature
+ the chance that nexenta will go away is higher then the chance that the se
project will be stoped i think
- nexentas got a package repo
On Thu, 18 May 2006, Mello wrote:
First off, I guess that the above URL should be
http://www.gnusolaris.org/ (Nexenta home page). Keep in mind it is
only available for x86 systems, though.
Thank you for fixing my typo.
In my case, I'm a total newbie when it comes to Solaris, I've tried
Solar
On 5/18/06, Bill Rushmore <[EMAIL PROTECTED]> wrote:
On Thu, 18 May 2006, Bernhard Neuhauser wrote:
http://www.gnusolaris.orgs.org
...
Hi Bill,
Good question, hope my answer won't be stupid or unuseful :)
First off, I guess that the above URL should be
http://www.gnusolaris.org/ (Nexenta home
On Thu, 18 May 2006, Bernhard Neuhauser wrote:
Hi all,
Im new to Solaris/OpenSolaris so maybe my questions might sound stupid. My only
sol confrontation was a short test-setup of sol10 1year ago.
Is OpenSolaris already ready to be used? Or is it still in a stage where its
only interesting fo
Nicolas Linkert wrote:
I would just like to know whether BrandZ is included in Solaris Express Build
38. Does anyone happen to know? I am trying to create a zone for Debian with
the following command:
No it is not. Why ? because the project is still in development.
See http://opensolaris.or
I would just like to know whether BrandZ is included in Solaris Express Build
38. Does anyone happen to know? I am trying to create a zone for Debian with
the following command:
create -B lx
which I found in a howto along the way. But it says that "-B" is not an option
...
This message pos
Hi all,
Im new to Solaris/OpenSolaris so maybe my questions might sound stupid. My only
sol confrontation was a short test-setup of sol10 1year ago.
Is OpenSolaris already ready to be used? Or is it still in a stage where its
only interesting for OpenSolaris developers?
Currently i dont need
20 matches
Mail list logo
