Re: OT] Joerg Schilling flames Linux on his Blog

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 31 May 2005, Joerg Schilling wrote:

Kyle Moffett <[email protected]> wrote:

BTW: an implementation that uses something like Solaris does with
/etc/path_to_inst and puts USB serial numbers into the path_to_inst
kernel instance database could come very close to the desired result
and would give stable SCSI addresses too.

But why fix what isn't broken?  I can tell all my other programs, from
dd to mount, that I want to use the udev-created /dev/green_burner, so
why do you indicate such usage is _deprecated_ in cdrecord?  For such
device nodes, a _filesystem_ is the preferred name=>number index, so
why add an extra strange file "just because Solaris does".

If you use /dev/ entries to directly address SCSI targets, then you
are relying on on assumptions that cannot be granted everywhere.

Cdrecord is portable and this needs to implement a way that is portable
and does not rely on nonportable assumptions like yours.


Portability is relative. It's normally handled with a wrapper.
If your software is to work on a Unix or Unix-like machine, a
claim to "portability" must mean that its interface on a Unix-
like machine is either through a virtual file in '/dev' or
through a socket. This is because these are the 'standards'
that we all have to live with whether we like then or not.

Your `cdrecord -scanbus` hack to find I,J,K numbers that the
rest of your code was written to use, probably took more
time to write than a Unix wrapper which would provide the
correct (for a Unix environment) interface semantics.

Administrators need to set up symbolic links for /dev/burner
or /dev/cdreader, etc., to help cut down nuisance complaints
from users who fail to write CDs on their CD readers. This
is the de-facto Unix way. We need 'devices' in /dev.

BYW I have used your software from its inception and it
always worked well in my SCSI environment. The best working
software in the universe will not receive due credit if
it doesn't meet user (and customer) expectations. If you
are still interested in improving your generous gift to
the Linux community, you should seriously consider writing
wrappers  to address portability issues.


And why again do you need stable SCSI addresses for my _USB_ drive?

Well if the udev program was polite to users, it would also support
to edit /etc/default/cdrecord......

... if it _really_ does wat you like with /dev/ links, then it has all
the information that is needed to also maintain /etc/default/cdrecord



Jörg

--
EMail:[email protected] (home) Jörg Schilling D-13353 Berlin
      [email protected]		(uni)
      [email protected]	(work) Blog: http://schily.blogspot.com/
URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Cheers,
Dick Johnson
Penguin : Linux version 2.6.11.9 on an i686 machine (5537.79 BogoMips).
 Notice : All mail here is now cached for review by Dictator Bush.
                 98.36% of all statistics are fiction.

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux