Re: Best 10Gbit/s card for FB 9.2

2013-10-07 Thread Albert Shih 
 Le 06/10/2013 à 18:24:27-0400, ill...@gmail.com a écrit
> On 6 October 2013 10:47, Albert Shih  wrote:
> > Hi,
> >
> > I would like to known what is the best 10 Gbits/s copper ethernet card for
> > FreeBSD 9.2 on Dell hardware :
> >
> > I got on the Dell's website
> >
> >
> >
> > Broadcom 57800 2x10Gb BT + 2x1Gb BT Network Daughter Card
> >
> > Broadcom 57810 DP 10Gb BT Converged Network Adapter
> >
> > Intel Ethernet X540 10Gb BT DP + i350 1Gb BT DP Network Daughter Card
> >
> > Intel Ethernet X540 DP 10GBASE-T Server Adapter, Low Profile
> >
> 
> It looks like (from grepping around) that the BCE578xx are only
> supported on FreeBSD 10 (bxe(4)).  The Intel adapter looks to be
> supported on 9.2 as ixgbe(4) which is in the GENERIC kernel & so
> should (cross fingers) work "out of the box".

Lots of thanks.

When I got my server I send here the result to confirm (or not) the
support. 

Regards.

JAS
-- 
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: j...@obspm.fr
Heure local/Local time:
lun 7 oct 2013 10:06:00 CEST
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

FreeBSD 9.2 - does not appear to support the 'dc' PCMCIA NIC driver

2013-10-07 Thread Kent Kuriyama 
I have a Netgear FA511 PCMCIA NIC that worked fine under 9.1.  Under 9.2 I
get the following message:

Oct  6 21:38:11 monitor4 kernel: dc0:  port 0x1100-0x11ff irq 19 at device 0.0 on cardbus0
Oct  6 21:38:11 monitor4 kernel: dc0: attaching PHYs failed

This used to work under 9.1, does anyone know what happened?  Thanks.

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

init(8) not executing everything cron, getty on some hosts

2013-10-07 Thread Julian Fagir 
Hi,

I've been experiencing a strange problem with one of my hosts (I think, since
upgrading to 9.1-RELEASE). The host does not start several services after
booting, especially no getty(8)s and no cron(8). When starting these services
manually, it does so without flaw (you can login via ssh).
I thought about that maybe being a hardware failure, as this host also
refuses to boot 9.2-RELEASE because of something timer-specific.

Now, upgrading two other hosts to 9.2-RELEASE, one of them with the same
hardware, they suddenly show the same behaviour: No getty(8)s are started
(though by hand, it works), no cron (by hand, again, it works), and on one
host no kdc (again, by hand you can start it).
On the other hand, another host upgraded to 9.2-RELEASE behaves as it should,
starting all services.
On the console, there are no errors, there is just no further message after
the last service (ntpd or sshd) is started.
I don't think it's a hardware issue, as one of the three machines runs on
different hardware than the other two (which are identical).

Everything is as standard as possible.
My ttys(5) is the standard one (comments and serial line left out):

> console noneunknown off secure
> ttyv0   "/usr/libexec/getty Pc" xterm   on secure
> ttyv1   "/usr/libexec/getty Pc" xterm   on secure
> ttyv2   "/usr/libexec/getty Pc" xterm   on secure
> ttyv3   "/usr/libexec/getty Pc" xterm   on secure
> ttyv4   "/usr/libexec/getty Pc" xterm   on secure
> ttyv5   "/usr/libexec/getty Pc" xterm   on secure
> ttyv6   "/usr/libexec/getty Pc" xterm   on secure
> ttyv7   "/usr/libexec/getty Pc" xterm   on secure
> ttyv8   "/usr/local/bin/xdm -nodaemon"  xterm   off secure   

My rc.conf(5) (this should not affect starting gettys), the second host does
not even have jails:

> fsck_y_enable="YES"
> dumpdev="AUTO"
> ip_kerberos2="XXX"
> ip_ldap1="XXX"
> hostname="XXX"
> ipv4_addrs_bge0="XXX $ip_ldap1 $ip_kerberos2"
> defaultrouter="XXX"
> ezjail_enable="YES"
> jail_flags="-s 3"
> nfs_client_enable="YES"
> rpcbind_enable="YES"
> rpc_statd_enable="YES"
> rpc_lockd_enable="YES"
> kerberos5_server_enable="YES"
> saslauthd_enable="YES"
> saslauthd_flags="-a kerberos5"
> slapd_enable="YES"
> slapd_flags='-c 147 -h "ldapi://%2fvar%2frun%2fopenldap%2fldapi/ ldap:///
ldaps:///"'
> slapd_sockets="/var/run/openldap/ldapi"
> slapd_sockets_mode="666"
> nrpe2_enable="YES"
> nut_upsmon_enable="YES"
> munin_node_enable="YES"
> sshd_enable="YES"
> ntpd_enable="YES"
> ntpd_sync_on_start="YES"
> fscd_enable="YES"
> bsdstats_enable="YES"   

Do you have any clues what could have gone wrong? freebsd-update's IDS does
not show any wrong checksums.

Regards, Julian


signature.asc
Description: PGP signature

Re: init(8) not executing everything cron, getty on some hosts

2013-10-07 Thread Julian Fagir 
Hi,

On Mon, 7 Oct 2013 10:47:09 +0200 Julian Fagir wrote:
> I don't think it's a hardware issue, as one of the three machines runs on
> different hardware than the other two (which are identical).

I have to update on that: The two servers with the identical hardware are the
ones with the "real" issue. It's about a Proliant DL385 G1.
The other one just got into an inconsistent state with the update, thinking
it's with 9.2-RELEASE, but apparently not having upgraded anything.

Regards, Julian


signature.asc
Description: PGP signature

Re: No Sound from Firefox

2013-10-07 Thread Jerry 
On Mon, 07 Oct 2013 05:08:09 +0200
Bernt Hansson articulated:

> On 2013-10-06 21:31, Jerry wrote:
> > $ /usr/local/bin/firefox
> >
> > (process:71385): GLib-CRITICAL **: g_slice_set_config: assertion
> > `sys_page_size == 0' failed
> >
> > This is all I could gather.
> >
> I get the same for firefox and thunderbird
> 
> % firefox &
> [1] 37788
> %
> (process:37788): GLib-CRITICAL **: g_slice_set_config: assertion 
> `sys_page_size == 0' failed
> 
> % thunderbird &
> [2] 38745
> %
> (process:38745): GLib-CRITICAL **: g_slice_set_config: assertion 
> `sys_page_size == 0' failed
> 
> My guess it's related to glib.

I did a quick check with other users of FreeBSD & Firefox and they all
reported the same thing. Either the error is harmless or the FreeBSD
team doesn't give a crap about it. Either way, I would like to see some
sort of an official statement on it. Something along the lines of why
it cannot be corrected or is safe to ignore. A list of side effects
would be nice to.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__



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

How do I ring a bell?

2013-10-07 Thread Frank Leonhardt 
In the good'ol days I could make UNIX ring a bell (literally) by sending 
\a to the console TTY (an ASR33 in my case). Now there's an electronic 
synthesised ting or beep from an terminal emulator IF it's got a sound 
card and so on, and an IBM-PC had a beep routine in the BIOS.


Is there any way to make a noise through the built in "bell" speaker 
found on an IBM PC compatible server box? Writing 007 to the BIOS cout 
routine might do it, but I've realised I haven't got a clue how to do that.


I could easily knock up a bit of hardware to go on a serial port (or 
similar) that could be triggered to make a noise, but these things have 
already got the hardware built in and I'm looking to use what I've 
already got.


Thanks, Frank.

P.S. "cdcontrol -f /dev/mycdrom eject" is the best I've come up with so 
far for getting attention.


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

Re: How do I ring a bell?

2013-10-07 Thread Peter Boosten 

On 7 okt. 2013, at 13:37, Frank Leonhardt  wrote:

> In the good'ol days I could make UNIX ring a bell (literally) by sending \a 
> to the console TTY (an ASR33 in my case). Now there's an electronic 
> synthesised ting or beep from an terminal emulator IF it's got a sound card 
> and so on, and an IBM-PC had a beep routine in the BIOS.
> 
> Is there any way to make a noise through the built in "bell" speaker found on 
> an IBM PC compatible server box? Writing 007 to the BIOS cout routine might 
> do it, but I've realised I haven't got a clue how to do that.
> 
> I could easily knock up a bit of hardware to go on a serial port (or similar) 
> that could be triggered to make a noise, but these things have already got 
> the hardware built in and I'm looking to use what I've already got.
> 
> Thanks, Frank.
> 
> P.S. "cdcontrol -f /dev/mycdrom eject" is the best I've come up with so far 
> for getting attention.
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


echo "CTRL-V CTRL-G" should do the trick 

-- 
Peter Boosten
http://www.boosten.org


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

Re: How do I ring a bell?

2013-10-07 Thread Polytropon 
On Mon, 07 Oct 2013 12:37:35 +0100, Frank Leonhardt wrote:
> In the good'ol days I could make UNIX ring a bell (literally) by sending 
> \a to the console TTY (an ASR33 in my case).

Ah, the famous ^G control character... :-)



> Now there's an electronic 
> synthesised ting or beep from an terminal emulator IF it's got a sound 
> card and so on, and an IBM-PC had a beep routine in the BIOS.

The terminal beep routine will primarily address the system's
speaker (located at or connected to the mainboard). A side
effect on the sound card is possible (the Logitech SoundMan
did have that feature), but it's not really in relation.



> Is there any way to make a noise through the built in "bell" speaker 
> found on an IBM PC compatible server box? Writing 007 to the BIOS cout 
> routine might do it, but I've realised I haven't got a clue how to do that.

Making it audible is part of the local terminal emulator,
either the TTY (text mode) driver or via xterm (or the
preferred alternative terminal emulator in X).

A simple

printf "\a"

from the shell prompt should be sufficient. Note that if
you're running this in X, you have to make sure the bell
is not disabled. For example, put

xset b 100 1000 15

in your ~/.xinitrc (or ~/.xsession respectively).

A more sophisticated interface is provided as soon as your
kernel has

device speaker

compiled in (or speaker.ko has been loaded). Now you can
play wonderful music through the speaker. :-)

See "man 4 speaker" for details.

See the following shell script as an example of what you
can do:

#!/bin/sh
read -p "CW ===> " TEXT
echo ${TEXT} | morse | awk '{
if(length($0) == 0)
printf("P4\n");
else {
gsub(" dit", "P32L32E", $0);
gsub(" di",  "P32L32E", $0);
gsub(" dah", "P32L8E",  $0);
printf("%sP16\n", $0);
}
}' | dd bs=256 of=/dev/speaker > /dev/null 2>&1

Feel free to add support for reading from stdin so you can
listen to your console messages piped into the script. :-)

Always make sure that the system actually _has_ got an
internal speaker! I assume that modern PC hardware could
have it removed along with floppy drive connector, parallel
port or power switch.



> P.S. "cdcontrol -f /dev/mycdrom eject" is the best I've come up with so 
> far for getting attention.

That's a really clever idea, never heared of that. It has
the advantage of being permanent because the drive will
stay open when the sound of its motor has finished. :-)


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: How do I ring a bell?

2013-10-07 Thread Frank Leonhardt 

On 07/10/2013 13:06, Peter Boosten wrote:


On 7 okt. 2013, at 13:37, Frank Leonhardt > wrote:


In the good'ol days I could make UNIX ring a bell (literally) by 
sending \a to the console TTY (an ASR33 in my case). Now there's an 
electronic synthesised ting or beep from an terminal emulator IF it's 
got a sound card and so on, and an IBM-PC had a beep routine in the BIOS.


Is there any way to make a noise through the built in "bell" speaker 
found on an IBM PC compatible server box? Writing 007 to the BIOS 
cout routine might do it, but I've realised I haven't got a clue how 
to do that.


I could easily knock up a bit of hardware to go on a serial port (or 
similar) that could be triggered to make a noise, but these things 
have already got the hardware built in and I'm looking to use what 
I've already got.


Thanks, Frank.

P.S. "cdcontrol -f /dev/mycdrom eject" is the best I've come up with 
so far for getting attention.


___
freebsd-questions@freebsd.org  
mailing list

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


echo "CTRL-V CTRL-G" should do the trick

Alas, not. The console driver won't ring the BIOS bell on anything I've 
tried. It might on a desktop with a built-in sound card and speakers, 
but it won't do anything with the "beep" speaker. It's actually the same 
solution I mentioned in the first line (\a translates to 007 which is 
ctrl-G).


Then there's the issue of writing it to the console rather than a 
virtual terminal, but I have a few hacks that'll achieve that part.


IIRC there was once a FreeBSD kernel module to drive the PC speaker 
(through /dev/pcspeaker or similar), but it seems to have gone or I'm 
confusing it with another BSD (or Linux).


No I'm not. /usr/src/sys/dev/speaker/spkr.c(!) I may be close to a 
solution...


Regards, Frank.

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

Re: How do I ring a bell?

2013-10-07 Thread Steve O'Hara-Smith 
On Mon, 07 Oct 2013 12:37:35 +0100
Frank Leonhardt  wrote:

> In the good'ol days I could make UNIX ring a bell (literally) by sending 
> \a to the console TTY (an ASR33 in my case). Now there's an electronic 
> synthesised ting or beep from an terminal emulator IF it's got a sound 
> card and so on, and an IBM-PC had a beep routine in the BIOS.

Try this:

echo ^G > /dev/console

You'll have to type ^V^G to get a real ^G in the command line
(^ means control of course).

-- 
Steve O'Hara-Smith 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: How do I ring a bell?

2013-10-07 Thread Leslie Jensen 



Frank Leonhardt skrev 2013-10-07 13:37:

In the good'ol days I could make UNIX ring a bell (literally) by sending
\a to the console TTY (an ASR33 in my case). Now there's an electronic
synthesised ting or beep from an terminal emulator IF it's got a sound
card and so on, and an IBM-PC had a beep routine in the BIOS.

Is there any way to make a noise through the built in "bell" speaker
found on an IBM PC compatible server box? Writing 007 to the BIOS cout
routine might do it, but I've realised I haven't got a clue how to do that.

I could easily knock up a bit of hardware to go on a serial port (or
similar) that could be triggered to make a noise, but these things have
already got the hardware built in and I'm looking to use what I've
already got.

Thanks, Frank.

P.S. "cdcontrol -f /dev/mycdrom eject" is the best I've come up with so
far for getting attention.

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




You also have the audio/yell port.




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

Re: How do I ring a bell?

2013-10-07 Thread RW 
On Mon, 07 Oct 2013 13:46:53 +0100
Frank Leonhardt wrote:


> Alas, not. The console driver won't ring the BIOS bell on anything
> I've tried. It might on a desktop with a built-in sound card and
> speakers, but it won't do anything with the "beep" speaker.

Are you sure you have one? The last two cases I bought didn't.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: How do I ring a bell?

2013-10-07 Thread Steve O'Hara-Smith 
On Mon, 07 Oct 2013 13:46:53 +0100
Frank Leonhardt  wrote:

> Then there's the issue of writing it to the console rather than a 
> virtual terminal, but I have a few hacks that'll achieve that part.

/dev/console is your friend.

-- 
Steve O'Hara-Smith 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

OpenBSD at vBSDcon October 25 - 27, 2013 in Herndon, VA

2013-10-07 Thread Miller, Vincent (Rick) 
For only USD$75 you can register for vBSDcon hosted by Verisign on October 25 – 
27, 2013 in Herndon, VA.  That is less than 3 weeks away!  If you have not 
registered yet, it is definitely recommended as vBSDcon will feature a series 
of roundtable discussions, educational sessions, best practice conversations, 
and exclusive networking opportunities.  Registrations for vBSDcon will be open 
until October 23, 2013 at http://www.vbsdcon.com/.

vBSDcon will feature developers, Henning Brauer and Reyk Floeter, from the 
OpenBSD project.  Henning and Reyk will be tag teaming a presentation on packet 
inspection with pf in OpenBSD.  pf was introduced in 2001 as an alternative to 
ipf. Over the years, pf has become a mature, secure, and powerful, yet easy to 
use high performance packet filter. In this presentation, Henning Brauer will 
describe some of the features of pf and Reyk Floeter will describe utilizing 
relayd in conjunction with pf. You can expect to hear about using hooks for 
transparent proxies, deep packet inspection, socket splicing, NATs, load 
balancing and more.

Read more about our speakers and their topics, the conference agenda, other 
activities, and registrations at http://www.vbsdcon.com/.  This is an event you 
will not want to miss.  Register now before it's too late!

Follow @VERISIGN and @hostileaddmin on Twitter for more news and updates on 
#vBSDcon

--
Vincent (Rick) Miller
Systems Engineer
vmil...@verisign.com

t: 703-948-4395  m: 703-581-3068
12061 Bluemont Way, Reston, VA  20190

http://www.vbsdcon.com
http://www.verisigninc.com

“This message (including any attachments) is intended only for the use of the 
individual or entity to which it is addressed, and may contain information that 
is non-public, proprietary, privileged, confidential and exempt from disclosure 
under applicable law or may be constituted as attorney work product. If you are 
not the intended recipient, you are hereby notified that any use, 
dissemination, distribution, or copying of this communication is strictly 
prohibited. If you have received this message in error, notify sender 
immediately and delete this message immediately.”
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: munin related

2013-10-07 Thread Dan Nelson 
In the last episode (Oct 05), Laszlo Danielisz said:
> Today while trying to install munin-node on 9.2 from ports I keep getting
> the following error:
> 
> ===>  Checking if sysutils/munin-common already installed
> ===> Creating users and/or groups.
> Using existing group `munin'.
> Creating user `munin' with uid `842'.
> pw: user 'munin' already exists
> *** [create-users-groups] Error code 74
> 
> Stop in /usr/ports/sysutils/munin-common.
> *** [build-depends] Error code 1
> 
> Stop in /usr/ports/sysutils/munin-node.
> *** [build] Error code 1
> 
> Stop in /usr/ports/sysutils/munin-node.
> 
> 
> Do you have any  idea what can cause this?
> The ports are up to date.

Do you have nscd caching enabled?  It sometimes doesn't realize immediately
that users/groups have been added to the system.  Try restarting nscd, or
disabling it temporarily while you install.

-- 
Dan Nelson
dnel...@allantgroup.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: munin related

2013-10-07 Thread Laszlo Danielisz 
Dear Dan, 

Yep killing nscd help me to get out of this trouble.

Thank you very much! 

-- 
Laszlo Danielisz



On 2013 October 7 Monday at 5:55 PM, Dan Nelson wrote:

> In the last episode (Oct 05), Laszlo Danielisz said:
> > Today while trying to install munin-node on 9.2 from ports I keep getting
> > the following error:
> > 
> > ===>  Checking if sysutils/munin-common already installed
> > ===> Creating users and/or groups.
> > Using existing group `munin'.
> > Creating user `munin' with uid `842'.
> > pw: user 'munin' already exists
> > *** [create-users-groups] Error code 74
> > 
> > Stop in /usr/ports/sysutils/munin-common.
> > *** [build-depends] Error code 1
> > 
> > Stop in /usr/ports/sysutils/munin-node.
> > *** [build] Error code 1
> > 
> > Stop in /usr/ports/sysutils/munin-node.
> > 
> > 
> > Do you have any  idea what can cause this?
> > The ports are up to date.
> > 
> 
> 
> Do you have nscd caching enabled? It sometimes doesn't realize immediately
> that users/groups have been added to the system. Try restarting nscd, or
> disabling it temporarily while you install.
> 
> -- 
> Dan Nelson
> dnel...@allantgroup.com (mailto:dnel...@allantgroup.com)
> ___
> freebsd-questions@freebsd.org (mailto:freebsd-questions@freebsd.org) mailing 
> list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org 
> (mailto:freebsd-questions-unsubscr...@freebsd.org)"
> 
> 


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

Re: munin related

2013-10-07 Thread Mark Felder 
On Mon, Oct 7, 2013, at 12:57, Laszlo Danielisz wrote:
> Dear Dan, 
> 
> Yep killing nscd help me to get out of this trouble.
> 
> Thank you very much! 
> 

Some day it might be feasible to tie a hook into pkg that clears the
uid/gid cache in nscd when trying to install packages so this isn't a
problem.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread alexus 
bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 7.4-RELEASE from update4.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
kernel/generic src/base src/bin src/cddl src/contrib src/crypto src/etc
src/games src/gnu src/include src/krb5 src/lib src/libexec src/release
src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin
src/usbin world/base world/dict world/doc world/games world/info
world/lib32 world/manpages world/proflibs

The following components of FreeBSD do not seem to be installed:
world/catpages

Does this look reasonable (y/n)? y

Fetching metadata signature for 7.4-RELEASE-p12 from update4.freebsd.org...
failed.
Fetching metadata signature for 7.4-RELEASE-p12 from update5.freebsd.org...
failed.
Fetching metadata signature for 7.4-RELEASE-p12 from update6.freebsd.org...
failed.
Fetching metadata signature for 7.4-RELEASE-p12 from update2.freebsd.org...
failed.
Fetching metadata signature for 7.4-RELEASE-p12 from update3.freebsd.org...
failed.
No mirrors remaining, giving up.
bash-4.2# uname -a
FreeBSD XX.X.org 7.4-RELEASE-p5 FreeBSD 7.4-RELEASE-p5 #0: Fri Dec 23
17:36:54 UTC 2011 r...@xx.x.org:/usr/obj/usr/src74/sys/GENERIC
amd64
bash-4.2#

Is there a way to upgrade 7.4-RELEASE-p5 to 7.4-RELEASE-p12 using
freebsd-update now?

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

Re: How do I ring a bell?

2013-10-07 Thread Frank Leonhardt 

On 07/10/2013 14:31, RW wrote:

On Mon, 07 Oct 2013 13:46:53 +0100
Frank Leonhardt wrote:



Alas, not. The console driver won't ring the BIOS bell on anything
I've tried. It might on a desktop with a built-in sound card and
speakers, but it won't do anything with the "beep" speaker.

Are you sure you have one? The last two cases I bought didn't.



They beep when you turn them on and they're ready to boot :-)

/dev/speaker appears to be the answer.

Thanks, Frank.

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

Re: How do I ring a bell?

2013-10-07 Thread Warren Block 

On Mon, 7 Oct 2013, Frank Leonhardt wrote:

On 07/10/2013 13:06, Peter Boosten wrote:


echo "CTRL-V CTRL-G" should do the trick


Or, more easily, printf "\a".

Alas, not. The console driver won't ring the BIOS bell on anything I've 
tried. It might on a desktop with a built-in sound card and speakers, but it 
won't do anything with the "beep" speaker. It's actually the same solution I 
mentioned in the first line (\a translates to 007 which is ctrl-G).


Make sure hw.syscons.bell is set to 1.  It can be changed at run time, 
like in /etc/sysctl.conf.  Some systems have it disabled (set to 0) 
because the bell is amazingly loud and piercing.  (Looking at you, 
Dell.)

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

Re: How do I ring a bell?

2013-10-07 Thread Frank Leonhardt 

On 07/10/2013 13:36, Polytropon wrote:

> Is there any way to make a noise through the built in "bell" speaker
> found on an IBM PC compatible server box? Writing 007 to the BIOS cout
> routine might do it, but I've realised I haven't got a clue how to 
do that.

> Making it audible is part of the local terminal emulator,
> either the TTY (text mode) driver or via xterm (or the
> preferred alternative terminal emulator in X).

Yers, but I'm not running X. Or a character terminal come to that :-)

>
> A more sophisticated interface is provided as soon as your
> kernel has
>
> device speaker
>
> compiled in (or speaker.ko has been loaded). Now you can
> play wonderful music through the speaker. :-)
>
> See "man 4 speaker" for details.

Thanks! This is what I was looking for.

> See the following shell script as an example of what you
> can do: 

Overkill. I have proper work to do rather than working out how to play 
appropriate bit silly little tunes for every eventuality. Actually 
spkr.c has some useful comments in it - apparently it works the same as 
IBM PC BASIC. Now how do I make it polyphonic...



> Always make sure that the system actually _has_ got an
> internal speaker! I assume that modern PC hardware could
> have it removed along with floppy drive connector, parallel
> port or power switch.

Remains to be seen, but most still seem to have one so the BIOS ROM can 
make "beep" diagnostic codes if it can't do anything else.


>> P.S. "cdcontrol -f /dev/mycdrom eject" is the best I've come up with so
>> far for getting attention.
> That's a really clever idea, never heared of that. It has
> the advantage of being permanent because the drive will
> stay open when the sound of its motor has finished. :-)

I use it all the time, especially when directing a tech to the 
appropriate server in a rack. "It's the one I just popped the CD drive 
on". These days servers have the spring-loaded notebook drives instead 
of the motorised trays, which is a pity. You could keep winding the 
motorised ones in and out until someone spotted it. I suppose if you did 
it energetically enough it might catch fire and set off the smoke alarm 
(audible). Or leave it wound out with a tin can balanced on it; to make 
a noise wind it back in and hear it clatter to the floor.


(Incidentally - email over-lap because earlier reply posted to me and 
list rather than just list)


Regards, Frank.

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

Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread Andreas Rudisch 
On Mon, 7 Oct 2013 15:22:17 -0400
alexus  wrote:

> bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12

> Is there a way to upgrade 7.4-RELEASE-p5 to 7.4-RELEASE-p12 using
> freebsd-update now?

What about:
# freebsd-update fetch
# freebsd-update install

http://www.freebsd.org/security/

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

Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread Mark Felder 
On Mon, Oct 7, 2013, at 14:22, alexus wrote:
> bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12

Just freebsd-update fetch && freebsd-update install is all you should
have to run. The -r flag is for jumping major releases (from 7.x to 8.x,
for example).

I can't comment on whether or not the freebsd-update data for 7.x is
still on the servers, though.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread alexus 
ok, I just did fetch & install and got bumped from p5 to p9

# uname -a
FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11
19:47:58 UTC 2012
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
 amd64
#

can I take it all the way to -p12? (I'm running fetch again, hoping it will
do that)



On Mon, Oct 7, 2013 at 4:16 PM, Mark Felder  wrote:

> On Mon, Oct 7, 2013, at 14:22, alexus wrote:
> > bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
>
> Just freebsd-update fetch && freebsd-update install is all you should
> have to run. The -r flag is for jumping major releases (from 7.x to 8.x,
> for example).
>
> I can't comment on whether or not the freebsd-update data for 7.x is
> still on the servers, though.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscr...@freebsd.org"
>



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

Re: freebsd-update upgrade -r 7.4-RELEASE-p12

2013-10-07 Thread alexus 
it didn't help..

# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 7.4-RELEASE from update6.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

The following files are affected by updates, but no changes have
been downloaded because the files have been modified locally:
/var/db/mergemaster.mtree

No updates needed to update system to 7.4-RELEASE-p12.

WARNING: FreeBSD 7.4-RELEASE-p9 HAS PASSED ITS END-OF-LIFE DATE.
Any security issues discovered after Fri Mar  1 00:00:00 UTC 2013
will not have been corrected.
# freebsd-update install
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
#



On Mon, Oct 7, 2013 at 5:13 PM, alexus  wrote:

> ok, I just did fetch & install and got bumped from p5 to p9
>
> # uname -a
> FreeBSD XX.X.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11
> 19:47:58 UTC 2012 
> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
>  amd64
> #
>
> can I take it all the way to -p12? (I'm running fetch again, hoping it
> will do that)
>
>
>
> On Mon, Oct 7, 2013 at 4:16 PM, Mark Felder  wrote:
>
>> On Mon, Oct 7, 2013, at 14:22, alexus wrote:
>> > bash-4.2# freebsd-update upgrade -r 7.4-RELEASE-p12
>>
>> Just freebsd-update fetch && freebsd-update install is all you should
>> have to run. The -r flag is for jumping major releases (from 7.x to 8.x,
>> for example).
>>
>> I can't comment on whether or not the freebsd-update data for 7.x is
>> still on the servers, though.
>> ___
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "
>> freebsd-questions-unsubscr...@freebsd.org"
>>
>
>
>
> --
> http://alexus.org/
>



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

failed to create gmirror with the handbook instructions

2013-10-07 Thread Andy Zammy 
Hi,

I used the second section of the handbook (20.4) to create a gmirror. In my
particular setup I had a 1GB /, 6GB swap, 1GB /tmp and the rest of the 1TB
drive was left for /usr

I had to deviate from the handbook when it came to running the dump +
restore commands, as the dump failed due to an issue with the journalling.
To get around this problem, I dropped into single user mode, so I could
remount root as read-only. The dump commands then worked. It specified in
the handbook to restart the machine, and boot from ada1.

It was at this point that I noticed something wasn't quite right. There was
a spew of 'not found/no such file or directory' messages. These were all
trying to reference libs and binaries that live in /usr.

I boot into single user mode, and upon checking the other partitions, I
notice that /tmp and /usr are empty, apart from a .snap file, and the
restoresymtable file.

Please could someone help me troubleshoot this problem? Let me know if you
need any more info, and I'll post it up asap.

Kind Regards

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

Re: failed to create gmirror with the handbook instructions

2013-10-07 Thread Warren Block 

On Tue, 8 Oct 2013, Andy Zammy wrote:


Hi,

I used the second section of the handbook (20.4) to create a gmirror. In my
particular setup I had a 1GB /, 6GB swap, 1GB /tmp and the rest of the 1TB
drive was left for /usr

I had to deviate from the handbook when it came to running the dump +
restore commands, as the dump failed due to an issue with the journalling.
To get around this problem, I dropped into single user mode, so I could
remount root as read-only. The dump commands then worked. It specified in
the handbook to restart the machine, and boot from ada1.

It was at this point that I noticed something wasn't quite right. There was
a spew of 'not found/no such file or directory' messages. These were all
trying to reference libs and binaries that live in /usr.

I boot into single user mode, and upon checking the other partitions, I
notice that /tmp and /usr are empty, apart from a .snap file, and the
restoresymtable file.

Please could someone help me troubleshoot this problem? Let me know if you
need any more info, and I'll post it up asap.


dump does not work reliably on filesystems with SUJ enabled.  Turn off 
SUJ on the filesystems to be dumped by booting in single-user mode and 
running

  tunefs -j disable /dev/ada0whatever

Do each filesystem, then use dump.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

jabberd14 crashes if built with Clang 3.3

2013-10-07 Thread other 

Hi Guys,

Just following up on a previous post (have changed the subject as this 
is a port specific issue that has cropped up since upgrading from 
9.1-RELEASE (amd64) to 9.2-RELEASE (amd64)).


This is interesting. I recompiled this port without Clang (using the 
base gcc) and it has not crashed once since (sig 10 bus error crashes 
are gone). Funnily enough, in FreeBSD 9.1-RELEASE, the same port 
compiled with Clang 3.1 did not crash ever. So the culprit has to be 
Clang 3.3.


I have the following in my /etc/make.conf (for clang building):

root@srv:~ # cat /etc/make.conf
NO_PROFILE=true
CC=clang
CXX=clang++
CPP=clang-cpp

Whilst building the port with the base compiler is a workaround, it's 
not a long term solution, since Clang will be the default Compiler in 
the not so distant future.


What is even more annoying is the lack of a port maintainer for 
net-im/jabber:


MAINTAINER= po...@freebsd.org
COMMENT=XMPP/Jabber server daemon

I assume the above email is just a generic email address for ports who 
do not have a maintainer?


Any suggestions what to do from here?

Kind Regards,
Alex.


On 2013-10-02 09:54, ot...@ahhyes.net wrote:



* /usr/ports/net/net-im/jabber (which appears not to have changed
versions between my system upgrade) randomly
aborts with signal 10 (bus error).

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

Re: How do I ring a bell?

2013-10-07 Thread Polytropon 
On Mon, 07 Oct 2013 21:09:44 +0100, Frank Leonhardt wrote:
> On 07/10/2013 13:36, Polytropon wrote:
> > > Is there any way to make a noise through the built in "bell" speaker
> > > found on an IBM PC compatible server box? Writing 007 to the BIOS cout
> > > routine might do it, but I've realised I haven't got a clue how to 
> > do that.
>  > Making it audible is part of the local terminal emulator,
>  > either the TTY (text mode) driver or via xterm (or the
>  > preferred alternative terminal emulator in X).
> 
> Yers, but I'm not running X. Or a character terminal come to that :-)

In that case, something line

printf "\a" > /dev/console

should work - I've just tried it. You can do that from a
shell script or maybe even via fprintf() from your own code.



>  > See the following shell script as an example of what you
>  > can do: 
> 
> Overkill. I have proper work to do rather than working out how to play 
> appropriate bit silly little tunes for every eventuality. Actually 
> spkr.c has some useful comments in it - apparently it works the same as 
> IBM PC BASIC. Now how do I make it polyphonic...

By adding more computers. This is the established solution
to _every_ IT-related problem. :-)

The code in /usr/src/sys/dev/speaker/spkr.c provides a more
streamlined interface to sound generation. It's even more
"bare metal" than what I remember from Borland Turbo-C:

sound(1000);
delay(2500);
nosound();

It was important not to miss the 3rd line or the "fun" would
never end. :-)



>  > Always make sure that the system actually _has_ got an
>  > internal speaker! I assume that modern PC hardware could
>  > have it removed along with floppy drive connector, parallel
>  > port or power switch.
> 
> Remains to be seen, but most still seem to have one so the BIOS ROM can 
> make "beep" diagnostic codes if it can't do anything else.

This proves that it is present, even if it's not an attached
speaker anymore. Many mainboards contain a little piezo speaker
directly mounted (my ultracheap home PC does, for example).



>  >> P.S. "cdcontrol -f /dev/mycdrom eject" is the best I've come up with so
>  >> far for getting attention.
>  > That's a really clever idea, never heared of that. It has
>  > the advantage of being permanent because the drive will
>  > stay open when the sound of its motor has finished. :-)
> 
> I use it all the time, especially when directing a tech to the 
> appropriate server in a rack. "It's the one I just popped the CD drive 
> on". These days servers have the spring-loaded notebook drives instead 
> of the motorised trays, which is a pity. You could keep winding the 
> motorised ones in and out until someone spotted it.

This seems to be better than those "slot-in" drives I had
in one server: no moving parts to the outside.



> I suppose if you did 
> it energetically enough it might catch fire and set off the smoke alarm 
> (audible).

This procedure has been part of an independent quality test
of CD recorders, performed by a PC maganzine many years ago.
Interesting result: the cheapest drive would last longer than
the most expensive one in which the gears automatically had
disassembled. :-)



> Or leave it wound out with a tin can balanced on it; to make 
> a noise wind it back in and hear it clatter to the floor.

Interesting use for the "4X cup holder". :-)



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

NAT: Handbook vs mailing list

2013-10-07 Thread Chris Stankevitz 
http://www.freebsd.org/doc/handbook/network-natd.html

http://lists.freebsd.org/pipermail/freebsd-questions/2011-April/229017.html

Hello,

Handbook section 31.9.3 suggests I should, among other things, add the
line ipdivert_load="YES" to /boot/loader.conf when setting up NAT.

The mailing list message linked above suggests that the handbook
information is the "old way" and that the correct way is to set
ipfw_enable and natd_enable in rc.conf.  "Then /etc/rc.d/ipfw will
load ipfw.ko, and if natd_enable is set, will invoke /etc/rc.d/natd,
which loads ipdivert.ko at the right time."

My inclination is to follow the handbook, but I thought I should first
check to ensure the handbook is up-to-date.

Thank you,

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

Re: NAT: Handbook vs mailing list

2013-10-07 Thread Olivier Nicole 
Chris,

On Tue, Oct 8, 2013 at 11:21 AM, Chris Stankevitz
 wrote:
> http://www.freebsd.org/doc/handbook/network-natd.html
>
> http://lists.freebsd.org/pipermail/freebsd-questions/2011-April/229017.html
>
> Hello,
>
> Handbook section 31.9.3 suggests I should, among other things, add the
> line ipdivert_load="YES" to /boot/loader.conf when setting up NAT.
>
> The mailing list message linked above suggests that the handbook
> information is the "old way" and that the correct way is to set
> ipfw_enable and natd_enable in rc.conf.  "Then /etc/rc.d/ipfw will
> load ipfw.ko, and if natd_enable is set, will invoke /etc/rc.d/natd,
> which loads ipdivert.ko at the right time."

>From what you copied/explained, natd_enable will load ipdivert.ko and
the handbook suggests that you load ipdivert.ko, so either way the
module will be loaded.

I'd go with the ipfw_enable and natd_enable as it may also do other
needed things than just loading a kernel module.

best regards,

Olivier

> My inclination is to follow the handbook, but I thought I should first
> check to ensure the handbook is up-to-date.
>
> Thank you,
>
> Chris
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: munin related

2013-10-07 Thread Trond Endrestøl 
On Mon, 7 Oct 2013 19:57+0200, Laszlo Danielisz wrote:

> Yep killing nscd help me to get out of this trouble.

I have long suspected nscd to reinitialise the timers whenever an 
entry is requested while still held in the cache, be it a positive or 
a negative result.

As such the only reasonable solution is to never cache negative 
results (TTL=0) and keep the positive TTL relatively short, say no 
more than 60 minutes.

Can someone more knowledgeable on nscd internals confirm my suspicion?

-- 
+---++
| Vennlig hilsen,   | Best regards,  |
| Trond Endrestøl,  | Trond Endrestøl,   |
| IT-ansvarlig, | System administrator,  |
| Fagskolen Innlandet,  | Gjøvik Technical College, Norway,  |
| tlf. mob.   952 62 567,   | Cellular...: +47 952 62 567,   |
| sentralbord 61 14 54 00.  | Switchboard: +47 61 14 54 00.  |
+---++___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"