Openserver 5.0.6 newbie help
Bus Driver
any windowing, so I left out the X11 stuff on the skunkware.
I have had some luck compiling some programs, but others all seem to fail in
the same place. While the ./configure script runs fine, the programs fail to
build and usually seem to give errors related to 'ld' stuff. (libraries?)
I have 3 questions:
1. What can I do so that when I am compiling, the environment has all the
necessary information? - presuming this is a library issue.....
2. If I re-install, could/would it be advisable to use a symlink for the
following:
Instead of having '/usr/lib' and '/usr/local/lib', could I just use /usr/lib
and create a symlink for this:
# ln -s /usr/local/lib /usr/lib
..then any libs that get installed, would all end up in the same
directory......
Lastly,
3. I am seeing a good amount of 'getty' processess running and I am only
currently licensed for 5 users.
is this an issue or is there a way to get rid of some of these processes?
Please excuse my obvious ignorance here....as I am still and will be for a
long time..learning.
Jeff
Serge Bromow
news:JqAz7.531704$Lw3.32...@news2.aus1.giganews.com...
> I have installed 'enterprise' version and the skunkware cd. I am not using
> any windowing, so I left out the X11 stuff on the skunkware.
OSR5X I guess. Add the X-Stuff. A lot of usefull and cool
utilities in the packages.
> I have had some luck compiling some programs, but others all seem to fail in
> the same place. While the ./configure script runs fine, the programs fail to
> build and usually seem to give errors related to 'ld' stuff. (libraries?)
Please include the output of the compile. These are usually simple
problems to resolve.
> I have 3 questions:
>
> 1. What can I do so that when I am compiling, the environment has all the
> necessary information? - presuming this is a library issue.....
See above or attach the configure file. xmkmf is pretty good at
reading your environment.
> 2. If I re-install, could/would it be advisable to use a symlink for the
> following:
>
> Instead of having '/usr/lib' and '/usr/local/lib', could I just use /usr/lib
> and create a symlink for this:
>
> # ln -s /usr/local/lib /usr/lib
You could, but the command format would be the reverse
(assumming /usr/lib is the source dir). ln -s /usr/lib /usr/local/lib
Since you installed apps from Skunky, software verifies may report
false errors. If you are having link problems, it is more prudent to
add -L/usr/local/lib to your compile line.
>
> ..then any libs that get installed, would all end up in the same
> directory......
True. But there are issues with Symbolic Links covered in
previous posts.
> Lastly,
>
> 3. I am seeing a good amount of 'getty' processess running and I am only
> currently licensed for 5 users.
Assuming (bad idea on my part) you are the only user of the system. The
getty's running are for the console multi-screens F1-F12. These do
not affect license count. They are considered as one.
> is this an issue or is there a way to get rid of some of these processes?
If you feel the need to close down some gettys, you can use
disable ttyXX where xx = 02-12.
DO NOT DISABLE TTY01. There is no real savings in doing so. The
gettys do not affect licensing and the getty process is a very small
program and efficiently written.
> Please excuse my obvious ignorance here....as I am still and will be for a
> long time..learning.
No need. This learning stuff seems to be an ongoing process.
Another 40 years (I hope) and I will be done.
> Jeff
I thought your name was Bus?
Good Luck
Serge
--
Posted from port-4.ottawa4.achilles.net [209.151.2.103]
via Mailgate.ORG Server - http://www.Mailgate.ORG
Jean-Pierre Radley
| I have installed 'enterprise' version and the skunkware cd. I am not using
| any windowing, so I left out the X11 stuff on the skunkware.
|
| I have had some luck compiling some programs, but others all seem to fail in
| the same place. While the ./configure script runs fine, the programs fail to
| build and usually seem to give errors related to 'ld' stuff. (libraries?)
Stop paraphrasing, stop using the word "sweem', be precise.
HICH program fails, and with WHICH error?
| I have 3 questions:
|
| 1. What can I do so that when I am compiling, the environment has all the
| necessary information? - presuming this is a library issue.....
Put whatever you want into the environment, but you haven't given us a
clue what's possibly missing.
| 2. If I re-install, could/would it be advisable to use a symlink for the
| following:
|
| Instead of having '/usr/lib' and '/usr/local/lib', could I just use /usr/lib
| and create a symlink for this:
|
| # ln -s /usr/local/lib /usr/lib
|
| ..then any libs that get installed, would all end up in the same
| directory......
Absolutely not. Don't do this. There's no reason.
|
| Lastly,
|
| 3. I am seeing a good amount of 'getty' processess running and I am only
| currently licensed for 5 users.
|
| is this an issue or is there a way to get rid of some of these processes?
Define "good amount". On which ttys is getty running? And so what?
You're licensed for 5 logins, which doesn't prevent you from having 50
gettys, if you had fifty ports.
| Please excuse my obvious ignorance here....as I am still and will be for a
| long time..learning.
Excuses not required -- just keep asking, but once again, be more
precise. An, for no additional cost, try to keep to one topic per
posting. That is, don't ask about logins in the same message as you ask
about compilations. Makes for more focused threads.
--
JP
Bus Driver
each post to a specific topic.
My name is "Jeff", but I post with screwy names and email, as I get ENOUGH
spam as it is!
I wanted to ask about install.
I am presuming that 5.0.6 no longer has the 8GB barrier limit?
Well, when I setup SCO on a 20GB drive, I use the following partitions:
/root = 10GB
/swap = 2GB
/stand = 100MB
/u= 7GB
Install runs fine, yet dfspace or df -B, shows an incorrect value. It shows
/u as 13GB and /root as 6GB.
<?> - I am quite familiar with Solaris and seem to have the install of both
OS's under my knowledge....is this a known bug??
I dont know what I am missing here...Next, I will try a "use full disk for
UNIX" install.
TIA.
Jeff
"Serge Bromow" <se...@omensys.com> wrote in message
news:b9f3f0e22766d12abc1...@mygate.mailgate.org...
John DuBois
Bus Driver <dri...@school.bus> wrote:
>Well, when I setup SCO on a 20GB drive, I use the following partitions:
>
>/root = 10GB
>/swap = 2GB
>/stand = 100MB
>/u= 7GB
>
>Install runs fine, yet dfspace or df -B, shows an incorrect value. It shows
>/u as 13GB and /root as 6GB.
Always include literal output if possible, rather than simply describing it.
In this case, only the df output is of interest, since dfspace just reformats
it.
John
--
John DuBois spc...@armory.com. KC6QKZ/AE http://www.armory.com./~spcecdt/
Ronald J Marchand
news:3bd4acf2$0$331$8ee...@newsreader.tycho.net...
> In article <tt99oun...@corp.supernews.com>,
> Bus Driver <dri...@school.bus> wrote:
> >Well, when I setup SCO on a 20GB drive, I use the following partitions:
> >
> >/root = 10GB
> >/swap = 2GB
> >/stand = 100MB
> >/u= 7GB
> >
> >Install runs fine, yet dfspace or df -B, shows an incorrect value. It
shows
> >/u as 13GB and /root as 6GB.
>
> Always include literal output if possible, rather than simply describing
it.
> In this case, only the df output is of interest, since dfspace just
reformats
> it.
And df -B is reporting 512K blocks .....
Ron
Bus Driver
root/stand/swap and all seems fine now!
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/root 17828465 1340573 16487892 8% /
/dev/boot 51200 9011 42189 18% /stand
$ dfspace
/ : Disk space: 16101.45 MB of 17410.61 MB available (92.48%).
/stand : Disk space: 41.20 MB of 49.99 MB available (82.40%).
Total Disk Space: 16142.65 MB of 17460.61 MB available (92.45%).
..I just dont understand why it wont work with 'custom' mount points. But
this is fine I guess.
"Ronald J Marchand" <roj...@telocity.com> wrote in message
news:c62B7.392$Qz.2...@newsrump.sjc.telocity.net...
Tom Parsons
| First off, thank you VERY much for all the comments. I will try and keep
| each post to a specific topic.
|
| My name is "Jeff", but I post with screwy names and email, as I get ENOUGH
| spam as it is!
|
| I wanted to ask about install.
|
| I am presuming that 5.0.6 no longer has the 8GB barrier limit?
|
| Well, when I setup SCO on a 20GB drive, I use the following partitions:
No, you did not. You created 1 partition with several divisions within
the partition. With OpenServer, you can have 4 partitions on a disk drive
and within each partition, 7 divisions. Divisions in the non-root
partition can be used as regular filesystems but I don't think it possible
to split stand and root across partitions.
| /root = 10GB
Much too big. 1.2 - 1.5 gig is more than adequate. Put non-distribution
files in other divisions.
| /swap = 2GB
How much memory do you have? That's way too much swap unless you are
running a development environment with more than a gig of memory AND
really do want to analyze core dumps.
| /stand = 100MB
Another waste of disk space. Unless you are mucking around where you
don't belong, /stand will not never get close to 20 meg.
| Install runs fine, yet dfspace or df -B, shows an incorrect value. It shows
| /u as 13GB and /root as 6GB.
Did you try to resize these divisions without unloading and reloading
the OS?
| I dont know what I am missing here...Next, I will try a "use full disk for
| UNIX" install.
Which will give you a 20 meg /stand, suggest a reasonable size for swap
and let you decide how to divide the remaining space between root and
a /u filesystem. The ISL actually asks you for the size of the /u
filesystem and uses the remainder for the root division.
--
==========================================================================
Tom Parsons t...@tegan.com
==========================================================================
Bill Vermillion
Bus Driver <dri...@school.bus> wrote:
>Thanx guys for the reply...I re-installed and used NO mounts but
>root/stand/swap and all seems fine now!
>Filesystem 1024-blocks Used Available Capacity Mounted on
>/dev/root 17828465 1340573 16487892 8% /
>/dev/boot 51200 9011 42189 18% /stand
>$ dfspace
>/ : Disk space: 16101.45 MB of 17410.61 MB available (92.48%).
>/stand : Disk space: 41.20 MB of 49.99 MB available (82.40%).
>Total Disk Space: 16142.65 MB of 17460.61 MB available (92.45%).
>
>..I just dont understand why it wont work with 'custom' mount points. But
>this is fine I guess.
It will be find >until< you have to upgrade, or have some OS
problems, or even a crash.
I've found that in system crash environment about the only system
that gets hit is the /
With a drive that large I'd not put more than 1GB on /. That
way any time you have to do maintenance or kernel rebuilds, etc.,
you can unmount all except the OS, perform a backup on that
partition, and if it goes totally awry - it will someday - you can
just remake the / and re-install that from your BackupEdge or
LoneTar recovery disks. I typicaly run no more than about
500-600MB for the OS.
That means the backup takes about 5+ minutes for the OS.
I have had problems where SW updates or vendor supplied
updates/drivers have made things unbootable - but the worst part
was some of them left things on the drive that should have been
removed when the install failed.
Just some advice from someone who fought a system for a full
weekend having to reinstall part of the OS after every failed
driver update. It was a bad script on the driver install package
that removed some needed parts of the OS along with its own pieces.
--
Bill Vermillion - bv @ wjv . com
John DuBois
Bus Driver <dri...@school.bus> wrote:
>..I just dont understand why it wont work with 'custom' mount points.
Custom disk layout should work just fine. If you try again, be sure to record
exactly what you do, so we can tell you what you did wrong if it fails again :)
Tony Lawrence
>
> In article <tt9epk5...@corp.supernews.com>,
> Bus Driver <dri...@school.bus> wrote:
> >..I just dont understand why it wont work with 'custom' mount points.
>
> Custom disk layout should work just fine.
Unless, of course, he tries to make mounts for /usr ..
--
Tony Lawrence
SCO/Linux Support Tips, How-To's, Tests and more: http://pcunix.com
Bus Driver
/u
/home
/junk
/xtra
simple stuff. I learned the hard way NOT to use /usr .......as a mount
point.
I am simply frustrated to the point where I think I will throw the towell in
on SCO. I truly appreciate all the assistance I was given from the group..I
want to thank you!
I am a solaris man true and true and I think thats where i will go hang out.
It was only an exercise in seeing an different OS....nothing business
related at least.
At work, we run Solaris......
thanx again guys!
Jeff
"Tony Lawrence" <to...@pcunix.com> wrote in message
news:3BD5E9C8...@pcunix.com...
Bus Driver
perhaps if I explain what it is I am trying to do with SCO, someone out here
might be able to kindly offer me some tips. I dont need hand holding, but a
little guidence would be helpful.
I am going to install SCO OServer 5.0.6 and have a 15user license.
I plan on running the following on this machine:
Squid - with a 1GB cache dir.
Sendmail
pop3/imap
Apache
Bind
SSH2
(along with a few other small apps)
With that in mind, I have a single 20GB IDE drive and 512MB ram.
I have read and re-read the tips you all gave me on partitions and need more
advice.
(Since I am from the Solaris world...this is different)
Usually I would make a mount point like '/usr,/var,/cache' and so on. I have
found that this is not good under SCO !
What is the most usefull way to setup the hard drive during CDROM
install? -I choose 'custom' for the hard disk setup and the install program
does see the whole 20GB drive (19,804 or so).
Since I am use to a 'var' partition for mail....I dont know what my options
are.
I will follow any advice and re-attempt install. However, if and when the OS
eventually reports incorrect 'dfspace' like it did before, I will post all
the revelant information.
Thanks in advance!
Ronald J Marchand
> After giving this more thought (and my friends insisting I get this to
work)
> perhaps if I explain what it is I am trying to do with SCO, someone out
here
> might be able to kindly offer me some tips. I dont need hand holding, but
a
> little guidence would be helpful.
>
> I am going to install SCO OServer 5.0.6 and have a 15user license.
>
> I plan on running the following on this machine:
>
> Squid - with a 1GB cache dir.
> Sendmail
> pop3/imap
> Apache
> Bind
> SSH2
> (along with a few other small apps)
>
> With that in mind, I have a single 20GB IDE drive and 512MB ram.
>
> I have read and re-read the tips you all gave me on partitions and need
more
> advice.
> (Since I am from the Solaris world...this is different)
>
> Usually I would make a mount point like '/usr,/var,/cache' and so on. I
have
> found that this is not good under SCO !
The directories to which you refer are created by the installation process
and are part of the root filesystem. divvy is used to create mountable
filesystems for application programs and data, and can be called whatever
suits you. The mount point for a CR-Rom is created after the installation.
Hope this helps.
Ron
Tony Lawrence
> What is the most usefull way to setup the hard drive during CDROM
> install? -I choose 'custom' for the hard disk setup and the install program
> does see the whole 20GB drive (19,804 or so).
>
> Since I am use to a 'var' partition for mail....I dont know what my options
> are.
I'd suggest reading http://pcunix.com/Unixart/filesystems.html
I'm sure you already know most of what is discussed there, but some of
it may be new to you or may help unfog your head as to where to start.
I might also suggest that you start with a default install- just root,
stand and swap- examine how sco lays stuff out, install some Skunkware
stuff and note how and where that goes (noting the symlink mess), and
then you'll have a better idea of how your planned installation is going
to look. Then reinstall with your new understanding.
One thing NOT to forget- a lot of advice suggests leaving root fairly
small. That's OK in and of itself, but keep in mind that on OSR5, /tmp
is NOT a separate filesystem by default, and many things make heavy use
of /tmp for (duh!) temporary files. I've had numrerous "incidents" of
mysterious failures on Linux systems from exactly this, and I've seen it
a handful of times on SCO systems that I didn't install. Given the
current cost of diskspace, I routinely give 2-4GB for root- it's massive
overkill, but I then have one less thing I have to worry about- even my
home Linux box has a 2GB root and is typically only about 40% used-
which is fine by me; cheap insurance.
Bus Driver
--
Tony Lawrence
SCO/Linux Support Tips, How-To's, Tests and more: http://pcunix.com
Tony- THANK you very much for replying. I wanted to kindly ask a few
things...
1. I did order 2 SCO books from Amazon.com and expect them any day now :-)
2. I do understand file layouts for the most part.....but
In installing SCO 5.0.6, I dont want / to be more than 2GB. But I am use to
a 'var' partition of 4GB or so to handle email and stuff. What are my
options there? One partiton, but different slices within..
I have installed SCO (over 15 times - sigh ) and installed the SKUNKWARE
2000 as well. I have an understanding how the goofy symlinks work. I have
(during one of the install attempts) setup a symlink so that all the stuff
got installed onto a /u slice I created. This worked well...but I have had
the most luck just using / for everything.
The most frustrating install comes when I specify a specifc slice size and
'df' reports it WAY different than I setup. For example - I told 'customise'
to set /home and /u1 for 6GB each. After install, df reported /home just
fine, but /u1 as 19.68GB! - almost like I tried to create a slice on the 'c'
partition under xBSD or Solaris......this was and still is my MOST serious
issue. If I can get past the partitioning and have it report correctly, most
of the other issues I face are compile errors.
Jeff
Bill Vermillion
Tony Lawrence <to...@pcunix.com> wrote:
>One thing NOT to forget- a lot of advice suggests leaving root
>fairly small. That's OK in and of itself, but keep in mind that
>on OSR5, /tmp is NOT a separate filesystem by default, and many
>things make heavy use of /tmp for (duh!) temporary files. I've had
>numrerous "incidents" of mysterious failures on Linux systems from
>exactly this, and I've seen it a handful of times on SCO systems
>that I didn't install.
You can always make /tmp a separate file systems, or in cases where
/tmp is too small, I've just symlinks to a directory much larger
until the system can be reinstalled/reimplemented properly.
I've seen many incidients on Linux systems - most were caused by
people who came from an DOS world and believed all the hype in the
PC mags and plunged on ahead using their old ways - instead of
unlearning the wrong ways and learning the right ones.
>Given the current cost of diskspace, I routinely give 2-4GB for
>root- it's massive overkill, but I then have one less thing I
>have to worry about- even my home Linux box has a 2GB root and
>is typically only about 40% used- which is fine by me; cheap
>insurance.
I still prefer smaller than that, and on multidrive systems I put
the second part of the boot/root device as another file syste,
workspace, etc., and keep the really big file systems on really big
secondary drives.
>
>--
>Tony Lawrence
>SCO/Linux Support Tips, How-To's, Tests and more: http://pcunix.com
John DuBois
Bus Driver <dri...@school.bus> wrote:
>Bus Driver wrote:
>In installing SCO 5.0.6, I dont want / to be more than 2GB. But I am use to
>a 'var' partition of 4GB or so to handle email and stuff. What are my
>options there? One partiton, but different slices within..
Anything you do in this regard will have to be done manually, and post-install.
For example, I might make a 'spool' division, install, mount the spool division
on a temporary mount point (like /mnt), copy everything in /usr/spool over to
it, move /usr/spool aside (e.g. to /usr/spool-), create a new /usr/spool mount
point, mount the spool division on it, verify that everything works properly,
remove the /usr/spool- hierarchy, and then make sure there's an appropriate
entry for spool in /etc/default/filesys. Be careful not to move anything off
of the root filesystem that will be needed in order to boot & get to
single-user mode.
>The most frustrating install comes when I specify a specifc slice size and
>'df' reports it WAY different than I setup. For example - I told 'customise'
>to set /home and /u1 for 6GB each. After install, df reported /home just
>fine, but /u1 as 19.68GB! - almost like I tried to create a slice on the 'c'
>partition under xBSD or Solaris......this was and still is my MOST serious
>issue.
Something went wrong in your case, and it's unusual enough that we won't know
what unless it happens again and you post the full details.