From: Zachary Kline <zkline@speedpost.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Progress reports
Date: Wed, 1 Dec 2010 10:12:31 -0800 (PST) [thread overview]
Message-ID: <alpine.LNX.2.00.1012011011180.4388@blackhawk.localdomain> (raw)
In-Reply-To: <20101201181037.GA3166@romuald.net.eu.org>
On Wed, 1 Dec 2010, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, Dec 01, 2010 at 06:30:26AM -0500, Chuck Hallenbeck wrote:
>> Is the
>> default for ln to make hard links or soft?
>
> I believe ln makes hard links by default.
>
>> Would either style work in
>> this setup?
>
> I don't see why not, but I could be wrong.
Technically, symlinks can cross filesystem boundaries, whereas hard links
cannot. Beyond that, for this particular situation I think they're pretty
much equivalent.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
pj
` Chuck Hallenbeck
` Gregory Nowak
` Zachary Kline [this message]
-- strict thread matches above, loose matches on Subject: below --
pj
pj
` Chuck Hallenbeck
` Frost
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=alpine.LNX.2.00.1012011011180.4388@blackhawk.localdomain \
--to=zkline@speedpost.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).