On Mon, May 02, 2005 at 05:44:52PM +0200, Joerg Schilling wrote:
Suid shell scripts work since approx. 25 years.
Only on *some* operating systems. On others, the setuid/setgid bits
are ignored when the kernel handles the shebang.
Example 1:
imadev:~$ uname -a
HP-UX imadev B.10.20 A 9000/785
Rob Bogus wrote:
Geoffrey wrote:
I've been googling around and such, but can't find anything on this.
Is there support for burning dual-layer dvds? I'm running SuSE 9.2
and Red Hat Workstation 4.
Pointers to any docs would be appreciated.
Seeing no reply after all this time I assume you're on
Hello one more time.
Gergely, yesterday I opened growisofs_mmc.cpp and confirmed that it was
patched. I also recompiled dvd+rw-tools and compared growisofs' md5sum to the
one that I used in that burn and it was exactly the same. After reading the
code I dont really know why the program didnt
On Tue, 3 May 2005 12:11:34 -0300, [EMAIL PROTECTED] writes:
Regarding my burning problem, I changed to kernel 2.6.11 and burned
a dvd-r successfuly at 4x, and thats all I need. :) I guess that the
problem was really in the scsi emulation, so it should be ok now.
I'm happy to see, that
Hello
I am ryting to record a CD-R using my LG 420B drive. The LG can blank the
media without a problem but when I try to burn an image this is what I got:
Device type: Removable CD-ROM
Version: 2
Response Format: 2
Capabilities :
Vendor_info: 'HL-DT-ST'
Identifikation :
Hi there,
I am curious as to why the actual speed I get happens to be a lot
slower than the nominal one. I am using Knoppix 3.8.1 with 2.6.11
kernel in /dev/hdc, and the DVD writer is /dev/hdd
If I do not use hdparm to set the speed of /dev/hdd to udma2, then
actual speed happens to be even
Hello
I would like to return my ide drives (dvd and dvdram drives) back to atapi.
The first thing that I did was to remove devfs=mount hdc=ide-scsi
hdd=ide-scsi from lilo.conf. After booting, Mandrake 10.0 cannot assign any
device to the drives.
Then I did:
a) I've checked Mandrake control
Had a bit of conversation over at usb-storage mailing list below.
cdrecord 2.00.3 works fine with USB freecom drive, but cdrecord 2.01
crashes the firmware. Looks like there are two new READ_BUFFER
scsi commands in 2.01, and the drive doesn't like the 2nd one
with a large transfer length (0xfc00).
8 matches
Mail list logo