search for: trulsson

Hi. This is mostly hypothetical, just because I want to see how knowledgeable people would go about achieving it: I want to sandbox Mozilla Firefox. For the sake of example, I'm running it under my own user account. The idea is that it should be allowed to connect to the X server, it should be allowed to write to ~/.mozilla and /tmp. I expect some configurations would want access to audio

I upgraded from 6.2 to 6.3 p5 last night. Upon rebooting, the second disk in the mirror is missing. # atacontrol status ar0 ar0: ATA RAID1 status: DEGRADED subdisks: 0 ad0 ONLINE 1 ---- MISSING # grep ata /var/run/dmesg.boot ad0: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at ata0-master UDMA100 ad1: 238475MB <WDC WD2500AVJB-63UDA0 00.02C01> at ata0-slave UDMA100 ar0: disk0

Not all FTP sites have the first release candidate, but it is at least available from ftp.freebsd.org. Please download and install this candidate and help us find bugs BEFORE we call it 4.9-RELEASE. ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.9-RC1 ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.9-RC1-i386-disc1.iso We are particularly interested in having people test this release

Hi, We bought a new Dell PowerEdge 2950III with Perc 6/i and have the disk geometry problem using 6.3 final or 7.0 RC1. Seems that we are not alone at least one guy has similar problem reported earlier: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-01/msg00506.html I was reading the mailing list and found that some of the people are happily using this hardware with the latest

Hi, I just had some issues with unvalidated certificates after the update of the mail/fetchmail port. The solution was to add the missing certificates manually, but that involved running the c_rehash script, that currently isn't installed. Of course, I could run it directly from src/crypto/openssl/tools/, but that isn't an option for users that don't have the source installed. So,

I just merged drm (Direct Rendering) from HEAD. - Support for latest Intel chips - Support and fixes for many AMD/ATI chips r500 and below - Support AMD/ATI IGP based chips (rs690/rs485) - Lots of code cleanups - Lots of other fixes and changes since the existing drm is 2+ years old If you are experiencing a "garbled" screen with

The FreeBSD 4.x (4.8-STABLE) has contributed sources for BZIP2 in the base system under /usr/src/contrib/bzip2. My problem is that I am not succeeding in building these sources for some strange reason. Some apps that I run would do well if I could get to install these success- fully. If there is anyone has succeeded, I'd highly appreciate the steps they went through to get bzip2 to build.

/usr/ports/www/README.html went from some 200 lines to over 500 on a `make readme' in that directory just now. I thought `cvsup -g -L 2 /etc/cvsup_ports' would update the README.html files too. Should I be running `make readme' and/or `make index' (and/or anything else) myself after cvsupdating ports? -- Doug Lee dgl@dlee.org http://www.dlee.org Bartimaeus

After compiling the kernel 4.9RC1 dmesg gives the following error lpt0: Interrupt-driven port ppi0: <Parallel I/O> on ppbus0 ed1: <Realtek Plug & Play Ethernet Card> at port 0x220-0x23f irq 5 on isa0 ed1: address 52:54:40:28:83:9a, type NE2000 (16 bit) ad0: 4112MB <WDC AC24300L> [8912/15/63] at ata0-master WDMA2 Mounting root from ufs:/dev/ad0s1a module_register: module

Hi there, When I do a make buildworld and try to do a make release it will fail telling that it needs the CVSROOT directory. I do cvsup /etc/cvs-supfile and receive nothing ; # /etc/cvs-supfile *default host=cvsup3.nl.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4_8 *default delete use-rel-suffix *default compress cvsroot-all If I remove

I am cleaning up my 4-STABLE system. After a fresh installworld, I am looking at files that did not get touched by the install. Is it safe to remove all such files? In particular, I am looking at /usr/libexec/lib-elf.so.1, which has the schg flag set. I am afraid to remove this for fear of making my system unbootable. Could somebody please reassure me that it is ok to noschg and remove this old

This is a belated heads up to let you know that I have merged DTrace to the releng7 branch in the nick of time before the feature freeze for 7.1. Those astute mailing list readers will note that the commit message appears to have gone missing. Well, either the dog ate it or subversion decided that it was for certain eyes only (and not yours, or mine). I have added a note to src/UPDATING

Mike Silbersack wrote: > On Tue, 16 Sep 2003, Scott Long wrote: > > >>Patches have been floated on the mailing list that revert PAE in its >>various stages. Maybe those need to be brought back up. Silby? Tor? >> >>Scott > > > I believe that Tor's commit on August 30th resolved the PAE-related > problems, so there is no need for a reversion.

Hello! > Date: Thu, 15 Jan 2004 16:53:18 +0100 > From: Kirill Ponomarew <krion@FreeBSD.org> > > > freshly updated ports tree on a 4.9 box is exactly the same as a > > > freshly updated ports tree on a 5.2 box. > >=20 > > Read the users email. They're using specific tags, not "." so there are > > (or may be) some

Hi, in the kernel I have these lines: [...] device miibus # MII bus support device rl device ed options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=0 #limit verbosity options IPDIVERT #divert sockets options DUMMYNET

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:01.texindex Security Advisory The FreeBSD Project Topic: Texindex temporary file privilege escalation Category: contrib Module: texinfo

On Tue, Oct 14, 2008 at 09:52:09PM -0400, John R. Huston wrote: > Hi, I am not very familiar with using mailing lists so if I have made > a mistake in the format or scope of the message please correct me. I > am pretty desperate for an answer by now so any help at all is really > very appreciated. > > I have a Shuttle SD30G2 computer (Specs: >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of

If you're one of the people who has cvsup'd to 4.8-stable since August 8th and you've since begun to experience panics on a previously stable system, please apply the attached patch and see if your previous stability has been restored. Please tell me your results. Thanks, Mike "Silby" Silbersack -------------- next part -------------- diff -u -r