Daniel wrote:
> Same here. Really, I'm surprised that anyone is using the 'users'
> group at all these days, especially on OpenBSD. If all users are in
> the same group, group permissions are no different from world
> permissions.
I believe the real problem here is that you're allowing users on
Is there someone who can give me OpenBSD Administration course online
(practice using ssh) ? That will cover BSDP Objectives.
Thanks
Defining a bunch of functions just to update the term title is
ridiculous.
--- src/etc/ksh.kshrc.orig Fri Oct 29 21:40:51 2010
+++ src/etc/ksh.kshrc Fri Oct 29 21:51:48 2010
@@ -45,16 +45,7 @@
HOSTNAME=${HOSTNAME:-`uname -n`}
HOST=${HOSTNAME%%.*}
- PROMPT="$USER:!$PS
Criador da Cosmitica Vegetal Junte-se ` Yves Rocher. Lider da Cosmetica
Vegetal e ganhe um Rendimento Extra e Poupe nos Cosmeticos Mediante as
vendas(compras) efectuadas sco imediatamente retiradas pela conselheira
as comissues a que tem direito(30%).
Quais as VANTAGENS em se tornar Conselheira YV
On Fri, Oct 29, 2010 at 11:25 AM, Henning Brauer
wrote:
> * Philip Guenther [2010-10-29 19:48]:
>
>> Group-per-user setups solve this by letting people safely have a umask
>> of 007 or 002. When they do work in a directory whose group is a
>> secondary group, the resulting files are (and stay) w
* Philip Guenther [2010-10-29 19:48]:
> Back in my pure sysadmin days, I found that when users all (or almost
> all) share a default group like "users", then it isn't easy enough for
> normal users to leverage other groups for shared access to files and
> directories. Because the default group is
$360Pistola
de pintar HVLP Premiun CCapacidad 600
cc / Presion Maxima 3 Bar / Uso Profesional
/ Incluye Manometro y Kit de Desarme y Limpieza $
On Fri, Oct 29, 2010 at 9:40 AM, Theo de Raadt
wrote:
>> On Fri, Oct 29, 2010 at 02:29:50PM +0200, Ingo Schwarze wrote:
...
>> This topic came up last year as well, including the same useradd/adduser
>> confusion:
>> http://kerneltrap.org/mailarchive/openbsd-tech/2009/5/8/5660874
>>
>> "useradd re
On Fri, Oct 29, 2010 at 10:52:46AM +0200, Tobias Ulmer wrote:
> The installer defaults to creating accounts with group "users", adduser
> creates a group for each user. Sync the two.
> Takes effect only if /etc/addusers.conf is regenerated, ie. new
> installations.
This should lead to at least the
On Sun, Oct 24, 2010 at 11:14 AM, Andres Perera wrote:
> On Sat, Oct 23, 2010 at 10:02 AM, Damien Bergamini
> wrote:
>> I finally found some time to finish RT3090 support in ral(4).
>> If you have such a device, please test the driver in -current
>> and report success/failure directly to me.
>
>
> On Fri, Oct 29, 2010 at 02:29:50PM +0200, Ingo Schwarze wrote:
> > Hi Tobias,
> >
> > i'm not sure as i don't use tools like adduser(8) and useradd(8),
> > and i doubt they are widely used among developers anyway. I think
> > they are around mostly because some people are used to them from
> >
On 27 October 2010 21:37, Christiano F. Haesbaert
wrote:
> The 0x8000 bit in a question isn't a cache flush indication.
> It's the QU bit, indicating the question accepts a unicast response,
although
> it's the same bit in the class field, they have completely different
meanings
> when in a RR or
Olympus 560WP USD 165 Olympus 6010 USD
275,60 Panasonic TS10 USD
360 Panasonic TS2 USD 430
Sony TX5 USD 430
On Fri, 29 Oct 2010 15:02:05 +0200
Tobias Ulmer wrote:
> "useradd really does that? A new group for every user? I think that
> is stupid behaviour."
>
> So, I stand by my patch,
> Tobias
Personally I prefer the unique group by default behaviour, but I also
don't have a problem with double che
On Fri, Oct 29, 2010 at 02:29:50PM +0200, Ingo Schwarze wrote:
> Hi Tobias,
>
> i'm not sure as i don't use tools like adduser(8) and useradd(8),
> and i doubt they are widely used among developers anyway. I think
> they are around mostly because some people are used to them from
> other systems.
Hi Tobias,
i'm not sure as i don't use tools like adduser(8) and useradd(8),
and i doubt they are widely used among developers anyway. I think
they are around mostly because some people are used to them from
other systems.
So, gratuitously changing the defaults is not necessarily a wise move.
As
The installer defaults to creating accounts with group "users", adduser
creates a group for each user. Sync the two.
Takes effect only if /etc/addusers.conf is regenerated, ie. new
installations.
Index: adduser.perl
===
RCS file: /srv
It was pointed out that as long as we're breaking anything that's using
KERN_PROC, struct kinfo_proc, or kvm_get(procs|argv|envv), there really
isn't any reason to not change those APIs to the new forms. I.e.,
kvm_getprocs() gains another arguments (elemsize) and the struct
kinfo_proc that it
18 matches
Mail list logo
