Date: Tue, 02 Oct 2007 10:11:29 +0000
From: steef <steefvanduin@zonnet.nl>
To: debian <debian-user@lists.debian.org>
Subject: cdrecord vs. wodim again
Message-ID: <47021951.2090509@zonnet.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
hi all and *especially j=F6rg s., long-term initiator of cdrecord and=20
cdrtools*.
two weeks ago i asked on this list 'what is better': cdrecord or wodim.=20
on one of the responses i answered that the most recent version of=20
cdrecord/cdr-tools completely damaged two brandnew cdrom's. j=F6rg asked=20
me for more info: and here comes some.
- only one cd/dvd-burner om my machine produced this undesirable=20
effect. a couple of other burners worked flawlessly with the most recent=20
b=EAta of j=F6rg sch.
so it could be that j=F6rg did not make this beta recognize this burner:=20
see /dev/hdb (from dmesg |less):=20
hda: MAXTOR STM3250820A, ATA DISK drive
hdb: Optiarc DVD RW AD-7173A, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: ST3120026A, ATA DISK drive
my machine: ($lspci -v)
0:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities:
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: 66MHz, fast devsel
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: 66MHz, fast devsel
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: 66MHz, fast devsel
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities:
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: 66MHz, fast devsel
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: 66MHz, fast devsel
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)=20
(prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=3D00, secondary=3D01, subordinate=3D01, sec-latency=3D=
0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: fd800000-fd8fffff
Prefetchable memory behind bridge: 00000000fd700000-00000000fd7ff=
fff
Capabilities:
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)=20
(prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=3D00, secondary=3D02, subordinate=3D02, sec-latency=3D=
0
I/O behind bridge: 0000b000-0000bfff
Memory behind bridge: fde00000-fdefffff
Prefetchable memory behind bridge: 00000000fdd00000-00000000fddff=
fff
Capabilities:
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)=20
(prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=3D00, secondary=3D03, subordinate=3D03, sec-latency=3D=
0
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fdc00000-fdcfffff
Prefetchable memory behind bridge: 00000000fd900000-00000000fd9ff=
fff
Capabilities:
00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce=20
6150] (rev a2) (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc. Unknown device 81cd
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 58
Memory at fc000000 (32-bit, non-prefetchable) [size=3D16M]
Memory at e0000000 (64-bit, prefetchable) [size=3D256M]
Memory at fb000000 (64-bit, non-prefetchable) [size=3D16M]
[virtual] Expansion ROM at 50000000 [disabled] [size=3D128K]
Capabilities:
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities:
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: 66MHz, fast devsel, IRQ 5
I/O ports at 4c00 [size=3D64]
I/O ports at 4c40 [size=3D64]
Capabilities:
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: 66MHz, fast devsel
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)=20
(prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 217
Memory at fe02f000 (32-bit, non-prefetchable) [size=3D4K]
Capabilities:
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)=20
(prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 209
Memory at fe02e000 (32-bit, non-prefetchable) [size=3D256]
Capabilities:
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) (prog-if 8a=20
[Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at fd00 [size=3D16]
Capabilities:
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller=20
(rev a1) (prog-if 85 [Master SecO PriO])
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 50
I/O ports at 09f0 [size=3D8]
I/O ports at 0bf0 [size=3D4]
I/O ports at 0970 [size=3D8]
I/O ports at 0b70 [size=3D4]
I/O ports at f800 [size=3D16]
Memory at fe02d000 (32-bit, non-prefetchable) [size=3D4K]
Capabilities:
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller=20
(rev a1) (prog-if 85 [Master SecO PriO])
Subsystem: ASUSTeK Computer Inc. Unknown device 81c0
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 209
I/O ports at 09e0 [size=3D8]
I/O ports at 0be0 [size=3D4]
I/O ports at 0960 [size=3D8]
I/O ports at 0b60 [size=3D4]
I/O ports at f300 [size=3D16]
Memory at fe02c000 (32-bit, non-prefetchable) [size=3D4K]
Capabilities:
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)=20
(prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, fast devsel, latency 0
Bus: primary=3D00, secondary=3D04, subordinate=3D04, sec-latency=3D=
128
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fdb00000-fdbfffff
Prefetchable memory behind bridge: fda00000-fdafffff
Capabilities:
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio=20
(rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 81cb
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 217
Memory at fe024000 (32-bit, non-prefetchable) [size=3D16K]
Capabilities:
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
Subsystem: ASUSTeK Computer Inc. Unknown device 816a
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 233
Memory at fe02b000 (32-bit, non-prefetchable) [size=3D4K]
I/O ports at f200 [size=3D8]
Capabilities:
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]=20
HyperTransport Technology Configuration
Flags: fast devsel
Capabilities:
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]=20
Address Map
Flags: fast devsel
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]=20
DRAM C troller
Flags: fast devsel
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]=20
Miscel neous Control
Flags: fast devsel
04:05.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A=20
IEEE-1394a-2000 Co roller (PHY/Link) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. K8N4-E Mainboard
Flags: bus master, medium devsel, latency 32, IRQ 225
Memory at fdbff000 (32-bit, non-prefetchable) [size=3D2K]
Memory at fdbf8000 (32-bit, non-prefetchable) [size=3D16K]
Capabilities:
04:08.0 Multimedia audio controller: Creative Labs SB Audigy LS
Subsystem: Creative Labs Unknown device 100a
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at cf00 [size=3D32]
Capabilities:
a good day to you all,
and regards,
steef
Date: Mon, 01 Oct 2007 09:26:34 -0700
From: Daniel Burrows <dburrows@debian.org>
To: felix@spodzone.org.uk
Cc: debian-user@lists.debian.org
Subject: Re: Debian packages without md5sums
Message-id: <20071001162634.GA22490@alpaca>
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
On Mon, Sep 24, 2007 at 05:37:51AM +0000, Felix Karpfen <felixk@webone.com.au> was heard to say:
> >> But How do you use the key(s) listed in "/etc/apt/trusted.gpg" to
> >> authenticate the individual installed packages.
> >
> > Oh, dpkg automatically checks it for you when you use apt-get/aptitude
> > to install package. (Unless you disable it.)
>
> So is the answer to my question:
>
> "use aptitude and not Synaptic" for installing packages?
It shouldn't matter which frontend you use. All the major frontends
check the signature of the Release file when you download package lists
from the archive. The Release file contains a cryptographic checksum
for the Packages file, which contains checksums for each individual .deb
package.
dpkg performs no key checking, at least on packages in the Debian
archive. There was some experimental code to stick embedded signatures
into .deb files, but I don't know what it's status is and packages
containing signatures aren't allowed in the archive last I heard.
Daniel
Date: Mon, 01 Oct 2007 20:47:06 -0700
From: Daniel Burrows <dburrows@debian.org>
To: Ron Johnson <ron.l.johnson@cox.net>
Cc: debian-user@lists.debian.org
Subject: Re: Etch-backports and gpg problems (SOLVED)
Message-id: <20071002034706.GA23085@alpaca>
Content-type: text/plain; charset=us-ascii
Content-disposition: inline
On Tue, Sep 25, 2007 at 08:37:12AM -0500, Ron Johnson <ron.l.johnson@cox.net> was heard to say:
> -----BEGIN PGP SIGNED MESSAGE-----
> What about:
> sudo (command_1 | command_2)
Won't work -- the ()s are shell metacharacters, and sudo knows
nothing about them. What you would need to do this with just one
sudo is something like:
sudo sh -c "command_1 | command_2"
with appropriate wariness towards quoting gremlins.
Daniel
End of debian-user-digest Digest V2007 Issue #2539
Received on Tue Oct 2 16:30:03 2007