Comment everything in /etc/rc.d/rc.modules you aren't interested in.
Linux Rocks ! ([EMAIL PROTECTED]) wrote*:
>
>Kernel compiled and boots, modules compiled w/out issue, but when installed,
>many complained from depmod, infact, more than I could scroll up to read. I
>noticed that a bunch of them (ifnot all) were scsi. I have no scsi, and didnt
>enable any scsi modules... I have no idea why it shold want to make any scsi
>modules!
> The hermes module loads, but the hostap_cs module gives me errors (but
>atleast it loads!)
>
>so... I guess its progress... Ill see if I can install the wireless tools
>again, and get something working!
>
>Jamie
>
>On Monday 02 September 2002 02:43 pm, Linux Rocks ! wrote:
>: Ive done that too.. but I havnt compiled a kernel ('cept the last couple
>: days....) for a few years... (rpm seems to work fine many times...) After
>: having problems compiling, I thought I ought to read the howto (maybe
>: things changed from 2.2 to 2.4 ?).
>: Heres a snipet starting at line 59 in /usr/src/linux/README.
>: Do NOT use the /usr/src/linux area! This area has a (usually
>: incomplete) set of kernel headers that are used by the library header
>: files. They should match the library, and not get messed up by
>: whatever the kernel-du-jour happens to be.
>: So... Since I couldnt fit all the programming, both 18, and 19 kernel
>: source (130MB each!), and libraries on the 720 meg disk, I droped the 19,
>: and just used the stock 18 slackware kernel source.
>: It seems to be compiling fine... It took between 1 and 2 hours to compile
>: the kernel, and so far over an hour for the modules...
>:
>: I do want the freshest I can get in the system, as I want the wireless nic
>: driver to work... If I get 18 working, I will probably try 19, this will
>: require deleteing 18's source tree though... but after the kernel and
>: modules are compiled for 18, I wont need it on the system anyway...
>:
>: I did try all this on my workstation with the pc-card reader, but I think
>: the wireless nic is incompatible with that reader... It wont work in
>: windows on that machine either....
>:
>: Jamie
>:
>: On Monday 02 September 2002 01:47 pm, Bob Crandell wrote:
>: : Well actually the kernel source goes in or should go in
>: : /usr/src/linux-2.4.19 or whatever with a simbolic link named linux that
>: : points to the source your using.
>: :
>: : At one point I had 2.2.19, 2.4.5, 2.4.17, 2.4.18 and 2.4.19. The active
>: : on was the one that /usr/src/linux pointed to. Now that I think about
>: : it, with a simlink, the kernel source could go anywhere your little heart
>: : desires.
>: :
>: : justin bengtson ([EMAIL PROTECTED]) wrote*:
>: : >in practice, i think you put the kernel in userspace so that you don't
>: : > screw up the kernel includes. kernel includes are somewhere in
>: : > /usr/src/linux/ and should _technically_ be the ones you compiled the
>: : > system with (well, that's what linus says... he's got includes running
>: : > back quite far.) but most people don't care (like me). it has the
>: : > potential to cause problems (i guess... i've never seen any.)
>: : >
>: : >if you're worried about it, put the kernel source into /root/linux (i
>: : > always compile a kernel as root. am i the only one?)
>: : >
>: : >--- Mike O <[EMAIL PROTECTED]> wrote:
>: : >> Eh? I'm using 2.4.19 right now and I've got it in
>: : >> /usr/src. Really, where else would you put it without
>: : >> screwing things up? As far as that one hour compile
>: : >> time... ouch. I could recompile about 15 times an
>: : >> hour.
>: : >
>: : >=====
>: : >Justin Bengtson @euglug=(v+ e- eug++ bsd? gnu++ s++)
>: : >[EMAIL PROTECTED]
>: : >
>: : >"i called some kid 'b' the other day. it's the price
>: : >you pay for living hip-hop every day of your life."
>: : >Jerry (from the Point Blank Rangers)
>: : >
>: : >__________________________________________________
>: : >Do You Yahoo!?
>: : >Yahoo! Finance - Get real-time stock quotes
>: : >http://finance.yahoo.com
>: : >_______________________________________________
>: : >Eug-lug mailing list
>: : >[EMAIL PROTECTED]
>: : >http://mailman.efn.org/cgi-bin/listinfo/eug-lug
>
>[EMAIL PROTECTED]
>http://mailman.efn.org/cgi-bin/listinfo/eug-lug
>
--
Bob Crandell
Assured Computing
When you need to be sure.
Voice 541-689-9159
FAX 240-371-7237
[EMAIL PROTECTED]
www.assuredcomp.com
Eugene, Or. 97402
_______________________________________________
Eug-lug mailing list
[EMAIL PROTECTED]
http://mailman.efn.org/cgi-bin/listinfo/eug-lug
