Linux-Misc Digest #745, Volume #25 Tue, 12 Sep 00 17:13:02 EDT
Contents:
Re: Drive Space in RH 6.0 (Johan Kullstam)
Re: Anyone want to be part of a new website...? (Tony Lawrence)
Re: Drive Space in RH 6.0 ("Peter T. Breuer")
Re: Stalling ("Jule Slootbeek")
Re: Command executed automatically when I dial up? How? ("Bob Billing (AKA Uncle
Bob)")
gethostbyname_r usage (mohanva)
Re: End-User Alternative to Windows ("Yannick")
Re: How to grep for date? ("Lurch")
Can't install LILO when Linux > 8 GB limit with PC with BIOS restriction (Pieter
Langendonck)
Unresolved Symbols (RH 6.2 on AMD T-bird on Abit KA-7 board) (Michael Hohensee)
----------------------------------------------------------------------------
Subject: Re: Drive Space in RH 6.0
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 12 Sep 2000 15:16:23 -0400
"Peter T. Breuer" <[EMAIL PROTECTED]> writes:
> Johan Kullstam <[EMAIL PROTECTED]> wrote:
> : "Peter T. Breuer" <[EMAIL PROTECTED]> writes:
>
> :> Johan Kullstam <[EMAIL PROTECTED]> wrote:
> :> : "Steve Wolfe" <[EMAIL PROTECTED]> writes:
> :>
> :> :> Forget my last message. I stopped reeading early, and should have pointed
> :> :> out a few more things.
> :> :>
> :> :> > "Safe" for what? / should be a small partition of about 64MB max,
> :> :>
> :> :> Why? Will 70 megs break something? For goodness sake, with hard drives
> :> :> costing less than twenty cents per megabyte, don't be so stingy.
> :>
> :> : twenty cents! it's difficult to pay even a tenth of that. consider a
> :> : top-of-the-line 9GB SCSI at $300, that's 3 cents per megabyte. a good
> :> : EIDE costs about 1 cent per megabyte. thus your statement is even
> :> : more powerful.
> :>
> :> Do neither of you get it? The chance of damage to your root partition
> :> is directly proportional to its size. Making it bigger is _worse_ not
> :> better. You want it as small as possible. Exactly as big as required to
> :> let you boot up and repair whatever _else_ is damaged, in fact, and no
> :> bigger.
>
> : i get it. but that's where tom's root/boot disk and your backup comes in.
>
> Not necessary. And a root disk and boot disk is terribly inconvenient
> compared to just loogging in as normal.
>
>
> :> :-) no no no. You don't get it. Sigh .. does everything which one
> :> thinks is so obvious as not to be worth stating have to repeated in
> :> Capital Letters twenty times on usenet?
>
> :> : that's why i do 4 partitions.
> :>
> :> : /boot around 20MB
> :> : / at least 2GB
> :> : /home whatever is left
> :> : <swap> 128MB (adjust to need/taste)
> :>
> :> And you are a nana,
>
> : i make backups. i have /home, /etc and a few random config
> : directories backed up on a regular basis.
>
> : so a disk fails every 5 years or so. big deal. anyhow, it's easy to
>
> Actually, the current statistics I have are that 15-20% of my disks fail
> every year. Yes, that would be an expected time between failures of 5
> years.
>
> But those are complete failures. I get non catastrophic failures with
> significant losses every six months or so in most disks. And failures
> in the file system are very frequent. About once every 2-4 weeks in
> most systems. You won't notice them .. they arise from momentary power
> spikes, slow disk response times, etc. etc. Here's one I dealt with on
> a main server today .. only symptom was an httpd consuming 99% cpu and
> sendmail hung on sending.
>
> wap_free: swap-space map bad (entry 0010e802)
> swap_free: swap-space map bad (entry 0010ee00)
> swap_free: swap-space map bad (entry 0010e902)
> swap_free: swap-space map bad (entry 0011ef02)
> swap_free: swap-space map bad (entry 0009ff00)
> swap_free: swap-space map bad (entry 000db102)
> swap_free: swap-space map bad (entry 000aeb00)
> swap_free: swap-space map bad (entry 0012fd02)
> swap_free: swap-space map bad (entry 00130300)
> swap_free: swap-space map bad (entry 0012fe02)
> swap_free: swap-space map bad (entry 00133902)
> swap_free: swap-space map bad (entry 0013c300)
> swap_free: swap-space map bad (entry 0013be02)
> swap_free: swap-space map bad (entry 00146700)
> swap_free: swap-space map bad (entry 00145f02)
> swap_free: swap-space map bad (entry 00146800)
> swap_free: swap-space map bad (entry 00146002)
> swap_free: swap-space map bad (entry 00150b00)
> eth0: Something Wicked happened! 2008.
> Hmm.. Trying to use unallocated swap (000db102)
> swap_free: swap-space map bad (entry 000db102)
> Adding Swap: 72256k swap-space (priority -1)
>
> That last was me getting in and fixing it.
>
> : simply reinstall the whole system area. and with decent backups, it's
>
> Reinstall the whole system area! And what happened to all your mods to
> fit the system into your net!
>
> :> du -sx /*
> :> (trimmed to show root dirs only)
> :> 4293 /bin
> :> 68 /dev
> :> 2664 /etc
> :> 16932 /lib
> :> 13 /lost+found
> :> 355 /root
> :> 4020 /sbin
> :> 76 /shlib
> :>
> :> which is about 28MB in total. Enough for a richly functioning system,
> :> in fact (about 4MB is sufficient to boot up, edit and telnet).
>
> As is evidenced by the rescue boot disks.
let me tell you what i don't like about your scheme. it calls for a
lot of smallish partitions and it's hard to predict how much you will
need in each in the future.
i tried that method about a year or so ago. i had 9GB disk and made
partitions thusly,
/ 256MB
/tmp 512MB
/usr 3GB
/var 512MB
/home ~3GB (whatever was left over)
<swap> 128MB
my idea was to be able to run / and /usr read-only most of the time
(or at least not have over much writing activity in them). i let them
be read/write-able for simplicity. i perhaps could have built a
/usr/src partition too.
this seemed to work but i was running out of room in the various
places. i was trying to burn a cd-rom image and that takes up to
3*640MB. 1 for the original stuff, 2 for a pruned copy of the orginal
(less the stuff i didn't want) in a directory tree, 3 for the iso9660
image. perhaps i should have made /tmp larger. however, it was
difficult to see how much i'd need before i needed it. and even
though i had plenty of free space, it was scattered all over the place
in useless pieces too small for my needs.
back in the day, i didn't have an effective back-up mechanism.
repartitioning is annoying. hence, next time i wanted a big linux
upgrade, i wiped out the scheme.
if i'd have had a smaller disk, e.g., 2GB (actually 3GB total but i
had win95 on 1GB of it), i am not sure what a good allocation would
be. i never did figure out one, so i used
/boot 10MB
<swap> 128MB
/ 1GB
/home nearly 1GB
this worked great on the 9GB disk too.
this was decidely superior to my first effort of
<swap> 128MB
/ nearly 2GB
since i could stash /etc and other configs in /home, then blow away
root on a re-install.
maybe now with disk space being so cheap, it is feasable to use it by
making lots of partitions.
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
sysengr
------------------------------
From: Tony Lawrence <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.m68k,comp.os.linux.networking,comp.os.linux.portable,comp.os.linux.powerpc,comp.os.linux.questions,comp.os.linux.redhat
Subject: Re: Anyone want to be part of a new website...?
Date: Tue, 12 Sep 2000 15:29:44 -0400
wBi wrote:
>
> Good afternoon,
>
> I am the webmaster of http://www.justBE.com and I an looking for
> trust-worthy people,
> For the rest of you, maybe you want to have a look at the website, and tell
> me what you think so far.
I think that even with 768K DSL it took a perilously long
time to load..
--
Tony Lawrence ([EMAIL PROTECTED])
SCO/Linux articles, help, book reviews, tests,
job listings and more : http://www.pcunix.com
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Drive Space in RH 6.0
Date: 12 Sep 2000 19:48:53 GMT
Johan Kullstam <[EMAIL PROTECTED]> wrote:
: let me tell you what i don't like about your scheme. it calls for a
: lot of smallish partitions and it's hard to predict how much you will
But that's fine. The more small partitions you have the more flexible
the system is. You can always combine a few together if you feel like
it (using raid or just removing the boundary). In contrast it's
terribly difficult to cut a large file system up into parts, becuase
where do you put the archive f it while you're fiddling around with
where it used to be..
: need in each in the future.
: i tried that method about a year or so ago. i had 9GB disk and made
: partitions thusly,
: / 256MB
Way too big.
: /tmp 512MB
Too large.
: /usr 3GB
: /var 512MB
A bit small for a system that size. As is tmp. I'd put /tmp in
/var/tmp and combine them to give you 1GB of temp/var space.
: /home ~3GB (whatever was left over)
: <swap> 128MB
: my idea was to be able to run / and /usr read-only most of the time
Yes, I have RO /usr on all systems. / is harder and I prefer to mirror
it rather than make big mods to standard distro setups.
: this seemed to work but i was running out of room in the various
: places. i was trying to burn a cd-rom image and that takes up to
: 3*640MB. 1 for the original stuff, 2 for a pruned copy of the orginal
Yes, I said your /tmp and /var were wrongly sized. I'd combine them
into one, which is large enough for at least one burn! I know.
(it doesn't take 3*, just 1* the final image).
: (less the stuff i didn't want) in a directory tree, 3 for the iso9660
: image. perhaps i should have made /tmp larger. however, it was
It's the temporary directory .. wherever it is .. that should have
been larger. Yours is too big for trivial tasks and too small for
nontrivial ones.
: difficult to see how much i'd need before i needed it. and even
: though i had plenty of free space, it was scattered all over the place
: in useless pieces too small for my needs.
Actually, it wasn't. You could always have made files as large as you
wanted on your various partitions, mounted each via loopback, and
combined the parts via raid linear mode into one big system. (yes,
folks, that's right .. this is a poor man's tmpfs).
: back in the day, i didn't have an effective back-up mechanism.
: repartitioning is annoying. hence, next time i wanted a big linux
It's not annoying, it's simply necessary. But I haven't done system
changes in years. Occasionally I need to resize user partitions, swap
bits and pieces around between machines, and so on, but that's normal
and not system changes. People always use more space. Backups always
use more space. I have to take an area assigned as backup and reassign
it as user space. Then I have to import more backup from a different
machine. I might move a user partition off one machien and use it for
backup or CD burning space. The system allocations don't change.
: if i'd have had a smaller disk, e.g., 2GB (actually 3GB total but i
This is about the max I use on any installation. A typical debian
install looks like:
/dev/hdb5 50717 29979 18119 62% /
/dev/hdb11 136227 69460 59732 54% /var
/dev/hdb7 511259 444982 39869 92% /usr
/dev/hdb8 257598 223191 21103 91% /usr/share
/dev/hdb10 50717 41530 6568 86% /spare
Or on a bigger machine:
/dev/hda5 62187 34008 24968 58% /
/dev/hda11 202182 48750 142992 25% /var
/dev/hda7 995115 415845 527864 44% /usr
/dev/hda8 497667 223896 248069 47% /usr/share
/dev/hda13 995115 187438 756271 20% /usr/local
/dev/hda10 62187 34692 24495 59% /spare
and on a huge SuSE server machine:
/dev/sda5 63439 53464 6699 89% /
/dev/sda9 1014895 868944 93523 90% /usr
/dev/sda10 1014895 200898 761569 21% /var
/dev/sda1 15847 3117 11912 21% /boot
/dev/sda8 507567 411504 69850 85% /opt
/dev/sda6 253807 200941 39760 83% /usr/X11R6
/dev/sda7 253807 153577 87124 64% /usr/share
/dev/sda13 1014895 506169 456298 53% /usr/local
/dev/sda15 63439 40131 20032 67% /spare
(/spare is always a daily mirror of /). If this machine gets
uncomfortable, it's partitions WILL be rearranged. It's hardly an
onerus task. Here's a server that's been around for years, and has
been pulled around contiunuously. I doubt it's ever been down for more
than a few seconds:
/dev/sda5 46632 36980 7244 84% /
/dev/md3 1033770 415591 564768 42% /var
/dev/sda7 256592 248518 5424 98% /usr
/dev/sda10 54410 42466 9135 82% /usr/X11R6
/dev/sda14 46632 38772 5452 88% /spare
/dev/sda9 497667 493992 3675 99% /usr/dist
/dev/md2 202187 150768 40977 79% /tftpboot
/dev/sdb9 513147 434759 51883 89% /usr/dist/share
/dev/sda6 46632 46075 76 100% /home
/dev/md0 2043271 1926887 86384 96% /bsd1
Note the raid devices ...
Personalities : [1 linear]
read_ahead 120 sectors
md0 : active linear sdb8 sdb10 sdb11 sdb6 2112416 blocks 4k rounding
md1 : active linear sda11 sda12 2008056 blocks 4k rounding
md2 : active linear sdb2 sdb4 208844 blocks 4k rounding
md3 : active linear sda1 sda3 sda8 sda13 1068224 blocks 4k rounding
Which shows how various partitions have been absorbed and pulled around
over the years.
: had win95 on 1GB of it), i am not sure what a good allocation would
: be. i never did figure out one, so i used
: /boot 10MB
: <swap> 128MB
: / 1GB
: /home nearly 1GB
: this worked great on the 9GB disk too.
: this was decidely superior to my first effort of
: <swap> 128MB
: / nearly 2GB
: since i could stash /etc and other configs in /home, then blow away
: root on a re-install.
: maybe now with disk space being so cheap, it is feasable to use it by
: making lots of partitions.
Peter
------------------------------
From: "Jule Slootbeek" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,alt.uu.comp.os.linux.questions
Subject: Re: Stalling
Date: Tue, 12 Sep 2000 16:12:51 -0400
Reply-To: "Jule Slootbeek" <[EMAIL PROTECTED]>
I can't access them, it stalles before i'm able to open 'm...i tried it to
figure it out...but i couldn't reach 'm...
"Glitch" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Do your logs say anything?????
> some more info would be helpful
>
> Jule Slootbeek wrote:
> >
> > Hey y'all
> >
> > I've got another problem here, this tme not w/ Samba wich ended up
working
> > great, but with the console itself, this is what happens: i boot up, and
> > then i log in w/ telnet from my windows:
> > and agfter i while my connection drops and the linuxmachine doesn't
respond
> > to any input anymore, from keyboard or mouse. it's an old P2 333 w/ 64
mb
> > and two Quantum HD's, i run RH 6 w/ kernel 2.2.5 and samba 2.0.6.
> > i know this isn't the greatest computer, but i wanted to fool
around w/
> > linux and so i got it out of my basement and got it to work, till now..
> > if anybody knows if it's a software problem, or simple outdated old,
crappy
> > software? please let me know.
> >
> > thnx
> >
> > Jule
> >
> > --
> > Please remove NOSPAM from my return address to reply!
------------------------------
From: "Bob Billing (AKA Uncle Bob)" <[EMAIL PROTECTED]>
Crossposted-To: uk.comp.os.linux
Subject: Re: Command executed automatically when I dial up? How?
Date: Tue, 12 Sep 2000 21:11:46 +0100
Phillip Deackes wrote:
> I tried putting a script in /etc/ppp/ip-up.d but this did not seem to be
> run when I connected.
The commonest reason for this not working is forgetting to set the x bit
in the permissions of the script.
This is my script (rc.local not rc.d - I'm running RedHat, I'm not sure
about storm) which works every time. It must do as I've received your
article.
-rwxr--r-- 1 root root 254 Jun 18 21:09 ip-up.local
# Things to do when the net has been contacted.
# Set the clock from the time server if it's up
if ping -c2 ntp.demon.co.uk ;
then
rdate -s ntp.demon.co.uk ;
hwclock --systohc ;
echo Clock Set ;
fi
# Fetch usenet news
/usr/local/sbin/fetchnews
--
I am Robert Billing, Christian, inventor, traveller, cook and animal
lover, I live near 0:46W 51:22N. http://www.tnglwood.demon.co.uk/
"It burned me from within. It quickened; I was with book as a woman
is with child." CS Lewis - Till we have faces, Ch 21.
------------------------------
From: mohanva <[EMAIL PROTECTED]>
Subject: gethostbyname_r usage
Date: Tue, 12 Sep 2000 20:24:10 GMT
Hi,
I couldn't find the man page for it. I had a question
regarding the usage of the following function.
int gethostbyname_r(char* name, hostent*result_buf,
char* buf, size_t buflen, hostent** result, int*
errno);
What is the difference between argument result_buf and
result ?
What are the possible return values of this function?
Where is the resulting hostent stored?
Thanks,
M
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "Yannick" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.advocacy
Subject: Re: End-User Alternative to Windows
Date: Tue, 12 Sep 2000 20:46:29 GMT
<[EMAIL PROTECTED]> a �crit dans le message :
8ph025$vh9$[EMAIL PROTECTED]
>
> Ingemar Lundin <[EMAIL PROTECTED]> wrote in message
> news:NzPu5.16$[EMAIL PROTECTED]...
> > rpm is not Linux alternative to winzip thats gzip/gunzip, rpm is the
> > alternative for .msi -files or rather .msi was invented by MS after rpm
> had
> > been around for awhile....strange he?
>
> Not really strange, it is just another case of Windows playing catch up
with
> Linux / unix.
Does RPM have an automatic repair functionality (not that useful, of course,
but still...) ? and also that possibility to advertise optional
functionality with on-demand installation ? And the package transformations,
allowing multiple package customizations while reducing HD space ? I don't
really know RPMs more than a average end-user, so these really are
questions.
In fact, the main concern is, can you install parts of a RPM in a
feature-oriented manner like you can an MSI, or do you need several RPMs and
an extra script or whatever ? Because the nice thing with .MSIs is that you
can they can come as a monolithic entity
which knows how to install selected parts of itself (the same as when you
get software on a CDROM, the setup programs asks you what you want and
installs what is needed), so it's really easy to use for the end user. At
the cost of download size, of course, because you made it monolithic...
Yannick
------------------------------
From: "Lurch" <[EMAIL PROTECTED]>
Subject: Re: How to grep for date?
Date: Tue, 12 Sep 2000 22:57:47 +0200
Hello,
$todaysdate contains the folowing information: "Sep 12"
this means that when you do a grep command, you actually do:
"grep Sep 12 /var/log/messages"
What you would actually want is this:
"grep "Sep 12" /var/log/messages"
Note the string "Sep 12" that is to be searched, instead of Sep 12 which
will search for "Sep" in file "12".
I'm not sure about the folowing syntax, but I think it will work:
grep "$todaysdate" /var/log/messages
Hope this helped...
Lurch
George <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I'm trying to learn a little about the Bash shell, by writing a script
> that will check my system log for events that happened today.
>
> If I use the following line in a script, I get the desired output
> (assuming the date is Sep 12):
>
> grep 'Sep 12' /var/log/messages
>
> I discovered the "set" builtin, and figured out how to use it to
> create a variable that is today's date:
>
> set $(date) ; todaysdate="'$2 $3'" ; echo $todaysdate
>
> The above command produces the output I'd expect, 'Sep 12', including
> the single quotes. But when I put it into grep, I don't get the
> results I expect:
>
> set $(date) ; todaysdate="'$2 $3'" ; \
> grep $todaysdate /var/log/messages
>
> I get this error message instead:
>
> grep: 12' No such file or directory
>
> Obviously, grep isn't seeing it's command line the same as when I
> typed the date directly. Why is it different?
>
> Thanks!
>
------------------------------
From: Pieter Langendonck <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.setup,comp.os.linux.questions
Subject: Can't install LILO when Linux > 8 GB limit with PC with BIOS restriction
Date: Tue, 12 Sep 2000 23:04:56 +0200
Reply-To: [EMAIL PROTECTED]
Hello all,
I have a PC which has a BIOS restriction of maximal 8 GB.
I have bought a 20,4 GB Harddisk. I would like to install
Linux, Windows95 and Windows NT on this system.
I know I can use the full 20,4 GB for Windows 95 with
Maxblast software.
What I want is to use all GBs > 8 GB for Linux. Below 8
GB I want to use Windows95 and NT. This is not a problem.
Unfortunately I can't get LILO installed. The Red Hat 6.0 setup
program gives a strange error.
I tried to make a small Linux partition below 8 GB, but the
Red Hat setup program forces me to install everything below
8 GB or nothing. I don't want to fully install Linux below 8 GB,
because I would like to have as much GBs as possible for
Windows95 and NT.
I'm willing to install a small part of Linux below 8 GB...
But I have no clue how to do that with setup program
of Red Hat.
Any suggestions?
Or can anyone explain me what to do, why I have the
problem installing Lilo. Everything during the install till that
point is working fine....
Greetings,
Pieter Langendonck
P.S. It is not possible that I flash my BIOS. The BIOS does just not
support partitions > 8 GB.
------------------------------
From: Michael Hohensee <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To:
alt.os.linux,comp.os.linux.hardware,comp.os.linux.setup,linux.redhat.install
Subject: Unresolved Symbols (RH 6.2 on AMD T-bird on Abit KA-7 board)
Date: Tue, 12 Sep 2000 21:04:27 -0400
I'm having problems properly compiling a kernel + modules for my RH 6.2
system, running on an AMD T-bird with an Abit KA-7 motherboard. Before
booting up for the first time, I had to recompile the kernel to prevent
it from attempting to turn off the nonexistant PIII identifier number
(which always resulted in a kernel panic). The only thing I changed in
the default kernel configuration was the Processor Type & Features menu
via 'make xconfig'. The machine now boots successfully, but is unable
to insmod any of the modules in /lib/modules. It first runs into a huge
sequence of depmod errors:
<Snip>
Sep 11 12:03:20 G22-71 rc.sysinit: Remounting root filesystem in
read-write mode succeeded
Sep 11 12:03:24 G22-71 depmod: depmod:
Sep 11 12:03:24 G22-71 depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/autofs.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/coda.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/fat.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/hfs.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/hpfs.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/lockd.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/minix.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/ncpfs.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/nfs.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/nfsd.o
Sep 11 12:03:24 G22-71 depmod: depmod: *** Unresolved symbols in
/lib/modules/2.2.14-5.0/fs/romfs.o
...
<Etc>
It does this for every module in /lib/modules. So naturally:
<Snip>
Sep 11 12:03:43 G22-71 autofs: autofs startup succeeded
Sep 11 12:03:43 G22-71 automount[382]: starting automounter version
3.1.4, path = /misc, maptype = file, mapname = /etc/auto.misc
Sep 11 12:03:43 G22-71 random: Initializing random number generator
succeeded
Sep 11 12:03:43 G22-71 insmod: /lib/modules/2.2.14-5.0/fs/autofs.o:
insmod autofs failed
Sep 11 12:03:43 G22-71 automount[382]: /misc: mount failed!
...
<Etc>
Interestingly enough, the system works fairly well, although anything
which requires the loading of a module (autofs, lockd, or sound) doesn't
work. Recompiling the modules doesn't appear to change anything, except
perhaps to generate more unusable modules.
Has anyone ever run into this problem before, or been able to
successfully install and test Linux on a system like mine? (AMD T-Bird
700MHz KA-7 board) If so, how was it corrected, or which distribution
did you use?
Thanks very much,
--
Michael Hohensee
------------------------------
** 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 (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
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-Misc Digest
******************************
