HEADS UP: FreeBSD 6.3 EoL coming soon

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, On January 31st, FreeBSD 6.3 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of this release are strongly encouraged to upgrade to a newer release before that date -- more conservative users will

Re: Cannot list a particular directory through NFS with UDP

Rick, Thanks for your time on this. On Thu, Dec 31, 2009 at 02:23:32PM -0500, Rick Macklem wrote: > [stuff snipped] > >> This appears to be the reply to the nfs readdir request, which is what > >> would be expected. It could be a problem with the content or the reply > >> or a NetBSD client issue

Re: cvsweb: src/UPDATING on RELENG_7

Le 1/01/2010 16:40, Ian Smith a écrit : Hi, Thought I had a clue on using cvsweb, but seem to have mislaid it .. After updating 7.0-RELEASE to RELENG_7 sources on Dec 28, checking UPDATING before and during buildworld, went hunting on cvsweb for the very version of UPDATING I was reading, 1.507

Re: Hacked - FreeBSD 7.1-Release

On Thu, 31 Dec 2009, Jeremy Chadwick wrote: > On Thu, Dec 31, 2009 at 04:16:07AM +1100, Ian Smith wrote: > > On Tue, 29 Dec 2009, David Wolfskill wrote: > > > On Tue, Dec 29, 2009 at 03:20:37AM -0800, Jeremy Chadwick wrote: > > > > ... > > > > I've written my own script to do all of this.

Re: problem with iwi driver in 8.0 and custom kernel (works on generic)

On Wed, 23 Dec 2009, ocean wrote: > i've got some problems with iwi in Freebsd 8.0, using GENERIC kernel > everything works just fine, compiling a custom kernel, just excluding some > modules i don't need, cause an interrupt storm to happen on irq11: > > Dec 22 22:35:18 legend kernel: iwi0: mem >

pkg_add thinks that -STABLE is -RELEASE (wrong __FreeBSD_version?)

Hi, I'm running 8.0-STABLE and I noticed that by default pkg_add -r uses packages-8.0-release/Latest/ as PACKAGESITE. I read in the handbook[1] that pkg_add should use packages-5-stable/Latest/ as PACKAGESITE when one is running -STABLE. I took a look at the source code, and noticed that pkg_add

Regression with Asus K8N7-E deluxe motherboard on 8-stable: ACPI or PCI drivers bug ?

Hi, I've met 3 regressions on 8-stable on my Asus K8N7-E deluxe motherboard: - PATA drivers (kern/139143) - USB 2.0 drivers (usb/139142) - Ethernet (nfe) drivers But, I don't think that the USB/PATA/nfe drivers are the problem: The problem seems came from ACPI or PCI bus drivers bug with this mo

kernel build failed

pls help me.. build kernel error.. I have to update their source code.. standart-supfile # IMPORTANT: Change the next line to use one of the CVSup mirror sites # listed at http://www.freebsd.org/doc/handbook/mirrors.html. *default host=CHANGE_THIS.FreeBSD.org *default base=/var/db *default prefix

Re: kernel build failed

On Sat, Jan 02, 2010 at 09:55:29PM +0200, E. O. wrote: > pls help me.. build kernel error.. > > I have to update their source code.. standart-supfile > > # IMPORTANT: Change the next line to use one of the CVSup mirror sites > # listed at http://www.freebsd.org/doc/handbook/mirrors.html. > *defau

kernel build failed

pls help me , kernel always returns an error /usr# ls -l /usr/ total 66 drwxrwxr-x 2 root operator512 2 Oca 14:26 .snap lrwxr-xr-x 1 root wheel10 1 Oca 20:35 X11R6 -> /usr/local drwxr-xr-x 2 root wheel 7168 2 Oca 12:43 bin drwxr-xr-x 3 root wheel 512 1 Oca 20

Re: pkg_add thinks that -STABLE is -RELEASE (wrong __FreeBSD_version?)

2010/1/2 Paride Legovini : > Hi, > > I'm running 8.0-STABLE and I noticed that by default pkg_add -r uses > packages-8.0-release/Latest/ as PACKAGESITE. I read in the handbook[1] > that pkg_add should use packages-5-stable/Latest/ as PACKAGESITE when > one is running -STABLE. > > I took a look at t

Re: kernel build failed

On Sat, 2 Jan 2010, E. O. wrote: source update and cd /usr/src make cleandir && make cleandir && rm -rf /usr/obj make buildkernel and error After updating source, you should buildworld before trying to build the kernel. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld

Re: kernel build failed

E. O. wrote: > # IMPORTANT: Change the next line to use one of the CVSup mirror sites > # listed at http://www.freebsd.org/doc/handbook/mirrors.html. > *default host=cvsup.FreeBSD.org I don't think that's going to work properly for you. Try going to http://www.freebsd.

Re: Regression with Asus K8N7-E deluxe motherboard on 8-stable: ACPI or PCI drivers bug ?

On Saturday 02 January 2010 19:54:11 Olivier Cochard-Labbé wrote: > ohci early: SMM active, request owner change > ohci early: SMM does not respond, resetting If the I/O address range changed, then the above can be explained by that we are reading/writing to an invalid range. USB debug sysctls:

Re: Cannot list a particular directory through NFS with UDP

On Sat, 2 Jan 2010, Jeremie Le Hen wrote: I will reduce the MTU and see if the problem arises with directories that could be read correctly otherwise. I will keep you informed. You can reduce rsize to 1024, so that it isn't happening, but that will also change the size of the readdir repl

Re: gstat: geom_gettree = -1: No such file or directory

On Fri, 01.01.2010 at 18:47:27 +0100, martinko wrote: > Hi list, > > gstat(8) does not work here on 8.0 (it worked happily on 6.x and 7.x) : > > # gstat > gstat: geom_gettree = -1: No such file or directory > > Is this known ? What can I do ? I doubt that it is widely known, but I've seen thes

Re: UTF-8 problem in 8.0

On Fri, 01.01.2010 at 15:47:36 -0800, Derek Kulinski wrote: > Hello, > > After installing FreeBSD 8.0 I noticed that some characters aren't > displayed correctly (it worked fine for 7.2). > > Mainly the dash character is most noticeable (though it's possible > it's more of them). > > Example: >

Re: UTF-8 problem in 8.0

On Sun, Jan 03, 2010 at 02:38:32AM +0100, Ulrich Sp??rlein wrote: > On Fri, 01.01.2010 at 15:47:36 -0800, Derek Kulinski wrote: > > Hello, > > > > After installing FreeBSD 8.0 I noticed that some characters aren't > > displayed correctly (it worked fine for 7.2). > > > > Mainly the dash character

Re: UTF-8 problem in 8.0

Hello Jonathan, Saturday, January 2, 2010, 7:28:07 PM, you wrote: >> me too, though I'm only setting LC_CTYPE to de_DE.UTF-8 and I don't >> always see it. It must be some combination of xterm/ssh and/or putty >> that breaks this. > Actually, I've just got en_NZ.UTF8, and I see it on the console

Re: UTF-8 problem in 8.0

On Sat, Jan 02, 2010 at 07:37:15PM -0800, Derek Kulinski wrote: > Hello Jonathan, > > Saturday, January 2, 2010, 7:28:07 PM, you wrote: > > >> me too, though I'm only setting LC_CTYPE to de_DE.UTF-8 and I don't > >> always see it. It must be some combination of xterm/ssh and/or putty > >> that br