Excellent.
Time to read about udev.
Will do my homework, try a few tests, and will get back with results and,
possibly, more questions :-D
Thank you, everybody for your valuable help (and time).
Best regards,
João
On Mon, Aug 20, 2018 at 2:54 AM Reco wrote:
> Hi.
>
> On Mon, Aug 20,
Hi.
On Mon, Aug 20, 2018 at 12:51:24AM -0300, Joao Roscoe wrote:
> Hmmm...
>
> If I create a NIS group (with a high ID), called serial_ports, dhould I
> just, as root, chgrp /dev/ttyS0 so that it's group is serial_ports ?
You could, and it may even work, but it would be temporary.
To
Hmmm...
If I create a NIS group (with a high ID), called serial_ports, dhould I
just, as root, chgrp /dev/ttyS0 so that it's group is serial_ports ?
João
On Sun, Aug 19, 2018 at 12:47 PM Michael Stone wrote:
> On Fri, Aug 17, 2018 at 02:48:56PM -0300, Joao Roscoe wrote:
> >Right, that's best
On Fri, Aug 17, 2018 at 02:48:56PM -0300, Joao Roscoe wrote:
Right, that's best practice.
But, what if I need to include a user who is defined in NIS in lp or ttyS0
group? Would going into /etc/group in *every* machine be unavoidable?
That's one option. Another would be to create new
Joao Roscoe wrote:
> But, what if I need to include a user who is defined in NIS in lp or ttyS0
> group? Would going into /etc/group in *every* machine be unavoidable?
your print server will be the only one to consider for lp group for example
or just do something with ansible or puppet or
Right, that's best practice.
But, what if I need to include a user who is defined in NIS in lp or ttyS0
group? Would going into /etc/group in *every* machine be unavoidable?
João
On Fri, Aug 17, 2018 at 1:42 PM Greg Wooledge wrote:
> On Fri, Aug 17, 2018 at 01:27:32PM -0300, Joao Roscoe
On Fri, Aug 17, 2018 at 01:27:32PM -0300, Joao Roscoe wrote:
> However, it will not solve the problem on how to centrally manage system
> resources access across distros.
You don't manage OS-specific (or "distro"-specific if you prefer that term)
group IDs in a network database. Those are
You are right, I forgot to state that yes, I do use NFS to share files -
great tip, this GID / UID remapping thing - thanks a lot.
However, it will not solve the problem on how to centrally manage system
resources access across distros.
Joao
On Fri, Aug 17, 2018 at 10:49 AM wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Aug 17, 2018 at 10:36:38AM -0300, Joao Roscoe wrote:
> I have redhat and debian machines in the same network. Users and groups are
> controlled via NIS
>
> I have realized that redhat and debian have different groups definitions
> for system
On Fri, Aug 17, 2018 at 10:36:38AM -0300, Joao Roscoe wrote:
What would be the best way to manage this (other than managing groups on
machines themselves, individually)? Different NIS domains for different
distros? Is there any tutorial on managing multiple domains on the same NIS
server, out
I have redhat and debian machines in the same network. Users and groups are
controlled via NIS
I have realized that redhat and debian have different groups definitions
for system resources access control. For instance, redhat machines have
group lp with GID 4, while debian states that lp group is
11 matches
Mail list logo
