On Mon, 15 Mar 1999, Dmitrij Tejblum wrote:
> Matthew Dillon wrote:
> > - error = acquire(lkp, extflags,
> > - LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE);
> > + if (p->p_flag & P_DEADLKTREAT) {
> > + error
unsubscribe
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Matthew Dillon wrote:
>
> We'll get a quick fix committed but the lockmgr stuff needs a real
> going-over... having interrupts using the general lockmgr call is
> a disaster waiting to happen.
Hmmm. After I looked a bit further, it looks like a bug in the
scheduler (?). Here is the s
On Mon, 15 Mar 1999, Dmitrij Tejblum wrote:
> Matthew Dillon wrote:
> >
> > We'll get a quick fix committed but the lockmgr stuff needs a real
> > going-over... having interrupts using the general lockmgr call is
> > a disaster waiting to happen.
>
> Hmmm. After I looked a bit furthe
"Donald J . Maddox" wrote:
>
> If you are *really* -current, /boot/loader.rc should probably
> just contain something like:
>
> include /boot/loader.4th
> start
>
> Then, you should copy /boot/defaults/loader.conf to /boot/loader.conf
> and edit it to match what you want to happen at boot.
Copy
[...]
> > => and on bringing the other goodies from
> > => http://www.cs.columbia.edu/~ezk/research/index.html
> Source for the cryptfs for FreeBSD. Do you have it?
Nope... I thought, it would be in the same place as the am-utils
source. And that is, indeed, so:
ftp://shekel.mcl.
Hi,
the way KLD's are handled seems to be bogus.
I have -current and build with PCCARD support into the kernel
( controller card0 & device pcic0 & device pcic1 )
if /etc/rc.pccard gets executed it does a:
...
if [ "X$pccard_enable" = X"YES" ] ; then
if kldload pcic; then
...
This le
Hi,
just for the record (as it is allready documented )
the latest -current kernels won't execute bladeenc (/usr/ports/audio/bladeenc)
an MPEG3 encoder. Former kernels did.
So one should either fix the kernel or BROKEN=YES the bladeenc Port or use the
linux executable (if it works at all)
Bye!
--
Hello,
My FreeBSD box keeps panicing when I'm trying to do a simple "cp
-rp" from a local disk to a NFS-mounted disk. The NFS server is a
Solaris 2.5 box; the NFS partition is mounted through amd.
The files I try to copy are just sendmail's cf directory (lots of
small files) and the panic happens
:
:> Matthew Dillon wrote:
:> >
:> > We'll get a quick fix committed but the lockmgr stuff needs a real
:> > going-over... having interrupts using the general lockmgr call is
:> > a disaster waiting to happen.
:>
:> Hmmm. After I looked a bit further, it looks like a bug in the
:> sc
Hi!
Will an SMP Kernel of 4.0-Current for two processors also run on one processor?
I'd like to check whether the SMP-kernel runs stable on my Asus P2B-DS with two
processors, but I'd like to be able to switch back to the non-SMP kernel
afterwards.
Ciao,
Thomas.
To Unsubscribe: send mail to
Thanks for the pointer. This seems to have been the problem and I have it
booting now. As a followup, is it possible to specify boot parameters
(i.e. splash screen, pnp config, etc) on a machine that is net booting?
Thanks for the help.
Nick
On Sun, 14 Mar 1999, Matthew Dillon wrote:
> I
>#14 0xc01ff64e in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 46137344,
> tf_esi = -1071149988, tf_ebp = -999002244, tf_isp = -999002304,
> tf_ebx = 18341888, tf_edx = -1000615936, tf_ecx = -1005747008,
> tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071650796, tf_cs = 8,
:Hello,
:
:My FreeBSD box keeps panicing when I'm trying to do a simple "cp
:-rp" from a local disk to a NFS-mounted disk. The NFS server is a
:Solaris 2.5 box; the NFS partition is mounted through amd.
:
:The files I try to copy are just sendmail's cf directory (lots of
:small files) and the panic
:Thanks for the pointer. This seems to have been the problem and I have it
:booting now. As a followup, is it possible to specify boot parameters
:(i.e. splash screen, pnp config, etc) on a machine that is net booting?
:
:Thanks for the help.
:
:Nick
:
:On Sun, 14 Mar 1999, Matthew Dillon wrote:
In message <199903152134.naa02...@apollo.backplane.com>, Matthew Dillon writes:
Shouldn't this be detected by PCI-id rather than by brute force probing ?
>:> I had a very weird problem with the new parallel port device that caused
>
>Try this patch. This is what I had to do to make my m
> In message <199903152134.naa02...@apollo.backplane.com>, Matthew Dillon
> writes:
>
> Shouldn't this be detected by PCI-id rather than by brute force probing ?
Since these are ISA chipsets, no.
They're not (all) PnP devices either, unfortunately.
>
> >:> I had a very weird problem with
On Mon, Mar 15, 1999 at 07:16:24PM +0900, Daniel C. Sobral wrote:
> "Donald J . Maddox" wrote:
> >
> > If you are *really* -current, /boot/loader.rc should probably
> > just contain something like:
> >
> > include /boot/loader.4th
> > start
> >
> > Then, you should copy /boot/defaults/loader.con
Hi Michael!
On Mon, Mar 15, 1999 at 05:25:38PM +0100, Michael Reifenberger wrote:
> just for the record (as it is allready documented )
> the latest -current kernels won't execute bladeenc (/usr/ports/audio/bladeenc)
> an MPEG3 encoder. Former kernels did.
Yes, this was discussed on freebsd-commi
On 15-Mar-99 Dirk Froemberg wrote:
> > So one should either fix the kernel or BROKEN=YES the bladeenc Port or use
> > the
> > linux executable (if it works at all)
>
> As a workaround I'll mark bladeenc as BROKEN for FreeBSD-current.
> As a better solution I'll ask the original author for a
>
> It seems to work fine except it core dumps on exit for some reason.
>
Marcel fixed that one a while back; update your system. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.
Dirk Froemberg once stated:
=As a better solution I'll ask the original author for a native FreeBSD
=version.
Does not seem a better solution to me at all. The problem is not
that bladeenc does not run, the problem is that a BSDI executable
does not run. Which breaks a promise from
http:/
Hi...ALL...:
Now my system had install FreeBSD 3.1 Release and cnet-1.4p3 with package
(not porting).
But when I run cnet
It shows the following message:
>cnet TICKTOCK
Warning - DISPLAY variable not defined, using ASCI environment
Linking ticktock.cnet
cc :could not exec elf/cc i
23 matches
Mail list logo