Am 04.02.2009, 12:07 Uhr, schrieb Thomas Schmitt :
Hi,
Matthias Andree wrote:
http://www.freebsd.org/gnome/docs/halfaq.html#q2
I'll put that into libburn docs.
It's not quite the same and also FreeBSD-specific. You don't want that.
Johannes Meixner's comment quote
So Thomas's earlier statement he has no interest in using unstable APIs
seems justified...
--
Matthias Andree
--
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
aintainers ;-)
--
Matthias Andree
--
To UNSUBSCRIBE, email to cdwrite-requ...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@other.debian.org
Joerg Schilling schrieb:
> Bill Davidsen wrote:
>
>
>>> Try to learn that hald on Linux is broken and acts on wrong status changes.
>>>
>>>
>> Nothing is ever your fault. Instead of learning from the applications
>> which burn CDs and DVDs without being root, your software has proble
Am Samstag, den 31.01.2009, 16:22 +0100 schrieb Joerg Schilling:
> "Thomas Schmitt" wrote:
>
> > Hi,
> >
> > > There always was only one cdrecord source code since it's
> > > creation in late 1995. The first DVD support code was added in
> > > February 1998 but could not be made OpenSource due t
Am Samstag, den 31.01.2009, 15:13 +0100 schrieb Norbert Preining:
> On Sa, 31 Jan 2009, Rob Bogus wrote:
> > Maybe you and Dr Norbert could take your pissing contest to email and
> > off this list.
>
> I don't discuss with Mr Schilling (and he not with me). I just want to
> get some things straig
Joerg Schilling schrieb:
> "Thomas Schmitt" <[EMAIL PROTECTED]> wrote:
>
>>> Why use a clone if you may use the original?
>> cdrskin is not a clone of anything.
>>
>>
>>> Nobody so far reported a problem with the original cdrecord
>> If it is about DVD then cdrecord is not
>> state of the art si
ar and offenses -- as this thread demonstrated with the
long anti-Linux pro-Solaris rant when he was asked about non-root BSD
usage.
--
Matthias Andree
.
Bill asked about BSD *ONLY*.
So will you answer his question or are you - as usual - unable to, because
you still can't get your feelings under control to an extent of discussing
in a professional manner?
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Matthias Andree <[EMAIL PROTECTED]> writes:
> cdrecord -scanbus in a21 doesn't work properly on Linux.
Whoops. I accidentally edited one detail. This is SUSE Linux 10.0,
$ uname -a
Linux foo 2.6.13-15.12-default #1 Thu Aug 24 11:23:58 UTC 2006 i686 athlon i386
GNU/Linux
--
M
: scsi3 Channel: 00 Id: 00 Lun: 02
Vendor: Generic Model: IC1210MMC/SD Rev: 1.9C
Type: Direct-AccessANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 03
Vendor: Generic Model: IC1210SM Rev: 1.9C
Type: Direct-AccessANSI S
1000.
What a botch. Perhaps it's time that cdrecord learns to treat device
identifiers as opaque string, without second-guessing a numbering that
falls apart the moment hotplug comes into play.
> J\366rg
Still not fixed your mailer?
--
Matthias Andree
uld use the right types for its job and fill them in where
missing on antedeluvian systems...
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[EMAIL PROTECTED] (Joerg Schilling) writes:
> I would need to look for my Suse-9.x HDD again
Don't bother. SUSE 9.0 has been discontinued ages ago.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
in the carrot fields of France.
>
> If you don't understand why is is bad style to use something other than
> 'caddr_t' or 'void *' for a pointer in a public interface, you better
> should not try to comment on it.
WTF is caddr_t? Certainly neither C nor
r short before giving up completely with Linux.
You have already done that, by pissing at people who aren't present to
defend themselves.
And BTW linuxcheck() is still nonfunctional on 2.6.10 and newer. But
that's a good thing since it omits yet another annoying warning :-)
--
Matthia
rbose || flags & F_VERSION) {
- printf("Cdrecord%s%s %s (%s-%s-%s) Copyright (C) 1995-2006 Jörg
Schilling\n",
+ printf("Cdrecord%s%s %s (%s-%s-%s) Copyright (C) 1995-2006
Joerg Schilling, 2006 Matthias Andree\n",
en that CD/DVD writer is writing.
It's a timing and perhaps device locking issue, mostly.
If the other device blocks the bus during an eject command, it's no
wonder the first complains with buffer underrun. And this still doesn't
justify making ATA look like SCSI.
I can as wel
Linux by removing artificial limits from libscg.
And, not to forget, it's the application that has to adjust to the
kernel, not the other way around.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Joerg Schilling schrieb am 2006-05-23:
> You believe that there is a Linux kernel where such a failure is not
> considered a bug?
> If you cannot help with the problem, please stay quiet.
Look who's talking.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
in the least.
We don't even have details as to the kernel version.
(And spare yourself the breath of replying to this post before Bill has
come up with details.)
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
output error. Cannot set
> SG_SET_TIMEOUT.
>
> I see devname still isn't supported.
Works for me, as root on SUSE Linux 10.0 (2.6.13-based kernel) i586,
with "plain old" VIA ATA drivers (VT8237 south bridge), and a NEC
ND-4550A FW 1.08.
What kernel and hardware and ATA drivers have you been using?
--
Matthias Andree
Joerg Schilling schrieb am 2006-03-22:
> Please try to stay reasonable.
You claim a violation but don't prove it, you don't even hint what's
allegedly your code that is used outside the GPL license...
Not very convincing.
--
Matthias Andree
--
To UNSUBSCRIBE, email t
Joerg Schilling <[EMAIL PROTECTED]> writes:
> linuxpiewie <[EMAIL PROTECTED]> wrote:
>
>> http://qpxtool.sourceforge.net
>
> This program violates the Copyright of cdrtools:
Which part of it specifically?
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAI
t problems for me with
a NEC ND-4550A, the kernel I've used was 2.6.13-mumble with SUSE patches.
Evidently this implies I haven't tested LightScribe or LabelFlash or
whatever the ND-4551A supports because the 4550A doesn't support it.
--
Matthias Andree
--
To UNSUBSCRIBE, e
Stefano Vesa <[EMAIL PROTECTED]> writes:
[Linux 2.6.15]
> Obviously no problem if I type ulimit -l unlimited before launching
> growisofs. Has my kernel or my bash too low limit values? There's a
> way to work around this problem without using ulimit?
It's the low kern
users being unable to do this and
that, change read speed and so on?
Besides that, the O_RDWR is insufficient to change device settings
(firmware, mode pages) and so on, so we can hardly assume that change
alone had made you happy.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
ur
providing lists of missing commands, it isn't even going to change.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Joerg Schilling <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>
>> > > I am looking since quite a while for the particular
>> > > and substantial security problems which one is said
>> > > to have if one allows w-access to a CD/DVD write
thing that has to
be taken into account given automount, submount, HAL, whatever.
> w-permission to setuid-cdrecord should be restricted to
> root, of course.
?
> Since years, i trust Joerg's ability to defend that setuid
> situation.
I don't.
There have been problems in th
ee code and make extensive validations of
the environment to prevent problems. seteuid() is really only a
convenience tool to prevent accident access to data where the invoking
user has no access, but nothing that would improve security WRT getting
root shells.
--
Matthias Andree
ld make Linux a mature project if such changes would be
> discussed for being reasonable with other people ( e.g. with experienced
> programmers like me).
It's good that you only attribute "experienced" and not other
adjectives to yourself here. One might otherwise get the idea y
Greg Wooledge schrieb am 2006-02-14:
> On Mon, Feb 13, 2006 at 10:27:52PM +0100, Matthias Andree wrote:
> > [ -f rpl8 ] && whatever
> >
> > fails if rpl8 is missing, and does not only skip "whatever" (here:
> > install), but also exits the whole compo
nstall), but also exits the whole compound command with code 1, which
aborts the make target.
"[ CONDITION ] && whatever" is therefore a Makefile pitfall.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[resending to right list]
Joerg Schilling schrieb am 2006-02-13:
> Matthias Andree <[EMAIL PROTECTED]> wrote:
>
> > Joerg Schilling schrieb am 2006-02-13:
> >
> > > Filtering SCSI commands was an unannounced change of the interface
> > > that needs to b
Joerg Schilling schrieb am 2006-02-13:
> Matthias Andree <[EMAIL PROTECTED]> wrote:
>
> > Joerg Schilling schrieb am 2006-02-13:
> >
> > > If the OS does not return useful error codes readcd has no chance
> > > to behave different.
> >
> > s
ration.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
WIO capability,
which root processes have by default.
The recommended installation on Linux is still setuid, so any claims
cdrecord were affected are hypocritical.
Plus, you have been offered by Linux developers to send a list of
commands that need to be allowed, you have not accepted that offer
nt
every submount filesystem (if Fedora uses that) for the device, and retry.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
_what_ to do.
>
> your problem is caused by the way _how_ it is done.
Entweder Du postest, was genau Du weißt, oder Du hältst die Finger
still.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
DMA mode.
No PIO (system time) load here.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
.9 times and that's about it.
That's not much, and it's not a problem per se; perhaps you should just
find somebody else to maintain your Linux port of libscg and cdrtools
(no, I'm not offering to do that at this time). That saves you the
hassles of staying up to date WRT Linux p
Answering three messages in one, to keep the thread concise.
Joerg Schilling schrieb am 2006-02-12:
> Matthias Andree <[EMAIL PROTECTED]> wrote:
>
> > >> status: 0x2 (CHECK CONDITION)
> > >> Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 08 00 00 00
;m not surprised there's
trouble. ISTR the maximum allowed length is 18 inches (45 cm).
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
r 49.
>
> Did you try this on a platform that is known to work?
I'm not interested in "known to work", but as the drive works with
FreeBSD 6-STABLE, is there a better way to isolate the problem than
running readcd with -v -V -d under strace(1) supervision?
--
Matthias And
eys information that Jörg has not extracted from messages since the
first time SG_IO in ide-cd cropped up.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sector 49.
Other operations, like reading with cdda2wav, appear to work properly on
both drives.
What is the interpretation of "logical unit communication failure" in
this context?
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe&
Joerg Schilling schrieb am 2006-02-03:
> "Jim Crilly" <[EMAIL PROTECTED]> wrote:
>
> > On 02/03/06 07:31:58PM +0100, Joerg Schilling wrote:
> > > Matthias Andree <[EMAIL PROTECTED]> wrote:
> > >
> > > > So patches to the
Joerg Schilling schrieb am 2006-02-03:
> Matthias Andree <[EMAIL PROTECTED]> wrote:
>
> > So patches to the rescue -- please review the patch below (for 2.01.01a05).
> > Note that GPL 2a and 2c apply, so you cannot merge a modified version of
> > my patch without a
cdrecord anyone? Two screenful removed by the patch, help yourself.
How does this look (setuid root, the kernel appears to refuse the
obsolete "REZERO UNIT" which breaks f.i. cdrecord -toc)?
$ bins/i686-linux-cc/cdrecord -scanbus
Cdrecord-Clone 2.01.01a04 (i686-pc-linux-gnu) Copyrigh
Joerg Schilling schrieb am 2006-01-30:
> Matthias Andree <[EMAIL PROTECTED]> wrote:
>
> > with this open letter, I officially request that you stop your
> > misrepresentations in cdrecord that claim Linux were noncompliant in a
> > place where it is conforming to PO
ted paragraph as
"Working around a new behavior in Linux since 2.6.9 that causes
cdrecord to be unable to allocate a SCSI transfer buffer.
These Linux kernel versions impose a tighter RLIMIT_MEMLOCK limit
than earlier versions that cause the allocation failure."
--
Ma
Joerg Schilling schrieb am 2006-01-30:
> Matthias Andree <[EMAIL PROTECTED]> wrote:
>
> > > > 2. scheduling writes is a complex matter in itself, and there is not a
> > > > single answer. The later you start writing, the more data you have
> > > >
Joerg Schilling schrieb am 2006-01-30:
> Matthias Andree <[EMAIL PROTECTED]> wrote:
>
> > 2. scheduling writes is a complex matter in itself, and there is not a
> > single answer. The later you start writing, the more data you have
> > available if the input rate
he actual use pattern. According to my manual pages,
Linux supports both. If it actually changes strategy, and which I/O
scheduler it uses, is a different question. Linux has several I/O
schedulers, the default appears to be the anticipatory scheduler, but it
also has CFQ and deadline schedulers.
--
avoiding it.
How would a buffer cache improve the situation for star? I may have
missed the beginning of the discussion, but caching
write-once-then-forget data seems pointless.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
changes for more than
a few -rc* would probably make people think twice before committing
incompatible changes.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
us 16-24X, whoever made them (MCC I believe)
and a few 10X CD-RW of various brands, neither caused a problem, and
reading SUSE 9.3 or 10.0 DVD 9 GB disks wasn't a problem either.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
n the gravestone of the party that starts flaming...)
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
e access is somewhat obsoleted by
the kernel's not being stable... be it right or wrong, doesn't count, it
matters if a working cdrecord can be compiled without jumping hoops.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ems in this
version.
I think this is their implementation of clauses 2a and 2c of the GPLv2.
--
Matthias Andree
ut malicious intent? I don't think so.
> If I see problems I name them and I do it in a direct way that just describes
> the problem. This is independent from the OS. If you don't see when I am
> atracking Solaris then you obviously close your eyes depending on where to
> l
got long-time observations yet, the NEC 4550A appears to
work good enough for the short term; but I did pick my media carefully
(the intersection of what NEC published as recommended and what the
German c't magazine deems acceptable media). For long-term, the media
itself matters, too.
--
M
ce something in Linux appears to impose a HARD
limit of 32kB on mmap()ed memory since Linux 2.6.9. If that turns out
true, there'll be little choice than to shuffle code a bit and mmap() as
root.
--
Matthias Andree
for instance.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
lling to waste my time with
> constanly trying out new Linux version as long as the Linux Folks is
> not willing to to stop introducing new problems for CD/DVD writing.
Well, your alternative would be to call Linux officially unsupported.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [
ou insisted that setuid would work in Linux (which it doesn't),
I'm showing you what works for me ATM. I'm not claiming it's appplicable
as is, I wanted to hear how your review is going.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of &q
mission to write, opening /dev/hda is
not a problem, and if you can access /dev/hdc without privileges, you
got a security problem".
Makes me wonder about set-group-id flag then, the little sibling of
set-user-id.
--
Matthias Andree
Joerg Schilling <[EMAIL PROTECTED]> writes:
> I fix all bugs that are verifiably caused by cdrecord and I try to find
> workarounds for all OS bugs. People just need to send a usable bug report.
How about my recent Linux SCSI buffer allocation patch? :-)
--
Matthias And
hout
locking themselves in to the commercial expiring stuff.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
will be changed to
>> comply to the man page.
>> A short answer would be welcome.
>
> Well, some things that are not done immediately because of workload may be
> forgotten if noone pings again.
How about using BerliOS's Bug Tracking System?
--
Matthias Andree
--
icted buffer
> > underruns" and "burnproof was 1x used"?
>
> A precited BU happens when the cdrecord FIFO fill ratio goes under 5%
Ah, so we just managed to refill the buffer in time 9x and failed to so
that 1x.
Thank you.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
t, i. e. with RT priority, mlocked pages and
everything. OK, it was Linux, not FreeBSD or Solaris...
In this context: what's the difference between "10 predicted buffer
underruns" and "burnproof was 1x used"?
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
That's the address to write to. Be sure to report a concrete bug with
detail, in English, and keep in mind that tech-pkg@ are nice guys,
packaging third-party software and aren't responsible for messups in
particular operating systems (kernel or libraries) -- pkgsrc is pretty
much independent of the OS; whether it's BSD, Linux, Solaris. For more
information, check <http://www.pkgsrc.org/>
--
Matthias Andree
sually tolerable, calling people names in public
(when running out of arguments, to be fair) is another.
It's about time that the list is calmed.
> Tell me how to configure correctly this shitty JavaMail webmail and I'll
> do it.
This doesn't belong on the cdwrite@ list.
--
Matthias Andree
>> burnfree kicked it at least once, and throw that CD if you want.
>
> But only if there is _another_ new option to enable/disable
> that fake failure exit.
Using a separate exit code (and documenting exit codes in the first
place!!) would suffice.
--
Matthias Andree
--
To UNS
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Matthias Andree wrote:
>> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>> > Matthias Andree wrote:
>> >> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>> >
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Matthias Andree wrote:
>> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>> > Why complicate the lives of cdrecord users with lots of options that
>> > don't even have a use case?
&g
ou'll
lose a machine to.
--
Matthias Andree
ut the topic.
You have a right to your opinion, but it isn't going to change
anything. You can waste energy on getting the defaults changed, or you
can invest some energy to write a /etc/default/... file.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
licly accused of
doing so. Working around all the firmware bug is, as you say, an
enormous effort, and if companies who create junk couldn't sell it their
junk, market would do the rest.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gue :-)), does not mean there
is none.
Running cdrecord underneath a front-end, in automated scripts, it might
be MUCH easier to look at the exit code rather than parse its messages.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
econds
(which are worth 10 to 60 MB, I know no writer with buffers that large).
> According to Jörg, the feature is off by default to ensure continuity
> and compatibility with .
> In my opinion, not a competent reason.
Aside from your right to your own opinion, what does it matter if you
can override the default?
--
Matthias Andree
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> Matthias Andree wrote:
>> "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
>> > Could you set burnfree on by default or give a competent reason to turn
>> > off burnfree?
>>
>>
material or just a random error.
For this reason it's best to not use these link capabilities but write a
continuous stream. I presume that might have been a reason to leave this
feature off by default. Reducing write speed is often a better
alternative, and you have a -dummy mode...
--
Matthias
debian.org list.
Please take this up to the shop that "fixed" your computer, and if that
doesn't help, with the vendors of your CD-writer and your commercial CD
writing software.
--
Matthias Andree
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
1x-4x
> media works fine. I even tried speed=4 with cdrecord when using the high
> speed media, but it fails in same fashion.
Why do you think this is a cdrecord problem?
Have you tried brand "High Speed" media such as Verbatim DataLifePlus?
Is your Toshiba's firmware up
ue sheet in -multi
- something else
How do we go about debugging this?
If it's a firmware bug, what's the contact inside Plextor to ask?
BTW, /etc/default/cdrecord is:
CDR_DEVICE=px4824
px4824= /dev/hdd -1 64m burnfree
--
Matthias Andree
--
To UNSUBSCRIBE, emai
88 matches
Mail list logo
