Re: CD writing in future Linux (stirring up a hornets' nest)

DervishD <[email protected]> wrote:


> other half doesn't have it probably has a bad user interface. You
> know that if a program uses a naming convention different from ALL
> the rest of programs is because the program has a problem. You know
> that if the only UNIX program out there that doesn't use /dev entries
> to talk to devices is cdrecord, the problem *probably* is in
> cdrecord, and not in UNIX...

So why do you like to introduce a different naming scheme?

Look into the real world and you will find that most SCSI related programs
use a namischscheme that is either identical to what cdrecord does
or a very similar one.

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/

---

• Follow-Ups:
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: DervishD <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Matthias Andree <[email protected]>

• References:
  • Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
    • From: Luke-Jr <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
    • From: Jan Engelhardt <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
    • From: Luke-Jr <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
    • From: Peter Read <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Matthias Andree <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: "Jim Crilly" <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: "Jim Crilly" <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: DervishD <[email protected]>

• Prev by Date: Re: [PATCH] percpu data: only iterate over possible CPUs
• Next by Date: Re: CD writing in future Linux (stirring up a hornets' nest)
• Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
• Next by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
• Index(es):
  • Date
  • Thread

[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]