Chris BeHanna wrote:
>
> I'm currently doing QA on a (very) large software project, and all
> of those things are important. Some of the testing uses existing
> industry test suites and benchmarking tools, and some of it (much of
> it) is custom. Being able to compile, install, and boot is
Isn't this something that can overcome the current shortcomings of jail(2) ?
(the no other stacks/no raw sockets problem)
- Ruben
--
,-_ ..
/() ) | Ruben van Staveren http://ruben.is.verweg.com/ |_o
(__ ( |M
Howdy,
Using FreeBSD 4.7 Stable
I have been playing with the loadable modules and ran into an issue with
the xl.ko driver.
For some reason if I have the miibus.ko module loaded, when the loader
code attempts to load the xl driver, the loader will determine that the
xl driver needs the miibuss d
>From: Michael Bretterklieber <[EMAIL PROTECTED]>
>Subject: Endless loop installing port
>
>Hi,
>
>I have an endless loop If I install a port, the system produces hundreds of
>make CHILD_DEPENDS=yes PARENT_CHECKED= package-depend .
>during registering of the package.
>
>If found that If I remo
On Wed, 16 Oct 2002, David Kleiner wrote:
> On Wed, Oct 16, 2002 at 11:03:21PM +0200, Fischer, Oliver wrote:
> > Mike Hoskins wrote:
> > >Hmm, I wonder if something similar is used or was developed for internal
> > >QA? Anyone? It seems like there should at least be a "best practice" for
> > >t
> But on connecting, I get this unpleasant result on both cards:
>
> ---
> FreeiSD/i386 (synapse.b(gcheese.com) (ttyd0)
>
> : gi
> SD/i386 (synapse.b(gcheese.com) (ttyd0)
>
> : gi
> ---
>
I too am getting corruption on the nrp driver for RX data (at 115,200). TX
works fine, no corrup
Just so everyone knows, I've MFC'd a bunch of changes to the if_xl driver
in the last few days. Most of these changes will have no functional
effect, and serve merely to synchronize the -current and -stable versions
of the driver. However, if your xl nic suddenly stops working, but it
worked fi
On 2002-Oct-17 11:02:34 +0930, Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote:
>On Thursday, 17 October 2002 at 9:35:40 +1000, Christopher Vance wrote:
>> On Wed, Oct 16, 2002 at 04:31:57PM -0300, Vitor de Matos Carvalho wrote:
>>> Detected the DST problem, because the Security Team did not notify
On Thursday, 17 October 2002 at 9:35:40 +1000, Christopher Vance wrote:
> On Wed, Oct 16, 2002 at 04:31:57PM -0300, Vitor de Matos Carvalho wrote:
>> Detected the DST problem, because the Security Team did not notify? It will
>> be that this error for being of did not enteresse of administrators
On Wed, Oct 16, 2002 at 10:30:09PM +0200, Michael Bretterklieber wrote:
> >Correct..the above options are not user-settable, and are for internal
> >use only within ports.
> >
> aha. Now (FreeBSD 4.7) I don't find this params anymore in
> defaults/make.conf, but it seems that in an earlier versi
On Thu, 2002-10-17 at 07:30, Mr. Darren wrote:
> Does anyone know of a way to use TV-out for FreeBSD
> under the terms that it does not interfear or use the
> main video card display. I require a completely
> separate 'out'. Name any hardware and I will buy it.
> Any information will be helpful
On Wed, Oct 16, 2002 at 11:03:21PM +0200, Fischer, Oliver wrote:
> Mike Hoskins wrote:
> >Hmm, I wonder if something similar is used or was developed for internal
> >QA? Anyone? It seems like there should at least be a "best practice" for
> >testing systems... How do we currently make a -RELEAS
12 matches
Mail list logo
