Linux-Misc Digest #177, Volume #21 Mon, 26 Jul 99 23:13:07 EDT
Contents:
Re: cdrecord error (Peter Buelow)
Need script to convert filenames from UPPER to lower ("Christopher R. Carlen")
Re: Bootable Cd for Linux ("Andrew J. Norman")
Quake under Mandrake 6 (Josh Morris)
Re: Recommendations: PPP+Proxy+POP (Christopher Browne)
Toronto + Rogers@home + RH 6 (Andrew)
Re: Need script to convert filenames from UPPER to lower (Christopher B. Browne)
----------------------------------------------------------------------------
From: Peter Buelow <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: cdrecord error
Date: Mon, 26 Jul 1999 19:58:22 -0500
Matt Garman wrote:
> Hello:
>
> I'm using Debian 2.1 Linux, trying to burn CDs using cdrecord v1.6
> (the Debian packaged one) and a internal Plextor PlexWriter 4/12 SCSI
> cd burner.
>
> Initially, it worked perfectly, always. Recently, though, it's been
> coming up with random errors. These errors may not come up on a dummy
> write, but will happen when I try to do the actual burn. Sometimes
> the errors show up on the dummy burn, too.
>
> Here is a script output of me doing a few dummy burns:
>
> Script started on Sat Jul 24 23:47:51 1999
> sh-2.01# nice -n -20 cdrecod rd -v speed=4 dev=0,4,0 -audio -dummy *.wav
> Cdrecord release 1.6 Copyright (C) 1995-1998 J�rg Schilling
> TOC Type: 0 = CD-DA
> scsidev: '0,4,0'
> scsibus: 0 target: 4 lun: 0
> Device type : Removable CD-ROM
> Version : 2
> Response Format: 2
> Capabilities : SYNC LINKED
> Vendor_info : 'PLEXTOR '
> Identifikation : 'CD-R PX-R412C '
> Revision : '1.04'
> Device seems to be: Generic mmc CD-R.
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> Driver flags : SWABAUDIO
> Track 01: audio 53 MB (05:18.02) no preemp
> Track 02: audio 38 MB (03:49.20) no preemp
> Track 03: audio 80 MB (07:56.21) no preemp
> Track 04: audio 47 MB (04:43.72) no preemp
> Track 05: audio 54 MB (05:21.96) no preemp
> Total size: 275 MB (27:17.12) = 122784 sectors
> Lout start: 275 MB (27:19/09) = 122784 sectors
> ATIP info from disk:
> Indicated writing power: 4
> Is unrestricted
> Is not erasable
> ATIP start of lead in: -11580 (97:27/45)
> ATIP start of lead out: 333226 (74:05/01)
> Disk type: Phthalocyanine or similar
> Manufacturer: Kodak Japan Limited
> Blocks total: 333226 Blocks remaining: 21988
> cdrecord: WARNING: Data may not fit on current disk.
> Starting to write CD at speed 4 in dummy mode for single session.
> Last chance to quit, starting dummy write in 9 seconds.
> Waiting for reader process to fill input-buffer ... input-buffer ready.
> Starting new track at sector: 311238
> Track 01: 0 of 53 MB written.
> Track 01: 1 of 53 MB written (fifo
> 99%).
> Track 01: 2 of 53 MB written (fifo 99%).
> Track 01: 3 of
> 53 MB written (fifo 100%).
> Track 01: 4 of 53 MB written (fifo
> 99%).
> Track 01: 5 of 53 MB written (fifo 99%).
> Track 01: 6 of
> 53 MB written (fifo 100%).
> Track 01: 7 of 53 MB written (fifo
> 100%).
> Track 01: 8 of 53 MB written (fifo 100%).
> Track 01: 9 of
> 53 MB written (fifo 100%).
> Track 01: 10 of 53 MB written (fifo
> 100%).
> Track 01: 11 of 53 MB written (fifo 99%).
> Track 01: 12 of
> 53 MB written (fifo 100%).
> Track 01: 13 of 53 MB written (fifo
> 100%).
> Track 01: 14 of 53 MB written (fifo 99%).
> Track 01: 15 of
> 53 MB written (fifo 100%).
> Track 01: 16 of 53 MB written (fifo
> 99%).
> Track 01: 17 of 53 MB written (fifo 99%).
> Track 01: 18 of
> 53 MB written (fifo 100%).
> Track 01: 19 of 53 MB written (fifo
> 100%).
> Track 01: 20 of 53 MB written (fifo 100%).
> Track 01: 21 of
> 53 MB written (fifo 100%).
> Track 01: 22 of 53 MB written (fifo
> 100%).
> Track 01: 23 of 53 MB written (fifo 100%).
> Track 01: 24 of
> 53 MB written (fifo 100%).
> Track 01: 25 of 53 MB written (fifo
> 100%).
> Track 01: 26 of 53 MB written (fifo 100%).
> Track 01: 27 of
> 53 MB written (fifo 100%).
> Track 01: 28 of 53 MB written (fifo
> 100%).
> Track 01: 29 of 53 MB written (fifo 100%).
> Track 01: 30 of
> 53 MB written (fifo 100%).
> Track 01: 31 of 53 MB written (fifo
> 100%).
> Track 01: 32 of 53 MB written (fifo 99%).
> Track 01: 33 of
> 53 MB written (fifo 100%).
> Track 01: 34 of 53 MB written (fifo
> 100%).
> Track 01: 35 of 53 MB written (fifo 99%).
> Track 01: 36 of
> 53 MB written (fifo 100%).
> Track 01: 37 of 53 MB written (fifo
> 99%).
> Track 01: 38 of 53 MB written (fifo 100%).
> Track 01: 39 of
> 53 MB written (fifo 99%).
> Track 01: 40 of 53 MB written (fifo
> 99%).
> Track 01: 41 of 53 MB written (fifo 100%).
> Track 01: 42 of
> 53 MB written (fifo 100%).
> Track 01: 43 of 53 MB written (fifo
> 100%).
> Track 01: 44 of 53 MB written (fifo 99%).
> Track 01: 45 of
> 53 MB written (fifo 100%).
> Track 01: 46 of 53 MB written (fifo
> 99%).
> Track 01: 47 of 53 MB written (fifo 100%).
> Track 01: 48 of
> 53 MB written (fifo 100%).
> Track 01: 49 of 53 MB written (fifo
> 100%).
> cdrecord: Success. write_g1: scsi sendcmd: retryable error
> CDB: 2A 00 00 05 15 A5 00 00 0D 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 0A 00 00
> Sense Key: 0x9 Vendor Unique, Segment 0
> Sense Code: 0x80 Qual 0x0A (limited laser life) [No matching qualifier] Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.002s timeout 40s
>
> write track data: error after 51704016 bytes
> Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
> Writing time: 80.402s
> Fixating...
> WARNING: Some drives don't like fixation in dummy mode.
> cdrecord: Success. close track/session: scsi sendcmd: retryable error
> CDB: 5B 00 02 00 00 00 00 00 00 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 01 00 00
> Sense Key: 0x9 Vendor Unique, Segment 0
> Sense Code: 0x80 Qual 0x01 (limited laser life) [No matching qualifier] Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.001s timeout 480s
> Fixating time: 0.003s
> cdrecord: fifo had 1819 puts and 1692 gets.
> cdrecord: fifo was 0 times empty and 1094 times full, min fill was 96%.
> sh-2.01# nice -n -20 cdrecord -v speed=4 dev=0,4,0 -audio -dummy *.wav
> Cdrecord release 1.6 Copyright (C) 1995-1998 J�rg Schilling
> TOC Type: 0 = CD-DA
> scsidev: '0,4,0'
> scsibus: 0 target: 4 lun: 0
> Device type : Removable CD-ROM
> Version : 2
> Response Format: 2
> Capabilities : SYNC LINKED
> Vendor_info : 'PLEXTOR '
> Identifikation : 'CD-R PX-R412C '
> Revision : '1.04'
> Device seems to be: Generic mmc CD-R.
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> Driver flags : SWABAUDIO
> Track 01: audio 53 MB (05:18.02) no preemp
> Track 02: audio 38 MB (03:49.20) no preemp
> Track 03: audio 80 MB (07:56.21) no preemp
> Track 04: audio 47 MB (04:43.72) no preemp
> Track 05: audio 54 MB (05:21.96) no preemp
> Total size: 275 MB (27:17.12) = 122784 sectors
> Lout start: 275 MB (27:19/09) = 122784 sectors
> ATIP info from disk:
> Indicated writing power: 4
> Is unrestricted
> Is not erasable
> ATIP start of lead in: -11580 (97:27/45)
> ATIP start of lead out: 333226 (74:05/01)
> Disk type: Phthalocyanine or similar
> Manufacturer: Kodak Japan Limited
> Blocks total: 333226 Blocks remaining: 21988
> cdrecord: WARNING: Data may not fit on current disk.
> Starting to write CD at speed 4 in dummy mode for single session.
> Last chance to quit, starting dummy write in 9 seconds.
> Waiting for reader process to fill input-buffer ... input-buffer ready.
> Starting new track at sector: 311238
> Track 01: 0 of 53 MB written.
> Track 01: 1 of 53 MB written (fifo
> 99%).
> Track 01: 2 of 53 MB written (fifo 99%).
> Track 01: 3 of
> ...
> 53 MB written (fifo 100%).
> Track 01: 49 of 53 MB written (fifo
> 100%).
> cdrecord: Success. write_g1: scsi sendcmd: retryable error
> CDB: 2A 00 00 05 15 A5 00 00 0D 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 0A 00 00
> Sense Key: 0x9 Vendor Unique, Segment 0
> Sense Code: 0x80 Qual 0x0A (limited laser life) [No matching qualifier] Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.002s timeout 40s
>
> write track data: error after 51704016 bytes
> Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
> Writing time: 80.362s
> Fixating...
> WARNING: Some drives don't like fixation in dummy mode.
> cdrecord: Success. close track/session: scsi sendcmd: retryable error
> CDB: 5B 00 02 00 00 00 00 00 00 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 01 00 00
> Sense Key: 0x9 Vendor Unique, Segment 0
> Sense Code: 0x80 Qual 0x01 (limited laser life) [No matching qualifier] Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.000s timeout 480s
> Fixating time: 0.002s
> cdrecord: fifo had 1819 puts and 1692 gets.
> cdrecord: fifo was 0 times empty and 931 times full, min fill was 97%.
> sh-2.01# nice -n -20 cdrecord -v speed=4 dev=0,4,0 -audio -dummy *.wav
> Cdrecord release 1.6 Copyright (C) 1995-1998 J�rg Schilling
> TOC Type: 0 = CD-DA
> scsidev: '0,4,0'
> scsibus: 0 target: 4 lun: 0
> Device type : Removable CD-ROM
> Version : 2
> Response Format: 2
> Capabilities : SYNC LINKED
> Vendor_info : 'PLEXTOR '
> Identifikation : 'CD-R PX-R412C '
> Revision : '1.04'
> Device seems to be: Generic mmc CD-R.
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> Driver flags : SWABAUDIO
> Track 01: audio 53 MB (05:18.02) no preemp
> Track 02: audio 38 MB (03:49.20) no preemp
> Track 03: audio 80 MB (07:56.21) no preemp
> Track 04: audio 47 MB (04:43.72) no preemp
> Track 05: audio 54 MB (05:21.96) no preemp
> Total size: 275 MB (27:17.12) = 122784 sectors
> Lout start: 275 MB (27:19/09) = 122784 sectors
> ATIP info from disk:
> Indicated writing power: 4
> Is unrestricted
> Is not erasable
> ATIP start of lead in: -11580 (97:27/45)
> ATIP start of lead out: 333226 (74:05/01)
> Disk type: Phthalocyanine or similar
> Manufacturer: Kodak Japan Limited
> Blocks total: 333226 Blocks remaining: 333226
> Starting to write CD at speed 4 in dummy mode for single session.
> Last chance to quit, starting dummy write in 9 seconds.
> Waiting for reader process to fill input-buffer ... input-buffer ready.
> Starting new track at sector: 0
> Track 01: 0 of 53 MB written.
> Track 01: 1 of 53 MB written (fifo
> 99%).
> Track 01: 2 of 53 MB written (fifo 99%).
> Track 01: 3 of
> 53 MB written (fifo 100%).
> Track 01: 4 of 53 MB written (fifo
> ...
> 99%).
> Track 01: 50 of 53 MB written (fifo 100%).
> Track 01: 51 of
> 53 MB written (fifo 100%).
> Track 01: 52 of 53 MB written (fifo
> 100%).
> Track 01: 53 of 53 MB written (fifo 99%).
> Track 01: Total bytes read/written: 56099904/56099904 (23852 sectors).
> Starting new track at sector: 24004
> Track 02: 0 of 38 MB written.
> Track 02: 1 of 38 MB written (fifo
> 99%).
> Track 02: 2 of 38 MB written (fifo 99%).
> Track 02: 3 of
> 38 MB written (fifo 98%).
> Track 02: 4 of 38 MB written (fifo
> ...
> 38 MB written (fifo 100%).
> Track 02: 34 of 38 MB written (fifo
> 100%).
> Track 02: 35 of 38 MB written (fifo 98%).
> Track 02: 36 of
> 38 MB written (fifo 100%).
> Track 02: 37 of 38 MB written (fifo 100%).
> Track 02: 38 of 38 MB
> written (fifo 100%).
> Track 02: Total bytes read/written: 40430880/40430880 (17190 sectors).
> Starting new track at sector: 41346
> Track 03: 0 of 80 MB written.
> Track 03: 1 of 80 MB written (fifo
> 99%).
> Track 03: 2 of 80 MB written (fifo 99%).
> Track 03: 3 of
> 80 MB written (fifo 98%).
> Track 03: 4 of 80 MB written (fifo
> ...
> 99%).
> Track 03: 77 of 80 MB written (fifo 100%).
> Track 03: 78 of
> 80 MB written (fifo 100%).
> Track 03: 79 of 80 MB written (fifo
> 100%).
> Track 03: 80 of 80 MB written (fifo 100%).
> Track 03: Total bytes read/written: 84004032/84004032 (35716 sectors).
> Starting new track at sector: 77214
> Track 04: 0 of 47 MB written.
> Track 04: 1 of 47 MB written (fifo
> 99%).
> Track 04: 2 of 47 MB written (fifo 100%).
> Track 04: 3 of
> 47 MB written (fifo 100%).
> Track 04: 4 of 47 MB written (fifo
> 100%).
> Track 04: 5 of 47 MB written (fifo 100%).
> Track 04: 6 of
> ...
> 47 MB written (fifo 99%).
> Track 04: 43 of 47 MB written (fifo
> 100%).
> Track 04: 44 of 47 MB written (fifo 99%).
> Track 04: 45 of
> 47 MB written (fifo 100%).
> Track 04: 46 of 47 MB written (fifo
> 100%).
> Track 04: 47 of 47 MB written (fifo 100%).
> Track 04: Total bytes read/written: 50048208/50048208 (21279 sectors).
> Starting new track at sector: 98645
> Track 05: 0 of 54 MB written.
> Track 05: 1 of 54 MB written (fifo
> 99%).
> Track 05: 2 of 54 MB written (fifo 99%).
> Track 05: 3 of
> ...
> 54 MB written (fifo 100%).
> Track 05: 52 of 54 MB written (fifo
> 100%).
> Track 05: 53 of 54 MB written (fifo 100%).
> Track 05: 54 of 54 MB written (fifo 100%).
> Track 05: Total bytes read/written: 56793744/56793744 (24147 sectors).
> Writing time: 435.019s
> Fixating...
> WARNING: Some drives don't like fixation in dummy mode.
> cdrecord: Success. close track/session: scsi sendcmd: retryable error
> CDB: 5B 00 02 00 00 00 00 00 00 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 09 00 00 00 00 0A 00 00 00 00 80 01 00 00
> Sense Key: 0x9 Vendor Unique, Segment 0
> Sense Code: 0x80 Qual 0x01 (limited laser life) [No matching qualifier] Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.000s timeout 480s
> Fixating time: 0.003s
> cdrecord: fifo had 9401 puts and 9401 gets.
> cdrecord: fifo was 0 times empty and 5666 times full, min fill was 91%.
> sh-2.01# exit
>
> Script done on Sun Jul 25 00:27:08 1999
>
> --
> Matt Garman, [EMAIL PROTECTED]
> "And through the window in the wall
> Come streaming in on sunlight wings
> A million bright ambassadors of morning."
> --Pink Floyd, "Echoes"
I can think of two things that would cause a CDR to start to wig out. One is bad
disks. Are all these errors coming from the same batch of disks? There getting
cheaper and I am finding that it is no easy to buy a large batch of disks and hope
that they all work. A bad disk can cause all sorts of errors. Two would be dust in
the unit. Get a can of compressed air and blow the thing out. I don't know if I
can recommend a cleaning tool, I've never used one, but I won't trust anything
that might accidentally scratch the lens. Either way, intermittent errors that
become more frequent are usually hardware. Check the cable and clean it is my best
advice if the disks are definately not the source of the problem.
If all else fails, try using cdrtoaster and see what happens. Otherwise, good
luck.
Peter Buelow
------------------------------
From: "Christopher R. Carlen" <[EMAIL PROTECTED]>
Subject: Need script to convert filenames from UPPER to lower
Date: Mon, 26 Jul 1999 20:05:34 -0400
I have a zipped bunch of files downloaded from a software vendor. All
the files have UPPERCASE names. But the program that reads them only
accepts lowercase names. Thus, I must either rename them all by hand,
one at a time (impossible), or get some command or small script to do
it.
Since I am not anymore a programmer, I think some script guru can
provide the needed lines in minutes, where I would require hours to cook
them up.
Anybody got the answer?
Thanks.
_____________________________
Christopher R. Carlen
[EMAIL PROTECTED]
My OS is Linux 2.0.29
------------------------------
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
From: "Andrew J. Norman" <[EMAIL PROTECTED]>
Subject: Re: Bootable Cd for Linux
Date: Tue, 27 Jul 1999 01:24:50 GMT
=====BEGIN PGP SIGNED MESSAGE=====
The standard "mkisofs" package will support "El Torito" bootable CDs. To
use this simply create a boot image (ussual a floppy disk which you can
dd into a image file) after you have this simply follow the directions in
the manpage (for mkisofs) and you can create the CD image. To write it to
a disk consider one of the many CDR packages (cdrecord or cdwrite or....)
which will burn your image onto your disk.
Andrew J. Norman
______________________________________________________________
Dept. of Physics Phone: 757-221-3571
College of William & Mary [EMAIL PROTECTED]
"It is only with the heart that one can see rightly;
what is essential is invisible to the eye" -The Little Prince
______________________________________________________________
On Mon, 26 Jul 1999, Bruno Quesnel wrote:
> I'm interested in doing bootable images of custom distribution for the
> companies site for install and recovery plan.
>
> Can someone tel me of a piece of software or methode to make this
> possible.
>
> Thanks in advance
>
> --
> Unix is user-friendly; it's just a little particular about which
> users it is friendly to.
>
> Bruno Quesnel [EMAIL PROTECTED]
> Genie Electrique [EMAIL PROTECTED]
> Electrical engineering VA2 BMG
> Ecole de technologie Superieure
>
>
>
=====BEGIN PGP SIGNATURE=====
Version: 2.6.3i
Charset: noconv
iQCVAwUBN50KYiRqxyk0Hh01AQFQAgP+P/VKUHPFXzuELnBCHVb8aeJ83ojq0jug
nYtpfUOgdcT/J4grsMj8FEqx1ETKuNTQoJ50MkQcvU0OqjAuRLL4N7jjTaydAa9/
fKfb5WVJzM5PVoDM657qnyYL1F28VNvFzya9yRKHozKLRNz/trQtHW9Mg1ZVhzVD
fivbZTWGZZQ=
=1gAl
=====END PGP SIGNATURE=====
------------------------------
From: Josh Morris <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.mandrake
Subject: Quake under Mandrake 6
Date: Mon, 26 Jul 1999 21:35:07 -0400
I recently installed Mandrake 6 on my system (clean install), and I've
run into just a couple of snafu's. The first one I noticed was that
running sndconfig with my Ensoniq PCI card (es1371) produces an error
when trying to play the sample (sox error). I can still here sound in
certain things like a CD player, kpoker, etc. That's not very important
since I here some stuff, but future adventures in Linux may be hampered
by this. The second problem is that I can't play Quake. The screen
goes blank and nothing appears to be happening in the background. The
other virtual terminals are blank as well. I can switch to another
virtual terminal and do the DOS three finger salute to reboot, but this
is really not what I want to do with this nice commercial game package.
I seem to fit all the requirements. I've upgraded to kernel 2.2.10, and
I have svga libraries (libvga.so.1.4.0) and glibc 2.1. Im trying to run
the svga version. The X11 version runs, but far below what I'd consider
decent performance. I have a Matrox Millenium G200 card. Everything
worked under RedHat 5.2 and Debian 2.1. Anyone know what's causing the
problems. I would think that maybe the glibc2.1 libs were the problem
since I heard about programs designed for glibc2 have problems with 2.1.
Any feedback is appreciated. Thanks.
***********************************
Josh Morris
[EMAIL PROTECTED]
[EMAIL PROTECTED]
PGP Keys for personal use
***********************************
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Subject: Re: Recommendations: PPP+Proxy+POP
Reply-To: [EMAIL PROTECTED]
Date: Tue, 27 Jul 1999 00:38:35 GMT
On Mon, 26 Jul 1999 20:28:29 GMT, Clay <[EMAIL PROTECTED]> wrote:
>We have a small office (20 stations), and I would like to implement a
>RedHat machine that will give everyone access to the internet through a
>Proxy+PPP (we have a dedicated dialup account with a local ISP). Also I
>would like to have an internal POP server for internal messaging, but I
>would also like for everyone to be able to access their own personal
>email accounts through the proxy.
>
>I would appreciate any recommendations on software and/or setup ideas
>(I have never setup anything like this before).
- You might want to consider, as an alternative, using an IMAP server
on the proxy box, as it is a more featureful protocol that is
increasingly supported. This would give you better control over the
mail, as it would primarily reside on *your* box, rather than on the
ISP's boxes.
- Install Squid on the proxy box; this will provide the ability to:
a) Log/Control what people get to web out to, and
b) Reduce the amount of data that goes on the outside pipeline by
cacheing it locally.
- The *big* issue that you'll have is in making sure that all your
people have individual mail identification *at the ISP.*
--
I called that number and they said whom the Lord loveth he chasteneth.
[EMAIL PROTECTED] <http://www.ntlug.org/~cbbrowne/internet.html>
------------------------------
From: Andrew <[EMAIL PROTECTED]>
Subject: Toronto + Rogers@home + RH 6
Date: Tue, 27 Jul 1999 02:50:11 +0100
Anybody know if the Canadian 'Rogers@home' cable internet service will
work okay with linux? I know some people who are getting it and may be
getting Linux on their computer, but want to know if it will work.
Please reply by email - as I can't check this newsgroup that often.
Thanks,
Andrew
(email - [EMAIL PROTECTED] )
------------------------------
From: [EMAIL PROTECTED] (Christopher B. Browne)
Subject: Re: Need script to convert filenames from UPPER to lower
Reply-To: [EMAIL PROTECTED]
Date: Tue, 27 Jul 1999 02:05:27 GMT
On Mon, 26 Jul 1999 20:05:34 -0400, Christopher R. Carlen
<[EMAIL PROTECTED]> posted:
>I have a zipped bunch of files downloaded from a software vendor. All
>the files have UPPERCASE names. But the program that reads them only
>accepts lowercase names. Thus, I must either rename them all by hand,
>one at a time (impossible), or get some command or small script to do
>it.
>
>Since I am not anymore a programmer, I think some script guru can
>provide the needed lines in minutes, where I would require hours to cook
>them up.
>
>Anybody got the answer?
Take the file, let's say, UPPERLIST.txt.
Run the command:
tr '[:upper:]' '[:lower:]' < UPPERLIST.txt > lowerlist.txt
Voila.
--
When I shop for hardware I always look for the "Designed for Windows 95" logo.
I really thank MICROS~1(TM) for encouraging manufacturers to label their
products this way, so I know what to AVOID.
[EMAIL PROTECTED] <http://www.ntlug.org/~cbbrowne/unix.html>
------------------------------
** 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
******************************
