Hello,
I have tried out the autoinstall functionality and it worked great. The
install log turning up as an email was a very nice touch.
One thing that I was thinking about when looking at the examples in
autoinstall(8) was that while System hostname is set in the response
file example, it is
On 26 April 2014 06:21, Patrik Lundin patrik.lundin@gmail.com wrote:
Hello,
I have tried out the autoinstall functionality and it worked great. The
install log turning up as an email was a very nice touch.
One thing that I was thinking about when looking at the examples in
On Sat, Apr 26, 2014 at 07:21:28AM -0400, Kenneth Westerback wrote:
Assuming you mean dhclient.conf and not dhcpd.conf, the hostname of
the system is not currently set by dhclient even if it is supplied.
The install process does cause dhclient to send the configured
hostname to the dhcpd
On 26 April 2014 07:45, Patrik Lundin patrik.lundin@gmail.com wrote:
On Sat, Apr 26, 2014 at 07:21:28AM -0400, Kenneth Westerback wrote:
Assuming you mean dhclient.conf and not dhcpd.conf, the hostname of
the system is not currently set by dhclient even if it is supplied.
The install
On Sat, Apr 26, 2014 at 07:54:44AM -0400, Kenneth Westerback wrote:
On 26 April 2014 07:45, Patrik Lundin patrik.lundin@gmail.com wrote:
On Sat, Apr 26, 2014 at 07:21:28AM -0400, Kenneth Westerback wrote:
Assuming you mean dhclient.conf and not dhcpd.conf, the hostname of
the system
The patch removes the unreasonable use of blank lines.
If its automatically generated then the patch is useless.
About the choices of the software, yes
$HOME/.xinitrc is used IF it exists.
Shouldnt then be the right choice to let the user choose its apps?
IMHO fvwm and xterm are quite arbitrary.
Hi, I found another simple way to do that,
add the limit to /etc/login.conf (nginx, php_fpm),
use /etc/rc.d/daemon script to start nginx,php_fpm
nginx:\
:maxproc=0:\
:tc=daemon:
php_fpm:\
:maxproc=0:\
:tc=daemon:
because the parent is runas root, and root can
On Sat, Apr 26, 2014 at 14:20, Héctor Luis Gimbatti wrote:
The patch removes the unreasonable use of blank lines.
If its automatically generated then the patch is useless.
About the choices of the software, yes
$HOME/.xinitrc is used IF it exists.
Shouldnt then be the right choice to let
Hi tech,
our IGMP packets don't contain router alert options.
According rfc 2236 (Internet Group Management Protocol, Version 2)
packets without this option have to be ignored. Some layer 3 switches
are blocking our igmp packets because of that.
The following patch is based on a FreeBSD patch
It's actually impossible to use a USB keyboard to enter ddb(8) on most
of the G3/G4 that come with such keyboard since they have a bluetooth
HID device that attaches as the console keyboard.
I assume this is also the case on various x86 Apple laptops, but I don't
have any hardware to test.
Diff
On Sat, Apr 26, 2014 at 05:57:30PM +0200, Martin Pieuchot wrote:
It's actually impossible to use a USB keyboard to enter ddb(8) on most
of the G3/G4 that come with such keyboard since they have a bluetooth
HID device that attaches as the console keyboard.
I assume this is also the case on
Date: Sat, 26 Apr 2014 17:57:30 +0200
From: Martin Pieuchot mpieuc...@nolizard.org
It's actually impossible to use a USB keyboard to enter ddb(8) on most
of the G3/G4 that come with such keyboard since they have a bluetooth
HID device that attaches as the console keyboard.
I assume this
Hello,
is there a reason why file system fragments are called blocks instead of
frags in comments in sys/ufs/ffs/fs.h sometime?
The patch below treats only occurrence.
Index: src/sys/ufs/ffs/fs.h
===
RCS file:
On Sat, 26 Apr 2014, David Vasek wrote:
Hello,
is there a reason why file system fragments are called blocks instead of
frags in comments in sys/ufs/ffs/fs.h sometime?
The patch below treats only occurrence.
- only one occurence.
Sorry.
Regards,
David
On Sat, Apr 26, 2014 at 05:36:45PM +0200, Florian Riehm wrote:
our IGMP packets don't contain router alert options.
According rfc 2236 (Internet Group Management Protocol, Version 2)
packets without this option have to be ignored. Some layer 3 switches
are blocking our igmp packets because of
On 04/26/14 20:35, Alexander Bluhm wrote:
/*
* To avoid byte-swapping the same value over and over again.
*/
FreeBSD has code matching this comment. In OpenBSD the code is
gone and so should the comment. Of course that is unrelated to
this diff.
I have
Hi,
On Tue, Apr 22, 2014 at 01:29:03AM +, Ben Cornett wrote:
The following corrects the termination condition on the write
loop in copyfile.
From inspection, i say the patch is clearly correct.
I was unable to find any condition where the bug might actually
hit: The file descriptor `to'
I've been doing some testing of fuse and discovered a small bug where it only
allows file names up to 254 characters due to not taking the NULL terminator
into consideration when allocating structures.
--
Helg xx...@msn.com
Index: dict.c
18 matches
Mail list logo
