Mac drive letters?
3 views
Skip to first unread message
Commander Kinsey
Feb 20, 2022, 8:55:56 AM2/20/22
to
I mainly use PCs and thought, how do Mac users manage without drive letters? How do you enter a path for example? How can a program refer to a file if there's no letter?
nospam
Feb 20, 2022, 9:15:22 AM2/20/22
to
In article <op.1hv6b...@ryzen.lan>, Commander Kinsey
> How do you enter a path for example? How can a program refer to a file if
> there's no letter?
name-of-disk/path/to/file
it can also be a partial path, which is relative to a known location,
such as the user's documents folder.
there are other ways to locate a file, including if it moves.
unix, on which mac os is based and predates dos/windows, does not use
drive letters.
classic mac os, which was not based on unix did not have drive letters
and did not rely on path names (although they could be used).
<C...@nospam.com> wrote:
> I mainly use PCs and thought, how do Mac users manage without drive letters?
quite well. not having drive letters is a huge advantage.
> I mainly use PCs and thought, how do Mac users manage without drive letters?
> How do you enter a path for example? How can a program refer to a file if
> there's no letter?
it can also be a partial path, which is relative to a known location,
such as the user's documents folder.
there are other ways to locate a file, including if it moves.
unix, on which mac os is based and predates dos/windows, does not use
drive letters.
classic mac os, which was not based on unix did not have drive letters
and did not rely on path names (although they could be used).
Chris
Feb 20, 2022, 10:21:47 AM2/20/22
to
Commander Kinsey <C...@nospam.com> wrote:
> I mainly use PCs and thought, how do Mac users manage without drive letters?
Easily.
> I mainly use PCs and thought, how do Mac users manage without drive letters?
> How do you enter a path for example? How can a program refer to a file
> if there's no letter?
to a unified system, drive letters make no sense.
Snit
Feb 20, 2022, 1:42:47 PM2/20/22
to
On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
<op.1hv6b...@ryzen.lan>:
> I mainly use PCs and thought, how do Mac users manage without drive letters?
> How do you enter a path for example? How can a program refer to a file if
> there's no letter?
It refers to it by name, and if needed the name of the drive.
Just got the path to a file on an external drive. This is what it looks like
(I did change the names for ease of reading):
file:///Volumes/External/Bearizona/IMG_1234.jpg
One cool thing about macOS is how flexible it is with this -- you can have a
link to a file (or app) and then change the name of the file and move it and
the link still works. You can even do this with the file open (in most cases).
Why should users have to remember a bunch of drive letters?
--
Personal attacks from those who troll show their own insecurity. They cannot use reason to show the message to be wrong so they try to feel somehow superior by attacking the messenger.
They cling to their attacks and ignore the message time and time again.
<op.1hv6b...@ryzen.lan>:
> I mainly use PCs and thought, how do Mac users manage without drive letters?
> How do you enter a path for example? How can a program refer to a file if
> there's no letter?
Just got the path to a file on an external drive. This is what it looks like
(I did change the names for ease of reading):
file:///Volumes/External/Bearizona/IMG_1234.jpg
One cool thing about macOS is how flexible it is with this -- you can have a
link to a file (or app) and then change the name of the file and move it and
the link still works. You can even do this with the file open (in most cases).
Why should users have to remember a bunch of drive letters?
--
Personal attacks from those who troll show their own insecurity. They cannot use reason to show the message to be wrong so they try to feel somehow superior by attacking the messenger.
They cling to their attacks and ignore the message time and time again.
Snit
Feb 20, 2022, 2:00:57 PM2/20/22
to
nospam
Feb 20, 2022, 2:07:17 PM2/20/22
to
In article <HdwQJ.23926$jxu4...@fx02.iad>, Snit
<brock.m...@gmail.com> wrote:
> >> How do you enter a path for example? How can a program refer to a file
> >> if there's no letter?
> >
> > It's a UNIX system so all paths are relative to root '/'. Once you get used
> > to a unified system, drive letters make no sense.
>
> Add to that on macOS you can move and rename files even when they are open.
and most apps automatically update with the new name & path.
> >> How do you enter a path for example? How can a program refer to a file
> >> if there's no letter?
> >
> > It's a UNIX system so all paths are relative to root '/'. Once you get used
> > to a unified system, drive letters make no sense.
>
> Add to that on macOS you can move and rename files even when they are open.
Snit
Feb 20, 2022, 2:10:17 PM2/20/22
to
On Feb 20, 2022 at 12:07:18 PM MST, "nospam" wrote
<200220221407189168%nos...@nospam.invalid>:
Correct. Recent files show it, etc.
<200220221407189168%nos...@nospam.invalid>:
nospam
Feb 20, 2022, 2:34:33 PM2/20/22
to
In article <smwQJ.56886$f2a5....@fx48.iad>, Snit
<brock.m...@gmail.com> wrote:
> >>>> How do you enter a path for example? How can a program refer to a file
> >>>> if there's no letter?
> >>>
> >>> It's a UNIX system so all paths are relative to root '/'. Once you get
> >>> used
> >>> to a unified system, drive letters make no sense.
> >>
> >> Add to that on macOS you can move and rename files even when they are open.
> >
> > and most apps automatically update with the new name & path.
>
> Correct. Recent files show it, etc.
true, but i was thinking of the window title bar.
> >>>> How do you enter a path for example? How can a program refer to a file
> >>>> if there's no letter?
> >>>
> >>> It's a UNIX system so all paths are relative to root '/'. Once you get
> >>> used
> >>> to a unified system, drive letters make no sense.
> >>
> >> Add to that on macOS you can move and rename files even when they are open.
> >
> > and most apps automatically update with the new name & path.
>
> Correct. Recent files show it, etc.
Snit
Feb 20, 2022, 2:40:16 PM2/20/22
to
location (and more) from there.
Commander Kinsey
Feb 20, 2022, 5:08:12 PM2/20/22
to
On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
> <op.1hv6b...@ryzen.lan>:
>
>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>> How do you enter a path for example? How can a program refer to a file if
>> there's no letter?
>
> It refers to it by name, and if needed the name of the drive.
>
> Just got the path to a file on an external drive. This is what it looks like
> (I did change the names for ease of reading):
>
> file:///Volumes/External/Bearizona/IMG_1234.jpg
Could you open up your firewall so I can access that image, which is on your own computer.
> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
> <op.1hv6b...@ryzen.lan>:
>
>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>> How do you enter a path for example? How can a program refer to a file if
>> there's no letter?
>
> It refers to it by name, and if needed the name of the drive.
>
> Just got the path to a file on an external drive. This is what it looks like
> (I did change the names for ease of reading):
>
> file:///Volumes/External/Bearizona/IMG_1234.jpg
Oh.... I thought you were sending a screenshot and forgot to upload first!
So that's not clear where on earth that is. c:\music\metallica\ride the lightning.mp3 is much better. The drive is the letter, the last one is the file, inbetween ones are folders. Why do you have file: at the start? WTF is the triple slash for? Is the drive called Volumes or External? Far more complicated if you want to refer to that file. A program you've installed wanting to refer to something in its data folder for example.
> One cool thing about macOS is how flexible it is with this -- you can have a
> link to a file (or app) and then change the name of the file and move it and
> the link still works. You can even do this with the file open (in most cases).
>
> Why should users have to remember a bunch of drive letters?
nospam
Feb 20, 2022, 5:24:10 PM2/20/22
to
In article <op.1hws3...@ryzen.lan>, Commander Kinsey
> c:\music\metallica\ride the
> lightning.mp3 is much better. The drive is the letter, the last one is the
> file, inbetween ones are folders.
which is basically the same as above, with the advantage of referencing
it by drive name instead of an abstract letter which is not always the
same.
> Why do you have file: at the start? WTF
> is the triple slash for?
go learn about file: urls.
it's also not needed.
> Is the drive called Volumes or External?
/volumes is where external drives are normally mounted. the drive can
have any name. in the above example, the name is external (which he
said he changed).
drives can also be mounted elsewhere, in which case it would be
/some/other/path/to/file.
> Far more
> complicated if you want to refer to that file. A program you've installed
> wanting to refer to something in its data folder for example.
an app wanting to refer something in its data folder would normally use
relative paths.
> > Why should users have to remember a bunch of drive letters?
>
> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
> disk. If you add another floppy it's B:, if you add a CDROM or another hard
> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive letter.
that does not scale well, plus driver letters are not always the same
across different pcs.
<C...@nospam.com> wrote:
> > Just got the path to a file on an external drive. This is what it looks like
> > (I did change the names for ease of reading):
> >
> > file:///Volumes/External/Bearizona/IMG_1234.jpg
>
> Could you open up your firewall so I can access that image, which is on your
> own computer.
>
> Oh.... I thought you were sending a screenshot and forgot to upload first!
>
> So that's not clear where on earth that is.
it's exactly clear where it is.
> > Just got the path to a file on an external drive. This is what it looks like
> > (I did change the names for ease of reading):
> >
> > file:///Volumes/External/Bearizona/IMG_1234.jpg
>
> Could you open up your firewall so I can access that image, which is on your
> own computer.
>
> Oh.... I thought you were sending a screenshot and forgot to upload first!
>
> So that's not clear where on earth that is.
> c:\music\metallica\ride the
> lightning.mp3 is much better. The drive is the letter, the last one is the
> file, inbetween ones are folders.
it by drive name instead of an abstract letter which is not always the
same.
> Why do you have file: at the start? WTF
> is the triple slash for?
it's also not needed.
> Is the drive called Volumes or External?
have any name. in the above example, the name is external (which he
said he changed).
drives can also be mounted elsewhere, in which case it would be
/some/other/path/to/file.
> Far more
> complicated if you want to refer to that file. A program you've installed
> wanting to refer to something in its data folder for example.
relative paths.
> > Why should users have to remember a bunch of drive letters?
>
> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
> disk. If you add another floppy it's B:, if you add a CDROM or another hard
> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive letter.
across different pcs.
Commander Kinsey
Feb 20, 2022, 5:33:59 PM2/20/22
to
On Sun, 20 Feb 2022 19:00:55 -0000, Snit <brock.m...@gmail.com> wrote:
> On Feb 20, 2022 at 8:21:46 AM MST, "Chris" wrote <sutmaa$e75$1...@dont-email.me>:
>
>> Commander Kinsey <C...@nospam.com> wrote:
>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>
>> Easily.
>>
>>> How do you enter a path for example? How can a program refer to a file
>>> if there's no letter?
>>
>> It's a UNIX system so all paths are relative to root '/'. Once you get used
>> to a unified system, drive letters make no sense.
>
> Add to that on macOS you can move and rename files even when they are open.
All paths relative to root? How fucking stupid. If it's on another drive it should start differently. You know, like differentiating between your kitchen and mine. You start with what house it's in.
> On Feb 20, 2022 at 8:21:46 AM MST, "Chris" wrote <sutmaa$e75$1...@dont-email.me>:
>
>> Commander Kinsey <C...@nospam.com> wrote:
>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>
>> Easily.
>>
>>> How do you enter a path for example? How can a program refer to a file
>>> if there's no letter?
>>
>> It's a UNIX system so all paths are relative to root '/'. Once you get used
>> to a unified system, drive letters make no sense.
>
> Add to that on macOS you can move and rename files even when they are open.
nospam
Feb 20, 2022, 5:47:22 PM2/20/22
to
In article <op.1hwua...@ryzen.lan>, Commander Kinsey
classic mac os didn't have that limitation, which was lost when macs
moved to mac os x and its unix core.
> If it's on another drive it
> should start differently.
it does.
for two drives named red and blue, it would be /volumes/red and
/volumes/blue. the only thing that's common is /volumes, which is
usually where they're mounted. they can be mounted anywhere in the file
system, which is both good and bad.
<C...@nospam.com> wrote:
> >>
> >>> How do you enter a path for example? How can a program refer to a file
> >>> if there's no letter?
> >>
> >> It's a UNIX system so all paths are relative to root '/'. Once you get used
> >> to a unified system, drive letters make no sense.
> >
> > Add to that on macOS you can move and rename files even when they are open.
>
> All paths relative to root? How fucking stupid.
welcome to unix.
> >>
> >>> How do you enter a path for example? How can a program refer to a file
> >>> if there's no letter?
> >>
> >> It's a UNIX system so all paths are relative to root '/'. Once you get used
> >> to a unified system, drive letters make no sense.
> >
> > Add to that on macOS you can move and rename files even when they are open.
>
> All paths relative to root? How fucking stupid.
classic mac os didn't have that limitation, which was lost when macs
moved to mac os x and its unix core.
> If it's on another drive it
> should start differently.
for two drives named red and blue, it would be /volumes/red and
/volumes/blue. the only thing that's common is /volumes, which is
usually where they're mounted. they can be mounted anywhere in the file
system, which is both good and bad.
Snit
Feb 20, 2022, 6:15:17 PM2/20/22
to
On Feb 20, 2022 at 3:47:21 PM MST, "nospam" wrote
<200220221747211474%nos...@nospam.invalid>:
> In article <op.1hwua...@ryzen.lan>, Commander Kinsey
> <C...@nospam.com> wrote:
>
>>>>
>>>>> How do you enter a path for example? How can a program refer to a file
>>>>> if there's no letter?
>>>>
>>>> It's a UNIX system so all paths are relative to root '/'. Once you get used
>>>> to a unified system, drive letters make no sense.
>>>
>>> Add to that on macOS you can move and rename files even when they are open.
>>
>> All paths relative to root? How fucking stupid.
>
> welcome to unix.
>
> classic mac os didn't have that limitation, which was lost when macs
> moved to mac os x and its unix core.
But you can "fake it" in AppleScript and I assume other languages. Well, you
can in Unix, too.
>
>> If it's on another drive it
>> should start differently.
>
> it does.
>
> for two drives named red and blue, it would be /volumes/red and
> /volumes/blue. the only thing that's common is /volumes, which is
> usually where they're mounted. they can be mounted anywhere in the file
> system, which is both good and bad.
<200220221747211474%nos...@nospam.invalid>:
> In article <op.1hwua...@ryzen.lan>, Commander Kinsey
> <C...@nospam.com> wrote:
>
>>>>
>>>>> How do you enter a path for example? How can a program refer to a file
>>>>> if there's no letter?
>>>>
>>>> It's a UNIX system so all paths are relative to root '/'. Once you get used
>>>> to a unified system, drive letters make no sense.
>>>
>>> Add to that on macOS you can move and rename files even when they are open.
>>
>> All paths relative to root? How fucking stupid.
>
> welcome to unix.
>
> classic mac os didn't have that limitation, which was lost when macs
> moved to mac os x and its unix core.
can in Unix, too.
>
>> If it's on another drive it
>> should start differently.
>
> it does.
>
> for two drives named red and blue, it would be /volumes/red and
> /volumes/blue. the only thing that's common is /volumes, which is
> usually where they're mounted. they can be mounted anywhere in the file
> system, which is both good and bad.
Snit
Feb 20, 2022, 6:16:12 PM2/20/22
to
On Feb 20, 2022 at 3:33:56 PM MST, ""Commander Kinsey"" wrote
<op.1hwua...@ryzen.lan>:
> On Sun, 20 Feb 2022 19:00:55 -0000, Snit <brock.m...@gmail.com> wrote:
>
>> On Feb 20, 2022 at 8:21:46 AM MST, "Chris" wrote <sutmaa$e75$1...@dont-email.me>:
>>
>>> Commander Kinsey <C...@nospam.com> wrote:
>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>
>>> Easily.
>>>
>>>> How do you enter a path for example? How can a program refer to a file
>>>> if there's no letter?
>>>
>>> It's a UNIX system so all paths are relative to root '/'. Once you get used
>>> to a unified system, drive letters make no sense.
>>
>> Add to that on macOS you can move and rename files even when they are open.
>
> All paths relative to root?
Absolute paths are. You can also have relative paths.
> How fucking stupid. If it's on another drive it should start differently. You
> know, like differentiating between your kitchen and mine. You start with what
> house it's in.
If things are in my user folder the reference is just ~/whatever
<op.1hwua...@ryzen.lan>:
> On Sun, 20 Feb 2022 19:00:55 -0000, Snit <brock.m...@gmail.com> wrote:
>
>> On Feb 20, 2022 at 8:21:46 AM MST, "Chris" wrote <sutmaa$e75$1...@dont-email.me>:
>>
>>> Commander Kinsey <C...@nospam.com> wrote:
>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>
>>> Easily.
>>>
>>>> How do you enter a path for example? How can a program refer to a file
>>>> if there's no letter?
>>>
>>> It's a UNIX system so all paths are relative to root '/'. Once you get used
>>> to a unified system, drive letters make no sense.
>>
>> Add to that on macOS you can move and rename files even when they are open.
>
> All paths relative to root?
> How fucking stupid. If it's on another drive it should start differently. You
> know, like differentiating between your kitchen and mine. You start with what
> house it's in.
Snit
Feb 20, 2022, 6:22:47 PM2/20/22
to
On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
<op.1hws3...@ryzen.lan>:
> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>
>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>> <op.1hv6b...@ryzen.lan>:
>>
>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>> How do you enter a path for example? How can a program refer to a file if
>>> there's no letter?
>>
>> It refers to it by name, and if needed the name of the drive.
>>
>> Just got the path to a file on an external drive. This is what it looks like
>> (I did change the names for ease of reading):
>>
>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>
> Could you open up your firewall so I can access that image, which is on your
> own computer.
You would need my IP. It was just an example, as a path with your C drive
would be.
> Oh.... I thought you were sending a screenshot and forgot to upload first!
:)
> So that's not clear where on earth that is. c:\music\metallica\ride the
> lightning.mp3 is much better.
How so?
> The drive is the letter, the last one is the file, inbetween ones are folders.
Pretty much the same but the first is noting it is in Volumes.
> Why do you have file: at the start?
It is a part of the URI.
https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
> WTF is the triple slash for?
Part of the URI.
> Is the drive called Volumes or External?
The drive is "External".
> Far more complicated if you want to refer to that file. A program you've
> installed wanting to refer to something in its data folder for example.
>
>> One cool thing about macOS is how flexible it is with this -- you can have a
>> link to a file (or app) and then change the name of the file and move it and
>> the link still works. You can even do this with the file open (in most cases).
>>
>> Why should users have to remember a bunch of drive letters?
>
> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
> disk. If you add another floppy it's B:, if you add a CDROM or another hard
> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
> letter.
You have remembered them. So have I. But why do we need to just to use a
computer?
<op.1hws3...@ryzen.lan>:
> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>
>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>> <op.1hv6b...@ryzen.lan>:
>>
>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>> How do you enter a path for example? How can a program refer to a file if
>>> there's no letter?
>>
>> It refers to it by name, and if needed the name of the drive.
>>
>> Just got the path to a file on an external drive. This is what it looks like
>> (I did change the names for ease of reading):
>>
>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>
> Could you open up your firewall so I can access that image, which is on your
> own computer.
would be.
> Oh.... I thought you were sending a screenshot and forgot to upload first!
> So that's not clear where on earth that is. c:\music\metallica\ride the
> lightning.mp3 is much better.
> The drive is the letter, the last one is the file, inbetween ones are folders.
> Why do you have file: at the start?
https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
> WTF is the triple slash for?
> Is the drive called Volumes or External?
> Far more complicated if you want to refer to that file. A program you've
> installed wanting to refer to something in its data folder for example.
>
>> One cool thing about macOS is how flexible it is with this -- you can have a
>> link to a file (or app) and then change the name of the file and move it and
>> the link still works. You can even do this with the file open (in most cases).
>>
>> Why should users have to remember a bunch of drive letters?
>
> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
> disk. If you add another floppy it's B:, if you add a CDROM or another hard
> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
> letter.
computer?
Commander Kinsey
Feb 20, 2022, 9:46:50 PM2/20/22
to
On Sun, 20 Feb 2022 23:22:46 -0000, Snit <brock.m...@gmail.com> wrote:
> On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
> <op.1hws3...@ryzen.lan>:
>
>> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>>
>>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>>> <op.1hv6b...@ryzen.lan>:
>>>
>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>> How do you enter a path for example? How can a program refer to a file if
>>>> there's no letter?
>>>
>>> It refers to it by name, and if needed the name of the drive.
>>>
>>> Just got the path to a file on an external drive. This is what it looks like
>>> (I did change the names for ease of reading):
>>>
>>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>>
>> Could you open up your firewall so I can access that image, which is on your
>> own computer.
>
> You would need my IP. It was just an example, as a path with your C drive
> would be.
I know your IP.
> On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
> <op.1hws3...@ryzen.lan>:
>
>> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>>
>>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>>> <op.1hv6b...@ryzen.lan>:
>>>
>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>> How do you enter a path for example? How can a program refer to a file if
>>>> there's no letter?
>>>
>>> It refers to it by name, and if needed the name of the drive.
>>>
>>> Just got the path to a file on an external drive. This is what it looks like
>>> (I did change the names for ease of reading):
>>>
>>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>>
>> Could you open up your firewall so I can access that image, which is on your
>> own computer.
>
> You would need my IP. It was just an example, as a path with your C drive
> would be.
>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>
> :)
>> So that's not clear where on earth that is. c:\music\metallica\ride the
>> lightning.mp3 is much better.
>
> How so?
>> The drive is the letter, the last one is the file, inbetween ones are folders.
>
> Pretty much the same but the first is noting it is in Volumes.
>
>> Why do you have file: at the start?
>
> It is a part of the URI.
>
> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>
>> WTF is the triple slash for?
>
> Part of the URI.
>> Is the drive called Volumes or External?
>
> The drive is "External".
>> Far more complicated if you want to refer to that file. A program you've
>> installed wanting to refer to something in its data folder for example.
>>
>>> One cool thing about macOS is how flexible it is with this -- you can have a
>>> link to a file (or app) and then change the name of the file and move it and
>>> the link still works. You can even do this with the file open (in most cases).
>>>
>>> Why should users have to remember a bunch of drive letters?
>>
>> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
>> disk. If you add another floppy it's B:, if you add a CDROM or another hard
>> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
>> letter.
>
> You have remembered them. So have I. But why do we need to just to use a
> computer?
Snit
Feb 20, 2022, 9:52:42 PM2/20/22
to
On Feb 20, 2022 at 7:46:47 PM MST, ""Commander Kinsey"" wrote
<op.1hw5z...@ryzen.lan>:
> On Sun, 20 Feb 2022 23:22:46 -0000, Snit <brock.m...@gmail.com> wrote:
>
>> On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
>> <op.1hws3...@ryzen.lan>:
>>
>>> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>>>
>>>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>>>> <op.1hv6b...@ryzen.lan>:
>>>>
>>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>>> How do you enter a path for example? How can a program refer to a file if
>>>>> there's no letter?
>>>>
>>>> It refers to it by name, and if needed the name of the drive.
>>>>
>>>> Just got the path to a file on an external drive. This is what it looks like
>>>> (I did change the names for ease of reading):
>>>>
>>>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>>>
>>> Could you open up your firewall so I can access that image, which is on your
>>> own computer.
>>
>> You would need my IP. It was just an example, as a path with your C drive
>> would be.
>
> I know your IP.
Fair enough.
>
>>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>>
>> :)
>
> Opera newsreader displayed it as a link. Perhaps the notation which looks very
> much like a URL confused it.
Likely.
>
>>> So that's not clear where on earth that is. c:\music\metallica\ride the
>>> lightning.mp3 is much better.
>>
>> How so?
>
> See the very next line.
As noted, it is pretty much the same -- but the human is not asked to figure
out letters instead of names.
>
>>> The drive is the letter, the last one is the file, inbetween ones are folders.
>>
>> Pretty much the same but the first is noting it is in Volumes.
>>
>>> Why do you have file: at the start?
>>
>> It is a part of the URI.
>>
>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>
>>> WTF is the triple slash for?
>>
>> Part of the URI.
>
> No idea what a URI is.
See the link, above. Posted with a URI. :)
> It seems absurd to use three slashes. And why are they facing the wrong way?
> I use forward slashes for switches. Eg. programname /help
I did not make the standard... but it is used on macOS, Windows, and Linux.
And more.
>
>>> Is the drive called Volumes or External?
>>
>> The drive is "External".
>
> So WTF is volumes for?
This might seem too obvious, but for volumes.
> Look, I write D: and you write file:///volumes/external. Which is shorter?
Shorter is not always better... and, really, I cannot think of when I have had
the need to write that out. I am sure I have at some point... but when?
>
>>> Far more complicated if you want to refer to that file. A program you've
>>> installed wanting to refer to something in its data folder for example.
>>>
>>>> One cool thing about macOS is how flexible it is with this -- you can have a
>>>> link to a file (or app) and then change the name of the file and move it and
>>>> the link still works. You can even do this with the file open (in most cases).
>>>>
>>>> Why should users have to remember a bunch of drive letters?
>>>
>>> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
>>> disk. If you add another floppy it's B:, if you add a CDROM or another hard
>>> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
>>> letter.
>>
>> You have remembered them. So have I. But why do we need to just to use a
>> computer?
>
> It doesn't take any effort, and is easier than remembering all that
> file:///volume shit. It's no different to remembering that 1 in your speed
> dial is your granddaughter and 2 is the president (see Stargate).
:)
<op.1hw5z...@ryzen.lan>:
> On Sun, 20 Feb 2022 23:22:46 -0000, Snit <brock.m...@gmail.com> wrote:
>
>> On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
>> <op.1hws3...@ryzen.lan>:
>>
>>> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>>>
>>>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>>>> <op.1hv6b...@ryzen.lan>:
>>>>
>>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>>> How do you enter a path for example? How can a program refer to a file if
>>>>> there's no letter?
>>>>
>>>> It refers to it by name, and if needed the name of the drive.
>>>>
>>>> Just got the path to a file on an external drive. This is what it looks like
>>>> (I did change the names for ease of reading):
>>>>
>>>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>>>
>>> Could you open up your firewall so I can access that image, which is on your
>>> own computer.
>>
>> You would need my IP. It was just an example, as a path with your C drive
>> would be.
>
> I know your IP.
>
>>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>>
>> :)
>
> Opera newsreader displayed it as a link. Perhaps the notation which looks very
> much like a URL confused it.
>
>>> So that's not clear where on earth that is. c:\music\metallica\ride the
>>> lightning.mp3 is much better.
>>
>> How so?
>
> See the very next line.
out letters instead of names.
>
>>> The drive is the letter, the last one is the file, inbetween ones are folders.
>>
>> Pretty much the same but the first is noting it is in Volumes.
>>
>>> Why do you have file: at the start?
>>
>> It is a part of the URI.
>>
>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>
>>> WTF is the triple slash for?
>>
>> Part of the URI.
>
> No idea what a URI is.
> It seems absurd to use three slashes. And why are they facing the wrong way?
> I use forward slashes for switches. Eg. programname /help
And more.
>
>>> Is the drive called Volumes or External?
>>
>> The drive is "External".
>
> So WTF is volumes for?
> Look, I write D: and you write file:///volumes/external. Which is shorter?
the need to write that out. I am sure I have at some point... but when?
>
>>> Far more complicated if you want to refer to that file. A program you've
>>> installed wanting to refer to something in its data folder for example.
>>>
>>>> One cool thing about macOS is how flexible it is with this -- you can have a
>>>> link to a file (or app) and then change the name of the file and move it and
>>>> the link still works. You can even do this with the file open (in most cases).
>>>>
>>>> Why should users have to remember a bunch of drive letters?
>>>
>>> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
>>> disk. If you add another floppy it's B:, if you add a CDROM or another hard
>>> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
>>> letter.
>>
>> You have remembered them. So have I. But why do we need to just to use a
>> computer?
>
> It doesn't take any effort, and is easier than remembering all that
> file:///volume shit. It's no different to remembering that 1 in your speed
> dial is your granddaughter and 2 is the president (see Stargate).
Commander Kinsey
Feb 20, 2022, 9:59:30 PM2/20/22
to
On Mon, 21 Feb 2022 02:52:40 -0000, Snit <brock.m...@gmail.com> wrote:
> On Feb 20, 2022 at 7:46:47 PM MST, ""Commander Kinsey"" wrote
> <op.1hw5z...@ryzen.lan>:
>
>> On Sun, 20 Feb 2022 23:22:46 -0000, Snit <brock.m...@gmail.com> wrote:
>>
>>> On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
>>> <op.1hws3...@ryzen.lan>:
>>>
>>>> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>>>>
>>>>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>>>>> <op.1hv6b...@ryzen.lan>:
>>>>>
>>>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>>>> How do you enter a path for example? How can a program refer to a file if
>>>>>> there's no letter?
>>>>>
>>>>> It refers to it by name, and if needed the name of the drive.
>>>>>
>>>>> Just got the path to a file on an external drive. This is what it looks like
>>>>> (I did change the names for ease of reading):
>>>>>
>>>>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>>>>
>>>> Could you open up your firewall so I can access that image, which is on your
>>>> own computer.
>>>
>>> You would need my IP. It was just an example, as a path with your C drive
>>> would be.
>>
>> I know your IP.
>
> Fair enough.
But can you work out where you let it slip? Hint: it wasn't in here.
> On Feb 20, 2022 at 7:46:47 PM MST, ""Commander Kinsey"" wrote
> <op.1hw5z...@ryzen.lan>:
>
>> On Sun, 20 Feb 2022 23:22:46 -0000, Snit <brock.m...@gmail.com> wrote:
>>
>>> On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
>>> <op.1hws3...@ryzen.lan>:
>>>
>>>> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>>>>
>>>>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>>>>> <op.1hv6b...@ryzen.lan>:
>>>>>
>>>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>>>> How do you enter a path for example? How can a program refer to a file if
>>>>>> there's no letter?
>>>>>
>>>>> It refers to it by name, and if needed the name of the drive.
>>>>>
>>>>> Just got the path to a file on an external drive. This is what it looks like
>>>>> (I did change the names for ease of reading):
>>>>>
>>>>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>>>>
>>>> Could you open up your firewall so I can access that image, which is on your
>>>> own computer.
>>>
>>> You would need my IP. It was just an example, as a path with your C drive
>>> would be.
>>
>> I know your IP.
>
> Fair enough.
>>>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>>>
>>> :)
>>
>> Opera newsreader displayed it as a link. Perhaps the notation which looks very
>> much like a URL confused it.
>
> Likely.
>>>> So that's not clear where on earth that is. c:\music\metallica\ride the
>>>> lightning.mp3 is much better.
>>>
>>> How so?
>>
>> See the very next line.
>
> As noted, it is pretty much the same -- but the human is not asked to figure
> out letters instead of names.
>>>> The drive is the letter, the last one is the file, inbetween ones are folders.
>>>
>>> Pretty much the same but the first is noting it is in Volumes.
>>>
>>>> Why do you have file: at the start?
>>>
>>> It is a part of the URI.
>>>
>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>>
>>>> WTF is the triple slash for?
>>>
>>> Part of the URI.
>>
>> No idea what a URI is.
>
> See the link, above. Posted with a URI. :)
>> It seems absurd to use three slashes. And why are they facing the wrong way?
>> I use forward slashes for switches. Eg. programname /help
>
> I did not make the standard... but it is used on macOS, Windows, and Linux.
> And more.
>>>> Is the drive called Volumes or External?
>>>
>>> The drive is "External".
>>
>> So WTF is volumes for?
>
> This might seem too obvious, but for volumes.
>> Look, I write D: and you write file:///volumes/external. Which is shorter?
>
> Shorter is not always better... and, really, I cannot think of when I have had
> the need to write that out. I am sure I have at some point... but when?
Snit
Feb 20, 2022, 10:10:35 PM2/20/22
to
On Feb 20, 2022 at 7:59:25 PM MST, ""Commander Kinsey"" wrote
<op.1hw6l...@ryzen.lan>:
> On Mon, 21 Feb 2022 02:52:40 -0000, Snit <brock.m...@gmail.com> wrote:
>
>> On Feb 20, 2022 at 7:46:47 PM MST, ""Commander Kinsey"" wrote
>> <op.1hw5z...@ryzen.lan>:
>>
>>> On Sun, 20 Feb 2022 23:22:46 -0000, Snit <brock.m...@gmail.com> wrote:
>>>
>>>> On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
>>>> <op.1hws3...@ryzen.lan>:
>>>>
>>>>> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>>>>>
>>>>>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>>>>>> <op.1hv6b...@ryzen.lan>:
>>>>>>
>>>>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>>>>> How do you enter a path for example? How can a program refer to a file if
>>>>>>> there's no letter?
>>>>>>
>>>>>> It refers to it by name, and if needed the name of the drive.
>>>>>>
>>>>>> Just got the path to a file on an external drive. This is what it looks like
>>>>>> (I did change the names for ease of reading):
>>>>>>
>>>>>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>>>>>
>>>>> Could you open up your firewall so I can access that image, which is on your
>>>>> own computer.
>>>>
>>>> You would need my IP. It was just an example, as a path with your C drive
>>>> would be.
>>>
>>> I know your IP.
>>
>> Fair enough.
>
> But can you work out where you let it slip? Hint: it wasn't in here.
I am well aware.
>>>>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>>>>
>>>> :)
>>>
>>> Opera newsreader displayed it as a link. Perhaps the notation which looks very
>>> much like a URL confused it.
>>
>> Likely.
>
> I wonder why they ended up so similar?
I believe a URL is a subset of URIs. I could be wrong on that.
>
>>>>> So that's not clear where on earth that is. c:\music\metallica\ride the
>>>>> lightning.mp3 is much better.
>>>>
>>>> How so?
>>>
>>> See the very next line.
>>
>> As noted, it is pretty much the same -- but the human is not asked to figure
>> out letters instead of names.
>
> Letters are quicker. Why do you think humans use anagrams?
Quicker to write... but having to remember computer letters to represent
drives is not as direct as names. Why do you give your files names? You could
have used c:\x\m\r.mp3
You did not. Much faster... but harder to use.
>
>>>>> The drive is the letter, the last one is the file, inbetween ones are folders.
>>>>
>>>> Pretty much the same but the first is noting it is in Volumes.
>>>>
>>>>> Why do you have file: at the start?
>>>>
>>>> It is a part of the URI.
>>>>
>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>>>
>>>>> WTF is the triple slash for?
>>>>
>>>> Part of the URI.
>>>
>>> No idea what a URI is.
>>
>> See the link, above. Posted with a URI. :)
>
> No doubt some made up shit by Jobs.
Nope.
>
>>> It seems absurd to use three slashes. And why are they facing the wrong way?
>>> I use forward slashes for switches. Eg. programname /help
>>
>> I did not make the standard... but it is used on macOS, Windows, and Linux.
>> And more.
>
> Windows does not use it for that purpose. It uses the backslash.
It also uses URIs.
https://docs.microsoft.com/en-us/uwp/api/windows.foundation.uri?view=winrt-22000
>
>>>>> Is the drive called Volumes or External?
>>>>
>>>> The drive is "External".
>>>
>>> So WTF is volumes for?
>>
>> This might seem too obvious, but for volumes.
>
> What else would you be referencing?
Maybe my home folder. Or the current folder. Or other folders.
>
>>> Look, I write D: and you write file:///volumes/external. Which is shorter?
>>
>> Shorter is not always better... and, really, I cannot think of when I have had
>> the need to write that out. I am sure I have at some point... but when?
>
> When you have letters, it's quicker than using the GUI. And think of
> programmers, or someone writing a script (as you do).
You did not use c:\x\m\r.mp3
>
>>>>> Far more complicated if you want to refer to that file. A program you've
>>>>> installed wanting to refer to something in its data folder for example.
>>>>>
>>>>>> One cool thing about macOS is how flexible it is with this -- you can have a
>>>>>> link to a file (or app) and then change the name of the file and move it and
>>>>>> the link still works. You can even do this with the file open (in most cases).
>>>>>>
>>>>>> Why should users have to remember a bunch of drive letters?
>>>>>
>>>>> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
>>>>> disk. If you add another floppy it's B:, if you add a CDROM or another hard
>>>>> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
>>>>> letter.
>>>>
>>>> You have remembered them. So have I. But why do we need to just to use a
>>>> computer?
>>>
>>> It doesn't take any effort, and is easier than remembering all that
>>> file:///volume shit. It's no different to remembering that 1 in your speed
>>> dial is your granddaughter and 2 is the president (see Stargate).
>>
>> :)
<op.1hw6l...@ryzen.lan>:
> On Mon, 21 Feb 2022 02:52:40 -0000, Snit <brock.m...@gmail.com> wrote:
>
>> On Feb 20, 2022 at 7:46:47 PM MST, ""Commander Kinsey"" wrote
>> <op.1hw5z...@ryzen.lan>:
>>
>>> On Sun, 20 Feb 2022 23:22:46 -0000, Snit <brock.m...@gmail.com> wrote:
>>>
>>>> On Feb 20, 2022 at 3:08:08 PM MST, ""Commander Kinsey"" wrote
>>>> <op.1hws3...@ryzen.lan>:
>>>>
>>>>> On Sun, 20 Feb 2022 18:42:45 -0000, Snit <brock.m...@gmail.com> wrote:
>>>>>
>>>>>> On Feb 20, 2022 at 6:55:54 AM MST, ""Commander Kinsey"" wrote
>>>>>> <op.1hv6b...@ryzen.lan>:
>>>>>>
>>>>>>> I mainly use PCs and thought, how do Mac users manage without drive letters?
>>>>>>> How do you enter a path for example? How can a program refer to a file if
>>>>>>> there's no letter?
>>>>>>
>>>>>> It refers to it by name, and if needed the name of the drive.
>>>>>>
>>>>>> Just got the path to a file on an external drive. This is what it looks like
>>>>>> (I did change the names for ease of reading):
>>>>>>
>>>>>> file:///Volumes/External/Bearizona/IMG_1234.jpg
>>>>>
>>>>> Could you open up your firewall so I can access that image, which is on your
>>>>> own computer.
>>>>
>>>> You would need my IP. It was just an example, as a path with your C drive
>>>> would be.
>>>
>>> I know your IP.
>>
>> Fair enough.
>
> But can you work out where you let it slip? Hint: it wasn't in here.
>>>>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>>>>
>>>> :)
>>>
>>> Opera newsreader displayed it as a link. Perhaps the notation which looks very
>>> much like a URL confused it.
>>
>> Likely.
>
> I wonder why they ended up so similar?
>
>>>>> So that's not clear where on earth that is. c:\music\metallica\ride the
>>>>> lightning.mp3 is much better.
>>>>
>>>> How so?
>>>
>>> See the very next line.
>>
>> As noted, it is pretty much the same -- but the human is not asked to figure
>> out letters instead of names.
>
> Letters are quicker. Why do you think humans use anagrams?
drives is not as direct as names. Why do you give your files names? You could
have used c:\x\m\r.mp3
You did not. Much faster... but harder to use.
>
>>>>> The drive is the letter, the last one is the file, inbetween ones are folders.
>>>>
>>>> Pretty much the same but the first is noting it is in Volumes.
>>>>
>>>>> Why do you have file: at the start?
>>>>
>>>> It is a part of the URI.
>>>>
>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>>>
>>>>> WTF is the triple slash for?
>>>>
>>>> Part of the URI.
>>>
>>> No idea what a URI is.
>>
>> See the link, above. Posted with a URI. :)
>
> No doubt some made up shit by Jobs.
>
>>> It seems absurd to use three slashes. And why are they facing the wrong way?
>>> I use forward slashes for switches. Eg. programname /help
>>
>> I did not make the standard... but it is used on macOS, Windows, and Linux.
>> And more.
>
> Windows does not use it for that purpose. It uses the backslash.
https://docs.microsoft.com/en-us/uwp/api/windows.foundation.uri?view=winrt-22000
>
>>>>> Is the drive called Volumes or External?
>>>>
>>>> The drive is "External".
>>>
>>> So WTF is volumes for?
>>
>> This might seem too obvious, but for volumes.
>
> What else would you be referencing?
>
>>> Look, I write D: and you write file:///volumes/external. Which is shorter?
>>
>> Shorter is not always better... and, really, I cannot think of when I have had
>> the need to write that out. I am sure I have at some point... but when?
>
> When you have letters, it's quicker than using the GUI. And think of
> programmers, or someone writing a script (as you do).
>
>>>>> Far more complicated if you want to refer to that file. A program you've
>>>>> installed wanting to refer to something in its data folder for example.
>>>>>
>>>>>> One cool thing about macOS is how flexible it is with this -- you can have a
>>>>>> link to a file (or app) and then change the name of the file and move it and
>>>>>> the link still works. You can even do this with the file open (in most cases).
>>>>>>
>>>>>> Why should users have to remember a bunch of drive letters?
>>>>>
>>>>> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
>>>>> disk. If you add another floppy it's B:, if you add a CDROM or another hard
>>>>> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
>>>>> letter.
>>>>
>>>> You have remembered them. So have I. But why do we need to just to use a
>>>> computer?
>>>
>>> It doesn't take any effort, and is easier than remembering all that
>>> file:///volume shit. It's no different to remembering that 1 in your speed
>>> dial is your granddaughter and 2 is the president (see Stargate).
>>
>> :)
Commander Kinsey
Feb 20, 2022, 10:15:55 PM2/20/22
to
>>>>>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>>>>>
>>>>> :)
>>>>
>>>> Opera newsreader displayed it as a link. Perhaps the notation which looks very
>>>> much like a URL confused it.
>>>
>>> Likely.
>>
>> I wonder why they ended up so similar?
>
> I believe a URL is a subset of URIs. I could be wrong on that.
>>>>>> So that's not clear where on earth that is. c:\music\metallica\ride the
>>>>>> lightning.mp3 is much better.
>>>>>
>>>>> How so?
>>>>
>>>> See the very next line.
>>>
>>> As noted, it is pretty much the same -- but the human is not asked to figure
>>> out letters instead of names.
>>
>> Letters are quicker. Why do you think humans use anagrams?
>
> Quicker to write... but having to remember computer letters to represent
> drives is not as direct as names. Why do you give your files names? You could
> have used c:\x\m\r.mp3
> You did not. Much faster... but harder to use.
>>>>>> The drive is the letter, the last one is the file, inbetween ones are folders.
>>>>>
>>>>> Pretty much the same but the first is noting it is in Volumes.
>>>>>
>>>>>> Why do you have file: at the start?
>>>>>
>>>>> It is a part of the URI.
>>>>>
>>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>>>>
>>>>>> WTF is the triple slash for?
>>>>>
>>>>> Part of the URI.
>>>>
>>>> No idea what a URI is.
>>>
>>> See the link, above. Posted with a URI. :)
>>
>> No doubt some made up shit by Jobs.
>
> Nope.
>>>> It seems absurd to use three slashes. And why are they facing the wrong way?
>>>> I use forward slashes for switches. Eg. programname /help
>>>
>>> I did not make the standard... but it is used on macOS, Windows, and Linux.
>>> And more.
>>
>> Windows does not use it for that purpose. It uses the backslash.
>
> It also uses URIs.
>
> https://docs.microsoft.com/en-us/uwp/api/windows.foundation.uri?view=winrt-22000
>>>>>> Is the drive called Volumes or External?
>>>>>
>>>>> The drive is "External".
>>>>
>>>> So WTF is volumes for?
>>>
>>> This might seem too obvious, but for volumes.
>>
>> What else would you be referencing?
>
> Maybe my home folder. Or the current folder. Or other folders.
>>>> Look, I write D: and you write file:///volumes/external. Which is shorter?
>>>
>>> Shorter is not always better... and, really, I cannot think of when I have had
>>> the need to write that out. I am sure I have at some point... but when?
>>
>> When you have letters, it's quicker than using the GUI. And think of
>> programmers, or someone writing a script (as you do).
>
> You did not use c:\x\m\r.mp3
Bob Campbell
Feb 20, 2022, 11:35:40 PM2/20/22
to
Spoken like a truly clueless newbie. The internet is based on Unix/Linux.
Not Macs and certainly not Windows.
>
> Then he stole it from Linux. At least MS designed theirs from scratch.
>
Spoken like a truly clueless newbie. Nothing was “stolen from Linux”.
MacOS is based on Unix, which predates Linux by decades.
Also, MS designed NOTHING here. DOS was purchased from Seattle Computer
Products, not written in-house at MS. The SCP product 86-DOS was designed
to be CP/M compatible. Drive letters came directly from CP/M.
> Not enough letters to do that for everything. But nobody has more than
> 26 drives. Although DOS and Windows Server allows AA, BB, etc.
>
Spoken like a truly clueless newbie. Certainly no one using Windows has
that many drives. Unix and Linux run on mainframes. Do you think
mainframes are limited to 24 drives?
The real question is, how does Windows get along with the 42 year old
concept of drive letters and the totally arbitrary limit of 24 drives?
Not Macs and certainly not Windows.
>
> Then he stole it from Linux. At least MS designed theirs from scratch.
>
MacOS is based on Unix, which predates Linux by decades.
Also, MS designed NOTHING here. DOS was purchased from Seattle Computer
Products, not written in-house at MS. The SCP product 86-DOS was designed
to be CP/M compatible. Drive letters came directly from CP/M.
> Not enough letters to do that for everything. But nobody has more than
> 26 drives. Although DOS and Windows Server allows AA, BB, etc.
>
that many drives. Unix and Linux run on mainframes. Do you think
mainframes are limited to 24 drives?
The real question is, how does Windows get along with the 42 year old
concept of drive letters and the totally arbitrary limit of 24 drives?
Commander Kinsey
Feb 21, 2022, 12:23:36 AM2/21/22
to
On Mon, 21 Feb 2022 04:35:34 -0000, Bob Campbell <no...@none.none> wrote:
> Commander Kinsey <C...@nospam.com> wrote:
>>
>> The whole internet is based on Macs!?
>
> Spoken like a truly clueless newbie. The internet is based on Unix/Linux.
> Not Macs and certainly not Windows.
Whoosh!
> Commander Kinsey <C...@nospam.com> wrote:
>>
>> The whole internet is based on Macs!?
>
> Spoken like a truly clueless newbie. The internet is based on Unix/Linux.
> Not Macs and certainly not Windows.
>> Then he stole it from Linux. At least MS designed theirs from scratch.
>
> Spoken like a truly clueless newbie. Nothing was “stolen from Linux”.
> MacOS is based on Unix, which predates Linux by decades.
> Also, MS designed NOTHING here. DOS was purchased from Seattle Computer
> Products, not written in-house at MS. The SCP product 86-DOS was designed
> to be CP/M compatible. Drive letters came directly from CP/M.
>> Not enough letters to do that for everything. But nobody has more than
>> 26 drives. Although DOS and Windows Server allows AA, BB, etc.
>
> Spoken like a truly clueless newbie. Certainly no one using Windows has
> that many drives. Unix and Linux run on mainframes. Do you think
> mainframes are limited to 24 drives?
"Not enough letters to do that for everything" was in reply to Snit which you stupidly snipped. He'd referred to letters for folders and files.
I never suggested Windows desktop has that many drives. But servers do. Servers can run Windows, we don't have to put geeky stuff on there.
> The real question is, how does Windows get along with the 42 year old
> concept of drive letters
> and the totally arbitrary limit of 24 drives?
nospam
Feb 21, 2022, 12:39:51 AM2/21/22
to
In article <op.1hxc9...@ryzen.lan>, Commander Kinsey
<C...@nospam.com> wrote:
> > Also, MS designed NOTHING here. DOS was purchased from Seattle Computer
> > Products, not written in-house at MS. The SCP product 86-DOS was designed
> > to be CP/M compatible. Drive letters came directly from CP/M.
>
> DOS was designed by Gates in a garage, this is common knowledge.
nope. he bought it.
> > Also, MS designed NOTHING here. DOS was purchased from Seattle Computer
> > Products, not written in-house at MS. The SCP product 86-DOS was designed
> > to be CP/M compatible. Drive letters came directly from CP/M.
>
> DOS was designed by Gates in a garage, this is common knowledge.
nospam
Feb 21, 2022, 12:39:52 AM2/21/22
to
In article <op.1hw7c...@ryzen.lan>, Commander Kinsey
had nothing to do with that level of the os anyway.
> At least MS designed theirs from scratch.
so did apple.
classic mac os did not use drive letters nor did it use file: urls,
which also did not exist at that time. classic mac os also didn't use
path names, except in very specific circumstances. because of that,
files could (and often did) move without any problems, even when open.
<C...@nospam.com> wrote:
> >>>>>> Why do you have file: at the start?
> >>>>>
> >>>>> It is a part of the URI.
> >>>>>
> >>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
> >>>>>
> >>>>>> WTF is the triple slash for?
> >>>>>
> >>>>> Part of the URI.
> >>>>
> >>>> No idea what a URI is.
> >>>
> >>> See the link, above. Posted with a URI. :)
> >>
> >> No doubt some made up shit by Jobs.
> >
> > Nope.
>
> Then he stole it from Linux.
nope. linux didn't exist when the original mac was designed, and jobs
> >>>>>> Why do you have file: at the start?
> >>>>>
> >>>>> It is a part of the URI.
> >>>>>
> >>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
> >>>>>
> >>>>>> WTF is the triple slash for?
> >>>>>
> >>>>> Part of the URI.
> >>>>
> >>>> No idea what a URI is.
> >>>
> >>> See the link, above. Posted with a URI. :)
> >>
> >> No doubt some made up shit by Jobs.
> >
> > Nope.
>
> Then he stole it from Linux.
had nothing to do with that level of the os anyway.
> At least MS designed theirs from scratch.
classic mac os did not use drive letters nor did it use file: urls,
which also did not exist at that time. classic mac os also didn't use
path names, except in very specific circumstances. because of that,
files could (and often did) move without any problems, even when open.
Snit
Feb 21, 2022, 1:32:56 AM2/21/22
to
On Feb 20, 2022 at 10:39:49 PM MST, "nospam" wrote
<210220220039495606%nos...@nospam.invalid>:
> In article <op.1hw7c...@ryzen.lan>, Commander Kinsey
> <C...@nospam.com> wrote:
>
>
>>>>>>>> Why do you have file: at the start?
>>>>>>>
>>>>>>> It is a part of the URI.
>>>>>>>
>>>>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>>>>>>
>>>>>>>> WTF is the triple slash for?
>>>>>>>
>>>>>>> Part of the URI.
>>>>>>
>>>>>> No idea what a URI is.
>>>>>
>>>>> See the link, above. Posted with a URI. :)
>>>>
>>>> No doubt some made up shit by Jobs.
>>>
>>> Nope.
>>
>> Then he stole it from Linux.
>
> nope. linux didn't exist when the original mac was designed, and jobs
> had nothing to do with that level of the os anyway.
I would not say "nothing" -- but not his focus.
>> At least MS designed theirs from scratch.
>
> so did apple.
With Classic Mac, yes. With macOS they got it from NeXT -- though that was
with Jobs as well. But that came from different Unix backgrounds.
But so what? The Windows UI largely came from Apple.
<210220220039495606%nos...@nospam.invalid>:
> In article <op.1hw7c...@ryzen.lan>, Commander Kinsey
> <C...@nospam.com> wrote:
>
>
>>>>>>>> Why do you have file: at the start?
>>>>>>>
>>>>>>> It is a part of the URI.
>>>>>>>
>>>>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>>>>>>
>>>>>>>> WTF is the triple slash for?
>>>>>>>
>>>>>>> Part of the URI.
>>>>>>
>>>>>> No idea what a URI is.
>>>>>
>>>>> See the link, above. Posted with a URI. :)
>>>>
>>>> No doubt some made up shit by Jobs.
>>>
>>> Nope.
>>
>> Then he stole it from Linux.
>
> nope. linux didn't exist when the original mac was designed, and jobs
> had nothing to do with that level of the os anyway.
>> At least MS designed theirs from scratch.
>
> so did apple.
with Jobs as well. But that came from different Unix backgrounds.
But so what? The Windows UI largely came from Apple.
>
> classic mac os did not use drive letters nor did it use file: urls,
> which also did not exist at that time. classic mac os also didn't use
> path names, except in very specific circumstances. because of that,
> files could (and often did) move without any problems, even when open.
> classic mac os did not use drive letters nor did it use file: urls,
> which also did not exist at that time. classic mac os also didn't use
> path names, except in very specific circumstances. because of that,
> files could (and often did) move without any problems, even when open.
Snit
Feb 21, 2022, 1:33:52 AM2/21/22
to
On Feb 20, 2022 at 10:23:32 PM MST, ""Commander Kinsey"" wrote
<op.1hxc9...@ryzen.lan>:
>
>> Also, MS designed NOTHING here. DOS was purchased from Seattle Computer
>> Products, not written in-house at MS. The SCP product 86-DOS was designed
>> to be CP/M compatible. Drive letters came directly from CP/M.
>
> DOS was designed by Gates in a garage, this is common knowledge.
Common knowledge or not, it is not accurate.
<op.1hxc9...@ryzen.lan>:
>
>> Also, MS designed NOTHING here. DOS was purchased from Seattle Computer
>> Products, not written in-house at MS. The SCP product 86-DOS was designed
>> to be CP/M compatible. Drive letters came directly from CP/M.
>
> DOS was designed by Gates in a garage, this is common knowledge.
Snit
Feb 21, 2022, 1:40:32 AM2/21/22
to
On Feb 20, 2022 at 8:15:50 PM MST, ""Commander Kinsey"" wrote
<op.1hw7c...@ryzen.lan>:
Hmmm, then maybe I am not aware.
But, really, even if Gremlin/LegionX finds it I am not that concerned. I am
not as impressed with his abilities as others seem to be. All I see is talk
from him. Well, when I look.
>
>>>>>>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>>>>>>
>>>>>> :)
>>>>>
>>>>> Opera newsreader displayed it as a link. Perhaps the notation which looks very
>>>>> much like a URL confused it.
>>>>
>>>> Likely.
>>>
>>> I wonder why they ended up so similar?
>>
>> I believe a URL is a subset of URIs. I could be wrong on that.
>
> The whole internet is based on Macs!?
Huh? The URI scheme existed before OS X / macOS.
>
>>>>>>> So that's not clear where on earth that is. c:\music\metallica\ride the
>>>>>>> lightning.mp3 is much better.
>>>>>>
>>>>>> How so?
>>>>>
>>>>> See the very next line.
>>>>
>>>> As noted, it is pretty much the same -- but the human is not asked to figure
>>>> out letters instead of names.
>>>
>>> Letters are quicker. Why do you think humans use anagrams?
>>
>> Quicker to write... but having to remember computer letters to represent
>> drives is not as direct as names. Why do you give your files names? You could
>> have used c:\x\m\r.mp3
>> You did not. Much faster... but harder to use.
>
> There are many files and folders. I only have two letters on this machine, and
> a third if I plug in a USB stick or backup disk. C: is the SSD, E: is the hard
> disk.
And how many disks do you have? I like knowing what they are by name... as you
do with files. Heck, I have three external USB drives... if I plug then in
differently should I have to figure out what letter they NOW have?
>
>>>>>>> The drive is the letter, the last one is the file, inbetween ones are folders.
>>>>>>
>>>>>> Pretty much the same but the first is noting it is in Volumes.
>>>>>>
>>>>>>> Why do you have file: at the start?
>>>>>>
>>>>>> It is a part of the URI.
>>>>>>
>>>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>>>>>
>>>>>>> WTF is the triple slash for?
>>>>>>
>>>>>> Part of the URI.
>>>>>
>>>>> No idea what a URI is.
>>>>
>>>> See the link, above. Posted with a URI. :)
>>>
>>> No doubt some made up shit by Jobs.
>>
>> Nope.
>
> Then he stole it from Linux. At least MS designed theirs from scratch.
URI's were defined, I think, by the Internet Engineering Task Force.
>
>>>>> It seems absurd to use three slashes. And why are they facing the wrong way?
>>>>> I use forward slashes for switches. Eg. programname /help
>>>>
>>>> I did not make the standard... but it is used on macOS, Windows, and Linux.
>>>> And more.
>>>
>>> Windows does not use it for that purpose. It uses the backslash.
>>
>> It also uses URIs.
>>
>> https://docs.microsoft.com/en-us/uwp/api/windows.foundation.uri?view=winrt-22000
>
> Only for aliasing certain system folders which could be placed anywhere
> depending on user preference.
Still uses them.
>
>>>>>>> Is the drive called Volumes or External?
>>>>>>
>>>>>> The drive is "External".
>>>>>
>>>>> So WTF is volumes for?
>>>>
>>>> This might seem too obvious, but for volumes.
>>>
>>> What else would you be referencing?
>>
>> Maybe my home folder. Or the current folder. Or other folders.
>
> c:\documents
\documents. Takes me to the root folder and then documents. If I want to
specify a different volume I will call it out by name. Like you do with files.
And that name will be the same no matter what Mac I connect it to.
>
>>>>> Look, I write D: and you write file:///volumes/external. Which is shorter?
>>>>
>>>> Shorter is not always better... and, really, I cannot think of when I have had
>>>> the need to write that out. I am sure I have at some point... but when?
>>>
>>> When you have letters, it's quicker than using the GUI. And think of
>>> programmers, or someone writing a script (as you do).
>>
>> You did not use c:\x\m\r.mp3
>
> Not enough letters to do that for everything. But nobody has more than 26
> drives. Although DOS and Windows Server allows AA, BB, etc.
USB allows for, what... 127 devices? Something like that. But the point was
you used names for everything else... so why not the drive?
>
>>>>>>> Far more complicated if you want to refer to that file. A program you've
>>>>>>> installed wanting to refer to something in its data folder for example.
>>>>>>>
>>>>>>>> One cool thing about macOS is how flexible it is with this -- you can have a
>>>>>>>> link to a file (or app) and then change the name of the file and move it and
>>>>>>>> the link still works. You can even do this with the file open (in most cases).
>>>>>>>>
>>>>>>>> Why should users have to remember a bunch of drive letters?
>>>>>>>
>>>>>>> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
>>>>>>> disk. If you add another floppy it's B:, if you add a CDROM or another hard
>>>>>>> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
>>>>>>> letter.
>>>>>>
>>>>>> You have remembered them. So have I. But why do we need to just to use a
>>>>>> computer?
>>>>>
>>>>> It doesn't take any effort, and is easier than remembering all that
>>>>> file:///volume shit. It's no different to remembering that 1 in your speed
>>>>> dial is your granddaughter and 2 is the president (see Stargate).
>>>>
>>>> :)
<op.1hw7c...@ryzen.lan>:
But, really, even if Gremlin/LegionX finds it I am not that concerned. I am
not as impressed with his abilities as others seem to be. All I see is talk
from him. Well, when I look.
>
>>>>>>> Oh.... I thought you were sending a screenshot and forgot to upload first!
>>>>>>
>>>>>> :)
>>>>>
>>>>> Opera newsreader displayed it as a link. Perhaps the notation which looks very
>>>>> much like a URL confused it.
>>>>
>>>> Likely.
>>>
>>> I wonder why they ended up so similar?
>>
>> I believe a URL is a subset of URIs. I could be wrong on that.
>
> The whole internet is based on Macs!?
>
>>>>>>> So that's not clear where on earth that is. c:\music\metallica\ride the
>>>>>>> lightning.mp3 is much better.
>>>>>>
>>>>>> How so?
>>>>>
>>>>> See the very next line.
>>>>
>>>> As noted, it is pretty much the same -- but the human is not asked to figure
>>>> out letters instead of names.
>>>
>>> Letters are quicker. Why do you think humans use anagrams?
>>
>> Quicker to write... but having to remember computer letters to represent
>> drives is not as direct as names. Why do you give your files names? You could
>> have used c:\x\m\r.mp3
>> You did not. Much faster... but harder to use.
>
> There are many files and folders. I only have two letters on this machine, and
> a third if I plug in a USB stick or backup disk. C: is the SSD, E: is the hard
> disk.
do with files. Heck, I have three external USB drives... if I plug then in
differently should I have to figure out what letter they NOW have?
>
>>>>>>> The drive is the letter, the last one is the file, inbetween ones are folders.
>>>>>>
>>>>>> Pretty much the same but the first is noting it is in Volumes.
>>>>>>
>>>>>>> Why do you have file: at the start?
>>>>>>
>>>>>> It is a part of the URI.
>>>>>>
>>>>>> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier
>>>>>>
>>>>>>> WTF is the triple slash for?
>>>>>>
>>>>>> Part of the URI.
>>>>>
>>>>> No idea what a URI is.
>>>>
>>>> See the link, above. Posted with a URI. :)
>>>
>>> No doubt some made up shit by Jobs.
>>
>> Nope.
>
> Then he stole it from Linux. At least MS designed theirs from scratch.
>
>>>>> It seems absurd to use three slashes. And why are they facing the wrong way?
>>>>> I use forward slashes for switches. Eg. programname /help
>>>>
>>>> I did not make the standard... but it is used on macOS, Windows, and Linux.
>>>> And more.
>>>
>>> Windows does not use it for that purpose. It uses the backslash.
>>
>> It also uses URIs.
>>
>> https://docs.microsoft.com/en-us/uwp/api/windows.foundation.uri?view=winrt-22000
>
> Only for aliasing certain system folders which could be placed anywhere
> depending on user preference.
>
>>>>>>> Is the drive called Volumes or External?
>>>>>>
>>>>>> The drive is "External".
>>>>>
>>>>> So WTF is volumes for?
>>>>
>>>> This might seem too obvious, but for volumes.
>>>
>>> What else would you be referencing?
>>
>> Maybe my home folder. Or the current folder. Or other folders.
>
> c:\documents
specify a different volume I will call it out by name. Like you do with files.
And that name will be the same no matter what Mac I connect it to.
>
>>>>> Look, I write D: and you write file:///volumes/external. Which is shorter?
>>>>
>>>> Shorter is not always better... and, really, I cannot think of when I have had
>>>> the need to write that out. I am sure I have at some point... but when?
>>>
>>> When you have letters, it's quicker than using the GUI. And think of
>>> programmers, or someone writing a script (as you do).
>>
>> You did not use c:\x\m\r.mp3
>
> Not enough letters to do that for everything. But nobody has more than 26
> drives. Although DOS and Windows Server allows AA, BB, etc.
you used names for everything else... so why not the drive?
>
>>>>>>> Far more complicated if you want to refer to that file. A program you've
>>>>>>> installed wanting to refer to something in its data folder for example.
>>>>>>>
>>>>>>>> One cool thing about macOS is how flexible it is with this -- you can have a
>>>>>>>> link to a file (or app) and then change the name of the file and move it and
>>>>>>>> the link still works. You can even do this with the file open (in most cases).
>>>>>>>>
>>>>>>>> Why should users have to remember a bunch of drive letters?
>>>>>>>
>>>>>>> They don't. Everybody knows it's A: for floppy (not used now), C: for hard
>>>>>>> disk. If you add another floppy it's B:, if you add a CDROM or another hard
>>>>>>> drive it's D: etc. Or you cna get fancy and call a folder or partition a drive
>>>>>>> letter.
>>>>>>
>>>>>> You have remembered them. So have I. But why do we need to just to use a
>>>>>> computer?
>>>>>
>>>>> It doesn't take any effort, and is easier than remembering all that
>>>>> file:///volume shit. It's no different to remembering that 1 in your speed
>>>>> dial is your granddaughter and 2 is the president (see Stargate).
>>>>
>>>> :)
nospam
Feb 21, 2022, 1:46:36 AM2/21/22