On Fri, 6 Jul 2007, Markus Ritzer wrote:
Hello!
My name is Markus Ritzer, and I have ported OpenBSD to the Microsoft Xbox.
I have done this as a project for university, and this project is
finished on July 18th.
It is not an official port until now, and I don't think it will become
one.
Disk: sd0 geometry: 3935/64/32 [8060926 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: idC H S -C H S [ start: size ]
0: 0B0 1 32 - 3935
On 7/6/07, Srebrenko Sehic [EMAIL PROTECTED] wrote:
Both work just fine. I myself, always run SCSI via mpi(4). Works like
a charm and performs quite well.
I confirm. I have several OpenBSD 4.1 VM in VMWare 6. Some use IDE,
some SCSI. No difference from what I can tell.
pf is probably the problem, 'keep state' is assumed unless
explicitelly stated otherwise.
On 7/6/07, Heinrich Rebehn [EMAIL PROTECTED] wrote:
Hello list,
after using ipsec for some years now, i never experienced an upgrade
breaking it. But after after moving to 4.1 (new install) i can not
Almir Karic wrote:
pf is probably the problem, 'keep state' is assumed unless
explicitelly stated otherwise.
On 7/6/07, Heinrich Rebehn [EMAIL PROTECTED] wrote:
Hello list,
after using ipsec for some years now, i never experienced an upgrade
breaking it. But after after moving to 4.1 (new
Karl O. Pinc wrote:
On 07/06/2007 06:46:26 PM, Chris Smith wrote:
I assume the problem is not enough RAM because when I
add more RAM everything works fine.
Repeatable? Sure you've ruled out a seating problem?
Yes, repeatable.
yep, I'd believe that.
Some time back (3.6?), when I stuffed
Todd Pytel wrote:
...If it
matters, this is going to be lightweight, home server kind of stuff.
There's the answer to your question: For your app, it just won't matter.
You've spent more time asking, and others (including myself) have spent
more time answering your question than you will ever
On Sat, 2007-07-07 at 10:44 -0400, Nick Holland wrote:
There's the answer to your question: For your app, it just won't matter.
You've spent more time asking, and others (including myself) have spent
more time answering your question than you will ever personally benefit
(i.e., more work done
On Mon, 4 Jun 2007, Bryan Vyhmeister wrote:
The later versions of the firmware (which I got) apparently do not allow
automated boot. I was very disappointed to find this out. I can't comment on
I'm actually one click away of buying a N2100.
Is this automated boot problem still true?
--
Is there a easy way to update OpenBSD's Xorg to latest cvs release of
it. This because of the added 'avivo' driver for my ATI Mobility Radeon
X1400 graphics card.
Timo
On Sat, 7 Jul 2007, Antoine Jacoutot wrote:
On Mon, 4 Jun 2007, Bryan Vyhmeister wrote:
The later versions of the firmware (which I got) apparently do not allow
automated boot. I was very disappointed to find this out. I can't comment
on
I'm actually one click away of buying a N2100.
Is
On 7/7/07, Timo Myyra [EMAIL PROTECTED] wrote:
Is there a easy way to update OpenBSD's Xorg to latest cvs release of
it. This because of the added 'avivo' driver for my ATI Mobility Radeon
X1400 graphics card.
Like from release to stable? If so then I would you anoncvs and
checkout Xs most
Hello,
I don't know, if this is a bug, but I can recognize a strange thing. Im
setting up a redundant pair of routers and run some tests with carp for
the failover on the lan side. Because of the bug refreshing the kernel
routing table when changing carp-state I use ifstated with an route
delete
On Sat, 7 Jul 2007, djgoku wrote:
On 7/7/07, Timo Myyra [EMAIL PROTECTED] wrote:
Is there a easy way to update OpenBSD's Xorg to latest cvs release of
it. This because of the added 'avivo' driver for my ATI Mobility Radeon
X1400 graphics card.
Like from release to stable? If so then I would
OK, to format a usb flash drive with an MS-DOS (FAT32) file system, I am
using the following procedure. First, I run fdisk
# fdisk -i -e sd0
and edit the MBR partition table as described in the previous message.
Then I run newfs_msdos
# newfs_msdos -F 32 -u 63 /dev/rsd0i
(Is the -u 63
Dovecot on a new 4.1 cvs install with 4.1 dovecot port will not fork any ideas..
here is kdump
[...]
3918 dovecot RET sigprocmask -65793/0xfffefeff
3918 dovecot CALL dup2(0x4,0)
3918 dovecot RET dup2 0
3918 dovecot CALL dup2(0x4,0x1)
3918 dovecot RET dup2 1
3918 dovecot
I've installed iwi-firmware-3.0.tgz per the iwi manpage, adjusted the
group associated with the four installed files to match that of everything
else in the directory:
$ ls -al /etc/firmware/iwi*
-rw-r--r-- 1 root bin 191142 Mar 26 2006 /etc/firmware/iwi-bss
-rw-r--r-- 1 root bin 185660
On 7/6/07, dreamwvr [EMAIL PROTECTED] wrote:
Dovecot on a new 4.1 cvs install with 4.1 dovecot port will not fork any ideas..
here is kdump
...
3918 dovecot CALL fork()
3918 dovecot RET fork 14942/0x3a5e
That shows that fork() was successful and that the pid of the child
was 14942.
18 matches
Mail list logo