I got a similar problem. I guess you installed grub which is not able to find
boot_archive.
For me adding the following entry in menu.lst, for Solaris entry, resolved the
issue.
kernel /platform/i86pc/multiboot kernel/unix
module /platform/i86pc/boot_archive
Regards,
-Sriram
Th
Rich Teer wrote:
On Thu, 17 Nov 2005, Alan Coopersmith wrote:
and putting it all in /usr/bin & /usr/lib directly, because the FHS
What's FHS?
Filesystem Hierarchy Standard, part of the Linux Standards Base, and
official naysayer of software-specific subdirs under /usr.
http://www.pathname
On Thu, 17 Nov 2005, Alan Coopersmith wrote:
and putting it all in /usr/bin & /usr/lib directly, because the FHS
What's FHS?
--
Rich Teer, SCNA, SCSA, OpenSolaris CAB member
President,
Rite Online Inc.
Voice: +1 (250) 979-1638
URL: http://www.rite-group.com/rich
Scott N. wrote:
Could you explain your problems with the X location?
I'll probably do something similar from your view as I don't know
what's important for you...
I was frustrated that I went to /usr to try and use
/user/X11/xconfigure and noticed that Nexenta had /usr/X11R6 instead
We
Scott,
I think /usr/X11 and missing xconfigure should be considered as a
packaging bug or not-yet implemented feature.
Nexenta Xorg should support 3td party drivers like recent Nvidia
additions, etc. This could be easily entered as a feature request in NBTS.
And someone will address it sooner or
On 11/17/05, Scott N. <[EMAIL PROTECTED]> wrote:
> I really think that opensolaris should remain a core that Sun uses to gather
> enhancements from some great minds in the open source community for its
> Solaris
> flagship rather than have opensolaris available to bastardize it with
> countless '
> Could you explain your problems with the X location?
> I'll probably do something similar from your view as I don't know
> what's important for you...
I was frustrated that I went to /usr to try and use
/user/X11/xconfigure and noticed that Nexenta had /usr/X11R6 instead PLUS
xconfigure was no
Ethernet adapters are availalbe that plug directly into an external USB port,
just like a camara or other consumer product.
Does Solaris 10 or Opensolaris support such cards? The nic on the integrated
chipset (nforce4) of my system is not suppport by either.
thanks
This message posted from
Daniel Rock <[EMAIL PROTECTED]> wrote:
> Joerg Schilling schrieb:
> > [EMAIL PROTECTED] wrote:
> >>When you boot from a device the node does not need to be present in
> >>/dev* in order for you to remoutn it r/w so you can fix it.
> >
> >
> > This was true before /devices was on the "devfs" file
On Nov 16, 2005, at 7:35 PM, Al Hopper wrote:
http://www.genunix.org/mirror/index.html>
Many congrats to team ZFS!
Yes, many kudos!
There were a few issues installing b27 on my Ultra 20 (biggest was CD
4 hung indefinitely -- had to kill -9 the process), but resolvable
for the most part
On Thursday 17 November 2005 05:58 am, Patrick Mauritz wrote:
> As for why not using pkgsrc, there are many things to consider: eg. that
> pkgsrc builds basically your whole userland again (at least the large
> chunks: yet another perl installation, yet another python, ..)
This is currently a prob
On 11/17/05, Stephen Hahn <[EMAIL PROTECTED]> wrote:
>
>I thought I should note that the packaging tools and also make(1S)
>and sccs(1) have been released as redistributable binaries:
>
>http://opensolaris.org/os/community/tools/pkgtools/
>http://opensolaris.org/os/community/tools/d
Is there a way to crypt/decrypt a folder by using the opensolaris crypto
service? (i'm talking about some crypt/decrypt system based on a symmetrical
key provided by the user at mount time)
This message posted from opensolaris.org
___
opensolaris-discus
I thought I should note that the packaging tools and also make(1S)
and sccs(1) have been released as redistributable binaries:
http://opensolaris.org/os/community/tools/pkgtools/
http://opensolaris.org/os/community/tools/devpro/
Discussion of specific issues will be in [EMAIL PROT
Joerg Schilling schrieb:
[EMAIL PROTECTED] wrote:
When you boot from a device the node does not need to be present in
/dev* in order for you to remoutn it r/w so you can fix it.
This was true before /devices was on the "devfs" filesystem.
But having /usr ready helps a lot.
It is no fun, cd
Ok, I know this the holiday season and some folks were wondering if there
would be a meeting this month since Thanksgiving is upon us. Well, the answer
is yes, the show must go on.
This months meeting is very special, as it offers a perspective into a
technology that offers a magnitude of possi
[EMAIL PROTECTED] wrote:
>
> >Please explain why you believe this.
> >
> >the only difference I see in your case is that you would need to find
> >the /devices entry to mount /usr so it makes sense to have find or
> >a name completing shell in /
>
>
> When you boot from a device the node does not
>Please explain why you believe this.
>
>the only difference I see in your case is that you would need to find
>the /devices entry to mount /usr so it makes sense to have find or
>a name completing shell in /
When you boot from a device the node does not need to be present in
/dev* in order for
[EMAIL PROTECTED] wrote:
>
> >> But the explanation is fairly simple: you cannot recover from a number
> >> of failures (corrupt vfstab, bad /dev* links for boot device) without
> >> having /usr mounted; you cannot mount /usr when those things happen.
> >
> >And you cannot recover if the same hap
"Scott N." <[EMAIL PROTECTED]> wrote:
> After my initial trial with Nexenta and then finding that X was installed in
> non-stardard Solaris location, I have now made an effort to only support TRUE
> Solaris-like 'distro's' like Schillix or even better may just stick with
> Solaris Express for m
>> But the explanation is fairly simple: you cannot recover from a number
>> of failures (corrupt vfstab, bad /dev* links for boot device) without
>> having /usr mounted; you cannot mount /usr when those things happen.
>
>And you cannot recover if the same happens with a big / installation
>eithe
[EMAIL PROTECTED] wrote:
>
>
> >Yes.
> >
> >> And we've long said you shouldn't be doign that :-)
> >
> >Show me the doc or white paper that says so and why.
>
>
> Read my Usenet postings :-)
>
> But the explanation is fairly simple: you cannot recover from a number
> of failures (corrupt vfstab,
Dennis Clarke <[EMAIL PROTECTED]> wrote:
> The boot -m milestone=none resulted in this :
>
> Booting to milestone "none".
> Requesting System Maintenance Mode
> (See /lib/svc/share/README for more information.)
> Console login service(s) cannot run
>
> Root password for system maintenance (control
Andy Tucker <[EMAIL PROTECTED]> wrote:
> Except for the binaries that are in Solaris Express but not part of
> OpenSolaris (and that aren't covered by the binary redistribution
> license). Bill could do this with SchilliX, or BeleniX, or Nexenta
> GNU/Solaris, but not with Solaris Express. (And
On Thu, 2005-11-17 at 14:23, Roberto Pereyra wrote:
> Why not use it?
there are people using it.
As for the GPL requirement, I assume you refer to the debian based
distro. It seems, they want to have a debian-style distro, and pkgsrc
won't help them in any way.
As for why not using pkgsrc, there
Hi
An option that I believe that it has not been considered in the news
distributions based on Opensolaris is to use the system of packages of
called NetBSD pkgsrc.
http://www.pkgsrc.org/
http://www.netbsd.org/Documentation/pkgsrc/platforms.html#solaris
Pkgsrc support Solaris well and use stand
On 11/17/05, alessioc <[EMAIL PROTECTED]> wrote:
> how did you install it? was it an upgrade or a clean install?
> i have had a similar problem with b24
> http://www.opensolaris.org/jive/thread.jspa?threadID=2745&tstart=0
This was a fresh install. I suspect that something went wrong during
the in
27 matches
Mail list logo
