Re: Spontaneous reboots on Intel i5 and FreeBSD 9.0

[Bas Smeelen]

On 01/25/2013 10:29 AM, Marin Atanasov Nikolov wrote:

Hello again :)

Here's my update on these spontaneous reboots after less than a week since
I've updated to stable/9.

First two days the system was running fine with no reboots happening, so I
though that this update actually fixed it, but I was wrong.


Not really a solution but you can take a look at sysutils/zfs-stats



The reboots are still happening and still no clear evidence of the root
cause. What I did so far:

* Ran disks tests -- looking good
* Ran memtest -- looking good
* Replaced power cables
* Ran UPS tests -- looking good
* Checked for any bad capacitors -- none found
* Removed all ZFS snapshots

There is also one more machine connected to the same UPS, so if it was a
UPS issue I'd expect that the other one reboots too, but that's not the
case.

Now that I've excluded the hardware part of this problem I started looking
again into the software side, and this time in particular -- ZFS.

I'm running FreeBSD 9.1-STABLE #1 r245686 on a Intel i5 with 8Gb of memory.

A quick look at top(1) showed lots of memory usage by ARC and my available
free memory dropping fast. I've made a screenshot, which you can see on the
link below:

* http://users.unix-heaven.org/~dnaeon/top-zfs-arc.jpg

So I went to the FreeBSD Wiki and started reading the ZFS Tuning Guide [1],
but honestly at the end I was not sure which parameters I need to
increase/decrease and to what values.

Here's some info about my current parameters.

 % sysctl vm.kmem_size_max
 vm.kmem_size_max: 329853485875

 % sysctl vm.kmem_size
 vm.kmem_size: 8279539712

 % sysctl vfs.zfs.arc_max
 vfs.zfs.arc_max: 7205797888

 % sysctl kern.maxvnodes
 kern.maxvnodes: 206227

There's one script at the ZFSTuningGuide which calculates kernel memory
utilization, and for me these values are listed below:

 TEXT=22402749, 21.3649 MB
 DATA=4896264192, 4669.44 MB
 TOTAL=4918666941, 4690.81 MB

While looking for ZFS tuning I've also stumbled upon this thread in the
FreeBSD Forums [2], where the OP describes a similar behaviour to what I am
already experiencing, so I'm quite worried now that the reason for these
crashes is ZFS.

Before jumping into any change to the kernel parameters (vm.kmem_size,
vm.kmem_max_size, kern.maxvnodes, vfs.zfs.arc_max) I'd like to hear any
feedback from people that have already done such optimizations on their ZFS
systems.

Could you please share what are the optimal values for these parameters on
a system with 8Gb of memory? Is there a way to calculate these values or is
it just a "test-and-see-which-fits-better" way of doing this?

Thanks and regards,
Marin

[1]: https://wiki.freebsd.org/ZFSTuningGuide
[2]: http://forums.freebsd.org/showthread.php?t=9143


On Sun, Jan 20, 2013 at 3:44 PM, Marin Atanasov Nikolov wrote:




On Sat, Jan 19, 2013 at 10:19 PM, John  wrote:


At 03:00am I can see that periodic(8) runs, but I don't see what could

have

taken so much of the free memory. I'm also running this system on ZFS and
have daily rotating ZFS snapshots created - currently the number of ZFS
snapshots are > 1000, and not sure if that could be causing this. Here's

a

list of the periodic(8) daily scripts that run at 03:00am time.

% ls -1 /etc/periodic/daily
800.scrub-zfs

% ls -1 /usr/local/etc/periodic/daily
402.zfSnap
403.zfSnap_delete

On a couple of my zfs machines, I've found running a scrub along with
other
high file system users to be a problem.  I therefore run scrub from cron
and
schedule it so it doesn't overlap with periodic.

I also found on a machine with an i3 and 4G ram that overlapping scrubs
and
snapshot destroy would cause the machine to grind to the point of being
non-responsive. This was not a problem when the machine was new, but
became one
as the pool got larger (dedup is off and the pool is at 45% capacity).

I use my own zfs management script and it prevents snapshot destroys from
overlapping scrubs, and with a lockfile it prevents a new destroy from
being
initiated when an old one is still running.

zfSnap has its -S switch to prevent actions during a scrub which you
should
use if you haven't already.



Hi John,

Thanks for the hints. It was a long time since I've setup zfSnap and I've
just checked the configuration and I am using the "-s -S" flags, so there
should be no overlapping.

Meanwhile I've updated to 9.1-RELEASE, but then I hit an issue when trying
to reboot the system (which appears to be discussed a lot in a separate
thread).

Then I've updated to stable/9, so at the least the reboot issue is now
solved. Since I've to stable/9 I'm monitoring the system's memory usage and
so far it's been pretty stable, so I'll keep an eye of an update to
stable/9 has actually fixed this strange issue.

Thanks again,
Marin



Since making these changes, a machine that would have to be rebooted
several
times a week has now been up 61 days.

John Theus
TheUs Group




--
Marin Atanasov Nikolov

dnaeon AT gmail DOT co

Re: FreeBSD wiki offline for a bit

[Bas Smeelen]

On 01/08/2013 10:00 AM, Trond Endrestøl wrote:

On Tue, 8 Jan 2013 09:39+0100, Bas Smeelen wrote:


On 01/08/2013 09:32 AM, Alexander Yerenkow wrote:


2013/1/8 Bas Smeelen mailto:b.smee...@ose.nl>>

 On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:

 http://wiki.freebsd.org/ZFSTuningGuide

 Seems not working :)


 Works here!


Hm, could you look at this:
ping wiki.freebsd.org <http://wiki.freebsd.org>
PING wfe0.ysv.freebsd.org <http://wfe0.ysv.freebsd.org> (8.8.178.110)

That's strange.
When I go to http://wiki.freebsd.org/ZFSTuningGuide it works.

But when I go to wiki.freebsd.org I get the same Error 503

It may seem browser cache is playing us some tricks.

Opera 12.12 on Windows (yikes) gave me the wiki front page, but as
soon as I started clicking on links I haven't touched before, I was
presented the 503 page:

Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 931044748
Varnish cache server

I launched links on a 9.1-S and directed the browser to
http://wiki.freebsd.org/ and was presented with:

Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 931044247
Varnish cache server


$ ping wiki.freebsd.org
PING wfe0.ysv.freebsd.org (8.8.178.110) 56(84) bytes of data.
64 bytes from wfe0.ysv.FreeBSD.org (8.8.178.110): icmp_req=1 ttl=54 time=160
ms



<http://wiki.freebsd.org/ZFSTuningGuide>



Error 503 Service Unavailable

Service Unavailable
Guru Meditation:

XID: 931032464

Varnish cache server


Here it is all working again!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD wiki offline for a bit

[Bas Smeelen]

On 01/08/2013 09:37 AM, Erich Dollansky wrote:

Hi,

On Tue, 8 Jan 2013 10:08:33 +0200
Alexander Yerenkow  wrote:


http://wiki.freebsd.org/ZFSTuningGuide

Error 503 Service Unavailable

Service Unavailable

Guru Meditation:

XID: 931036950

Varnish cache server

is all I get.

Erich


http://wiki.freebsd.org/ThwackAFAQ
http://wiki.freebsd.org/ 
same Error 503 as above

But http://wiki.freebsd.org/ZFSTuningGuide works in two different browsers, 
refreshed the page several times and have no proxy in between.




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD wiki offline for a bit

[Bas Smeelen]

On 01/08/2013 09:32 AM, Alexander Yerenkow wrote:



2013/1/8 Bas Smeelen mailto:b.smee...@ose.nl>>

On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:

http://wiki.freebsd.org/ZFSTuningGuide

Seems not working :)


Works here!


Hm, could you look at this:
ping wiki.freebsd.org <http://wiki.freebsd.org>
PING wfe0.ysv.freebsd.org <http://wfe0.ysv.freebsd.org> (8.8.178.110)


That's strange.
When I go to http://wiki.freebsd.org/ZFSTuningGuide it works.

But when I go to wiki.freebsd.org I get the same Error 503

$ ping wiki.freebsd.org
PING wfe0.ysv.freebsd.org (8.8.178.110) 56(84) bytes of data.
64 bytes from wfe0.ysv.FreeBSD.org (8.8.178.110): icmp_req=1 ttl=54 time=160 ms



<http://wiki.freebsd.org/ZFSTuningGuide>




Error 503 Service Unavailable

Service Unavailable
Guru Meditation:

XID: 931032464

Varnish cache server



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD wiki offline for a bit

[Bas Smeelen]

On 01/08/2013 09:08 AM, Alexander Yerenkow wrote:

http://wiki.freebsd.org/ZFSTuningGuide

Seems not working :)



Works here!


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Will we get a RELEASE-9.1 for Christmas?

[Bas Smeelen]

On 12/21/12 00:40, Matthew Seaman wrote:

On 13/12/2012 08:29, Matthew Seaman wrote:

(On 'pkg check -Ba' producing 'shared library not found' errors for some
packages)


Unfortunately it seems to be a fairly common effect in some large
projects. Other packages showing the same symptoms:

thunderbird (yeah -- that one was predictable...)
openjdk6
virtualbox-ose

... and that's just out of what's installed on my desktop: by no means
comprehensive.  As far as I can tell from a quick check, openjdk6
doesn't rely on setting LD_LIBRARY_PATH in the environment.

I've raised issue #403 in pkgng Github.

I've just finished committing fixes for this problem to the master and
release-1.0 branches in Github.  If anyone is feeling enthusiastic and
would like to try pulling those sources and confirming that their
favourite packages no longer generate scads of nasty errors when
re-analysing shlib dependencies, I'd be grateful.

Cheers,

Matthew

PS.  If you're running pkg-1.0.3, I recommend you pull down the
release-1.0 branch for these tests.  While you could upgrade to 1.1.a1
from master, that involves various local.sqlite DB schema changes which
will be tedious to unwind should you want to revert to the released
version.



I would like to.
But just getting used to svn and other new things since simple csup and 
friends.

How do I pull it?
I have pkg-1.0.3_1 on a machine building packages for my laptop right now.



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: portupgrade problem after upgrading to 9.1-(PRE)RELEASE

[Bas Smeelen]

On 12/20/12 00:21, CeDeROM wrote:

On Wed, Dec 19, 2012 at 11:57 PM, Jakub Lach  wrote:

Prerelease was using -STABLE packages.

Are -stable packages in sync with port tree? Are -release frozen
version of -stable when a release is made?


Magic of enviroment variables...
http://www.freebsd.org/doc/handbook/packages-using.html

Yea, new tool PKG in 9.1 at last :-) :-)


I use poudriere to build packages for 9.1-RELEASE i386 and make them 
available on

http://dd.ose.nl/91i386-default

This is for my own convenience because my laptop takes about 20 hours 
just to rebuild xfce4, firefox and thunderbird.


You can use them if you like, the packages can be viewed with a web browser.

Just set PACKAGESITE to the URL and add/update with pkg
It might be unavailable at times because the machine is running CURRENT



http://www.freebsd.org/doc/handbook/pkgng-intro.html

Thanks Jakub! :-)



had all blocked with ipfw but now it is open :)

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: repo.txz missong on packages-9-stable for pkg

[Bas Smeelen]

On 12/20/12 14:34, CeDeROM wrote:

Thank you Matthew! Good luck with your works! :-)



I will see if I can built them with poudriere for 9.1 amd64 also
But it can take a while

Do you have a list, you can obtain it with portmaster --list-origins

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: portupgrade problem after upgrading to 9.1-(PRE)RELEASE

[Bas Smeelen]

On 12/20/12 13:40, CeDeROM wrote:

On Thu, Dec 20, 2012 at 1:31 PM, Bas Smeelen  wrote:

I use poudriere to build packages for 9.1-RELEASE i386 and make them
available on
http://dd.ose.nl/91i386-default

Thank you Bas :-) I am using AMD64 :-) Anyway I was wondering if
freebsd-stable repository works as a binary store for a current port
tree (or its up to date snapshot).

It would be great to have debian's "apt-get" functionality in FreeBSD :-)


I think pkg is as good as apt-get or even better

The main difference in FreeBSD is that you have the base system which 
you can binary update/upgrade with freebsd-update or via source 
preferably with svn.


Then you have the ports or third party applications which you can binary 
upgrade with the old way pkg_tools (replace tools with add, delete etc) 
or the new generation pkg tools. They can also be kept up to date via 
source with the make tools or you can use portmaster, portupgrade and 
friends for keeping them up to date via source and/or binary packages.


I also was wondering why on RC portupgrade was working fine, while on
a release it failed. I know there are no packages yet and no release,
but it should fall back into the repository it was using for RC,
shouldn't it? :-)


I can't tell you.
I don't know what the current pkg repositories for the new generation 
pkg tools (or the older pkg_tools) are, thus I build them for myself 
with poudriere.




Best regards :-)
Tomek




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: portupgrade problem after upgrading to 9.1-(PRE)RELEASE

[Bas Smeelen]

On 12/20/12 00:21, CeDeROM wrote:

On Wed, Dec 19, 2012 at 11:57 PM, Jakub Lach  wrote:

Prerelease was using -STABLE packages.

Are -stable packages in sync with port tree? Are -release frozen
version of -stable when a release is made?


Magic of enviroment variables...
http://www.freebsd.org/doc/handbook/packages-using.html

Yea, new tool PKG in 9.1 at last :-) :-)


I use poudriere to build packages for 9.1-RELEASE i386 and make them 
available on

http://dd.ose.nl/91i386-default

This is for my own convenience because my laptop takes about 20 hours 
just to rebuild xfce4, firefox and thunderbird.


You can use them if you like, the packages can be viewed with a web browser.

Just set PACKAGESITE to the URL and add/update with pkg
It might be unavailable at times because the machine is running CURRENT



http://www.freebsd.org/doc/handbook/pkgng-intro.html

Thanks Jakub! :-)




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: MFC: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd)) (fwd)

[Bas Smeelen]

On 12/18/12 18:44, Chris H wrote:

On 12/18/12 16:18, Robert Watson wrote:

Dear all:

Just an FYI that the new distributed audit daemon has been MFC'd to
9
20121201:
  With the addition of auditdistd(8), a new auditdistd user is now
  depended on during installworld.  "mergemaster -p" can be used
to add
  the user prior to installworld, as documented in the handbook.

should be "prior to installkernel" then also instead of "prior to
installworld"

Greetings,
  FWIW, I just performed an build(world||kernel) && install(world||kernel) 
yesterday.
I used the following:

cd /usr/src

make buildworld
make buildkernel KERNCONF=
make install KERNCONF=


Hi
I guess you did make installkernel instead of just make install 
KERNCONF= ?


I did a day ago on a 9.1-RC3:

freebsd-update
make buildkernel
make installkernel

Then got prompted that the auditdistd user did not exist so I had to add 
it prior to installing the kernel.

But this was when going from 9.1-RC3 to 9.1-RELEASE
So I copied the bits from a CURRENT machine where everything went fine 
using the standard buildworld, buildkernel, installkernel, mergemaster 
-p, installworld, mergemaster procedure


So that was not the usual way, but just using freebsd-update and 
installing a custom kernel.


On CURRENT it went al well.

Never mind and thanks.



reboot to single user...

mount -u /
mount -a

cd /usr/src
mergemaster -p
blah,blah,blah...
make installworld
mergemaster
reboot

All of the auditdistd bits were merged into my system, and all is well.
Isn't that the way Updating lists the "correct" order?


Yes it is. I did an unusual combination of binary update and then 
building and installing a custom kernel.



Anyway, that's how I understood it, and just wanted to report that it
all worked as expected/anticipated.

HTH, and best wishes.

--Chris




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: MFC: Distributed audit daemon committed (was: svn commit: r243752 - in head: etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd (fwd)) (fwd)

[Bas Smeelen]

On 12/18/12 16:18, Robert Watson wrote:


Dear all:

Just an FYI that the new distributed audit daemon has been MFC'd to 
9-STABLE.


Thanks.



As noted in UPDATING, you will need to run "mergemaster -p" before 
using installkernel or installworld targets in order to add the new 
"auditdistd" system user.  This should be part of the regular update 
cycle anyway, but after the experience of adding auditdistd in 
10-CURRENT, we've discovered that many people are skipping that step 
in the update cycle, so I figured it best to point out here.


(Technically, only installworld requires the user, but the user-check 
guards in the system Makefiles are enforced for both targets.)


Maybe /usr/src/UPDATING should be updated?
The end of /usr/src/UPDATING mentiones mergemaster -p after the 
installtion of the new kernel and rebooting to single user mode instead 
of before. This is on 9.1-RELEASE and also in CURRENT.


At least the entry in /usr/src/UPDATING on CURRENT for this change

20121201:
With the addition of auditdistd(8), a new auditdistd user is now
depended on during installworld.  "mergemaster -p" can be used 
to add

the user prior to installworld, as documented in the handbook.

should be "prior to installkernel" then also instead of "prior to 
installworld"





More details on the daemon below.

Robert N M Watson
Computer Laboratory
University of Cambridge

-- Forwarded message --
Date: Sat, 1 Dec 2012 15:15:11 + (GMT)
From: Robert Watson 
To: curr...@freebsd.org
Cc: secur...@freebsd.org
Subject: Distributed audit daemon committed (was: svn commit: r243752 
- in head:

 etc etc/defaults etc/mail etc/mtree etc/rc.d share/man/man4 usr.sbin
usr.sbin/auditdistd (fwd))


Dear all:

I've now committed the build glue required to install the recently 
merged Audit Distribution Daemon (auditdistd) contributed by the Pawel 
Dawidek, and sponsored by the FreeBSD Foundation.  This allows 
individual hosts generating audit trails to submit trails to a central 
audit server for review and safe keeping.  Part of the goal is to 
ensure that a host submitting trail data can't later modify the 
trails.  Pawel uses a variety of useful security- and 
resilience-related features such as TLS, Capsicum, etc, in 
auditdistd.  As the recent security incident in the FreeBSD.org 
cluster illustrated, having reliable and detailed audit trails makes a 
big difference in forensic work, and hopefully this will allow the 
FreeBSD Project (and our users) to do that better in the future.


Robert N M Watson
Computer Laboratory
University of Cambridge

-- Forwarded message --
Date: Sat, 1 Dec 2012 15:11:46 + (UTC)
From: Robert Watson 
To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
svn-src-h...@freebsd.org
Subject: svn commit: r243752 - in head: etc etc/defaults etc/mail 
etc/mtree

etc/rc.d share/man/man4 usr.sbin usr.sbin/auditdistd

Author: rwatson
Date: Sat Dec  1 15:11:46 2012
New Revision: 243752
URL: http://svnweb.freebsd.org/changeset/base/243752

Log:
  Merge a number of changes required to hook up OpenBSM 1.2-alpha2's
  auditdistd (distributed audit daemon) to the build:

  - Manual cross references
  - Makefile for auditdistd
  - rc.d script, rc.conf entrie
  - New group and user for auditdistd; associated aliases, etc.

  The audit trail distribution daemon provides reliable,
  cryptographically protected (and sandboxed) delivery of audit tails
  from live clients to audit server hosts in order to both allow
  centralised analysis, and improve resilience in the event of client
  compromises: clients are not permitted to change trail contents
  after submission.

  Submitted by:pjd
  Sponsored by:The FreeBSD Foundation (auditdistd)

Added:
  head/etc/rc.d/auditdistd   (contents, props changed)
  head/usr.sbin/auditdistd/
  head/usr.sbin/auditdistd/Makefile   (contents, props changed)
Modified:
  head/etc/defaults/rc.conf
  head/etc/ftpusers
  head/etc/mail/aliases
  head/etc/master.passwd
  head/etc/mtree/BSD.var.dist
  head/etc/rc.d/Makefile
  head/share/man/man4/audit.4
  head/usr.sbin/Makefile

Modified: head/etc/defaults/rc.conf
== 


--- head/etc/defaults/rc.confSat Dec  1 13:46:37 2012 (r243751)
+++ head/etc/defaults/rc.confSat Dec  1 15:11:46 2012 (r243752)
@@ -590,6 +590,9 @@ sendmail_rebuild_aliases="NO"# Run newa
 auditd_enable="NO"# Run the audit daemon.
 auditd_program="/usr/sbin/auditd"# Path to the audit daemon.
 auditd_flags=""# Which options to pass to the audit daemon.
+auditdistd_enable="NO"# Run the audit daemon.
+auditdistd_program="/usr/sbin/auditdistd"# Path to the auditdistd 
daemon.

+auditdistd_flags=""# Which options to pass to the auditdistd daemon.
 cron_enable="YES"# Run the periodic job daemon.
 cron_program="/usr/sbin/cron"# Which cron executable to run (if 
enabled).

 cron_

Re: Will we get a RELEASE-9.1 for Christmas?

[Bas Smeelen]

On 12/10/2012 06:34 PM, Brett Glass wrote:

At 03:41 PM 12/9/2012, Adrian Chadd wrote:
  

I'll amend my "stuff that will help" list:

* Donate to the freebsd foundation, along with opening discussions to
them about how your organisation uses / relies upon freebsd;


I just had a little conversation with my employer about donating to the 
FreeBSD Foundation and sent the three *most important* people in the 
organization a follow up mail on it with the link of course. Let's see what 
happens. Maybe they will take it out of our Christmas gift :)


Thanks!

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update mergemaster options

[Bas Smeelen]

On 12/11/2012 12:58 AM, Ask Bjørn Hansen wrote:

Hi,

On an 8.2 box, I run

freebsd-update -r 8.3-RELEASE upgrade

I am getting hundreds of files with "conflicts" like:

<<< current version
# $FreeBSD: src/etc/auth.conf,v 1.6.32.1.4.1 2010/06/14 02:09:06 kensmith Exp $
===
# $FreeBSD: src/etc/auth.conf,v 1.6.32.1.8.1 2012/03/03 06:15:13 kensmith Exp $


I don't know why this happens. Upgrading a couple of boxes from 8.1-RELEASE 
to 8.3-RELEASE did not give me these conflicts.
As far as I know freebsd-update does not use mergemaster.rc, just 
freebsd-update.conf


It might be the case that you have upgraded from source before on this 
machine that causes this situation?



8.3-RELEASE

... which is just tremendously unhelpful. I'm using the default freebsd-update 
configuration. Per an old mail from the archives I made sure I have 
/etc/mergemaster.rc setup as below, but it doesn't seem to make a difference.

Any ideas?  In the past I've just given up on using freebsd-update and gone 
back to manually compiling and installing world, but for this box I'd really 
like not to.


Ask

$ cat /etc/mergemaster.rc
# Automatically install files that do not exist
AUTO_INSTALL='yes'
# Automatically upgrade files that have not been edited
AUTO_UPGRADE='yes'
# Ignore files that I don't want changed
IGNORE_FILES='/etc/motd'
# Do not display changes that only affect whitespace
DIFF_FLAG="'.Bub'"
# Ignore CVS id lines to stop replacing files where only that line has changed
DIFF_OPTIONS='-I$FreeBSD:.*[$]'




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 12/07/12 21:36, Jakub Lach wrote:

While it's very, very minute detail, I think that in #officesuite
there should be "Apache OpenOffice" not "Apache Open Office"
as they were very careful even bureaucratic [*] if I reckon correctly,
when choosing new branding.

[*] They have "branding initiative guidelines" and held vote-
https://blogs.apache.org/OOo/entry/openoffice_org_is_now_apache


Hi Jakub
You can file a patch for it

Index: en_US.ISO8859-1/books/faq/book.xml
===
--- en_US.ISO8859-1/books/faq/book.xml(revision 40304)
+++ en_US.ISO8859-1/books/faq/book.xml(working copy)
@@ -3523,7 +3523,7 @@

 
   The open-source -  url="http://www.openoffice.org";>Apache Open 
Office
+  url="http://www.openoffice.org";>Apache 
OpenOffice

 and http://www.libreoffice.org";>LibreOffice
 office suites work natively on &os;.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/27/2012 08:44 AM, Andrea Venturoli wrote:

On 11/26/12 23:09, Bas Smeelen wrote:


Probable addition
8.8 I get a lot of 'spurious interrupts detected' messages on a modified
i386 build kernel and my computer does not work right. What did I do wrong?

You have a single processor computer, build your own customized kernel
and disabled
options SMP (multiprocessor).
Probably you also disabled the line below,
device  apic# I/O APIC

This is code for the advanced programmable interrupt controller which
also controls interrupts for your attached devices, being ethernet cards
and others.
Do not disable this device.


While I don't know about apic, there used to be "KEEP THIS!!!" comments in 
GENERIC's conf file.
I guess this would be more on the spot than a FAQ you'd read *after* 
removing this.


Just my 2c.

 bye
av.


You're probably right. It must have been before 6.3-RELEASE, where there are 
no KEEP THIS comments in GENERIC.

Though in NOTES it says "Mandatory".

It is a very stupid user error on my side, which I stumbled upon quite a 
time ago and maybe not even FAQ worthy then.



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 9.1-RELEASE

[Bas Smeelen]

On 11/26/12 23:48, Bas Smeelen wrote:

On 11/26/12 23:36, Rick Miller wrote:

On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen  wrote:

Hi
Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
Who has a no non-release policy, management?

It's not just management,


Just to sum it up

Make sure you document with second and third party approval!
What you did and How you did it

There is no reason to document for Why you did it, though this can be 
beneficial.


With this, it comes to that the FreeBSD development and distributing 
model is very well, let's say highly transparent, it is up to you as a 
systems administrator or even developer (they are more out in the clear 
though) to account for (document and get this approved) and be 
transparant for all the actions that have been commited, to the FDA for 
instance in the industries (Pharma, Biomed, etc, I work in). I guess 
fbi, cia, nsa or other 'higher' governmental institutions don't have to 
account for this, because they are much smarter anyway.


I apologise for the dutch grammar.

Cheers



checked, they don't have a clue, that's what we're here for


  but also software engineers,


checked, mutually accepted, they know what you're up to, and keep them 
clear, be honest

and even better, they know what they're up to, but try to blame you for
just keep them as very close 'friends'
it helps when you are able to 'clean up their messes sometimes'


  architects


is like in between management and software engineers, dangerous maybe


, and
business folks.


management or otherwise


   When a company runs a service whose production SLA is
100%, many tend to be less forgiving.


100% that's a dare!
For them it may be 100%, for me I am at 98% then, at best 99,636% :)
There is a lot of playfield unknown


   There's a lot riding on running
a development branch in production, even if it is a "Release
Candidate".



Agree 100% :)
RELEASE is better than RC or even BETA for sakes ;)




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 9.1-RELEASE

[Bas Smeelen]

On 11/26/12 23:36, Rick Miller wrote:

On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen  wrote:

Hi
Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
Who has a no non-release policy, management?

It's not just management,


checked, they don't have a clue, that's what we're here for


  but also software engineers,


checked, mutually accepted, they know what you're up to, and keep them 
clear, be honest

and even better, they know what they're up to, but try to blame you for
just keep them as very close 'friends'
it helps when you are able to 'clean up their messes sometimes'


  architects


is like in between management and software engineers, dangerous maybe


, and
business folks.


management or otherwise


   When a company runs a service whose production SLA is
100%, many tend to be less forgiving.


100% that's a dare!
For them it may be 100%, for me I am at 98% then, at best 99,636% :)
There is a lot of playfield unknown


   There's a lot riding on running
a development branch in production, even if it is a "Release
Candidate".



Agree 100% :)
RELEASE is better than RC or even BETA for sakes ;)




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 9.1-RELEASE

[Bas Smeelen]

On 11/26/12 22:42, mat...@hush.ai wrote:

Hi. With the recent delays from the security incident and the three SAs out of 
the way, what now are we waiting for? I think we should just get rid of the 
release schedule on FreeBSD.org if we aren't even going to be close to the set 
dates.
RC3 has been really stable for me, but we have a no non-release policy on 
production machines.
We're so far behind compared to 
http://www.freebsd.org/releases/9.1R/schedule.html (which has already been 
updated multiple times because of delay after delay)


Hi
Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
Who has a no non-release policy, management?

9.1-RC3 is working for me very well also



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/20/12 20:25, Eitan Adler wrote:

On 19 November 2012 15:07, Aldis Berjoza  wrote:


19.11.2012, 22:04, "Andrea Venturoli" :

On 11/19/12 18:44, Eitan Adler wrote:


  Hey all,

  The FAQ for FreeBSD needs a significant amount of updating and
  changing.  The first step in that process is to figure out what needs
  to be changed.

  If you can a take a moment and thoroughly review just one
  question and add your comments and concerns it
  would be immensely helpful.

  http://wiki.freebsd.org/ThwackAFAQ

...

I've migrated the comments on the mailing list to the wiki and will
working on fixing them shortly.  Content patches are appreciated but
not required. Ideally every row on the wiki will be either green or
red.

Fixing the content is a very long term project.




Probable addition
8.8 I get a lot of 'spurious interrupts detected' messages on a modified 
i386 build kernel and my computer does not work right. What did I do wrong?


You have a single processor computer, build your own customized kernel 
and disabled

options SMP (multiprocessor).
Probably you also disabled the line below,
device  apic# I/O APIC

This is code for the advanced programmable interrupt controller which 
also controls interrupts for your attached devices, being ethernet cards 
and others.

Do not disable this device.




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/26/12 22:27, Schaich Alonso wrote:

On 2012-11-26 (Monday) 22:15:27 Miroslav Lachman wrote:

[...]

So a kernel alone has 12MB, with debug symbols 62MB (12+50).
And all *.symbols files can be deleted (if more space on /boot is needed)
I don't know how it should be mentioned in FAQ.

Miroslav Lachman

Specifying WITHOUT_KERNEL_SYMBOLS=YES in src.conf to not generate debug
information IMO is a cleaner and more preferable solution then deleting the
files, and it also reduces the amount of storage space needed for /usr/obj (or
whereever else the kernel's built) by about 1GB on STABLE-9.


Thanks for this (man 5 src.conf)
I guess this way is preferred instead of customizing the kernel 
configuration file?
From the manpage I understand the symbol files will not get installed, 
but will still be build.
To decrease building time, one should modify the kernel configuration 
file anyway?




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/26/12 22:20, Bas Smeelen wrote:

On 11/26/12 22:02, Doug Hardie wrote:

On 26 November 2012, at 12:53, Bas Smeelen wrote:


On 11/26/12 21:27, Bas Smeelen wrote:

On 11/26/12 17:25, Jakub Lach wrote:

Thanks!

Regarding FAQ, some info about journalling should  be added to
"Chapter 9 Disks, File Systems, and Boot Loaders", especially now,
when SU+J is default.

Please also add:
SU+J does not work (yet) with dump on a live filesystem i.e. use 
snapshot.
If you want to use snapshot (dump -L) then disable the soft updates 
journal for that filesystem
It would be helpful to include information on how to do that during 
install (still trying to figure that out myself), and using the 
recover CD for when you forget to do it during install.


Right now, when installing a new system it's easiest to reboot to 
single user mode after the install and tunefs -j disable 'the 
filesystems' to disable journaling of soft updates.


When changing the root ( / ) filesystem in single user mode, reboot 
immediately after disabling the soft updates journal otherwise it will 
still be enabled. No need for a rescue cd/usb here.




If you want to accomplish this during the install, choose shell at the 
disk partitioning part and add slices and/or partitions with gpart and 
then newfs them with the appropriate options, then mount them on /mnt 
and the appropriate places beneath and continue the install by 
quitting the shell.


There are some nice entries on http://wiki.freebsd.org/RootOnZFS
Just substitute the ZFS stuff with the easier gpart and then newfs -U 
etc... then make sure the filesystems are mounted under /mnt and 
continue the installation.
I hope that I will not confuse you too much with the proposed solution 
i.e. use these resources as a guideline. Else see reboot to single 
user mode after install above and tunefs




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/26/12 22:15, Miroslav Lachman wrote:

Bas Smeelen wrote:

On 11/26/12 16:57, Jakub Lach wrote:

[...]

Thanks Miroslav Lachman for the reply with the correct sizes for GENERIC
kernels.

Change FAQ 8.3 Why is my kernel so big?

Nowadays kernels are compiled in /debug mode by default/. Kernels built
in debug mode contain many symbols that are used for debugging, thus
greatly increasing the size of the kernel. Note that there will be
little or no performance decrease from running a debug kernel, and it is
useful in case of a system panic.

However


I think that debug symbols are in another files (*.symbols)

FreeBSD 8.3-RELEASE amd64 GENERIC

> ls -lh /boot/kernel/kernel*
-r-xr-xr-x  1 root  wheel   12M May  8  2012 /boot/kernel/kernel
-r-xr-xr-x  1 root  wheel   50M May  8  2012 /boot/kernel/kernel.symbols

So a kernel alone has 12MB, with debug symbols 62MB (12+50).
And all *.symbols files can be deleted (if more space on /boot is needed)
I don't know how it should be mentioned in FAQ.


You are right.
From the FAQ I understand with 'kernel so big' the contents of the 
/boot/kernel directory is being referred to as a whole?
Thus disabling (commenting) makeoptions DEBUG=-g (which is default the 
last couple of releases, since 7?) and then rebuilding and installing 
the kernel you get rid if them 'the right way'


So FAQ 8.3 is still right just changing that nowadays it's default for 
GENERIC to be build with the debug symbols.






___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/26/12 22:02, Doug Hardie wrote:

On 26 November 2012, at 12:53, Bas Smeelen wrote:


On 11/26/12 21:27, Bas Smeelen wrote:

On 11/26/12 17:25, Jakub Lach wrote:

Thanks!

Regarding FAQ, some info about journalling should  be added to
"Chapter 9 Disks, File Systems, and Boot Loaders", especially now,
when SU+J is default.

Please also add:
SU+J does not work (yet) with dump on a live filesystem i.e. use snapshot.
If you want to use snapshot (dump -L) then disable the soft updates journal for 
that filesystem

It would be helpful to include information on how to do that during install 
(still trying to figure that out myself), and using the recover CD for when you 
forget to do it during install.


Right now, when installing a new system it's easiest to reboot to single 
user mode after the install and tunefs -j disable 'the filesystems' to 
disable journaling of soft updates.


If you want to accomplish this during the install, choose shell at the 
disk partitioning part and add slices and/or partitions with gpart and 
then newfs them with the appropriate options, then mount them on /mnt 
and the appropriate places beneath and continue the install by quitting 
the shell.


There are some nice entries on http://wiki.freebsd.org/RootOnZFS
Just substitute the ZFS stuff with the easier gpart and then newfs -U 
etc... then make sure the filesystems are mounted under /mnt and 
continue the installation.
I hope that I will not confuse you too much with the proposed solution 
i.e. use these resources as a guideline. Else see reboot to single user 
mode after install above and tunefs




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/26/12 21:27, Bas Smeelen wrote:

On 11/26/12 17:25, Jakub Lach wrote:

Thanks!

Regarding FAQ, some info about journalling should  be added to
"Chapter 9 Disks, File Systems, and Boot Loaders", especially now,
when SU+J is default.


Please also add:
SU+J does not work (yet) with dump on a live filesystem i.e. use snapshot.
If you want to use snapshot (dump -L) then disable the soft updates 
journal for that filesystem




Add to FAQ 9.4 Which partitions can safely use Soft Updates? I have 
heard that Soft Updates on / can cause problems.


Journaled Soft Updates (SU+J) is now default on FreeBSD 9.x-RELEASE 
installs.
This feature keeps a journal on soft updates which avoids a background 
filesystem check and speeds up a filesystem check during boot to a few 
seconds or less.

For history and technical details see:
http://jeffr-tech.livejournal.com/22716.html
and
http://www.*bsdcan*.org/2010/schedule/attachments/141_suj-slides.pdf

This can also be enabled/disabled with tunefs -j enable | disable
For more information see man 8 tunefs



New FAQ 9.28 I have heard about TRIM for Solid State Drives (SSD), is 
it supported by FreeBSD?


The TRIM filesystem flag is very useful for devices that use 
flash-memory (SSD for instance) and support the BIO_DELETE command.
This flag is not enabled by default and can be enabled/disabled with 
tunefs -t enable | disable

For more information see man 8 tunefs
 -t enable | disable
 Turn on/off the TRIM enable flag.  If enabled, and if the 
under-
 lying device supports the BIO_DELETE command, the file 
system

 will send a delete request to the underlying device for each
 freed block.  The trim enable flag is typically set when the
 underlying device uses flash-memory as the device can use 
the
 delete command to pre-zero or at least avoid copying 
blocks that

 have been deleted.

Important when using tunefs:
 This utility does not work on active file systems.  To change the 
root
 file system, the system must be rebooted after the file system is 
tuned.


FIlesystems have to be mounted read-only or not mounted at all



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/26/12 16:57, Jakub Lach wrote:

As a reminder, this isn't a contest in kernel size :)



Didn't mean to, I just put it there to state that 1.5 - 2.5 MB for a 
GENERIC kernel is not appropriate anymore.

More useful would be if somebody would check GENERIC
on i386/amd64 for FAQ update.


Thanks Miroslav Lachman for the reply with the correct sizes for GENERIC 
kernels.


Change FAQ 8.3 Why is my kernel so big?

Nowadays kernels are compiled in /debug mode by default/. Kernels built 
in debug mode contain many symbols that are used for debugging, thus 
greatly increasing the size of the kernel. Note that there will be 
little or no performance decrease from running a debug kernel, and it is 
useful in case of a system panic.


However



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/26/12 17:25, Jakub Lach wrote:

Thanks!

Regarding FAQ, some info about journalling should  be added to
"Chapter 9 Disks, File Systems, and Boot Loaders", especially now,
when SU+J is default.


Add to FAQ 9.4 Which partitions can safely use Soft Updates? I have 
heard that Soft Updates on / can cause problems.


Journaled Soft Updates (SU+J) is now default on FreeBSD 9.x-RELEASE 
installs.
This feature keeps a journal on soft updates which avoids a background 
filesystem check and speeds up a filesystem check during boot to a few 
seconds or less.

For history and technical details see:
http://jeffr-tech.livejournal.com/22716.html
and
http://www.*bsdcan*.org/2010/schedule/attachments/141_suj-slides.pdf

This can also be enabled/disabled with tunefs -j enable | disable
For more information see man 8 tunefs



New FAQ 9.28 I have heard about TRIM for Solid State Drives (SSD), is it 
supported by FreeBSD?


The TRIM filesystem flag is very useful for devices that use 
flash-memory (SSD for instance) and support the BIO_DELETE command.
This flag is not enabled by default and can be enabled/disabled with 
tunefs -t enable | disable

For more information see man 8 tunefs
 -t enable | disable
 Turn on/off the TRIM enable flag.  If enabled, and if the 
under-

 lying device supports the BIO_DELETE command, the file system
 will send a delete request to the underlying device for each
 freed block.  The trim enable flag is typically set when the
 underlying device uses flash-memory as the device can use the
 delete command to pre-zero or at least avoid copying 
blocks that

 have been deleted.

Important when using tunefs:
 This utility does not work on active file systems.  To change the root
 file system, the system must be rebooted after the file system is 
tuned.


FIlesystems have to be mounted read-only or not mounted at all





___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Help review the FAQ

[Bas Smeelen]

On 11/26/2012 04:26 PM, Volodymyr Kostyrko wrote:

26.11.2012 16:49, Jakub Lach:

Absolutely not, it's a heavily stripped custom kernel on this machine on
/boot/.


Do you call this heavily stripped? :)

> ls -la /boot/kernel/kernel
-r-xr-xr-x  1 root  wheel  5757970 Nov 26 10:57 /boot/kernel/kernel

However it's very hard to strip kernel further and make it usable for all 
machines.



I was pointing to that, if my kernel is 9 MB, there's no way GENERIC could
be
1.5-2.5 MB.


That's true...



i386 kernel with the only devices I need without debug symbols is 4.5MB on 
7.4-STABLE

fb1:/home/Freebee % uname -a
FreeBSD fb1 7.4-STABLE FreeBSD 7.4-STABLE #7: Mon Nov 26 11:27:42 CET 
2012 root@fb1:/usr/obj/usr/src/sys/FB1  i386

fb1:/home/Freebee % ls -lh /boot/kernel/kernel
-r-xr-xr-x  1 root  wheel   4.6M Nov 26 11:27 /boot/kernel/kernel

amd64 same story on 9.1-RC3 is 6.3MB
[Freebee@sys:~] $ uname -a
FreeBSD sys 9.1-RC3 FreeBSD 9.1-RC3 #0: Wed Oct 31 11:56:55 CET 2012 
root@sys:/usr/obj/usr/src/sys/SYS  amd64

[Freebee@sys:~] $ ls -hl /boot/kernel/kernel
-r-xr-xr-x  1 root  wheel   6.3M Oct 31 11:56 /boot/kernel/kernel



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How go back from X.Y-RELEASE-pZ to X.Y-RELEASE?

[Bas Smeelen]

On 11/23/2012 12:22 PM, Peter Olsson wrote:
> We are currently using cvs for both source and ports.
> I have begun changing to portsnap for ports, and I
> would also like to try changing at least some of our
> servers to freebsd-update.
>
> But all servers have been patched, using either RELENG_8_3
> or RELENG_9_0 as cvs tag. I need to revert them to their
> respective RELEASE to be able to use freebsd-update.
> Complete reinstall from eg CD is not an option, and I don't
> want to upgrade to a newer RELEASE at the moment.
>
> Can I change the cvs tags to RELENG_8_3_0_RELEASE or
> RELENG_9_0_0_RELEASE, and then build/install world and
> kernel as usual?
> Or will that method cause problems for the system or the
> installed ports?
>
> Thanks!

RELENG_9_0 and RELENG_8_3 are RELEASE branches including patches 
(8.3-RELEASE-p4 for instance), so you should be able to use freebsd-update 
ont them without changing anything.
If the servers are up to date then freebsd-update doesn't have to do 
anything for them untill the next paches for them come around.



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: confirm that csup is still usable fos the new 9.1

[Bas Smeelen]

On 11/16/2012 05:25 PM, Edwin L. Culp W. wrote:
> I haven't received updates to sources, ports or release for a few days.
> The process seems to work, no errors, but no updating.
>
> I seem to remember talk of no longer using csup but I could be confused.
>
> Thanks.
>
> results of named:
>
>   9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #320 r229960M: Sun Nov 11 05:04:45
> CST 2012

Hi Ed,

Uhm, no confirmation for the future I guess?
I still had a couple of servers upgraded with csup to 9.1-RC3 using cvs 
tag RELENG_9_1.
It seems that you have RELENG_9 which correspondents to 9-STABLE.
This is still at 9.1-PRERELEASE and maybe there are no updates due to 
the focus on 9.1-RELEASE.
I remember having read that cvs will not be available in the future for 
the new releases being RELENG_8_3 (8.3-RELEASE) and RELENG_9_1 
(9.1-RELEASE) at the moment, but it will continue to be available for 
the STABLE and CURRENT.

 From the revision number in uname I guess you are using svn ? Or is 
this also available when using csup?



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update and sources of 9.1-RC3

[Bas Smeelen]

On 11/06/2012 09:21 AM, Eugene Grosbein wrote:
> 04.11.2012 17:55, Bas Smeelen wrote:
>
>> To get the sources you can always use csup and set
>> default release=cvs tag=RELENG_9_1
>> or use subversion
> csup will gone in 3 or 4 month, not a long-term solution I need.

You're right.
For now you can still use it to get the source and then keep it updated with 
freebsd-update

> subversion still misses lightweight binary package like cvsup-nox11 was some 
> time ago.

Me too. With subversion you get about 14 extra dependencies and it is not 
really lightweight like csup.
csup will be available for the STABLE branches in the future but for how long?



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/04/2012 04:33 PM, Zoran Kolic wrote:
>> Just rebooting to single user mode after the install and then tunefs -j
>> disable /dev/ada0p2 works for me.
>> After a reboot then I just removed /.sujournal
> That crystillized to me as a correct way in this situation.
> Just one "fsck" at the very beginning? Manual says about
> some options available after it only.

I did not fsck just disable journaling for soft updates reboot and 
delete ./sujournal
> People mostly mention journaling for servers. Anybody using
> 9.x on laptop with ssd?
> Thanks all for help, regarding this option.
I don't have a laptop with ssd
Journaling SU is not recommended because of the extra writes but 
nowadays ssd should be fine with it, though less writes is less wear.  
Just take care to align your partitions to 1 or 2 MB which can be 
accomplished by going to shell on the partedit part of bsdinstall and 
use gpart -a or gpart -b





This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/04/2012 03:43 PM, George Mitchell wrote:
> On 11/03/12 15:09, Jeremy Chadwick wrote:
>> (Please keep me CC'd, as I'm not subscribed to -stable)
>>
>> I've CC'd Nathan Whitehorn, who according to bsdinstall(8) is the
>> author (not sure if maintainer) of the code.
>>
>> This default has already begun to bite users/SAs in the ass:
>>
>> http://lists.freebsd.org/pipermail/freebsd-questions/2012-November/246069.html
>>  
>>
>>
>> SU+J (the journalling part specifically) needs to be disabled by default
>> in the installer.  This default was a very bad choice and should not
>> have been done.  It either indicates someone was out of touch with the
>> rest of the issues surrounding the feature, or that someone
>> intentionally decided "it's the best way to get people using it for
>> testing" (I have seen this justification presented in the past, and it
>> is the wrong approach).
>>
>> However, since some people DO want it (and those folks don't use dump),
>> the installer should be modified to make SU+J support toggleable via a a
>> checkbox.  The default, obviously, should be unchecked.
>>
>> If the user checks the checkbox, an ominous warning message should be
>> displayed informing the user of the repercussions.  The only option at
>> that point should be "OK", after which the checkbox is checked.
>>
>> Do not tell me "send patches".  This issue/problem has gone on long
>> enough, and the community bitched hard/long enough, that the person who
>> committed this default should be responsible for fixing it.
>>
>> We should operate under the assumption that this bug/problem will never
>> be fixed.  It probably will be, but again, we must operate with the
>> assumption that Kirk et al will require years to fix it.  (It has
>> already been something like 9 months.  Or is it a year?)
>>
>> [...]
>
> I will give this comment a BIG, BIG, +1!   -- George

A small patch already sent via pr

http://www.freebsd.org/cgi/query-pr.cgi?pr=173301

Let's see what goes



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/04/2012 01:13 PM, HATANO Tomomi wrote:
> Hi all.
>
> The point is:
>
>  There is completely no way to take a snapshot of SU+J partition
>  unless modify one's kernel.
>
> Whether some issue still exist or not,
> how about enabling snapshoting SU+J partition
> through sysctl variable?
>
> Would you mind to see patch attached?
>
> 1. Taking a snapshot of SU+J partition is controlled through sysctl variable.
>
> 2. Default to disable.
> One who want to enable it should set the variable manually.
>
> 3. The default value in bsdinstall(8) may be left as is.

Hi
If I understand correctly this still leaves your default installed 
system with SU+J and if you set the sysctl variable it means okay I am 
prepared for trouble when taking a snapshot of a SU+J filesystem?
Why would I want a sysctl variable that gives me known trouble?
Or have I misread your patch?

When taking a snapshot of a SU+J filesystem we already get the nice not 
supported error instead of getting into trouble.

I think SU+J should not be default unless it works fine with the rest of 
the system as described in the handbook.




This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update and sources of 9.1-RC3

[Bas Smeelen]

On 11/04/2012 12:08 PM, jb wrote:
> Bas Smeelen  ose.nl> writes:
>
>> ...
>> To file a PR it will require some work to find out exactly what the PR
>> should be about.
>> Since freebsd-update is meant to update the system I don't really see a
>> point to make it install sources (or others things) if they are not
>> present on the system being updated.
>> ...
> Well, that proves my earlier point.

You are right.

>
> But, you brought up that "StrictComponents yes" option and we have to figure
> out what it means ...

 From looking at the freebsd-update script (it's in /usr/sbin) I 
understand when StrictComponents is set to yes it skips the step, 
inspecting system and uses the list provided in freebsd-update.conf, 
so this option might save some time and disk activity.
I don't fully understand what the impact might be when running a custom 
kernel.

>
> # When upgrading between releases, should the list of Components be
> # read strictly (StrictComponents yes) or merely as a list of components
> # which *might* be installed of which FreeBSD Update should figure out
> # which actually are installed and upgrade those (StrictComponents no)?
> # StrictComponents no
>
> The components are:
> Components src world kernel
>
> Then what gives ? Does it not apply to src component ?
> jb
>
>



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update and sources of 9.1-RC3

[Bas Smeelen]

On 11/04/2012 11:25 AM, jb wrote:
> Bas Smeelen  ose.nl> writes:
>
>> ...
>> Can't this be accomplished by setting
>> StrictComponents yes
>> in /etc/freebsd-update.conf ?
>>
>> Then feebsd-update does not try to figure out the components to update
>> by itself, but updates the components mentioned in
>> Components src world kernel
>>
>> I didn't try what happens if no source is installed.
> Good shot, that could be the "override" option ...
>
> I did the test and it did not work out for me.

OK, well this could have been expected because freebsd-update is meant 
to update the components on a system and not to install new components. 
On the update servers there are delta binaries present but not full 
binaries (or archives) to add new components. See further below.
>
> # cat /etc/freebsd-update.conf
> ...
> Components src world kernel
> ...
> StrictComponents yes
> ...
> #


>
> # uname -a
> FreeBSD localhost.localdomain 9.1-RC3 FreeBSD 9.1-RC3 #0 r242324: Tue Oct 30 
> 00:
> 18:27 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  
> i38
> 6
>
> No luck. Should we file a PR# (there are some error msgs anyway) ?
> jb

To file a PR it will require some work to find out exactly what the PR 
should be about.
Since freebsd-update is meant to update the system I don't really see a 
point to make it install sources (or others things) if they are not 
present on the system being updated.

To get the sources you can always use csup and set
default release=cvs tag=RELENG_9_1
or use subversion





This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/04/2012 06:19 AM, Zoran Kolic wrote:
>> There's an existing checkbox to disable it. There was substantial
>> consensus for 9.0 that SUJ was something we wanted
> Nice to hear. I assume you mean check box during install
> process? Not mentioned in install guide in handbook.
> So, after I accept guided partitioning, I should go to
> "modify" or else? Sorry to bother again and again, but
> it is not clear to me at the moment. I'd avoid further
> tunefs if possible.
> If not possible, let me clear that branch 8 has no J as
> default and I found myself wondering. Correct me if I'm
> wrong. I have to go to single user mode first. Make fsck
> on partition that contains freebsd-ufs ( / ). Check
> options for that partition with "tunefs -p partition".
> What exact name that partition would have? Next I have to
> disable journaling with "-j disable" and enable trim with
> "-t enable". Reboot and voila?
> People mention file or partition that has to be deleted.
> Next few days I will put ssd into laptop and manage install,
> when release shows up. If there is another point I have
> to choose for journaling, let me know.
> Best regards all
>
>Zoran

I have just installed fresh from 9.1-RC3 ISO and cannot find a checkbox 
to disable journaling or enable TRIM. Do I miss something here?

The only way I can find to customize is to go to the shell, which is an 
option in bsdinstall partedit and then gpart and newfs from there. This 
way I can align to 1 or 2 MB, enable TRIM and disable journaling, and 
make use of all options someone desires.

Also I tried using the shell at the end of the install to disable 
journaling, but this cannot be done since /mnt is busy.

Just rebooting to single user mode after the install and then tunefs -j 
disable /dev/ada0p2 works for me.
Replace ada0 with the device your disk is on, p2 is the defalt partition 
for /
After a reboot then I just removed /.sujournal

Still I have send a pr with patch to change the default, let's see what 
goes.



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update and sources of 9.1-RC3

[Bas Smeelen]

On 11/03/2012 05:03 PM, jb wrote:
> Eugene Grosbein  grosbein.net> writes:
>
>> ...
>> My real question is how make freebsd-update download sources they are not
>> installed?
> I am not 110% sure, but you can not.
> When freebsd-update runs, it checks its config file /etc/freebsd-update.conf
> and then takes inventory of your system (that's why it is called "update", and
> that's why you do not get new src set).
> FREEBSD-UPDATE(8) does not give any "override" option.
> So, here you are. But next time (assuming you keep your src) you will be fine.
> jb

Can't this be accomplished by setting
StrictComponents yes
in /etc/freebsd-update.conf ?

Then feebsd-update does not try to figure out the components to update 
by itself, but updates the components mentioned in
Components src world kernel

I didn't try what happens if no source is installed.




This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/02/2012 10:42 PM, Daniel Eischen wrote:
> On Sat, 3 Nov 2012, Adam Strohl wrote:
>
>> On 11/2/2012 23:47, Bas Smeelen wrote:
>>> Hi
>>>
>>> Why are journaled soft updates the default when installing a new system
>>> from a 9.1-RC2 ISO?
>>>
>>> I admit I did not pay too much attention when installing a new system
>>> from an 9.1-RC2 ISO and found out when taking a snapshot with dump 
>>> (dump
>>> -0Lauf) to clone the system. Other systems (9-STABLE, 9.1-RC2 and
>>> 9.1-RC3) have been upgraded from 8.X-RELEASE and earlier, so there are
>>> no journaled soft updates enabled, just soft updates, and well there
>>> dump with snapshot works just fine.
>>>
>>> Can SU+J be disabled for the 9.1-RELEASE or do you think this is not
>>> going to be a problem for users of FreeBSD? I will have to boot these
>>> two systems single user now to disable the soft updates journal, 
>>> because
>>> I use dump + restore on live systems, not a problem for me, it is just
>>> an inconvenience.
>>
>>
>> I have to second this sentiment.  Unless the dump/snapshot issue has 
>> been resolved they journal should be turned off by default.
>
> +1
>
I have submitted a PR with patch, see how it goes
Cheers



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [patch] Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/02/2012 07:59 PM, Gary Palmer wrote:
> On Fri, Nov 02, 2012 at 07:41:31PM +0100, Mateusz Guzik wrote:
>> On Fri, Nov 02, 2012 at 07:30:04PM +0100, Bas Smeelen wrote:
>>> On 11/02/2012 07:17 PM, Bas Smeelen wrote:
>>>> On 11/02/2012 07:08 PM, Bas Smeelen wrote:
>>>>> On 11/02/2012 06:27 PM, Adam Strohl wrote:
>>>>>> On 11/3/2012 0:13, Mike Jakubik wrote:
>>>>>>> You can disable SU+J after installing, though it would be nice if the
>>>>>>> installer gave you a choice.
>>>>>> This assumes that you know about this flaw, which most people do not.
>>>>>>
>>>>>> I didn't until I discovered it by panic-ing a perfectly fine running
>>>>>> server.  Getting burned by a known bug like this shouldn't be "SOP"
>>>>>> for users of FreeBSD.
>>>>>>
>>>>>> If anything it should be turned off by default, and people can turn it
>>>>>> on if they want given the landmine it plants.  If they know how to
>>>>>> turn it on they're much more likely to be aware of the issue.
>>>>>>
>>>>>>
>>>>>>
>>> To sum it up
>>> SU+J should be turned off by default because of
>>> 1. It does not work with dumping a live system e.g. snapshot
>>> 2. it is not recommended for SSD installs
>>> 3. "Smart" admins can turn it on if they want
>>>
>>> root@sys:/usr/src/usr.sbin/bsdinstall/partedit # diff -u gpart_ops.c
>>> gpart_ops.cnew
>>> --- gpart_ops.c2012-08-06 01:54:33.0 +0200
>>> +++ gpart_ops.cnew2012-11-02 19:07:45.0 +0100
>>> @@ -90,8 +90,8 @@
>>>{"SU", "Softupdates",
>>>"Enable softupdates (default)", 1 },
>>>{"SUJ", "Softupdates journaling",
>>> -"Enable file system journaling (default - "
>>> -"turn off for SSDs)", 1 },
>>> +"Disable file system journaling (default - "
>>> +"turn on for adventurish admins)", 0 },
>>>{"TRIM", "Enable SSD TRIM support",
>>>"Enable TRIM support, useful on solid-state drives",
>>>0 },
>>>
>>> Please comment, then I can file a PR or not
>> As was noted in my another mail, the kernel will no longer crash when an
>> attempt to take a snapshot is made. Also AFAIR SUJ can be disabled
>> later.
>>
>> Given that I prefer the following:
>>
>> diff --git a/usr.sbin/bsdinstall/partedit/gpart_ops.c 
>> b/usr.sbin/bsdinstall/partedit/gpart_ops.c
>> index 479365a..80296c2 100644
>> --- a/usr.sbin/bsdinstall/partedit/gpart_ops.c
>> +++ b/usr.sbin/bsdinstall/partedit/gpart_ops.c
>> @@ -91,7 +91,7 @@ newfs_command(const char *fstype, char *command, int 
>> use_default)
>>  "Enable softupdates (default)", 1 },
>>  {"SUJ", "Softupdates journaling",
>>  "Enable file system journaling (default - "
>> -"turn off for SSDs)", 1 },
>> +"turn off for SSDs or if you use snapshots)", 1 },
>>  {"TRIM", "Enable SSD TRIM support",
>>  "Enable TRIM support, useful on solid-state drives",
>>  0 },
>>
>> http://people.freebsd.org/~mjg/patches/suj-snapshot-comment.diff
> How many people realise that snapshots are needed for dump based backups
> (and other related features)?
>
> Gary

My guess? A lot.
But most who realize would turn SU+J off on new installs.
I just ran across this when doing a new install from 9.1-RC2 and not 
paying attention e.g. realizing that SU+J is turned on by default now.
I have seen coming this across the mail lists before though.



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [patch] Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/02/2012 07:41 PM, Mateusz Guzik wrote:
> On Fri, Nov 02, 2012 at 07:30:04PM +0100, Bas Smeelen wrote:
>> On 11/02/2012 07:17 PM, Bas Smeelen wrote:
>>> On 11/02/2012 07:08 PM, Bas Smeelen wrote:
>>>> On 11/02/2012 06:27 PM, Adam Strohl wrote:
>>>>> On 11/3/2012 0:13, Mike Jakubik wrote:
>>>>>> You can disable SU+J after installing, though it would be nice if the
>>>>>> installer gave you a choice.
>>>>> This assumes that you know about this flaw, which most people do not.
>>>>>
>>>>> I didn't until I discovered it by panic-ing a perfectly fine running
>>>>> server.  Getting burned by a known bug like this shouldn't be "SOP"
>>>>> for users of FreeBSD.
>>>>>
>>>>> If anything it should be turned off by default, and people can turn it
>>>>> on if they want given the landmine it plants.  If they know how to
>>>>> turn it on they're much more likely to be aware of the issue.
>>>>>
>>>>>
>>>>>
>> To sum it up
>> SU+J should be turned off by default because of
>> 1. It does not work with dumping a live system e.g. snapshot
>> 2. it is not recommended for SSD installs
>> 3. "Smart" admins can turn it on if they want
>>
>> root@sys:/usr/src/usr.sbin/bsdinstall/partedit # diff -u gpart_ops.c
>> gpart_ops.cnew
>> --- gpart_ops.c2012-08-06 01:54:33.0 +0200
>> +++ gpart_ops.cnew2012-11-02 19:07:45.0 +0100
>> @@ -90,8 +90,8 @@
>>{"SU", "Softupdates",
>>"Enable softupdates (default)", 1 },
>>{"SUJ", "Softupdates journaling",
>> -"Enable file system journaling (default - "
>> -"turn off for SSDs)", 1 },
>> +"Disable file system journaling (default - "
>> +"turn on for adventurish admins)", 0 },
>>{"TRIM", "Enable SSD TRIM support",
>>"Enable TRIM support, useful on solid-state drives",
>>0 },
>>
>> Please comment, then I can file a PR or not
> As was noted in my another mail, the kernel will no longer crash when an
> attempt to take a snapshot is made. Also AFAIR SUJ can be disabled
> later.
>
> Given that I prefer the following:
>
> diff --git a/usr.sbin/bsdinstall/partedit/gpart_ops.c 
> b/usr.sbin/bsdinstall/partedit/gpart_ops.c
> index 479365a..80296c2 100644
> --- a/usr.sbin/bsdinstall/partedit/gpart_ops.c
> +++ b/usr.sbin/bsdinstall/partedit/gpart_ops.c
> @@ -91,7 +91,7 @@ newfs_command(const char *fstype, char *command, int 
> use_default)
>   "Enable softupdates (default)", 1 },
>   {"SUJ", "Softupdates journaling",
>   "Enable file system journaling (default - "
> - "turn off for SSDs)", 1 },
> + "turn off for SSDs or if you use snapshots)", 1 },
>   {"TRIM", "Enable SSD TRIM support",
>   "Enable TRIM support, useful on solid-state drives",
>   0 },
>
> http://people.freebsd.org/~mjg/patches/suj-snapshot-comment.diff
>

Hi Mateusz
I can see some benefits of having journaled soft updates and I 
understand your preference.
Though the last 10 years I have not had the inconvenience of having to 
deal with long fsck' s or bgfsck' s on servers or workstation installs, 
so I think this should not be default on new installs.
Since there are more SSD installs nowadays, it might be a good option to 
turn soft updates journaling off by default.
Can you explain the benefits of having journaled soft updates turned on?
There are also a lot of back-up service providers who use the snapshot 
functionality to be able to host a lot of back-ups, though they might be 
using zfs for this now I would guess.
Kind regards
Bas





This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/02/2012 07:31 PM, Mateusz Guzik wrote:
> On Sat, Nov 03, 2012 at 12:27:18AM +0700, Adam Strohl wrote:
>> On 11/3/2012 0:13, Mike Jakubik wrote:
>>> You can disable SU+J after installing, though it would be nice if the
>>> installer gave you a choice.
>> This assumes that you know about this flaw, which most people do not.
>>
>> I didn't until I discovered it by panic-ing a perfectly fine running
>> server.  Getting burned by a known bug like this shouldn't be "SOP"
>> for users of FreeBSD.
>>
> Currently when you try to take a snapshot, the kernel checks whether SUJ
> is enabled on specified mount-point, and if yes it returns EOPNOTSUPP.
>
> See this commit (MFCed as r230725):
> http://svnweb.freebsd.org/base?view=revision&revision=230250
>
> So it's not that bad.

How about more installs on SSD and the hint about this in the 
bsdinstaller source?



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[patch] Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/02/2012 07:17 PM, Bas Smeelen wrote:
> On 11/02/2012 07:08 PM, Bas Smeelen wrote:
>> On 11/02/2012 06:27 PM, Adam Strohl wrote:
>>> On 11/3/2012 0:13, Mike Jakubik wrote:
>>>> You can disable SU+J after installing, though it would be nice if the
>>>> installer gave you a choice.
>>> This assumes that you know about this flaw, which most people do not.
>>>
>>> I didn't until I discovered it by panic-ing a perfectly fine running
>>> server.  Getting burned by a known bug like this shouldn't be "SOP"
>>> for users of FreeBSD.
>>>
>>> If anything it should be turned off by default, and people can turn it
>>> on if they want given the landmine it plants.  If they know how to
>>> turn it on they're much more likely to be aware of the issue.
>>>
>>>
>>>
To sum it up
SU+J should be turned off by default because of
1. It does not work with dumping a live system e.g. snapshot
2. it is not recommended for SSD installs
3. "Smart" admins can turn it on if they want

root@sys:/usr/src/usr.sbin/bsdinstall/partedit # diff -u gpart_ops.c 
gpart_ops.cnew
--- gpart_ops.c2012-08-06 01:54:33.0 +0200
+++ gpart_ops.cnew2012-11-02 19:07:45.0 +0100
@@ -90,8 +90,8 @@
  {"SU", "Softupdates",
  "Enable softupdates (default)", 1 },
  {"SUJ", "Softupdates journaling",
-"Enable file system journaling (default - "
-"turn off for SSDs)", 1 },
+"Disable file system journaling (default - "
+"turn on for adventurish admins)", 0 },
  {"TRIM", "Enable SSD TRIM support",
  "Enable TRIM support, useful on solid-state drives",
  0 },

Please comment, then I can file a PR or not
Cheers
Bas




This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [patch proposal typo corrected] Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/02/2012 07:08 PM, Bas Smeelen wrote:
> On 11/02/2012 06:27 PM, Adam Strohl wrote:
>> On 11/3/2012 0:13, Mike Jakubik wrote:
>>> You can disable SU+J after installing, though it would be nice if the
>>> installer gave you a choice.
>> This assumes that you know about this flaw, which most people do not.
>>
>> I didn't until I discovered it by panic-ing a perfectly fine running
>> server.  Getting burned by a known bug like this shouldn't be "SOP"
>> for users of FreeBSD.
>>
>> If anything it should be turned off by default, and people can turn it
>> on if they want given the landmine it plants.  If they know how to
>> turn it on they're much more likely to be aware of the issue.
>>
>>

Sorry for the spam.
Also since newer systems will be installing more and more on SSD it is 
better to default SU+J to off as I understand from the original source.
Cheers

> Hi all
>
> I am not sure if this is the right place, but would like to propose this
> patch
> root@sys:/usr/src/usr.sbin/bsdinstall/partedit # diff -p gpart_ops.c
> gpart_ops.cnew
> *** gpart_ops.cMon Aug  6 01:54:33 2012
> --- gpart_ops.cnewFri Nov  2 19:02:43 2012
> *** newfs_command(const char *fstype, char *
> *** 90,97 
> {"SU", "Softupdates",
> "Enable softupdates (default)", 1 },
> {"SUJ", "Softupdates journaling",
> ! "Enable file system journaling (default - "
> ! "turn off for SSDs)", 1 },
> {"TRIM", "Enable SSD TRIM support",
> "Enable TRIM support, useful on solid-state drives",
> 0 },
> --- 90,97 
> {"SU", "Softupdates",
> "Enable softupdates (default)", 1 },
> {"SUJ", "Softupdates journaling",
> ! "Disable file system journaling (default - "
> ! "turn on for adventurish admins)", 0 },
> {"TRIM", "Enable SSD TRIM support",
> "Enable TRIM support, useful on solid-state drives",
> 0 },
>
> If OK I will file a PR
> Cheers
> Bas
>
>
>
> This e-mail message, including any attachment(s), is intended solely for the 
> addressee or addressees. Any views or opinions presented herein are solely 
> those of the author and do not necessarily represent those of OSE.
>
> If you are not the intended recipient of this communication please return 
> this e-mail message and the attachment(s) to the sender and delete and 
> destroy all copies.
>
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[patch proposal typo corrected] Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/02/2012 06:27 PM, Adam Strohl wrote:
> On 11/3/2012 0:13, Mike Jakubik wrote:
>> You can disable SU+J after installing, though it would be nice if the
>> installer gave you a choice.
>
> This assumes that you know about this flaw, which most people do not.
>
> I didn't until I discovered it by panic-ing a perfectly fine running
> server.  Getting burned by a known bug like this shouldn't be "SOP"
> for users of FreeBSD.
>
> If anything it should be turned off by default, and people can turn it
> on if they want given the landmine it plants.  If they know how to
> turn it on they're much more likely to be aware of the issue.
>
>
Hi all

I am not sure if this is the right place, but would like to propose this 
patch
root@sys:/usr/src/usr.sbin/bsdinstall/partedit # diff -p gpart_ops.c 
gpart_ops.cnew
*** gpart_ops.cMon Aug  6 01:54:33 2012
--- gpart_ops.cnewFri Nov  2 19:02:43 2012
*** newfs_command(const char *fstype, char *
*** 90,97 
   {"SU", "Softupdates",
   "Enable softupdates (default)", 1 },
   {"SUJ", "Softupdates journaling",
! "Enable file system journaling (default - "
! "turn off for SSDs)", 1 },
   {"TRIM", "Enable SSD TRIM support",
   "Enable TRIM support, useful on solid-state drives",
   0 },
--- 90,97 
   {"SU", "Softupdates",
   "Enable softupdates (default)", 1 },
   {"SUJ", "Softupdates journaling",
! "Disable file system journaling (default - "
! "turn on for adventurish admins)", 0 },
   {"TRIM", "Enable SSD TRIM support",
   "Enable TRIM support, useful on solid-state drives",
   0 },

If OK I will file a PR
Cheers
Bas



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[patch proposal] Re: SU+J on 9.1-RC2 ISO

[Bas Smeelen]

On 11/02/2012 06:27 PM, Adam Strohl wrote:
> On 11/3/2012 0:13, Mike Jakubik wrote:
>> You can disable SU+J after installing, though it would be nice if the
>> installer gave you a choice.
>
> This assumes that you know about this flaw, which most people do not.
>
> I didn't until I discovered it by panic-ing a perfectly fine running 
> server.  Getting burned by a known bug like this shouldn't be "SOP" 
> for users of FreeBSD.
>
> If anything it should be turned off by default, and people can turn it 
> on if they want given the landmine it plants.  If they know how to 
> turn it on they're much more likely to be aware of the issue.
>
>
Hi all

I am not sure if this is the right place, but would like to propose this 
patch
root@sys:/usr/src/usr.sbin/bsdinstall/partedit # diff -p gpart_ops.c 
gpart_ops.cnew
*** gpart_ops.cMon Aug  6 01:54:33 2012
--- gpart_ops.cnewFri Nov  2 19:02:43 2012
*** newfs_command(const char *fstype, char *
*** 90,97 
   {"SU", "Softupdates",
   "Enable softupdates (default)", 1 },
   {"SUJ", "Softupdates journaling",
! "Enable file system journaling (default - "
! "turn off for SSDs)", 1 },
   {"TRIM", "Enable SSD TRIM support",
   "Enable TRIM support, useful on solid-state drives",
   0 },
--- 90,97 
   {"SU", "Softupdates",
   "Enable softupdates (default)", 1 },
   {"SUJ", "Softupdates journaling",
! "Disble file system journaling (default - "
! "turn on for adventurish admins)", 0 },
   {"TRIM", "Enable SSD TRIM support",
   "Enable TRIM support, useful on solid-state drives",
   0 },

If OK I will file a PR
Cheers
Bas



This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

SU+J on 9.1-RC2 ISO

[Bas Smeelen]

Hi

Why are journaled soft updates the default when installing a new system 
from a 9.1-RC2 ISO?

I admit I did not pay too much attention when installing a new system 
from an 9.1-RC2 ISO and found out when taking a snapshot with dump (dump 
-0Lauf) to clone the system. Other systems (9-STABLE, 9.1-RC2 and 
9.1-RC3) have been upgraded from 8.X-RELEASE and earlier, so there are 
no journaled soft updates enabled, just soft updates, and well there 
dump with snapshot works just fine.

Can SU+J be disabled for the 9.1-RELEASE or do you think this is not 
going to be a problem for users of FreeBSD? I will have to boot these 
two systems single user now to disable the soft updates journal, because 
I use dump + restore on live systems, not a problem for me, it is just 
an inconvenience.

Cheers
Bas


This e-mail message, including any attachment(s), is intended solely for the 
addressee or addressees. Any views or opinions presented herein are solely 
those of the author and do not necessarily represent those of OSE.

If you are not the intended recipient of this communication please return this 
e-mail message and the attachment(s) to the sender and delete and destroy all 
copies.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 9.1-PRERELEASE and ntpd problem

[Bas Smeelen]

On 07/20/2012 10:18 AM, Daniel Braniss wrote:

my console is filling up with:

Jul 20 11:08:18 pundit ntpd[1075]: bind() fd 27, family AF_INET6, port 123,
scope 2, addr fe80::f66d:4ff:fee1:f7ba, mcast=0 flags=0x11 fails: Can't assign
requested address
Jul 20 11:08:18 pundit ntpd[1075]: unable to create socket on re0 (8) for
fe80::f66d:4ff:fee1:f7ba#123
Jul 20 11:13:18 pundit ntpd[1075]: bind() fd 27, family AF_INET6, port 123,
scope 2, addr fe80::f66d:4ff:fee1:f7ba, mcast=0 flags=0x11 fails: Can't assign
requested address
Jul 20 11:13:18 pundit ntpd[1075]: unable to create socket on re0 (9) for
fe80::f66d:4ff:fee1:f7ba#123

any ideas?
thanks,
danny



Hi Danny

I don't see this problem here with a GENERIC kernel and unmodified ntp.conf
Are you using IPv6 ?
Do you have an unmodified ntp.conf ?
What does /var/log/messages give when you do a service ntpd restart ?

Here it is:
Jul 20 10:40:49 dd ntpd[1030]: ntpd exiting on signal 15
Jul 20 10:40:49 dd ntpd[1390]: ntpd 4.2.4p5-a (1)
Jul 20 10:40:56 dd ntpd[1391]: kernel time sync status change 2001
on a uname -a
FreeBSD dd.ose.nl 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #6:
Fri Jul 20 09:04:04 CEST 2012 r...@dd.ose.nl:/usr/obj/usr/src/sys/GENERIC  amd64


I have ssh bound to tcp4 and tcp6 and ntpd is bound to udp4 and udp6
tcp4   0  0 *.ssh  *.* LISTEN
udp4   0  0 *.ntp

tcp6   0  0 *.ssh  *.* LISTEN
udp6   0  0 *.ntp  *.*




Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Recommendation for Hyervisor to host FreeBSD

[Bas Smeelen]

On 07/05/2012 01:43 PM, Pete French wrote:

So, my work surprise for a Thursday morning is an urgent requirement to
see if we can run a set of FreeBSD machines under virtualised servers.
I have not done this before personally, but I notice from post here
that it doesnt seem uncommon, and I see Xen related commits flowing
past, so I am guessing it is doable.

So, for running 8 or 9 STABLE can anyone recommend which hypervisor
works best, and is 8 or 9 better as the OS to run ? Am doing a bit
of research myself, but nothing beats persoanl experience in these
matters!

cheers,

-pete.


I have got some 8 and 9 STABLE servers running under KVM linux which works 
good with either ide or scsi drives and e1000 nics or the virtio drives and 
nics that use the virtio kernel modules from ports. I would recommend this.
Also the free of charge vmware server 2 on linux is doing a good job for 
FreeBSD guests.


But if you are going to choose a hypervisor on bare metal for FreeBSD 
guests, why not just run FreeBSD with jails?





Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: flowtable usable or not

[Bas Smeelen]

On 03/03/2012 04:32 PM, H wrote:

Bas Smeelen wrote:

/>/ away. Binary packages are a big time saver and are more efficient. It
/>/ should be easy for FreeBSD to make it easy to install the most recent
/>/ versions of all binary packages, its beyond belief they cannot pull
/>/ off such a simple ans straight forward, and basic part of any OS.  /

come on, you really think I need lecturing about how to read threads?

and I did not misquoted nothing, you are trying to save your ass here :)

in the above excerpt _YOU_ are talking about packages and how easy it is
... and this "cannot pull off" thing ...

then you tell us today that ports is the best ever happened to you


I am sorry, but I really did not write the sentences you quote. It is 
what David Jackson wrote and I replied to it.


Please see again
http://lists.freebsd.org/pipermail/freebsd-questions/2012-January/237779.html 



I will paste the the message below:


 Unable to upgrade packages on FreeBSD

*Bas Smeelen* b.smeelen at ose.nl 
<mailto:freebsd-questions%40freebsd.org?Subject=Unable%20to%20upgrade%20packages%20on%20FreeBSD&In-Reply-To=CAGy-%2Bi9pYgB3VjG8KQg98Bfr5Ax2BOLOnuqrzOe_P5juDe%2BVjw%40mail.gmail.com>

/Mon Jan 30 23:01:17 UTC 2012

/

On Mon, 30 Jan 2012 17:04:56 -0500
David Jacksonhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions>>  wrote:


/  On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelenhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions>>  wrote:

/>/
/>/  >  On Mon, 30 Jan 2012 12:52:07 -0500
/>/  >  David Jacksonhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions>>  wrote:
/>/  >
/>/  >  >  I have tried endlessly to no avail to upgrade binary the packages
/>/  >  >  on Freebsd to the latest version. I have tried:
/>/  >  >
/>/  >  >  *portupgrade -PP -a
/>/  >  >  *portmaster -PP -a
/>/  >  >  *pkg_update
/>/  >  >
/>/  >  >  All fail miserably and totally and have left the system in an
/>/  >  >  unuseable state.
/>/  >
/>/  >  What's unusable? For instance, servers are perfectly usable without
/>/  >  graphical tools. If you have tried `endlessly` why didn't you
/>/  >  consult /usr/ports/UPDATING and just recompile the ports without
/>/  >  using binary packages?
/>/  >  Or you might want to try PCBSD, it's FreeBSD with some fancy stuff
/>/  >  taken care of which might solve the problem you complain about.
/>/  >  >
/>/  >
/>/
/>/
/>/  I wish to use binary packages and I specifically do not want to
/>/  compile anything, it tends to take far too long to compile programs
/>/  and would rather install some packages and have it all work right
/>/  away. Binary packages are a big time saver and are more efficient. It
/>/  should be easy for FreeBSD to make it easy to install the most recent
/>/  versions of all binary packages, its beyond belief they cannot pull
/>/  off such a simple ans straight forward, and basic part of any OS.
/
I understand your motivations.
On my 1,6GHz celeron it takes a lot of time to compile the ~600 ports I
use, especially chromium for instance and when I forget to give an
option to not bother me with questions it sits there waiting for me to
enter y or n.
Ports/ packages are not `a basic part` of the FreeBSD OS. I also don't
think it is simple and straight forward to satisfy all different user
requirements and options in a package system. Ubuntu for my taste has
had flukes in many ways many times in the past and still has (often
enough the developers desktop users complain). It works good with
complete upgrades at times, on the other hand it still leaves me
sometimes with an unusable freezing OS on the desktop, and before every
upgrade it has becomes mandatory to me to first try it with an USB boot.
This is something I cannot have on server systems being used 24x7.


/

/>/
/>/  >  >  Why can't FreeBSD just make the package system "just work". Right
/>/  >  >  after installing FreeBSD I should be able to type a single command
/>/  >  >  such as update_packages and it should update all packages on the
/>/  >  >  system, with no errors and without requiring any configurations
/>/  >  >  to be troubleshooted, it should work out of the box.
/>/  >  >
/>/  >  >  Why not? Why is something so simple so difficult and impossible?
/>/  >  >  Ubuntu can do it, why not FreeBSD?
/>/  >
/>/  >  FreeBSD unlike Ubuntu is an entirely volunteer project. Ubuntu has
/>/  >  a dedicated corporation working on it and I guess a larger user
/>/  >  base.
/>/  >
/>/
/>/  The reason that FreeBSD has a smaller user base is because it has a
/>/  dysfunctional package system and it is hard to upgrade package to the
/>/ 

Re: flowtable usable or not

[Bas Smeelen]

On 03/03/2012 10:18 AM, H wrote:

Bas Smeelen wrote:

On 03/02/2012 07:42 PM, H wrote:

Doug Barton wrote:

... and here is the crux of the problem. The vast majority of our
developers don't use FreeBSD as their regular workstation. So it has
increasingly become an OS where changes are being lobbed over the wall
by developers who don't run systems that those changes affect. That's
no way to run a railroad. Doug

wow

since it is not April 1st it must be revelation's day ...:)

is this then the bottomline ?

if [ $using_ports=YES ]; get_screwed($big_time); fi



Hey people

There are still a lot of us which might not be smart enough or lack
the resources to help you debug issues but we still use and depend on
FreeBSD, and we test, and hopefully give you some debugging hints

I have some production servers running on STABLE  and even some on
CURRENT to stress our developers, but most run RELEASE and use
freebsd-update

Keep up the good work, it makes me a more confident sysadmin
Ports is the best thing happening to me after going through al the apt
and other stuff

you talk like the wind blows my friend ...

remembering  your own most recent words in another occasion  what
certainly do not match your last sentence ...


The last sentences:

In short: FreeBSD makes you think about what you are doing beforehand
which makes a great way to upgrade/ update application, database e.g.
on servers whithout running into service downtime. Other OS's don't or
do it less. I like that a lot, it saves a lot of incoming phone calls.

http://lists.freebsd.org/pipermail/freebsd-questions/2012-January/237779.html





/ On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelenhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions>>  wrote:

/>/
/>/>  On Mon, 30 Jan 2012 12:52:07 -0500
/>/>  David Jacksonhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions>>  wrote:
/>/>
/>/>  >  I have tried endlessly to no avail to upgrade binary the packages
/>/>  >  on Freebsd to the latest version. I have tried:
/>/>  >
/...

/>  >

/>/>  >  All fail miserably and totally and have left the system in an
/>/>  >  unuseable state.
/>/>
/

/

/>/
/>/ I wish to use binary packages and I specifically do not want to
/>/ compile anything, it tends to take far too long to compile programs
/>/ and would rather install some packages and have it all work right
/>/ away. Binary packages are a big time saver and are more efficient. It
/>/ should be easy for FreeBSD to make it easy to install the most recent
/>/ versions of all binary packages, its beyond belief they cannot pull
/>/ off such a simple ans straight forward, and basic part of any OS.  /









Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: flowtable usable or not

[Bas Smeelen]

On 03/03/2012 10:18 AM, H wrote:

you talk like the wind blows my friend ...

remembering  your own most recent words in another occasion  what
certainly do not match your last sentence ...


What you 'mis'quote further down was not my writing.
http://lists.freebsd.org/pipermail/freebsd-questions/2012-January/237779.html
My reply to djackson was and more, see link above

I understand your motivations.
On my 1,6GHz celeron it takes a lot of time to compile the ~600 ports I
use, especially chromium for instance and when I forget to give an
option to not bother me with questions it sits there waiting for me to
enter y or n.
Ports/ packages are not `a basic part` of the FreeBSD OS. I also don't
think it is simple and straight forward to satisfy all different user
requirements and options in a package system. Ubuntu for my taste has
had flukes in many ways many times in the past and still has (often
enough the developers desktop users complain). It works good with
complete upgrades at times, on the other hand it still leaves me
sometimes with an unusable freezing OS on the desktop, and before every
upgrade it has becomes mandatory to me to first try it with an USB boot.
This is something I cannot have on server systems being used 24x7.






/ On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelenhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions>>  wrote:

/>/
/>/>  On Mon, 30 Jan 2012 12:52:07 -0500
/>/>  David Jacksonhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions>>  wrote:
/>/>
/>/>  >  I have tried endlessly to no avail to upgrade binary the packages
/>/>  >  on Freebsd to the latest version. I have tried:
/>/>  >
/...

/>  >

/>/>  >  All fail miserably and totally and have left the system in an
/>/>  >  unuseable state.
/>/>
/

/

/>/
/>/ I wish to use binary packages and I specifically do not want to
/>/ compile anything, it tends to take far too long to compile programs
/>/ and would rather install some packages and have it all work right
/>/ away. Binary packages are a big time saver and are more efficient. It
/>/ should be easy for FreeBSD to make it easy to install the most recent
/>/ versions of all binary packages, its beyond belief they cannot pull
/>/ off such a simple ans straight forward, and basic part of any OS.  /









Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[SOLVED] 9-STABLE Gnome keyring cannot allocate secure memory

[Bas Smeelen]

On Mon, 30 Jan 2012 10:02:46 +0100
Bas Smeelen  wrote:

> On 01/30/2012 07:46 AM, Bas Smeelen wrote:
>
> > To be sure I deleted all ports and re-installed, but it still has
> > the same issue. The screen stays blank and on the console there is
> > a message from gnome keyring that it cannot allocate secure memory.
> > I did not find anything significant in src/UPDATING and I did not
> > update the ports-tree, because these versions were working fine.
> >
> > Any suggestions?
> > Thanks in advance.
> I guess I'll start digging through
> http://www.freebsd.org/gnome/index.html tonight.
> The strange thing is however that Gnome was running fine on 9-STABLE
> with hald and dbus and /proc until after the update.
> 
Solved. It seems like using a mix of packages and ports is not always a
good thing. To re-install all ports I used
portmaster -P `cat my-installed-ports-list`
However there is an entry in ports/UPDATING about x11/xcb-util which
requires a lot of ports to be rebuild and maybe the corresponding
packages were not updated?
Anyhow, I found out by installing fluxbox to have a wm for firefox and
claws-mail. The latter wouldn't start and led me to libxcb-aux.0.so
Sorry for the noise.


Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 9-STABLE Gnome keyring cannot allocate secure memory

[Bas Smeelen]

On 01/30/2012 07:46 AM, Bas Smeelen wrote:
> Hi,
>
> I have update my 9-STABLE system with csup from 21 jan. to 28 jan. last 
> weekend.
> After building and installing kernel and world and recompiling all ports the
> Gnome desktop does not start through anymore. This is with gmd after
> providing the password or without when just running startx as a normal user.
> It was all working fine before. The X window system works, it is just a
> Gnome issue.
> To be sure I deleted all ports and reinstalled, but it still has the same
> issue. The screen stays blank and on the console there is a message from
> gnome keyring that it cannot allocate secure memory.
> I did not find anything significant in src/UPDATING and I did not update the
> portstree, because these versions were working fine.
>
> Any suggestions?
> Thanks in advance.
I guess I'll start digging through http://www.freebsd.org/gnome/index.html
tonight.
The strange thing is however that Gnome was running fine on 9-STABLE with
hald and dbus and /proc until after the update.


Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

9-STABEL Gnome keyring cannot allocate secure memory

[Bas Smeelen]

Hi,

I have update my 9-STABLE system with csup from 21 jan. to 28 jan. last weekend.
After building and installing kernel and world and recompiling all ports the
Gnome desktop does not start through anymore. This is with gmd after
providing the password or without when just running startx as a normal user.
It was all working fine before. The X window system works, it is just a
Gnome issue.
To be sure I deleted all ports and reinstalled, but it still has the same
issue. The screen stays blank and on the console there is a message from
gnome keyring that it cannot allocate secure memory.
I did not find anything significant in src/UPDATING and I did not update the
portstree, because these versions were working fine.

Any suggestions?
Thanks in advance.


Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Goo lists to subscribe to hear quickly about vulns ? ( was: Re: FLAME - security advisories on the 23rd ? uncool idea is uncool)

[Bas Smeelen]

On topic, where do you guys subscribe to know of these vulns ahead of
  their release on the ML ?

security, stable and questions
it has been discussed here and there




Disclaimer: http://www.ose.nl/email
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FLAME - security advisories on the 23rd ? uncool idea is uncool

[Bas Smeelen]

> These vulnerabilities are known many days before in other distributions .

>Thank you very much .

>Mehmet Erol Sanliturk

you're right, these were discussed on the mailinglists also
_but_ FreeBSD is not a distribution
It is *a complete operating system*
Happy holidays


Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FLAME - security advisories on the 23rd ? uncool idea is uncool

[Bas Smeelen]

>Look, just a rant here.


>Who in *HELL* thought it would be a cool idea to release no less than
>FOUR security advisories today ?
What's the impact for your boxes?

>I mean, couldn't this have waited and remained undisclosed until monday ?
Best time to exploit is Christmas/holidays

>I for one do *NOT* relish the idea of updating 50+ boxes this evening
>and tomorrow !
updating 30 boxes right now

>Not to mention a whole lot of merchants and banks have toggled IT Freeze
>a few weeks ago, to ensure xmas shopping doesn't get disturbed by
>production changes.


>Seriously, this is just irritating.
If you don't use telnet, ftpd, dns, pam, then it's not a big problem

merry Christmas

Disclaimer: http://www.ose.nl/email

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"