From: Joost Kremers <joostkremers@yahoo.com>
Subject: Re: Why I have two same executable files for running emacs?
Date: 21 Dec 2006 10:29:48 GMT [thread overview]
Message-ID: <slrneokofc.35c.joostkremers@j.kremers4.news.arnhem.chello.nl> (raw)
In-Reply-To: emdckj$s24$1@news.yaako.com
Ronald wrote:
> Why I have two same executable files for running emacs?
>
> -rwxr-xr-t 2 root root 8365030 2006-12-21 15:08 emacs
> -rwxr-xr-t 2 root root 8365030 2006-12-21 15:08 emacs-22.0.92
>
> Do you?
yup. they're not two files, though, they're one and the same file that has
two different names referring to it. you can do this by creating a hard
link.
if you do `ls -il emacs*' in the directory where emacs is residing, you'll
see that they have the same inode number, which makes it the same file:
joost@teuctli:/usr/local/bin # ls -il emacs*
3071276 -rwxr-xr-t 2 root root 7703867 2006-12-11 03:21 emacs*
3071276 -rwxr-xr-t 2 root root 7703867 2006-12-11 03:21 emacs-22.0.91*
3071271 -rwxr-xr-x 1 root root 30475 2006-12-11 03:21 emacsclient*
--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
prev parent reply other threads:[~2006-12-21 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 7:20 Why I have two same executable files for running emacs? Ronald
2006-12-21 10:29 ` Joost Kremers [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrneokofc.35c.joostkremers@j.kremers4.news.arnhem.chello.nl \
--to=joostkremers@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is 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).