Linux-Setup Digest #173, Volume #21 Sun, 6 May 01 05:13:07 EDT
Contents:
Re: File System going bad (Scott)
Please Help (Xterm problems with RedHat Linux 6.2) (Cupid)
Soundblaster 16 PCI setup (Scott)
Re: Soundblaster 16 PCI setup (Scott)
Loading modules (Scott)
Real Player configuration (Scott)
Installing windows and linux (Simon Lemieux)
Re: Redhat 7.1 + kde desktop (J Hayward)
Re: Redhat 7.1 + kde desktop (J Hayward)
Re: ipchains test with nmap and iptables logging (HateLinux)
Re: HOWTO setup a US Robotics/3Com 56K PCI FaxModem Model 5610/2977 (HateLinux)
Re: LILO 1024 cylinder limit (Silvio NT)
BINGO ! - THANKS ERIC !! ... ("Alex")
not enough RAM during RH 7.1 install ("Waldermar")
setup FTP server failed !! ("Eric Chow")
Re: LILLL? Prompt (Carl Peto)
Re: File System going bad (Floyd Davidson)
Re: Newbie - Just downloaded and compiled 2.0.38 but it reboots (Carl Peto)
----------------------------------------------------------------------------
From: Scott <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.help,comp.os.linux.misc,alt.linux.slakware
Subject: Re: File System going bad
Date: Sat, 05 May 2001 21:19:39 -0500
Naw, just got new memory, and am waiting to see what happens.
Took a power hit last night, and reboot's fsck gave me
'Deleted inode xxxx has zero dtime. FIXED'
Those are the kind of things that got accumulated before,
without hostile shutdowns.
We'll see..
John Hasler wrote:
>
> Scott writes:
> > Perhaps if I...turned up my thermostat?
>
> Your getting close. Get yourself a can of freeze-spray and a hair dryer,
> open up the case, and start heating and cooling various components.
> --
> John Hasler
> [EMAIL PROTECTED] (John Hasler)
> Dancing Horse Hill
> Elmwood, WI
------------------------------
From: Cupid <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To:
alt.os.linux,cz.comp.linux.redhat-cz,dc.org.linux-users,linux.news.groups,thenet.support.linux,alt.uu.comp.os.linux.questions,at.fido.linux,comp.os.linux.misc
Subject: Please Help (Xterm problems with RedHat Linux 6.2)
Date: Sat, 05 May 2001 22:37:03 -0400
I'm running Redhat Linux 6.2 Professional (with updated kernel) on a
System with:
Pentium 233 MMX
128 MB Ram
4 MB Video
60.5 GB HDD
When I try to load Xterm (Start Button -> Utilities -> Regular Xterm), I
get a message saying:
Warning: Cannot allocate colormap entry for "Wheat"
Warning: Cannot allocate colormap entry for "Orchid"
After the message, Xterm loads, but I don't see anything that I'm typing
in the window. I'm assuming that the foreground & background colors are
the same (black) since it cannot allocate the colormap for the correct
colors...
I've tried everything to resolve this problem. I've tried changing the
resolution, etc., but nothing helps. Been at this for weeks.
NOTE: I can use Color Xterm (from the Utilities Menu) or Terminal (from
the Toolbar), and they both work ok, except for Regular Xterm.
Please help.
------------------------------
From: Scott <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.networking,comp.os.linux.misc,comp.os.linux.help
Subject: Soundblaster 16 PCI setup
Date: Sat, 05 May 2001 21:41:26 -0500
Ok, I've been searching, and have gotten close with my SB 16 card.
Here are some questions I'm hoping someone can answer:
I rebuilt the kernel with ensoniq 1371 loaded. I DO get sound,
but it's kinda staticy
However, 'cat /dev/sndstat' gives me Device not found.
It was there when I had tried building the kernel with SB16 support.
But now it's not there...
Is this correct? Or does it mean something is wrong?
(this drove me crazy rebuilding, re-booting, over and over again,
thinking I didn't have sound, as it was my test. Then I
'cat sound.au >/dev/audio' and it WORKS!)
I'm also trying to figure out modules, but haven't gotten the
hang of it yet. See my other thread.
-Scott Weber
------------------------------
From: Scott <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.networking,comp.os.linux.misc,comp.os.linux.help
Subject: Re: Soundblaster 16 PCI setup
Date: Sat, 05 May 2001 21:42:55 -0500
DOH! I forgot to specify my version:
Linux 2.2.16, Slackware 7.1, on a P333
Scott wrote:
>
> Ok, I've been searching, and have gotten close with my SB 16 card.
>
> Here are some questions I'm hoping someone can answer:
>
> I rebuilt the kernel with ensoniq 1371 loaded. I DO get sound,
> but it's kinda staticy
>
> However, 'cat /dev/sndstat' gives me Device not found.
> It was there when I had tried building the kernel with SB16 support.
> But now it's not there...
> Is this correct? Or does it mean something is wrong?
> (this drove me crazy rebuilding, re-booting, over and over again,
> thinking I didn't have sound, as it was my test. Then I
> 'cat sound.au >/dev/audio' and it WORKS!)
>
> I'm also trying to figure out modules, but haven't gotten the
> hang of it yet. See my other thread.
>
> -Scott Weber
------------------------------
From: Scott <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.networking,comp.os.linux.misc,comp.os.linux.help
Subject: Loading modules
Date: Sat, 05 May 2001 21:52:24 -0500
Using Slackware 7.1, kernel 2.2.16:
When I rebuilt the kernel with drivers as modules, they didn't load.
I'm trying to trace the boot flow to see how they are loaded, and
can't quite figure it out. It looks like it's called from rc.S.
I added modules to /etc/rc.d/modules.rc but that didn't seem to do it.
Can anyone explain this, or point me to something besides the howto?
When I do a kernel rebuild, and 'make modules' the modules
are compiled, but not moved to /lib/modules/2.2.16/...
Do I have to move them manually?
'make bzlilo' installs the kernel for me, am I just too spoiled by this?
As an example, I added sound support to my kernel. Was it even
nessesary to rebuild? Could I have just loaded sound.o and
es1371.o? I couldn't figure out where to get those to load.
(lsmod didn't show them as loaded)
kerneld is specified as needed to load and unload modules. But
the only place it appears is in rc.modules, and it's commented
out.
I'm a little lost on modules. If I knew at least one place to
start, I could slowly start to learn this. But none of the
stuff I can find starts out that simple. It all seems to assume
a lot further understanding than where I'm starting from.
Thanks for any help.
-Scott Weber
------------------------------
From: Scott <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.misc,comp.os.linux.networking,comp.os.linux.help
Subject: Real Player configuration
Date: Sat, 05 May 2001 21:59:52 -0500
I've got Slackware 7.12, 2.2.16, and SB PCI 16 card.
It's all working. I believe it's good enough.
Real Player 8 had trouble playing as anyone but root. I
chmod 666 the audio, mixer, dsp, sound, etc... Now it plays
as the regular user.
But, then I had to set it to http ONLY for all the protocols.
Why?
I tried running the autoconfig feature in it's preferences, and
it fails, saying it can't contact a server.
But I can browser the whole world with netscape just fine.
I've run real player on my MS Windows box behind the same firewall.
It's definitely NOT a network issue, or an issue with networking
on this specific linux box.
It's working for now, using HTTP, but I'd prefer to have it
running correctly.
Can anyone give me any ideas about this? Any help is
appreciated.
-Scott Weber
------------------------------
From: Simon Lemieux <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Installing windows and linux
Date: Sun, 06 May 2001 03:20:10 GMT
Hi,
I will need, in a near future, to compile for the Windows platform. I've
decided since I'm going to reinstall my distribution anyway to arrange the
partitions on my HD. I have 2 hard disks, one for the system and windows and
the other will hold my /home and /usr/local for linux... The second HD (hdc)
should be left untouched by Windows and it should only be installed on the first
partition of my hda.
Here is what I'm probably going to do:
Abstract from fdisk /*
Command (m for help): p
Disk /dev/hda: 255 heads, 63 sectors, 784 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 262 2104483+ b Win95 FAT32
/dev/hda2 263 328 530145 82 Linux swap
/dev/hda3 329 784 3662820 83 Linux
Command (m for help): v
62 unallocated sectors
Command (m for help):
*/
hda1 is my Windows partition of 2G (2048M). I think I need it to be bootable,
but I'm unsure if it's necessary. Also unsure about the kind of partition to
make FAT32 vs FAT16? LBA? What to do?
hda2 is my Swap partition of 512M (I know it's big, but I like it this way...)
hda3 is my main linux partition will hold all that is not my personnal files and
is about (6.4G - 2.5G = 3.9G), which is more than enough... Maybe I should push
this windows partion a gig higher... anyway, those things are details...
I'm just looking to know if this will work for the installation? I'm planning
on reseting the partition map, reboot, install windows, reboot, install Redhat
7.1 and then settle down for awhile... What do you think of this? Will windows
delete my partition table (as it often did when I tried before...)?
Thanks for any suggestion, help, hint!
Simon
--
+--------------------------------+---------------------------+
| Simon Lemieux | http://666Mhz.myip.org/ |
| Email : [EMAIL PROTECTED] | Povray and OpenGL Gallery |
+--------------------------------+---------------------------+
------------------------------
From: J Hayward <[EMAIL PROTECTED]>
Subject: Re: Redhat 7.1 + kde desktop
Date: Sat, 5 May 2001 20:25:46 -0700
Hello,
Download these fonts and new XftConfig
http://keithp.com/~keithp/fonts/truetype.tar.gz
http://keithp.com/~keithp/fonts/XftConfig
Unzip the fonts in usr/X11R6/lib/X11/fonts
Backup your old XftConfig in /etx/X11
Unzip the new XftConfig in /etx/X11
Add this path to the new XftConfig: dir "/usr/X11R6/lib/X11/fonts/truetype"
Under "look & feel" "style" enable anti-aliased fonts.
Restart KDE. Then set your fonts in "look & feel" "fonts".
I'm using Verdana looks the best to me. The default KDE fonts will not look
good with anti-aliasing enabled.
You can use these fonts without using anti-aliasing, but it looks great :-).
You can also add XftConfig to your home directory if you want it just for
one user, but rename it "xftconfig".
Regards,
Jim H
John Smith wrote:
> Under "look & feel" there are only ~ 5 fonts listed as options to be used
> within KDE. How can I include extra fonts ? I hate the standard fonts >:|
>
> Thanks,
> J
>
>
------------------------------
From: J Hayward <[EMAIL PROTECTED]>
Subject: Re: Redhat 7.1 + kde desktop
Date: Sat, 5 May 2001 20:28:24 -0700
oops, typo. that should be:
>
> Backup your old XftConfig in /etc/X11
> Unzip the new XftConfig in /etc/X11
Regards,
Jim H
------------------------------
From: 2b@home (HateLinux)
Crossposted-To: comp.os.linux.security
Subject: Re: ipchains test with nmap and iptables logging
Date: Fri, 04 May 2001 15:47:24 GMT
On Mon, 30 Apr 2001 04:22:01 GMT, Manfred Bartz <[EMAIL PROTECTED]>
>Try <http://scan.sygatetech.com/>
Just what I needed. Fast, without all the burocracy of the
other testers. My firewall came out fine.
>Or you can ask a friend to scan you from the outside.
>If you want me to run a nmap scan send me an email with the details.
We live in different time zones. Not practical. Thanks for the
offer.
>
>> BTW, nice site you have....
>
>Thanks. :)
Deserved.
------------------------------
From: 2b@home (HateLinux)
Subject: Re: HOWTO setup a US Robotics/3Com 56K PCI FaxModem Model 5610/2977
Date: Fri, 04 May 2001 15:47:19 GMT
On Wed, 25 Apr 2001 17:29:51 -0700, Norman de Groot <[EMAIL PROTECTED]>
wrote:>--------------------->snip
>> setserial /dev/ttyS1 port 0x0d400 irq 11 uart 16550A
>> where:
>--------------------->snip
>
>Thanks for your simple, straightforward instructions concerning Linux
>setup of a Robotics 5610 internal hardware modem. . My problem was
>trying to relate Windows 2000 information about the modem port, address,
>and IRQ with the similar information in Linux. Windows claims the
>modem is on COM 3, uses IRQ 9, and is at 0xdfe0. In Linux, cat
>/proc/pci reports that the modem is at the same address but IRQ 3. I
>also did not realize that I was free to use any unoccupied COM port
>rather than having to repeat the Windows COM 3 assignment. I ended up
>with ttyS1, port 0xdfe0, IRQ 3. It works.
>
>The "Modem busy" error message that Linux provides when the port and
>adress and IRQ are not set correctly is worse than useless since it
>leads one to look elsewhere for the problem, e.g., perhaps a lock file
>or something else.
>
>Thanks again.
You are welcome
Sorry, did not see your reply. Well , if it helped at least
one person, it was worth posting.
Seeya
------------------------------
From: Silvio NT <[EMAIL PROTECTED]>
Crossposted-To:
alt.comp.linux,alt.os.linux.redhat,comp.os.linux.questions,comp.os.linux.redhat
Subject: Re: LILO 1024 cylinder limit
Date: Sun, 06 May 2001 00:45:35 -0300
Hello:
If you are using RedHat 7.0 or 7.1 you can boot in any part of the HDD
using the blbal option 'lba32' in the configuration file of LILO
(lilo.conf). In this case LILO must be in the MBR.
On Sat, 05 May 2001 19:18:18 GMT, "Robert Lafleur"
<[EMAIL PROTECTED]> wrote:
>I'm trying to install Red Hat Linux on a partition past the 1024 cylinder.
>From what I understand LILO must be installed either:
>
>1. In the first 1024 block of the HDD
>2. In the first ~8GB of the HDD if the BIOS can abstract disk sectors for
>LILO
>
>Is this correct? I'm trying to install LILO entirely within a partition
>beginning around the 13th GB. Am I going to have to create a small
>partition for /boot? I don't want to shift my partitions around with
>Partition Magic. Any comments are appreciated.
>
------------------------------
From: "Alex" <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,linux.redhat,linux.redhat.install,linux.redhat.misc
Subject: BINGO ! - THANKS ERIC !! ...
Date: Sun, 6 May 2001 17:08:48 +1000
Foremost, I apologize for the verbose subject above !!.... (and the
exclamation marks).
Eric... you're a legend !! ..... after many nights of frustrating re-install
the problem has now been solved ... thanks to your good observation of my
error message.
Yes, 0X0302 actually refers to hda2... and there lies all the problem.
Very simply, Lilo (under RH7.1) install made an assumed connectivity to the
"DOS/Win" evironment... I don't know how it selects the specific partition,
except that it does.
So, for those of us, who do not use the conventional DOS/Win startups... the
Lilo boot creation will terminate because it was unable to locate a bootable
partition under dos/win.
My solution was very simple, remove that reference under lilo.conf and then
linux boot was successfully installed on the 2nd HDD. Its little over
sight like this that makes one ... want to kick oneself !
Thank you all, who contributed in assisting me in the last week.
I suggest the rest of you still trying to resolve Linux Redhat 7.1 lilo
problems ...
run "lilo -v -v" and you'll soon see everthing that Lilo is doing. THANKS
Eric.
A New Linux convert ... :-)
"Eric" <[EMAIL PROTECTED]> wrote in message
news:9cueki$kcf$[EMAIL PROTECTED]...
> > Warning: /dev/hdb1 is not on the first disk.
> > Warning: device 0X0302 exceeds 1024 cylinder limit.
>
> Hmm.... I justs noticed now
> 0x0302 is hda2!
>
> Are you sure it says 0x0302??
>
> could you show your lilo.conf and the fdisk listing:
> `/sbin/fdisk -l /dev/hd[a-d]`
>
> > Fatal: geo_comp_addr cylinder number is too big 2028>1023
> >
> > Thanks Eric... I will try the lilo with the "-v -v" parameters.
> > What does that do ?
>
> It's just a verbosity switch (man lilo)
>
> > I certainly do agree with you that the 1024 is a bios limitation. My
> system
> > is brand new, and I'm using red hat 7.1... do you know if Lilo that
comes
> > with RH7.1 is not restricted by the 1024 cylinder boundary ?
>
> The lilo that ships with RH7.1 is definately new enough to support booting
> from beyond cylinder 1024. And as your PC is to, you don't have a real
> problem.
>
> > As you have advised, I can ignore the various warning messages...
> > how about the last line.. the fatal error .. 2028>1023....
>
> Errors you obviously cannot ignore.
>
> > seem like RH did not completely install but halted 99% to completion ?
>
> It's just lilo that's not installed.
> (Probably. I recently helped someone with a similar problem. Turned out he
> had been using a bad CD!)
>
> > Or has the install completed, and above three lines of warning and error
> can
> > be safely ignored... by doing the appropriate modification to the
> lilo.conf
> > file?
>
> You cannot ignore it, you can solve it.
> Boot from the floppy you created during install. (Or from the installation
> CD if
> you neglected to make that floppy)
>
> CD booting: at the liloprompt, enter "linux rescue root=/dev/hdXXXX"
> (without the quotes!) where hdXXXX should be replaced with your
> actual root partition.
>
> Eric
>
>
------------------------------
From: "Waldermar" <[EMAIL PROTECTED]>
Subject: not enough RAM during RH 7.1 install
Date: Sun, 06 May 2001 07:36:35 GMT
Hi,
I'm trying to set up RedHat 7.1 on a 486x16M machine.
Guess what - 7.1 wants more RAM (32???) and fails to install.
I know, memory is cheap, etc., but the question is can I make
it work with 16? Anyone bypassed it somehow?
Thanks for any info,
--V.
------------------------------
From: "Eric Chow" <[EMAIL PROTECTED]>
Subject: setup FTP server failed !!
Date: Sun, 6 May 2001 16:04:35 +0800
Hello,
I installed RedHat Linux 7.1, but when I tried to use ftp in other PC(which
in the same LAN). It always show "Login failed". The messages as following :
C:\>ftp 192.168.0.1
Connected to 192.168.0.1.
220 ns.ericjoey.com FTP server (Version wu-2.6.1-16) ready.
User (192.168.0.1:(none)): eric
331 Password required for eric.
Password:
530 Login incorrect.
Login failed.
ftp>
I don't know what caused this. When I use RedHat 6.2, I just installed
everything, and it can use as a FTP server. But in RedHat 7.1, it can't. Is
there any config to to that ? Would you please to teach me what should I do
?
Best regards,
Eric
------------------------------
From: Carl Peto <[EMAIL PROTECTED]>
Subject: Re: LILLL? Prompt
Date: Sun, 06 May 2001 08:22:58 GMT
Each of the letters L I L and O in the prompt represent one of the
phases of booting LILO having been completed thus you could see L- on
bootup or LI- or LIL- or LILO (and then it runs, hopefully). I've not
seen it repeat a letter before but it could conceivably be trying a step
repeatedly and failing repeatedly.
The documentation that comes with LILO is first class (classic British
saying, right! :-) ) and it makes a fascinating read. In my
distribution (an ancient 6 year old Slackware) it is under
/usr/lib/lilo. There's a README which is the plain text form of the
manual and a much more easily readable DVI file with the same contents
but a in a book format called user.dvi in the doc subdirectory (I use
xdvi to view it in XFree86).
Extract from my README on my old (probably much older than yours)
version of LILO...
"LI The first stage boot loader was able to load the second stage boot
loader, but has failed to execute it. This can either be caused by a
geometry mismatch or by moving /boot/boot.b without running the map
installer.
LIL The second stage boot loader has been started, but it can't
load
the descriptor table from the map file. This is typically caused by
a
media failure or by a geometry mismatch.
LIL? The second stage boot loader has been loaded at an incorrect
address. This is typically caused by a subtle geometry mismatch or
by
moving /boot/boot.b without running the map installer.
LIL- The descriptor table is corrupt. This can either be caused by
a
geometry mismatch or by moving /boot/map without running the map
installer.
LILO All parts of LILO have been successfully loaded."
Personally I used to keep getting LIL- and I had no idea why; re-running
lilo after booting from a rescue disk had no effect, often. I have my
distribution on /dev/hda4 and so one of the (previously) mysterious
lines in the setup created /etc/lilo.conf file was "boot=/dev/hda4". I
had thought that this meant "boot the /dev/hda4 partition" but it
actually meant "install LILO on the boot sector of the /dev/hda4
partition" the problem then being how the MBR (q.v.) itself boots LILO.
Unbeknownst to me I had installed LILO as a replacement MBR over the DOS
MBR at one time earlier as well as the installation I thought I was
dealing with on the boot sector of /dev/hda4. All became clear with the
pretty little diagrams of boot sectors, partition tables, partitions,
logical partitions, etc. in the documentation and it has worked like a
charm ever since!
Hope this helps, otherwise sorry to have wasted your time.
Regards,
Carl Peto
------------------------------
From: Floyd Davidson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.misc,alt.linux.slakware
Subject: Re: File System going bad
Date: 05 May 2001 23:50:56 -0800
Scott <[EMAIL PROTECTED]> wrote:
>Naw, just got new memory, and am waiting to see what happens.
>
>Took a power hit last night, and reboot's fsck gave me
>'Deleted inode xxxx has zero dtime. FIXED'
If that is the only kind of problem fsck is coming up with, then
you probably don't really have a problem.
What kernel are you using and what version of e2fsck and mke2fs
are you using?
>Those are the kind of things that got accumulated before,
>without hostile shutdowns.
>
>We'll see..
>
--
Floyd L. Davidson <http://www.ptialaska.net/~floyd>
Ukpeagvik (Barrow, Alaska) [EMAIL PROTECTED]
------------------------------
From: Carl Peto <[EMAIL PROTECTED]>
Crossposted-To: alt.linux
Subject: Re: Newbie - Just downloaded and compiled 2.0.38 but it reboots
Date: Sun, 06 May 2001 08:53:10 GMT
==============A82B06B49A77CC345F3174E5
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Oops. RTFM eh? :-) Thanks for your help so far, I don't know if you
could elaborate a bit further?
As I understand it the Changes document in the Documentation
subdirectory of the 2.0.38 distribution I've unpacked says that I
need...
"Current Releases (the latest necessary for basic functionality, not
necessarily the latest and greatest)
- Kernel modules 2.0.0
- PPP daemon 2.2.0f
- Dynamic linker (ld.so) 1.7.14
- GNU CC 2.7.2.1
- Binutils 2.7.0.3
- Linux C Library Stable: 5.2.18, Beta: 5.4.33
- Linux C++ Library 2.7.2.1
- Termcap 2.0.8
- Procps 1.01
- Gpm 1.10
- SysVinit 2.64
- Util-linux 2.5
- Mount 2.5p
- Net-tools 1.32-alpha
- Kbd 0.91"
Whereas I've got...
gcc -v = 2.7.2
libc = 5.3.12
libc++ = 27.1.4 ?? (meaning 2.7.1.4 I suppose?)
Binutils: ld -v = "cygnus-2.6 (with BFD 2.6.0.14)"
ldd -v & -V = 1.8.2
modules = 2.0.0
sysVinit = 2.62
I didn't find any reference to "modutils" in the document.
I'm slightly nervous about upgrading where I don't need to in case
backward compatibity is an issue and I end up breaking my system and
having to buy a new distribution, backup, restore, pick through old and
new files, etc., re-install and generally waste a few weekends and make
my girlfriend think I don't love her anymore! ;-) I can see that my
binutils is out of date which could cause problems but wouldn't the
dynamic linker, C library, C++ library (both .so and therefore dynamic?)
all only come into play after the kernel has started and is running user
mode programs?
Sorry if I'm being dense, I have never built kernels before Linux and
this is the first major change to my kernel since it was installed!
Thanks,
Carl
==============A82B06B49A77CC345F3174E5
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<font face="Courier New,Courier">Oops. RTFM eh? :-) Thanks
for your help so far, I don't know if you could elaborate a bit further?</font><font
face="Courier New,Courier"></font>
<p><font face="Courier New,Courier">As I understand it the Changes document
in the Documentation subdirectory of the 2.0.38 distribution I've unpacked
says that I need...</font><font face="Courier New,Courier"></font>
<p><font face="Courier New,Courier">"Current Releases (the latest necessary
for basic functionality, not necessarily the latest and greatest)</font><font
face="Courier New,Courier"></font>
<p><font face="Courier New,Courier">- Kernel
modules
2.0.0</font>
<br><font face="Courier New,Courier">- PPP
daemon
2.2.0f</font>
<br><font face="Courier New,Courier">- Dynamic linker (ld.so) 1.7.14</font>
<br><font face="Courier New,Courier">- GNU
CC
2.7.2.1</font>
<br><font face="Courier New,Courier">-
Binutils
2.7.0.3</font>
<br><font face="Courier New,Courier">- Linux C
Library
Stable: 5.2.18, Beta: 5.4.33</font>
<br><font face="Courier New,Courier">- Linux C++ Library
2.7.2.1</font>
<br><font face="Courier New,Courier">-
Termcap
2.0.8</font>
<br><font face="Courier New,Courier">-
Procps
1.01</font>
<br><font face="Courier New,Courier">-
Gpm
1.10</font>
<br><font face="Courier New,Courier">-
SysVinit
2.64</font>
<br><font face="Courier New,Courier">-
Util-linux
2.5</font>
<br><font face="Courier New,Courier">-
Mount
2.5p</font>
<br><font face="Courier New,Courier">-
Net-tools
1.32-alpha</font>
<br><font face="Courier New,Courier">-
Kbd
0.91"</font>
<br><font face="Courier New,Courier"></font> <font face="Courier
New,Courier"></font>
<p><font face="Courier New,Courier">Whereas I've got...</font><font face="Courier
New,Courier"></font>
<p><font face="Courier New,Courier">gcc
-v
= 2.7.2</font>
<br><font face="Courier
New,Courier">libc
= 5.3.12</font>
<br><font face="Courier
New,Courier">libc++
= 27.1.4 ?? (meaning 2.7.1.4
I suppose?)</font>
<br><font face="Courier New,Courier">Binutils: ld -v
= "cygnus-2.6 (with BFD 2.6.0.14)"</font>
<br><font face="Courier New,Courier">ldd -v &
-V
= 1.8.2</font>
<br><font face="Courier
New,Courier">modules
= 2.0.0</font>
<br><font face="Courier
New,Courier">sysVinit
= 2.62</font><font face="Courier
New,Courier"></font>
<p><font face="Courier New,Courier">I didn't find any reference to "modutils"
in the document.</font><font face="Courier New,Courier"></font>
<p><font face="Courier New,Courier">I'm slightly nervous about upgrading
where I don't need to in case backward compatibity is an issue and I end
up breaking my system and having to buy a new distribution, backup, restore,
pick through old and new files, etc., re-install and generally waste a
few weekends and make my girlfriend think I don't love her anymore!
;-) I can see that my binutils is out of date which could cause problems
but wouldn't the dynamic linker, C library, C++ library (both .so and therefore
dynamic?) all only come into play after the kernel has started and is running
user mode programs?</font><font face="Courier New,Courier"></font>
<p><font face="Courier New,Courier">Sorry if I'm being dense, I have never
built kernels before Linux and this is the first major change to my kernel
since it was installed!</font><font face="Courier New,Courier"></font>
<p><font face="Courier New,Courier">Thanks,</font><font face="Courier
New,Courier"></font>
<p><font face="Courier New,Courier">Carl</font></html>
==============A82B06B49A77CC345F3174E5==
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.setup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************
