This exact thing happened to me again, except I had removed the empty line
after the previous incident. I have two systems with otherwise identical root
crontabs (one still has a blank line) and this happened only on one. It
appears it happened just after or before a reboot, but it was a plann
On Tue, 2009-05-05 at 08:55 +0530, Anil Gulecha wrote:
...
> * StormOS: An XFCE based derivative of NCP2 is in the works. For those
> looking for a desktop variation of NCP2, keep a lookout on the StormOS
> website. The beta release of StormOS Hail is in the offing.
>
Nice to see one more lightw
Hi All,
This is to announce availability of NexentaCore Platform 2.0 RC2.
The release has stabilized. This release will become the final release
if no major bugs are reported.
Release Highlights:
--
* OpenSolaris build 104+ based with critical patches.
* Over 13000 packages i
On Tue, May 5, 2009 at 1:32 AM, Andre Lue wrote:
> Running powertop is showing the following errors. Anyone know what the
> problem may be
>
> eon:16:/deep/ips/usr/bin#truss -v all -w all -r all -o /tmp/foo ./powertop
> OpenSolaris PowerTOP version 1.1 (C) 2008 Intel Corporation
I already ans
Didn't work; it's not generating a core file, but running it from mdb gave
this, if it helps:
> ::stack
hash_lookup_pidthr+0x38()
> ::status
debugging PID 25513 (32-bit)
file: /export/home/alan/top/i386/top
threading model: raw lwps
status: stopped on SIGSEGV (Segmentation Fault)
event: stop on S
Alan Coopersmith wrote:
> Joerg Schilling wrote:
> > But please note that at the time Solaris 8 was created, Sun was just in a
> > state
> > where the managers believed in closed source. With Solaris 8, there are
> > only
> > thre OSS packages:
> >
> > - mkisofs
> > - gzip
> > - bash
>
On Mon, May 4, 2009 at 8:22 PM, Alan Coopersmith
wrote:
> Joerg Schilling wrote:
>> But please note that at the time Solaris 8 was created, Sun was just in a
>> state
>> where the managers believed in closed source. With Solaris 8, there are only
>> thre OSS packages:
>>
>> - mkisofs
>> -
Hi Martin,
Nearly two years ago I tweaked the SUNWlsimega driver to recognise the LSI
MegaRAID SATA 300-8X raid controller and have been using ever since (as I used
to manage the ftp site so know from which locations it was downloaded which
included Sun). It was a minor change and I found the d
Joerg Schilling wrote:
> But please note that at the time Solaris 8 was created, Sun was just in a
> state
> where the managers believed in closed source. With Solaris 8, there are only
> thre OSS packages:
>
> - mkisofs
> - gzip
> - bash
Even Solaris 8 had a lot more than just 3 o
The only reason I pointed it out was that I tried to install OpenSolaris as my
base OS and found the feature missing. Sometimes, knowing what question to ask
is almost as difficult as answering the question.
Thanks for the feedback.
--
This message posted from opensolaris.org
__
Running powertop is showing the following errors. Anyone know what the problem
may be
eon:16:/deep/ips/usr/bin#truss -v all -w all -r all -o /tmp/foo ./powertop
OpenSolaris PowerTOP version 1.1 (C) 2008 Intel Corporation
powertop: ../cpufreq.c : cpu-change-speed probe unavailable
powertop:
I have reasons.
What I didn't like were a few questions of how things were handled.
Nevertheless, I do respect him.
It is a thing of the past, it is ok.
%martin
On Mon, May 4, 2009 at 5:44 PM, Joerg Schilling
wrote:
> Martin Bochnig wrote:
>
>> In 2005 I got banned from the csw mailing lists
On Mon, May 4, 2009 at 5:23 PM, Joerg Schilling
wrote:
> Alan Coopersmith wrote:
>
>> Joerg Schilling wrote:
>> > For any of the dependencies, it should be obvious that the dependencies
>> > that
>> > are valid for Solaris 8 need to be installed for Solaris 11 too as any
>> > blastwave package n
!!! ONLY 5 MORE DAYS !!!
Remember the deadline for package submissions is May 8th.
The Software Porters Community can help if you have questions:
http://opensolaris.org/os/community/sw-porters/
Make sure to register your pkgs as soon as possible, you can
always add more later.
BTW. You can upd
Martin Bochnig wrote:
> In 2005 I got banned from the csw mailing lists (because I didn't like
> Dennis' ***intransparent*** ***business model*** , where all work
I have no idea why you don't like Dennis
...
> And: During times of non-dictatorship COMMUNITY effort, under
> co-leadersh
Alan Coopersmith wrote:
> Joerg Schilling wrote:
> > For any of the dependencies, it should be obvious that the dependencies that
> > are valid for Solaris 8 need to be installed for Solaris 11 too as any
> > blastwave package need to use the other probrams from it's own environment
> > in
> >
On Mon, May 4, 2009 at 5:03 PM, russell aspinwall
<7will...@dsl.pipex.com> wrote:
> Hi,
>
> It is great that it can be done using the methods you have outlined but the
> user is not prompted
>
> "Do you wish to add a device driver? Press Y to add driver"
>
> so the process is not that user frien
On Mon, May 4, 2009 at 5:02 PM, Hay, Mausul W wrote:
> Martin,
>
> I did not mean to imply that Windows had a Live product. What I was
> referring to is that while installing Windows, there is a point at which
> you may insert a manufacturer supplied diskette for drivers for hardware
> that is not
Hi,
It is great that it can be done using the methods you have outlined but the
user is not prompted
"Do you wish to add a device driver? Press Y to add driver"
so the process is not that user friendly compared to Windows or Ubuntu.
--
This message posted from opensolaris.org
__
On Mon, May 4, 2009 at 4:29 PM, Hay, Mausul W wrote:
> I have to agree with Russell on this one. Not to start an OS war here,
> but this feature has been available on Windows for years and they have a
Which feature? That you can add a driver into a running LiveCD system?
I wonder how this can be
Martin,
I did not mean to imply that Windows had a Live product. What I was
referring to is that while installing Windows, there is a point at which
you may insert a manufacturer supplied diskette for drivers for hardware
that is not supported by the media you are using (for example, you may
not h
On Mon, May 4, 2009 at 3:58 PM, russell aspinwall
<7will...@dsl.pipex.com> wrote:
> Thanks for the reply but building my own Live CD distro is not a very elegant
> solution.
> Surely a more practical approach would enable drivers to be added during the
> boot process either by automatically scann
I have to agree with Russell on this one. Not to start an OS war here,
but this feature has been available on Windows for years and they have a
much broader support for devices that does Solaris/Open Solaris... Is
there an architectural reason why it could not be done?
-Original Message-
F
Sun hosts a set of free forums which have been used for a long time to
discuss Solaris 10 issues. You need to register to post, but there is no
other cost involved:
http://forums.sun.com/category.jspa?categoryID=65
Since the Solaris 10 codebase is over 4 years old, the forums can be
more rele
Gian Paolo writes:
> is possible to install Crossbow on Solaris 10 10/08 sparc ?
No.
You could reinstall your system with OpenSolaris, and thus get
Crossbow (plus a lot of other new features), but there's no way to
install Crossbow on Solaris 10.
If you have a support contract, then I would reco
Thanks for the reply but building my own Live CD distro is not a very elegant
solution.
Surely a more practical approach would enable drivers to be added during the
boot process either by automatically scanning USB drives or a second DVD drive
if present.
This would allow a Live CD to recognise
On Mon, 2009-05-04 at 05:37 -0700, russell aspinwall wrote:
> Hi.
>
> I would like to install a device driver during the boot process of the Live
> CD so that it correctly identifies my hardware?
> Is this a feature that the Live CD supports?
> Could this feature be added to subsequent Live CD
Hi.
I would like to install a device driver during the boot process of the Live CD
so that it correctly identifies my hardware?
Is this a feature that the Live CD supports?
Could this feature be added to subsequent Live CDs?
This message is relates to the posting below in OpenSolaris:Discuss a
Try their list at http://www.opensolaris.org/jive/forum.jspa?forumID=110
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
I'm using OSOL snv_101b on a pair of HP DL360 G5.
I've configured AVS, and it was running fine during testing.
One of the 350's is used as a NFS server, and the other one being a
standby server.
Now AVS "fails" with the message entered logging mode: net write failed.
I've configured autosync to
On Mon, May 4, 2009 at 11:28 AM, Martin Bochnig wrote:
> That's not the problem.
> The problem is, that 5.9, 5.10, 5.10.1 and 5.11 are only symlinks to
> 5.8 most of the time, inside the csw repo.
> For simplicity it would have been sufficient to concentrate only on 2
> build targets, out of the c
Hi,
is possible to install Crossbow on Solaris 10 10/08 sparc ?
Thanks bye...
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Mon, May 4, 2009 at 10:57 AM, Joerg Schilling
wrote:
> Shawn Walker wrote:
>
>> Joerg Schilling wrote:
>> > Shawn Walker wrote:
>> >
>> >> My point was that a dependency algorithm was not the cause of the issue
>> >> with the blastwave packages. It is primarily an issue of how they are
>> >>
Shawn Walker wrote:
> Joerg Schilling wrote:
> > Shawn Walker wrote:
> >
> >> My point was that a dependency algorithm was not the cause of the issue
> >> with the blastwave packages. It is primarily an issue of how they are
> >> built.
> >
> > There is no "issue" with Blastwave packages. T
Joerg Schilling wrote:
Shawn Walker wrote:
My point was that a dependency algorithm was not the cause of the issue
with the blastwave packages. It is primarily an issue of how they are
built.
There is no "issue" with Blastwave packages. These packages just make use from
the binary compati
Shawn Walker wrote:
> My point was that a dependency algorithm was not the cause of the issue
> with the blastwave packages. It is primarily an issue of how they are
> built.
There is no "issue" with Blastwave packages. These packages just make use from
the binary compatibility grant from Su
Martin Bochnig wrote:
On Mon, May 4, 2009 at 5:15 AM, Shawn Walker wrote:
blastwave's packages are built with the assumption that libaries live
relative to the rest of the programs (such as under /opt/csw), are compiled
with different flags, and generally assume dependencies must be provided by
37 matches
Mail list logo