Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)

[Chris Rees]

Hi people, (and thanks Alan for copying me in)

On 2018-12-17 01:42, Mark Linimon wrote:

On Sun, Dec 16, 2018 at 04:35:32PM -0500, Alex McKeever wrote:

I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC)
on my eMac.


I don't know of anyone else who has tried to run it.

The server-class ports on powerpc64 have been in good shape for several
years.  However, the desktop ports are lagging way behind.  For 
instance,
we are still working to get gnome and kde working properly.  Other 
desktop
environments are going to require more people to take up working on 
them.


I personally would like to see powerpc64 ports at (near-) parity with
amd64, but we have a lot of work to go yet.


I'm not sure if it's supported on PowerPC at all anyway by the 
developers (although obviously it used to work, perhaps not on FreeBSD 
though).


Was it a straightforward error?

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

Re: pkg issue after FreeBSD 11 upgrade

[Chris Rees]

Cassiano Peixoto wrote:

Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
with when I need to restart a service without upgrading? Reaper
functionnality is a trouble for many administrators who made meta ports to
manage their servers. I really think it could be a option to be
enabled/disabled. Can you see this possibility?

Thanks.

On Wed, Aug 30, 2017 at 9:59 AM, Baptiste Daroussin 
wrote:


On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote:

Hi Baptiste,

Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.

It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in
freebsd
kernel appeared in 10.2

Cron is just an example, I manage more than 50 FreeBSD servers, and I've
been using ports for years to update some configs and restart the service
on all of them. Many times I need to change nginx config, ldap, etc. I

just

need to restart the service.

HANDLE_RC_SCRIPTS=true in your pkg.conf and pkg will automatically restart
anything rc script provide once the package containing it is upgrading.

This is off by default because in many cases it is dangerous (database
upgrades,
dovecot like things upgrade etc). But if you know what you are doing it
does the
job.

Best regards,
Bapt





Hey,

I think you also want process supervision given your other comments.  
You can do this easily using daemon -P to run your scripts (but you'd 
need to rewrite the rc script...)


Or use runit or similar?  You could implement "runlevels" with that if 
that's REALLY what you want :)


Cheers,

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

Re: named fails two weeks ago unexpectedly

[Chris Rees]

On 27 January 2013 20:25,  jmore...@jmorenov.com.co wrote:
 Hi

 I was used FreeBSD 9.1 Release since December 2012, I usually use
 portsnap fetch  update and portmaster-a to keep my system updated.
 Two weeks ago unexpectedly named not worked. this is my case:

 Problem:
 root@server:/etc # /etc/rc.d/named start
 /etc/rc.d/named: ERROR: get_pidfile_from_conf: /etc/namedb/named.conf does
 not exist (named)
 Checking:
 root@server:/etc # ls -l /var/named/etc/namedb
 total 40
 drwxr-xr-x 2 bind wheel 512 Dec 4 04:32 dynamic
 drwxr-xr-x 2 root wheel 512 Dec 4 04:34 master
 -rw-r--r-- 1 bind wheel 15150 Jan 17 15:57 named.conf
 -rw-r--r-- 1 bind wheel 3135 Dec 4 04:34 named.root
 -rw--- 1 bind wheel 97 Dec 22 03:49 rndc.key
 drwxr-xr-x 2 bind wheel 512 Dec 4 04:32 slave
 drwxr-xr-x 2 bind wheel 512 Jan 27 13:25 working

 root@server:/root # cat /etc/defaults/rc.conf | grep named
 # named. It may be possible to run named in a sandbox, man security for
 named_enable=NO # Run named, the DNS server (or NO).
 named_program=/usr/sbin/named # Path to named, if you want a different
 one.
 named_conf=/etc/namedb/named.conf # Path to the configuration file
 #named_flags= # Use this for flags OTHER than -u and -c
 named_uid=bind # User to run named as
 named_chrootdir=/var/named # Chroot directory (or  not to auto-chroot
 it)
 named_chroot_autoupdate=YES # Automatically install/update chrooted
  # components of named. See /etc/rc.d/named.
 named_symlink_enable=YES # Symlink the chrooted pid file
 named_wait=NO # Wait for working name service before exiting
 named_wait_host=localhost # Hostname to check if named_wait is enabled
 named_auto_forward=NO # Set up forwarders from /etc/resolv.conf
 named_auto_forward_only=NO # Do forward only instead of forward
 first

 root@server:/root # cat /etc/rc.conf | grep named
 named_enable=YES

 Cause:
 FreeBSD 9.1 was running OK, but named failed for no apparent reason

 My Solution:
 root@server:/etc # ln -s /var/named/etc/namedb /etc/namedb
 root@server:/etc # /etc/rc.d/named start
 Starting named.

 I do not know what happened with named that it fails two weeks ago, any
 ideas ?

Necro-reply, sorry.

That symlink is there on all of my systems, you must have accidentally
removed it.

[crees@pegasus]~% grep -n namedb /usr/src/etc/Makefile
220:@if [ ! -e ${DESTDIR}/etc/namedb ]; then \
222:ln -s ../var/named/etc/namedb ${DESTDIR}/etc/namedb; \
226:${_+_}cd ${.CURDIR}/namedb; ${MAKE} install

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: wireless mouse on 9.1

[Chris Rees]

On 21 Apr 2013 17:19, Zoran Kolic zko...@sbb.rs wrote:

 I had usb switch to share keyboard and mouse for two nodes, of
 which freebsd worked flawlessly, but openbsd disconnected quite
 often and made a lot of antics in X. After all, I dismembered
 the configuration and now I have 2 kb-s and 2 mice. A lot of
 wires on the table. The plan would be to get not too expensive
 wireless mouse for freebsd node.
 Reading forums I found a lot of people having problem with
 those kind of mice. Could someone recommend one what is known
 to work on branch 9? For some reason I prefer logitech. And I
 assume that usb dongle works on hardware level and does not need
 anything to work?
 Best regards

Normally yes, wireless mice are the same driver wise.

Are both machines always on?  Have you thought of Synergy?

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: Ghosted logins in w/who

[Chris Rees]

On 10 April 2013 15:59,  damon...@mac.hush.com wrote:
 Got it. I'll double check to make sure everything was recompiled
 correctly. Thanks!
 Damon

While you're at it, I'll echo Ronald's concern-- make sure
/usr/include/utmp.h does NOT exist for you.

If it does, you must run make delete-old in /usr/src.

Chris

 On 4/10/2013 at 9:49 AM, Tom Evans  wrote:On Wed, Apr 10, 2013 at
 3:09 PM,   wrote:
 If I wipe the utmp file all the w/who content goes away, resets if
 you
 will. But in a matter of moments the problem reappears.. is this
 something that needs to be submitted as a bug report do you think?
 Thanks!
 Damon


 Hi Damon

 Fabian was explaining to you that utmp was replaced by utmpx.

 All programs in base that wrote to utmp now write to utmpx instead. If
 you still have programs not from base that write to utmp, you will get
 incorrect/crazy values reported - you must rebuild all tools that
 currently write to utmp so that they no longer do so.

 Cheers

 Tom
 ___
 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: What is the Right Way(™) to run X?

[Chris Rees]

On 17 Mar 2013 12:07, Daniel O'Connor dar...@dons.net.au wrote:

 Hi,
 I recently updated my 9.1-PRE system's ports and my previous X config now
results in no mouse (but the keyboard does work).

 I found that I needed to add the following..
 Section ServerFlags
 Option  AllowEmptyInput False
 EndSection

 I am pretty sure this used to be necessary, then wasn't, but now seems
required again.. From what I can see this means a 'startx' with no config
is broken which is a bit of a step backwards.

 BTW I have dbus  hald running.

Have you read http://www.wonkity.com/~wblock/docs/html/aei.html ?

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: lang/ruby19: ruby-1.9.3.392,1 is vulnerable: ** [check-vulnerable] Error code 1

[Chris Rees]

On 9 March 2013 09:37, Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
 I try to compile port lang/ruby19 and I always get on a FreeBSD
 9.1-STABLE box the following error message, which is obviously triggered
 by some port auditing - but I do not find the knob to switch it off.

 Can someone give a hint, please?

I guess you sent it to -stable by mistake-- the knob you need is
DISABLE_VULNERABILITIES=yes.

I'm sure I don't need to lecture you on Be careful with this :)

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: rc.d/sysctl fails to parse sysctl.conf

[Chris Rees]

On 27 February 2013 21:19, Andreas Nilsson andrn...@gmail.com wrote:
 Hello,

 I tried to get my sound working, and long story short: rc.d/sysctl parses
 sysctl.conf wrongly if there are sysctls of the form

 mib=val1=val2

 which is what you need for sound. For reference I needed/wanted

 dev.hdaa.4.nid25_config=as=1,seq=15
 dev.hdaa.4.nid31_config=as=1

 I believe the following patch would address the incorrect parsing:

 --- /etc/rc.d/sysctl.old2013-02-27 22:00:00.0 +0100
 +++ /etc/rc.d/sysctl2013-02-27 22:05:24.0 +0100
 @@ -26,7 +26,7 @@
 \#*|'')
 ;;
 *)
 -   mib=${var%=*}
 +   mib=${var%%=*}
 val=${var#*=}

 if current_value=`${SYSCTL} -n ${mib}
 2/dev/null`; then

I think that this is the right thing to do here.

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: Why can't gcc-4.2.1 build usable libreoffice?

[Chris Rees]

On 21 Feb 2013 02:23, Greg Miller greglmil...@gmail.com wrote:

 On 2/20/13, Matthias Andree matthias.and...@gmx.de wrote:
  What is your point, besides getting software from the museum to build
  stuff from the relative future?

 I can't speak for the OP, but I tried it because clang, gcc46, and
 gcc47 wouldn't produce a working executable at all for a long time
 (and continue to fail) on my 9.0 and 9.1 systems. There's been so much
 libreoffice breakage that I don't even bother reporting it or making
 much effort to fix it. I just reboot to Windows for the cases where I
 need a working libreoffice. I don't much care whether gcc 4.2 produces
 a working libreoffice; I just wish something did.

Try the packages Dominic Fandrey generated.

http://wiki.bsdforen.de/anwendungen/libreoffice_aus_inoffiziellen_paketen#freebsd_amd64i386_9183_kamikaze

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: Why can't gcc-4.2.1 build usable libreoffice?

[Chris Rees]

On 19 Feb 2013 14:23, Mikhail T. mi+t...@aldan.algebra.com wrote:

 18.02.2013 15:26, Chris Rees написав(ла):

 I'm sure you understand that our compiler in base is rather elderly,
 and that a project as insanely huge as Libreoffice is going to be
 highly sensitive to minute changes.

 No, Chris... I do not understand this wonderfully PR-esque response. See,
my understanding always was, the only possible reasons for a compiler to
produce a non-starting executable are:
 The code is buggy.
 The compiler is buggy.
 Both of the above.
 My question was, which is it?

My answer is that it is almost certainly (b).

You are welcome to ask upstream about it, but I doubt they would show much
interest in such an old compiler.

I think it's insanity that we still use this version for ports by default,
but never mind.

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: Why can't gcc-4.2.1 build usable libreoffice?

[Chris Rees]

Somehow attribution has been screwed here-- I will perhaps blame the
appalling Android Gmail app that I used to reply to an earlier
message.

On 19 February 2013 18:54, Mikhail T. mi+t...@aldan.algebra.com wrote:
snip
 These were, indeed, complaints, but not about the port not working after I 
 broke it. My complaint is that, though the port works out of the box, the 
 office@ maintainers have given up on the base compiler too easily -- comments 
 in the makefile make no mention of any bug-reports filed with anyone, for 
 example. It sure seems, no attempts were made to analyze the failures... I 
 don't think, such going with the flow is responsible and am afraid, the 
 inglorious days of building a special compiler just for the office will 
 return...

I'm sorry that you feel that the maintainers of Libreoffice have taken
an easy route; you can certainly show them how easy it is to do by
providing some patches/fixes, or working with upstream.  I don't see
how anyone on freebsd-stable@ will either be interested or
knowledgeable in Libreoffice internals.

 Maybe, it is just an omission -- and the particular shortcomings of the base 
 compiler (and/or the rest of the toolchain) are already known and documented 
 somewhere else?

 Licensing prevents us from updating gcc in the base.

 Licensing? Could you elaborate, which aspect of licensing you have in mind?

GPLv3.

 Maintainers of large opensource suites are likely to have little interest in 
 supporting
 LibreOffice's own Native_Build page makes no mention of a required compiler 
 version. Unless a compiler is documented to not support a required feature, 
 it is supposed to work. Thus, filing a bug-report with LibreOffice could've 
 been fruitful -- if it is the code, rather than the toolchain, that are at 
 fault...

 a buggy old compiler years after it has been obsoleted by newer versions.

 So, it is your conclusion too, that our base compiler is buggy -- and that 
 little can be done about it.

That is why we're replacing it with LLVM/Clang.

 Am I really the only one here disturbed by the fact, that the compilers 
 shipped as cc(1) and/or c++(1) in our favorite operating system's most recent 
 stable versions (9.1 and 8.3) are considered buggy? Not just old -- and thus 
 unable to process more modern language-standards/features, but buggy -- 
 processing those features incorrectly? There is certainly nothing in our 
 errata about it...

It is no secret that our base compiler is old.  What do you think
happens in newer versions, if not added features and bugfixes?

 On 19.02.2013 13:05, Adrian Chadd wrote:

 .. I think the compiler people just use the port as compiled with the
 compiler that is known to work with it, and move on.


 Such people would, perhaps, be even better served by an RPM-based system, 
 don't you think? But I don't think so -- the amount of OPTIONS in the port is 
 large, and a lot of people are likely to build their own. Not because they 
 like  it, but because they want a PostgreSQL driver or KDE4 (or GTK3) 
 interface or...

Irrelevant.  You choosing to compile with a different compiler adds no
value and can't be compared with a different interface.

Please fix it yourself, or talk to upstream.

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: Why can't gcc-4.2.1 build usable libreoffice?

[Chris Rees]

On 14 February 2013 13:57, Mikhail T. mi+t...@aldan.algebra.com wrote:
 Hello!

 I just finished building editors/libreoffice with gcc-4.2.1 -- had to
 edit the port's Makefile to prevent it from picking a different
 compiler. Everything built and installed, but libreoffice dies on
 start-up (right after flashing the splash-window):

 (gdb) where
 #0  0x00080596c1aa in cppu::__getTypeEntries ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #1  0x00080596c333 in cppu::__queryDeepNoXInterface ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #2  0x00080596d4a2 in cppu::WeakImplHelper_query ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #3  0x0008116f2b03 in
 
 cppu::WeakImplHelper1com::sun::star::lang::XEventListener::queryInterface
 ()
from /opt/lib/libreoffice/ure/lib/bootstrap.uno.so
 #4  0x000805970347 in
 cppu::OInterfaceContainerHelper::disposeAndClear ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #5  0x0008059705b2 in
 cppu::OMultiTypeInterfaceContainerHelper::disposeAndClear ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #6  0x00080593309f in cppu::OComponentHelper::dispose ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #7  0x000805963d00 in cppu::OFactoryComponentHelper::dispose ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #8  0x0008116ec296 in stoc_smgr::OServiceManager::disposing ()
 from /opt/lib/libreoffice/ure/lib/bootstrap.uno.so
 #9  0x00080596af05 in cppu::WeakComponentImplHelperBase::dispose ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #10 0x0008116e6244 in stoc_smgr::ORegistryServiceManager::dispose ()
from /opt/lib/libreoffice/ure/lib/bootstrap.uno.so
 #11 0x00080596a573 in cppu::WeakComponentImplHelperBase::release ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #12 0x0008059482f6 in (anonymous namespace)::createTypeRegistry ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #13 0x0008059487bf in
 cppu::defaultBootstrap_InitialComponentContext ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #14 0x000805948918 in
 cppu::defaultBootstrap_InitialComponentContext ()
from
 /opt/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3
 #15 0x00080212f883 in
 desktop::Desktop::InitApplicationServiceManager ()
from /opt/lib/libreoffice/program/libmergedlo.so
 #16 0x00080211f362 in desktop::Desktop::Init () from
 /opt/lib/libreoffice/program/libmergedlo.so
 #17 0x000807622113 in InitVCL () from
 /opt/lib/libreoffice/program/libvcllo.so
 #18 0x000807623151 in ImplSVMain () from
 /opt/lib/libreoffice/program/libvcllo.so
 #19 0x0008076232d5 in SVMain () from
 /opt/lib/libreoffice/program/libvcllo.so
 #20 0x00080214942e in soffice_main () from
 /opt/lib/libreoffice/program/libmergedlo.so
 #21 0x00400773 in main ()

 I do not blame the office@ team -- the port did not want to use
 gcc-4.2.1, I forced it to. But I'd like to know, what is wrong with the
 compiler shipped by FreeBSD-9.1 (and the only one, if WITHOUT_CLANG is
 defined), that prevents building a healthy libreoffice?

 Is there a bug fixed in gcc-4.6? Or is it some (incorrect) assumption
 made by libreoffice code? Thank you,

Hi Mikhail,

Libreoffice and openoffice have traditionally recommended that one use
binary packages instead of building it from scratch.

I'm sure you understand that our compiler in base is rather elderly,
and that a project as insanely huge as Libreoffice is going to be
highly sensitive to minute changes.  As a consequence, some very
narrow criteria are chosen to make maintenance of the port possible.

You are welcome to try with gcc-4.6, but the last I heard it will only
build with clang.  Your mileage may vary, please let us know of
success stories!

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: some issues with /usr/sbin/service

[Chris Rees]

On 16 Feb 2013 09:21, Jeremy Chadwick j...@koitsu.org wrote:
 I do not know who maintains the rc(8) and rc.subr(8) framework, but
 they've got their work cut out for them.

That's an interesting comment Care to guess at the obvious answer? :)

No-one actively maintains the infrastructure, though there are some
knowledgeable and generous individuals who will review patches sent to rc@.

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: some issues with /usr/sbin/service

[Chris Rees]

On 16 February 2013 17:05, Paul Mather p...@gromit.dlib.vt.edu wrote:
 On Feb 16, 2013, at 4:21 AM, Jeremy Chadwick wrote:

 On Sat, Feb 16, 2013 at 12:23:33PM +0400, Boris Samorodov wrote:
 16.02.2013 01:32, Jeremy Chadwick ??:

 Follow up -- I read Alfred's most recent mail.  Lo and behold, I find
 this in /var/log/messages (but such did not come to my terminal):

 Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: $svnserve_enable 
 is not set properly - see rc.conf(5).
 Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: $smartd_enable is 
 not set properly - see rc.conf(5).
 Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: $rsyncd_enable is 
 not set properly - see rc.conf(5).
 Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: 
 $htcacheclean_enable is not set properly - see rc.conf(5).
 Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: $fetchmail_enable 
 is not set properly - see rc.conf(5).

 Cute.  Agreed -- this is unacceptable on two levels (as I see it):

 1) These messages should be going to stdout or stderr in some way, so
 honestly logger(8) should be called with the -s flag (IMO).

 Fully agreed here.

 It turns out logger -s has no effect, just like how the echo 12
 statements in warn() and err() have no effect either (these should be
 outputting the warnings in question to stderr) -- see rc.subr's source
 for what I'm referring to.

 Gary and I have been discussing this off-list and the reason has been
 found: service(8) has this code in it:

   checkyesno $rcvar 2/dev/null  echo $file

 This explains why there's no warn() or err() output on the terminal --
 it's being redirected to /dev/null prior.

 I do not know who maintains the rc(8) and rc.subr(8) framework, but
 they've got their work cut out for them.

 (Note: the echo statements in warn() and err() could be replaced with
 logger -s as I said; this would allow the echo 12 to be removed)

 2) These messages should not be displayed at all (i.e. lack of an
 xxx_enable variable should imply xxx_enable=no).

 I see this message as one more level of supervision.

 If undefined at /etc/make.conf the value of xxx_enable is no from the
 system's POV (i.e. the service is not strarted). From the
 admininstrators's POV the port was installed BUT is not used. It's up
 to admininstrator whether it's OK or not -- just let him remind.

 I believe the point you're trying to make is that the warning in
 question should 'act as a reminder to the administrator that they need
 to set xxx_enable=yes in rc.conf'.

 If not: please explain if you could what you mean, because I don't
 understand.

 If so: I strongly disagree with this method of approach, as what you've
 proposed is a borderline straw man argument.

 Reminding the admin to set xxx_enable is presently done inside most
 ports' pkg-message.  IMO, this should really be done inside bsd.port.mk
 when USE_RC_SUBR is used, emitting a message during install that says
 something like:

 To enable the xxx service, please add the following to /etc/rc.conf:
 xxx_enable=yes

 Of course, I don't know if this would work for packages.

 The current message for missing xxx_enable in rc.conf is this:

 WARNING: $xxx_enable is not set properly - see rc.conf(5).

 The message is entirely misleading for this specific situation; it isn't
 reminding an administrator -- if anything it's confusing them (thread
 is case in point).  If we're going to cater to ignorance, then the
 message should reflect the situation.

 Thus IMO, this is what ***should*** happen:

 Definition in rc.confBehaviour/result
 ---  ---
 myprog_enable=yes  emit no warnings, service should run
 myprog_enable=no   emit no warnings, service should not run
 myprog_enable=abc123   emit a warning,   service should not run
 no definition  emit no warnings, service should not run


 I think case 4 (no definition) is a case where a warning should be 
 emitted because it is arguably not immediately apparent what will actually 
 happen if no definition is present.  In the case of services in the base OS 
 it is well-defined: every service should have an explicit default in 
 /etc/defaults/rc.conf that you can easily consult to know definitively what 
 will happen with that service.  (If it doesn't, that is a bug, IMHO.)

 For ports, the case is not so clear.  There is a general trend for the port 
 rc.d script to default its respective xxx_enable explicitly to NO.  But it 
 is not a universal rule that no definition = default to NO.  The 
 net/avahi-app port, for example, doesn't default to NO if xxx_enable is not 
 set: it defaults to whatever the gnome_enable setting is defined to be.

With few exceptions, it should be considered a rule that ports rc
scripts contain:

: ${xxx_enable=no}

to avoid this.  If you see any ports that don't define the _enable
variable at all, they are wrong and need fixing.

Chris

Re: some issues with /usr/sbin/service

[Chris Rees]

On 16 February 2013 18:08, Gary Palmer gpal...@freebsd.org wrote:
 On Sat, Feb 16, 2013 at 05:38:56PM +, Chris Rees wrote:
 On 16 February 2013 17:05, Paul Mather p...@gromit.dlib.vt.edu wrote:
  On Feb 16, 2013, at 4:21 AM, Jeremy Chadwick wrote:
 
  On Sat, Feb 16, 2013 at 12:23:33PM +0400, Boris Samorodov wrote:
  16.02.2013 01:32, Jeremy Chadwick ??:
 
  Follow up -- I read Alfred's most recent mail.  Lo and behold, I find
  this in /var/log/messages (but such did not come to my terminal):
 
  Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: 
  $svnserve_enable is not set properly - see rc.conf(5).
  Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: $smartd_enable 
  is not set properly - see rc.conf(5).
  Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: $rsyncd_enable 
  is not set properly - see rc.conf(5).
  Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: 
  $htcacheclean_enable is not set properly - see rc.conf(5).
  Feb 15 13:26:20 icarus jdc: /usr/sbin/service: WARNING: 
  $fetchmail_enable is not set properly - see rc.conf(5).
 
  Cute.  Agreed -- this is unacceptable on two levels (as I see it):
 
  1) These messages should be going to stdout or stderr in some way, so
  honestly logger(8) should be called with the -s flag (IMO).
 
  Fully agreed here.
 
  It turns out logger -s has no effect, just like how the echo 12
  statements in warn() and err() have no effect either (these should be
  outputting the warnings in question to stderr) -- see rc.subr's source
  for what I'm referring to.
 
  Gary and I have been discussing this off-list and the reason has been
  found: service(8) has this code in it:
 
checkyesno $rcvar 2/dev/null  echo $file
 
  This explains why there's no warn() or err() output on the terminal --
  it's being redirected to /dev/null prior.
 
  I do not know who maintains the rc(8) and rc.subr(8) framework, but
  they've got their work cut out for them.
 
  (Note: the echo statements in warn() and err() could be replaced with
  logger -s as I said; this would allow the echo 12 to be removed)
 
  2) These messages should not be displayed at all (i.e. lack of an
  xxx_enable variable should imply xxx_enable=no).
 
  I see this message as one more level of supervision.
 
  If undefined at /etc/make.conf the value of xxx_enable is no from the
  system's POV (i.e. the service is not strarted). From the
  admininstrators's POV the port was installed BUT is not used. It's up
  to admininstrator whether it's OK or not -- just let him remind.
 
  I believe the point you're trying to make is that the warning in
  question should 'act as a reminder to the administrator that they need
  to set xxx_enable=yes in rc.conf'.
 
  If not: please explain if you could what you mean, because I don't
  understand.
 
  If so: I strongly disagree with this method of approach, as what you've
  proposed is a borderline straw man argument.
 
  Reminding the admin to set xxx_enable is presently done inside most
  ports' pkg-message.  IMO, this should really be done inside bsd.port.mk
  when USE_RC_SUBR is used, emitting a message during install that says
  something like:
 
  To enable the xxx service, please add the following to /etc/rc.conf:
  xxx_enable=yes
 
  Of course, I don't know if this would work for packages.
 
  The current message for missing xxx_enable in rc.conf is this:
 
  WARNING: $xxx_enable is not set properly - see rc.conf(5).
 
  The message is entirely misleading for this specific situation; it isn't
  reminding an administrator -- if anything it's confusing them (thread
  is case in point).  If we're going to cater to ignorance, then the
  message should reflect the situation.
 
  Thus IMO, this is what ***should*** happen:
 
  Definition in rc.confBehaviour/result
  ---  ---
  myprog_enable=yes  emit no warnings, service should run
  myprog_enable=no   emit no warnings, service should not run
  myprog_enable=abc123   emit a warning,   service should not run
  no definition  emit no warnings, service should not run
 
 
  I think case 4 (no definition) is a case where a warning should be 
  emitted because it is arguably not immediately apparent what will actually 
  happen if no definition is present.  In the case of services in the base 
  OS it is well-defined: every service should have an explicit default in 
  /etc/defaults/rc.conf that you can easily consult to know definitively 
  what will happen with that service.  (If it doesn't, that is a bug, IMHO.)
 
  For ports, the case is not so clear.  There is a general trend for the 
  port rc.d script to default its respective xxx_enable explicitly to NO.  
  But it is not a universal rule that no definition = default to NO.  
  The net/avahi-app port, for example, doesn't default to NO if xxx_enable 
  is not set: it defaults to whatever the gnome_enable setting is defined to 
  be.

 With few

Re: setfacl man page states d=delete_child and D=delete

[Chris Rees]

On 8 February 2013 20:42, Edward Tomasz Napierała tr...@freebsd.org wrote:
 Wiadomość napisana przez Eitan Adler w dniu 8 lut 2013, o godz. 20:05:
 On 8 February 2013 13:46, Edward Tomasz Napierała tr...@freebsd.org wrote:
 Wiadomość napisana przez Harald Schmalzbauer w dniu 8 lut 2013, o godz. 
 16:08:
 Hello,

 I think there's a confusion in the man page setfacl(1).

 In my tests, D means delete_child and d delete; like it's true
 for other NFSv4 implementations. But manpage tells the other way around.

 Fixed the man page, thanks!

 There are more errors.  Please see the PR:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=docs/174433

 The 'S' issue was fixed earlier.  Thanks for pointing out this PR.

 I _really_ wish we had a bugtracker that would allow me to subscribe
 to keywords such as acl, growfs or iscsi.  ;-/

Have a look in /g/hubgnats/gnats-aa/incoming-PRs/bin/lookups.txt on
hub.freebsd.org.

Just don't be too greedy with your keywords ;)

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: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

[Chris Rees]

On 3 February 2013 03:55, Kimmo Paasiala kpaas...@gmail.com wrote:
 On Sun, Feb 3, 2013 at 4:06 AM, Mark Linimon lini...@lonesome.com wrote:
 On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote:
 I'm not sure why I'm being jumped on in this weeks old report of a
 now-fixed problem.

 I'm sorry, I'm that far behind in email.  I did not realize the problem
 had already been solved.

 More often than not the problem is simply thrown over the fence for
 the ports team to deal with.

 mcl

 There is no PR yet with my fix and therefor no commit to ports tree
 that would fix the problem. I'll file a PR soon (TM).

The problem was in base, and is fixed there.

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: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9

[Chris Rees]

On 3 February 2013 17:15, Stefan Bethke s...@lassitu.de wrote:

 Am 03.02.2013 um 10:57 schrieb Chris Rees cr...@freebsd.org:

 On 3 February 2013 03:55, Kimmo Paasiala kpaas...@gmail.com wrote:

 There is no PR yet with my fix and therefor no commit to ports tree
 that would fix the problem. I'll file a PR soon (TM).

 The problem was in base, and is fixed there.

 Huh? With -current r246283, I still get a segfault from sudo unless I have 
 Kimmo's patch.

 Is there some confusion about which problem is addressed by Kimmo's patch?


Hm, perhaps it might be necessary then.

Kimmo, please would you submit the patch you had as a PR?  I'm sure
Wesley would appreciate the hint.

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: svn - but smaller?

[Chris Rees]

On 25 Jan 2013 13:39, Ian Smith smi...@nimnet.asn.au wrote:

 On Thu, 24 Jan 2013 00:57:17 -0800, 'Jeremy Chadwick' wrote:

   On Thu, Jan 24, 2013 at 06:34:33PM +1100, Dewayne wrote:
The objective is to return to a base build of FreeBSD that performs
the expected task of being able to pull source, without having to
acquire a port.  Regardless of our individual solutions/workarounds,
the task is to pull and maintain source.
   
Is the discussion going to result in something like svn-lite that
enters into the /usr/src/contrib along with the responsibilities
associated with maintaining it?  And then we need to take into
consideration of being overwriting the base svn with a full svn
package, if required by the user/admin.
 [..]
I build svn from ports with all options off except for:
ENHANCED_KEYWORD P4_STYLE_MARKERS STATIC which results in a 4.2MB svn
program. Suites me but doesn't address the underlying problem - and I
don't think that the plan is to make FreeBSD dependent upon the ports
system (for subversion)

 [..]
   As for your last line:
  
   FreeBSD is already dependent upon Subversion.  This has been the case
   for quite some time, but has only recently (as an indirect result of
the
   security incident) become forced upon users/administrators of FreeBSD.
   The entire project is presently managed/maintained under Subversion.
   The Handbook now documents that if you want to pull down src/ you need
   to install Subversion.  If you want to pull down ports/ you can use
   portsnap and waste lots of /var space, hoping that the portsnap mirrors
   are up to date, and a bunch of other hullabaloo... or you could just
use
   Subversion and be done with it.
  
   There is no more cvsup.  There is no more csup.  There is no more cvs.

 I'm trying to work out exactly when support for checking out 9-STABLE
 CVS sources - and I'm only talking about system sources here - will end?

 Peter Wemm (cc'd) writes in https://wiki.freebsd.org/CvsIsDeprecated,
 last edited 2013-01-22:

   3. For FreeBSD 9-stable, 8-stable and 7-stable, we will be attempting
 to continue updates through the exporter the official support
 end-of-life for last release on the branch at the time of writing
 (November 16th, 2012).
   * This means, updates will be maintained on a best effort
 basis until 9.0-RELEASE, 8.3-RELEASE, 7.4-RELEASE are no longer
 supported.
   * This notice pre-dates 9.1-RELEASE, and the release of 9.1
 will not extend the lifetime of RELENG_9 branch exporter.
   * This is not a commitment to operate the services, it will
 only be done on a best effort basis. If serious problems develop or
 usage dies down significantly we may accelerate its end-of-life.

 But after kerfuffle about 9.1-RELEASE branch sources not (then) being
 available via c{v,}sup, Bjoern Zeeb wrote on Sept 18th 2012 in

http://lists.freebsd.org/pipermail/freebsd-stable/2012-September/069600.html
 RELENG_9_1 is now exported the CVS as well and will be for as long as
 things will be exported to CVS.  Other posts around that time clearly
 said that CVS source access would remain for the lifetime of 9-STABLE.

 Could someone please clarify this situation?

 As others have suggested, an SVN package that could be installed with a
 static build and run dependency-free binary would help ease the pain for
 those looking specifically at updating 9.x or 8.x sources to -STABLE as
 a directly usable csup replacement, preferably on install media but at
 least easily fetchable as a package?  I find portsnap fine for ports.

I've just created devel/subversion-static that will be available by pkg_add
once the package builds are back.

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: Spontaneous reboots on Intel i5 and FreeBSD 9.0

[Chris Rees]

On 25 Jan 2013 10:27, Marin Atanasov Nikolov dna...@gmail.com wrote:

 On Fri, Jan 25, 2013 at 12:12 PM, Bob Bishop r...@gid.co.uk wrote:

  Hi,
 
  On 25 Jan 2013, at 09:29, 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.
  
   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
 
  Have you done anything to rule out the machine's power supply?
 
 

 Hi,

 Yes, it's a brand new one.

 Regards,
 Marin



   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.

I used to get daily(ish) lockups with my server.

I guess the drives are mirrored?  Try yanking one for a bit (leave the
computer on) and try it in another computer.

I tried that, and only one of them failed, proving a bad drive.  Seagate
replaced it.

This was 2TB, 16G RAM.

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: svn - but smaller?

[Chris Rees]

On 25 Jan 2013 18:28, Dimitry Andric d...@freebsd.org wrote:

 On 2013-01-25 16:41, Chris Rees wrote:
 ...

 I've just created devel/subversion-static that will be available by
pkg_add
 once the package builds are back.


 Thanks, but the port does not link on head, due to a problem in apr:

 /usr/local/lib/libapr-1.a(apr_snprintf.o): In function `apr_vformatter':
 /usr/ports/devel/apr1/work/apr-1.4.6/strings/apr_snprintf.c:1023:
undefined reference to `isnan'

 The issue is that apr-1-config --libs does not list -lm.  Any idea how
 to correct that?

That's a question for Lev really, since it applies equally to
devel/subversion.

I'll fix it tomorrow when I'm back at the keyboard unless Lev fixes it
first.

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: svn - but smaller?

[Chris Rees]

On 24 Jan 2013 14:33, John Mehr j...@visi.com wrote:

 For testing against svn.freebsd.org -- this is pull only? So you only
 need read permissions on svn.freebsd.org?  That's fine: the SVN
 repository is open to public access and you can just use it without
 asking permission.  Although I'd use one of the mirror sites listed in
 the handbook rather than svn.freebsd.org directly.


 Correct.  I just want to give the folks that administer the servers a
heads-up that there's going to be a lot more entries in their log files
coming from me -- unless it's an undocumented feature of the svn protocol,
md5 signatures for files are not included in directory requests and I need
to issue a get-file command for each and every file to get their md5
signatures in order to determine which local files need an update.  :(

It'd probably be faster for you to use svnsync to get a local mirror of the
repo.

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: svn - but smaller?

[Chris Rees]

On 23 Jan 2013 21:55, Jeremy Chadwick j...@koitsu.org wrote:

 (Please keep me CC'd as I'm not subscribed to the list)

  Great idea;
 
  http://www.bayofrum.net/~crees/patches/svn-static.diff
 
  Lev, do you mind if I commit this?  I haven't touched the subversion
  port, but it'll have you as maintainer :)
 
  If you prefer, I don't mind maintaining this.

 As I understand it this patch would induce the build cluster to build
 subversion-static.tbz (eventually) and put it on the package servers.

 So what happens when one of the underlying dependencies that you've
 included statically (those would possibly be: Oracle/SleepyCat DB, APR,
 expat, sqlite3, neon, gettext, and iconv) have security holes or major
 bugs found/addressed in them?

The package would be updated on the next build, since a dependency changed.

 As I understand it -- based on history -- the packages on the FTP
 servers get updated whenever.  My other post shows some haven't been
 updated in months (and yes I'm aware of the security incident).

That's why, so for normal use it's irrelevant.

 So how long would a key piece of software containing insecure
 statically-linked libraries be on the FTP servers?

No longer than any other package.

 How would the port maintainer(s) even know the libraries/software which
 subversion is dependent upon had been updated, thus requiring a new
 subversion package to be pushed out to the package servers ASAP (i.e.
 immediately, not days, weeks, or months)?

 My point: ports have always been best-effort.  They are advertised
 vehemently throughout everything FreeBSD as being third-party software
 and therefore infinite list of caveats.  Yet now critical pieces to
 FreeBSD development (and now end-users too, as a result of using the
 security incident to push SVN) rely upon something in ports.  That's
 quite a conundrum the Project has created for itself, an ouroboros of
 sorts.

This is not intended as general use for everyone, it's intended as a
shortcut when building a new machine or anything else.  I'll put a big
warning in pkg message :)

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: svn - but smaller?

[Chris Rees]

On 23 Jan 2013 15:37, Oliver Brandmueller o...@e-gitt.net wrote:

 On Wed, Jan 23, 2013 at 04:12:22PM +0100, Frank Staals wrote:
  This type of question has been asked quite a few times recently. At this
  point there is no svn version of csup, however there were people working
  on it (or at least: there is a svnsup project). For details please
  search recent ports or questions mailing list archives. As far as I know
  there is also no alternative svn-client.

 Pointer to svnsup is fine; it seems I just missed to the first hint.

  I'm kind of surprised for the need of this though. Why not simply use
  portsnap if you are not actively developing ports?

 Well, for ports this is mostly fine, though on several places I prefer
 to use csup (or svn now) even for ports, since I maintain quite a set of
 local patches - this sometimes gives problems together with potsnap.
 Where this is neede, I have a shared ports tree anyway, so the whole svn
 setup is only needed in one machine.

 But my main concern is the system sources anyway. freebsd-update is not
 feasible for me, as described in the original post.

The single binaries inside the archives at [1] may help you out.  I built
them fairly recently, so they should be up to date (ish), and they should
be fine on 9+.  Just untar and use.

Chris

[1] http://www.bayofrum.net/svn-static/
___
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: svn - but smaller?

[Chris Rees]

On 23 January 2013 20:41, Isaac (.ike) Levy i...@blackskyresearch.net wrote:
 On Jan 23, 2013, at 2:17 PM, Emanuel Haupt wrote:
 Oliver Brandmueller o...@e-gitt.net wrote:
 Hi,

 in ancient times there was cvsup. cvsup was a PITA if you wanted (or
 needed) to install it via ports, the only reasonable way was to use
 pkg_add for that if you didn't want to pollute your system with
 otherwise unneeded software.

 Then there came csup. Small, in the base. You could install FreeBSD
 and the first task (for me and my environment) was often to simply
 csup to -STABLE (or a known good version of that) and to build an
 up-to-date and customised system. Like tayloring make.conf and
 src.conf to my needs and leave out most of the stuff I don't need on
 my system and in the kernel. Software and drivers that aren't there
 can't fail and won't be a security problem.

 Times have been changing, we're now up to svn. svn is far more modern
 than cvs and there are pretty good reasons to use it.

 However, I either overlook something important or we are now at the
 point we had with cvsup in the early days: The software I need to
 (source-)update the system doens't come with the base and installing
 svn is a PITA. It pulls in a whole lot of dependencies, at the time
 being in FBSD-9.1-R I cannot even pkg_add -r subversion out of the
 box. And in the end I have my system polluted with software and
 libraries I don't really need in many cases for anything else.

 So, is there some alternative small svn client, that leaves a
 drastically smaller footprint probably somewhere around, probably
 even in the ports or is there anything I'm missing? The current
 situaion for me is a bit annoying. From the user's or admin's point
 of view at least. I didn't even see an option in svn to not build the
 server components, which would probably already help to make things
 smaller?

 Thanx,
  Oliver

 On Jan 23, 2013, at 2:09 PM, Peter Wemm wrote:
 On Wed, Jan 23, 2013 at 9:05 AM, Isaac (.ike) Levy
 i...@blackskyresearch.net wrote:

 1) License.  Many of SVN's dependencies will never be available in the 
 FreeBSD source.
 While this is totally OK for development, SVN is 3rd party software, this 
 is unacceptable to force as 'the' respected path for OS source builds.

 Don't confuse the excessive ports default settings as dependencies.
 You can make a quite mean and lean svn client.  I did a 100%
 BSD-license-compatible src/contrib/svn style proof-of-concept back
 when we were planning what to do.  Things like gdbm and bdb are not
 required and are license contamination that we don't need.  But that's
 the fault of the port, not a fundamental property of using svn.


 On Jan 23, 2013, at 2:17 PM, Emanuel Haupt wrote:
 devel/subversion already has an option to build a static version. A
 solution could be to create a stub port (devel/subversion-static)
 similar to:

 shells/bash-devel
 shells/bash-static-devel

 dns/ldns
 dns/py-ldns

 That way the package build cluster would create a package of the static
 version which wouldn't pull in any runtime dependencies.

 Emanuel

 Peter, this work sounds great, and sounds like it would make a great stub 
 port itself!
 I'd love to see whatever you have remaining from the proof-of-concept work, 
 to perhaps help expand it into 'devel/subversion-lite' or 
 'devel/subversion-static' ?  I'd happily use it for development.

 --
 However, SVN for development use is not what the point, this thread is about 
 using, administrating, and maintaining FreeBSD systems- not about development 
 process.  And in that case, SVN is still a fairly massive toolset for the 
 simple task of fetching REL, STABLE, or CURRENT:

   Source for SVN-alone:55M
   Source for FreeBSD 9.1:  746M

 That's still over 7% of the size of the entire OS.

 I believe it's not at all necessary to have anything except the base FreeBSD 
 OS, to update/install FreeBSD.

 --
 A NYC*BUG list user posted this reminder, we've been here before:

 Deja-vu…  This reminds me of cvsup+modula-3.

 http://www.mavetju.org/mail/view_message.php?list=freebsd-currentid=209027


 I'll keep hacking on our shell utility, and will post the PR to this thread.

Your shell utility appears to fetch a new tarball of the entire repo
each time?  That's very bandwidth-unfriendly for the Project's servers
as well as yours...

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: svn - but smaller?

[Chris Rees]

On 23 January 2013 19:17, Emanuel Haupt eha...@freebsd.org wrote:
 devel/subversion already has an option to build a static version. A
 solution could be to create a stub port (devel/subversion-static)
 similar to:

 shells/bash-devel
 shells/bash-static-devel

 dns/ldns
 dns/py-ldns

Great idea;

http://www.bayofrum.net/~crees/patches/svn-static.diff

Lev, do you mind if I commit this?  I haven't touched the subversion
port, but it'll have you as maintainer :)

If you prefer, I don't mind maintaining this.

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: svn - but smaller?

[Chris Rees]

On 23 Jan 2013 21:45, Lev Serebryakov l...@freebsd.org wrote:

 Hello, Chris.
 You wrote 24 января 2013 г., 1:25:44:

 CR Great idea;
 CR http://www.bayofrum.net/~crees/patches/svn-static.diff
  I think, adding SERF or NEON (what is smaller) is good idea, or this
 build will lack http support, and it could be surprise to user, as
 http access method is well-know and useful in case of corporate
 firewalls.

 CR Lev, do you mind if I commit this?  I haven't touched the subversion
 CR port, but it'll have you as maintainer :)
  Ok :)

I'll check which makes a smaller package- thanks for the quick approval.

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: Does / Is anyone maintaining CVS for FreeBSD?

[Chris Rees]

On 4 Jan 2013 09:25, Erich Dollansky erichsfreebsdl...@alogt.com wrote:

 Hi,

 On Fri, 4 Jan 2013 09:38:05 +0100
 Patrick M. Hausen hau...@punkt.de wrote:

  Am 03.01.2013 um 19:21 schrieb Matthew Seaman
  m.sea...@infracaninophile.co.uk:
   On 03/01/2013 17:48, Patrick M. Hausen wrote:
   I'm a bit reluctant to installing svn on every system that needs
   source updates. Are there more lightweight ways?
  
   freebsd-update(8)
  
   which is what 'make update' will run by default and in the absence
   of any configuration to use other mechanisms.
 
 
  Sorry for being too terse in my first post. Seems like I should have
  a closer look at freebsd-update. Of course I have lines like this
  in my /etc/make.conf on each machine that I update from sources:

 no matter, you showed how deeply this integration was up to the point
 that you did not notice it anymore.

 You also showed that there was a reliable infrastructure available
 which served you for years without any problems.

 What will happen after the jump into the cold water?

Is there a problem with using freebsd-update for your sources too?

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: Does / Is anyone maintaining CVS for FreeBSD?

[Chris Rees]

On 2 Jan 2013 11:08, Thomas Mueller muelle...@insightbb.com wrote:

  There has been some discussion about removing CVS from the base system
  now it is no longer used.  No concensus was reached, so it's not going
  away immediately (and would not be removed from 9.x or earlier branches
  in any case).

  CVS is (and will remain) available in ports (devel/cvs).

  --
  Peter Jeremy

 Now CVS may be no longer used for FreeBSD servers, but NetBSD servers
still use it for system source and pkgsrc.

 I like to keep up with NetBSD 6-STABLE and HEAD, maybe a final try for
NetBSD 5.2, and that includes pkgsrc.

 If somebody could persuade NetBSD to switch to svn, I would surely not
quarrel.

To clarify, no-one wants to remove CVS completely, the suggestion was to
move it out of the base system.

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: Does / Is anyone maintaining CVS for FreeBSD?

[Chris Rees]

On 2 January 2013 16:05, Derek Kulinski tak...@takeda.tk wrote:
 Eitan Adler li...@eitanadler.com wrote:

On 2 January 2013 06:26, Chris Rees utis...@gmail.com wrote:
 To clarify, no-one wants to remove CVS completely, the suggestion was
to
 move it out of the base system.

As the developer responsible for this:

CVS will be removed from base.  It already exists as a port in
devel/cvs

 Will svn be added to the base? Not long ago I run into an issue when trying 
 to downgrade my system to 9.0.

 After I noticed how majority of ports were broken due to changes in the libc 
 I decided to back out by fetching 9.1 release just to learn that svn does not 
 work as well. There were a lot of dependencies I decided to use portupgrade 
 which required me to recompile ruby. After that it was a lot of compiling 
 (for example Apache because apr was broken). Having svn in the base would 
 save tons of time in my situation.

It certainly wouldn't, it would mean that instead of only building
when you installed the port, it would build with every buildworld :)

http://svnweb.FreeBSD.org/base/user/des/svnsup/

needs fixing if you're feeling brave.  It won't be easy, however.

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: Does / Is anyone maintaining CVS for FreeBSD?

[Chris Rees]

On 31 Dec 2012 19:52, Chris H chris#@1command.com wrote:

 Greetings,
  The following is hijacked from another thread, which prompts me to
 post this question:

  On Mon, Dec 31, 2012 at 11:49:06AM -0600, Stephen Montgomery-Smith
wrote:
  (Not sure if this is the right mailing list, but here goes.)
 
 
  -doc@ is a better choice.
 
  Last night I did a csup to retrieve the whole cvs repository.  I
noticed
  that huge numbers of files in doc and www have been deleted.  Is this
  intentional, or is it the svn to cvs program not working properly?  And
  if it is the latter, are there plans to restore it?
 
 
  We are not exporting docs from SVN to CVS.  There are no plans to do so.

 After more that 25yrs of enjoying *BSD, and all it has to offer. I find
 myself ever so resistant to change -- what with all the maintenance
scripts,
 and procedures I've created/accumulated over the years. As I'm guessing
I'm
 not the only one feeling this way, I'm wondering if there is still a CVS
 that's still current, that I might be able to mirror, and maintain, moving
 forward? Perhaps this is all folly, but this subject has been bugging me
 for some time, and reading this thread prompted me to attempt to address
 it.

 Thank you for all your time, and consideration.

I'm sorry, but the exporter scripts were always a stopgap.

Help is available for updating your scripts to use Subversion, please feel
free to ask.

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: Does / Is anyone maintaining CVS for FreeBSD?

[Chris Rees]

On 31 Dec 2012 20:40, Chris H chris#@1command.com wrote:

 Greetings Chris, and thank you for your reply.
  On 31 Dec 2012 19:52, Chris H chris#@1command.com wrote:
 
  Greetings,
   The following is hijacked from another thread, which prompts me to
  post this question:
 
   On Mon, Dec 31, 2012 at 11:49:06AM -0600, Stephen Montgomery-Smith
  wrote:
   (Not sure if this is the right mailing list, but here goes.)
  
  
   -doc@ is a better choice.
  
   Last night I did a csup to retrieve the whole cvs repository.  I
  noticed
   that huge numbers of files in doc and www have been deleted.  Is
this
   intentional, or is it the svn to cvs program not working properly?
 And
   if it is the latter, are there plans to restore it?
  
  
   We are not exporting docs from SVN to CVS.  There are no plans to do
so.
 
  After more that 25yrs of enjoying *BSD, and all it has to offer. I find
  myself ever so resistant to change -- what with all the maintenance
  scripts,
  and procedures I've created/accumulated over the years. As I'm guessing
  I'm
  not the only one feeling this way, I'm wondering if there is still a
CVS
  that's still current, that I might be able to mirror, and maintain,
moving
  forward? Perhaps this is all folly, but this subject has been bugging
me
  for some time, and reading this thread prompted me to attempt to
address
  it.
 
  Thank you for all your time, and consideration.
 
  I'm sorry, but the exporter scripts were always a stopgap.

 That's what I was afraid I would hear. Recently, I was informed by SF.NET,
 that my account would be upgraded, and all the projects I have, which all
 use CVS, would be upgraded to SVN (which renders them useless). When I
 asked why, they told me because CVS was so old. To which I stated:
 Indeed, CVS is _quite_ old, and so is TCP/IP. Yet no one can seem live
 without it.
 Sigh...
 IM(NS)HO; SVN is an inferior RCS created so Windows users wouldn't feel
 left out.
 Are there _any_ CVS servers/trunks/tree's left? If so, how _current_ are
 they?

As far as I know, no FreeBSD CVS repos are current.

 Thanks again for taking the time to reply, Chris.

You can run your own CVS server should you wish; it's not that hard; there
are instructions at [1] if you want something more fully-featured.

I promise you that there are many good reasons to switch to something
better; I was an avid CVS user at one point, but I sure wouldn't go back
now.

Chris

[1] http://www.freebsd.org/doc/en/articles/cvs-freebsd/article.html
___
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: Post 9.1 stable file system problems

[Chris Rees]

On 1 Jan 2013 00:01, Dominic Fandrey kamik...@bsdforen.de wrote:

 I have a Tinderbox that I just updated to the current RELENG_9.
 Following the update build times for packages have increased by a
 factor between 5 and 20. I.e. I have packages that used to build in
 5 minutes and now take an hour.

 I'm suspecting the file system ever since I saw that the majority of CPU
 load was caused by ls when I looked at top (more than 2 minutes of CPU
 time were counted that moment). The majority of the time most of the CPU
 load is caused by bsdtar, pkg_add, qmake-qt4, etc. Without exception
 tools that access a lot of files.

 The file system on which packages are built is nullfs mounted from
 an async mounted UFS. I turned async off, to no avail.

 /usr/src/UPDATING says that there were nullfs optimisations. So I
 think this is where the problem originates. I might hack the tinderbox to
 use 'ln -s' or set it up for NFS to verify this.

Is your kernel newer than the Jail?  The converse causes problems.

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: 9.1 minimal ram requirements

[Chris Rees]

On 23 Dec 2012 06:40, Adrian Chadd adr...@freebsd.org wrote:

 Hi guys,

 Would someone please file a PR for this? This is a huge unused
 allocation of memory for something that honestly likely shouldn't have
 been included by default in GENERIC.

 I've cc'ed ken on a reply to this. Hopefully after the holidays he can
 chime in and figure out what's going on.

 Maybe just disabling it in GENERIC moving forward is enough - chances
 are it'll be fine being just a module.

Oh gods... Please let's just make it an erratum notice at this stage!

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: What is negative group permissions? (Re: narawntapu security run output)

[Chris Rees]

On 23 December 2012 16:23, Barney Wolff bar...@databus.com wrote:

[moving Barney's top post down]

 On Sun, Dec 23, 2012 at 10:51:24AM -0500, Mikhail T. wrote:
 On 23.12.2012 03:05, Charlie Root wrote:
  Checking negative group permissions:
8903027 -rw--w-r--  1 miwww794277 Oct 23 07:47:45 2007 
  /home/mi/public_html/syb/order/download.log
 Hello!

 The above started to appear in the daily security run output after I
 upgraded to 9.1. I don't understand, what this check is doing or why the
 above file is reported -- what's abnormal (warning-worthy) about
 allowing the web-server to write to, but not read a file? I did it on
 purpose to keep all files associated with a project together, but
 without inadvertently serving some of them...

 The r for other means that you have not accomplished your goal.  It makes
 no sense to have group with less permission that other, so the script is
 warning of a misconfiguration.

Not at all; anything in www group can't read the file, which is what
Mikhail wants to do.

If he has thought about the consequences of exactly what this means;
i.e. normal users can read-only, www group can write-only, mi can
read/write, then he can ignore the warning.

Negative group permissions are sometimes useful, that's why they're allowed.

 I understand, I can explicitly disable it, but I'm curious... Whether it
 should run by default or not, what is the purpose of it?

They involve a lot of thought to get right, as well as chmod g-w on
something where you probably meant chmod go-w is a disastrous but
(perhaps) common error.

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: No more torrents.....

[Chris Rees]

On 19 Dec 2012 09:47, Volodymyr Kostyrko c.kw...@gmail.com wrote:

 19.12.2012 01:22, Peter Wemm:

 I would be very much be willing to assist with seeding if we make dht
 torrent files available from my nodes located in downtown Los Angeles
 for west-coast and APAC network presence.

 as an aside:
 I have been running libtorrent/rtorrent for a bit and it seems like a
 pretty decent platform for building on.  having said that - I am not a
 security researcher and would be keen to hear if libtorrent/rotrrent
 suffers from these similar issues?


 Oh wait, I told a lie.  It wasn't py-bittornado we used.. it was
 rtorrent.  Thanks for prompting that.

 I have no concerns with rtorrent except that it was a curses beastie.
 It was something we had to manually start up after a machine reboot
 until we did some evil scripts with screen.


 The ports contain at least two torrent clients that can daemonize:
transmission and btpd. At least first one surely knows about DHT.

Transmission definitely does, and it is built to be lightweight.

Would clusteradm be interested on that?

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: No more torrents.....

[Chris Rees]

On 18 Dec 2012 19:44, Eitan Adler li...@eitanadler.com wrote:

 On 18 December 2012 03:59, Willem Jan Withagen w...@digiware.nl wrote:

  So what is the reason for this?

 The software used to seed the torrents was horribly insecure.   This
 was found *prior* to the security incident.

What software?

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: confirm that csup is still usable fos the new 9.1

[Chris Rees]

On 26 Nov 2012 08:12, Perry Hutchison per...@pluto.rain.com wrote:

 Kevin Oberman kob6...@gmail.com wrote:

  ... don't bet that csup and cvs will be around long ...
  It's really time to get away from CVS and I suspect
  it will be going away sooner than had been planned.

 Once csup goes away, how will a base-only system update
 the sources, e.g. to follow a security branch?

freebsd-update will update your sources for you.

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: confirm that csup is still usable fos the new 9.1

[Chris Rees]

On 18 Nov 2012 09:49, Andrea Venturoli m...@netfence.it wrote:

 On 11/17/12 21:04, Kevin Oberman wrote:

 Looks like everything is back up again.
 Thanks for the good work.


 Yes, but don't bet that csup and cvs will be around long.


 I'm aware of this and I'm (adimttedly slowly) moving away from csup.




 The outage
 was the result of an intrusion into core FreeBSD systems. Please read
 the posting at http://www.freebsd.org/news/2012-compromise.html.


 Read that.




 It's
 really time to get away from CVS and I suspect it will be going away
 sooner than had been planned. I notice that no response has confirmed
 whether it will be available for 9.1, probably because the security
 team is still evaluating the situation.


 Simply out of curiosity, I wonder why csup/cvsup/cvs are less secure than
alternatives, say SVN.
 Why would this compromise be impossible without cvs?
 Any link on this?

Not impossible, but because of the way cvs mirrors are propagated any
tampering is also synced.  Subversion propagation only pulls commits, which
is why it's faster and also tampering in the history is not propagated.

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: nomenclature for conf files

[Chris Rees]

On 12 Nov 2012 05:20, Kurt Buff kurt.b...@gmail.com wrote:

 On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic zko...@sbb.rs wrote:
  It might sound stupid, but I'd like to know if there's
  any difference. Are those 3 line the same?
 
  WITH_KMS=YES
  WITH_KMS=YES
  WITH_KMS=yes

 With regard to their use in /etc/rc.conf, no, absolutely not.

 In general, from my experience, only the second one will work.

 This might, or might not, be true for other uses, but rc.conf is
 pretty picky about this.

All three are fine in make.conf and rc.conf

The issue with rc.conf is when people put spaces around the = sign.

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: nomenclature for conf files

[Chris Rees]

On 12 Nov 2012 08:55, Paul Schenkeveld free...@psconsult.nl wrote:

 On Mon, Nov 12, 2012 at 08:29:27AM +, Chris Rees wrote:
  On 12 Nov 2012 05:20, Kurt Buff kurt.b...@gmail.com wrote:
  
   On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic zko...@sbb.rs wrote:
It might sound stupid, but I'd like to know if there's
any difference. Are those 3 line the same?
   
WITH_KMS=YES
WITH_KMS=YES
WITH_KMS=yes
  
   With regard to their use in /etc/rc.conf, no, absolutely not.
  
   In general, from my experience, only the second one will work.
  
   This might, or might not, be true for other uses, but rc.conf is
   pretty picky about this.
 
  All three are fine in make.conf and rc.conf
 
  The issue with rc.conf is when people put spaces around the = sign.
 
  Chris

 Indeed /etc/rc (executed by /bin/sh) accepts all three forms because
 quotes are optional in /bin/sh and /etc/rc.subr (sourced by /etc/rc)
 matches the value against [Yy][Ee][Ss]|[Tt][Rr][Uu][Ee]|[Oo][Nn]|1.

 Also, the FreeBSD makefiles and sources test all WITH_* variables with
 .ifdef or #ifdef so the value doesn't matter and can even be empty.
 White space around the = is permitted too (but not in rc.conf!).

 However, things are different when people start using tools to maintain
 rc.conf/make.conf.  If not written with the above in mind, these tools
 may have problems parsing these files.

 It's good practice to be consistent and use a canonical form that
 matches the documentation or example files as this is probably the
 syntax that is guarenteed to not confuse such tools.  In other words:
 Be conservative in what you send [write], liberal in what you accept.

Doesn't sound like a very good tool if it can't handle quoting and capital
letters, but I accept the principle.

Quotes in Makefiles are often harmful, so good practice IMO is to only use
them when necessary.

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: nomenclature for conf files

[Chris Rees]

On 12 Nov 2012 15:35, Kurt Buff kurt.b...@gmail.com wrote:

 On Mon, Nov 12, 2012 at 12:29 AM, Chris Rees utis...@gmail.com wrote:
 
  On 12 Nov 2012 05:20, Kurt Buff kurt.b...@gmail.com wrote:
 
  On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic zko...@sbb.rs wrote:
   It might sound stupid, but I'd like to know if there's
   any difference. Are those 3 line the same?
  
   WITH_KMS=YES
   WITH_KMS=YES
   WITH_KMS=yes
 
  With regard to their use in /etc/rc.conf, no, absolutely not.
 
  In general, from my experience, only the second one will work.
 
  This might, or might not, be true for other uses, but rc.conf is
  pretty picky about this.
 
  All three are fine in make.conf and rc.conf
 
  The issue with rc.conf is when people put spaces around the = sign.
 
  Chris

 This has not been my experience - but I will experiment soon and see
 if I can verify.

Anything that complains about any of those syntaxes is a bug.  Please file
a PR if you find any examples.

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: [releng_9_1 tinderbox] failure on powerpc64/powerpc

[Chris Rees]

On 4 Nov 2012 20:12, George Mitchell george+free...@m5p.com wrote:

 On 11/04/12 14:59, FreeBSD Tinderbox wrote:

 TB --- 2012-11-04 19:53:34 - tinderbox 2.9 running on
freebsd-stable.sentex.ca
 TB --- 2012-11-04 19:53:34 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE
FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012
mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server  amd64
 TB --- 2012-11-04 19:53:34 - starting RELENG_9_1 tinderbox run for
powerpc64/powerpc
 TB --- 2012-11-04 19:53:34 - cleaning the object tree
 TB --- 2012-11-04 19:53:34 - checking out /src from svn://
svn.freebsd.org/base/releng/9.1
 TB --- 2012-11-04 19:53:34 - cd /tinderbox/RELENG_9_1/powerpc64/powerpc
 TB --- 2012-11-04 19:53:34 - /usr/local/bin/svn cleanup /src
 TB --- 2012-11-04 19:54:02 - /usr/local/bin/svn update /src
 TB --- 2012-11-04 19:54:02 - WARNING: /usr/local/bin/svn returned exit
code  1
 TB --- 2012-11-04 19:54:02 - WARNING: sleeping 30 s and retrying...
 TB --- 2012-11-04 19:54:32 - /usr/local/bin/svn update /src
 TB --- 2012-11-04 19:54:32 - WARNING: /usr/local/bin/svn returned exit
code  1
 TB --- 2012-11-04 19:54:32 - WARNING: sleeping 60 s and retrying...
 TB --- 2012-11-04 19:55:32 - /usr/local/bin/svn update /src
 TB --- 2012-11-04 19:55:32 - WARNING: /usr/local/bin/svn returned exit
code  1
 TB --- 2012-11-04 19:55:32 - WARNING: sleeping 90 s and retrying...
 TB --- 2012-11-04 19:57:02 - /usr/local/bin/svn update /src
 TB --- 2012-11-04 19:57:02 - WARNING: /usr/local/bin/svn returned exit
code  1
 TB --- 2012-11-04 19:57:02 - WARNING: sleeping 120 s and retrying...
 TB --- 2012-11-04 19:59:02 - /usr/local/bin/svn update /src
 TB --- 2012-11-04 19:59:02 - WARNING: /usr/local/bin/svn returned exit
code  1
 TB --- 2012-11-04 19:59:02 - ERROR: unable to check out the source tree
 TB --- 2012-11-04 19:59:02 - 3.92 user 4.38 system 328.82 real



http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9_1-powerpc64-powerpc.full
 ___
 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


 Gosh, I'm SO looking forward to depending on svn instead of csup for
 software updates.
The subversion server is being moved; a one off thing.

No major drama here.

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: Tinderbox spam

[Chris Rees]

On 24 Sep 2012 10:23, Dag-Erling Smørgrav d...@des.no wrote:

 I recently switched the machine that builds 7 and 8 from csup to svn.
 Unfortunately, it seems to have trouble maintaining a stable connection
 to svn.freebsd.org.  I'm testing a patch that makes it retry up to three
 times before giving up, so hopefully the spurious failures will go away
 soon.

I've found that svn:// seems to be more aggressive with rate-limiting if
that's what it does.

Have you tried using http:// ?

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: Tinderbox spam

[Chris Rees]

On 24 Sep 2012 12:26, Dag-Erling Smørgrav d...@des.no wrote:

 Chris Rees utis...@gmail.com writes:
  Have you tried using http:// ?

 Both should work, but svn is significantly faster.

Yes, that's why I tried it instead, but my point is that you may need to
sleep a bit between tries; if svn is faster, you're more likely to hit any
rate limit.

I could be wrong, but I can't see any other explanation for the weird
failures we've both been seeing.

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: Clang as default compiler

[Chris Rees]

On 12 Sep 2012 07:19, Christer Solskogen christer.solsko...@gmail.com
wrote:

 On Wed, Sep 12, 2012 at 8:04 AM, Mark Linimon lini...@lonesome.com
wrote:

  For most of the failures, we are already aware of them, as a result of
  our periodic runs.  So, just filing a PR to say broken on clang
doesn't
  really help us all that much.
 

 I disagree. Just a tiny bit ;-)
 If the PR says that USE_GCC=4.2 works as a workaround, it helps.

We don't want thousands of PRs duplicating the information from a simple
list of failures.

Any can be fixed in this way.

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: FreeBSD 9.1-RC1 Available...

[Chris Rees]

On 28/08/2012, Arno J. Klaassen a...@heho.snv.jussieu.fr wrote:
 Jim Pingle li...@pingle.org writes:

 On 8/23/2012 11:43 AM, Ian Lepore wrote:
 On Thu, 2012-08-23 at 11:17 -0400, Ken Menzel wrote:

 I found two good primers:
 http://mebsd.com/configure-freebsd-servers/update-freebsd-source-tree-using-subversion-svn.html
 http://www.freebsd.org/doc/en/articles/committers-guide/article.html#SUBVERSION-PRIMER

 The second primer in the committer handbook seems to indicate that it
 is difficult to run an SVN mirror. This appears to me to be the
 biggest drawback.  I have been using CVS and perforce for years,  but
 subversion is new to me.

 It may be difficult to run an svn mirror that allows you to commit
 locally and get those changes back to the project, but running a
 read-only mirror is trivial.  The script I run nightly from cron to sync
 my local mirror is:

 #!/bin/sh
 #
 # svnsync to pull in changes from FreeBSD to my local mirror.
 #
 svnsync sync file:///local/vc/svn/base

 I can't remember how I initially created and populated the mirror, but
 it's likely I grabbed a snapshot of the mirror at work and brought it
 home on a thumb drive (just to avoid initial network DL time).

 I spent a little time today setting up an SVN mirror after reading this
 thread and wrote up a how-to for those looking to do the same.

 http://www.pingle.org/2012/08/24/freebsd-svn-mirror

 Comments/Flames/Corrections welcome...

 thanx; works out of the box for me (using the svnserve_enable path).

 That said : I glanced at a diff of a stable/8 checkout both from
 /home/ncvs repo and new /home/freebsd-svn one, and saw a (maybe well-known
 ..)
 'feature' :

   diff ./src/contrib/amd/include/am_defs.h
 /raid1/bsd/8/src/contrib/amd/include/am_defs.h

  42c42
   * $FreeBSD: stable/8/contrib/amd/include/am_defs.h 174299 2007-12-05
 16:03:52Z obrien $
 ---
  * $FreeBSD: src/contrib/amd/include/am_defs.h,v 1.15.2.1 2009/08/03
 08:13:06 kensmith Exp $


 I wondered why the date (and commiter ...) in the expansion were
 different (from the svn log ):

   
   r196045 | kensmith | 2009-08-03 10:13:06 +0200 (Mon, 03 Aug 2009) | 4
   lines

   Copy head to stable/8 as part of 8.0 Release cycle.

   Approved by:re (Implicit)

   
   r174299 | obrien | 2007-12-05 17:03:52 +0100 (Wed, 05 Dec 2007) | 3
   lines


 So the 'Copy head' chain does not update the $FreeBSD tag, whereas the
 consequent svn to cvs chain does.

That's because CVS does not consider tagging/branching a commit,
whereas Subversion does.

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: ports /databases/postgresql92-server beta 3

[Chris Rees]

On 10 August 2012 12:28, Marcelo Gondim gon...@bsdinfo.com.br wrote:
 Em 10/08/2012 08:10, Denis Granato escreveu:

 Good morning guys.

 I installed sucessfully a postgresql 9.2 beta 2 last month in
 databases/postgresql92-server

 But yesterday in another server ai update my ports tree and this change to
 postgresql 9.3
 but the make install clean can fetch the file
 postgresql-9.2beta3.tar.bz2
   (file not found)

 Any knows the port maintainer?

 regards
 ___
 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

 Hi Denis,

 Try to use portmaster to resolve this problem with the parameter -o.
 Example:

 portmaster -o databases/postgresql92-server atual_packet_installed

 This goes change atual_packet_installed for databases/postgresql92-server

S'ok, I've just fixed it.  The URL was wrong in the port, sorry.

Patch at 
http://svnweb.freebsd.org/ports/head/databases/postgresql92-server/Makefile?view=patchr1=302226r2=302384pathrev=302384

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: lsof needs update

[Chris Rees]

On 21 July 2012 10:36, Daniel Braniss da...@cs.huji.ac.il wrote:
 hi, lsof on freebsd 9.1:
 COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
 ntpd1707 root  cwd unknown file
 system type: newnfs
 ntpd1707 root  rtd unknown file
 system type: newnfs
 ntpd1707 root  txt unknown file
 system type: newnfs
 ntpd1707 root  txt unknown file
 system type: newnfs
 ntpd1707 root  txt unknown file
 system type: newnfs
 ntpd1707 root  txt unknown file
 system type: newnfs
 ntpd1707 root  txt unknown file
 system type: newnfs
 ntpd1707 root  txt unknown file
 system type: newnfs
 ntpd1707 root  txt unknown file
 system type: newnfs
 ntpd1707 root  txt unknown file
 system type: newnfs

Did you recompile lsof when upgrading?

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: lsof needs update

[Chris Rees]

On 21 July 2012 18:04, Daniel Braniss da...@cs.huji.ac.il wrote:
 On 21 July 2012 10:36, Daniel Braniss da...@cs.huji.ac.il wrote:
  hi, lsof on freebsd 9.1:
  COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
  ntpd1707 root  cwd unknown file
  system type: newnfs
  ntpd1707 root  rtd unknown file
  system type: newnfs
  ntpd1707 root  txt unknown file
  system type: newnfs
  ntpd1707 root  txt unknown file
  system type: newnfs
  ntpd1707 root  txt unknown file
  system type: newnfs
  ntpd1707 root  txt unknown file
  system type: newnfs
  ntpd1707 root  txt unknown file
  system type: newnfs
  ntpd1707 root  txt unknown file
  system type: newnfs
  ntpd1707 root  txt unknown file
  system type: newnfs
  ntpd1707 root  txt unknown file
  system type: newnfs

 Did you recompile lsof when upgrading?

 Chris
 I compiled it last week, but just in case I did it again, samr result

 lsof -v
 lsof version information:
 revision: 4.86
 latest revision: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/
 latest FAQ: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ
 latest man page: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_man
 constructed: Sat Jul 21 20:00:36 IDT 2012
 constructed by and on: root@pe-00
 compiler: cc
 compiler flags: -pipe -fno-strict-aliasing -DHASEFFNLINK=i_effnlink 
 -DHASF_VNODE -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_VM_MEMATTR_T 
 -DHAS_CDEV2PRIV -DHAS_NO_SI_UDEV -DHAS_SYS_SX_H -DHAS_ZFS -DHAS_V_LOCKF 
 -DHAS_LOCKF_ENTRY -DHAS_NO_6PORT -DHAS_NO_6PPCB -DNEEDS_BOOLEAN_T 
 -DFREEBSDV=9000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHASUTMPX 
 -DHAS_STRFTIME -DLSOF_VSTR=9.1-PRERELEASE -I/usr/src/sys -O2
 loader flags: -L./lib -llsof  -lkvm
 system info: FreeBSD pe-00 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #6: Fri 
 Jul 20 17:41:41 IDT 2012 danny@rnd:/home/obj/rnd/r+d/stable/9/sys/HUJI amd64
 Anyone can list all files.
 /dev warnings are enabled.
 Kernel ID check is enabled.
 Device cache file read-only paths:
 Named via -D: none
 Named in environment variable LSOFDEVCACHE: none
 Personal path format (HASPERSDC): %h/%p.lsof_%L
 Modified personal path environment variable: LSOFPERSDCPATH
 LSOFPERSDCPATH value: none
 Personal path: /root/.lsof_pe-00
 Device cache file write paths:
 Named via -D: none
 Named in environment variable LSOFDEVCACHE: none
 Personal path format (HASPERSDC): %h/%p.lsof_%L
 Modified personal path environment variable: LSOFPERSDCPATH
 LSOFPERSDCPATH value: none
 Personal path: /root/.lsof_pe-00

OK, I've copied in the lsof port maintainer too then, so he knows.

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: FreeBSD not so free anymore ? Long live FreeBSD...

[Chris Rees]

On 15 June 2012 18:53, Etienne Robillard animelo...@gmail.com wrote:
 On 06/15/2012 01:08 PM, Jerry wrote:

 Skype 4.0 for Linux is now available. Is there any possibility of
 getting it ported to FreeBSD? The latest version in ports is only
 2.x.



 Why not? Thinking FreeBSD could become immune to remote exploits is absurd.

 So without much efforts  I can guess ports like Skype will become more
 widespread now that FreeBSD has gived up on network security, preferring to
 announce critical security vulnerabilities once the exploit has been
 confirmed without any warnings.

 A good reason to stop using this bloated OS if you ask me and use
 something more respectful to their users base relaying on STABLE for
 stability reasons...


New versions of Skype require ALSA.  This is at their insistence.

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: Why Are You NOT Using FreeBSD ?

[Chris Rees]

On Jun 12, 2012 10:48 AM, H h...@hm.net.br wrote:

 On Monday 11 June 2012 20:59 Chuck Swiger wrote:
  Hi, Dave--
 
  On Jun 11, 2012, at 4:35 PM, Dave Hayes wrote:
  [ ... ]
 
   Do I have this wrong? Anyone see a problem with this picture?
   What can we do to just upgrade in a safe fashion when we want to?
 
  Two things help tremendously:
 
  #1: Have working backups.  If you run into a problem, roll back the
  system to a working state.  If you cannot restore a working system
  easily, fix your backup solution until you can rollback easily.
 
  #2: Have a package-building box and test builds before installing
  new package builds to other boxes.  Your downtime for upgrades
  to the rest of your boxes become minimized.
 
  Regards,


 of course it helps ...

 but please do not forget that most people just want their desktop up to
date
 and have a working kde (or any other) environment

 I believe the ports tree simply must? should? be seen as it is, partially
good
 working, and partially a jorney to very dark places , depends on which
ports
 and how many  you have installed

 in any case it is for somebody who knows what he does and can find his
way out,
 or is courageous, a normal desktop user probably is not able to upgrade
kde4
 properly and ends up with an unusable machine



 On Monday 11 June 2012 20:20 Dave Hayes wrote:
  Rainer Duffner rai...@ultra-secure.de writes:
   Sometimes, options only make sense in context of the selection of
   options of other ports and it thus may no be easily explainable in one
   line.
 
  I don't understand Are you saying this is a reason not to document what
  these options do?


 both here deepen the lead into the dark theory


 On Sunday 10 June 2012 14:10 O. Hartmann wrote:
  portmaster does even more damage. Sometimed a port reels in some newly
  updates, a port gets deleted. if on of the to be updated prerquisits
  fail, the port in question isn't there anymore.


 this is caused of ports tree's install script maior logic failure, BTW by
 portmaster AND portupgrade and it happens quite often,

 as already commented, nobody sits in front of the screen and watch the
compile
 process so this problems go under at first sight

 I think, correcting this, would help a lot and may solve a lot of existing
 [hidden] problems.

 I see only one way, having a complete package collection for easy upgrade

 most of you do not like it, but you must look at the competitors, Fedoras
 upgrade system works, user do not need the newest features and none of
them
 are essential for a desktop to work properly

 of course the package collection needs then something similar to
portversion,
 but not based on ports tree versions, in order to find available updates

 who then wants to customize or learn or who dares, can use the ports tree

You have hit the nail right on the head there, and that is the intention
with pkgng.  Please feel free to have a go with it using the beta repos :)

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: Why Are You NOT Using FreeBSD ?

[Chris Rees]

On 10 June 2012 11:12, Martin Sugioarto mar...@sugioarto.com wrote:
 Am Sat, 09 Jun 2012 21:09:09 +0700
 schrieb Adam Strohl adams-free...@ateamsystems.com:

 I get the feeling people are updating their ports tree and then
 recompiling/reinstalling everything just because and then are
 complaining when one thing breaks (its the only thing I can think of).

 Hi.

 But it does not need to break. Sometimes it would be enough just to
 test if the port compiles before committing it (I'm talking about
 libreoffice here which is broken). Some people rely on some essential
 ports. I can understand that porters are not Gods and make errors, but
 they should be fixed within hours, when they have been found on
 important ports.

 I mean, ports collection is sure great and this is one of the aspects
 why I am using FreeBSD, but at the moment FreeBSD is losing strength
 here, in my opinion.

Er... people always test their commits.  Sometimes edge cases will
creep in, such as the libreoffice failure which was due to different
configurations, but to suggest that the commit wasn't tested is quite
frankly insulting-- it built on a clean system perfectly well.

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: Why Are You NOT Using FreeBSD ?

[Chris Rees]

On 10 June 2012 11:51, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
 On 06/10/12 12:37, Chris Rees wrote:
 On 10 June 2012 11:12, Martin Sugioarto mar...@sugioarto.com wrote:
 Am Sat, 09 Jun 2012 21:09:09 +0700
 schrieb Adam Strohl adams-free...@ateamsystems.com:

 I get the feeling people are updating their ports tree and then
 recompiling/reinstalling everything just because and then are
 complaining when one thing breaks (its the only thing I can think of).

 Hi.

 But it does not need to break. Sometimes it would be enough just to
 test if the port compiles before committing it (I'm talking about
 libreoffice here which is broken). Some people rely on some essential
 ports. I can understand that porters are not Gods and make errors, but
 they should be fixed within hours, when they have been found on
 important ports.

 I mean, ports collection is sure great and this is one of the aspects
 why I am using FreeBSD, but at the moment FreeBSD is losing strength
 here, in my opinion.

 Er... people always test their commits.  Sometimes edge cases will
 creep in, such as the libreoffice failure which was due to different
 configurations, but to suggest that the commit wasn't tested is quite
 frankly insulting-- it built on a clean system perfectly well.

 Chris

 In do not see any insulting statement! Why those exaggerations?

 Sometimes it would be enough just to
 test if the port compiles before committing it (I'm talking about
 libreoffice here which is broken)
___
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: WAS: Re: Why Are You NOT Using FreeBSD ? New: port annoyance LibreOffice

[Chris Rees]

On 10 June 2012 18:10, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
 On 06/10/12 17:43, John Merryweather Cooper wrote:
 On 06/10/12 09:54, Martin Sugioarto wrote:
 Am Sun, 10 Jun 2012 11:37:09 +0100
 schrieb Chris Reescr...@freebsd.org:

 Er... people always test their commits.  Sometimes edge cases will
 creep in, such as the libreoffice failure which was due to different
 configurations, but to suggest that the commit wasn't tested is quite
 frankly insulting-- it built on a clean system perfectly well.
 Hi,

 I don't mean to insult anyone. As I have already told, I am really
 thankful that people invest their precious time into updating the ports
 collection.

 Whatever clean system means. It is surely not the default case that
 someone has got a freshly installed set of ports.

 Among all the default problems with ports, libreoffice[1] adds to the
 group of annoyances[2] at the moment. I don't know when I have seen
 portmaster -ad run through successfully last time. I need more and
 more -x options to exclude ports which fail to build.

 [1] german/libreoffice and libreoffice fails all the time in
 (LOCALIZED_LANG is set to de):

 Module 'lingucomponent' delivered successfully. 12 files copied, 2
 files unchanged

 ---
          Oh dear - something failed during the build - sorry !
    For more help with debugging build errors, please see the section in:
              http://wiki.documentfoundation.org/Development

    internal build errors:

 ERROR: error 65280 occurred while
 making
 /usr/workdir-ports/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj


   it seems that the error is inside 'vcl', please re-run build
   inside this module to isolate the error and/or test your fix:
 ---


 Whatever this tries to tell me. I don't get it. This is a completely
 useless error message for me.

 Not even in german/libreoffice. i try to build the standard version and
 I receive the same error.

 I can fix this by doing what the buildsystem suggests, but then I have a
 stop in sfx2 and others and it ends up in some module called tail_,
 where the build never ends when performing the repair as suggested. I
 had once a box running all the night looping building in this folder.


 [2] The default annoyances are for example:

 - After updating perl, php or whatever, it makes sense to enforce
    updating the modules that belong to these ports. I've seen 100x the
    same message that p5-XML-Parser does not work and know what it means,
    but this should be resolved by the port system. I mean, when you
    update perl, the perl modules won't work anymore. This is totally
    clear and it makes sense to update them first before going on.

 I can confirm that. I fixed that for me by portmaster p5- in case
 p5-SAX-XXX failed.

There's an UPDATING message written for that very purpose.


 - When specifying WITHOUT_X11 the ports should respect this and not try
    to pull in the X11 variants of ports. I regularly see some ports
    pulling ImageMagick instead of the already installed
    ImageMagick-nox11. I still do not fully understand what is going on
    with WITHOUT_GNOME, but I'll try to figure it out later. But I am
    quite sure that some ports pull in unneeded Gnome dependencies.

 - Ports are being marked as interactive and stop the update process. The
    idea behind portmaster was (earlier) to avoid interactive building of
    ports and ask all the needed questions, before the builds start. I
    mean, earlier, I could get out and enjoy some coffee outdoors, now I
    have to sit at the keyboard. This is unacceptable! ;)

 portmaster does even more damage. Sometimed a port reels in some newly
 updates, a port gets deleted. if on of the to be updated prerquisits
 fail, the port in question isn't there anymore.

 portmaster fails quite often in oberwriting remnant files. If a port
 gets corrupted by accident, like graphics/netpbm, One need to delete all
 binaries manually from /usr/local/bin, otherwise the installation fails.

 Somehow I wish to have a brute force knob to overwrite everything in a
 brutal way.

FORCE_PKG_REGISTER.


 - It would be nice to have a mechanism that tells you that your perl,
    mysql or whatever is not the default version anymore and you should
    consider updating to the default (and recommended) port.


 Martin

 From /etc/defaults/periodic.conf:

 # 400.status-pkg
 weekly_status_pkg_enable=YES                # Find out-of-date pkgs
 pkg_version=pkg_version                           # Use this program
 pkg_version_index=/usr/ports/INDEX-9      # Use this index file

 There's an override script in ports-mgmt/portupgrade that uses it's
 database, also.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send 

Re: Why Are You NOT Using FreeBSD?

[Chris Rees]

On Jun 6, 2012 3:38 AM, Erich erichfreebsdl...@ovitrap.com wrote:

 Hi,

 On 05 June 2012 7:13:47 Mark Linimon wrote:
  On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote:
   But is this true for apache only or for the whole ports tree?
 
  Entire tree.

 my problem with this is that the documentation states something very
different:

 From the handbook at the location where beginners will look for it:

 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html

 'Which version(s) of them do you want?

 With CVSup, you can receive virtually any version of the sources that
ever existed. That is possible because the cvsupd server works directly
from the CVS repository, which contains all of the versions. You specify
which one of them you want using the tag= and date= value fields.

 Warning: Be very careful to specify any tag= fields correctly. Some tags
are valid only for certain collections of files. If you specify an
incorrect or misspelled tag, CVSup will delete files which you probably do
not want deleted. In particular, use only tag=. for the ports-*
collections.'

 I think that this states very clearly that there are no tags.


No it doesn't. It states clearly that you shouldn't use tags unless you
know what you are doing, as several of us have explained more than once.

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: Why Are You NOT Using FreeBSD?

[Chris Rees]

On 6 June 2012 14:12, Erich erichfreebsdl...@ovitrap.com wrote:
 Hi,

 On 06 June 2012 8:48:10 Chris Rees wrote:
 On Jun 6, 2012 3:38 AM, Erich erichfreebsdl...@ovitrap.com wrote:
 

 No it doesn't. It states clearly that you shouldn't use tags unless you
 know what you are doing, as several of us have explained more than once.

 is my English really this bad?

 From the handbook:

 '. In particular, use only tag=. for the ports-* collections.'

Your English is fine, but being told to use tag=. != tag=. is the
only tag that exists.

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: Why Are You NOT Using FreeBSD?

[Chris Rees]

On Jun 5, 2012 3:07 AM, Erich erichfreebsdl...@ovitrap.com wrote:

 Hi,

 On 05 June 2012 11:24:25 Mark Andrews wrote:
 

  Version tagging is just a convient way to get a snapshot at a
  particular point in time unless you create branches that are them

 we do not ask for more. There should be only one difference to a
snapshot. As snapshot has a date. No matter in what state the ports tree
was, it is in that state in the ports tree. If user - especially the one
not so fit in this aspect - want to use a snapshot, it will be difficult to
impossible to figure out which one they need.

 If version numbers would be introduced, it would be ok to use the version
number of the FreeBSD and have only version available which reflect the
release version of the ports tree.

 People here want to make always a perfect system. People like me want to
have some small things in there available with a click.

 As the ports trees are there anyway, only the direct link to the snapshot
of that day or a version number in the ports tree would be needed to make
this available for people who just want to use FreeBSD.

 Please note, I do not want any extra work spend here to make this
perfect. I only want a simple way to fall back to a big net which is not
that old from which the user can restart.


I and most others will purposely refuse to document this in any official
capacity, but I'll give you a hint.

Look for the date tag in man csup.

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: Why Are You NOT Using FreeBSD ?

[Chris Rees]

On Jun 4, 2012 9:50 AM, Dave Hayes d...@jetcafe.org wrote:

 Mark Linimon lini...@lonesome.com writes:
  On Sun, Jun 03, 2012 at 07:24:11PM -0700, Dave Hayes wrote:
  I see features and pkgng and things being offered up as solutions...
  these are all well and good, but in my opinion more comprehensive
  documentation and support in these areas would do more good than pkgng.
  IMHO pkgng and optionsng are necessary, but not sufficient, to solve
  our current problems.

 Optionsng is nice, but lacking in documentation. Is it too much to ask
 port maintainers to write a bit more documentation on the options they
 are providing?

Where are you looking? I updated the Porter's Handbook- is there something
missing?

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: Why Are You NOT Using FreeBSD?

[Chris Rees]

On 3 June 2012 21:55, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
 On 06/03/12 15:29, Erich wrote:
 Hi,

 On 03 June 2012 PM 5:14:10 Adam Strohl wrote:
 On 6/3/2012 11:14, Erich wrote:
 What I really do not understand in this whole discussion is very simple. 
 Is it just a few people who run into problems like this or is this simply 
 ignored by the people who set the strategy for FreeBSD?

 I mention since yeares here that putting version numbers onto the port 
 tree would solve many of these problems. All I get as an answer is that it 
 is not possible.

 I think that this should be easily possible with the limitation that older 
 versions do not have security fixes. Yes, but of what help is a security 
 fix if there is no running port for the fix?

 I feel like I'm missing something.  Why would you ever want to go back
 to an old version of the ports tree?  You're ignoring tons of security
 issues!

 ... I think the PNG update isn't a security issue. And for not being a
 security issue, it triggered an inadequate  mess!


 And if a port build is broken then the maintainer needs to fix it, that
 is the solution.

 Look at the comment of the maintainer of LibreOffice ...

 I must be missing something else here, it just seems like the underlying
 need for this is misguided (and dangerous from a security perspective).

 yes, you miss a very simple thing. Updated this morning your ports tree. 
 Your client asks for something for Monday morning for which you need now a 
 program which needs some kind of PNG but you did not install it.

 ... I spent now two complete days watching my boxes updating their
 ports. Several ports do not compile anymore (inkscape, libreoffice,
 libxul, to name some of the very hurting ones!).


 Do you have a machine that is fast enough to upgrade all your ports and 
 still finish what your client needs Monday morning?

 Even my fastest box, a brand new 6 core Sandy-Bridge-E, wasn't capable
 of compiling all the ports in due time. Several ports requested
 attendance, several, as mentioned, didn't compile out of the blue.


 The ports tree is not broken as such. Only the installation gets broken in 
 some sense. Have a version number there would allow people to go back to the 
 last known working ports tree, install the software - or whatever has to be 
 done - with a working system.

 Of course, the next step will be an upgrade. But only after the work which 
 brings in the money is done.

 You do not face this problem on Windows. You can run a 10 year old 'kernel' 
 and still install modern software.

 Erich

 I like having a very modern system with the most recent software. But in
 some cases, like these days with the PNG, FreeBSD's ports becomes again
 a problem. There is no convenient way to downgrade or allow the
 user/admin managing how to deal with the load of updates.

You can't have both.  As has been repeatedly explained to you, you
should not expect an easy life with the very latest of software.

Either stick to releases, or put up with lots of compiling etc-- you
should not complain because of self-inflicted problems.

Please remember that we do compile packages for release, or if more up
to date packages are required you can use the stable package sets
which are rarely over five days or so.

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: Why Are You NOT Using FreeBSD ?

[Chris Rees]

On Jun 3, 2012 4:39 AM, Erich erichfreebsdl...@ovitrap.com wrote:

 Hi,

 On 02 June 2012 PM 4:07:23 Alexander Yerenkow wrote:
  I'll try to be short.
  I'm using FreeBSD both at servers and as a desktop, but I see
  struggling of my friends with it in some things.
 
  1. Ports mess. You can very easily render system unusable, or broken
  if you trying to use latest ports. And then you had to became a port
  master to fix all. Of course you need a lot of free time, right? :)

 this seems to be ignored. I have just a small discussion in the thread
Why are you using FreeBSD about this. It would be already a step forward to
help people out of this fix when the ports tree of release would be easily
available.

  2. No decent packet manager (I hope pkgng will make life easier). You
  can't just upgrade this and that packet and see what's new, and
  rollback if you don't like somthing .

 I really hope this will never come. Why? It will kill make install. Make
install is the key to FreeBSD.

 I believe a better solution would be versioning of the ports tree. When
the ports tree compiles fully, it can be saved and its version number
incremented.

The Ports Tree is very rarely in a broken state-- the vast majority of
commits are thoroughly tested and nearly all ports will always compile on a
clean system.

 I do not believe that much more would be needed. Of course, we have then
a huge number of versions. Would it matter? Give the ports tree the major
version number of the latest release. So, at the moment it would be 10.
Increment then the minor every hour if you want. Just make sure that the
ports tree can be downloaded for some time under this version number.

This is already possible

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: Why Are You NOT Using FreeBSD?

[Chris Rees]

On Jun 3, 2012 5:26 AM, Erich erichfreebsdl...@ovitrap.com wrote:

 Hi,

 On 02 June 2012 PM 2:56:01 Chris Nehren wrote:
  On Sat, Jun 02, 2012 at 14:11:06 -0400 , Paul Mather wrote:
   I'm not sure what the solution is for the end user.  I know I get
   somewhat leery of updating my ports if I see a large number of changes
   coming via portsnap (like the 4000+ that accompanied the recent libpng
   upgrade) and there is nothing new in UPDATING (which, happily wasn't
   the case with the libpng upgrade).  Usually, I wait a while for the
   dust to clear and an UPDATING entry potentially to appear.
 
  If you're concerned about things breaking, don't follow the bleeding
  edge. This seems to be common sense.

 is there a second version of the ports tree available?

 What is the response of the list if you want to install a new package
with you old ports tree?


The response is Don't ask for support if you do that, I'm afraid.

No major OS I can think of allows you to mix and match like that (though I
could be wrong).

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: Why Are You Using FreeBSD?

[Chris Rees]

On Jun 2, 2012 4:04 AM, Erich Dollansky er...@alogreentechnologies.com
wrote:

 Hi,

 On 30 May 2012 PM 7:20:31 David Chisnall wrote:
 
  This is off-topic, so please feel free to disregard it, but I'm sending
it to this list in the hope that it will reach a largish number of users.
 
  I am currently looking at updating some of our advocacy material (which
advertises exciting new features like SMP support), and before I do I'd
like to get a better feel for why the rest of you are using FreeBSD.  If
you had to list the three things you most like about FreeBSD, which would
you pick?  Are they the same as when you first started using it?
 

 I must say that it is a long time ago when I sat at the first BSD
machine. The most important feature is the configuration and the update
procedure. Things rarely change in a way that users have to relearn.

 It is also important that it is possible to use a machine and upgrade it
only every six or twelve months without facing fundamental problems. What
helps there that the user can define a branch (8.x or 9.x) and stick with
it as long it is supported. The users are not forced to move to the next
version which might introduces some changes the user is not used to it.

 This allows users to skip one main branch. While it is possible to stick
with 8 until 10 is released, it is also possible to move to 9 or even 10.
Sticking with 8 reduces the risk to get caught with some problems during
the upgrade by some 50%

 But I have to mention one disadvantage. The ports are in no way linked to
the releases. This leads to situations in which a small change in a basic
library will result in a complete update of the installed ports. I
expressed this already many time here. It would be of advantage if the
ports tree would also have tags like the base system itself.


Unfortunately this is a massive amount of extra work - we only just keep up
with updates as it is.

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: Why Are You NOT Using FreeBSD?

[Chris Rees]

On Jun 2, 2012 3:19 PM, O. Hartmann ohart...@zedat.fu-berlin.de wrote:

 On 06/02/12 14:47, Daniel Kalchev wrote:
 
 
  On 02.06.12 15:32, Erich wrote:
  I know that the ports tree is a moving target. But it stops moving
  during the release period. This could be used to give a fall back
  solution.
 
  Or do I see this really too simple?
 
  The ports tree is a moving target during release periods still, although
  there are efforts to make movements smaller. This is why, after a
  release it suddenly moves more :)
 
  Daniel

 Even IF the ports tree IS a moving target, updating of UPDATING, for
 instance, follows most times AFTER the critical ports has been
 changed/updated and folks started updating their ports without realizing
 that they have shot themselfs into the foot!


Not reading UPDATING until there are problems is not the fault of the ports
tree; it should be checked every time you update.

Of course, many of us forget, but that still doesn't make it anyone else's
problem when we do!

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: Why Are You Using FreeBSD?

[Chris Rees]

On 2 June 2012 10:42, Erich Dollansky er...@alogreentechnologies.com wrote:
 Hi,

 On 02 June 2012 AM 9:14:28 Chris Rees wrote:
 On Jun 2, 2012 4:04 AM, Erich Dollansky er...@alogreentechnologies.com
 wrote:
 
  But I have to mention one disadvantage. The ports are in no way linked to
 the releases. This leads to situations in which a small change in a basic
 library will result in a complete update of the installed ports. I
 expressed this already many time here. It would be of advantage if the
 ports tree would also have tags like the base system itself.
 

 Unfortunately this is a massive amount of extra work - we only just keep up
 with updates as it is.

 I do not think so. At least not for the first step as I see it. Just make 
 snapshots of the ports tree when the release comes out. These snapshots are 
 with the releases anyway.

 What I did was very simple. I got the ports tree that comes with the release 
 and installed the system back to the release status. Ok, it was some work for 
 me - maybe not for others - to find this tree.

 A simple link could help here.

 I do not know if this is just an opinion which is too optimistic.

 What I know is that all the security fixes which appeared since the release 
 are not in there. If I have the choice between three days or more of 
 compiling and known security holes, I will take the security holes, make the 
 client happy and upgrade after the work for the client is finished.

 I would not expect that FreeBSD will provide more than this.

Then you already have all you need-- RELEASEs use packages compiled at
time of release if you use pkg_add -r, and the ports tree is tagged at
release if you wish to get a 'snapshot'.

Note that you will not get any official support if you choose to use a
tagged tree :)

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: Why Are You NOT Using FreeBSD ?

[Chris Rees]

On 1 June 2012 16:20, Nomen Nescio nob...@dizum.com wrote:
 Dear All ,

 There is a thread

 Why Are You Using FreeBSD ?


 I think another thread with the specified subject   'Why Are You NOT Using
 FreeBSD ? may be useful :


 If you are NOT using FreeBSD for any area or some areas , would you please
 list those areas with most important first to least important last ?

 1. The X-org changeover a few years ago screwed up a FreeBSD installation I
 had been using so badly I never trusted FreeBSD's rolling update ports
 system again. That should have been a major FreeBSD release, but instead it
 was done just in the ports with no version bump and no choice and no notice
 unless you read the fine print.

 2. Broken ports galore. Much of the stuff I wanted broke on AMD64 after
 downloading tarballs for hours. Not good. Contacted package maintainer and
 received answer: yeah, I know it doesn't work on AMD64.

That is unacceptable.  Submit a PR next time you find something like
that-- ports that are broken on an arch should be marked as such so
people don't waste their time as you have been made to.

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: Why Are You Using FreeBSD?

[Chris Rees]

On 30 May 2012 19:20, David Chisnall thera...@freebsd.org wrote:
 Hi Everyone,

 This is off-topic, so please feel free to disregard it, but I'm sending it to 
 this list in the hope that it will reach a largish number of users.

 I am currently looking at updating some of our advocacy material (which 
 advertises exciting new features like SMP support), and before I do I'd like 
 to get a better feel for why the rest of you are using FreeBSD.  If you had 
 to list the three things you most like about FreeBSD, which would you pick?  
 Are they the same as when you first started using it?


You might not have wanted opinions from developers... but

1) Complete base system-- if I mess up badly with ports I can delete
them all and still have a usable system to recover from

2) Simplicity of configuration-- mostly configured with flat text
files rather than directories full of conf files

3) Friendly community; easy to get support from people who really know
what they're doing.

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: FreeBSD9 and the sheer number of problem reports

[Chris Rees]

On 24 February 2012 01:35, Erich Dollansky erichfreebsdl...@ovitrap.com wrote:
 Hi,

 On Friday 24 February 2012 01:25:01 Damien Fleuriot wrote:

 This is NOT a troll.
 This is NOT a flame.
 Do NOT hijack this thread to troll/flame.

 allow them some fun too.


 Now, I find the number of problem reports regarding 9.0-RELEASE alarming
 and I'm growing more and more fearful towards it.

 In the current state of things, I have *absolutely* no wish to run it in
 production :(

 Did you read deeply into the strategy behind the releases? If I remember 
 right, the odd numbers are a little bit more experimental compared to the 
 even numbers. For myself, I try to stick with even numbers whenever possible. 
 If I install FreeBSD on a serious machine, I never use x.0. It must be at 
 least x.1.

There's no such odd/even number policy with FreeBSD-- I think you're
thinking of another OS ;)

You're right that x.0 is slightly more experimental in general though
(by its nature, it must be).

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: FreeBSD9 and the sheer number of problem reports

[Chris Rees]

On 26 February 2012 11:32, Erich Dollansky erichfreebsdl...@ovitrap.com wrote:
 Hi,

 On Sunday 26 February 2012 18:16:53 Chris Rees wrote:
 On 24 February 2012 01:35, Erich Dollansky erichfreebsdl...@ovitrap.com 
 wrote:
 
  On Friday 24 February 2012 01:25:01 Damien Fleuriot wrote:
 
  This is NOT a troll.
  This is NOT a flame.
  Do NOT hijack this thread to troll/flame.
 
  allow them some fun too.
 
 
  Now, I find the number of problem reports regarding 9.0-RELEASE alarming
  and I'm growing more and more fearful towards it.
 
  In the current state of things, I have *absolutely* no wish to run it in
  production :(
 
  Did you read deeply into the strategy behind the releases? If I remember 
  right, the odd numbers are a little bit more experimental compared to the 
  even numbers. For myself, I try to stick with even numbers whenever 
  possible. If I install FreeBSD on a serious machine, I never use x.0. It 
  must be at least x.1.

 There's no such odd/even number policy with FreeBSD-- I think you're
 thinking of another OS ;)

 maybe something got stuck in my head with the move from 4 to 5.

4 to 5 was SMP-related, and when the Project decided to move to
time-based rather than feature-based releases -- pure coincidence that
5 was odd.

 How easy was the move to 6 then?

_Just_ before my time I'm afraid ;)

 Independent of this, it is still true that there is always the older branch 
 available when a new one opens at .0.

 You're right that x.0 is slightly more experimental in general though
 (by its nature, it must be).

 And has nothing to do with FreeBSD as such.


Exactly :)

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: libutempter

[Chris Rees]

On 14 Jan 2012 08:48, Andre Goree an...@drenet.info wrote:

 On Tue, 10 Jan 2012 19:58:13 -0600, Andre Goree an...@drenet.info wrote:

 I recently csup'd 9-STABLE and was able to get it working along with my
 custom kernel.  I'm now in the process of rebuilding all my ports, and
I've
 come across something when running 'portmaster -af' that I can't seem to
 find any information on.

 === Launching child to reinstall libutempter-1.1.5_1

 === Port directory: /usr/ports/sysutils/libutempter

=== This port is marked IGNORE
=== is now contained in the base system


=== If you are sure you can build it, remove the
   IGNORE line in the Makefile and try again.

 === Update for libutempter-1.1.5_1 failed
 === Aborting update

 Terminated


 I figure, ok I'll just delete the package and move on.  However, there
 are many packages I have installed that depend on libutemper.  I would
 still just proceed with the removal given that the functionality is
 provided in base now, however I don't want to break all these ports and
 have to deal with the mess when I portmaster -af again.

 What is the recommended action here?  Should I just force exclude that
port
 from the upgrade?  That's probably the easiest way but I'd have to deal
 with this at some point.

 Thanks in advance for any advice

 --
 Andre Goree
 andre@drenetinfo


 So I've rebuilt everything that I could, but when I get to the ports that
depend on libutempter, I get an error that they could not be reinstalled
due to a failure with libutempter  :/

 ---  Skipping 'www/opera' (opera-11.60) because a requisite package
'libutempter-1.1.5_1' (sysutils/libutempter) failed (specify -k to force)
 ---  Skipping 'www/opera-linuxplugins' (opera-linuxplugins-11.60)
because a requisite package 'opera-11.60' (www/opera) failed (specify -k to
force)
 ---  Skipping 'deskutils/kdeplasma-addons' (kdeplasma-addons-4.7.3)
because a requisite package 'kdepimlibs-4.7.3' (deskutils/kdepimlibs4)
failed (specify -k to force)
 ---  Skipping 'graphics/libkdcraw-kde4' (libkdcraw-4.7.3) because a
requisite package 'libutempter-1.1.5_1' (sysutils/libutempter) failed
(specify -k to force)


 I installed misc/compat8x, however it informed my that I'd need to add 
to the kernel conf.  When I try to do that, I'm met with this error:

 /usr/src/sys/amd64/conf/DESKTOPKERN9: unknown option COMPAT_FREEBSD8
 *** Error code 1
 Stop in /usr/src.


 Which is weird, because:

 [root@desktop src]# uname -r
 9.0-STABLE


 Meaning I'm certainly running 9.0-STABLE.  So what gives re: that error
above about unknown option?  I even tried to csup source and buildworld
again, but to no avail -- the error remains.


Just pkg_delete -f it.

Since it's in base, its absence won't cause a problem.

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: FLAME - security advisories on the 23rd ? uncool idea is uncool

[Chris Rees]

On 23 Dec 2011 18:56, George Kontostanos gkontos.m...@gmail.com wrote:

 On Fri, Dec 23, 2011 at 8:40 PM, Matthew Seaman
 m.sea...@infracaninophile.co.uk wrote:
  On 23/12/2011 18:05, George Kontostanos wrote:
  Are all cvs mirror servers updated regarding these changes ?
 
  ANYBODY 
 
  Should have by now.  Commits usually take about an hour to propagate to
  the official cvsup servers.
 
  Easy enough to tell though -- the advisories have all the version
  numbers in, and you'ld only need to check a file or two from each of
  them to be reasonably sure you'ld got all the updates.
 
 Cheers,
 
 Matthew
 
  --
  Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
   Flat 3
  PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW
 

 Thanks for the info Matthew. I think though that it is best for all to
 first make sure that the servers all updated before sending out all
 those security advisories.


The emails contain patches.

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: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server

[Chris Rees]

On 15 December 2011 17:58, O. Hartmann ohart...@zedat.fu-berlin.de wrote:
 Since ZFS in Linux can only be achieved via FUSE (ad far as I know), it
 is legitimate to compare ZFS and ext4. It would be much more competetive
 to compare Linux BTRFS and FreeBSD ZFS.



Er... does ext4 guarantee data integrity?

You're not comparing like with like; please do some research on the
point of ZFS before asserting that they're fair comparisons.

A fair(er) comparison could be ext4 with UFS+soft-updates.

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: Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 Server

[Chris Rees]

On 15 Dec 2011 21:25, Kevin Oberman kob6...@gmail.com wrote:

 On Thu, Dec 15, 2011 at 10:46 AM, Chris Rees cr...@freebsd.org wrote:
  On 15 December 2011 17:58, O. Hartmann ohart...@zedat.fu-berlin.de
wrote:
  Since ZFS in Linux can only be achieved via FUSE (ad far as I know), it
  is legitimate to compare ZFS and ext4. It would be much more
competetive
  to compare Linux BTRFS and FreeBSD ZFS.
 
 
 
  Er... does ext4 guarantee data integrity?
 
  You're not comparing like with like; please do some research on the
  point of ZFS before asserting that they're fair comparisons.
 
  A fair(er) comparison could be ext4 with UFS+soft-updates.

 Wouldn't UFS+SUJ be the closest atch?

Yup. Thanks.

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: WITHOUT_SYSINSTALL (stable-9)

[Chris Rees]

On 31 October 2011 04:03, Andrew Lankford lankfordand...@charter.net wrote:
 I was able to buildworld, buildkernel to 9.0-RC1 from 8-stable without
 incident.  Yay.  However, I noticed a new sysinstall executable  in
 /usr/sbin even though I included WITHOUT_SYSINSTALL=yes  in
 /etc/src.conf.  My src.conf  looks like it's in good order, and the
 other WITHOUT_ options were heeded.


You mention a new sysinstall executable, as in it was *definitely*
installed by the installworld and not just left over? Is the mtime the
same as others in that dir?

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: /usr/bin/script eating 100% cpu with portupgrade and xargs

[Chris Rees]

On 14 Oct 2011 21:50, Stefan Bethke s...@lassitu.de wrote:


 Am 14.10.2011 um 14:03 schrieb Jilles Tjoelker:

  On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote:
  On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote:
  I won't be in a position to create a simpler test case, raise a PR or
  try patches till Tuesday evening (UK) at the earliest.
 
  So far I have been unable to reproduce the problem with portupgrade
(and
  will probably move to portmaster).
 
  I have however found a different but possibly related problem with the
  new version of script in RELENG_8, for which I have raised this PR:
 
  misc/161526: script outputs corrupt if input is not from a terminal
 
  Blast, should of course been bin/
 
  The extra ^D\b\b are the EOF character being echoed. These EOF
  characters are being generated by the new script(1) to pass through the
  EOF condition on stdin.
 
  One fix would be to change the termios settings temporarily to disable
  the echoing but this may cause problems if the application is changing
  termios settings concurrently and generally feels bad.
 
  It may be best to remove writing EOF characters, perhaps adding an
  option to enable it again if there is a concrete use case for it.

 I finally figured out why my ports aren't updating anymore: when running
portupgrade -a --batch from cron, stdin is /dev/null, and that produces the
gobs of ^D in the output, as well as the script file that portupgrade
creates.  What's worse is that the upgrade never completes.


Worst of all, you're running portupgrade from cron without reading UPDATING,
which is just asking for trouble.

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: bsdinstall partitioning

[Chris Rees]

On 9 October 2011 22:30, Gabor Kovesdan ga...@freebsd.org wrote:
 Hi,

 I just had my first encounter with the new installer. I chose manual
 partitioning, created a BSD disk (not GPT) with one swap and the rest for /.
 Rest of the installation went fine but then my system didn't boot. I
 repeated everything and I chose guided partitioning. This time it worked but
 I think the manual way with BSD disk format should also work as it did in
 sysinstall. Besides, the partition types (freebsd-ufs, freebsd-swap and
 freebsd-boot) should be listed somehow or there should be radio buttons. If
 you choose manual partition with GPT, only the first two are shown in the
 description so one may not know that there is also a freebsd-boot type,
 which is mandatory.

 Anyway, the rest of the installer and the configuration is very convenient
 and I loved that I could configure my wifi connection w/o hand-editing the
 config files, so thanks a lot to Nathan for the hard work!

Wifi was the main thing I was pleased with too-- thanks from me.

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: BETA3 not buildable

[Chris Rees]

On 8 October 2011 03:25, Jeremy Chadwick free...@jdc.parodius.com wrote:
 On Fri, Oct 07, 2011 at 02:36:25PM -0400, Aryeh Friedman wrote:
 Just a quick note the repo was synced about 15 mins before this

 On Fri, Oct 7, 2011 at 2:34 PM, Aryeh Friedman 
 aryeh.fried...@gmail.comwrote:

  I have a local cvs repo and after checking src into a completely fresh
  /usr/src I get:
 
  flosoft# make buildworld
  find: /usr/src/sys/sys/param.h: No such file or directory
  Makefile, line 217: warning: find /usr/src/sys/sys/param.h -mtime -0s
  returned non-zero status
  find: /usr/src/sys/sys/param.h: No such file or directory
  Makefile, line 217: warning: find /usr/src/sys/sys/param.h -mtime -0s
  returned non-zero status

 Note that I just synced with the repo 15 minutes ago does not mean
 much.  Those repos are also often behind, given that they only sync
 with cvsup-master every so often.  What's every so often?  It varies
 from public cvsup server to public cvsup server, and there's no way to
 know.  Great isn't it?

 If you are syncing directly off of cvsup-master -- shame on you.  You
 aren't supposed to do this, and I believe the Handbook or freebsd-hubs
 even has a policy about it being considered inappropriate.


Not much chance of that;

[crees@zeus]~% grep host supfile  csup supfile
*default host=cvsup-master.freebsd.org
Connected to 69.147.83.50
Authentication required by the server and not supported by client
[crees@zeus]~%

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

Fwd: Re: [HEADSUP]: ports feature freeze starts soon

[Chris Rees]

Just on case anyone's not on ports@:

-- Forwarded message --
From: Chris Rees cr...@freebsd.org
Date: 8 Oct 2011 10:30
Subject: Re: [HEADSUP]: ports feature freeze starts soon
To: Thomas Mueller mueller6...@bellsouth.net
Cc: freebsd-po...@freebsd.org, Erwin Lansing er...@freebsd.org

On 8 October 2011 10:22, Thomas Mueller mueller6...@bellsouth.net wrote:
 from Erwin Lansing er...@freebsd.org:

 In preparation for 9.0 the ports tree will be in feature freeze
 after release candidate 1 (RC2)is released, currently planned for
 October 17.

 Was there a typo here?  Did you mean release candidate 1 or 2?

 RC1 seems more logical, since RC1 has not been released yet,
 and October 17 is only nine days away.



-- Forwarded message --
From: Erwin Lansing er...@freebsd.org
Date: 7 October 2011 17:34
Subject: Re: [HEADSUP]: ports feature freeze starts soon
To: develop...@freebsd.org develop...@freebsd.org
On Oct 7, 2011, at 11:20, Erwin Lansing er...@freebsd.org wrote:

 In preparation for 9.0 the ports tree will be in feature freeze
 after release candidate 1 (RC2)is released, currently planned for
 October 17.

Sorry about the typo, just to be clear I did mean RC2, not RC1 as
usual as an RC3 has been planned in this release cycle.

Erwin
___
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 9.0-BETA3 Available...

[Chris Rees]

What is your Wiki name?
On 4 Oct 2011 16:26, Arnaud Lacombe lacom...@gmail.com wrote:
 Hi,

 On Mon, Oct 3, 2011 at 7:50 PM, Arnaud Lacombe lacom...@gmail.com wrote:
 Hi,

 On Wed, Sep 28, 2011 at 9:42 PM, Ken Smith kensm...@buffalo.edu wrote:

 The third BETA build of the 9.0-RELEASE release cycle is now
 available.  Since this is the first release of a brand new branch
 I cross-post the announcements on both -current and -stable.  But
 just so you know most of the developers active in head pay more
 attention to the -current mailing list.  If you notice problems you
 can report them through the normal Gnats PR system or on the -current
 mailing list.

 The 9.0-RELEASE cycle will be tracked here:

http://wiki.freebsd.org/Releng/9.0TODO

 could you please update that page ? It's wayy out of date...

 The page is immutable, so I guess a lambda user cannot edit it.

 Could you please give me the credential to update it ?

 Providing an out-of-date status update page in a release is really
 amateurish; the only real use of that page being during the release
 process...

 Thanks,
 - Arnaud
 ___
 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: FreeBSD 9.0-BETA3 Available...

[Chris Rees]

On 4 October 2011 16:35, Chris Rees utis...@gmail.com wrote:
 On 4 Oct 2011 16:26, Arnaud Lacombe lacom...@gmail.com wrote:
 On Mon, Oct 3, 2011 at 7:50 PM, Arnaud Lacombe lacom...@gmail.com wrote:
 On Wed, Sep 28, 2011 at 9:42 PM, Ken Smith kensm...@buffalo.edu wrote:

 The third BETA build of the 9.0-RELEASE release cycle is now
 available.  Since this is the first release of a brand new branch
 I cross-post the announcements on both -current and -stable.  But
 just so you know most of the developers active in head pay more
 attention to the -current mailing list.  If you notice problems you
 can report them through the normal Gnats PR system or on the -current
 mailing list.

 The 9.0-RELEASE cycle will be tracked here:

        http://wiki.freebsd.org/Releng/9.0TODO

 could you please update that page ? It's wayy out of date...

 The page is immutable, so I guess a lambda user cannot edit it.

 Could you please give me the credential to update it ?

 Providing an out-of-date status update page in a release is really
 amateurish; the only real use of that page being during the release
 process...

 What is your Wiki name?

Just to clarify, I will fix you up with access, but the re page should
not be edited without re approval!

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: FreeBSD 9.0-BETA3 Available...

[Chris Rees]

On 4 October 2011 19:36, Arnaud Lacombe lacom...@gmail.com wrote:
 Hi,

 On Tue, Oct 4, 2011 at 11:35 AM, Chris Rees utis...@gmail.com wrote:
 What is your Wiki name?

 ArnaudLacombe

 created this morning, with the same email address as the one I'm
 sending this email with.


Sorry Arnaud, the policy on editing the TODO page is strict. You'll
have to negotiate a strategy.

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: ports/sysutils/diskcheckd (Re: bad sector in gmirror HDD)

[Chris Rees]

On 25 August 2011 18:54, Chris Rees utis...@gmail.com wrote:
 On 24 August 2011 16:14,  per...@pluto.rain.com wrote:
 When the specified or calculated rate exceeds 64KB/sec, the
 required sleep interval between 64KB chunks is less than one
 second.  Since diskcheckd calculates the interval in whole seconds
 -- because it calls sleep() rather than usleep() or nanosleep()
 -- an interval of less than one second is calculated as zero ...
 I suspect the fix will be to calculate in microseconds, and call
 usleep() instead of sleep().

 I think I may have this fixed.

 Could one of you try the attached patch?  I'm especially interested
 to see if this also clears up the issues reported as connected with
 gmirror (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/143566),
 since I haven't been able to reproduce that part here.

 Summary of changes:

 * Calculate delays in microseconds, so that delays of less than
  one second between reads (needed to implement rates exceeding
  64KB/sec) do not get rounded down to zero.

 * Fix a reinitialization problem when handling SIGHUP.

 * Additional debug messages (only with -d).

 * Comment and manpage improvememts.


 Hi Perry,

 The changes look good, so if there's no response for a few days I'll
 commit the changes.

 Thanks for rescuing the port :)


Committed. Thanks!

-- 
Chris Rees          | FreeBSD Developer
cr...@freebsd.org   | http://people.freebsd.org/~crees
___
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: ports/sysutils/diskcheckd (Re: bad sector in gmirror HDD)

[Chris Rees]

On 24 August 2011 16:14,  per...@pluto.rain.com wrote:
 When the specified or calculated rate exceeds 64KB/sec, the
 required sleep interval between 64KB chunks is less than one
 second.  Since diskcheckd calculates the interval in whole seconds
 -- because it calls sleep() rather than usleep() or nanosleep()
 -- an interval of less than one second is calculated as zero ...
 I suspect the fix will be to calculate in microseconds, and call
 usleep() instead of sleep().

 I think I may have this fixed.

 Could one of you try the attached patch?  I'm especially interested
 to see if this also clears up the issues reported as connected with
 gmirror (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/143566),
 since I haven't been able to reproduce that part here.

 Summary of changes:

 * Calculate delays in microseconds, so that delays of less than
  one second between reads (needed to implement rates exceeding
  64KB/sec) do not get rounded down to zero.

 * Fix a reinitialization problem when handling SIGHUP.

 * Additional debug messages (only with -d).

 * Comment and manpage improvememts.


Hi Perry,

The changes look good, so if there's no response for a few days I'll
commit the changes.

Thanks for rescuing the port :)

Chris

-- 
Chris Rees          | FreeBSD Developer
cr...@freebsd.org   | http://people.freebsd.org/~crees
___
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: The FreeBSD 7.4-BETA1 CD wont boot properly on this machine

[Chris Rees]

On 19 December 2010 19:55, Torfinn Ingolfsen
torfinn.ingolf...@broadpark.no wrote:
 Hi,
 I am trying to install FreeBSD 7.4-BETA1 / amd64 on this[1] machine.
 The machine doesn't have a CD drive built-in, so I am using a Plextor
 PX-608CU external DVD writer which connects via usb as the CD drive to
 install from. I use the FreeBSD-7.4-BETA1-amd64-disc1.iso, which is burned
 to a CD.
 After powering on the machine, I press F8, get a nice little bootmenu,
 select the Plextor drive, and off we go. The kernel boots, and
 everything is great.
 But, after detecting the hard drive (ad4, ok it's really a SSD) and the
 cd drive, it just spits out messages like these:
 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
 run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
 run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
 run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config

 and after spitting out one more message  (the one for 300 seconds), it just
 sits there. Booting with verbose doesn't give men any more messages related
 to this. I've tried the -bootonly CD too - it has the same problem.
 Yes, the sha256 checksums on the files verifies a-ok, the CD's can be mounted
  in FreeBSD, etc.
 I even mad a usb memory stick image of the -disc1 and booted the machine from 
 that,
 and it has the same problem (the run_interrupt... messages).

 Kicker: the machine boots nicely from a FreeBSD 8.1-release (amd64) CD.
 Also tried with a OpenBSD 4.8 (amd64) install CD, yep - it also boots nicely.

 So, any hints on how to get FreeBSD 7.4-BETA1 onto this machine?

 References:
 1) http://sites.google.com/site/tingox/asus_v7-p7h55e
 --
 Regards,
 Torfinn Ingolfsen

Did you try installing using a different computer onto that hard drive?

Is the hardware supported by 7.x
(http://www.freebsd.org/releases/7.3R/hardware.html for pointers)

Is there a reason you want 7.4 rather than 8.1?

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: Unresponsive keyboard after a few boots

[Chris Rees]

On 10 February 2010 07:10, Mehmet Erol Sanliturk
m.e.sanlit...@gmail.com wrote:


 On Tue, Feb 9, 2010 at 8:52 PM, Rohit Grover rgrov...@gmail.com wrote:
 Initially start FreeBSD and dump all of the related circuit register values
 . This may require a key board . Problem is to override this requirement .
 If in the system there is also a PS/2 key board slot , a PS/2 keyboard may
 be utilized . Another way may be a shell script or program starting on boot
 automatically to dump the required values . In that case , a key board may
 not be required .

There are no PS/2 or any other legacy connectors on any Intel Mac.

USB only (firewire keyboards are a rarity, but maybe worth a try!)

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: Unresponsive keyboard after a few boots

[Chris Rees]

On 8 February 2010 11:47, Jeremy Chadwick free...@jdc.parodius.com wrote:
 On Mon, Feb 08, 2010 at 02:19:06PM +0530, Rohit Grover wrote:
 I am using a very recent Freebsd 8.0 STABLE on a Macbook. I updated my
 sources and rebuilt a kernel about 3 days ago. I was able to use the
 machine fine once or twice after that. But now the keyboard has
 stopped working. The boot program is able to use the keyboard, but the
 kernel isn't, and I am unable to do anything useful with the machine
 from the login screen.

 I had rebuilt the kernel twice with slightly varying settings, so I
 don't have a copy of the previously working kernel in
 /boot/kernel.old.

 It may not be easy for me to download a ISO image. Can someone please help?

 Is the keyboard USB?


No Mac since late generation Powerbooks and iBooks has used ADB, so
yes, the Macbook
keyboard is USB.

HTH,

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: bootless!

[Chris Rees]

2009/10/17 Clifford, Ken ken.cliff...@mirror-image.com:
 Take me off this fucking list!@

From the bottom of the email you just sent:

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


You're welcome.

Chris


-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in a mailing list?
___
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: I need to add commands that starts every time at system boot.

[Chris Rees]

2009/6/7 Clifton Royston clift...@lava.net:
 On Sun, Jun 07, 2009 at 04:12:41PM -0400, Scott Ullrich wrote:
 On Sun, Jun 7, 2009 at 3:36 PM, Chris Reesutis...@googlemail.com wrote:
  2009/6/7 Clifton Royston clift...@lava.net:
 
  If you feel you just *can't* do it via a script in
  /usr/local/etc/rc.d, which is the better way, add a script called
  /etc/rc.local and that will be run after all the other start-up steps.
 
  What's wrong with rc.local?

 Probably stems from this discussion:
 http://lists.freebsd.org/pipermail/freebsd-stable/2007-July/035996.html

  No, I hadn't actually seen that discussion before.

  I used to work on BSD/OS, which had only the rc.local mechanism, and
 when I first switched over to FreeBSD it was what I used.  Eventually I
 got my head around the /etc/rc.d and /usr/local/etc/rc.d mechanism and
 found it distinctly superior, so now I use it almost exclusively.

  Major highlights as to why are:

  * You can readily implement whatever additional operations your service
   should support, such as restart/shutdown/whatever;
  * you can add or remove different services as discrete entities,
   without having to merge their change or removal into a single text
   file;
  * the startup/shutdown script can therefore readily be packaged for
   removal/installation together with any other software for the
   service in question;
  * you can get your service or operation run in a specific order
   relative to other services;
  * you can use the same script to start, shutdown, or restart the
   service at another time if appropriate or necessary

  It used to be a little harder to write them than a few lines in
 rc.local, but now sourcing rc_subr provides shell functions which make
 it trivial.

  These days I only use rc.local if I need to do some kind of
 non-critical quick hack, e.g. for troubleshooting a problem.
  -- Clifton

 --
    Clifton Royston  --  clift...@iandicomputing.com / clift...@lava.net
       President  - I and I Computing * http://www.iandicomputing.com/
  Custom programming, network design, systems and network consulting services


Nice, thanks a lot, didn't know about rc_subr. Thanks Scott too.

Chris

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in a mailing list?
___
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: I need to add commands that starts every time at system boot.

[Chris Rees]

2009/6/7 Clifton Royston clift...@lava.net:

 If you feel you just *can't* do it via a script in
 /usr/local/etc/rc.d, which is the better way, add a script called
 /etc/rc.local and that will be run after all the other start-up steps.

What's wrong with rc.local?

Chris


-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in a mailing list?
___
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

Recommended wireless card (or is there a chance to get either iwi or ath fixed)?

[Chris Rees]

2009/2/25 Paul B. Mahol one...@gmail.com:
 On 2/24/09, SDH Support ad...@stardothosting.com wrote:

 I tried using my ath based D-Link DWL G650, which still seems to have
 some issues in regard to interrupt handling:


 I've been able to get /most/ wireless cards working with ndiswrapper.

 *BSD doesnt have ndiswrapper.


 --
 Paul
 ___
 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


Yeah it does...

[ch...@amnesiac]~% ndisgen
       ==
       -- Windows(r) driver converter ---
       ==

       This script is designed to guide you through the process
       of converting a Windows(r) binary driver module and .INF
       specification file into a FreeBSD ELF kernel module for use
       with the NDIS compatibility system.

       The following options are available:

       1] Learn about the NDIS compatibility system
       2] Convert individual firmware files
       3] Convert driver
       4] Exit

       Enter your selection here and press return:

--
R $h !  $- ! $+      $@ $2  @ $1 .UUCP.  (sendmail.cf)
___
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: Recommended wireless card (or is there a chance to get either iwi or ath fixed)?

[Chris Rees]

2009/2/25 Christian Walther cptsa...@gmail.com:
 2009/2/24 SDH Support ad...@stardothosting.com:

 I tried using my ath based D-Link DWL G650, which still seems to have
 some issues in regard to interrupt handling:


 I've been able to get /most/ wireless cards working with ndiswrapper.

 This is just my personal opinion, and I tend to make scarce use of the
 word hate - but in this case: I really hate ndiswrapper.
 It might be suitable for some people, but I rather get some piece
 hardware that is properly supported. Bugs are bad luck, of course, as
 well as a kernel module author who stops working. But at least I don't
 have to rely on a windows driver.
 ___
 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


True, but ndiswrapper for me was an epiphany of the incredible things
free software can do.

I found it right back in Debian Woody, where my Ralink card wasn't
supported. I got sick of Linux and moved to BSD, where the ral driver
was instantly recognised and loaded.

-- 
R $h !  $- ! $+  $@ $2  @ $1 .UUCP.  (sendmail.cf)
___
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: Test

[Chris Rees]

2008/12/17  test1...@cogeco.ca:
 This is a test message from Cogeco Cable. No reply is necessary.

What's wrong with http://lists.freebsd.org/mailman/listinfo/freebsd-test ?

-- 
R $h !  $- ! $+  $@ $2  @ $1 .UUCP.  (sendmail.cf)
___
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: Is FreeBSD a suitable choice for a MacBook?

[Chris Rees]

 Date: Sat, 04 Oct 2008 21:00:48 +0200
 From: Eirik Wix?e Svela [EMAIL PROTECTED]
 Subject: Is FreeBSD a suitable choice for a MacBook?
 To: freebsd-stable@freebsd.org
 Message-ID: [EMAIL PROTECTED]
 Content-Type: text/plain; charset=ISO-8859-1

 I have an Apple MacBook with an Intel Core 2 Duo processor (November
 2007 edition, cf. the Wikipedia article for specifications), and I have
 been considering switching to one of the free UNIX clones for some time
 now. I understand that Ubuntu GNU/Linux is supposed to work well on this
 kind of machine, but I would rather use some variant of BSD if that is a
 viable alternative.

 I would therefore like to ask you whether anyone here has any experience
 with FreeBSD, either 7.0-RELEASE or any other version, that they would
 like to share so I might know what to expect if I choose to go through
 with this. I have some time on my hands the next couple of weeks, so I
 am prepared to spend some days tweaking things to work if it is worth
 the effort, but if it isn't, I might as well take Ubuntu for a spin or
 do a clean install of Mac OS X.

 Best regards
 Eirik W. Svela


On my Macbook, I ran and used Ubuntu and FreeBSD in the days of 6.1
for a while, but the big problem is power management.

On a laptop that is a killer... Standby is unreliable, breaks, and
basically means that if you're on the move you have to shutdown and
boot every time you want to put your laptop away. Is that what you
really want? Say goodbye to your battery life too.

Apart from that, all the cool parts of FreeBSD are just as good on it.
I just found it's far better on my PC.

-- 
R $h !  $- ! $+  $@ $2  @ $1 .UUCP.  (sendmail.cf)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Wireless net Card

[Chris Rees]

2008/8/11 Warren Liddell [EMAIL PROTECTED]:
 Which Belkin wireless card do you have? Which arch are you running
 (i386/amd64)?

 I had horrific trouble with a Belkin on the Realtek chipset, played up
 with Ubuntu, FreeBSD, Fedora, even Windows!

 Trouble with Belkin is, you never know what you're getting. You need
 the revision number of the card, and then find out which chipset it
 is. Make sure the drivers you downloaded are for that exact revision.

 Hope you have more luck than I did, I tossed mine and bought a Ralink.

 Chris

 AMD64 Arch  ironically it worked beautifully for ages in windows, but i  got
 sick of windows having been used to FreeBSD, so i re-installed FreeBSD an
 using the onboard LAN card atm, but am wanting to goto wireless.


 [EMAIL PROTECTED]:3:5:0:   class=0x02 card=0x700f1799 chip=0x700f1799
 rev=0x20 hdr=0x00
vendor = 'Belkin Research and Development Labs'
class  = network
subclass   = ethernet


 Chipset is RT8185L an i used the ndisgen to create the .ko file, which is just
 over 572kb in size.

 ironically the 8180 works fine, but naturally wont do my wireless card.


This card I have also had problems with. It appears to be an 8185, but
nothing works with it. Even in Windows, unless you have the Belkin
drivers, it won't work properly.

I couldn't load the Windows driver with ndisgen either, and
ndiswrapper in Linux doesn't work either, nor does the Realtek Linux
driver.

-- 
R $h !  $- ! $+  $@ $2  @ $1 .UUCP.  (sendmail.cf)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Wireless net Card

[Chris Rees]

 Date: Sun, 10 Aug 2008 14:33:54 +1000
 From: Warren Liddell [EMAIL PROTECTED]

 I downloaded the drivers for the chipset my belkin wireless card has, used
 ndisgen to create the kernel module, which all went aok .. however when
 trying to load the module it hard hangs the machine to the point of it
 restarting itself .. is there something i perhaps mybe missing or am i out in
 the cold in not being able to use this wireless card untill some time a
 freebsd driver is done ?


Which Belkin wireless card do you have? Which arch are you running (i386/amd64)?

I had horrific trouble with a Belkin on the Realtek chipset, played up
with Ubuntu, FreeBSD, Fedora, even Windows!

Trouble with Belkin is, you never know what you're getting. You need
the revision number of the card, and then find out which chipset it
is. Make sure the drivers you downloaded are for that exact revision.

Hope you have more luck than I did, I tossed mine and bought a Ralink.

Chris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: em(4) on FreeBSD is sometimes annoying

[Chris Rees]

Martin [EMAIL PROTECTED] wrote:

 On Sat, 02 Aug 2008 12:55:53 +0200
 Torfinn Ingolfsen [EMAIL PROTECTED] wrote:

 Just to be sure: also if the first command you try on the interface is
 'ifconfig up'?

 Hello Torfinn,

 good point, no. The problem appears when the first thing called on this
 interface is dhclient (caused by ifconfig_em0=DHCP). I could also
 provoke this behavior after the interface was once up had an IP and was
 working (ping). All I need to do is to disconnect the NIC from the
 switch when I type /etc/rc.d/netif restart.

 I have noticed further strange effects here. The behavior seems to
 be even more complex.

 After I typed /etc/rc.d/netif restart, I waited until I get giving
 up message. Then I plugged the cable in. After about 30 seconds the
 link LED was on. I noticed that at this point I couldn't get an address
 using DHCP.

 So I disconnected physically the NIC (no cable) and link LED was
 still on! ifconfig showed me state: active with no cable plugged in.
 After further 30 seconds the LED went off.

 I attached the NIC again to the switch again and after 30 seconds
 again I got some other effect. The link LED went on (status: active)
 and the data LED was permanently blinking (about 2,5 times a second). I
 pulled the cable again and now the link LED is still on and the data
 LED still blinking (since about 10 minutes already).

 By the way...
 Now I'm typing this E-Mail without an ethernet cable plugged in and the
 link status LED is still on and the other data LED is blinking.

 --
 Martin

I may have misunderstood the purpose of this, but do you have the bpf
compiled into your kernel? If you're having DHCP troubles, this could
be a problem.

Chris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: em(4) on FreeBSD is sometimes annoying

[Chris Rees]

2008/8/4 Jeremy Chadwick [EMAIL PROTECTED]:
 On Mon, Aug 04, 2008 at 11:00:16AM +0100, Chris Rees wrote:
 Martin [EMAIL PROTECTED] wrote:

  On Sat, 02 Aug 2008 12:55:53 +0200
  Torfinn Ingolfsen [EMAIL PROTECTED] wrote:
 
  Just to be sure: also if the first command you try on the interface is
  'ifconfig up'?
 
  Hello Torfinn,
 
  good point, no. The problem appears when the first thing called on this
  interface is dhclient (caused by ifconfig_em0=DHCP). I could also
  provoke this behavior after the interface was once up had an IP and was
  working (ping). All I need to do is to disconnect the NIC from the
  switch when I type /etc/rc.d/netif restart.
 
  I have noticed further strange effects here. The behavior seems to
  be even more complex.
 
  After I typed /etc/rc.d/netif restart, I waited until I get giving
  up message. Then I plugged the cable in. After about 30 seconds the
  link LED was on. I noticed that at this point I couldn't get an address
  using DHCP.
 
  So I disconnected physically the NIC (no cable) and link LED was
  still on! ifconfig showed me state: active with no cable plugged in.
  After further 30 seconds the LED went off.
 
  I attached the NIC again to the switch again and after 30 seconds
  again I got some other effect. The link LED went on (status: active)
  and the data LED was permanently blinking (about 2,5 times a second). I
  pulled the cable again and now the link LED is still on and the data
  LED still blinking (since about 10 minutes already).
 
  By the way...
  Now I'm typing this E-Mail without an ethernet cable plugged in and the
  link status LED is still on and the other data LED is blinking.
 
  --
  Martin
 
 I may have misunderstood the purpose of this, but do you have the bpf
 compiled into your kernel? If you're having DHCP troubles, this could
 be a problem.

 I have never seen device bpf cause any sort of DHCP-related problems
 on FreeBSD.

 Can you expand on this, and provide reference material confirming such?

 --
 | Jeremy Chadwickjdc at parodius.com |
 | Parodius Networking   http://www.parodius.com/ |
 | UNIX Systems Administrator  Mountain View, CA, USA |
 | Making life hard for others since 1977.  PGP: 4BD6C0CB |



Sorry, I was referring to the possible absence of it.

Ref:

http://www.freebsd.org/doc/en/books/handbook/network-dhcp.html , section 27.5.4:

Make sure that the bpf device is compiled into your kernel. To do
this, add device bpf to your kernel configuration file, and rebuild
the kernel.

Chris

-- 
R $h !  $- ! $+  $@ $2  @ $1 .UUCP. 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Failure building apache22 and mysql51

[Chris Rees]

2008/7/14 Sorin Pânca [EMAIL PROTECTED]:
 I'm sorry for my late response, I was on vacation.
 I think this was the case (although I thought we have only amd64 machines).
 Is there a way to recover from this situation by ssh access only?

 Thank you!
 Sorin.

 Chris Rees wrote:

 Date: Mon, 23 Jun 2008 18:43:04 +0300
 From: Sorin P?nca [EMAIL PROTECTED]


 Hello people!
 I recently upgraded a amd64 machine from FreeBSD-6.2-RELEASE-p11 to
 FreeBSD-7.0-RELEASE-p2 using the tutorial found at

 http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html
 All went well with the base system.

 I don't want to patronise, but are you sure you were running
 FreeBSD/amd64-6.2 before? Looks kinda like you've tried to upgrade
 from 6.2/i386 to 7.0/amd64. In case you have, you can't do that.

 Check you haven't disabled and processor-specific extensions in your
 BIOS, like SSE, that would also create problems if you have optimised
 your ports.

 Chris





 I thought devel/linuxthreads was using some old library so I tried to
 rebuild it:

 # cd ../../devel/linuxthreads  make install clean # portupgrade -f
 wouldn't do anything
 ===  linuxthreads-2.2.3_23 is only for i386, while you are running
 amd64.
 *** Error code 1

 Stop in /usr/ports/devel/linuxthreads.


 Any ideas what to do next?
 Thank you!

 Sorin.




If I understand you correctly, you want to revert to FreeBSD/i386; in
which case I'd advise that you are *extremely* careful, and make sure
that everything important is recompiled in i386; FreeBSD/amd64 can run
binaries from FreeBSD/i386, but not vice-versa.

I *think* that you should be ok running a source update (csup sources,
make buildworld installworld kernel) with arch as i386, then reboot,
pkg_delete -f portupgrade\*, pkg_add -r portupgrade, portupgrade -faP
etc

Don't take my word for it, it is beyond my expertise, I've
deliberately made it obtuse; get someone with more knowledge to
elucidate :P

Or, you could stick with /amd64.
-- 
R $h !  $- ! $+  $@ $2  @ $1 .UUCP.  (sendmail.cf)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

RE: MCP55 SATA data corruption in FreeBSD 7

[Chris Rees]

 Date: Wed, 2 Jul 2008 10:55:07 +0200
 Daniel Eriksson [EMAIL PROTECTED] wrote:
 Jeremy Chadwick wrote:

 Can the OP get some non-Samsung disks for testing?

 I've got a 750 GB Western Digital that I've been planning to use to
 verify if it's a SATA-150 / SATA-300 problem (it can be jumpered to
 SATA-150), but the drive is packed with valuable data that I'd have to
 move elsewhere first.

 I'll get to it eventually, but maybe not this week.

 ___
 Daniel Eriksson (http://www.toomuchdata.com/)


Looks like I'm the guinea pig for now, I'll post in about half an hour
with the results :)

This is a clean install; it works perfectly with the restriction
jumper on, now it comes off.

Chris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: MCP55 SATA data corruption in FreeBSD 7

[Chris Rees]

On 02/07/2008, Chris Rees [EMAIL PROTECTED] wrote:
  Date: Wed, 2 Jul 2008 10:55:07 +0200
   Daniel Eriksson [EMAIL PROTECTED] wrote:
   Jeremy Chadwick wrote:
  
   Can the OP get some non-Samsung disks for testing?
  
   I've got a 750 GB Western Digital that I've been planning to use to
   verify if it's a SATA-150 / SATA-300 problem (it can be jumpered to
   SATA-150), but the drive is packed with valuable data that I'd have to
   move elsewhere first.
  
   I'll get to it eventually, but maybe not this week.

 
   ___
   Daniel Eriksson (http://www.toomuchdata.com/)
  


 Looks like I'm the guinea pig for now, I'll post in about half an hour
  with the results :)

  This is a clean install; it works perfectly with the restriction
  jumper on, now it comes off.


  Chris


Real sorry fellas, can't reproduce on my M2N-SLI; chipset 570 SLI.
I've been building ports for hours on here, everything's working
perfectly I'm afraid.

# pciconf -lv

- snip -

[EMAIL PROTECTED]:0:5:0:class=0x010185 card=0x82391043 chip=0x037f10de
rev=0xa3 hdr=0x00
vendor = 'Nvidia Corp'
device = 'MCP55 SATA Controller'
class  = mass storage
subclass   = ATA

- snip -

# FreeBSD hydra.bayofrum.net 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #1:
Wed Jul  2 16:50:49 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/HYDRA  amd64


Looks like mine's hardware revision (rev=) 0xa3; yours however is 0xa2.

I had PS/2 port trouble on Linux, and needed a BIOS update, perhaps it
came with that? Is the revision a firmware or hardware property?

Good luck tracking that down, anyway, hope my tests helped :)

Chris

-- 
R $h !  $- ! $+  $@ $2  @ $1 .UUCP.  (sendmail.cf)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]