I have a very bad problem. I need to seetup
large number of jails (about 100) to do virtual hosting
and i am doing it on 5.3-STABLE (not 5.3-RELEASE, i mean
-STABLE which is cvsupped). So, when i setup one jail -
everything runs fine for many days. If i setup one more jail
or 3 or more - server lo
On Sun, Jan 09, 2005 at 01:58:53PM +0100, Jilles Tjoelker wrote:
>
> Try all USB ports on your computer; use MAKEDEV to create /dev/usb1,
> /dev/usb2, etc (they are not created by default).
That was it.
Absolutely wonderful!
`usbd' is now working, in fact before it just did not _seem_ to work.
Th
Folks,
I kicked off a thread just before the holidays regarding some problems
we are having with an Intel SRCU42X RAID controller in a dual
processor production server originally under 5.3-STABLE and now
under 4.10-STABLE. The thread ran out of steam, with no resolution to
the problem, but I'm ho
Howdie,
Is there a way to get the default BSD 5.3 openssh to compile against
the MIT kerberos libraries? I have set NO_KERBEROS=yes in /etc/make.conf so
that the heimdal kerberos is not built, and rebuilt world, then installed
/usr/ports/security/krb5 and rebuilt world again. sshd is however not
Rick Updegrove <[EMAIL PROTECTED]> writes:
> This machine runs 4.11-STABLE just fine. I can make buildworld all day.
> Before that it ran Win2k for many months with no problems. For these
> reasons, I do not suspect hardware at this point.
>
> When I install 5.3-RELEASE it runs fine until...
Hi, freebsd users.
After upgrade from 4.10 to 5.3, I can't write disks
with burncd tool. I see this error:
# burncd -emv -s 10 data akt.iso fixate
adding type 0x08 file akt.iso size 554522 KB 277261 blocks
next writeable LBA 0
addr = 0 size = 567830528 blocks = 277261
writing from file akt
Below is a message I posted to x11@ regarding an apparent problem I am having
with a new mobo and getting DRI support. At the very least, it appears that
my AGP is not being probed correctly, and I hope that is where my DRI problem
lies. The mobo is an ECS 755-A2 (Athlon 64 socket 754, but I a
On Wed, 5 Jan 2005 12:51:56 -0800, Brooks Davis
<[EMAIL PROTECTED]> wrote:
> ALTQ makes no sense of virtual interfaces. ALTQ works by providing
> fine-grained control of the dequeueing of packets on to the wire. It's
> too early to do this when you're still in the virtual interface.
PF does not
On Tue, 2005-01-11 at 16:55 +0200, Nikolay Pavlov wrote:
> Hi, freebsd users.
> After upgrade from 4.10 to 5.3, I can't write disks
> with burncd tool. I see this error:
>
> # burncd -emv -s 10 data akt.iso fixate
> adding type 0x08 file akt.iso size 554522 KB 277261 blocks
> next writeable
On 2004.11.12 21:12:12 +0100, Simon L. Nielsen wrote:
> Today I suddenly couldn't log in via ssh to a server I upgraded to
> FreeBSD 5.3-RELEASE 4 days ago. When I tried connect to port 22 using
> telnet(1) the following just happend:
>
> [EMAIL PROTECTED]:~] telnet 192.168.3.2 22
> Trying 192.1
Mark Kirkwood wrote:
I have fired off an email to Promise support asking what the chip
PDC20XXX string is for the TX4200. Will post any useful reply obtained.
Promise support have come back to me with the chipset. Referring to
frode's posting plus some Internet searching provides what looks like
On Tuesday 11 January 2005 10:29 am, Jonathan Fosburgh wrote:
> Below is a message I posted to x11@ regarding an apparent problem I
> am having with a new mobo and getting DRI support. At the very
> least, it appears that my AGP is not being probed correctly, and I
> hope that is where my DRI prob
0n Wed, Jan 12, 2005 at 06:59:10AM +1030, Simon L. Nielsen wrote:
>On 2004.11.12 21:12:12 +0100, Simon L. Nielsen wrote:
>
>> Today I suddenly couldn't log in via ssh to a server I upgraded to
>> FreeBSD 5.3-RELEASE 4 days ago. When I tried connect to port 22 using
>> tel
On January 11, 2005 04:21 pm, Wilkinson, Alex wrote:
> 3.9 ?
> I have an updated ports collection and
> # grep -i portv /usr/ports/security/openssh/Makefile
> PORTVERSION=3.6.1
> DISTNAME= openssh-${PORTVERSION}
> PATCHFILES= openbsd28_${PORTVERSION}.patch
Wrong directory, you
Nate Lawson wrote:
M. Warner Losh wrote:
In message: <[EMAIL PROTECTED]>
Christopher Sean Hilton <[EMAIL PROTECTED]> writes:
: Second, what I haven't been able to completely research:
: : The PC card bus dies when on the first suspend resume. There
: seems to be no way to rest
On Tuesday 11 January 2005 16:42, Jung-uk Kim wrote:
>
> I think I screwed up the PCI ID. :-(
>
> Can you test the attached patch? It's for 6-CURRENT but you get the
> idea.
>
It now probes correctly:
agp0: mem 0xd800-0xdfff at device 0.0 on
pci0
The output from pciconf is still inv
Christopher Sean Hilton wrote:
Nate Lawson wrote:
My cardbus works fine after suspend/resume. The only current bug is
the extremely long time before resume methods run that was introduced
in the past couple weeks.
This afternoon I retested. Here's a better description of the problem.
My Netgea
17 matches
Mail list logo
