axe CPU_UPGRADE_HW_CACHE from i386 specific code
It looks like CPU_UPGRADE_HW_CACHE is only used in PC98, so it can be removed from all I386 specific code. Any objections to the following patch? Mark Index: conf/options.i386 === RCS file: /usr/cvs/src/sys/conf/options.i386,v retrieving revision 1.218 diff -d -u -r1.218 options.i386 --- conf/options.i386 17 Mar 2005 01:20:49 - 1.218 +++ conf/options.i386 26 Mar 2005 00:57:20 - @@ -63,7 +63,6 @@ CPU_RSTK_ENopt_cpu.h CPU_SOEKRISopt_cpu.h CPU_SUSP_HLT opt_cpu.h -CPU_UPGRADE_HW_CACHE opt_cpu.h CPU_WT_ALLOC opt_cpu.h CYRIX_CACHE_REALLY_WORKS opt_cpu.h CYRIX_CACHE_WORKS opt_cpu.h Index: i386/conf/NOTES === RCS file: /usr/cvs/src/sys/i386/conf/NOTES,v retrieving revision 1.1190 diff -d -u -r1.1190 NOTES --- i386/conf/NOTES 18 Mar 2005 09:34:52 - 1.1190 +++ i386/conf/NOTES 26 Mar 2005 00:57:42 - @@ -151,8 +151,6 @@ # CPU_SUSP_HLT enables suspend on HALT. If this option is set, CPU # enters suspend mode following execution of HALT instruction. # -# CPU_UPGRADE_HW_CACHE eliminates unneeded cache flush instruction(s). -# # CPU_WT_ALLOC enables write allocation on Cyrix 6x86/6x86MX and AMD # K5/K6/K6-2 CPUs. # @@ -206,7 +204,6 @@ optionsCPU_RSTK_EN optionsCPU_SOEKRIS optionsCPU_SUSP_HLT -optionsCPU_UPGRADE_HW_CACHE optionsCPU_WT_ALLOC optionsCYRIX_CACHE_WORKS optionsCYRIX_CACHE_REALLY_WORKS -- RIPE NCC - Delft University of Technology - The FreeBSD Project [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Simulate device-file in userland?
On Sun, Jul 25, 2004 at 06:57:00PM +0200, Jan Branbergen wrote: Content-Description: body i was wondering if it is possible to simulate a device-file ( for example a serial port or videograbbing device ) in userland? You may want to look at ng_device. Be prepared for rough edges though ;) Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: obtaining a kernel crash dump
On Wed, May 19, 2004 at 04:34:42PM +0300, Nick Strebkov wrote: I can't obtain a crash dump. Can you, on a clean -current, break into DDB and force a panic by simply typing panic ? Please report whether the kernel dumps core in this case. Some systems have problems with ATA that prevents them from dumping. Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
diff included in commit mail
Hi, I know it was discussed once somewhere, but I can't find the thread in question. What I would like to be able to do is see the actual commit included in the mail. I know it can't be done at the moment the message arrives, as that is before it arrives in my cvs tree. On my machine I have the cvs repo mirrored, so doing it in realtime is no problem. Does anybody have scripts or whatever available to do this? Thanks Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
DEVICE_IDENTIFY(9)
The above manpage documents the return values, but it is a void function. Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Power Patches
On Sat, Jan 03, 2004 at 06:47:13PM -0800, Nate Lawson wrote: I get a panic on my T23 due to the ATA driver not being detected so no rootvp. Same here on a Dell Latitude C640. Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
early write to pci conf register
What is the earliest point in the boot process that I can write to a pci conf registers of a pci device? I would like to disable some sub devices before they get probed. Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nswap
On Tue, Jan 21, 2003 at 01:33:01AM -0800, David Schultz wrote:
Thus spake Mark Santcroos [EMAIL PROTECTED]:
Yes, that is also what I meant. We now have a swapoff() system call that
does all the work itself.
My idea was to split that up:
/* turn of swap device */
static int swapoff_one(struct swdevt *sp)
{
/* Do all things that we don't want to know about outside this function
*/
}
/* turn off all swap devices */
int swapoff_all()
{
int index;
struct swdevt *sp;
for (sp = swdevt, index = 0; index nswdev; index++, sp++)
swapoff_one(sp);
}
So the swapoff() system call would call swapoff_one() and my code in
kern/kern_swsuspend.c would call swapoff_all().
See swapoff(8), in particular the -a flag.
I'm aware of that, but imho it doesn't suite my purpose. Are you strongly
against having such code inside the kernel?
Mark
--
Mark SantcroosRIPE Network Coordination Centre
http://www.ripe.net/home/mark/New Projects Group/TTM
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: nswap
On Fri, Jan 17, 2003 at 03:27:29PM -0800, David Schultz wrote: Thus spake Mark Santcroos [EMAIL PROTECTED]: in sys/systm.h: extern int nswap; /* size of swap space */ in vm/vm_swap.c: static int nswap; /* first block after the interleaved devs */ Is the extern pointing to this variable? (It seems so, don't see any other such variable in the three) If so, is there any problem with making nswap non-static? It's a constant that is only relevant to the management of the swap allocation bitmap, so it is properly static. It shouldn't be declared in sys/systm.h. I need to get access to the swap interface. More precisely, I want to turn it off. Either some of the values and functions need to be made global or the interface should be changed. I need this for software suspending on which I am working. (Page in processes and turn off swap devices before I write out the memory to it) Is it worth my time to produce patches that change the swapoff interface? Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
nswap
in sys/systm.h: extern int nswap; /* size of swap space */ in vm/vm_swap.c: static int nswap; /* first block after the interleaved devs */ Is the extern pointing to this variable? (It seems so, don't see any other such variable in the three) If so, is there any problem with making nswap non-static? Thanks Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
closing all fd's in ng_device before node removal
In a kernel driver, is is possible to get the list of open fd's on a dev_t entry? I can probably do it using a double administration by storing all accesses to open() and close() but I would rather not. Any input appreciated! Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: vmware reads disk on non-sector boundary
On Thu, Oct 03, 2002 at 09:04:04AM +0100, Ian Dowse wrote: See the patch I posted in: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=0+6285+/usr/local/www/db/text/2002/freebsd-emulation/20020908.freebsd-emulation There may still be further issues, but it allowed me to use vmware2 on a current from a week or two ago. That's only for virtual disks, and that is not where the problem is (was). For most people this is not a solution. I have an almost-ready patch that implements linux_read() syscall. This will check if we are reading from a raw disk and in that case it will enlarge the read() to the next sector boundary. I have it working in the kernel but I have problems returning the right read buffer to userland. Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: vmware reads disk on non-sector boundary
On Thu, Oct 03, 2002 at 09:50:45PM +1000, Bruce Evans wrote: Unbreaking block devices would be a better solution. Without buffering, reads of raw disks using an unbuffered linux_read() might be sector size times slower than they should be. You are right. The quick and dirty hack I had in mind was less quick and more dirty than I expected ;-) What was the reason for the removal of block devices anyway? It would be nice if you would tell me some background about that.. :) Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: vmware reads disk on non-sector boundary
On Thu, Oct 03, 2002 at 05:57:56PM +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: If a buffered access-mode on block devices is desired, it should be implemented either as an ioctl controllable feature, or as a GEOM module. The latter is probably by far the easiest way. It was desired, and was sort of promised. And we're close to the point where it can happen... So 'ignoring' the historic facts, and assuming that we just want block devices, we can do such a thing in GEOM in the future? Is this something you will be doing yourself Poul, or is it just that you are saying that it is possible? If not, I really would like to help to get vmware back, but I don't know anything more about GEOM than option\t\tGEOM. Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ACPI programming under FreeBSD?
Hi,
I have a very simple program that does exactly this using sysctl's.
Find it attached.
ACPI developers, there is alot more information available in the kernel about
ACPI that we don't export to userland yet.
Do you think we should do that using more sysctl's or should we implement
some ioctl's on /dev/acpi to retrieve the information?
Mark
On Tue, Oct 01, 2002 at 04:23:00PM -0400, Craig Rodrigues wrote:
Hi,
I am interested in retrieving power statistics type of information from a
system running FreeBSD. I am interested in information such as:
power consumed, temperature, percentage of battery available, etc.
Is it possible to do this with ACPI, and if so, are there any
examples of how to gather this information at the user-level?
How stable is ACPI support in -STABLE and -CURRENT for this
kind of work?
Thanks.
--
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Mark SantcroosRIPE Network Coordination Centre
http://www.ripe.net/home/mark/New Projects Group/TTM
#define KELVIN_TO_CELSIUS(t)((t-2732+5)/10)
#include stdio.h
int main()
{
int ret;
int intbuf;
size_t len;
ret=sysctlbyname(hw.acpi.thermal.tz0.temperature,intbuf,len,NULL,0);
if(ret==0)
printf(tz0 temperarture: %d C\n,KELVIN_TO_CELSIUS(intbuf));
ret=sysctlbyname(hw.acpi.thermal.tz0._CRT,intbuf,len,NULL,0);
if(ret==0)
printf(tz0 crit temperarture: %d C\n,KELVIN_TO_CELSIUS(intbuf));
ret=sysctlbyname(hw.acpi.acline,intbuf,len,NULL,0);
if(ret==0)
printf(AC Line status: %s\n,intbuf?online:offline);
ret=sysctlbyname(hw.acpi.battery.units,intbuf,len,NULL,0);
if(ret==0)
printf(Number of battery units: %d\n,intbuf);
ret=sysctlbyname(hw.acpi.battery.state,intbuf,len,NULL,0);
if(ret==0)
printf(Battery state: %d\n,intbuf);
ret=sysctlbyname(hw.acpi.battery.life,intbuf,len,NULL,0);
if(ret==0)
printf(Remaining battery life: %d%%\n,intbuf);
ret=sysctlbyname(hw.acpi.battery.time,intbuf,len,NULL,0);
if(ret==0)
printf(Remaining battery time: %d:%d\n,intbuf/60,intbuf%60);
printf(crit: %d\n,KELVIN_TO_CELSIUS(3732));
return(0);
}
Re: vmware reads disk on non-sector boundary
On Thu, Sep 26, 2002 at 07:50:36PM +0100, Josef Karthauser wrote:
It took a while to find, but this is the hack I was referring to:
Take a look at /sys/compat/linux/linux_stats.c,
Thanks for taking the effort for looking this up.
However, the function in question - newstat_copyout - is not in 'action'
here. (had set a breakpoint in ddb)
It's still unclear to me what recent change broke vmware.
The removal of block devices Julian referred to is not something recent,
is it?
I mentioned earlier to you that I am writing a linux_read system call.
This will basicly work, as long as I will be able to do the following (in
pseudo code):
linux_read(readsize) {
if (read_is_on_raw_device)
readlen = (readlen % BLOCKSIZE) + BLOCKSIZE;
/* or something like this plus some other mangling of the buffer
*/
read(readlen);
}
The only thing I have to find out is the check to see whether it is a read
on a raw device or not. I strongly prefer to do the check in linux_read
and not in the disk layer code. (It would be easier, but not cleaner)
Mark
--
Mark Santcroos RIPE Network Coordination Centre
http://www.ripe.net/home/mark/ New Projects Group/TTM
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
vmware reads disk on non-sector boundary
Vmware2 stopped running from both md and ad devices. Virtual disks still work. It is caused by a read that is not on sector boundary. Should a program be able to read non-sector sized chunks from a raw disk yes or no? What is the desired behaviour? The fact that this did work, was it a bug or did this come out due to some other change. The stacktrace from read(2) is below. Any input welcome, it's about time that vmware runs again on -current. Mark dscheck(c7528a70,c0c20800,4,c7528a70,c28f0800) at dscheck diskstrategy(c7528a70,10,4,c0c20800,c0c2086c) at diskstrategy+0x7f readdisklabel(c23f4e00,c28f0800,1,c23d4000,c23f4e4c) at readdisklabel+0xb8 dsopen(c2347e00,2000,0,c23d9588,c23d9200) at dsopen+0x1e6 diskopen(c2347e00,1,2000,c23e0cc0,c26c4700) at diskopen+0x15f spec_open(cdac9a2c,cdac9ac8,c027796b,cdac9a2c,c0911c50) at spec_open+0x150 spec_vnoperate(cdac9a2c,c0911c50,1,100,c23e0cc0) at spec_vnoperate+0x18 vn_open_cred(cdac9bcc,cdac9ccc,0,c26c4700,cdac9cb8) at vn_open_cred+0x3eb vn_open(cdac9bcc,cdac9ccc,0,1,cdac9b04) at vn_open+0x29 kern_open(c23e0cc0,8048639,0,1,0) at kern_open+0x1e3 open(c23e0cc0,cdac9d10,c,c23e0cc0,3) at open+0x30 syscall(2f,2f,2f,bfbffae4,bfbffaec) at syscall+0x2ca Xint0x80_syscall() at Xint0x80_syscall+0x1d -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: vmware reads disk on non-sector boundary
On Wed, Sep 25, 2002 at 07:41:44PM +0200, Poul-Henning Kamp wrote: The fact that this did work, was it a bug or did this come out due to some other change. The stacktrace from read(2) is below. This hasn't worked for a long time in -current. Long as in 6 months? By looking at the code history it seems so indeed. Do you have an idea what might have 'covered' this though? A fact is that vmware did work up until a few months. I didn't do a binary search yet. That is last resort... Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: vmware reads disk on non-sector boundary
On Wed, Sep 25, 2002 at 11:29:12AM -0700, Julian Elischer wrote: vmware used the blocking (b devices) interface to disks that do blocking for you. Some well meaning but misguided individuals removed block devices without providing an alernate way of doing this. It should be possible to do the equivalent of a vn device that accepts misalligned accesses and reblocks them, but I'll leave that to those whose job it is to finish. Hi Julian, That was the background info I was looking for. I might try to do the remapping myself. Thanks Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: VMware 3 on FreeBSD?
On Fri, Aug 30, 2002 at 09:20:12AM +0100, Bruce M Simpson wrote: Having said that though, I have had 3.0 running as well as 2.0, under ^^ Can you elaborate a bit more please? Probably your definition of 'running' is less strict than mine. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 09:43:45AM +0200, Martin Blapp wrote:
I suspect all the SIG4 and SIG11 problems we see are due
memory corruption in CURRENT.
In the latter case, the affected file looks like:
case HASH('^', 'e'):
case HASH('^', 'i'):
case HASH('^' 'o'):
\xc0 case HASH('^', 'u'):
%case HADH('`', \xc0A'):
^@ase HASH('`', 'E'):
case HASH('`', 'I'):
case HASH('`', 'O'):
case HASH('`', 'U'):
The file is correct after a reboot, so the corruption was limited to the
copy cached in RAM.
Thats memory corruption. I'm also not able anymore
to make 10 buildworlds (without -j, that triggers
panics in pmap code).
Bye the way, I'm experiencing this since about 4-5 months.
All hackers, please help to track this down.
Is it P4 specific or not?
Mark
--
Mark Santcroos RIPE Network Coordination Centre
http://www.ripe.net/home/mark/ New Projects Group/TTM
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 11:30:50AM +0200, Udo Schweigert wrote: Only a little addition from me: I had the same problems on -stable and they only disappeared after compiling the kernel without debugging. I had the impression that it has to do with the size of the kernel (but this of course maybe wrong). After dropping -g from kernel compiling I hadn't a problem again on -stable. (At the moment I do not have -current on a P-IV, the motherboard is a Fujitsu-Siemens) I will try that asap. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
Hi Martin, As you know this problem for longer, did you already try to make the problem a bit more reproducable / narrowed down? If not, we really should try to, that will be the first step in fixing it. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 02:38:25AM -0700, Terry Lambert wrote: Alternatively, rather than those options, try losing 512M of the RAM... I note they are all 1G boxes. No, mine is 256MB. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 02:33:57AM -0700, Terry Lambert wrote: options DISABLE_PSE options DISABLE_PG_G Coming up next in this theater :-) btw, how does the report that using the other compiler fixed everything for KT fit in? -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 03:17:03AM -0700, Terry Lambert wrote: Mark Santcroos wrote: On Thu, Aug 22, 2002 at 02:33:57AM -0700, Terry Lambert wrote: options DISABLE_PSE options DISABLE_PG_G Coming up next in this theater :-) btw, how does the report that using the other compiler fixed everything for KT fit in? It looks indeed like it is a 'winner'. The buildworld is still running but getting further already than the previous 10. Coincidentally. It's hard to trigger the bug, so it's easy to work around it accidently. Thats very true indeed. I can take that as a good 'explanation'. I remember you talking about this PSE problems earlier and more often. Is it fixable? I assume we would like to turn these options back on as they improve performance don't they? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 04:23:46AM -0700, Terry Lambert wrote: Ugh! Wait until it seems to work for a statistically significant sample size, and for more than one person before calling it happy! Also, I'm not sure looking at the code whether or not the PG_G is truly significant, or just preterbs the workaround. The problem I've referred to in my hunch here is actually related solely to the PSE, but with the recent code reorganization in locore.s, etc., it could have become more significant. I was just giving a slight report, not yelling halleluja yet ;-) It's doing the 2nd buildworld now. Do you also want me to try to split up the disabling of the two options? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 04:31:02AM -0700, Terry Lambert wrote: If it's a 3-for-3 workaround, then I probably need to take the discussion offline with Peter Wemm, and come up with a permanent fix. There was something with non-disclosure, am I right? -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
Hi, Can you revert back to the system compiler and also compile your kernel with this options and do some buildworlds again? Thanks Mark On Thu, Aug 22, 2002 at 01:41:13PM +0200, Soeren Schmidt wrote: It seems Terry Lambert wrote: Martin Blapp wrote: options DISABLE_PSE options DISABLE_PG_G Just added them. I'll now build 20 buildworlds with those enabled. Let the list know if it does anything. If Soren could also test, that would give a sample size. Sure, but I dont have the problem :) I can buildworld for days on my (heavily overclocked btw) Athlon with no problems at all... -S?ren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 01:55:42PM +0200, Soeren Schmidt wrote: Can you revert back to the system compiler and also compile your kernel with this options and do some buildworlds again? I already use the system compiler... That's why the message was addressed to kt ;-) -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Memory corruption in CURRENT
On Thu, Aug 22, 2002 at 05:21:54AM -0700, Terry Lambert wrote: Mark Santcroos wrote: On Thu, Aug 22, 2002 at 01:41:13PM +0200, Soeren Schmidt wrote: Sure, but I dont have the problem :) I can buildworld for days on my (heavily overclocked btw) Athlon with no problems at all... Can you revert back to the system compiler and also compile your kernel with this options and do some buildworlds again? You are making the same mistake I did. No, you are making the same mistake as Soren ;-) I did ask KT, look at the 'To:' field. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: projects?
On Thu, Jun 20, 2002 at 01:21:30PM -0700, Julian Elischer wrote: I've been considereing this as a fun project. The difficult comes at the interface/IP boundary.. we'd need am ng_route node to multiplex the packets to the correct output nodes... Would it be needed to duplicate the whole stack in the netgraph node or would it be relatively easy to hook it up to the existing ip and tcp code? Just wondering. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: projects?
On Fri, Jun 21, 2002 at 11:04:36AM -0700, Brooks Davis wrote: For my purposes, it would need to be seperate so you could copy the module and hack in a new TCP without changing the existing one. I understand, but you won't need to do that for the IP layer in your case. Other people might have a reverse situation, so some hooks to both these layers would come in handy, that was my point. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: kernel booting diff between boot2 and loader
On Tue, Jun 11, 2002 at 03:26:28AM +0200, Mark Santcroos wrote: I wonder what is different in booting the kernel from loader(8) and from boot2. In vmware2 I am not able to boot the kernel from boot2, it hangs after loading the kernelfile. Using loader it goes fine. I tried current,stable and generic kernels, all without luck. This was not really a problem, until I wanted to use etherboot, where I ofcourse can't use loader. fyi: this was fixed by statically compiling the hints file into the kernel. -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
kernel booting diff between boot2 and loader
I wonder what is different in booting the kernel from loader(8) and from boot2. In vmware2 I am not able to boot the kernel from boot2, it hangs after loading the kernelfile. Using loader it goes fine. I tried current,stable and generic kernels, all without luck. This was not really a problem, until I wanted to use etherboot, where I ofcourse can't use loader. Any help or insight into this will be gladly accepted :-) Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Recommend a laptop for FreeBSD
On Thu, Apr 18, 2002 at 11:20:37PM -0700, Koroush Saraf wrote: I'm looking to purchase a laptop to run FreeBSD. Other than the best price performance, I'm looking for troublefree installation and native support for all the hardware. My main requirement is native openGL driver support to take advantage of the 3D hardware acceleration. I'm leaning toward the Dell Dimension line of laptops, if you can recommend a better --name brand-- machine please let me know as well. This is a faq on freebsd-mobile. Read the archives there. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: kernel panic: vm_object_reference
On Wed, Mar 27, 2002 at 08:28:50AM +, Ceri wrote: Forcibly unmounting a file system that is in use will panic your system. It's not exactly a bug, it's just how it works. :) I don't agree. I know this is a little foolproof programming but I should return something like busy FS How would that be different from not forcing it ? That (or something similar) should be returned to the process accessing the unmounted fs, not the umount itself. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: please remove blank line
On Wed, Mar 06, 2002 at 10:39:16AM -0800, Julian Elischer wrote: The coding style guide for freebsd says that a blank line shalll be above the code and below teh variable declarations.. most peopple take this to read that the blank line still appears if there are no variables. style(9): /* Insert an empty line if the function has no local variables. */ Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: RS232/V24 Driver
On Sat, Mar 02, 2002 at 05:21:08PM -0700, Doug Russell wrote: On Sun, 3 Mar 2002, Volker Sturm wrote: I want to write a driver for a device on the serial port. The problem is that I dont get any info on the protocol that is used for data .. there already? If not, are there ways to analyze the protocol by a monitor or whatever technique appropriate? You might take a look at ports/comms/snooper Better try: http://www.gphoto.org/ because afaik this model is already supported :-) -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: a daemon C skeleton
man 3 daemon
On Fri, Feb 15, 2002 at 11:52:22AM +0300, Magdalinin Kirill wrote:
Hello,
can anyone, please, point out a C skeleton for FreeBSD daemon.
Is the following simple example correct for FreeBSD?
if (getppid() != 1)
{
signal(SIGTTOU, SIG_IGN);
signal(SIGTTIN, SIG_IGN);
signal(SIGTSTP, SIG_IGN);
if (fork() != 0)
exit(0);
setsid();
}
getrlimit(RLIMIT_NOFILE, flim);
for (fd = 0; fd flim.rlim_max; fd++)
close(fd);
chdir(/);
.
thanks in advance,
Kirill Magdalinin
[EMAIL PROTECTED]
_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
--
Mark Santcroos RIPE Network Coordination Centre
http://www.ripe.net/home/mark/ New Projects Group/TTM
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
[PATCH] nmdm fixes
Using the nmdm driver for serial console debugging in vmware I was really surprised to notice that the thing actually doesn't work at all (anymore). As far as I could find out it only supported one pair. Also after a close, when I would do a ls -al /dev/nmdm*, I would get a kernel panic. I rewrote nmdm.c to the basic point that it works fine for me. One can now create multiple pairs and I haven't got any panics or problems whatsoever. I also took the liberty to remove the ancient KR requirements at the same time now there is a large code change anyway. Please review the patch at: http://www.ripe.net/home/mark/files/nmdm.diff I would appreciate any feedback ranging from: 'hey, you should do it like this!' to 'committed!'. I only used/tested this on -CURRENT btw. Thanks to Julian for writing the driver initially. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging question
Ah great. Thanks alot! Mark On Wed, Oct 31, 2001 at 01:11:07AM -0800, Julian Elischer wrote: Mark Santcroos wrote: Thats what I already said in my email :) I was hoping that there is some way to dump the codepath of the kernel. Or is it maybe possible from ddb to move the context of a certain process and trace from there? tr PID gives you teh stack of that PID then set a breakpoint in a location that you know it will go through (e.g. one of the return addresses given in the trace) and then continue. Mark ps. I have narrowed it down already a bit more and hope to come with a bug report on -current in the coming days. On Tue, Oct 30, 2001 at 03:38:45PM -0800, Julian Elischer wrote: when the system is looping, hit CTLALTESC to drop into the debugger. On Tue, 30 Oct 2001, Andrew R. Reiter wrote: On Tue, 30 Oct 2001, Mark Santcroos wrote: :How can I see in what piece of the kernel it is looping? :(I know about where it is, but not exactly) : Use ddb to set a break -- you may need to do this upon boot (boot -d) *-. | Andrew R. Reiter | [EMAIL PROTECTED] | It requires a very unusual mind | to undertake the analysis of the obvious -- A.N. Whitehead To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- ++ __ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ [EMAIL PROTECTED] +--x USA\ a very strange | ( OZ)\___ ___ | country ! +- X_.---._/presently in San Francisco \_/ \\ v To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
debugging question
Hi I suspect that there is some endless loop somewhere in my kernel (-CURRENT). I can escape to ddb but a trace ofcourse only goes back to spot where the ddb gets called from the keyboard. How can I see in what piece of the kernel it is looping? (I know about where it is, but not exactly) I hope that there is another way then to place printf's everywhere. Thanks Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: debugging question
Thats what I already said in my email :) I was hoping that there is some way to dump the codepath of the kernel. Or is it maybe possible from ddb to move the context of a certain process and trace from there? Mark ps. I have narrowed it down already a bit more and hope to come with a bug report on -current in the coming days. On Tue, Oct 30, 2001 at 03:38:45PM -0800, Julian Elischer wrote: when the system is looping, hit CTLALTESC to drop into the debugger. On Tue, 30 Oct 2001, Andrew R. Reiter wrote: On Tue, 30 Oct 2001, Mark Santcroos wrote: :How can I see in what piece of the kernel it is looping? :(I know about where it is, but not exactly) : Use ddb to set a break -- you may need to do this upon boot (boot -d) *-. | Andrew R. Reiter | [EMAIL PROTECTED] | It requires a very unusual mind | to undertake the analysis of the obvious -- A.N. Whitehead To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
debugging vmware3 linux binary
I've been working on porting vmware3-beta to FreeBSD. Just as with vmware2 a sourcecode version for Linux is available for vmware3 and I have modified that to FreeBSD using the same approach as with vmware2. The kernel module compiles cleanly now and should probably work... [TM] However, the vmware program itself is only shipped as a Linux binary. Did the vmware2 binary ran flawlessly on FreeBSD, the vmware3 one does not. My question now: how the hell can I track this down? (ktrace doesn't seem to provide any valuable input, but maybe I overlook something) Thanks Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Junior Kernel Hacker task: improve vnode-v_tag
On Tue, Sep 04, 2001 at 02:27:00PM +0200, Poul-Henning Kamp wrote: I've done a /cursory/ look over how this v_tag is used. I'm not sure this is a simple/clean as you propose, since this is used in the IS_LOCKING_VFS macro, as well as in union_subr.c... Well, that is just too bad, because IS_LOCKING_VFS is wrong then. That's what the line of comment above it said ;) /* * [dfr] Kludge until I get around to fixing all the vfs locking. */ Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: import NetBSD rc system
What is the difference between the present rc scheme and the NetBSD one? Mark On Mon, Jun 11, 2001 at 01:44:26AM -0700, Doug Barton wrote: David Xu wrote: Hello, Is there any plan to import NetBSD rc system, I am willing to see it appears in FreeBSD 5.0. Yes. Several of us have started work on it. Personally, the last two times I carved time out to work on it I got bombed by unstable -current. Doug -- If you're never wrong, you're not trying hard enough. Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: import NetBSD rc system
Can it be called SysV style? Or not seperated in that way? (I must say, the big ugly rc thing is the only thing I don't like about FreeBSD, I'm very much in favor of the SysV style init. But thats another war ;) Mark On Mon, Jun 11, 2001 at 12:00:43PM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Mark Santcroos writes: : What is the difference between the present rc scheme and the NetBSD one? The NetBSD rc scheme, in a nutshell, put each thing into its own file and does order dependencies automatically. Ours is one big monolithic beast that kinda can do extra things, but only if their order can be coerced into being right. Warner -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Biometric security?
On Tue, Jan 23, 2001 at 04:14:54PM -0800, Ken Bolingbroke wrote: Has anyone gotten any biometric security devices to work with FreeBSD? I'm particularly interested in something like a fingerprint scanner that I could use to authenticate logins or disable my password protected screensaver rather than typing in my password all the time... Hi, Compaq has some cheap devices for workstations at around $100. The API you can find at www.bioapi.org. Mark ps. if you get me a device, I might be interested in writing a driver ;) -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: adding an address family
On Tue, Jan 16, 2001 at 11:34:09PM -0600, Michael C . Wu wrote: | Ok I'm trying to make a port of the IrDA stack on Linux to FreeBSD. | I've now written the driver for the chipset on my laptop, and I am ready | with that to pass data to an upper layer. Basically, we really do not want the Linux solution of doing IrDA. Using Netgraph would be much simpler. Email me and I will let you into my CVS repo of the IrDA ongoing work that Benno and I have done. Benno is working hard on FreeBSD/PPC kernel porting. I am doing the FreeBSD/PowerPC userland porting as well as I18N wchar* changes. Both of us are swamped, and the IrDA work has stagnated. I think we will gladly hand over the work. :) Ok, that's fine with me, I am eager to see what progress you two have made. | Following to that one I had another question: | | 2. Is Netgraph going to be the future in FreeBSD network stacks. Iaw, will | tcp/ip be based on Netgraph in the future or will it just be a nice | extension but not more. Possibly, but why? TCP/IP can be very resource intensive. After all, we have systems designed to only do TCP/IP, servers. IrDA, at maximum performance, cannot be higher than ~4mbit/sec, compared to gigabit ethernet and ATM networks that FreeBSD supports. At such high levels of I/O and CPU time, we can afford to have TCP/IP services in the kernel. On the contrary, IrDA is ugly and should be organized by Netgraph. *nods* That was the answer I expected, but wanted it to know for sure. | The reason I ask it is this: Is it wise to implement my protocol based on | Netgraph (so I can do it as a kernel module), or should I just build it | into the kernel? Netgraph all the way. (/me pondering what Julian is thinking) IrDA is a bunch of messed up ugly protocols that can simply be different ng_* Netgraph nodes. I get the feeling I should use netgraph *grin* Do you have the IrDA ISA driver? If so, for what chipset? Is yours the National Semiconductor Super IO chipsets? Can I see the IrDA ISA driver? :) I've written the PCI IrDA driver for my Toshiba laptop, the OBOE chipset. I am willing to write other drivers too, if someone can supply me with the needed hardware to develop for. One thing I will look at tonight is an old Tulip laptop I have laying around somewhere. It has an infrared port, but I have no idea what chipset. My driver is strongly based on the OBOE driver from Linux, so porting the other drivers should not be a big problem probably. (This one costed me a bit more time because it was my first PCI driver) Mark -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [IrDA] adding new network stack
On Wed, Jan 17, 2001 at 05:43:40AM -0800, Julian Elischer wrote: You may also want to talk to: Roger Hardiman [EMAIL PROTECTED] who expressed an interest in doing IrDA last June.. probably also worth puting out a general call for interested parties. I'll keep that in mind, hopefully the subject attracts the potential interested people :) Then just look at the drivers for various line cards such as the if_sr.c file and if_lmc.c and check out the sample netgraph file, ng_sample.c and the sample device driver (share/examples/drivers/make_device_driver.sh) (warning only up-to date in -current) I've been looking alot at other drivers already. My device driver is heavily based on the scheme in the example. But I've made it a module so I can develop it outside the source tree. If you want to send me your driver I'll even make a first attempt to bolt a netgraph interface to it. (or you can try and I'll check it for you) Thanks for the offer, I will do a first try myself, to learn more about it, but will certainly come to you when I can't work things out. check the 'blueprints' article on netgraph in daemon-news for a good run-down on what it all means (though it's abot out of date and had a few small lastly, read netgraph(4) done (doing) here is a list of existing netgraph drivers: sys/dev/lmc/if_lmc.c sys/dev/usb/udbp.c sys/i386/isa/if_ar.c sys/i386/isa/if_sr.c sys/i4b/driver/i4b_ing.c sys/netgraph/ng_ether.c sys/netgraph/ng_tty.c sys/pci/if_mn.c sys/dev/musycc/musycc.c *nods* already found them Do you have the IrDA ISA driver? If so, for what chipset? Is yours the National Semiconductor Super IO chipsets? Can I see the IrDA ISA driver? :) I've written the PCI IrDA driver for my Toshiba laptop, the OBOE chipset. I am willing to write other drivers too, if someone can supply me with the needed hardware to develop for. One thing I will look at tonight is an old Tulip laptop I have laying around somewhere. It has an infrared port, but I have no idea what chipset. maybe just old async IR.. we should try handle that too :-) *nods* for the driver part we can use ALOT from Linux for a sample PCI driver do: (on current) cd /usr/share/examples/drivers sh make_device_driver.sh irda then examine the generated files.. :-) Like I said above, I've used the info in there but created my own module, to be able to develop outside the tree. (I'm fairly new to FreeBSD/CVS so I do not know an easy way to work on a cvstree and keep it up to date(when your changes don't get uploaded) at the same time) I don't know what is the normal behaviour, but maybe it's possible to get an early framework into -CURRENT sooner or later? (If it doesn't interfere with other code) Within a day or so I hope to release my first pieces of code. In the next day I will try to insert a little netgraph code into it. Mark -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
adding an address family
Hi, I wonder if it is possible to dynamicly add an address family from a kernel module. I ask this because I am working on IrDA support for FreeBSD. I want to create AF_IRDA and all the corresponding structures and functions. So would it be possible to add another network stack at runtime or is the code not ready for that? Thanks Mark -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: adding an address family
On Tue, Jan 16, 2001 at 10:22:12AM -0800, Julian Elischer wrote: So would it be possible to add another network stack at runtime or is the code not ready for that? we do this in ng_socket.c where we add our own protocol. Thanx, I didn't thought on the netgraph code. Is this likely going to replace all the implementations of the current supported network protocols? In other words, is netgraph the right way to go for me, or should I rather focus on the more static part and drop the idea of implementing it as a kernel module? Mark -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: adding an address family
On Tue, Jan 16, 2001 at 01:01:54PM -0800, Julian Elischer wrote: Is this likely going to replace all the implementations of the current supported network protocols? In other words, is netgraph the right way to go for me, or should I rather focus on the more static part and drop the idea of implementing it as a kernel module? I don't know.. I don't know what you need :-) Hi, Ok I'm trying to make a port of the IrDA stack on Linux to FreeBSD. I've now written the driver for the chipset on my laptop, and I am ready with that to pass data to an upper layer. In Linux IrDA is handled as AF_IRDA, so in userland you create an AF_IRDA socket just as you would do with a normal TCP/IP stack and then you can commnunicate with other IrDA devices. I had two questions: 1. How can I dynamicly implement a new network protocol as a kernel module. The answer for that one seems to be Netgraph Following to that one I had another question: 2. Is Netgraph going to be the future in FreeBSD network stacks. Iaw, will tcp/ip be based on Netgraph in the future or will it just be a nice extension but not more. The reason I ask it is this: Is it wise to implement my protocol based on Netgraph (so I can do it as a kernel module), or should I just build it into the kernel? I know; A lot of questions, but I sure need the help :-) (And wouldn't it be cool if we would have IrDA support?) Mark -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
new kld style
Hi, While implementing a module based on /usr/share/examples/cdev??? I noticed that after loading it I get a warning that originates from kern/kern_linker.c telling me that I'm using the old kld style. [This all on -CURRENT] Can you please point me to the right direction for the "new" style. Or explain me if I'm missing something :-) [or even tell me that I should not worry about this] Regards, Mark -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
