From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Permission Policy
Date: Fri, 28 Dec 2007 14:26:18 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.0.9999.0712281423530.9217@nqv-yncgbc> (raw)
In-Reply-To: <99F5377B-360E-4024-BCEB-FE528A60DB3F@science.uva.nl>
On Fri, 28 Dec 2007, Hans van der Meer wrote:
> I ran into trouble with "luatools --generate"
> which does not seem to work with "sudo luatools --generate"
> The seem applies to texmfstart and friends.
What error message do you get?
> Why this manco? I want to keep my system as safe as possible
> especially regarding applications and stuff that takes a lot of time
> installing (like the texlive system).
> Therefore I have this in an administrator account (root:wheel).
> Cannot ConTeXt cope with such a scheme? All it has to do is honor
> sudo, apparently.
sudo luatools --generate works here (Ubuntu Linux). AFAIU, luatools
--generate only reads the relevant files from $TEXMF and writes details to
$TEXMFCACHE. If all directories in $TEXMF are readable by normal user
(should be) and $TEXMFCACHE is writable by normal user (should be), then
you do not even need a sudo.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2007-12-28 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 16:09 Hans van der Meer
2007-12-28 19:20 ` Hans Hagen
2007-12-28 19:26 ` Aditya Mahajan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.0.9999.0712281423530.9217@nqv-yncgbc \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/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).