Linux-Setup Digest #475, Volume #20 Mon, 22 Jan 01 14:13:07 EST
Contents:
Re: Swap size / Memory upgrade (Johan Kullstam)
Linux and USB and SmartMedia, oh my! ([EMAIL PROTECTED])
Re: Newbie: Compiling Kernel ("ne...")
Re: Protect yourself! I got hacked by the Ramen worm (webbgroup)
ISDN configuration ("Tomas Andersen")
how to duplicate a linux installation? (Alois Treindl)
----------------------------------------------------------------------------
Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc
Subject: Re: Swap size / Memory upgrade
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 22 Jan 2001 12:41:00 -0500
ekk <[EMAIL PROTECTED]> writes:
> Thanks, Jamess for your advice. The person whose job I inherited told me
> that the swap space should be double the amount of RAM for up to 512 MB,
> 1.5x for 512 - 1024, and 1x for above 1024 MB.
certain older (and maybe some current) unix distributions require that
you have enough swap space for all your memory, i.e., anything in
memory is also mirrored on disk swap. the left-over is swap storage.
it's similar to inclusive/exclusive L1/L2 caching on a CPU. the AMD
(tbird and duron) uses exclusive, the intel uses inclusive.
linux does not repeat core in swap. thus the linux swap is whatever
the left-over would have under the traditional regime.
> I'm not terribly sure why he
> thought so much swap was required, but I think he arrived at those ratios
> through experience dealing with many different machines and RAM
> amounts.
old system experience.
> The machines he set up are stable and rarely get bogged down, as long as the
> users don't push them over the RAM!
swap can be used for storing dead shells and dormant daemons at
virtually no performance penalty. some use of swap is just moving the
sleeping, non-running stuff out of the way of a process which wants to
run.
> Thank you kindly,
> Ken
>
> [EMAIL PROTECTED] wrote:
>
> > ekk wrote:
> > >
> > > Trying to make a judgement call without enough experience -
> > >
> > > I just upgraded from 512 RAM to 1 GB. My swap space is 768. Should
> > > I increase the swap? We do often use all of the RAM available on a
> > > machine, but we of course try to avoid using the swap.
don't bother unless you find yourself running out of swap.
> > > In the same way, I also downgraded a 1 GB RAM machine to 512 (bad RAM).
> > > Do I need to lower the swap space?
> > >
> > > In both situations disk space is not a concern.
> > >
> > > I assume the best way to adjust the swap is to use Partition Magic?
> > > I don't want to go through a whole reinstall of either machine.
> > >
> > > Ken
> >
> > I have 256 MB RAM and 128 MB swap on my box. It hardly ever uses any of
> > the swap at all except for programs like Netscape, and then it uses very
> > little swap. I don't think that you need more than 128 MB of swap when
> > you have a lot of ram.
> >
> > jamess
> > --
> > "On the side of the software box, in the 'System Requirements' section,
> > it said 'Requires Windows 95 or better'. So I installed Linux."
> >
> > -Anonymous
>
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
sysengr
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware
Subject: Linux and USB and SmartMedia, oh my!
Date: Mon, 22 Jan 2001 18:16:49 GMT
Hello all,
I've been working at getting a ZiO! USB SmartMedia reader working under
Linux 2.4.0-test12. The ZiO uses the SDDR-09 driver and I've gone to
the Linux USB homepage and the SDDR-09 mini-howto homepage
(http://www.theneals.net/linux/SDDR09-HOWTO) for help, but so far I
haven't been able to mount the drive.
I have compiled into the kernel scsi support, scsi disk support, scsi
generic support, and scsi emulation support (as per the SDDR-09
mini-howto). I have compiled the USB support as modules (usbcore,
usb-uhci, & usb-storage).
When I boot up it appears that the SCSI drivers come up ok. When I
load up the USB modules and plug in the ZiO I get the following output
from the following proc files:
/proc/bus/usb/devices:
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 7 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI-alt Root Hub
S: SerialNumber=ff80
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=07 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1
P: Vendor=04e6 ProdID=0003 Rev= 2.07
S: Manufacturer=SCM Microsystems Inc.
S: Product=eUSB SmartMedia Adapter
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01
Driver=usb-storage
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl= 32ms
/proc/scsi/scsi:
Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: Sandisk Model: ImageMate SDDR09 Rev: 0207
Type: Direct-Access ANSI SCSI revision: 02
/var/log/messages shows this after insmod usb-uhci & usb-storage:
Jan 22 13:02:04 zee kernel: usb-uhci.c: $Revision: 1.251 $ time 07:03:35
Jan 22 2001
Jan 22 13:02:04 zee kernel: usb-uhci.c: High bandwidth mode enabled
Jan 22 13:02:04 zee kernel: usb-uhci.c: USB UHCI at I/O 0xff80, IRQ 10
Jan 22 13:02:04 zee kernel: usb.c: new USB bus registered, assigned bus
number 1
Jan 22 13:02:04 zee kernel: Product: USB UHCI Root Hub
Jan 22 13:02:04 zee kernel: SerialNumber: ff80
Jan 22 13:02:04 zee kernel: hub.c: USB hub found
Jan 22 13:02:04 zee kernel: hub.c: 2 ports detected
Jan 22 13:02:22 zee kernel: usb.c: registered new driver usb-storage
Jan 22 13:02:22 zee kernel: USB Mass Storage support registered.
after plugging in the ZiO /var/log/messages has this addition output:
Jan 22 13:03:42 zee kernel: hub.c: USB new device connect on bus1/1,
assigned device number 13
Jan 22 13:03:42 zee kernel: Manufacturer: SCM Microsystems Inc.
Jan 22 13:03:42 zee kernel: Product: eUSB SmartMedia Adapter
Jan 22 13:03:42 zee kernel: scsi1 : SCSI emulation for USB Mass Storage
devices
Jan 22 13:03:43 zee kernel: sda:<7>usb-storage: queuecommand() called
/var/log/debug has a MUCH longer output (please see end of post for
debug output)
When I try to mount the scsi device I get this:
zee:~# mount /dev/sda1 /mnt
mount: block device /dev/sda1 is write-protected, mounting read-only
mount: /dev/sda1 is not a valid block device
zee:~#
And /var/log/debug spits out:
Jan 22 13:08:33 zee kernel: usb-storage: queuecommand() called
Jan 22 13:08:33 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:08:33 zee kernel: usb-storage: Skipping START_STOP command
Jan 22 13:08:33 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:08:33 zee kernel: usb-storage: queuecommand() called
Jan 22 13:08:33 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:08:33 zee kernel: usb-storage: Skipping START_STOP command
Jan 22 13:08:33 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:08:33 zee kernel: usb-storage: queuecommand() called
Jan 22 13:08:33 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:08:33 zee kernel: usb-storage: Skipping START_STOP command
Jan 22 13:08:33 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:08:33 zee kernel: usb-storage: queuecommand() called
Jan 22 13:08:33 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:08:33 zee kernel: usb-storage: Skipping START_STOP command
Jan 22 13:08:33 zee kernel: usb-storage: *** thread sleeping.
I'm stuck now because I haven't found any info on what to try next.
Has anyone else ran into this problem and if so, what was your solution?
Thanks,
Kevin
/var/log/debug output:
Jan 22 13:03:42 zee kernel: hub.c: port 1 connection change
Jan 22 13:03:42 zee kernel: hub.c: port 1, portstatus 101, change 1, 12
Mb/s
Jan 22 13:03:42 zee kernel: hub.c: port 1, portstatus 103, change 0, 12
Mb/s
Jan 22 13:03:42 zee kernel: usb.c: kmalloc IF c12b4560, numif 1
Jan 22 13:03:42 zee kernel: usb.c: new device strings: Mfr=1, Product=2,
SerialNumber=0
Jan 22 13:03:42 zee kernel: usb.c: USB device number 13 default language
ID 0x409
Jan 22 13:03:42 zee kernel: usb-storage: Searching unusual device list
for (0x4e6, 0x3, 0x207)...
Jan 22 13:03:42 zee kernel: usb-storage: -- found matching device:
Sandisk ImageMate SDDR09
Jan 22 13:03:42 zee kernel: usb-storage: USB Mass Storage device
detected
Jan 22 13:03:42 zee kernel: usb-storage: Endpoints: In: 0xc65acd34 Out:
0xc65acd20 Int: 0xc65acd48 (Period 32)
Jan 22 13:03:42 zee kernel: usb-storage: Result from
usb_set_configuration is 0
Jan 22 13:03:42 zee kernel: usb-storage: New GUID
04e600030000000000000000
Jan 22 13:03:42 zee kernel: usb-storage: Transport: EUSB/SDDR09
Jan 22 13:03:42 zee kernel: usb-storage: Protocol: Transparent SCSI
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Command INQUIRY (6 bytes)
Jan 22 13:03:42 zee kernel: usb-storage: 12 00 00 00 ff 00 12 c0 28 ec
22 c1
Jan 22 13:03:42 zee kernel: usb-storage: Fixing INQUIRY data to show
SCSI rev 2
Jan 22 13:03:42 zee kernel: usb-storage: scsi cmd done, result=0x0
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad LUN (0/1)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (1/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (2/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (3/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (4/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (5/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (6/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Bad target number (7/0)
Jan 22 13:03:42 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:42 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:42 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:42 zee kernel: usb-storage: Command TEST_UNIT_READY (6
bytes)
Jan 22 13:03:42 zee kernel: usb-storage: 00 00 00 00 00 00 00 00 00 00
57 c3
Jan 22 13:03:42 zee kernel: usb-storage: SDDR09: Send control for
command 00 20 00 00 00 00 00 00 00 00 00 00
Jan 22 13:03:43 zee kernel: usb-storage: -- Stall on control pipe.
Clearing
Jan 22 13:03:43 zee kernel: usb-storage: -- usb_clear_halt() returns 0
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates command
failure
Jan 22 13:03:43 zee kernel: usb-storage: Issuing auto-REQUEST_SENSE
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: Send control for
command 03 20 00 00 12 00 00 00 00 00 00 00
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: Control for command OK
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: receiving 18 bytes
Jan 22 13:03:43 zee kernel: usb-storage: SCM data in transfer 18 sg
buffers 0
Jan 22 13:03:43 zee kernel: usb-storage: Transfered 18 of 18 bytes
Jan 22 13:03:43 zee kernel: usb-storage: rd: 70 00 06 00 00 00 00 0B 00
00 00 00 28 00 00 00
Jan 22 13:03:43 zee kernel: usb-storage: rd: 00 00
Jan 22 13:03:43 zee kernel: usb-storage: -- Result from auto-sense is 0
Jan 22 13:03:43 zee kernel: usb-storage: -- code: 0x70, key: 0x6, ASC:
0x28, ASCQ: 0x0
Jan 22 13:03:43 zee kernel: usb-storage: Unit Attention: (unknown
ASC/ASCQ)
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x2
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command TEST_UNIT_READY (6
bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 00 00 00 00 00 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: Send control for
command 00 20 00 00 00 00 00 00 00 00 00 00
Jan 22 13:03:43 zee kernel: usb-storage: SDDR09: Control for command OK
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x0
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command READ_CAPACITY (10
bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 25 00 00 00 00 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: Reading capacity...
Jan 22 13:03:43 zee kernel: usb-storage: Result of send_control for
device ID is 0
Jan 22 13:03:43 zee kernel: usb-storage: SCM data in transfer 64 sg
buffers 0
Jan 22 13:03:43 zee kernel: usb-storage: Transfered 64 of 64 bytes
Jan 22 13:03:43 zee kernel: usb-storage: rd: 98 EA 41 69 22 22 22 22 22
22 22 22 22 22 22 22
Jan 22 13:03:43 zee kernel: usb-storage: rd: 22 22 22 22 22 22 22 22 22
22 22 22 22 22 22 22
Jan 22 13:03:43 zee kernel: usb-storage: rd: 22 22 22 22 22 22 22 22 22
22 22 22 22 22 22 22
Jan 22 13:03:43 zee kernel: usb-storage: Result of read_deviceID is 0
Jan 22 13:03:43 zee kernel: usb-storage: Device ID = EA
Jan 22 13:03:43 zee kernel: usb-storage: Manuf ID = 98
Jan 22 13:03:43 zee kernel: usb-storage: Read control address 00000000
blocks 0200
Jan 22 13:03:43 zee kernel: usb-storage: Result for send_control in
read_control 0
Jan 22 13:03:43 zee kernel: usb-storage: SCM data in transfer 32768 sg
buffers 1
Jan 22 13:03:43 zee kernel: usb-storage: Transfered 32768 of 32768 bytes
Jan 22 13:03:43 zee kernel: usb-storage: Result for bulk read in
read_control 0
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0000 <-> PBA 0002
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0002 <-> PBA 0003
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0006 <-> PBA 0007
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0007 <-> PBA 0008
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0008 <-> PBA 0009
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0009 <-> PBA 000A
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000A <-> PBA 000B
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000B <-> PBA 000C
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000C <-> PBA 000D
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000D <-> PBA 000E
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000E <-> PBA 000F
Jan 22 13:03:43 zee kernel: usb-storage: LBA 000F <-> PBA 0010
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0003 <-> PBA 0017
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0005 <-> PBA 0033
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0001 <-> PBA 0053
Jan 22 13:03:43 zee kernel: usb-storage: LBA 0004 <-> PBA 0059
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x0
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: queuecommand() called
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command MODE_SENSE (6 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 1a 00 3f 00 08 00 00 00 00 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: CB_reset() called
Jan 22 13:03:43 zee kernel: usb-storage: CB[I] soft reset failed -32
Jan 22 13:03:43 zee kernel: usb-storage: -- transport indicates
transport failure
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x70000
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: usb-storage: *** thread awakened.
Jan 22 13:03:43 zee kernel: usb-storage: Command READ_10 (10 bytes)
Jan 22 13:03:43 zee kernel: usb-storage: 28 00 00 00 00 00 00 00 02 00
57 c3
Jan 22 13:03:43 zee kernel: usb-storage: READ_10: read block 0002 (LBA
0000) page 0 pages 2
Jan 22 13:03:43 zee kernel: usb-storage: Read 02 pages, from PBA 0002
(LBA 0000) page 00
Jan 22 13:03:43 zee kernel: usb-storage: Result for send_control in
read_data 0
Jan 22 13:03:43 zee kernel: usb-storage: SCM data in transfer 512 sg
buffers 0
Jan 22 13:03:43 zee kernel: usb-storage: Transfered 512 of 512 bytes
Jan 22 13:03:43 zee kernel: usb-storage: rd: 01 03 D9 01 FF 18 02 DF 01
20 04 00 00 00 00 21
Jan 22 13:03:43 zee kernel: usb-storage: rd: 02 04 01 22 02 01 01 22 03
02 04 07 1A 05 01 03
Jan 22 13:03:43 zee kernel: usb-storage: rd: 00 02 0F 1B 08 C0 C0 A1 01
55 08 00 20 1B 0A C1
Jan 22 13:03:43 zee kernel: usb-storage: scsi cmd done, result=0x0
Jan 22 13:03:43 zee kernel: usb-storage: *** thread sleeping.
Jan 22 13:03:43 zee kernel: WARNING: USB Mass Storage data integrity not
assured
Jan 22 13:03:43 zee kernel: USB Mass Storage device found at 13
Jan 22 13:03:43 zee kernel: usb.c: usb-storage driver claimed interface
c12b4560
Jan 22 13:03:43 zee kernel: usb.c: kusbd: /sbin/hotplug add 13
Jan 22 13:03:43 zee kernel: usb.c: kusbd policy returned 0xfffffffe
Sent via Deja.com
http://www.deja.com/
------------------------------
From: "ne..." <[EMAIL PROTECTED]>
Subject: Re: Newbie: Compiling Kernel
Date: Mon, 22 Jan 2001 18:33:29 GMT
On Jan 23, 2001 at 01:49, L-X-Q eloquently wrote:
>Hi,
>
>I just tried to update my kernel to 2.4.0, from RH7. I have followed all the
>instructions in Kernel-HOWTO, and also all the instructions from:
>My steps to building and installing the 2.4 kernel in Redhat 7
>http://www.linuxnewbie.org/nhf/intel/compiling/kernel2.4upgrade.html
>
>I downloaded the kernel source, the unzip it.
>Then I upgraded all the other library as written in Documention/Changes
>Then run make mrproper.
>Then make menuconfig, and set the config for the kernel.
>Then make dep, make clean, make bzImage.
Try this instead:
make mrproper menuconfig
make dep clean bzImage
It will save on the key strokes.
>Then copied the bzImage to /boot
>Then add another pointer in lilo to point to the new bzImage
>Then /sbin/lilo
>Then reboot
>
>There was no error message. My computer just hanged after displaying this
>message:
>Loading linux...........
>Uncompressing Linux... Ok, booting the kernel
>
>I have tried 3 times, with different configuration on the make menuconfig,
>but all failed. But if I boot using the old kernel, it runs smoothly. What
>happened? Please help me. Thank you very much.
Did you copy the System.map as well?
--
Registered Linux User # 125653 (http://counter.li.org)
Catch a wave and you're sitting on top of the world.
-- The Beach Boys
1:30pm up 11 days, 16:28, 10 users, load average: 0.09, 0.02, 0.01
------------------------------
From: webbgroup <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.install,linux.redhat.misc,comp.os.linux.misc
Subject: Re: Protect yourself! I got hacked by the Ramen worm
Date: Mon, 22 Jan 2001 18:34:44 GMT
Sorry you got hacked, but RedHat had fixes on their website last year
before the worm was created.
1. You should have a firewall.
2. You should read the new xinet.d man pages and why they started using
them (I don't really care whether I use inet or xinet cause I am behind
a firewall anyway)
3. Use SSH for all your ftp and telnet like connections. It is
unbelievably easy to sniff and get cleartext passwords).
4. Read the Security How-to.
In article <[EMAIL PROTECTED]>,
E J <[EMAIL PROTECTED]> wrote:
> Install the nfs, wu for RH6.2 and LPR for RH7.0 Now.
>
> Commands to update and effectively close these
> vulnerabilities on Redhat Linux 6.2 server:
> rpm -Uvh
> ftp://updates.redhat.com/6.2/i386/nfs-utils-0.1.9.1-1.i386.rpm
> rpm -Uvh
> ftp://updates.redhat.com/6.2/i386/wu-ftpd-2.6.0-14.6x.i386.rpm
>
> Commands to update and effectively close these
> vulnerabilities on Redhat Linux 7.0 server:
> rpm -Uvh
> ftp://updates.redhat.com/7.0/i386/LPRng-3.6.24-2.i386.rpm
>
> I did not do any installation of updates on RH7.0 because it was
freshly
> installed.
> I got hacked this morning. I was wondering why my hard disk was
> whirling.
> I ran 'top' and found 'find' was running.
> I turn netscape to 'http://localhost' and sure enough I was hacked by
> the Ramen worm.
> My printer does not print anymore because they exploited lpr.
> I check my security logs and found the offending computer who launched
> the attack.
> When I turned my netscape to "http://xxx.yyy.zzz.www" and looked at
> their website, it
> came with the Ramen worm webpage.
> I sent an email to CERT notifying about the hack on my computer.
> To repair the damage, I went to
> http://www.whitehats.com/library/worms/ramen/ and followed their
> instruction.
> It wiped out all of my index.html with the Ramen worm webpage.
> I had to do an upgrade of all the RH7.0 packages I installed. (2
hours
> of work)
> I had to get all personal index.html from my quite recent backup.
> I wrote to www.digitaldesk.com because they said it was a beneficial
> worm in their news story.
> What a shitty story!!!
> The Ramen work causes too much damage to my computer.
>
>
--
^*
0 0 Happy Holidays!!
( V )
Sent via Deja.com
http://www.deja.com/
------------------------------
From: "Tomas Andersen" <[EMAIL PROTECTED]>
Subject: ISDN configuration
Date: Mon, 22 Jan 2001 18:42:33 GMT
Hi!
I'm having problems configuring my ISDN card. I have installed a
ASUSCOM ISDNlink PCI card. I enclose some information that might
be useful....
I'm grateful for any help..
btw: The 'make xconfig' - "window" shows only ASUSCOM ISDNlink ISA cards..
Is it possible to use this for the PCI card as well?
I read somewhere that the HISax support must be run as a module using PCI
cards of ASUSCOM ISDNlink.
The HiSax module FAILS to install.. Does anyone have some clues??
depmod -a shows that there are unresolved symbols in modules:
/lib/modules/.../hisax.o
/lib/modules/.../isdn.o
Why is that?
Thanks in advance
Tomas Andersen
configuration in 'make xconfig'
****************************************************************************
***
ISDN subsystem:
- ISDN support yes
- Support synchronous PPP yes
- Use VJ-compression with syncronous PPP yes
- The rest of the parameters are set to no
ISDN feature submodules
- All parameters are set to no
Passive ISDN cards
- HiSax Siemens ChipSet driver support module
- HiSax Support for EURO/DSS1 yes
- ASUSCOM ISA cards yes
- The rest of the parameters are set to no
Active ISDN cards
- All parameters are set to no
terminal window output when running isdn-config:
****************************************************************************
***
Loading ISDN modules /lib/modules/2.4.0/kernel/drivers/isdn/hisax/hisax.o:
unresolved symbol register_isdn_Rsmp_e38a8833
/lib/modules/2.4.0/kernel/drivers/isdn/hisax/hisax.o: insmod
/lib/modules/2.4.0/kernel/drivers/isdn/hisax/hisax.o failed
/lib/modules/2.4.0/kernel/drivers/isdn/hisax/hisax.o: insmod hisax failed
[FAILED]
Starting isdnlog [ OK ]
Sorry - this system lacks PPP kernel support.
Check whether you configured at least the ippp0 device!
Adding provider 'Tele2' on devive 'ippp0' [ OK ]
[root@localhost /root]# modprobe -a
bash: modprobe: command not found
[root@localhost /root]# /sbin/modprobe -a
modprobe: Nothing to load ???
Specify at least a module or a wildcard like \*
[root@localhost /root]#
/var/log/messages:
****************************************************************************
***
Jan 21 14:45:13 localhost last message repeated 4 times
Jan 21 14:45:13 localhost modprobe: modprobe: Can't locate module
block-major-11
Jan 21 14:45:13 localhost modprobe: modprobe: Can't locate module
block-major-11
Jan 21 14:45:14 localhost modprobe: modprobe: Can't locate module
char-major-45
Jan 21 14:45:14 localhost modprobe:
/lib/modules/2.4.0/kernel/drivers/isdn/hisax/hisax.o: unresolved symbol
register_isdn_Rsmp_e38a8833
Jan 21 14:45:14 localhost modprobe:
/lib/modules/2.4.0/kernel/drivers/isdn/hisax/hisax.o: insmod
/lib/modules/2.4.0/kernel/drivers/isdn/hisax/hisax.o failed
Jan 21 14:45:14 localhost modprobe:
/lib/modules/2.4.0/kernel/drivers/isdn/hisax/hisax.o: insmod hisax failed
Jan 21 14:45:14 localhost isdn: Loading ISDN modules failed
Jan 21 14:45:14 localhost modprobe: modprobe: Can't locate module
char-major-45
Jan 21 14:45:14 localhost modprobe: modprobe: Can't locate module
char-major-45
Jan 21 14:45:14 localhost isdn: isdnlog startup succeeded
Jan 21 14:45:14 localhost modprobe: modprobe: Can't locate module
char-major-45
Jan 21 14:45:14 localhost last message repeated 10 times
Jan 21 14:45:14 localhost modprobe: modprobe: Can't locate module ippp0
Jan 21 14:45:14 localhost last message repeated 3 times
Jan 21 14:45:14 localhost isdn: Adding provider 'Tele2' on devive 'ippp0'
succeeded
Jan 21 14:45:14 localhost modprobe: modprobe: Can't locate module
char-major-45
Jan 21 14:45:14 localhost last message repeated 2 times
Jan 21 14:45:14 localhost modprobe: modprobe: Can't locate module
block-major-11
Jan 21 14:45:14 localhost modprobe: modprobe: Can't locate module
block-major-11
Jan 21 14:45:15 localhost modprobe: modprobe: Can't locate module
char-major-45
Jan 21 14:45:15 localhost last message repeated 4 times
Jan 21 14:45:15 localhost modprobe: modprobe: Can't locate module
block-major-11
Jan 21 14:45:16 localhost modprobe: modprobe: Can't locate module
block-major-11
Jan 21 14:45:16 localhost modprobe: modprobe: Can't locate module
char-major-45
Jan 21 14:45:16 localhost last message repeated 4 times
Jan 21 14:45:17 localhost modprobe: modprobe: Can't locate module
block-major-11
Jan 21 14:45:17 localhost modprobe: modprobe: Can't locate module
block-major-11
Jan 21 14:45:17 localhost modprobe: modprobe: Can't locate module
char-major-45
Jan 21 14:45:17 localhost last message repeated 5 times
------------------------------
From: Alois Treindl <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.install
Subject: how to duplicate a linux installation?
Date: Mon, 22 Jan 2001 19:02:26 GMT
For a web server farm, I need identical Linux (Redhat 6.2) installations
on a whole set of servers, which differ only by their IP addresses.
I would like to be able to maintain the linux system only on one of the
servers, and
push a copy of it to each of the identical machines.
Is there a how-to description somewhere how to do this in a convenient way?
Alois
------------------------------
** 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
******************************
