Hello,
I'm on OpenBSD 4.0, I set up X using xorgcfg -textmode, the setup went
smooth but on starting x and moving the cursor it jumps around
crazily.
I've confirmed that the hardware is OK by installing and testing with
Solaris and Ubuntu.
I've Googled for an answer but without a satisfactory
* Nick Guenther [EMAIL PROTECTED] [2007-08-23 02:59]:
4) trusts externally set TOS/DSCP
No one should trust external TOS or DSCP markings. Again, what Google is
doing is an excellent argument for re-marking capability in all routers.
Yeah, really. Maybe we are misunderstanding, but
* David Newman [EMAIL PROTECTED] [2007-08-23 01:30]:
Also, I noticed today that Google marks all their stuff with a DSCP of
0x38 (high throughput, low delay). Nice trick, but also an excellent
argument for re-marking capability in all routers.
nice trick? rather useless. I'd be
I run -stable on an IBM/Lenovo T41p laptop with 512M memory and 2G swap.
I cvs-updated /usr/src on Aug 22 around 21:00 GMT. As usual, I followed
the instructions at http://www.openbsd.org/stable.html to rebuild...
but unlike all the other times I've done this, this time 'make build'
died while
On 2007/08/23 10:26, Henning Brauer wrote:
ISPs tend to run at much higher utilization levels than enterprises and
congestion is a reality on at least some of their pipes.
i know the ISP market very well, and I have yet to see that. at least
in europe, basically everybody has spare
Hi list,
I am having troubles with running freedt to supervise the mldonkey daemon. I
use 4.1-release and installed both mldonkey and freedt from ports.
I created /etc/svc.d directory where I put service directories. Created a
run file in /etc/svc.d/mldonkey/run with following content:
#!/bin/sh
Hi *,
I just reinstalled a box (running -CURRENT). I added a third IDE drive:
wd2 at pciide0 channel 1 drive 1: WDC WD2500JB-00REA0
wd2: 16-sector PIO, LBA48, 238475MB, 488397168 sectors
wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5
dkcsum: wd2 matches BIOS drive 0x82
It will be fully
# fdisk -i wd2
# disklabel -E wd2 (created 'a' partition)
# newfs wd2a
[...]
wd2a: id not found writing fsbn 488397104 (wd2 bn 8796581419375; cn
547561868 tn 158 sn 1), retrying
It looks like you are indeed running a -CURRENT (or fairly recent) kernel,
but with an older userland.
Are you
Argh! So stupid!
I just started a rebuild of userland tools... I'll keep you informed.
Tx Miod!
Xavier
--
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)
On Thu, 23 Aug 2007, Miod Vallat wrote:
# fdisk -i wd2
# disklabel -E wd2 (created 'a'
On Thu, 23 Aug 2007, Mayuresh Kathe wrote:
The Mouse section in xorg.conf looks as below:
Section InputDevice
# Identifier and driver
Identifier Mouse1
Driver mouse
Option ProtocolIMPS/2
Option ZAxisMapping 4 5
Could someone please point me in the right direction?
Try
It worked.
Thanks a million.
On 8/23/07, Antoine Jacoutot [EMAIL PROTECTED] wrote:
On Thu, 23 Aug 2007, Mayuresh Kathe wrote:
The Mouse section in xorg.conf looks as below:
Section InputDevice
# Identifier and driver
Identifier Mouse1
Driver mouse
Option Protocol
Hello,
I tried ( and failed ) to set up an IPSEC Tunnel to a LANCOM VPN Router in a
somewhat special constellation:
main mode is ok
quick mode negotiated successfully and established the following flow:
# ipsecctl -s flow
flow esp in from 172.17.0.0/16 to 172.17.7.50 peer a.b.c.d srcid
[EMAIL
And here we come full circle. Given the OpenBSD now IS a router --
whether it's a little two-interface pf box for home use or some big
studly hardware running OpenBGPD and OpenOSPFD box for ISPs, I would say
the addition of support for DSCP re-marking would be a very desirable
feature.
On Tue, 21 Aug 2007, nicodache wrote:
when getting the stage 2 boot loading prompt, I also get the following
message :
probing: pc0 com0 mem[639K 1023M a20=on]
disk: fd0 fd1 hd0+ hd1+
OpenBSD/i386 BOOT 2.13
boot
So, my installation sees an com port. is that because it is physically
On 2007/08/23 11:59, Theo de Raadt wrote:
And here we come full circle. Given the OpenBSD now IS a router --
whether it's a little two-interface pf box for home use or some big
studly hardware running OpenBGPD and OpenOSPFD box for ISPs, I would say
the addition of support for DSCP
And here we come full circle. Given the OpenBSD now IS a router --
whether it's a little two-interface pf box for home use or some big
studly hardware running OpenBGPD and OpenOSPFD box for ISPs, I would say
the addition of support for DSCP re-marking would be a very desirable
feature.
i'd
Ok, problem solved, it was indeed a mismatch between kernel userland!
Tx!
Xavier
--
The first time that Microsoft makes a product that doesn't suck
will be when they start making vacuum cleaners!
On Thu, 23 Aug 2007, Miod Vallat wrote:
# fdisk -i wd2
# disklabel -E wd2 (created 'a'
* David Newman [EMAIL PROTECTED] [2007-08-23 19:49]:
And here we come full circle. Given the OpenBSD now IS a router --
whether it's a little two-interface pf box for home use or some big
studly hardware running OpenBGPD and OpenOSPFD box for ISPs, I would say
the addition of support for
Hi again,
just for your information and if anybody runs into the same problem.
I found outr that there are a lot of sysctl values for IPSec which
can be changed so that it is possible for me to not use the default
timeout of 86400. Have a look:
# sysctl -a | grep ipsec
I ve got a 1.5 GHz MacMini attached to a 17 IBM TFT panel that has a
1280x1024 resolution.
How can I set the MacMini's display resolution to 1280x1024 24 bit
colors in OpenFirmware?
In OFW, 'dev screen show-modes' shows me a list of valid modes, amongst
them the one I want, but when doing a
On Aug 23, 2007, at 2:16 PM, Marc Balmer wrote:
I ve got a 1.5 GHz MacMini attached to a 17 IBM TFT panel that has
a 1280x1024 resolution.
How can I set the MacMini's display resolution to 1280x1024 24 bit
colors in OpenFirmware?
In OFW, 'dev screen show-modes' shows me a list of valid
- Forwarded message from Travers Buda [EMAIL PROTECTED] -
Date: Thu, 23 Aug 2007 19:43:53 -0500
From: Travers Buda [EMAIL PROTECTED]
To: Janjaap van Velthooven [EMAIL PROTECTED]
Subject: Re: kernel/5563: ipv6 traffic causes page fault trap
In-Reply-To: [EMAIL PROTECTED]
User-Agent:
22 matches
Mail list logo
