From: Martin Dalecki <dalecki@evision-ventures.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Kurt Garloff <garloff@suse.de>,
Linux kernel list <linux-kernel@vger.kernel.org>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] /proc/scsi/map
Date: Thu, 20 Jun 2002 23:36:31 +0200 [thread overview]
Message-ID: <3D124ADF.6030103@evision-ventures.com> (raw)
In-Reply-To: Pine.LNX.4.44.0206201401010.8225-100000@home.transmeta.com
Użytkownik Linus Torvalds napisał:
>
> On Thu, 20 Jun 2002, Martin Dalecki wrote:
>
>>> /devices/disks/disk0 -> ../../pci0/00:02.0/02:1f.0/03:07.0/disk0
>>
>> ^^^^^^^^^^ You notice the redundancy in naming here :-).
>
>
> I'd rather have redundancy than have horrible names like just "0", thank
> you very much.
>
> It takes up no space, all the dentries are virtual anyway, and a dentry
> embeds the storage for the first n characters (n ~16 or something like
> that).
>
>
>>Boah the chierachies are already deep enough. /devices/net/eth@XX
>>will cut it.
>
>
> There is _no_ excuse for being terse.
Yes indeed:
ls DIR
cp COPY
mv REANME
cat TYPE
Note: the VMS stuff was even longer. You ever used the "shell" there?
> Also, never EVER use special characters like "@" unless there is _reason_
> to use them. I don't see any reason to make a filesystem look like perl.
The reaons is that it is making the splitup betwen the enumeration
and naming part very easy. Not just for scripts but for C code as well.
Numbers get user quite frequently for versioning as well.
And I tought the above should be mainly used by programs?
> Please use sane names like "disknnn" over insane cryptographically secure
> filesystem contents like "sd@nnn".
I'm so used to sd@ :-). Don't invent where you can borrow - or you will
go the esperanto way.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Kurt Garloff <garloff@suse.de>,
Linux kernel list <linux-kernel@vger.kernel.org>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] /proc/scsi/map
Date: Thu, 20 Jun 2002 23:36:31 +0200 [thread overview]
Message-ID: <3D124ADF.6030103@evision-ventures.com> (raw)
In-Reply-To: Pine.LNX.4.44.0206201401010.8225-100000@home.transmeta.com
Użytkownik Linus Torvalds napisał:
>
> On Thu, 20 Jun 2002, Martin Dalecki wrote:
>
>>> /devices/disks/disk0 -> ../../pci0/00:02.0/02:1f.0/03:07.0/disk0
>>
>> ^^^^^^^^^^ You notice the redundancy in naming here :-).
>
>
> I'd rather have redundancy than have horrible names like just "0", thank
> you very much.
>
> It takes up no space, all the dentries are virtual anyway, and a dentry
> embeds the storage for the first n characters (n ~16 or something like
> that).
>
>
>>Boah the chierachies are already deep enough. /devices/net/eth@XX
>>will cut it.
>
>
> There is _no_ excuse for being terse.
Yes indeed:
ls DIR
cp COPY
mv REANME
cat TYPE
Note: the VMS stuff was even longer. You ever used the "shell" there?
> Also, never EVER use special characters like "@" unless there is _reason_
> to use them. I don't see any reason to make a filesystem look like perl.
The reaons is that it is making the splitup betwen the enumeration
and naming part very easy. Not just for scripts but for C code as well.
Numbers get user quite frequently for versioning as well.
And I tought the above should be mainly used by programs?
> Please use sane names like "disknnn" over insane cryptographically secure
> filesystem contents like "sd@nnn".
I'm so used to sd@ :-). Don't invent where you can borrow - or you will
go the esperanto way.
next prev parent reply other threads:[~2002-06-20 21:36 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 0:44 [PATCH] /proc/scsi/map Kurt Garloff
2002-06-20 0:44 ` Kurt Garloff
2002-06-20 5:03 ` Linus Torvalds
2002-06-20 7:09 ` Martin Schwenke
2002-06-20 7:09 ` Martin Schwenke
2002-06-20 15:13 ` Linus Torvalds
2002-06-20 15:36 ` Dave Jones
2002-06-20 17:01 ` Linus Torvalds
2002-06-20 16:55 ` Andries Brouwer
2002-06-20 16:55 ` Andries Brouwer
2002-06-20 17:52 ` Patrick Mansfield
2002-06-20 18:36 ` Linus Torvalds
2002-06-20 18:52 ` James Bottomley
2002-06-20 19:15 ` Linus Torvalds
2002-06-20 16:28 ` Benjamin Herrenschmidt
2002-06-21 0:46 ` Linus Torvalds
2002-06-20 16:49 ` Benjamin Herrenschmidt
2002-06-20 20:06 ` Oliver Xymoron
2002-06-22 18:27 ` Pavel Machek
2002-06-20 18:11 ` Linus Torvalds
2002-06-20 22:59 ` Martin Schwenke
2002-06-20 23:13 ` Linus Torvalds
2002-06-22 18:25 ` Pavel Machek
2002-06-26 16:03 ` Ihno Krumreich
2002-07-01 17:33 ` Patrick Mochel
2002-06-20 19:55 ` Greg KH
2002-06-20 19:18 ` Patrick Mochel
2002-06-21 6:28 ` Mike Touloumtzis
2002-06-20 11:25 ` Kurt Garloff
2002-06-20 11:25 ` Kurt Garloff
2002-06-20 15:34 ` Linus Torvalds
2002-06-20 16:30 ` Martin Dalecki
2002-06-20 16:30 ` Martin Dalecki
2002-06-20 16:58 ` James Bottomley
2002-06-20 18:27 ` Linus Torvalds
2002-06-20 20:55 ` Martin Dalecki
2002-06-20 20:55 ` Martin Dalecki
2002-06-20 21:04 ` Linus Torvalds
2002-06-20 21:36 ` Martin Dalecki [this message]
2002-06-20 21:36 ` Martin Dalecki
2002-06-20 20:12 ` Patrick Mochel
2002-06-20 22:29 ` Martin Dalecki
2002-06-20 22:29 ` Martin Dalecki
2002-06-22 18:42 ` Pavel Machek
2002-06-21 14:29 ` sullivan
2002-06-21 16:17 ` Patrick Mochel
2002-07-03 4:29 ` [PATCH] driverfs scsi for 2.5.24 Douglas Gilbert
2002-07-03 14:34 ` James Bottomley
2002-07-05 1:45 ` Douglas Gilbert
2002-07-05 18:50 ` Patrick Mochel
2002-07-05 18:31 ` Patrick Mochel
2002-06-21 21:33 ` [PATCH] /proc/scsi/map Oliver Xymoron
2002-06-22 4:38 ` Nick Bellinger
2002-06-22 19:41 ` Douglas Gilbert
2002-06-22 19:11 ` Nick Bellinger
2002-06-25 18:13 ` Patrick Mochel
2002-06-25 16:05 ` Patrick Mochel
2002-06-25 16:57 ` Oliver Xymoron
2002-06-25 18:58 ` Patrick Mochel
2002-07-03 1:01 ` Pavel Machek
2002-06-20 18:32 ` Kurt Garloff
2002-06-20 18:53 ` Linus Torvalds
2002-06-21 9:07 ` Kurt Garloff
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 23:59 Grover, Andrew
2002-06-22 6:29 Adam J. Richter
2002-06-25 16:17 ` Patrick Mochel
2002-06-22 17:24 David Brownell
2002-06-22 17:48 ` Roman Zippel
2002-06-22 17:48 ` Roman Zippel
2002-06-22 20:11 ` Douglas Gilbert
2002-06-22 20:57 ` Roman Zippel
2002-06-22 20:57 ` Roman Zippel
2002-06-22 18:18 ` Nick Bellinger
2002-06-24 1:50 ` David Brownell
2002-06-25 16:46 ` Patrick Mochel
2002-06-25 16:46 ` Patrick Mochel
2002-06-25 16:33 ` Patrick Mochel
2002-06-25 16:33 ` Patrick Mochel
2002-06-25 17:49 ` David Brownell
2002-06-26 23:39 ` Nick Bellinger
2002-07-01 17:45 ` Patrick Mochel
2002-07-03 0:59 ` Pavel Machek
2002-07-03 0:59 ` Pavel Machek
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=3D124ADF.6030103@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=James.Bottomley@steeleye.com \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.