On Tue, 2005-09-27 at 07:52 +, randhir phagura wrote:
I will have to learn bash scripting to sufficient degree to be able to
become 'root' in the middle of an automating install script, at the 'make
install' stage for each package. As of now, I don't even know if it is
possible at all.
On 9/24/05, Lennon Cook [EMAIL PROTECTED] wrote:
Actually it's so I can tell easily which ones I've installed already;
and so that 'for i in /etc/gconf/schemas/* ; do gconftool-2
--install-schema-file=$i ; done' doesn't reinstall things
unnecesarily.
Instead of the for command above use the
On 9/24/05, randhir phagura [EMAIL PROTECTED] wrote:
Why is it required that building of a package be done as an unprevilged
user? I saw this indication in the Book too (Now as root user issue the
following command...) but never bothered to investigate. I tend to automate
my install of most
Hi Lennon,
Hi David,
Thanks for your answers. I am obliged.
Regards,
Randhir Phagura
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
On 9/24/05, randhir phagura [EMAIL PROTECTED] wrote:
Why is it required that building of a package be done as an unprevilged
user?
In straight BLFS (without hints), it strictly isn't - it's mostly a
matter of you don't *need* to be root to build it, and it is therefore
good practice not to be.
In straight BLFS (without hints), it strictly isn't - it's
mostly a matter of you don't *need* to be root to build it,
and it is therefore good practice not to be.
Exactly. It's basically added security - by building a package as
non-root you elliminate the risk of dodgy / malicious config
Since I use the package user hint, when I build a package that
installs GConf schemas I pass --disable-schemas-install to ./configure
Could you enlighten me as to why this is necessary?
It is because gconftool-2, as well as its configuration file and schema
database belong to the gconf user
On 9/23/05, David Ciecierski [EMAIL PROTECTED] wrote:
The same applies to scrollkeeper.
There's an easy way around it with scrollkeeper: chmod u+s `which
scrollkeeper-update` . If you make it SUID the user that installed
it, it will work fine.
This isn't much an option with gconftool-2,
