the zpool-features(5)
manual page.
Unfortunately, I do not have a manual page for zpool-features.
Does this mean that I can not update from 9 to 10? This amd64 has zfs
root.
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.f
On Tue, 18 Sep 2012, Fabian Keil wrote:
Darrel wrote:
OpenBSD Packet Filter seems to have broken between 9.0 and 9.1, as it did
from 8.2 to 9.0. I built stable/9 and it was not fixed. Since I like to
run Packet Filter, I ran these commands:
# cd /usr
# svn co svn://svn.freebsd.org/base
directories incorrect or some other combination
of make calls required there?
Thanks,
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Wed, 19 Sep 2012, Darrel wrote:
Does this mean that I can not update from 9 to 10?
No.
So I ran mergemaster and upgraded zpool from '28' to 'zpool-features'
and installed the new bootcode to ada0 and ada1. The next step
needs to be right before I can reboot
Welcome to the wonderful world that no one knows how UPDATING works anymore...
-Garrett
Thank you.
Assholes [ pardon me] that they tend to be, with many exceptions- the
steps would have been included in an OpenBSD update that required portions
of the tree to be recompiled.
Darrel
snip
Actually, I am becoming suspicious that FreeBSD does not maintain a OpenBSD
Packet Firewall that survives upgrades. Perhaps I should just take all of
the Packet Firewall stuff out of my kernel and learn to use ipfw2.
Darrel
On the subject of OpenBSD Packet Firewall
OpenBSD 4.5
snip
Actually, I am becoming suspicious that FreeBSD does not maintain a OpenBSD
Packet Firewall that survives upgrades. Perhaps I should just take all of
the Packet Firewall stuff out of my kernel and learn to use ipfw2.
Darrel
On the subject of OpenBSD Packet Firewall
OpenBSD 4.5
ue_request'
*** [kernel.debug] Error code 1
Stop in /usr/obj/usr/src/sys/D.
*** [buildkernel] Error code 1
Stop in /usr/src.
*** [buildkernel] Error code 1
Stop in /usr/src.
(132) @ 23:41:19>
Darrel
___
freebsd-current@freebsd.org mailing
Error code 1
Stop in /usr/obj/usr/src/sys/D.
*** [buildkernel] Error code 1
Stop in /usr/src.
*** [buildkernel] Error code 1
Stop in /usr/src.
(132) @ 23:41:19>
That is probably result of building atapicam together with option ATA_CAM,
that is at least useles
zone is currently equal to 0. How might I tweak it
just enough to fix this?
Also, I have been disregarding the prefetch notice about zfs. I have
not seen any adverse results.
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freeb
estroy commands availed nothing- perhaps there
were subsequent or subcommands to run there.
Is there a good method to reduce the encrypted swap, perhaps? I might
like to have a total of 3g encrypted swap plus 3g zvol swap.
Darrel
___
freebsd-c
ize from each disk of the mirror and also 94M precisely
from zfs swap?
Thank you,
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
;> No ORIGIN in /var/db/pkg/postgresql-server-9.2.1/+CONTENTS
Terminated
(48) @ 12:58:40>
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Mon, 15 Oct 2012, Darrel wrote:
Would it be best to deinstall portmaster for now? Portmaster typically
updates itself, but this might be a special case.
I got it:
# cd /usr/port/ports-mgmt/portmaster
# make deinstall
# make rmconfig
# make reinstall
- select pkgngpatch > O
r should interoperate with pkgng pretty smoothly.
Certainly it should be using pkgng's local.sqlite database to pull out
package contents rather than trying to parse +CONTENTS files.
Thanks, Matthew!
Darrel
___
freebsd-current@freebsd.org mailin
Hello,
Is it possible to regenerate the package database or somehow start over?
I am seeing errors like these:
pkg_info: Don't use the pkg_ tools if you are using pkgng
pkg_info: the package info for package 'ca_root_nss-3.14' is
grep pkgconf' then the output is fine.
Oh, I just noticed that portmaster-3.14 *and* portmaster-3.14_7 exist in
/var/db/pkg. That can not be alright.
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
Is it possible to regenerate the package database or somehow
start over? I am seeing errors like these:
pkg_info: Don't use the pkg_ tools if you are using pkgng
pkg_info: the package info for package 'ca_root_nss-3.14' is
corrupt
If you still have the binari
ss that my database is messed up.
Thanks for your reply,
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Somehow my installation has both
The moment you run pkg2ng you lose any right to use pkg_* tools -
this is what the first warning is telling you.
I have a patch awaiting approval which makes the error more clear.
Yes, the existing man 8 pkg doe
On Sat, 3 Nov 2012, Garrett Cooper wrote:
On Sat, Nov 3, 2012 at 6:15 PM, Darrel wrote:
...
Yes, the existing man 8 pkg does not seem to match all of the facts.
What you probably ran into is the common chicken and egg problem where
if pkgng is upgraded ports, it blows up when it
ine in /etc/make.conf
exists 'WITH_PKGNG=yes' and I ran pkg2ng on the 15th of October.
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Hello,
Since fbsd10 has moved by default to pkgng, would it make sense to remove
all references to pkg_info from /etc/periodic/daily/490.status-pkg-changes
?
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
lude /boot/menu-commands.4th
Anyone seen this before?
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
that seems to be the correct solution.
I have a basically identical ruleset on fbsd91 and no error message.
Any ideas?
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
ply raise dyn_max.
It's a writeable sysctl. I set it to 65535 on my systems in
/etc/sysctl.conf with no apparent ill effects.
This is just an internal server, so at first will try an increment:
net.inet.ip.fw.dyn_max=16384
Thank you,
Darrel
_
a new group.
I ran installworld and am stuck here:
===> /usr.sbin/fifolog/fifolog_writer (install)
This is amd64 and has been stuck like this for 9 hours. Any
suggestions?
Thank you,
Darrel
___
freebsd-current@freebsd.org mailing list
http://li
hether or not I cleared /usr/obj
before the build- could be due to brain damage of the system
administrator.
Darrel
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to &qu
28 matches
Mail list logo
