Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #56572 > unrolled thread
| Started by | Siri Cruz <chine.bleu@yahoo.com> |
|---|---|
| First post | 2014-02-15 19:08 -0800 |
| Last post | 2014-03-03 15:18 +0000 |
| Articles | 20 on this page of 24 — 13 participants |
Back to article view | Back to comp.sys.mac.system
Case sensitive file system? Siri Cruz <chine.bleu@yahoo.com> - 2014-02-15 19:08 -0800
Re: Case sensitive file system? Ian Collins <ian-news@hotmail.com> - 2014-02-16 16:15 +1300
Re: Case sensitive file system? Kaz Kylheku <kaz@kylheku.com> - 2014-02-16 03:19 +0000
Re: Case sensitive file system? Jolly Roger <jollyroger@pobox.com> - 2014-02-16 03:29 +0000
Re: Case sensitive file system? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-16 01:01 -0500
Re: Case sensitive file system? Barry Margolin <barmar@alum.mit.edu> - 2014-02-16 02:14 -0500
Re: Case sensitive file system? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-16 16:56 -0500
Re: Case sensitive file system? Jolly Roger <jollyroger@pobox.com> - 2014-02-16 15:53 +0000
Re: Case sensitive file system? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-16 17:01 -0500
Re: Case sensitive file system? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-16 06:08 +0000
Re: Case sensitive file system? Jolly Roger <jollyroger@pobox.com> - 2014-02-16 15:49 +0000
Re: Case sensitive file system? David Ritz <dritz@mindspring.com> - 2014-02-15 22:28 -0600
Re: Case sensitive file system? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-16 06:05 +0000
Re: Case sensitive file system? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-16 09:18 -0500
Re: Case sensitive file system? Michael Vilain <vilain@NOspamcop.net> - 2014-02-15 23:28 -0800
Re: Case sensitive file system? Siri Cruz <chine.bleu@yahoo.com> - 2014-02-16 04:24 -0800
Re: Case sensitive file system? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-16 09:17 -0500
Re: Case sensitive file system? Kaz Kylheku <kaz@kylheku.com> - 2014-03-02 18:19 +0000
Re: Case sensitive file system? Michael Vilain <vilain@NOspamcop.net> - 2014-03-02 12:37 -0800
Re: Case sensitive file system? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-03-02 20:23 -0500
Re: Case sensitive file system? scott@slp53.sl.home (Scott Lurndal) - 2014-03-03 15:06 +0000
Re: Case sensitive file system? Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2014-03-03 15:10 +0000
Re: Case sensitive file system? scott@slp53.sl.home (Scott Lurndal) - 2014-03-03 16:59 +0000
Re: Case sensitive file system? Tim Streater <timstreater@greenbee.net> - 2014-03-03 15:18 +0000
Page 1 of 2 [1] 2 Next page →
| From | Siri Cruz <chine.bleu@yahoo.com> |
|---|---|
| Date | 2014-02-15 19:08 -0800 |
| Subject | Case sensitive file system? |
| Message-ID | <chine.bleu-1E20C5.19082615022014@news.eternal-september.org> |
Is there a simple way in a program to see if a file system uses case sensitive names (like traditional Unix) or case irrelevant (like plain old HFS+)? -- :-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted. 'I desire mercy, not sacrifice.'
[toc] | [next] | [standalone]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Date | 2014-02-16 16:15 +1300 |
| Message-ID | <bmaoquFdje3U2@mid.individual.net> |
| In reply to | #56572 |
Siri Cruz wrote: > Is there a simple way in a program to see if a file system uses case sensitive > names (like traditional Unix) or case irrelevant (like plain old HFS+)? If open "ZZ? fails, create "zz" and try to open "ZZ"? -- Ian Collins
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <kaz@kylheku.com> |
|---|---|
| Date | 2014-02-16 03:19 +0000 |
| Message-ID | <20140215190913.4@kylheku.com> |
| In reply to | #56572 |
On 2014-02-16, Siri Cruz <chine.bleu@yahoo.com> wrote: > Is there a simple way in a program to see if a file system uses case sensitive > names (like traditional Unix) or case irrelevant (like plain old HFS+)? Make a temporary directory in that filesystem, and there create a file "fOO" or some such mixed-case identifier. If you can open it as "foo", the system is case-insensitive. Then list the directory. If the name lists as "fOO", then it is case-preserving. If it appears as "foo" or "FOO", it is case folding. Is there are nondestructive way to just find out this info? I don't think so. There is nothing *standard* out of pathconf or fstat. Mac OS/Darwin evidently has a _PC_CASE_SENSITIVE constant that can be used with pathconf. You could detect this in a C program with #ifdef to implement the test more efficiently. It appears there is also a _PC_CASE_PRESERVING. I'd detect these individually to short-circuit the relevant parts of the logic, such that if both are provided, then no temporary modification of the filesystem takes place. -- Music DIY Mailing List: http://www.kylheku.com/diy ADA MP-1 Mailing List: http://www.kylheku.com/mp1
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-02-16 03:29 +0000 |
| Message-ID | <bmapkvFsm3rU1@mid.individual.net> |
| In reply to | #56572 |
On 2014-02-16, Siri Cruz <chine.bleu@yahoo.com> wrote:
>
> Is there a simple way in a program to see if a file system uses case
> sensitive names (like traditional Unix) or case irrelevant (like plain
> old HFS+)?
This command will tell you whether or not the boot device is
case-sensitive:
# diskutil info `df / | sed -e /Filesystem/d | awk '{print $1}'` | grep
"Personality"
File System Personality: Journaled HFS+
If it's case-sensitive, it will say: "Case-sensitive Journaled HFS+".
Otherwise it will just say: "Journaled HFS+".
--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.
JR
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-02-16 01:01 -0500 |
| Message-ID | <5300541d$0$22469$c3e8da3$f6268168@news.astraweb.com> |
| In reply to | #56575 |
On 14-02-15 22:29, Jolly Roger wrote:
> # diskutil info `df / | sed -e /Filesystem/d | awk '{print $1}'` | grep
> "Personality"
Can you explain the `df ?
Bash doesn't take kindly to unclosed quotes (or in this case grave accent)
Can you explain what the sed -e /Filesystem/d does ? and why the awk to
print the lines ?
> File System Personality: Journaled HFS+
Snow Leopard Server:
File System: Journaled HFS+
Type: hfs
Name: Mac OS Extended (Journaled)
Journal: Journal size 81920 KB at offset 0x1d1c000
Owners: Enabled
So the word "Personality" may not be standard across all
platfiorms/versions.
[toc] | [prev] | [next] | [standalone]
| From | Barry Margolin <barmar@alum.mit.edu> |
|---|---|
| Date | 2014-02-16 02:14 -0500 |
| Message-ID | <barmar-1D1AC4.02142616022014@news.eternal-september.org> |
| In reply to | #56577 |
In article <5300541d$0$22469$c3e8da3$f6268168@news.astraweb.com>,
JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 14-02-15 22:29, Jolly Roger wrote:
>
> > # diskutil info `df / | sed -e /Filesystem/d | awk '{print $1}'` | grep
> > "Personality"
>
> Can you explain the `df ?
This runs df /, which prints information about the root filesystem,
removes the heading line, then uses awk to get the first column, which
is the disk device that the filesystem is mounted on. The backticks
substitute the output of that command into the original command line.
On my system
df / | sed -e /Filesystem/d | awk '{print $1}'
prints:
/dev/disk0s2
so it's equivalent to:
# diskutil info /dev/disk0s2 | grep "Personality"
>
> Bash doesn't take kindly to unclosed quotes (or in this case grave accent)
It's not unclosed. You can have multiple commands inside backticks. The
closing backtick is after the awk command.
>
> Can you explain what the sed -e /Filesystem/d does ? and why the awk to
> print the lines ?
"sed -e /Filesystem/d" deletes all lines that contain Filesystem, i.e.
the heading line that df prints.
"awk '{print $1}'" prints the first field of each line.
>
>
>
>
>
> > File System Personality: Journaled HFS+
>
> Snow Leopard Server:
>
>
> File System: Journaled HFS+
> Type: hfs
> Name: Mac OS Extended (Journaled)
> Journal: Journal size 81920 KB at offset 0x1d1c000
> Owners: Enabled
>
> So the word "Personality" may not be standard across all
> platfiorms/versions.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-02-16 16:56 -0500 |
| Message-ID | <53013420$0$55750$c3e8da3$b280bf18@news.astraweb.com> |
| In reply to | #56580 |
On 14-02-16 02:14, Barry Margolin wrote:
>> > # diskutil info `df / | sed -e /Filesystem/d | awk '{print $1}'` | grep
>> > "Personality"
> On my system
>
> df / | sed -e /Filesystem/d | awk '{print $1}'
>
> prints:
>
> /dev/disk0s2
>
Thanks for explanation. I had not noticed the closing ` after the awk
command and was trying to mentally parse the command sequentially and
trying diskutil info 'df thinking its output was going to the sed
command etc etc.
Learn something new everyday.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-02-16 15:53 +0000 |
| Message-ID | <bmc58eF71g0U2@mid.individual.net> |
| In reply to | #56577 |
On 2014-02-16, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 14-02-15 22:29, Jolly Roger wrote:
>
>> # diskutil info `df / | sed -e /Filesystem/d | awk '{print $1}'` | grep
>> "Personality"
>
> Can you explain the `df ?
>
> Bash doesn't take kindly to unclosed quotes (or in this case grave accent)
>
> Can you explain what the sed -e /Filesystem/d does ? and why the awk to
> print the lines ?
Barry explained sufficiently. Though, as Lewis mentioned, since
diskutil info accepts file system paths (such as /), all of this is
overkill. (Thanks again, Lewis.)
>> File System Personality: Journaled HFS+
>
> Snow Leopard Server:
>
>
> File System: Journaled HFS+
> Type: hfs
> Name: Mac OS Extended (Journaled)
> Journal: Journal size 81920 KB at offset 0x1d1c000
> Owners: Enabled
>
> So the word "Personality" may not be standard across all
> platfiorms/versions.
So, instead use:
# diskutil info / | grep "File System"
File System Personality: Journaled HFS+
--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.
JR
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-02-16 17:01 -0500 |
| Message-ID | <5301352a$0$55750$c3e8da3$b280bf18@news.astraweb.com> |
| In reply to | #56598 |
On 14-02-16 10:53, Jolly Roger wrote: > Barry explained sufficiently. Though, as Lewis mentioned, since > diskutil info accepts file system paths (such as /), all of this is > overkill. (Thanks again, Lewis.) You can also specify mount points such as /volumes/mydisk For instance, on my server / and /volumes/DMA1 produce the same diskutil info output, and I can specify other disks on the system. (I realise that consumer Macs only have 1 disk, but Macpros and Xserves have multiple drives).
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-02-16 06:08 +0000 |
| Message-ID | <slrnlg0leu.27s1.g.kreme@oswin.local> |
| In reply to | #56575 |
In message <bmapkvFsm3rU1@mid.individual.net>
Jolly Roger <jollyroger@pobox.com> wrote:
> On 2014-02-16, Siri Cruz <chine.bleu@yahoo.com> wrote:
>>
>> Is there a simple way in a program to see if a file system uses case
>> sensitive names (like traditional Unix) or case irrelevant (like plain
>> old HFS+)?
> This command will tell you whether or not the boot device is
> case-sensitive:
> # diskutil info `df / | sed -e /Filesystem/d | awk '{print $1}'` | grep
> "Personality"
> File System Personality: Journaled HFS+
$ diskutil info / | grep " HFS"
File System Personality: Journaled HFS+
--
'Vetinari isn't mad.' 'Depends how you look at it. No one can be as sane
as he is without being mad.' --Feet of Clay
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-02-16 15:49 +0000 |
| Message-ID | <bmc50gF71g0U1@mid.individual.net> |
| In reply to | #56579 |
On 2014-02-16, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
> In message <bmapkvFsm3rU1@mid.individual.net>
> Jolly Roger <jollyroger@pobox.com> wrote:
>> On 2014-02-16, Siri Cruz <chine.bleu@yahoo.com> wrote:
>>>
>>> Is there a simple way in a program to see if a file system uses case
>>> sensitive names (like traditional Unix) or case irrelevant (like plain
>>> old HFS+)?
>
>> This command will tell you whether or not the boot device is
>> case-sensitive:
>
>> # diskutil info `df / | sed -e /Filesystem/d | awk '{print $1}'` | grep
>> "Personality"
>
>> File System Personality: Journaled HFS+
>
> $ diskutil info / | grep " HFS"
> File System Personality: Journaled HFS+
Ah, cool. Didn't realize diskutil info took a fil system path. Even better.
Thanks.
--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.
JR
[toc] | [prev] | [next] | [standalone]
| From | David Ritz <dritz@mindspring.com> |
|---|---|
| Date | 2014-02-15 22:28 -0600 |
| Message-ID | <alpine.OSX.2.11.1402152227180.13244@mako.ath.cx> |
| In reply to | #56572 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 15 February 2014 19:08 -0800, in article <chine.bleu-1E20C5.19082615022014@news.eternal-september.org>, Siri Cruz <chine.bleu@yahoo.com> wrote: > Is there a simple way in a program to see if a file system uses case > sensitive names (like traditional Unix) or case irrelevant (like > plain old HFS+)? $ diskutil info disk0s2 | grep File File System Personality: Journaled HFS+ - -- David Ritz <dritz@mindspring.com> Be kind to animals; kiss a shark. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (Darwin) iEYEARECAAYFAlMAPlsACgkQUrwpmRoS3uu0JACghZzt5EnQPb25R5ilIKGhZEef 8gsAn0Fsc6gEoeeyzBLTEfF/89aRSWNV =3nqS -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-02-16 06:05 +0000 |
| Message-ID | <slrnlg0l8h.27s1.g.kreme@oswin.local> |
| In reply to | #56572 |
In message <chine.bleu-1E20C5.19082615022014@news.eternal-september.org> Siri Cruz <chine.bleu@yahoo.com> wrote: > Is there a simple way in a program to see if a file system uses case sensitive > names (like traditional Unix) or case irrelevant (like plain old HFS+)? touch test; touch TEST; ls -1rt two files = case sensitive. You can also look in Disk Utility. -- Dinner will be ready when the smoke alarm goes off.
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-02-16 09:18 -0500 |
| Message-ID | <iM6dnXDMkZ1ZVZ3OnZ2dnUVZ_rSdnZ2d@giganews.com> |
| In reply to | #56578 |
On 2014.02.16, 01:05 , Lewis wrote:
> In message <chine.bleu-1E20C5.19082615022014@news.eternal-september.org>
> Siri Cruz <chine.bleu@yahoo.com> wrote:
>> Is there a simple way in a program to see if a file system uses case sensitive
>> names (like traditional Unix) or case irrelevant (like plain old HFS+)?
>
> touch test; touch TEST; ls -1rt
>
> two files = case sensitive.
>
> You can also look in Disk Utility.
My first reaction was to open Disk Utility which shows (under the 'info'
button) "Mac OS Extended (Journaled, Encrypted)" and I'm not sure at all
that is indicative of case insensitivity. Is it?
--
Privacy has become an essential personal chore that most
people are not trained to perform.
- Jaron Lanier, Scientific American, 2013.11.
[toc] | [prev] | [next] | [standalone]
| From | Michael Vilain <vilain@NOspamcop.net> |
|---|---|
| Date | 2014-02-15 23:28 -0800 |
| Message-ID | <vilain-A30470.23285415022014@news.individual.net> |
| In reply to | #56572 |
In article <chine.bleu-1E20C5.19082615022014@news.eternal-september.org>, Siri Cruz <chine.bleu@yahoo.com> wrote: > Is there a simple way in a program to see if a file system uses case > sensitive > names (like traditional Unix) or case irrelevant (like plain old HFS+)? I've recently discovered this thing on the web. It's called Google and it's replaced my CRC Handbook, my Sun Tech manuals, and my old DEC manuals. I asked this question at the Google prompt and this came back. http://apple.stackexchange.com/questions/71357/how-to-check-if-my-hd-is-c ase-sensitive-or-not -- DeeDee, don't press that button! DeeDee! NO! Dee... [I filter all Goggle Groups posts, so any reply may be automatically ignored]
[toc] | [prev] | [next] | [standalone]
| From | Siri Cruz <chine.bleu@yahoo.com> |
|---|---|
| Date | 2014-02-16 04:24 -0800 |
| Message-ID | <chine.bleu-F99049.04243216022014@news.eternal-september.org> |
| In reply to | #56581 |
In article <vilain-A30470.23285415022014@news.individual.net>, Michael Vilain <vilain@NOspamcop.net> wrote: > I've recently discovered this thing on the web. It's called Google and Odd but since Google doesn't actually have a human interpretting the query, all it takes is slightly off query and it's useless, no matter how many hours you spend on it. I remember once spending a day trying to find out how to record screen audio with screen video, only reading I would need a mic out to sound in amplifier/cable. Tried again and now there's a software bit to do that. -- :-<> Siri Seal of Disavowal #000-001. Disavowed. Denied. Deleted. 'I desire mercy, not sacrifice.'
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-02-16 09:17 -0500 |
| Message-ID | <iM6dnXHMkZ3jVZ3OnZ2dnUVZ_rSdnZ2d@giganews.com> |
| In reply to | #56581 |
On 2014.02.16, 02:28 , Michael Vilain wrote:
> In article
> <chine.bleu-1E20C5.19082615022014@news.eternal-september.org>,
> Siri Cruz <chine.bleu@yahoo.com> wrote:
>
>> Is there a simple way in a program to see if a file system uses case
>> sensitive
>> names (like traditional Unix) or case irrelevant (like plain old HFS+)?
>
> I've recently discovered this thing on the web. It's called Google
Snide reply aside I'm glad when these questions come along and there is
a spectrum of replies on how to find the answers. Sometimes I learn
something. And interesting that it's split between "probers" (find the
info from the system) and "testers" (contrive a test that shows
behaviour and thus settings).
Indeed my first reaction was to open Disk Utility which shows (under the
'info' button) "Mac OS Extended (Journaled, Encrypted)" and I'm not sure
at all that is indicative of case insensitivity (I'll refer to Lewis in
his reply).
As to brevity I guess Lewis' method seems best.
--
Those who have reduced our privacy, whether they are state
or commercial actors, prefer that we do not reduce theirs.
- Jaron Lanier, Scientific American, 2013.11.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <kaz@kylheku.com> |
|---|---|
| Date | 2014-03-02 18:19 +0000 |
| Message-ID | <20140302101428.693@kylheku.com> |
| In reply to | #56581 |
On 2014-02-16, Michael Vilain <vilain@NOspamcop.net> wrote: > In article ><chine.bleu-1E20C5.19082615022014@news.eternal-september.org>, > Siri Cruz <chine.bleu@yahoo.com> wrote: > >> Is there a simple way in a program to see if a file system uses case >> sensitive >> names (like traditional Unix) or case irrelevant (like plain old HFS+)? > > I've recently discovered this thing on the web. It's called Google and > it's replaced my CRC Handbook, my Sun Tech manuals, and my old DEC > manuals. I asked this question at the Google prompt and this came back. You and Siri Cruz are not so different, you know, haha: Siri Cruz: User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) Michael Vilain: User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) Someone who uses an actual newsreader and connects to an actual NNTP server probably doesn't benefit from "learn how to use a search engine" type advice.
[toc] | [prev] | [next] | [standalone]
| From | Michael Vilain <vilain@NOspamcop.net> |
|---|---|
| Date | 2014-03-02 12:37 -0800 |
| Message-ID | <vilain-1429B1.12374502032014@news.individual.net> |
| In reply to | #57405 |
In article <20140302101428.693@kylheku.com>, Kaz Kylheku <kaz@kylheku.com> wrote: > On 2014-02-16, Michael Vilain <vilain@NOspamcop.net> wrote: > > In article > ><chine.bleu-1E20C5.19082615022014@news.eternal-september.org>, > > Siri Cruz <chine.bleu@yahoo.com> wrote: > > > >> Is there a simple way in a program to see if a file system uses case > >> sensitive > >> names (like traditional Unix) or case irrelevant (like plain old HFS+)? > > > > I've recently discovered this thing on the web. It's called Google and > > it's replaced my CRC Handbook, my Sun Tech manuals, and my old DEC > > manuals. I asked this question at the Google prompt and this came back. > > You and Siri Cruz are not so different, you know, haha: > > Siri Cruz: > User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) > > Michael Vilain: > User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) > > Someone who uses an actual newsreader and connects to an actual NNTP server > probably doesn't benefit from "learn how to use a search engine" type advice. au contraire. Google has replaced most of my bookshelf of O'Reilly books. While I'm sure it wouldn't have replaced the gray wall of DEC manuals, it does answer all the "how do I" questions I've asked it about Linux. And now that I've asked it MacOS questions, it's come up with some answers. But it misses more times than on Linux. -- DeeDee, don't press that button! DeeDee! NO! Dee... [I filter all Goggle Groups posts, so any reply may be automatically ignored]
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-03-02 20:23 -0500 |
| Message-ID | <5313d98d$0$32622$c3e8da3$dbd57e7@news.astraweb.com> |
| In reply to | #57416 |
On 14-03-02 15:37, Michael Vilain wrote: > au contraire. Google has replaced most of my bookshelf of O'Reilly > books. While I'm sure it wouldn't have replaced the gray wall of DEC > manuals The Grey Wall was replaced at 5.5-2 in early 1990s. First to CDs and currently available somewhere on the HP web site where it is preserved (hopefully) for the no-longer-developped VMS OS.
[toc] | [prev] | [next] | [standalone]
Page 1 of 2 [1] 2 Next page →
Back to top | Article view | comp.sys.mac.system
csiph-web