RE: PXE Boot FreeBSD with Etherboot

2005-08-11 Thread Norbert Koch
> It seems there are some problems with using pxeboot in combination with > the network boot code from the etherboot project. I have tried many > combinations of options with no success. The result is very similar to > the following photo I found: > > http://photos.night-shade.org.uk/photo.php?p

Re: preferable way to control kernel module

2005-08-11 Thread Matthew N. Dodd
On Thu, 11 Aug 2005, Julian Elischer wrote: In the past, I've used a sysctl to communicate out the syscall number. you only need to do the syscall once, and it confirms to the program that the syscall is correctly installed. Why not just use a sysctl period? Think of it as "syscall by name".

PXE Boot FreeBSD with Etherboot

2005-08-11 Thread Loren M. Lang
It seems there are some problems with using pxeboot in combination with the network boot code from the etherboot project. I have tried many combinations of options with no success. The result is very similar to the following photo I found: http://photos.night-shade.org.uk/photo.php?photo=6364 I

Re: Checking sysctl values from within the kernel.

2005-08-11 Thread Doug Ambrisko
John Baldwin writes: | On Friday 05 August 2005 10:50 am, Dan Nelson wrote: | > In the last episode (Aug 05), Thordur I. Bjornsson said: | > > If I want to check a sysctl value from within the kernel (e.g. an | > > KLD), should I use the system calls described in sysctl(3) ? | > > | > > If not, wha

Re: Global txpower in ath

2005-08-11 Thread Sam Pierson
Is there a way to check the txpow in sysctl or something along those lines? I'm changing txpower and it appears as though it will do a reset every once in awhile. From what I can gather from if_ath.c, it looks like ath_init resets the txpow as well. I'd like to know whether or not my originally

Re: preferable way to control kernel module

2005-08-11 Thread Julian Elischer
Dirk GOUDERS wrote: > >>Shouldn't that be no problem if he sets the offset parameter to > >>SYSCALL_MODULE to NO_SYSCALL (get the next free offset)? > > > > > > But then you have to communicate the syscall number out to your userland > > applications somehow, and the applications have to

Re: Converting libfoo.so for linux to freebsd

2005-08-11 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Norikatsu Shigemura <[EMAIL PROTECTED]> writes: : Linuxpluginwrapper(LPW) is a most famous killer application : of libmap.conf(5)! (I think:-) Definitely. While threading games are interesting, the linux plugin wrapper definitely is much mo

Re: Converting libfoo.so for linux to freebsd

2005-08-11 Thread Norikatsu Shigemura
Linuxpluginwrapper(LPW) is a most famous killer application of libmap.conf(5)! (I think:-) On Thu, 11 Aug 2005 10:46:04 -0600 (MDT) "M. Warner Losh" <[EMAIL PROTECTED]> wrote: > Here's a breif outline of what I've learned: > (1) To remove the symbol versioning goo from a sha

Re: preferable way to control kernel module

2005-08-11 Thread Dirk GOUDERS
> >>Shouldn't that be no problem if he sets the offset parameter to > >>SYSCALL_MODULE to NO_SYSCALL (get the next free offset)? > > > > > > But then you have to communicate the syscall number out to your userland > > applications somehow, and the applications have to know how to invoke a

Re: preferable way to control kernel module

2005-08-11 Thread Sergey Uvarov
John Baldwin wrote: On Thursday 11 August 2005 12:16 pm, Dirk GOUDERS wrote: > > Thank you for advise. But I wonder: what is wrong with syscall > > approach (via SYSCALL_MODULE macro)? > > I just haven't done one personally. I think there's also a lot more > potenti al > for collisions when tr

Re: preferable way to control kernel module

2005-08-11 Thread John Baldwin
On Thursday 11 August 2005 12:16 pm, Dirk GOUDERS wrote: > > > Thank you for advise. But I wonder: what is wrong with syscall > > > approach (via SYSCALL_MODULE macro)? > > > > I just haven't done one personally. I think there's also a lot more > > potenti al > > for collisions when trying t

Re: Converting libfoo.so for linux to freebsd

2005-08-11 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Hajimu UMEMOTO <[EMAIL PROTECTED]> writes: : Hi, : : > On Tue, 9 Aug 2005 16:31:30 -0500 : > Dan Nelson <[EMAIL PROTECTED]> said: : : dnelson> In the last episode (Aug 09), M. Warner Losh said: : > I have recently purcahsed a device that comes w

Re: preferable way to control kernel module

2005-08-11 Thread Dirk GOUDERS
> > Thank you for advise. But I wonder: what is wrong with syscall approach > > (via SYSCALL_MODULE macro)? > > I just haven't done one personally. I think there's also a lot more potenti > al > for collisions when trying to pick a syscall number versus picking a string > name for a sys

Re: preferable way to control kernel module

2005-08-11 Thread John Baldwin
On Wednesday 10 August 2005 05:50 pm, Sergey Uvarov wrote: > I'm writing a kernel module for my own needs. AFAIK the following > methods could be used: > > 1) allocate not used system call with help of SYSCALL_MODULE macro > > 2) allocate proprieatry oid via SYSCTL_OID(OID

Re: Long Uptime

2005-08-11 Thread pablo . delgado
Nice, I to have a machine that is not to far behind you, its been up for 1 year and 4 months. I use it to show potential customers the power and stability of the FreeBSD System. I dont ever recall any windows server staying up that long. =) -Pablo > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA

[RFC] usr.bin patches for compilation with gcc 4.x

2005-08-11 Thread Divacky Roman
hi I made patches for usr.bin to compile with gcc4.x (tested with 4.1 snapshot), here it is: hysteria.sk/~neologism/find.patch hysteria.sk/~neologism/hexdump.patch hysteria.sk/~neologism/mkuzip.patch hysteria.sk/~neologism/tar.patch hysteria.sk/~neologism/wc.patch hysteria.sk/~neologism/window.pa

Re: gjournal public alpha release

2005-08-11 Thread Eric Anderson
Ivan Voras wrote: Hi! I'm announcing the first public version of the gjournal GEOM class :) The code is here: http://ivoras.sharanet.org/gjournal.tgz, together with a README file (reproduced below). I'd like to hear as many testing and bug reports as possible :) [..snip..] # make Warning: Ob

Re: Realtek RTL8100S on FreeBSD 5.4: no carrier.

2005-08-11 Thread Jordan Snodgrass
I did some more research, it appears that the Abit AA8-DuraMax actually uses the RealTek RTL8100S chipset, not the 8169. The hardware compatibility list for 5.4 shows support for the 8110S chipset, but not my specific motherboard. Perhaps it is a new chip revision? I tried the patch by Da

Re: Using sysarch specific syscalls in assembly?

2005-08-11 Thread alexander
On Wed Aug 10 05, Daan Vreeken [PA4DAN] wrote: > > I can confirm that. I have tested the program on 5.4-RELEASE here. Testing > your program (I called it "p") 10 times gives the following output : > > [EMAIL PROTECTED] for a in 0 1 2 3 4 5 6 7 8 9;do echo "starting p"; ./p ;done > starting p > s