Linux-Misc Digest #157, Volume #21 Sun, 25 Jul 99 14:13:09 EDT
Contents:
cdrecord error (Matt Garman)
Re: using Condor checkpointing on linux.... (Mark Brown)
Re: AMD processor upgrade ("Nevyn")
Re: Need opinions- how's S.u.S.E. 6.1 (Michael Hasenstein)
Mounting NTFS in OpenLinux (Murphy)
Re: redhat vs suse (Lev Babiev)
Re: Linux driver for ESS solo-1 sound chip (Rod Roark)
Re: sound problems (Ken Corbin)
Re: Where is NULL/__null? (John Winters)
Re: cp -r versus cp -R (William Burrow)
Re: C question (fred smith)
Re: cp -r versus cp -R ("R.K.Aa")
Re: weird ping (Jerrad Pierce)
Re: xterm: scrolling up and down (Gary Momarison)
Re: spin down HDD (Simon Hosie)
Re: embracing humanity's parasitic nature ("Kelly Robinson")
MP3 Tag Editor (Patrick M. Geahan)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Matt Garman)
Crossposted-To: comp.os.linux.hardware
Subject: cdrecord error
Date: 25 Jul 1999 05:35:57 GMT
Reply-To: [EMAIL PROTECTED]
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"
------------------------------
From: Mark Brown <[EMAIL PROTECTED]>
Subject: Re: using Condor checkpointing on linux....
Date: 25 Jul 1999 17:08:03 +0100
Pratap Arangil <[EMAIL PROTECTED]> writes:
> I'd like to know if anybody has used Condor to checkpoint an MPI
> application on linux 2.0.32. I'm trying to use the standalone
> checkpointing feature offered by Condor but I'm unable to use
> condor_compile to compile an MPI application. In other words I'm not able
> to use condor_compile with mpicc. I've read most of the manual but I have
> not come across any information regarding this feature. If anybody has
> used Condor with MPI please let me know your experiences. Otherwise, if
> anybody has any ideas or pointers on how to checkpoint an MPI application
> I'm all ears.
I'd suggest asking in somewhere like comp.parallel.mpi or the Beowulf
mailing lists rather than here - this is quite specialist stuff. In
any case, you need to provide more information - which MPI
implementation are you using (MPICH, LAM, something else?) and what
errors do you get?
--
Mark Brown mailto:[EMAIL PROTECTED] (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFS http://www.eusa.ed.ac.uk/societies/filmsoc/
------------------------------
From: "Nevyn" <[EMAIL PROTECTED]>
Subject: Re: AMD processor upgrade
Date: Sun, 25 Jul 1999 17:29:38 +0100
thankx......though i might reinstall windows at the same time.....jus for
fun ya know.........and since i'll b replacing motherboard, processor,
graphics card, sound card, and ram.........i fink a few reinstalls might be
in order.........should clear all the unneeded filed out though shouldnt
it?????..d:o�
------------------------------
From: Michael Hasenstein <[EMAIL PROTECTED]>
Subject: Re: Need opinions- how's S.u.S.E. 6.1
Date: Sun, 25 Jul 1999 16:51:08 +0200
Nick Zentena wrote:
> There will always be something missing. If SuSE shipped on ten CDs
> something would get missed. Just too many things out there. I couldn't
> find from on any of the CDs. I admit I didn't look too hard. No problem
> I went and get the src and compiled it. Maybe I'm the only person in the
> world still using it-) Now when will SuSE start shipping on DVDs? Why
> isn't SuSE waiting for XFree 3.3.5?
Let�s see... because there�ll always be a new version RSN of one of the
>1300 programs on the 6 CDs of 6.2? Even if you just look at seom core components this
>still holds true.
--
Michael Hasenstein
http://www.csn.tu-chemnitz.de/~mha/
Private Pilot (ASEL) since 1998
------------------------------
From: Murphy <[EMAIL PROTECTED]>
Subject: Mounting NTFS in OpenLinux
Date: Mon, 26 Jul 1999 00:21:22 +0800
Is there any ticks in mounting a NTFS to be used by ordnary user in
Linux system?!
As I'd tried to add entry in etc/fstab
/dev/hdb1 /mnt/nt ro, user, noauto 0 0
I can mount it without using root login, but I got the message
'Permission denied' when I
trying to access /mnt/nt. And I'd notice that the access right is set
to rw for root, and all blanks
for other user... Is there any tricks for such issue?!
Looking foreward for any kind of suggestions.
Best regard
------------------------------
From: Lev Babiev <[EMAIL PROTECTED]>
Subject: Re: redhat vs suse
Date: Sun, 25 Jul 1999 12:33:04 -0400
Mike Bartman wrote:
>
> On 25 Jul 1999 01:31:13 GMT, Paul Trost <[EMAIL PROTECTED]> wrote:
>
> >find SuSE more to my liking. Red Hat will cost about $80 and SuSE about
> >$29.
>
> I can't comment on SuSE, but where are you buying software that sells
> Red Hat for $80??? I got a copy of 5.2 at CompUSA last year for
> $30...and CompUSA is NOT known for low prices!
RH 6.0 has a version for $80, I think it's $50 for core (just CDs), $80
for CDs and books and even more for complete set with powertools etc.
Of course thats hardly an argument, since you can get any distro on CD
for $2 from cheapbytes, lsl or linuxmall.
- Lev
--
==============================================================================
"I don't think Microsoft is | mailto:[EMAIL PROTECTED]
evil in itself; I just think they |
make really crappy | irc: CrazyLion, #linuxlounge @ EFnet
operating systems." |
- Linus Torvalds | Linux forever!
==============================================================================
------------------------------
From: Rod Roark <[EMAIL PROTECTED]>
Subject: Re: Linux driver for ESS solo-1 sound chip
Date: 25 Jul 1999 16:47:17 GMT
Dave Meyer <[EMAIL PROTECTED]> wrote:
>According to Jonathan <[EMAIL PROTECTED]>:
>> I have an all-in-one motherboard with ESS solo-1 sound chip build in. I
>> can not find the correct driver for it. Anyone can help?
>ALSA (http://www.alsa-project.org) supports the ESS solo-1, though
>there have been a couple of reports (not sure how reliable) of trouble
>with built-in cards.
I have been installing the ALSA drivers for solo-1 support on the
AOpen MX3L and MX3ZA (both S-370 boards) and they have been working
nicely. You need to invoke amixer at boot time to restore your
mixer settings.
-- Rod
======================================================================
Sunset Systems Preconfigured Linux Computers
http://www.sunsetsystems.com/ and Custom Software
======================================================================
------------------------------
From: [EMAIL PROTECTED] (Ken Corbin)
Subject: Re: sound problems
Date: 25 Jul 1999 15:45:08 GMT
In article <[EMAIL PROTECTED]>, scable writes:
> When I try 1), I get an error window saying "Can't open
> /dev/dsp". 2) gives silence. 3) gives an error window that
> says something like "Can't open sound device. May be
> locked by aonother user."
The default Redhat 6.0 installation sets up security on the sound card
device files so that normal users can't write to or read from them.
Check to make sure you have read/write access
------------------------------
From: [EMAIL PROTECTED] (John Winters)
Crossposted-To: uk.comp.os.linux
Subject: Re: Where is NULL/__null?
Date: 25 Jul 1999 18:13:46 +0100
In article <7nfc1c$[EMAIL PROTECTED]>,
Konrad Hambrick <[EMAIL PROTECTED]> wrote:
[snip]
>Here is a handy trick to find out which ones you might need
>from the standard /usr/include/ heirarchy ( it is one way to
>do it, that is ;-):
>
>[tim@tim source]$ srcdir=`pwd` # optional -- save your place
>[tim@tim source]$ export srcdir # optional
>[tim@tim source]$ cd /usr/include
>[tim@tim include]$ egrep '^ *#define *NULL ' `find . -name "*.h" -print` |less
>[tim@tim include]$ cd $srcdir # optional -- restore your place
>
>replace the '^ *#define *NULL ' with whatever defined constant, etc
>you want to know about.
>
>Here is the output on my RH 5.2 box:
>
>../libio.h:#define NULL (__null)
>../libio.h:#define NULL ((void*)0)
>../libio.h:#define NULL (0)
>../malloc.h:#define NULL 0
>../malloc.h:#define NULL ((__malloc_ptr_t) 0)
>../stdio.h:#define NULL 0
>../stdio.h:#define NULL (void*)0
>../g++/streambuf.h:#define NULL (__null)
>../g++/streambuf.h:#define NULL (0)
>../pgsql/c.h:#define NULL ((void *) 0)
>../pgsql/c.h:#define NULL 0
>../python1.5/mymalloc.h:#define NULL ((ANY *)0)
>../python1.5/object.h:#define NULL 0
>../tcl.h:#define NULL 0
The trouble with this sort of empirical method of working out where
something should be is that it will often yield the wrong answer.
A better method is simply to check the language specification.
For C, the macro NULL is defined in stdio.h and stddef.h
Quite a few of those headers above are arguably illegal for attempting
to define the NULL macro. If they need the NULL macro they should include
the relevant headers. More importantly, if you pick one of them and
include it in order to get the NULL macro, your code may well break
on a different or upgraded installation and it'll be your problem. If
you include stddef.h to get the NULL macro and it later disappears from
there you can with justification complain to the implementation provider.
John
--
John Winters. Wallingford, Oxon, England.
The Linux Emporium - a source for Linux CDs in the UK
See <http://www.polo.demon.co.uk/emporium.html>
------------------------------
From: [EMAIL PROTECTED] (William Burrow)
Subject: Re: cp -r versus cp -R
Date: 25 Jul 1999 16:16:44 GMT
Reply-To: [EMAIL PROTECTED]
On Sun, 25 Jul 1999 00:41:12 +0000,
RKAA <[EMAIL PROTECTED]> wrote:
>Any idea how -R copies /proc/kcore ? just curious.
kcore is a regular file, so if you had permission to access it, cp would
copy the entire thing. Which is one good reason to umount /proc if you
want to cp -R /.
>But apropos the difference - browsed an IRIX manpage here and it stresses
>the difference as one regarding how they treat symbolic links (which can
>also be networked fileareas or directories.) cp -r would chase all the
>links it find while -R would only copy the link as such and not chase
>links beyond the root dir. -R is the POSIX compliant flag here, -r is
>"*nix" flavour dependant.
I'd say this would be the most common difference encountered. I find
that cp -a is very convenient, though it doesn't handle some
circumstances correctly (particularly, with --one-file-system, it
forgets to copy the mount point of other file systems).
--
William Burrow -- New Brunswick, Canada o
Copyright 1999 William Burrow ~ /\
~ ()>()
------------------------------
Crossposted-To: comp.os.linux.admin,comp.os.linux.help,comp.os.linux.questions
From: [EMAIL PROTECTED] (fred smith)
Subject: Re: C question
Date: Sun, 25 Jul 1999 12:07:27 GMT
me ([EMAIL PROTECTED]) wrote:
: hello.
: I want to access file information in linux using C. ie. filesize, date
: modified, filename etc. I wrote the following piece of code in DOS using
: borland Turbo C++. How do I write an equivalent linux version?????
Try looking at stat(2), e.g.:
man 2 stat
Note that this is NOT a findfirst replacement, but it does get you the
information you asked for.
Also note that anothe poster gave you some valid portability advice.
Fred
--
===============================================================================
.---- Fred Smith /
( /__ ,__. __ __ / __ : /
/ / / /__) / / /__) .+' Home: [EMAIL PROTECTED]
/ / (__ (___ (__(_ (___ / :__ 781-438-5471
================================ Jude 1:24,25 =================================
------------------------------
From: "R.K.Aa" <[EMAIL PROTECTED]>
Subject: Re: cp -r versus cp -R
Date: Sun, 25 Jul 1999 19:13:41 +0200
William Burrow wrote:
>
> On Sun, 25 Jul 1999 00:41:12 +0000,
> RKAA <[EMAIL PROTECTED]> wrote:
> >Any idea how -R copies /proc/kcore ? just curious.
>
> kcore is a regular file, so if you had permission to access it, cp would
> copy the entire thing. Which is one good reason to umount /proc if you
> want to cp -R /.
Hmm. Isn't kcore just a "visualisation" of what's stored in memory and
not a real file occupying space?
The bugger actually chomps up space too? That would mean...that for a
one gig MB RAM system you need at least a one gig area in /proc *in
addition* to a one gig swap partition? I didn't even know it was common
to have /proc as a mountpoint.. unless../proc *is* the swap area? (And
here I thought i was getting the hang of this.. lol)
K.
--
-- To E-mail, delete "spam" --
------------------------------
From: Jerrad Pierce <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: weird ping
Date: Sun, 25 Jul 1999 13:32:27 -0400
Firstly, how did you end up trying 55butes as a packet size?
Secondly, it seemd that 55 will never go through, try pinging anywhere with it
(eg mit.edu), no go.
Hope this helps
--
--
Please take the time to answer the simple survey at:
http://www.pthbb.org/cgi.bin/survey/
* __ * .
\ | / . . . . . ((_
_____ . . .
-- / \ -- . . . + . . _/\
oooooooooo. | * . . . * / ;M\_ .
.oooooooooooo.oo. . . . . /\ . / :IMM\
..oooooooooooo..oo. Jerrad Pierce /\ / \ / ;IIWMM
..oooooooooo....... 209 North Street + / \ / \ . / ;IIIIWM
...ooooooooo....... Randolph, MA 02368 / \ \ ___/ :;IIIIIWM
....ooo....o....... / \ \ / :: ;;IIIMI
.....ooo......... http://www.pthbb.org / \ \ : :::;IIIM
..ooooooo.... __________________________ || || ::.....::::::
MOTD on Swee
------------------------------
Subject: Re: xterm: scrolling up and down
From: Gary Momarison <[EMAIL PROTECTED]>
Date: 25 Jul 1999 10:23:16 -0700
[EMAIL PROTECTED] (Roy Culley) writes:
> the bash command history. I have tried adding the following
> to my .Xdefaults without any affect:
>
> *VT100.Translations: #override <Key>KP_Prior: scroll-back(1,page)\n\
> <Key>KP_Next: scroll-forw(1,page)
>
I keep mine in ~/.Xresources and use <KeyPress> instead of <Key>.
My WM is fvwm2. You DID do "xrdb -load .Xdefaults" (or -merge?)
didn't you?
--
Look for Linux info at http://www.dejanews.com/home_ps.shtml and
Gary's Encyclopedia at http://www.aa.net/~swear/pedia/index.html
------------------------------
From: Simon Hosie <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux,alt.os.linux.slackware,comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: spin down HDD
Date: 26 Jul 1999 02:32:44 +1200
Lindoze 2000:
> I use hdparm to spin down my HDD after 1/2 hr or so.
> the problem is, it spins up again after 1/2 hr. then it spins back down.
> has anyone had that problem?
> why wont it stay asleep?
> the system seems idle. no hdd activity detected.
Look at /usr/doc/Linux-mini-HOWTOs/Battery-Powered.
I used hdparm to power down one of my hard drives... later that night I
thought my other hard drive had gone mental because I could hear it seeking
every five seconds. I looked at the above document to see if I could shut
it up and found why it was doing what it was doing. It turns out that
/sbin/update was flushing the file buffers every five seconds, regardless of
whether they needed it, and in response my hard drive was unparking and
parking again.
Anyway, the document suggested changing the delay to an hour, but I would
have thought that that would cause the problem you're experiencing.
It shouldn't be swap, anyway. My swap drive powers down, and I only hear
from it again when I recompile a kernel or suchlike.
I'd like to find a real solution to the problem so that both my hard drives
can power down. I was thinking perhaps a couple of scripts that get called
when the system becomes idle or non-idle, basically to do the job my BIOS
would be doing if it worked properly (stupid $*(%^(#$)($&% AMI - never
again!).
--
# Please try to quote no more than you need to show the context of your post.
# If you also quote my .Sig then I hate you and I hope you get hiccups.
#
# email: Gumboot, at an ISP named Clear.Net, in New Zealand.
------------------------------
From: "Kelly Robinson" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.advocacy,comp.os.linux.advocacy,gnu.misc.discuss
Subject: Re: embracing humanity's parasitic nature
Date: Sun, 25 Jul 1999 10:49:09 -0500
And this relates to Linux because...
------------------------------
From: Patrick M. Geahan <[EMAIL PROTECTED]>
Subject: MP3 Tag Editor
Date: 25 Jul 1999 16:17:17 GMT
Can anyone recommend a good MP3 tag editor for Linux? I've got some MP3's
that don't have tagged titles, that I'd like to have some. I'd much
prefer if it was command-line or X11 based, and that I wouldn't have to
install gtk or KDE or any of that fun stuff. However, I'll take any
reocmmendations. Thanks.
--
=======Patrick M [EMAIL PROTECTED]=======ICQ:3784715==========
USENET Quote of the Week: "I'm still pondering whether i should
pre-emptively register 'I can't believe it's not Jesus' as a name for a
low-calorie communion wafer" - Tanuki on alt.sysadmin.recovery
------------------------------
** 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
******************************
