On Fri, 10 May 2013 04:18:42 +0200, Benjamin Adams
wrote:
On 05/09/2013 10:06 PM, Jeremy Chadwick wrote:
On Thu, May 09, 2013 at 09:47:27PM -0400, Benjamin Adams wrote:
On 05/09/2013 08:53 PM, Shane Ambler wrote:
On 09/05/2013 22:48, Benjamin Adams wrote:
Hello zfs question about memory.
On May 10, 2013, at 1:08 PM, "Ronald Klop" wrote:
> On Fri, 10 May 2013 04:18:42 +0200, Benjamin Adams
> wrote:
>
>> On 05/09/2013 10:06 PM, Jeremy Chadwick wrote:
>>> On Thu, May 09, 2013 at 09:47:27PM -0400, Benjamin Adams wrote:
On 05/09/2013 08:53 PM, Shane Ambler wrote:
> On 09/
On 05/09/13 22:42, Dewayne Geraghty wrote:
An ugly workaround to complete the jail closure, when relying on jail.conf, is
to:
jail -r $JAILNAME
umount /$LOCATION_OF_JAILS/$JAILNAME/dev || true
The only problem with devfs I'm aware of is it not catching the right
ruleset when starting in the r
Hey All,
I'm looking to generate a FreeBSD 9-stable (and maybe 10-current) ISO that
has certain packages pre-installed. I'd like to create my own installation
media that will have certain things installed, like a web management UI
that I'm actively working on. It'd be like what pfSense does.
I di
On Fri, May 10, 2013 at 9:55 AM, Shawn Webb wrote:
> Hey All,
>
> I'm looking to generate a FreeBSD 9-stable (and maybe 10-current) ISO that
> has certain packages pre-installed. I'd like to create my own installation
> media that will have certain things installed, like a web management UI
> tha
As Rick pointed out, the package split script will get the packages on the
media. You also need to modify the install process to actually install the
default packages. You might want to look at the bsdinstall setup and add a
script there to load the packages. Another approach is to create a scri
This patch works on one of my 9.1 systems in addition to my CURRENT
system.
On Thu, 9 May 2013, Jim Ohlstein wrote:
On 05/09/13 12:04, Konstantin Belousov wrote:
On Thu, May 09, 2013 at 11:42:28AM -0400, Jim Ohlstein wrote:
On 05/09/13 10:30, Konstantin Belousov wrote:
On Thu, May 09, 2
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154
It has been suggested to me (by a committer) that I should raise the
issue of this PR here on these lists, because the problem described
within the PR remains a real problem, and despite my having proposed
something that seems to be a perfectl
Hi!
> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154
>
> It has been suggested to me (by a committer) that I should raise the
> issue of this PR here on these lists, because the problem described
> within the PR remains a real problem, and despite my having proposed
> something that seems
In message <20130510213610.gg8...@home.opsec.eu>, you wrote:
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154
>>
>> It has been suggested to me (by a committer) that I should raise the
>> issue of this PR here on these lists, because the problem described
>> within the PR remains a real
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE
FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE
FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE
FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE
FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE
FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE
FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-10 23:38:53 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:38:53 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE
FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-05-10 23:38:23 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:38:23 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE
FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
Hi stable list,
Now ipfw_nat's rules must be write directly in firewall_nat_flags. This is
messy to describe many rules. firewall_nat_rules will be treat smartly.
To enable firewall_nat_rules,apply following patch to /etc/rc.firewall
--- /etc/rc.firewall.org2013-05-11 08:23:13.0 +
19 matches
Mail list logo