Re: [osol-discuss] Blastwave.org
+-- | On 2008-08-10 17:17:03, Brent Jones wrote: | | Is there a FreeBSD ports style packaging system? Source based, with sane and | configurable build options, with dependency checking, and easy methods of | removal/updates? I've been using pkgsrc (NetBSD's ports tree) for the last two years to good effect. Only for server/CLI stuff. Nothing GUI-related. -- bda Cyberpunk is dead. Long live cyberpunk. http://mirrorshades.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] df doesn't work well with chroot,
sorry, in fact, I have already loopback mount /etc/mnttab. I set up the environment in Solaris10 and Solaris9. but solaris 9 works well. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
On Sun, Aug 10, 2008 at 4:43 PM, Patrick Ale <[EMAIL PROTECTED]> wrote: > On Mon, Aug 11, 2008 at 1:38 AM, Mike Meyer <[EMAIL PROTECTED]> wrote: > > On Sun, 10 Aug 2008 22:48:08 +0200 > > > > > Ah, the solaris community is just *full* of flashbacks. Chasing down > > and installing the dependencies for a package by hand? Something I > > thought I'd seen the last of in 1998. > > I am not saying which is better, I am just saying the dependencies are > there for giving full facts in the discussion's sake :) > > Both Sunfreeware and CSW have pros and cons, just use what you feel > more comfortable with, I am really too busy for a sunfreeware vs CSW > vs the world flame bate > > -- > Patrick > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > Is there a FreeBSD ports style packaging system? Source based, with sane and configurable build options, with dependency checking, and easy methods of removal/updates? Regards, -- Brent Jones [EMAIL PROTECTED] ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
On Mon, Aug 11, 2008 at 1:38 AM, Mike Meyer <[EMAIL PROTECTED]> wrote: > On Sun, 10 Aug 2008 22:48:08 +0200 > > Ah, the solaris community is just *full* of flashbacks. Chasing down > and installing the dependencies for a package by hand? Something I > thought I'd seen the last of in 1998. I am not saying which is better, I am just saying the dependencies are there for giving full facts in the discussion's sake :) Both Sunfreeware and CSW have pros and cons, just use what you feel more comfortable with, I am really too busy for a sunfreeware vs CSW vs the world flame bate -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] openoffice wont load
I downloaded the code again and this is what i see when I try to rn the install. Says it cannot find the java but java is isntalled. bash-3.2# which java /usr/bin/java bash-3.2# java -version java version "1.6.0_04" Java(TM) SE Runtime Environment (build 1.6.0_04-b12) Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode) bash-3.2# This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] what is wrong with mu install
With both my dell e521 and hp a705w I just hit enter when moving the mouse doesn't work. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] openoffice wont load
I installed in on a Toshiba Laptop. the which command says /usr/bin/soffice /usr/bin/soffice bash-3.2# soffice ld.so.1: soffice.bin: fatal: /etc/openoffice.org2.4/program/libvcl680si.so: corrupt or truncated file ld.so.1: soffice.bin: fatal: libvcl680si.so: open failed: No such file or directory ld.so.1: soffice.bin: fatal: relocation error: file /opt/openoffice.org2.4/program/soffice.bin: symbol __1cEEditIdragOver6MrknDcomDsunEstarMdatatransferDdndTDropTargetDragEvent__v_: referenced symbol not found /usr/bin/soffice[254]: wait: 705: Killed This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] what is wrong with mu install
OK Ill try that . It seem to do it all the time the screen saver kicks in. I think the monitor had a built in power save option. Not sure if you can change that or not. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] dual display
Can you explain to me what this is for? I dont want to jsut make a change. Would like to understand why, Thanx This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
On Sun, Aug 10, 2008 at 4:30 PM, UNIX admin <[EMAIL PROTECTED]> wrote: >> There were enough problems with how the stuff from >> blastwave/csw was packaged to make it distasteful to >> use, this simply puts the last nail in the coffin. >> For the most part I build everything from the source, >> for those that I don't really want to take the time >> to build I'll go to www.sunfreeware.com > > Heh! > > Anybody with an insane idea of still "packaging" stuff into /usr/local and > not declaring dependencies obviously doesn't fully understand what they are > doing. But of course you've read the text provided with the hyperlink that states the dependencies eh? ;-) To be honest with you I use both CSW and sunfreeware at times. CSW when I need something really really quick and dont care too much for the bloatware dependencies installed, sunfreeware when I have a bit more time to spend on what I need, and sources when I want to make myself unmissable at work ;-) -- Patrick ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
Dr. Robert Pasken writes: > Actually a request for a single utility got you a bunch of c**p that wasn't > necessary spread into places that made it difficult to remove once you found > out the utility you thought you wanted dropped a core. Using mtx as an > example; mtx doesn't have a lot of dependencies and can be built with a > simple "configure --prefix=/opt/local; make; make install" and it will work. > Yet the same cann't be said for the blastwave version. > No, it depends on a massive total of one other package - CSWcommon. Never forget CSW packages are built on Solaris 8 and work on all newer versions. So they can't base their packages on native Solaris packages, there are too many versions. Ian. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
Actually a request for a single utility got you a bunch of c**p that wasn't necessary spread into places that made it difficult to remove once you found out the utility you thought you wanted dropped a core. Using mtx as an example; mtx doesn't have a lot of dependencies and can be built with a simple "configure --prefix=/opt/local; make; make install" and it will work. Yet the same cann't be said for the blastwave version. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] I want to understand 'Boot Environment'!
This interests me too. I don't have the answers, but can offer some of what
I've learned.
On Sun, Aug 10, 2008 at 5:32 PM, Uwe Dippel <[EMAIL PROTECTED]> wrote:
> This is not so much a question of a specific problem, than one of concepts
> and limitations.
> If you look at the various posts of mine in here, I asked at different
> times on essentially the same topic: What constitutes a Boot Environment; in
> the meaning of 'how complete is it', can it be transferred?'. One of my
> questions was, why can I not transfer a full slice to another machine? The
> answers given were not fully on-topic, like 'use flash archive'.
I agree that it would not answer your question, but people sometimes try to
offer some help towards solving your problem even when they can not give you
all the answers, thus alternative methods are suggested.
In any case, you generally CAN transfer a slice. Whether that is all you
need to do to make a system bootable is another question. What is in the
slice? What file system is used on the slice?
Off the top of my head a few reasons why a slice moved to a new system might
not be bootable:
1. Entried in /etc/vfstab might not be valid on the new system - you will
need to carefully check this. In most cases, booting from a CD-rom you may
be able to edit these entries and fix them
2. If using ZFS as root file system you need to boot into failsafe mode and
mount the file system. This updates the physical device path to the disk
and after that the disk will probably be mountable.
3. Some of the boot phase information is not stored in the slice. Parts of
it is potentially in the disk boot block and/or the disk's master boot
sector. For this purpose you have to be very clear about the distinction
between a slice and an fdisk partition.
4. You should allow the system to re-create the device tree. On the first
boot you need to at least perform a reconfiguration boot.
5. Does the boot environment have any dependancies on anything on the
network, any specific hardware in the system, sound cards, graphic cards,
etc. You might think this is a simple answer, but when Sun says "You can
move the disk to another system and it will boot" it means ANYBODY with ANY
configuration can do it. Thus they will not lightly make such a promise.
6. OS versions and hardware are sometimes interlinked. A specific OS
version may not boot on older hardware, and most newer hardware require
new-ish versions of the OS to load. For you this may sound like a non-issue
when all your systems are similarly configured, but again Sun would rather
let you run the installer (eg with flar) than make a promise.
>
> I also asked about the comprehensive BE ('is it?'), when suggesting that -
> if it was comprehensive - ought to be bootable (e.g. VirtualBox). The
> answer, again, was a tad off-topic: 'boot from grub'!
> Also, with respect to liveupgrade, I do understand lucreate, as to write
> the current '/' to another slice. But I am told, you can't simply boot that.
> My question: why would that be?
I think with comprehensive you mean complete. What I understand from the man
page and my own recent experience is that lucreate does not blindly copy
everything to the target environment. You would have to dig into the LU
scripts executed at reboot time to see what exactly else is needed to make a
system bootable.
My understanding lucreate+luactivate is enough to build a bootable
environment, except for the sync-ing of a few files. These files are synced
when the new BE is booted - the start-up scripts in the new BE will go try
to find the files to sync from in the old BE and copy them over.
I have moved my system from one hard drive to another folowing these steps:
zpool create -f NEWPOOL c0d0s0
lucreate -p NEWPOOL -n newBEname
luactivate -n newBEname
init 6
In this situation, after completion, the new disk has got no dependancies on
the old disk - it can be moved to another system and booted there, but some
data are not automatically brought over by lucreate - in particular the
so-called non-critical (shareable) file systems such as /export will he used
from the source data.
So basically live-upgrade intentionally creates dependancies on the old BE
in the new BE - this is part of its design and intended way of use. LU is
not intended as a tool for "duplicating" systems for quick instalation. Sun
does include free tools for that purpose with Solaris - in particular
jumpstart and flar files.
> Then one can liveupgrade, fine, and then it is done? No, it seems:
> luactivate is needed. I'd understand, that some metadata need to be
> adjusted, like mounts and grub. is it bootable, then? No, I am told, one
> definitively needs some init 6. I still don't know why. I would like to
> understand this. I can do
When rebooting with init 6, certain additional scripts run during shut
down. One of these sets the "default" entry in the grub menu. check the
output from bootadm list-menu before rebooting.
> that with Open
[osol-discuss] I want to understand 'Boot Environment'!
This is not so much a question of a specific problem, than one of concepts and
limitations.
If you look at the various posts of mine in here, I asked at different times on
essentially the same topic: What constitutes a Boot Environment; in the meaning
of 'how complete is it', can it be transferred?'. One of my questions was, why
can I not transfer a full slice to another machine? The answers given were not
fully on-topic, like 'use flash archive'.
I also asked about the comprehensive BE ('is it?'), when suggesting that - if
it was comprehensive - ought to be bootable (e.g. VirtualBox). The answer,
again, was a tad off-topic: 'boot from grub'!
Also, with respect to liveupgrade, I do understand lucreate, as to write the
current '/' to another slice. But I am told, you can't simply boot that. My
question: why would that be?
Then one can liveupgrade, fine, and then it is done? No, it seems: luactivate
is needed. I'd understand, that some metadata need to be adjusted, like mounts
and grub. is it bootable, then? No, I am told, one definitively needs some init
6. I still don't know why. I would like to understand this. I can do that with
OpenBSD and Linux (of course, minus the liveupgrade), but as system admin I
find it most suitable that partitions can be moved, and booted to (no need
telling me slices are different, that arguments won't invalidate my question).
Or slices, on BSD. When I look at my mount:
/dev/dsk/c1d0s4 15G 8.5G 6.1G59%/
/dev/dsk/c1d0s7 42G36G 5.5G87%/export/home
I have two slices that I use. Why would those not be straightforward mountable
(like from grub menu?). If I lucreate /dev/dsk/c1d0s5, why not that one? I
could understand if it was done on purpose, to avoid illegal cloning. But as of
now, it seems SUN moves to FOSS. Nothing better and easier than allowing the
creation of a BE, for whatever purpose, eventually backup, and then copying all
data, and - voilà - , there it is, readily bootable. Even in a VM. After a
luupgrade, no need to shut down, all the init 6 - hassle that tends tends to
fail here and there (luckily not only with me), requiring arcane action; but
rather just starting a VirtualBox, and see it coming up or not (without the
/export/home).
I am asking also on the grounds, that to my understanding, a fully
self-contained BE after lucreate or luupgrade would very much increase the
attractiveness of OpenSolaris. It would simplify testing of an upgrade, just as
deployment (at least on a bunch of identical hardware, like in a students'
lab). No, please, don't tell me 'flash archive is much better'. That may be the
case, but as of now, we have procedures in place to dump/restore full
partitions and slices, and I am still curious why a Solaris slice doesn't seem
to like the handling as a slice as a fully self-contained (boot-)entity.
Thanks,
Uwe
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
Thanks Dennis! =) This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] dual display
> I run a Toshiba LT with an external HP w2207 monitor. > Opensolaris see the monitor but does not extend the > desktop to it. Just duplicates it. > > What do I need to configure to get it to use the > monitor in extended format? /etc/xorg.conf: Section "ServerFlags" Option "Xinerama" "true" EndSection This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Blastwave.org
> There were enough problems with how the stuff from > blastwave/csw was packaged to make it distasteful to > use, this simply puts the last nail in the coffin. > For the most part I build everything from the source, > for those that I don't really want to take the time > to build I'll go to www.sunfreeware.com Heh! Although CSW packages were not perfect (i.e. never fully System V compliant), going from CSW to Sunfreeware is like going from riding a horse to riding a donkey. I suppose that if one goes in with the mindset of "I'll just run make; make install", one wouldn't care about how badly Sunfreeware stuff is packaged (no dependencies, /usr/local), otherwise, that stuff should never even see the light of day, let alone ever be installed on a production system. Anybody with an insane idea of still "packaging" stuff into /usr/local and not declaring dependencies obviously doesn't fully understand what they are doing. With that written, best of luck with Sunfreeware! This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] df doesn't work well with chroot, how to resolve it.
Hi,
wan_jm wrote:
> the problem is the follow command gives the error message . but the command
> works well in solaris9. Is it a bug ?
> bash-3.00# chroot /secroot /usr/sbin/df -b /
> df: cannot statvfs /secroot: No such file or directory
>
> what should I do.
>
> part result of "truss chroot /secroot /usr/sbin/df -b /" is following:
> resolvepath("/", "/", 1024) = 1
> statvfs64("/secroot", 0xFFBFFCF8) Err#2 ENOENT
> fstat64(2, 0xFFBFE958) = 0
> df: cannot statvfs /secroot: No such file or directorywrite(2, " d f : c a
> n n o t s".., 54)= 54
>
> write(2, "\n", 1) = 1
I suspect this will work if you loopback mount etc/mnttab within your chroot
environment, along the lines of mount -F lofs /etc/mnttab /secroot/etc/mnttab;
I used to look after a number of chroot build environments in which we
performed that trick so that df etc would report correctly.
Unfortunately this makes the chroot area less secure an insular
as it exposes external knowledge within the chroot; it
also upsets some utilities which attempt to canonicalize a pathname
since they can now see the true path to their root directory,
and they land up prepending /secroot or whatever to some
paths.
Cheers
Gavin
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] why should i have to modify the /etc/nsswittch.conf file?
On Sun, Aug 10, 2008 at 8:40 AM, Kaw Ay <[EMAIL PROTECTED]> wrote: > > i then editted /etc/nsswitch.conf and modified the following line: > hosts: files > to this: > hosts: files dns > > after this i could browse to google.com in firefox and resolve it via a > host lookup > > > what i dont understand is: > why should i have to modify the /etc/nsswittch.conf file? > basically: /etc/resolv.conf configures the DNS client. /etc/nsswitch.cong configured the name resolutions services TO USE THE DNS client. nslookup uses DNS (and thus /etc/resolv.conf) automatically. Most other services (ping, getent, telnet) uses the generic name lookup services (as they should), which then when correctly configured, will redirect the name lookup entry to DNS. -- Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke Afrikaanse Stap Website: http://www.bloukous.co.za My blog: http://initialprogramload.blogspot.com ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
