rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: bk@analytikerna.se (Bengt KLEBERG)
To: rc@hawkwind.utcs.toronto.edu
Subject: Subject: Re: 8.5 on x
Date: Sat, 5 Jun 1993 05:41:35 -0400	[thread overview]
Message-ID: <9306050941.AA22655@analytikerna.se> (raw)

> From rc-owner@hawkwind.utcs.toronto.edu Fri Jun  4 14:24:13 1993
> To: steve@gec-epl.co.uk (Steve_Kilbane)
> Cc: rc@hawkwind.utcs.toronto.edu
> Subject: Re: 8.5 on x 
> Date: 	Fri, 4 Jun 1993 08:19:23 -0400
> From: John Robert LoVerso <loverso@osf.org>
> Content-Length: 151
> 
> > but you still don't get the union directories)
> 
> I would expect that something like Sun's translucent file system would be able
> to supply this.
> 
> John
> 
Sun will not continue with TLFS. Sun Sweden mentioned this at a SweSUG
meeting over a year ago. The replay was that one should not base any
new projects on NeWS or TLFS. Can't say I'm sorry. Unix is getting
very big as it is anyway.

Bengt


                 reply	other threads:[~1993-06-05  9:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9306050941.AA22655@analytikerna.se \
    --to=bk@analytikerna.se \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).