mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joerg Schilling <schilling@fokus.gmd.de>
To: schilling@fokus.gmd.de, vherva@niksula.hut.fi
Cc: cdwrite@other.debian.org, linux-kernel@vger.kernel.org
Subject: Re: 2.4.10ac10, cdrecord 1.9-6, Mitsumi CR-4804TE: lock up burning too large image
Date: Sun, 21 Oct 2001 13:56:06 +0200 (MEST)	[thread overview]
Message-ID: <200110211156.f9LBu6308916@burner.fokus.gmd.de> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]


>From vherva@niksula.hut.fi Sun Oct 21 13:46:25 2001

>On Sun, Oct 21, 2001 at 01:37:01PM +0200, you [Joerg Schilling] claimed:
>> 

>Thanks for the timely reply!

>> This must be a broken drive....

>Hmm. It used to work with 2.2-kernel. With too large image, it just gave an
>error.

I may only judge from information you provide, not from information you hide.

>> Don't use outdated cdrecord versions, I cannot support them!

>Ok. I updated to 1.10 from redhat rawhide, but as said it didn't work at all

1.10 is outdated too, please read

http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/problems.html

>with 2.2 ("failed to mmap /dev/null" or something) so I went back to 1.9. I

I cannot prevent you from broken Linux installations!

The linux kernel people still have propblems with interfaces and make thanges that
break binary compatibility when going to more recent Linux versions.
Why do you believe that a cdrecord that has been compiled on 2.4 will run on 2.2?

Linux needed close to 10 years to finally support mmap() (ther OS like SunOS
did this since 1987). Cdrecord's outoconf chooses the best interfaces of the OS.
SVS shared mem is outdated and badly implemented on Linux (too many restrictions).
mmap is the modern method to get shared memory but Linux didn't support is before
November 2000.



Jörg

 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de		(uni)  If you don't have iso-8859-1
       schilling@fokus.gmd.de		(work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix

             reply	other threads:[~2001-10-21 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-21 11:56 Joerg Schilling [this message]
2001-10-21 12:08 ` Ville Herva
  -- strict thread matches above, loose matches on Subject: below --
2001-10-22  5:48 Paul Kreiner
2001-10-21 12:10 Joerg Schilling
2001-10-21 17:25 ` Ville Herva
     [not found] <200110211137.f9LBb1w08887@burner.fokus.gmd.de>
2001-10-21 11:46 ` Ville Herva
2001-10-21 10:54 Ville Herva
2001-10-22 19:03 ` bill davidsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200110211156.f9LBu6308916@burner.fokus.gmd.de \
    --to=schilling@fokus.gmd.de \
    --cc=cdwrite@other.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vherva@niksula.hut.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®