Linux-Misc Digest #814, Volume #26 Sun, 14 Jan 01 14:13:01 EST
Contents:
Re: 'tar' with large backup jobs / spanning tapes (Robert Jones)
Command Line Napster Client? (M.Knight)
scsi emulation problem... (Ben Bergen)
Re: scsi emulation problem... (=?ISO-8859-1?Q?Rasmus_B=F8g_Hansen?=)
Re: cdrecord problem ("Toone Mastic")
Re: Red Hat Linux 7.1 (E J)
Re: Regular Expression Question ("Jan Schaumann")
Re: Red Hat Linux 7.1 ([EMAIL PROTECTED])
Re: How do I access an old linux drive?? ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: Robert Jones <[EMAIL PROTECTED]>
Subject: Re: 'tar' with large backup jobs / spanning tapes
Date: Sun, 14 Jan 2001 12:10:11 -0600
[EMAIL PROTECTED] wrote:
> In article <[EMAIL PROTECTED]>,
> Marc Billiet <[EMAIL PROTECTED]> wrote:
> > I have no experience with it, but according to 'info tar', =93the method=
> > =20
> > 'tar' uses is not perfect, and fails on some operating systems or on som=
> > e=20
> > devices=94. The solution in that case is to use the option --tape-length=
> > .=20
> > So I suggest to try it out.
> > Note that 'info tar' seems to give more information than 'man tar'.
> >
> > Marc
>
> It's actually up the device and the device driver to return the
> correct information back to the application layer. I've had
> problems with this with every version of Unix long before linux
> even existed. It's not a problem with tar as it also occurs on
> other utilities. Only hope besides getting a differant drive is
> to see if a better driver is available or fix it yourself if you
> know kernel programming.
>
> Sent via Deja.com
> http://www.deja.com/
FWIW, the -M option *does* work on my machine. RH6.0, tar-1.12-9,
kernel 2.2.16 with integral aic7xxx driver, Adaptec 2940, (IBM) HP 35480A.
--
Meester, do you vant to buy a duck?
11:54am up 21 days, 16:13, 1 user, load average: 0.08, 0.09, 0.03
------------------------------
From: M.Knight <[EMAIL PROTECTED]>
Subject: Command Line Napster Client?
Date: Sun, 14 Jan 2001 18:06:01 GMT
I'm looking for a command line Napster client.
I've used both GTKNap and gnapster. Neither provides command line
interface.
Is there such a beast?
-Michael
--
COMBAT AIRCRAFT: A mix Michael David Knight F-4 |Phantom II
of sharp teeth, cold Gulfstream Aerospace /O\
steel, cosmic warlords, Georgia Tech Aerospace
\_______[|(.)|]_______/
and evil spirits Anti-Spam in Effect o ++ O ++ o
Sent via Deja.com
http://www.deja.com/
------------------------------
From: Ben Bergen <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat,linux.redhat.misc,comp.os.linux.setup
Subject: scsi emulation problem...
Date: Sun, 14 Jan 2001 12:15:39 -0700
I am trying to set up scsi emulation on my dell inspiron 5000e with a
SONY CD-RW CRX700E. I have compiled in emulation support, scsi support,
and scsi generic support. I am running redhat 7.0 with kernel 2.2.18.
In my lilo.conf I tell linux to ignore my cdrom as an ide device:
append="hdc=ide-scsi". I have moved the cdrom link from /dev/hdc to
/dev/scd0. When I run cdrecord -scanbus I get,
{root@taiga}->cdrecord -scanbus
Cdrecord 1.9 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg Schilling
Linux sg driver version: 2.1.39
Using libscg version 'schily-0.1'
scsibus0:
0,0,0 0) 'SONY ' 'CD-RW CRX700E ' '1.4h' Removable
CD-ROM
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
which seems fine. However, I am unable to mount the cdrom drive. When
I try I get,
{root@taiga}->mount /cdrom
mount: the kernel does not recognize /dev/cdrom as a block device
(maybe `insmod driver'?)
Am I missing a module? Or have I forgotten something. By the way, the
cdrom works fine if I treat it as an ide drive.
------------------------------
From: =?ISO-8859-1?Q?Rasmus_B=F8g_Hansen?= <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat,linux.redhat.misc,comp.os.linux.setup
Subject: Re: scsi emulation problem...
Date: Sun, 14 Jan 2001 19:26:08 +0100
On Sun, 14 Jan 2001, Ben Bergen wrote:
> {root@taiga}->mount /cdrom
> mount: the kernel does not recognize /dev/cdrom as a block device
> (maybe `insmod driver'?)
Your /dev/cdrom is probably set up wrong. It must pooint to the
appropriate scsi-cdrom - probably /dev/scd0.
Or you will have to edit your /etc/fstab to use /dev/scd0 (or whatever)
instead of /dev/cdrom.
Rasmus B�g Hansen
------------------------------
From: "Toone Mastic" <[EMAIL PROTECTED]>
Subject: Re: cdrecord problem
Crossposted-To: comp.os.linux.hardware
Date: Sun, 14 Jan 2001 18:25:06 GMT
I got the same kind of problems but when writing audio cd : linux hangs !
I use RedHat 7.0 witch use the kernel 2.2.16.
I try with the Mandrake 7.2 witch use the kernel 2.2.17 : and no problem.
So I upgrade my RedHat machine with the 2.2.18 kernel and all my problems
are resolved.
Pierre
Dans l'article <93c81k$94hb3$[EMAIL PROTECTED]>, "Mads Ipsen"
<[EMAIL PROTECTED]> a �crit :
> Dear Jorg Schilling and other SCSI wizards,
>
> I have a SCSI HP 9200 cdburner installed on my Redhat 7.0 Box. If I
> reboot the computer, CDRecord works fine and I can burn away all day.
> However, when I come to work the next day CDRecord fails. Eg. the
> command
>
> cdrecord -eject -v dev=1,6,0 blank=fast
>
> fails with with the message
>
> cdrecord: No disk / Wrong disk!
>
> and the computer has to be rebooted to retrieve a functional burning
> setup.
>
> I've been struggling quite a lot getting this to work, and I'd be really
> thankful if anybody have some suggestions on how to get things running
> in a proper fashion.
>
> The full output from
>
> cdrecord -eject -v -V dev=1,6,0 blank=fast
>
> is included below in this posting,
>
> +------------------------------------------------------------------+
> | Mads Ipsen | |
> | Dept. of Physical Chemistry | phone: +49-30-8413 5302 |
> | Fritz-Haber-Institut der MPG | fax: +49-30-8413 5106 |
> | Faradayweg 4-6, 14195 Berlin, Germany | [EMAIL PROTECTED] |
> +------------------------------------------------------------------+
>
>
>
> Cdrecord 1.8.1 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg
> Schilling TOC Type: 1 = CD-ROM scsidev: '1,6,0' scsibus: 1 target: 6
> lun: 0 Using libscg version 'schily-0.1' atapi: 0
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.007s timeout 40s
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.009s timeout 40s
>
> Executing 'inquiry' command on Bus 1 Target 6, Lun 0 timeout 40s CDB:
> 12 00 00 00 24 00 cmd finished after 0.002s timeout 40s Inquiry Data :
> 05 80 04 02 5B 00 00 10 48 50 20 20 20 20 20 20 43 44 2D
> 57 72 69 74 65 72 2B 20 39 32 30 30 20 31 2E 30 63
>
> Executing 'inquiry' command on Bus 1 Target 6, Lun 0 timeout 40s CDB:
> 12 00 00 00 60 00 cmd finished after 0.002s timeout 40s Inquiry Data :
> 05 80 04 02 5B 00 00 10 48 50 20 20 20 20 20 20 43 44 2D
> 57 72 69 74 65 72 2B 20 39 32 30 30 20 31 2E 30 63 20 4F 63 74 32 39 20
> 2C
> 20 20 4D 59 39 35 30 35 39 52 31 55 00 00 00 00 00 00 00 00 00 00 00 00
> 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00
> 00 00
> Inquiry Data : ....[...HP CD-Writer+ 9200 1.0c Oct29 ,
> MY95059R1U........................................
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 3F 00 00 00 00 00 08 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 E0 70 00 00 00 00 08
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.002s timeout 40s
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 02 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 Mode Sense Data (converted) 25
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.00A 00 2A 00 00
> 00 00 00 02 00 cmd finished after 0.001s timeout 40s Mode Sense Data 00
> 28 Mode Sense Data (converted) 25
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 70 00 00 00 00 08 00 00 00 00 00 00 08 00 2A
> 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data (converted) 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07 07 71 63 29
> 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Page Data 2A 18 07 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05
> 83 02 C2 00 00 00 00
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 70 00 00 00 00 08 00 00 00 00 00 00 08 00 2A
> 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data (converted) 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07 07 71 63 29
> 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.005s timeout 40s
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 02 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 Mode Sense Data (converted) 25
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 70 00 00 00 00 08 00 00 00 00 00 00 08 00 2A
> 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data (converted) 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07 07 71 63 29
> 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Page Data 2A 18 07 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05
> 83 02 C2 00 00 00 00
>
> Executing 'mode sense g1' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5A 00 2A 00 00 00 00 00 2A 00 cmd finished after 0.001s timeout
> 40s Mode Sense Data 00 28 70 00 00 00 00 08 00 00 00 00 00 00 08 00 2A
> 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data (converted) 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07
> 07 71 63 29 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Mode Sense Data 25 70 00 08 00 00 00 00 00 00 08 00 2A 18 07 07 71 63 29
> 23 16 0D 01 00 10 00 16 0D 00 00 05 83 02 C2 00 00 00 00
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags :
> SWABAUDIO
>
> Executing 'read buffer cap' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 5C 00 00 00 00 00 00 00 0C 00 cmd finished after 0.000s timeout
> 40s BFree: 4085 K BSize: 4085 K Drive buf size : 4183808 = 4085 KB
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.004s timeout 40s
>
> Executing 'start/stop unit' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 1B 00 00 00 03 00 cmd finished after 0.001s timeout 40s
>
> Executing 'start/stop unit' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 1B 00 00 00 01 00 cdrecord: Input/output error. start/stop unit:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 1B 00
> 00 00 01 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.008s timeout 40s
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.009s timeout 40s
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.009s timeout 40s
>
> Executing 'test unit ready' command on Bus 1 Target 6, Lun 0 timeout 40s
> CDB: 00 00 00 00 00 00 cdrecord: Input/output error. test unit ready:
> scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION) CDB: 00 00
> 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00 30 00 00 00
> Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual 0x00
> (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not valid)
> cmd finished after 0.009s timeout 40s cdrecord: Input/output error. test
> unit ready: scsi sendcmd: retryable error status: 0x2 (CHECK CONDITION)
> CDB: 00 00 00 00 00 00 Sense Bytes: 70 00 02 00 00 00 00 12 00 00 00 00
> 30 00 00 00 Sense Key: 0x2 Not Ready, Segment 0 Sense Code: 0x30 Qual
> 0x00 (incompatible medium installed) Fru 0x0 Sense flags: Blk 0 (not
> valid)
>
> Executing 'prevent/allow medium removal' command on Bus 1 Target 6, Lun
> 0 timeout 40s CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout
> 40s cdrecord: No disk / Wrong disk!
------------------------------
From: E J <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.misc,redhat.general
Subject: Re: Red Hat Linux 7.1
Date: Sun, 14 Jan 2001 18:30:07 GMT
First quarter of 2001: codename Florence probably includes kernel 2.4.x
rick wrote:
> Any estimated release date for rh 7.1?
>
> thx
------------------------------
From: "Jan Schaumann" <[EMAIL PROTECTED]>
Subject: Re: Regular Expression Question
Date: Sun, 14 Jan 2001 13:42:03 -0500
* "Bob Simon" <[EMAIL PROTECTED]> wrote:
> In article <EVk86.4285$[EMAIL PROTECTED]>,
> "Jan Schaumann" <[EMAIL PROTECTED]> wrote:
>
>> B/c RE's are (usually (always?)) greedy. That means, they match the
>> very first instance they encounter.
>>
>> I) [A-Za-z]* II) [A-Za-z][A-Za-z]*
>> ---a-- ----b---
>>
>> (I) will start and when it encounters the empty string, it
>> matches (0 or more alpha-chars) and terminates.
>
> Jan, I don't doubt that you're right and I certainly observe it to work
> that way. But this "greedy" behavior contradicts the rule that regular
> expressions match the LONGEST string of characters that match the
> pattern. Is my understanding of this
> "rule" wrong?
I think greedyness supersedes matching the longest.
The RE is greedy, that is, it tries to match first, without looking ahead
if something lateron might match that might theoretically be a better
match. The first match in (I) is the empty string. The RE is matched and
the RE's done, as far at it's concerned. It does not further invesiogate
any other characters, it does not care that after the empty string there
might a long, long word that has more characters which it could match.
(I) said "0 or more", thus the RE's satisfied with 0 and happily
terminates.
(II), as exlpained, matches "one or more", and thus will happily
terminate if it encounteres a string containing at least one
alpha-character. Again, the RE does not care that there could be other,
longer (thus, maybe, "better") matches.
Hmm, this does not explain why you would want it to match the LONGEST
possibility - so I quickly grabbed my Camel-book and can quote:
[...] when someone trots out a stock phrase like "left-most,
longest match", you'll know that overall Perl prefers left-most
over the longest.
This, of course, only goes for Perl. I think the real RE-experts sit in
comp.lang.perl.misc and possibly in comp.os.linux.dev Maybe pose your
question there.
>> Please change your signature-delimiter to "-- ".
>
> What are you seeing as my delimiter? It looks like "-- " to me. I think
> that deja supplies these dashes when I post through them.
It's "--" (no space after the dashes). Might be a deja-thing, true.
Anyway, HTH,
-Jan
--
Jan Schaumann <http://www.netmeister.org>
$ drink <bottle; opener
bottle: cannot open
opener: not found
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Red Hat Linux 7.1
Date: Sun, 14 Jan 2001 18:47:01 GMT
Robert Spangler <[EMAIL PROTECTED]> writes:
> On Sun, 14 Jan 2001 07:03:48 -0900, rick wrote:
>
> > Any estimated release date for rh 7.1?
>
> What would interest me more is if RH is going to add the 2.4 kernel to the
> 7.x or wait until 8.x?
That's an interesting question. 'Tis not clear whether it is more
likely in their interests to:
a) Release a 7.1 version, conforming with "tradition," that would
refresh XFree86, probably include 2.4, and have the "warm fuzzies"
normally associated with the notion that "Oh, RHAT has decided to
stabilize their unstable .0 release producing a .1 release."
[That was pretty much a valid way of looking at the evolutions of
4.x, 5.x, and 6.x, and 7.0 was unstable enough to hold onto the
theory...]
b) Release a new "Red Hat Version 8" with all the fixes suggested
above.
It's coming about the usual time for a .1 release, if a) be the
strategy...
--
(concatenate 'string "aa454" "@freenet.carleton.ca")
<http://www.ntlug.org/~cbbrowne/>
"Starting a project in C/C++ is a premature optimization."
-- Peter Jensen
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: How do I access an old linux drive??
Date: Sun, 14 Jan 2001 18:47:12 GMT
[EMAIL PROTECTED] writes:
> I have installed a new harddrive in my computer and set up RH7 on
> it. I would like to get the inforamtion off my old drive but how do
> I do this?
> I have mounted the old drive as /old but when I cd into that
> directory, I get a bunch of System.map, boot.b, vmlinuz files and
> only one dir...lost+found. I would have exected to see /old/bin,
> /old/home, /old/usr etc....
> Is is possible to get at my data in this fashion? Please let me
> know.
It _should_ be; it sounds as if the old drive has multiple partitions
and that all you are mounting is what used to be the /boot partition.
You might run:
# fdisk -l
which will list all the partitions on your drives. You may need to be
more specific, and do:
# fdisk -l /dev/hda
or
# fdisk -l /dev/hdb
This is likely to list multiple partitions, perhaps something like
the following:
Disk /dev/hda: 255 heads, 63 sectors, 4865 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 2 16033+ 83 Linux
/dev/hda2 3 385 3076447+ 83 Linux
/dev/hda3 386 516 1052257+ 82 Linux swap
/dev/hda4 * 517 4865 34933342+ 5 Extended
/dev/hda5 517 601 682731 83 Linux
/dev/hda6 602 686 682731 83 Linux
/dev/hda7 687 1069 3076416 83 Linux
/dev/hda8 1070 1154 682731 83 Linux
/dev/hda9 1155 1239 682731 83 Linux
/dev/hda10 1240 1622 3076416 83 Linux
/dev/hda11 1623 1707 682731 83 Linux
/dev/hda12 1708 2090 3076416 83 Linux
/dev/hda13 2091 2473 3076416 83 Linux
You would then mount several of the partitions individually under your
favorite mount points.
Perhaps something like:
# mount -t /old /dev/hda1
# mount -t /old/usr /dev/hda2
# mount -t /old/home /dev/hda3
# mount -t /old/boot /dev/hda4
.. and so on ...
Precisely what to mount where depends on how the old drive was
partitioned, and how you arranged the partitions.
You may add entries to /etc/fstab to allow these partitions to be
mounted by default at boot time, if you so desire; you'd create
entries analagous to the ones already there for the RH7 partitions.
--
(concatenate 'string "aa454" "@freenet.carleton.ca")
<http://www.ntlug.org/~cbbrowne/>
"Starting a project in C/C++ is a premature optimization."
-- Peter Jensen
------------------------------
** 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.misc.
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
******************************
