direction of the specifics of the problem (if they exist, if not, I may
try to create a simpler test case then java)?
I tried a few searches, but nothing matching what I remembered came up.
--
David E. Cross
___
freebsd-hackers@freebsd.org mailing list
PIO4
atapicam doesn't fix it. UDMA doesn't fix it. GENERIC kernel.
Reading works fine.
Suggestions?
--
David E. Cross
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any
the computer off in response to ACLine/UPS failure.)
Cheers,
--
David E. Cross
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
I have an NFS server that recently began to display the following behaviour
(technically the brhaviour is displayed on the clients):
(4.6.2-RELEASE)
mount_nfs -3 -T server:/path /mnt (UDP doesn't exhibit this)
dd bs=64k if=/dev/zero of=/mnt/somefile
I now get about 7 times/second on the client:
I just cvs-ed to RELENG_4_6_2_RELEASE and tried to do a make buildworld
and I get the errors included below.
It _appears_ to be related to the binutils/ld changes that went in,
but I am unsure how that change affected this, and only this.
errors bellow
make-roken.c
cc -O -pipe
# Power management support (see LINT for more options)
device apm0at nexus? flags 0x20 # Advanced Power Management
delete this line and build a new kernel.
i got the same problem here with an amd 750mhz and epox mainboard.
after i build a new kernel, the microuptime
# Power management support (see LINT for more options)
device apm0at nexus? flags 0x20 # Advanced Power Management
delete this line and build a new kernel.
i got the same problem here with an amd 750mhz and epox mainboard.
after i build a new kernel, the microuptime
I haven't seen microuptime messages in a _very_ long time; over this weekend
I replaced the PowerSupply a couple of fans and the CPU heatsinks in my
computer (none were yet bad, but one of the CPU fans was starting to
slow down, and I had a problem warm-rebooting the machine: it had a 90%
I'd like to create a /boot.config switch that will have boot1 _not_ read from
the console; this is for a secure setup. Would others be interested in these
patches when I finish them?
--
David Cross | email: [EMAIL PROTECTED]
Lab Director
Well, I can do the commit, I am just looking for interest, and code reviewers
;)
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
I received the following from gdb today:
#0 0x0 in ?? ()
#1 0x280a8d22 in svc_getreqset2 () from /usr/lib/libc.so.4
#2 0x280a8c5b in svc_getreqset () from /usr/lib/libc.so.4
#3 0x804c85f in yp_svc_run ()
#4 0x804cd94 in main ()
#5 0x8049a09 in _start ()
Uhm... I didn't think that was
I notice that a lot of people downloaded the ypserv update. I also know that
many people have had the same troubles I reported with the 'old' ypserv.
Have any of you who have had troubles tested this version? Did it work?
For those who are running it, have you noticed any problems?
--
David
To those of us experiencing problems with ypserv, I have made a copy of
my binary available at:
DO NOT READ ANY FURTHER IF YOU HAVE NOT SETUP AND ADMINED A NIS DOMAIN!
THIS IS NOT FOR YOU!
http://www.cs.rpi.edu/~crossd/FreeBSD/ypserv
MD5 (ypserv) = 1f1c6c01eafd690059b32e615e5b6efc
It is binary
Ok... I have just finished the first step in a rewrite of the hash routines
for berkleydb (read-only at this point), and I have ypserv compiled using
them. So far so good :). And ypserv uses a _lot_ less CPU resources now.
(I have totally removed all of the buffer management code in berkley db,
I am apparently bug-compatible with the original too, though it took
longer to trip over it (and the code runs LOTS faster :)... So probably
not tonight. I am going to be placing debugging statements in the code to
see if I can figure out where information is being stepped on.)
--
David Cross
In my case it would be usefull as I was trying to tell the last time
'telnetd' was run. (yes, not perfect, but better than nothing)
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer Polytechnic
Hmm... would it be as easy as
VOP_GETATTR();
.
.
.
VOP_SETATTR();
within the exec() code?
Certainly this would be an 'easy' fix (and I can work up diffs for review),
but is it the 'correct' fix?
--
David Cross | email: [EMAIL PROTECTED]
Lab Director
I noticed that exec(2) does not update the last access time of a file...
is this intentional?
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Well over NFS an exec will update atime (because NFS doesn't differentiate
between 'exec' and 'read').
Under Solaris8/Sparc (on a memfs mount) exec-ing an executable does indeed
update the access time.
--
David Cross | email: [EMAIL PROTECTED]
Lab Director
Hello, sound is not working correctly on this IBM model T22 laptop.
Specifically whenever sound plays it is very garbled. I can get it
to play almost correctly via either 'ping -f somehost' or
'dd bs=512 if=/dev/zero of=foo.zero' (well, at least until the filesystem
fills up ;) the ethernet
Hmm... an interesting followup to the laste email...
a flood ping FROM the laptop TO another machine clears up the problem...
a flood ping TO the laptop FROM another machine does nothing.
I assumed this may have had something to do with context switches (or
something)... so I did a 'while
Cool
What is the 'long term' fix? (and when will it be in -stable ;)
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of
It is definitely the powersaving/pci clkrun problem... as that is the only
power change I made ;)
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
I saw this the other day:
http://www.sleepycat.com/historic.html
Down at the bottom:
Finally, you should not upgrade your GNU gcc or Solaris compiler.
Optimizations in versions of gcc 2 that were in alpha test in the
summer of 1997, and a version of the standard Solaris WorkShop Compiler
Ok... I am coming to the conclusion that there is some sort of kernel
issue that is causing this problem. Here is what I have done and discovered
to date (this is all with 4.3-RC2 FWIW):
At some point the 'qhead' CIRCLEQ structure in yp_dblookup.c gets corrupted.
This is declared as a static,
After some more intensive debugging, and a leap of faith, I _think_ I have
the problem licked, but I would appreciate some more brains to examine the
logic.
The original cause of ypserv's problems was the sharing of DBPs between
the parent and child. The resolution to this was to close all of
I have found _a_ bug in ypserv (I think I may be stumbling over multiple
different bugs, but this one is very reproducable).
It is dying in the yp_testflags routine, in the for loop that goes through
the CIRCLEQ. The loop dies with qptr pointing to a struct that is all NULL
(my reading of
I have trace the problem in ypserv down to the RPC dispatch routines..
I am digging further and I hope to have it found and eliminated today
(in time for -RELEASE ;)
If anyone has any idea how it could be tripping up here, please let me
know. My 2 guesses are a corrupted svc_callback entry (no
Well, I am able to reproduce the crash pretty reliably, I don't know what is
causing it yet, I just kill all the other ypservs on a subnet except for this
one and it crashes about once every 5 minutes. I have some questions/theories
that I'd like to bounce off of people:
1) In the yp_all
The ypserv bug (the one where ypserv randomly stops responding or
just seg-faults) is still very much alive. I had to restart it
about 11 times in the course of 20 minutes this morning. That's
the bad news, the good news is that I started it each time with
'ktrace -i'.
Going back a bit, Matt
I recently tried (for the first time) to get gif running under FreeBSD
4.3-BETA (cvsup-ed yesterday). I noticed the following:
gifconfig gif0 inet 10.1.1.1 10.1.2.1
ifconfig gif0 192.168.1.1 192.168.1.2 netmask 0xff00
and then I 'ping 192.168.1.1' it will try to route the packet instead of
I need to use multiple malloc disks for a custom net-boot image I am working
on. The problem is that whenever I access /dev/md1 from the disk it gives
me a 'device not configured' error. I originally thought that this was an
error in how a preloaded image interfaced with the system, but I also
Thank you...
After a couple of hours, Jon Chen and I have figured out most of what you
just said :P :)
How would one use hints with a kld?
Badly. 8( You can only really set them with the loader right now.
There are a couple of kernel datastores that need some tweaking; the
I am writing a simple, I/O only device driver (no lectures about /dev/io
please ;). It has not PnP abilities, and I have run into the following
problem with bus_set_resource():
static int das1400adc_isa_probe(device_t dev)
{
struct das1400adc_softc *sc = device_get_softc(dev);
Thank you...
After a couple of hours, Jon Chen and I have figured out most of what you
just said :P :)
How would one use hints with a kld?
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer
Thank you...
After a couple of hours, Jon Chen and I have figured out most of what you
just said :P :)
How would one use hints with a kld?
Badly. 8( You can only really set them with the loader right now.
There are a couple of kernel datastores that need some tweaking; the
No, I am just using vinum stripes. The problem seems to have fixed itself
when I got a ufs_readwrite.c update from Matt after it was committed.
This is an interesting problem, since I am not entirely sure what fixed it,
if it is really fixed, etc...
Sigh, oh well.
--
David Cross
I have run across a problem since updating to -STABLE a week or so ago...
my CVS vinum partition would go corrupt after a few updates. I have been
running with no softupdates on my system for a day now and no problems.
Has anyone else seen this?
--
David Cross |
I pruned the Cc: list a bit...
One of the email messages that you quoted has the URL for the latest
development of the lockd code. As far as tests go it appears to be mostly
complete (there appears to be an issue with RPC64 on little endian machines,
but I have not yet had a chance to crawl
Going with the lockd code on builder is great with me. The last I had
looked it had some of the same issues as the lockd developed here (no
handling of grace periods, etc.), so on a featureset we are even. The rpics
lockd has the advantage of being known by some of us to a much greater extent
I'm not going to take such an action w/o the blessing of -core. :)
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of
The latest snapshots off of releng4.freebsd.org have a couple of problems
with the kern.flp/mfsroot.flp images. The first problem is that the
"boot.config" file doesn't exist; this makes serial console installs
problematic (although easily fixed).
Secondly the 2913 image has the problem
I have recently had the time to start devoting more time to FreeBSD;
especially the NFS code. I have stumbled upon a problem that seems
to be out of my league.
The problem is manifested when NFS/TCP connections just hang.
Sometimes for only a few seconds, other times for minutes.
Below is a
I upgraded to 4.1-RC1 today; attempted to fire up esound and my system hung.
I rebooted into X, fired up esound from text mode and system hung again
with a message that an NMI was caught.
I remember that the SBLive has some issues with ECC systems, resulting in
some NMIs being thrown. It would
Hmm... backing out to emu10k1.c version 1.6 did not fix my problem. Does
anyone else have a SBLive! in an ECC machine that is throwing an NMI
whenever you try to use xmms or esd? If not, I will try to binary search
the dates to see if I can find when the change that tickeled the NMI bug on
the
Yes, I know it is a long dead horse.
I was just looking for a copy of the modifications that were made by
Carlos Tapang. Could someone point me at them, or know Carlos's
current email adress?
--
David Cross | email: [EMAIL PROTECTED]
Lab Director
If you can reproduce the problem regularly then I recommend putting
a signal guard in to see if the corruption is being caused by the
signal interrupting at an inausipcious moment.
In main() block SIGHUP, SIGINT, SIGTERM, and SIGCHLD using sigsetmask().
Just prior to the
Ok, I posted some panic messages awhile ago that appeared to go largely
unnoticed. I just got it again (this time while running in X) and I
was able to capture them via serial console. I will separate this
message into 'fact', 'observation', and 'speculation':
Fact:
1) This was the same
I was previously under the impression that a NFS FH was basically a
concatenation of a device # and an inode #. This was shot down earlier today.
The problem was that a disk had failed and we where doing a replacement (the
new disk was not identical to the old, it was substantially larger). I
D'oh. My bad. I think I am remembering this behaviour from SunOS days
past.
Oh Well.
--
David Cross | email: [EMAIL PROTECTED]
Lab Director | Rm: 308 Lally Hall
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
I apologize profusely for the delay of this, but lockd-0.2 is out.
The URL is: http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-0.2.tar.gz
A couple of notes on this release:
1) the statd hooks to lockd are not yet done (or started)
2) you need a patched libc (for XDR64 types). I have included the
Version 2 of the lock manager is ready to be released. Amitha
says that it passes all of the tests in the suite posted by Drew (thanks
Drew). A noteable exception to this is on SGI where some lock requests
are never even received from the remote host. Also DOS sharing is not
yet complete.
On
Hmm... would this address the specific instances of our problems as well?
The two problems that we saw were a hard-locked machine, and the emacs
process in forever disk-wait. The emacs binary would never have been in a
position to be truncated or modified at all when this problem happened.
--
Ah!... ok, it is an NFS bug. I've been trying to track this down
for a while ever since you reported the 3.4 lockup bug. This is probably
related to a similar problem.
There is a bug somewhere related to NFS locking up while doing a
pagein from the executable image.
I just ran a tcpdump -s1500 for 5 minutes, gathered ~21k of data over that
time, no mentions of stale NFS handles from the NFS server... it would
appear the NFS client is not asking for those pages (it makes sense, since if
it asked and got the 'stale' error one would expect the SEGV).
--
David
Solaris has this nifty little tool for querying the bootparam server on a
booting system. Handy little gadget for getting various system configuration
at boot time. Neither OpenBSD nor FreeBSD have it (FreeBSD has callbootd,
but I cannot get it to work easily), so I wrote a simple 'bpgetfile'
This is only the second time ever this has happened, but it is still an
interesting problem... I have a large number of "emacs" processes stuck in
disk-wait. Here is the ps axl line for one such process:
33639 88194 1 0 -22 0 5856 340 vmpfw D qi- 0:01.34 emacs proxy.
Any
Ok... we'll start with the process table...
monica# ps axl | grep D
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
0 0 0 0 -18 0 00 sched DLs ??0:00.81 (swapper)
0 2 0 0 -18 0 00 psleep DL??1:10.93
There was some mention in the SBLive earlier this year (January), whatever
became of it? I checked www.posi.net and I do not see the driver listed
there at all. Pointers/suggestions?
--
David Cross | email: [EMAIL PROTECTED]
Acting Lab Director
I am seeing a situation where a 3.4 system hard-locks while running 3.4
(hard lock being that it does not respond to its serial console, nor is
it pingable). I believe (perhaps) that it may be NFS related, with a
program running on an NFS client when the executable itself is deleted
from the
Amitha (the person who has been working on the lockd code) has finished
most of his work. There are still some issues with handling async locks
and cancel messages. Also we were not able to implement the full NLM
protocol as the FreeBSD kernel does not currently request NFS locks (we
should
It is almost done. A working and very lightly tested version of the code will
be made available on Monday (Jan 24). It should be considered alpha quality,
I would not recommend running important NFS servers with this code.
--
David Cross | email: [EMAIL PROTECTED]
I have found a reproduceable panic in recent 3.4-STABLE images (past couple
of weeks). I am not sure how to reproduce it thought ;) The panic occurs
in the tty code it would appear. It is often preceded by strange TTY
behavior (strange characters suddenly appearing in the output, a randomly
We have come across a problem wrt to a network file lock manager.
Consider the case of a lock on a local file, and a request from a remote
machine to lock that same file. fcntl(fd, F_SETLK, fl) will return
immediately with EAGAIN (this is for an exclusive case, of course),
F_SETLKW will block
Ok... I have *had* it with the meta, but not really, lockd. Are there any
kernel issues with correctly implimenting rpc.lockd?How can I take a
filehandle and map it into a filename, with path, so I may open it and lock
it on the server? Are there any protocol specs? I downloaded the RFC
Does NetBSD have a working rpc.lockd... that would make this much easier.
--
David Cross | email: [EMAIL PROTECTED]
Acting Lab Director | NYSLP: FREEBSD
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Rensselaer
I've noticed about 99% of the panics on our machines are the result of NFS,
more often than not it is the result of a backing store file being blown
away underneath the client. ie. person editing a file on one machine,
compiling and running on a second, then removing the binary on the first
I have been noticing of late a disturbing trend of AMD wedging and
eventually taking the entire system down. The WCHAN that it is locked in is
"sbwait". I now have the luxury of having this happen on a non-critical
system with DDB compiled in (the system is the one I am typing on now).
How
I received the following panic() on our primary user fileserver. Note that
this is the first panic we have received in well over 80 days.
Below is a backtrace obtained from a kernel with debugging symbols:
IdlePTD 2977792
initial pcb at 264d38
panicstr: softdep_lock: locking against myself
We have a number of solaris 2.78 machines (I am in the process of installing
them now), and I notice that if I ls a directory that is mounted NFSv3/UDP from
a FreeBSD server to a Solaris 2.7 client there are a number of files that
show up missing. This is most intreaging with a large
We have a number of solaris 2.78 machines (I am in the process of installing
them now), and I notice that if I ls a directory that is mounted NFSv3/UDP from
a FreeBSD server to a Solaris 2.7 client there are a number of files that
show up missing. This is most intreaging with a large untar as I
We have a very hetergenous environment here (even among the FreeBSD boxes).
Each PC tends to be just a little bit different. This expecially causes
problems since we wish to have XDM on each machine on boot and have X
on a NFS partition. TO alleviate this we invented a simple Perl script
to
Softupdates has known bugs relating to filesystem full conditions which
I believe Kirk is working on. There isn't much you can do until then
other then either disable softupdates or work to avoid the disk-full
condition. The panic does not occur very frequently so working
Umm, you can edit /usr/X11R6/lib/X11/xdm/Xservers to configure xdm to
run say /usr/config/X (which would be stored on the local machiens hard
drive) instead of /usr/X11R6/bin/X. This is a much simpler solution.
:) (Just symlink /usr/config/X to /usr/X11R6/bin/XF86_Whatever.)
Simpler? It
We have a very hetergenous environment here (even among the FreeBSD boxes).
Each PC tends to be just a little bit different. This expecially causes
problems since we wish to have XDM on each machine on boot and have X
on a NFS partition. TO alleviate this we invented a simple Perl script
to
Softupdates has known bugs relating to filesystem full conditions which
I believe Kirk is working on. There isn't much you can do until then
other then either disable softupdates or work to avoid the disk-full
condition. The panic does not occur very frequently so working
Umm, you can edit /usr/X11R6/lib/X11/xdm/Xservers to configure xdm to
run say /usr/config/X (which would be stored on the local machiens hard
drive) instead of /usr/X11R6/bin/X. This is a much simpler solution.
:) (Just symlink /usr/config/X to /usr/X11R6/bin/XF86_Whatever.)
Simpler? It
Our ftp server crashed early this morning with what appears to be a softupdates
error:
Sep 13 09:56:19 stumble /kernel: pid 41477 (perl), uid 0 on /exports/share3/ftp/.2:
file system full
panic: softdep_write_inodeblock: indirect pointer #0 mismatch 0 != 15597568
syncing disks... panic:
Our ftp server crashed early this morning with what appears to be a softupdates
error:
Sep 13 09:56:19 stumble /kernel: pid 41477 (perl), uid 0 on
/exports/share3/ftp/.2: file system full
panic: softdep_write_inodeblock: indirect pointer #0 mismatch 0 != 15597568
syncing disks... panic:
Well, it has been a long time since I have needed to write an email with that
tagline. Our primary NFS server had been up for almost 2 months with no
panics. We did need to reboot it for a network change, but it was up for 28
days at that point. Anyway here are the details:
dev = 0x20014,
Well, it has been a long time since I have needed to write an email with that
tagline. Our primary NFS server had been up for almost 2 months with no
panics. We did need to reboot it for a network change, but it was up for 28
days at that point. Anyway here are the details:
dev = 0x20014,
I am modifying the tulip device driver to support this xircom card. I have it
almost entirely working, *except* that it goes into infinite re-neogitiate
loops. The card probes correctly at bootup, but any attempt to change
information via ifconfig ("ifconfig de0 inet ..." and "ifconfig de0
I am modifying the tulip device driver to support this xircom card. I have it
almost entirely working, *except* that it goes into infinite re-neogitiate
loops. The card probes correctly at bootup, but any attempt to change
information via ifconfig (ifconfig de0 inet ... and ifconfig de0 up,
and
I have been writing a nasty kludge to treat a CardBus bridge as a standard
PCI bridge (with static config) you may start throwing rocks now. I have
it to the point where I can (after the system is booted) 'pciconf -r
pci5:0:0 0' and get scan information (neat, huh :). Welll, I thought it would
I have been attempting to track down why cdrom boots will not work with
/boot/loader, but do just fine with the boot-block. I have come to the
following wild speculation, and stab in the dark. /boot/loader uses some
int13 stuff, which I found while reading in the boot0inst man page may cause
I have been attempting to track down why cdrom boots will not work with
/boot/loader, but do just fine with the boot-block. I have come to the
following wild speculation, and stab in the dark. /boot/loader uses some
int13 stuff, which I found while reading in the boot0inst man page may cause
I am trying to write a very kludgey/monolithic driver for a CardBus ethernet
adapter. I have run into a bit of a stumbling block on some issues. One such
issue is the attach (I need to map some registers of the adapter into memory
space so I can read/write values.). Anyway if someone could
I offered (to Theo T'So) before our (Computer Science Department at RPI)
resources to setup a RO CVS repo for Kerberos V. He accepted out offer
but things stagnated after that on setting up the details. My fault mostly
for not taking the tourch that has been passed. I am [now] offering
again,
I am terribly sorry. I had 2 messages about kerboers5 come in at the same
time (one from -hackers, one from mit), I replied to to wrong one.
--
David Cross | email: [EMAIL PROTECTED]
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
I offered (to Theo T'So) before our (Computer Science Department at RPI)
resources to setup a RO CVS repo for Kerberos V. He accepted out offer
but things stagnated after that on setting up the details. My fault mostly
for not taking the tourch that has been passed. I am [now] offering
again,
I am terribly sorry. I had 2 messages about kerboers5 come in at the same
time (one from -hackers, one from mit), I replied to to wrong one.
--
David Cross | email: cro...@cs.rpi.edu
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
I am attempting to get FreeBSD 3.2 and/or 4.0 to go on a TP 360c. The
problem I am having is that the keyboard works all the way up to sysinstall.
I can use the keyboard in the visual kernel config/etc. I searched and found
under 2.2 they suggested setting flags 0x10 on syscons. 0x10
You are quite right that the code in question was just moved from sc
to atkbd and there is essentially no difference between the two
versions.
This is the first time that I hear the flag 0x10 for sc works in 2.X,
but the flag 0x4 for atkbd does not in 3.1 or later :-( I think
I heard
I am attempting to get FreeBSD 3.2 and/or 4.0 to go on a TP 360c. The
problem I am having is that the keyboard works all the way up to sysinstall.
I can use the keyboard in the visual kernel config/etc. I searched and found
under 2.2 they suggested setting flags 0x10 on syscons. 0x10 isn't
I am attempting to get FreeBSD 3.2 and/or 4.0 to go on a TP 360c. The
problem I am having is that the keyboard works all the way up to sysinstall.
I can use the keyboard in the visual kernel config/etc. I searched and found
under 2.2 they suggested setting flags 0x10 on syscons. 0x10 isn't
You are quite right that the code in question was just moved from sc
to atkbd and there is essentially no difference between the two
versions.
This is the first time that I hear the flag 0x10 for sc works in 2.X,
but the flag 0x4 for atkbd does not in 3.1 or later :-( I think
I heard just
A friend writing some portable network tunneling software ran into an
interesting thing... when you specify "IP_HDRINCL" with SOCK_RAW, and
IPPROTO_RAW you need to construct the outgoing packet in host byte order.
This seems wonderfully inconsistent with all of the other socket based
A friend writing some portable network tunneling software ran into an
interesting thing... when you specify IP_HDRINCL with SOCK_RAW, and
IPPROTO_RAW you need to construct the outgoing packet in host byte order.
This seems wonderfully inconsistent with all of the other socket based
networking
Here is a pro vote for enabling BPF in GENERIC:
It will let us use a dhcp client in the install programs, this is of tremendous
use to many people as DHCP starts to become much more popular. I cannot
net install a machine at home since that is on a DHCP cable modem service.
Also, if root is
Here is a pro vote for enabling BPF in GENERIC:
It will let us use a dhcp client in the install programs, this is of tremendous
use to many people as DHCP starts to become much more popular. I cannot
net install a machine at home since that is on a DHCP cable modem service.
Also, if root is
1 - 100 of 196 matches
Mail list logo
