[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3 SysAdmin questions
Tuvik Beker wrote:
>
> Hi,
>
> Three questions of varying complexity -
>
> 1. I have the following problem: I want to share home directories in a
> network with hosts of different architectures, that were recently put
> together. Currently we have SGI and Linux, others may be added. The
> problem is to map the UID/GID spaces correctly. On a pure linux net,
> this could theoretically be accomplished by giving the 'map_daemon'
> option in /etc/exports to use ugidd for that mapping. However I think
> this is a security risk, and anyhow it doesn't apply to the mixed system
> in question. I think the right thing to do is maintain a central user
> database, with all the relevant parameters, and have each host access it
> to create its own /etc/passwd file, with unified UID/GID's.
> The problem (apart from how to do it properly...) is the silly group
> convention used by RedHat, which is unlike anything standard, POSIX or
> other. Do you think it would matter much if I abandon it and adopt a
> more conventional GID allocation? Does anyone have better ideas of how
> to accomplish the task? Bare in mind that each host already has its set
> of users, and some users have separate accounts on different hosts. The
> aim is to cause minimal disturbance while doing the merge.
I'd recommand you to move all users and user groups (NOT
"system groups") to a unified NIS database.
It might be a little hassle at first but after that things should
go smoothly.
> 2. Any recommecdations as to a good backup tool for linux? Of course,
> one can simply write backup scripts to be run with cron, but I guess
> there should exist smarter applications, giving easy controll over
> multiple backups to tapes and disks etc.
Never used any, but Debian has afbackup. You might also want to
use GNU tar with incremental backups (it comes with scripts to do
that).
> 3. There were threads in the past dealing with HD->HD duplication in the
> case of identical disks, and several solutions were suggested. What
> about moving an entire system to a larger disk? What is least likely to
> cause problems - tar|tar or dd (or cp -... ).
As far as I remember we converged on using "cp -a".
Cheers,
--Amos
--Amos Shapira | "Of course Australia was marked for
133 Shlomo Ben-Yosef st. | glory, for its people had been
chosen
Jerusalem 93 805 | by the finest judges in England."
ISRAEL amos@dsi.co.il | -- Anonymous
Follow-Ups:
References: