y, June 03, 2000 10:58 AM
Subject: Re: [Cooker] So, if 7.1 is now final...
> Chmouel Boudjnah wrote:
> >
> > John Cavan <[EMAIL PROTECTED]> writes:
> >
> > > 2. When you create a normal user at install time it also creates a
group
> > > that matches the u
John Cavan <[EMAIL PROTECTED]> writes:
> Anyways, enough said. I don't plan to modify the RPM, it's a maintenance
> headache to keep doing that everytime an upgraded RPM comes down the
> pipe, so I'll deal with the behaviour.
a modified version of adduser in
/usr/local/sbin/ ?
it's what most a
John Grange wrote:
> it is actualy very usefull because say you want user A to be able to access
> files in a dirrectory but you do not want the people in the users group to be
> able to access them, then you just set the gid of the dir to that users gid ,
> it's not stupid it's very usefull and i
Geoffrey Lee wrote:
>
> patch the code yourself if youd on't like how it works :ppp
No offense, but that's a crummy response to user feedback, a habit on
this list I might add. Yes, I can patch the code, but that's not
relevant to the discussion, nor can I do that during install. In actual
fact,
John Cavan wrote:
> Chmouel Boudjnah wrote:
> >
> > John Cavan <[EMAIL PROTECTED]> writes:
> >
> > > 2. When you create a normal user at install time it also creates a group
> > > that matches the user. That means I get john:john instead of john:users
> >
> > this is the standard way on our distr
RH/Debian/Slack
>
> Fair enough, note I said Unix :o). I don't think they always did it that
> way, it appears to be a logic change in useradd. I find it odd that it
> was done that way, normally you shouldn't have to tell something to
> explicitly take system defaults... it should be the other w
John Cavan <[EMAIL PROTECTED]> writes:
> Anyways, I personally, and that's just personally, think it's the wrong
> way to do it, but as I said, it's not a big problem. I'll just have to
> remember to add -D or -n to useradd when creating users. :o)
yep 8)
--
MandrakeSoft Inchtt
Chmouel Boudjnah wrote:
>
> John Cavan <[EMAIL PROTECTED]> writes:
>
> > It may be the standard way on Mandrake, but it's not a standard way for
> > Unix... it is unexpected behaviour and you do have a group labled
>
> it's the standard way on a Linux System see on a RH/Debian/Slack
Fair enoug
John Cavan <[EMAIL PROTECTED]> writes:
> It may be the standard way on Mandrake, but it's not a standard way for
> Unix... it is unexpected behaviour and you do have a group labled
it's the standard way on a Linux System see on a RH/Debian/Slack
--
MandrakeSoft Inchttp://www.ma
Chmouel Boudjnah wrote:
>
> John Cavan <[EMAIL PROTECTED]> writes:
>
> > 2. When you create a normal user at install time it also creates a group
> > that matches the user. That means I get john:john instead of john:users
>
> this is the standard way on our distribution, a user has a group and
John Cavan <[EMAIL PROTECTED]> writes:
> 2. When you create a normal user at install time it also creates a group
> that matches the user. That means I get john:john instead of john:users
this is the standard way on our distribution, a user has a group and
after the administrator manage to set h
Is the code freeze off? It would be good if we could start packaging up
some of the newer versions of the software that is out there.
By the way, I tried the new installation (FTP'd, through a firewall on
an ADSL connection) and I'd like to say that it went great. Two minor
problems that I saw:
12 matches
Mail list logo
