afterboot.8 hasn't been changed to reflect the fact that a user can
be created during installation and you have no other option but to
login as root on first boot.
comments/ok?
-mark
Index: afterboot.8
===
RCS file: /cvs/src/share
Hi Mark,
Mark Lumsden wrote on Sat, Jan 22, 2011 at 11:35:20AM +:
> afterboot.8 hasn't been changed to reflect the fact that a user can
> be created during installation and you have no other option but to
> login as root on first boot.
You have a point, but the text seems easier to follow
I agree with what you have done. Thanks.
Although I've included the information about the user created via the
installation method being added to the wheel group. But then again I would even
go as far as informing the user during the installation that the users they are
about to create are mem
Shampoo,Acondicionador,Gel de bano, en botellitas personalizadas o sachets
diferentes modelos , Jabones en varios
gramajes y presentaciones , Cofias para bano , Kits Dental ,de Afeitar , Vanity
Pack, Panuelitos tissue , Fajitas para desinfectado ,
Costureritos,Boligrafos promocionales, Etiquetas
can anyone test this diff? your feedback will be most welcome
On Wed, Sep 08, 2010 at 11:51:11AM -0300, Gleydson Soares wrote:
> hi,
>
> - ipv6 support for tftp client.
>
> based on an old itojun's diff.
Index: tftpsubs.c
===
RCS fi
Hello all.
Just got that:
1. ksh updates it's "real" argv when "set --" is used.
2. /etc/netstart does the following (excerpts):
while :; do
if [ "$cmd2" ]; then
set -- $cmd2
# ...
else
read af name mask bcaddr ext1 ext2 || break
NetBSD (where our usb stack came from) has a /dev/usb device node.
this node exists primarily for reading usb events. however, we
do not create /dev/usb, which means we have no way to get the usb
events. usb events are device/driver attach/detachments. we have
hotplug(4) to get this info.
I don
On Sun, Jan 23, 2011 at 05:03:18AM +, Jacob Meuser wrote:
> NetBSD (where our usb stack came from) has a /dev/usb device node.
> this node exists primarily for reading usb events. however, we
> do not create /dev/usb, which means we have no way to get the usb
> events. usb events are device/d
