4:51 PM, Philip Guenther wrote:
On 11/3/07, Jason Murray <[EMAIL PROTECTED]> wrote:
I'm just a bit surprised that no one can give me any clues as to what
that error is. It's almost as if /dev/null is trying to execute, but
how can that be? I'm stumped, hence my post here.
con
at 7:27 PM, Brian A Seklecki (Mobile) wrote:
I can build you a custom 4.2 release with bsd.rd install images w/
RAIDFrame support, if needed.
I need to put together a 4.2 build box anyway
--
Jason Murray
IMBA Durham Region Rep - www.imba.com/canada
DMBA President - www.durhammountainb
10th is when I did the 4.0 -> 4.1 upgrade.
On a whim I unpacked config from my 4.1 tarballs. Same problem.
GENERIC shouldn't be broken as it is fresh from sys.tar.gz. I took a
quick look and it looks fine.
On 2-Nov-07, at 7:39 PM, Ted Unangst wrote:
On 11/2/07, Jason Murray <[EMAI
current" ;-) - you have to expect to deal with the
unforeseen.
Absolutely. And -misc has always provided me with that one clue I
needed.
--
Jason Murray
IMBA Durham Region Rep - www.imba.com/canada
DMBA President - www.durhammountainbiking.ca
TORBG Exec - www.torbg.org
It's not a shortcut. It is documented, just not "supported."
On 2-Nov-07, at 6:23 PM, Stuart Henderson wrote:
On 2007/11/02 18:03, Jason Murray wrote:
On the 4.1 box. As I've said I've done this since 3.6 with no
problems.
If you were able to take a shortcut f
On the 4.1 box. As I've said I've done this since 3.6 with no problems.
On 2-Nov-07, at 4:21 PM, Stuart Henderson wrote:
On 2007/11/02 14:45, Jason Murray wrote:
I have a 4.1 box that uses RAIDFrame so I need to compile a
customer kernel
in order to upgrade. I know this is not supp
to
indicate that this would only affect packages.
Thank in advance to whoever helps me out.
--
Jason Murray
IMBA Durham Region Rep - www.imba.org/canada
DMBA President - www.durhammountainbiking.ca
TORBG Executive - www.torbg.org
Thanks. Things usually go so smoothly that we're all a bit spoiled. Even
when we don't do things in the "supported" fashion.
I did the gcc upgrade, compiled some new kernels, and I now have nice
shiny 4.0 install with RAIDframe.
Joachim Schipper wrote:
Read http://www.openbsd.org/faq/upgrade
On Fri, November 3, 2006 0:10, Theo de Raadt said:
>> Will it be possible to build GENERIC kernel for the next OpenBSD
>> release 4.1 using release or stable 4.0 system (with comp40.tgz set
>> installed)?
>
> That would be a bit hard, since 4.1 is about 6 months away.
>
> But I get your drift. Can
I've had a failed HD in my raid array that I have finally bought a
replacement for. It is bigger so it should be large enough. I just want a
sanity check that I am doing the right thing. I have read the man pages,
but hey it's my data, and even though I've got a backup, it is
intimidating doing
I previously had a bit of trouble with my raid array. That is now cleared
up and I need to replace one HD of the mirrored set. Never having done
this I thought I'd check here to see if there was any advice on HD selection.
Natrually the replacement HD will have to be at least the same size as t
my data as possible. I'm hoping that those blocks are on a
"system" partition like /usr. Does anyone know of a tool that will tell me
which partition those blocks are in?
Next time my raid will be hardware based. :)
Thanks for your help thus far.
Jeff Quast wrote:
On 7/17
I've tried, again, to fix my raid array with raidctl -R. I did it on the
console port this time so I could capture the output from ddb>
Here is some output:
# raidctl -s raid0
raid0 Components:
/dev/wd0d: failed
/dev/wd1d: optimal
No spares.
Parity status: DIRTY
Reconstruc
Is it "standard" practice to use raidctl on a raid set while your system is
running from that raid set?
I'm just curious as to what "best practice" might be?
Last night I booted to a different disk so I could run raidctl -R against the
array while it was not being used. That caused a kernel pa
This mail is only so those who come after me can find something to help
them.
I had a recommendation to downgrade to station firmware 1.7.4, so I did.
wi0 at pci0 dev 20 function 0 "Intersil PRISM2.5" rev 0x01: irq 11
wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.1.1 (primary),
1.7.4 (
: mgmt. buffer allocation failed
wi0: wi_start: xmit failed
The first 5 wi0: lines occur when the network is started. The 6th line
occurs when httpd is started.
Jason Murray wrote:
$ cat /var/run/dmesg.boot | grep wi0
wi0 at pci0 dev 20 function 0 "Intersil PRISM2.5" rev 0x01: irq
Hello, just inquiring about the current state of tomcat on OpenBSD. I
did a search on the list and the only resent mention of tomcat
degenerated into a RoR sucks flamewar.
ease, with
raidframe and autoconfig option. Is the patch you submitted later than
that.
Melameth, Daniel D. wrote:
Melameth, Daniel D. wrote:
Jason Murray wrote:
Hello. I've been having a problem for the last year or so. This
problem has occurred in 3.6 - 3.9.
Let me try to explain it.
I
Hello. I've been having a problem for the last year or so. This problem
has occurred in 3.6 - 3.9.
Let me try to explain it.
I have a server with a wireless (802.11b) card in it and I have a laptop
that is using that server as its gateway. Whenever the traffic over the
wireless network increa
First off why am I doing this? Because I use RaidFrame and the upgrade I
need the raid psuedo device compiled into the kernel. I have
successfully used this approach to move from 3.6->3.7->3.8. I was hoping
to use this to move to 3.9.
Yes I've searched the web for answers. I can't find anythin
20 matches
Mail list logo
