Linux-Setup Digest #854, Volume #20 Sun, 18 Mar 01 14:13:10 EST
Contents:
Re: Lilo Floppy Question (Carl Wick)
CD-ROM and harddisk fighting over DMA (Wouter Verhelst)
help with playing StarCraft games behind a linux firewall (Hung Ngoc Lai)
Re: Telnet Help (~absinth~)
Re: Modules problems when upgrading from 2.2.16-32 to 2.4.0 (~absinth~)
Problem of 2.4.2 kernel? (OrangeDino)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Carl Wick)
Subject: Re: Lilo Floppy Question
Date: Sun, 18 Mar 2001 18:08:09 GMT
cool...now this is what I couldn't find in TFM. ;-)
Thanks for the help...I will give it a go.
On Sun, 18 Mar 2001 17:40:42 GMT, E J <[EMAIL PROTECTED]> wrote:
># vi /mnt/floppy/etc/lilo.conf
>
>boot=/dev/fd0
>timeout=100
>message=/boot/message
>prompt
>image=/boot/vmlinuz-2.2.16-22 #change this to where your kernel is on the hard
>disk. Mine is on /boot
> label=linux
> root=/dev/hda4
> initrd=/boot/initrd.img # change this to where your initrd image is on
>the hard disk. Mine is on /boot
>
># lilo -C /mnt/floppy/etc/lilo.conf # VERY IMPORTANT!!! This update lilo on
>the boot floppy
>
>
>Carl Wick wrote:
>
>> Thanks...
>>
>> That is basically what my lilo.conf looks like on the floppy. But it
>> does not load the kernel off of the hard disk...it loads the kernel,
>> vmlinuz-2.2.16-22 off of the floppy....
>>
>
>But you did not run lilo on floppy. If you did, you would find it would
>complain it could not find kernel and initrd image because it was looking on
>the harddisk. That is what I found out playing with it many years ago.
>
>>
>> I am trying to have lilo running on the floppy but load the kernel off
>> of the hard disk.../dev/hda2
>>
>> On Sun, 18 Mar 2001 04:26:34 GMT, E J <[EMAIL PROTECTED]> wrote:
>>
>> >$ man lilo.conf # RTFM on lilo.conf also :)
>> >$ # this is what my lilo.conf for my floppy looks like. Yours would be
>> >different from mine. Adjust your lilo.conf
>> >$ # accordingly
>> >$ cat /mnt/floppy/etc/lilo.conf
>> >
>> >boot=/dev/fd0
>> >timeout=100
>> >message=/boot/message
>> >prompt
>> >image=/vmlinuz-2.2.16-22
>> > label=linux
>> > root=/dev/hda4
>> > initrd=/initrd.img
>> >
>> >Carl Wick wrote:
>> >
>> >> The issue is..I'm not sure what the lilo.conf should look like...
>> >>
>> >> thanks for the help....welll.....thanks for the feedback.
>> >>
>> >> On Sun, 18 Mar 2001 00:18:15 GMT, E J <[EMAIL PROTECTED]> wrote:
>> >>
>> >> >$ man lilo # RTFM on lilo :)
>> >> >
>> >> >This is the option you want
>> >> > -C config-file
>> >> > lilo reads its instructions about what files to map from
>> >> >its config
>> >> > file, by default /etc/lilo.conf. This option can be used
>> >> >to specify
>> >> > a non-default config file.
>> >> >
>> >> ># mount /dev/fd0 /mnt/floppy # mount that linux boot floppy
>> >> ># lilo -C /mnt/floppy/etc/lilo.conf # update lilo on the boot floppy
>> >> ># umount /mnt/floppy # unmount that linux boot floppy
>> >> >
>> >> >Carl Wick wrote:
>> >> >
>> >> >> Signature didn't work on this post...please remove the numbers to
>> >> >> email me directly...
>> >> >>
>> >> >> Thanks
>> >> >>
>> >> >> On Sat, 17 Mar 2001 21:18:35 GMT, [EMAIL PROTECTED] (Carl Wick)
>> >> >> wrote:
>> >> >>
>> >> >> >I run mkbootdisk and it creates a floopy boot disk using Lilo and it
>> >> >> >works fine. I would like to be able boot Lilo off the floppy, but
>> >> >> >have the kernel load off of the hard disk instead of the floppy. I
>> >> >> >had done it that way several years ago with a Slackware
>> >> >> >distribution...
>> >> >> >
>> >> >> >Can someone help? I am pretty sure it is doable, but am struggling
>> >> >> >with Lilo. I read the mini HOWTO on Lilo but still struggling.
>> >> >> >
>> >> >> >Thanks in advance...
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> Remove the numbers in the email address...
>> >> >>
>> >> >> Carl
>> >> >
>> >
>
Remove the numbers to email
Carl
------------------------------
From: [EMAIL PROTECTED] (Wouter Verhelst)
Subject: CD-ROM and harddisk fighting over DMA
Date: Sun, 18 Mar 2001 18:31:06 GMT
(if this is not the right place to ask, please redirect)
Hello
I've got a slight problem here:
When both my CD-ROM and my harddisk are using DMA, I sometimes get
errors over my console:
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
If I switch off DMA on the harddisk (using hdparm), the problem is
solved. However, harddisk data throughput is minimized then, so I
prefer not to do that if something else is possible.
I'm using 2.4.2, but I've had the problem since I installed this
system (with 2.2.17 -- although the "status" hex number had some other
value back then), so I suppose it's not something involving the
kernelversion.
Could someone help me out?
My hardware: I've got a AMI BIOS (on a Pentium 166, I suppose it's
quite old), a 40 GB "Maxtor" harddisk, and a 32x "Lite-On" CD-ROM
player.
If you need more information, feel free to ask.
--
wouter dot verhelst at advalvas in belgium
Real men don't take backups.
They put their source on a public FTP-server and let the world mirror it.
-- Linus Torvalds
------------------------------
From: Hung Ngoc Lai <[EMAIL PROTECTED]>
Subject: help with playing StarCraft games behind a linux firewall
Date: 18 Mar 2001 18:31:38 GMT
Hi Everyone,
I am running redhat 7 with kernel 2.4.2 on my home network. This
linux has 2 NICs is doing NAT for my Windows machines sitting
behind the linux box. I would like to be able to play the StarCraft
game on my Microsoft Windows machine. What do I need to
modify the rc.firewall script rule set for this to work? I understand
that in kernel 2.2.x you have to run the loose UDP but I am running
kernel 2.4.2 now. Please help....
Here is my rc.firewall script
#********************
#!/bin/bash
#
# This is a sample firewall for ip_tables, the tool for doing firewalling
# and masquerading under the 2.3.x/2.4.x series of kernels.
#
# Be warned, this is a very restrictive set of firewall rules (and they
# should be, for proper security). Anything that you do not _specifically_
# allow is logged and dropped into /dev/null, so if you're wondering why
# something isn't working, check /var/log/messages.
#
# This is about as close as you get to a 'secure' firewall. It's nasty,
# it's harsh, and it will make your machine nearly invisible to the rest
# of the internet world. Have fun.
#
# To run this script you must 'chmod 700 iptables-script' and then execute
# it. To stop it from running, run 'iptables -F'
#Point this to your copy of ip_tables. This step must be done to ensure
#that iptables is loaded properly.
IPT="/sbin/iptables"
#Load the module.
modprobe ip_tables
#Enable IP Forwarding on the Linux box. This step ensures that NAT will
#be handled properly.
$IPT -P FORWARD ACCEPT
echo 1 > /proc/sys/net/ipv4/ip_forward
#Flush old rules, delete the firewall chain if it exists
$IPT -F
$IPT -F -t nat
$IPT -X firewall
#Setup Masquerading. Change the IP to your internal network and uncomment
#this in order to enable it.
$IPT -A POSTROUTING -t nat -s 172.16.1.0/24 -j MASQUERADE
#Set up the firewall chain
$IPT -N firewall
$IPT -A firewall -j LOG --log-level info --log-prefix "Firewall:"
$IPT -A firewall -j DROP
#Accept ourselves
$IPT -A INPUT -s 127.0.0.1/32 -d 127.0.0.1/32 -j ACCEPT
#If you're using IP Masquerading, change this IP to whatever your internal
#IP addres is and uncomment it
#$IPT -A INPUT -s 172.16.1.0/24 -d 0/0 -j ACCEPT
#Accept DNS, 'cause it's warm and friendly
$IPT -A INPUT -p udp --source-port 53 -j ACCEPT
$IPT -A INPUT -p tcp --source-port 113 -j ACCEPT
$IPT -A INPUT -p tcp --destination-port 113 -j ACCEPT
#Allow ftp to send data back and forth.
$IPT -A INPUT -p tcp ! --syn --source-port 20 --destination-port 1024:65535 -j ACC
EPT
#These rules block two particular types of "malformed" packets. Nmap,
#a popular and powerful port scanner, uses these types of packets to get through
#ordinary packet filtering routers and some "non-stateful" firewalls.
# Block XMAS packets
iptables -A INPUT -p tcp --tcp-flags ALL ALL -j DROP
iptables -A FORWARD -p tcp --tcp-flags ALL ALL -j DROP
# Block NULL packets
iptables -A INPUT -p tcp --tcp-flags ALL NONE -j DROP
iptables -A FORWARD -p tcp --tcp-flags ALL NONE -j DROP
#Accept SSH. Duh.
$IPT -A INPUT -p tcp --destination-port 22 -j ACCEPT
#Send everything else ot the firewall.
$IPT -A INPUT -p icmp -j firewall
$IPT -A INPUT -p tcp --syn -j firewall
$IPT -A INPUT -p udp -j firewall
#*******************
------------------------------
From: ~absinth~ <[EMAIL PROTECTED]>
Subject: Re: Telnet Help
Date: Sun, 18 Mar 2001 20:24:38 +0200
Do not. telnet is horribly not secure. setting up a telnet
server is like opening your door and going to sleep.
use ssh.
look it up in a search engine.
Ben.
O'Banion wrote:
> I'm new to the whole Linux world, and I'm trying to enable Telnet on my
> Linux Box. I know this may sound like a silly problem, but if anyone can
> give me any advice, I would greatly appreciate it. I am running Debian 2.2.
>
> Thanks
------------------------------
From: ~absinth~ <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.questions,linux.redhat.ppp,comp.os.linux.redhat
Subject: Re: Modules problems when upgrading from 2.2.16-32 to 2.4.0
Date: Sun, 18 Mar 2001 20:21:49 +0200
I was dissapointed too to have witnessed ppp not working
no matter what with kernel 2.4.0. But I've found a solution !!
I went happily back to kernel 2.2.x :-)
My Linux theory is not to break my teeth trying to solve
cutting-edge hardware mysteries. just flow patiently and
the next version would work just fine :-)
Ben.
Richard Ng wrote:
> Hi, I have the same problem. I also upgraded my RH7 with kernel 2.2.16 to
> 2.4.2. I have installed all the ppp modules in my kernel. I had tried
> different versions(2.4.0, 2.4.0b2, 2.4.0b4) of ppp but none of them works.
> All of the complain my kernel does not support ppp. It seems that there is a
> miscommunication between ppp and kernel 2.4.2. I don't know whether
> modutils-2.4.3 could help or not but I am using modutils-2.4.2. I will try
> anyway. Thanks, in advance, for anyone who help.--Richard
>
>
> Christos Dimitrakakis wrote:
>
>
>> OK, I've installed ppp.2.4.0, kernel 2.4.2 (for amd) with
>> ppp_generic, ppp_async, ppp_deflate and ppp_synctty as modules
>>
>> However, I get an error from pppd that kernel does not have support for
>> PPP(!). It actually says to do modprobe -v ppp (of course ppp.o does not
>> exist!).. hm..
>>
>> It looks like none of my modules get loaded under 2.4.2, (while my
>> 2.2.16-32 installation works OK). lsmod only shows the dummy.o module
>> loaded!!!!!!!!!
>>
>> Maybe I am missing some step .. maybe I should change some init files(?)
>>
>> Anyway, modprobe and insmode produce this output:
>>
>> <------------------modprobe/insmode outputs----------------------->
>> [olethros@localhost olethros]$ /sbin/modprobe -v ppp
>> modprobe: Can't locate module ppp
>> [olethros@localhost olethros]$ /sbin/modprobe
>> modprobe: Nothing to load ???
>> Specify at least a module or a wildcard like \*
>> [olethros@localhost olethros]$ /sbin/modprobe \*
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: unresolved symbol
>> _mmx_memc
>> py
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: insmod
>> /lib/modules/2.4.2/k
>> ernel/drivers/parport/parport.o failed
>> /lib/modules/2.4.2/kernel/drivers/net/dummy.o: create_module: Operation
>> not perm
>> itted
>> /lib/modules/2.4.2/kernel/drivers/net/dummy.o: insmod
>> /lib/modules/2.4.2/kernel/
>> drivers/net/dummy.o failed
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
>> /lib/modules/2.4.2/kernel/d
>> rivers/net/slhc.o failed
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
>> /lib/modules/2.4.2/kernel/d
>> rivers/net/slhc.o failed
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
>> /lib/modules/2.4.2/kernel/d
>> rivers/net/slhc.o failed
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
>> /lib/modules/2.4.2/kernel/d
>> rivers/net/slhc.o failed
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
>> /lib/modules/2.4.2/kernel/d
>> rivers/net/slhc.o failed
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: unresolved symbol
>> _mmx_memc
>> py
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: insmod
>> /lib/modules/2.4.2/k
>> ernel/drivers/parport/parport.o failed
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: unresolved symbol
>> _mmx_memc
>> py
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: insmod
>> /lib/modules/2.4.2/k
>> ernel/drivers/parport/parport.o failed
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: unresolved symbol
>> _mmx_memc
>> py
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: insmod
>> /lib/modules/2.4.2/k
>> ernel/drivers/parport/parport.o failed
>> /lib/modules/2.4.2/kernel/drivers/scsi/sg.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/scsi/sg.o: insmod
>> /lib/modules/2.4.2/kernel/dr
>> ivers/scsi/sg.o failed
>> /lib/modules/2.4.2/kernel/drivers/scsi/sr_mod.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/scsi/sr_mod.o: insmod
>> /lib/modules/2.4.2/kerne
>> l/drivers/scsi/sr_mod.o failed
>> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o: create_module:
>> Operation n
>> ot permitted
>> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o: insmod
>> /lib/modules/2.4.2/
>> kernel/drivers/sound/ac97_codec.o failed
>> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o: create_module:
>> Operation n
>> ot permitted
>> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o: insmod
>> /lib/modules/2.4.2/
>> kernel/drivers/sound/ac97_codec.o failed
>> /lib/modules/2.4.2/kernel/drivers/sound/soundcore.o: create_module:
>> Operation no
>> t permitted
>> /lib/modules/2.4.2/kernel/drivers/sound/soundcore.o: insmod
>> /lib/modules/2.4.2/k
>> ernel/drivers/sound/soundcore.o failed
>> /lib/modules/2.4.2/kernel/drivers/usb/usb-uhci.o: unresolved symbol
>> _mmx_memcpy /lib/modules/2.4.2/kernel/drivers/usb/usb-uhci.o: insmod
>> /lib/modules/2.4.2/kern
>> el/drivers/usb/usb-uhci.o failed
>> /lib/modules/2.4.2/kernel/drivers/usb/storage/usb-storage.o: unresolved
>> symbol _
>> mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/usb/storage/usb-storage.o: insmod
>> /lib/modules
>> /2.4.2/kernel/drivers/usb/storage/usb-storage.o failed
>> /lib/modules/2.4.2/kernel/fs/fat/fat.o: unresolved symbol _mmx_memcpy
>> /lib/modules/2.4.2/kernel/fs/fat/fat.o: insmod
>> /lib/modules/2.4.2/kernel/fs/fat/
>> fat.o failed
>> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o: insmod
>> /lib/modules/2.4.2/kernel/
>> net/sunrpc/sunrpc.o failed
>> /lib/modules/2.4.2/kernel/fs/fat/fat.o: unresolved symbol _mmx_memcpy
>> /lib/modules/2.4.2/kernel/fs/fat/fat.o: insmod
>> /lib/modules/2.4.2/kernel/fs/fat/
>> fat.o failed
>> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o: insmod
>> /lib/modules/2.4.2/kernel/
>> net/sunrpc/sunrpc.o failed
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-15.o: create_module:
>> Operation notpermitted
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-15.o: insmod
>> /lib/modules/2.4.2/ker
>> nel/fs/nls/nls_iso8859-15.o failed
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-7.o: create_module:
>> Operation not p
>> ermitted
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-7.o: insmod
>> /lib/modules/2.4.2/kern
>> el/fs/nls/nls_iso8859-7.o failed
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-4.o: create_module:
>> Operation not p
>> ermitted
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-4.o: insmod
>> /lib/modules/2.4.2/kern
>> el/fs/nls/nls_iso8859-4.o failed
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-3.o: create_module:
>> Operation not p
>> ermitted
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-3.o: insmod
>> /lib/modules/2.4.2/kern
>> el/fs/nls/nls_iso8859-3.o failed
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-2.o: create_module:
>> Operation not p
>> ermitted
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-2.o: insmod
>> /lib/modules/2.4.2/kern
>> el/fs/nls/nls_iso8859-2.o failed
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-1.o: create_module:
>> Operation not p
>> Using /lib/modules/2.4.2/kernel/drivers/net/slhc.o
>> Symbol version prefix ''
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o failed
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod ppp_async failed
>> [root@localhost olethros]# /sbin/modprobe -v slhc
>> /sbin/insmod /lib/modules/2.4.2/kernel/drivers/net/slhc.o
>> Using /lib/modules/2.4.2/kernel/drivers/net/slhc.o
>> Symbol version prefix ''
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o failed
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod slhc failed
>> [root@localhost olethros]# insmod
>> bash: insmod: command not found
>> [root@localhost olethros]# /sbin/insmod ppp
>> insmod: ppp: no module by that name found
>> [root@localhost olethros]# /sbin/insmod ppp_generic
>> Using /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
>> _mmx_memcpy
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
>> slhc_free_R2894cfb0
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
>> slhc_remember_R0bc55868
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
>> slhc_toss_Rf89e3455
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
>> slhc_uncompress_R3bc1319e
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
>> slhc_compress_R76135e6c
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
>> slhc_init_R2e0e927f
>> [root@localhost olethros]# /sbin/insmod slhc
>> Using /lib/modules/2.4.2/kernel/drivers/net/slhc.o
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
>> _mmx_memcpy
>> [root@localhost olethros]#
>>
>> <----------------------------------------------------------------------->
>>
>> This is my modules.dep file:
>>
>> [root@localhost olethros]# more /lib/modules/2.4.2/modules.dep
>> /lib/modules/2.4.2/kernel/drivers/char/lp.o:
>> /lib/modules/2.4.2/kernel/driver
>> s/parport/parport.o
>> /lib/modules/2.4.2/kernel/drivers/net/dummy.o:
>> /lib/modules/2.4.2/kernel/drivers/net/plip.o:
>> /lib/modules/2.4.2/kernel/driver
>> s/parport/parport.o
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_async.o:
>> /lib/modules/2.4.2/kerne
>> l/drivers/net/ppp_generic.o
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_deflate.o:
>> /lib/modules/2.4.2/kerne
>> l/drivers/net/ppp_generic.o
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o:
>> /lib/modules/2.4.2/kerne
>> l/drivers/net/slhc.o
>> /lib/modules/2.4.2/kernel/drivers/net/ppp_synctty.o:
>> /lib/modules/2.4.2/kerne
>> l/drivers/net/ppp_generic.o
>> /lib/modules/2.4.2/kernel/drivers/net/slhc.o:
>> /lib/modules/2.4.2/kernel/drivers/parport/parport.o:
>> /lib/modules/2.4.2/kernel/drivers/parport/parport_pc.o:
>> /lib/modules/2.4.2/kerne
>> l/drivers/parport/parport.o
>> /lib/modules/2.4.2/kernel/drivers/scsi/sg.o:
>> /lib/modules/2.4.2/kernel/drivers/scsi/sr_mod.o:
>> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o:
>> /lib/modules/2.4.2/kernel/drivers/sound/soundcore.o:
>> /lib/modules/2.4.2/kernel/drivers/sound/via82cxxx_audio.o:
>> /lib/modules/2.4
>> .2/kernel/drivers/sound/soundcore.o \
>> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o
>> /lib/modules/2.4.2/kernel/drivers/usb/storage/usb-storage.o:
>> /lib/modules/2.4.2/kernel/drivers/usb/usb-uhci.o:
>> /lib/modules/2.4.2/kernel/fs/fat/fat.o:
>> /lib/modules/2.4.2/kernel/fs/lockd/lockd.o:
>> /lib/modules/2.4.2/kernel/net/su
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-1.o:
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-15.o:
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-2.o:
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-3.o:
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-4.o:
>> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-7.o:
>> /lib/modules/2.4.2/kernel/fs/smbfs/smbfs.o:
>> /lib/modules/2.4.2/kernel/fs/vfat/vfat.o:
>> /lib/modules/2.4.2/kernel/fs/fat/fat.o
>> /lib/modules/2.4.2/kernel/net/ipx/ipx.o:
>> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o:
>>
>> A<------------------------------------------------------->
>>
>> And this is my modules tree..
>>
>> [root@localhost 2.4.2]# ls -Rt
>> .:
>> modules.dep modules.pcimap pcmcia kernel build
>>
>> ./pcmcia:
>>
>> ./kernel:
>> net fs drivers
>>
>> ./kernel/net:
>> sunrpc ipx
>>
>> ./kernel/net/sunrpc:
>> sunrpc.o
>>
>> ./kernel/net/ipx:
>> ipx.o
>>
>> ./kernel/fs:
>> fat lockd msdos nfs nls smbfs vfat
>>
>> ./kernel/fs/fat:
>> fat.o
>>
>> ./kernel/fs/lockd:
>> lockd.o
>>
>> ./kernel/fs/msdos:
>> msdos.o
>>
>> ./kernel/fs/nfs:
>> nfs.o
>>
>> ./kernel/fs/nls:
>> nls_iso8859-1.o nls_iso8859-2.o nls_iso8859-4.o
>> nls_iso8859-15.o nls_iso8859-3.o nls_iso8859-7.o
>>
>> ./kernel/fs/smbfs:
>> smbfs.o
>>
>> ./kernel/fs/vfat:
>> vfat.o
>>
>> ./kernel/drivers:
>> net parport scsi sound usb char
>>
>> ./kernel/drivers/net:
>> [root@localhost 2.4.2]# ls -Rt
>> .:
>> modules.dep modules.pcimap pcmcia kernel build
>>
>> ./pcmcia:
>>
>> ./kernel:
>> net fs drivers
>>
>> ./kernel/net:
>> sunrpc ipx
>>
>> ./kernel/net/sunrpc:
>> sunrpc.o
>>
>> ./kernel/net/ipx:
>> ipx.o
>>
>> ./kernel/fs:
>> fat lockd msdos nfs nls smbfs vfat
>>
>> ./kernel/fs/fat:
>> fat.o
>>
>> ./kernel/fs/lockd:
>> lockd.o
>>
>> ./kernel/fs/msdos:
>> msdos.o
>>
>> ./kernel/fs/nfs:
>> nfs.o
>>
>> ./kernel/fs/nls:
>> nls_iso8859-1.o nls_iso8859-2.o nls_iso8859-4.o
>> nls_iso8859-15.o nls_iso8859-3.o nls_iso8859-7.o
>>
>> ./kernel/fs/smbfs:
>> smbfs.o
>>
>> ./kernel/fs/vfat:
>> vfat.o
>>
>> ./kernel/drivers:
>> net parport scsi sound usb char
>>
>> ./kernel/drivers/net:
>> dummy.o ppp_async.o ppp_generic.o slhc.o
>> plip.o ppp_deflate.o ppp_synctty.o
>>
>> ./kernel/drivers/parport:
>> parport.o parport_pc.o
>>
>> ./kernel/drivers/scsi:
>> sg.o sr_mod.o
>>
>> ./kernel/drivers/sound:
>> ac97_codec.o soundcore.o via82cxxx_audio.o
>>
>> ./kernel/drivers/usb:
>> storage usb-uhci.o
>>
>> ./kernel/drivers/usb/storage:
>> usb-storage.o
>>
>> ./kernel/drivers/char:
>> lp.o
>>
>> -------------------------------------------------------------
>>
>> Hope someone can help me!!!!!!
>>
>> Christos Dimitrakakis
------------------------------
From: OrangeDino <[EMAIL PROTECTED]>
Subject: Problem of 2.4.2 kernel?
Date: Mon, 19 Mar 2001 02:11:29 +0800
I have compiled and run my linux box with the 2.4.2 kernel for some days
but I find that I cannot read the long file name in cdr burnt under
Windoz envirnoment. It work under the 2.2.x kernel which I used before.
Then I try to re-compile the 2.4.2 kernel to solve this.
As I re-compile, it cannot "make bzImage" even I use the kernel
configuration of the one I am using.
Would this be something wrong with some software in my linux box dealing
with "make bzImage"?
And also how to solve the problem of long file name of cdr?
Thanks for your kindly concern!
------------------------------
** 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
******************************
