> I am not sure the right forum to ask this question - is there any effort done
> to find portable code between different OSes, particularly freebsd and linux?
> Specifically, the networking layer could be portable between the 2 and there
> could be some set of APIs to call into the OS specific
> Can you back this up? I cannot recall having ever rendered a FreeBSD
> system unbootable due to UFS/UFS2 problems after a power failure or
> crash. I once had a problem with snapshots that made background fsck
> fail and crash the system, but it was fixable by booting single user and
> running fs
> >Please don't. This functionality is extremely useful. Consider this:
>
> It may be useful but it is nonstandard.
FreeBSD mostly follows standards. But there are several examples of
FreeBSD *not* following standards because the standards are considered
broken.
In this particular case - I co
> > Hopefully European GPS project (Galileo) will provide an alternative.
> > It still has a long way to go though.
>
> Galileo strikes me as unnecessary, unless the receivers will be
> cheaper to get the same resolution. The 1 meter resolution seems
> a little poor, compared to differential.
G
> Whether the packet loss is random or not, there is packet loss occuring.
> What's the exact network setup between the two machines? Perhaps it's a
> collision occuring each time.
Please don't imply that normal half duplex Ethernet collisions cause
packet loss. They don't.
Steinar Haug, Nethel
> In linux, the packet reception can be done efficiently through the usage of
>ethernet sockets.
>
> In FreeBSD, one of the option is by using the BPF. But, as already commented,
>BPF is not a high performance device.
It sounds like you're saying that BPF is less efficient than Linux
> > > There is a bug in Adaptec BIOSen that they will not tolerate DD disks.
> >
> > Which controllers have this bug? I've got a whole bunch of 7880 and 79xx
> > controllers with disks running in DD mode and never have had this problem.
>
> Happens to me on L440GX+ boards.
Also happens on IBM N
> What's the point with having device nodes for devices you don't have?
A warm fuzzy feeling of having all the device nodes you're used to,
even if the devices don't exist? :-)
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe f
> I tested your patch and it solved our problem 100%. There's no
> timedrift anymore.
>
> Do you think the patch will make it in 4.4R. ? We need it urgently.
I can confirm the solution to the time drift problem. Our Netfinity
5600 SMP servers with Serverworks LE chipset now stay nicely in sync.
> > You use emacs, don't you?
>
> No, vi. My first experiences with Unix (SysV.2) were in the days that
> Emacs was considered anti-social (on 8MB memory machines with 68020 CPUs).
What, you mean you *haven't* run emacs on a Sun-3/50 with 4 Mbytes? :-)
Steinar Haug, Nethelp consulting, [EMAIL P
I'm seeking recommendation for a backup system (software) that can be
used with a decent sized tape library, probably LTO based, and FreeBSD
4.3-STABLE.
I'm sure we could roll our based on freely available tools (eg. Amanda)
- but by now I'm used to Tivoli ADSM/TSM, and *like* the convenience
ADS
> Unfortunately, when I choose a netmask such as 255.255.255.227 (11100011),
> I'm
> left with only 6 IPs for the DMZ:
Netmasks must be contiguous, which means that 255.255.255.227 is an
invalid netmask. (This is a CIDR requirement.)
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubs
> Second, it looks like there's a few things in thttpd that could be
> optimized further.
...
> .) pre-forking, this would help with stalling on disk IO.
Since the author of thttpd makes a point of *not* using pre-forking (and
thttpd still being very fast), I'm not sure that pre-forking patches
w
According to the "Maxtor picks Windows, dumps open source" article at
http://news.cnet.com/news/0-1003-200-5009496.html?tag=lh
FreeBSD "did not support large file sizes, Macintosh and newer Novell
file systems, or backup and management software from companies such as
OpenView, Tivoli and
I work mainly for Enitel, a medium sized ISP in Norway. We use FreeBSD
a lot (eivind and des can tell you more about this). Today I got an
interesting question from IBM Norway: What would be needed for IBM to
support FreeBSD for Enitel? Basically: What FreeBSD version, what kind
of hardware do we
> Compact Flash. They take those Compact Flash cards that are used in
> digital cameras and run them in TrueIDE mode so they look for all the
> world like a IDE disk to the host computer.
Any specific types/brands of CF to IDE adapter you could recommend?
Steinar Haug, Nethelp consulting, [EMAI
> I am running FreeBSd 4.2 on machine with 2 Pentium II CPU's
>
> When I run "top", it shows my processes with 0.00% CPU
Are you by any chance running an Asus P2B-DS motherboard? There was
an issue with some versions of the BIOS for the motherboards not
initializing the Real time clock (as far a
> Relevant dmesg output:
>
> fxp0: Ethernet address 00:08:c7:7b:05:bd
> bpf: fxp0 attached
> fxp1: Ethernet address 00:b4:c0:91:d2:9c, 10Mbps
> bpf: fxp1 attached
> fxp2: Ethernet address 00:b4:c0:91:d2:9c, 10Mbps
> bpf: fxp2 attached
> fxp3: Ethernet address 00:b4:c0:91:d2:9c, 10Mbps
>
> Say wh
> I know I'm getting into this late but I can reliably reproduce this
> problem. I ran into it about 3 months ago when using a custom PXE-based
> installer for our SCSI boxes. I even annoyed -hackes and got John Baldwin
> to help me decode the register dumps. The IP does end up in the SCSI BIOS
> Of course it works, and very well. You should try hping
> (http://www.kyuzz.org/antirez/hping/) which is a _very cool_ tool
> developped by Antirez. With it you could do (among many things)
> traceroute over tcp.
Ah, you mean just like FreeBSD's "traceroute -P tcp" does?
Steinar Haug, Nethelp
> Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to
> the 840 boards, but using some kind of "ServerWork LE" chipset. However, I
> have also been hearing bad news about these boards as well.
The IBM Netfinity 3500 servers (possibly other Netfinity models also)
use the Server
tcpdump -p (interface in non-promiscuous mode) shows incoming and outgoing
traffic in 3.4-STABLE (as expected).
tcpdump -p does *not* show outgoing traffic in 4.0-STABLE. Incoming is
fine. Is this intended?
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
> > I suspect a generic chipset fault, or some design quirk that we are not
> > working around. Note that the windoze drivers for these devices put them
> > permanently in store-and-forward mode. if_de has the exact same problem on
> > all of the systems above.
...
> Store and forward mode intro
> > > Such editors are broken. What if the file is a symlink ? IMHO
> > > open() write() write() write() ftruncate() close() is the only way.
> >
> > If that is the only way, then emacs is of course broken. (And I
> > disagree - I use emacs every day...)
>
> Now there's an argument waiting to
> Such editors are broken. What if the file is a symlink ? IMHO
> open() write() write() write() ftruncate() close() is the only way.
If that is the only way, then emacs is of course broken. (And I
disagree - I use emacs every day...)
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To U
> Yeah, I miss the blinky lights. I went to the x-over cable because
> the hub I bought originally was giving me non-stop collisions under
> load.
It should be noted that a lot of collisions is *expected* under load.
If you saturate a half-duplex segment (using for instance ttcp), the
sende
> i have compiled freeBSD 3.4 SMP. but when i try to boot it the kernel
> shows "Testing APIC 8254" and then it hangs. earlier i had run mptable
> and it showed:I/O APICs:
> --
> {Lots of stuff}
>
> APIC ID Version State Address
> 2 0x20
> A while back, I wrote a simplistic, but effect script to print out
> information about who has a particular port open.
There is already a nice program to do this as part of the standard
FreeBSD distribution: sockstat. It deserves wider use, IMHO.
Steinar Haug, Nethelp consulting, [EMAIL PROTEC
> I still have uncommitted patches that add support for the Netfinity
> 5600's host-to-PCI bridge. They're not perfect, but they work fine.
>
> http://www.freebsd.org/~des/software/>
As far as I can see, these patches aren't needed for 4.0-STABLE. I
have a 4.0-STABLE system here with no
> > A modern hard disk can do 10-30 MBytes/sec to/from the platter, assuming
> > no seeks. But the moment it needs to seek the performance drops
> > drastically ... generally down to 1-5 MBytes/sec.
>
> I haven't seen any 30MB/s. The 10K LVD IBM's were just about the
> fastest at 20MB/s co
> > I once put in an extra digit in the serial number.
> > This made a secondary use a serial number, which was larger than mine, and
> > could probably be the modulus 2^32.
> > I had to call the hostmaster there (A "3.rd secondary" hosted at our
> > uplink) to get the zonefile removed, so the rig
Does anybody know of tools to read a Digital Unix "vdump" tape on FreeBSD?
I have a number of such tapes, and would prefer to read them on an (Intel)
FreeBSD box instead of having to reinstall DU on a machine which has had
its disks wiped.
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To
> > 1) I managed to crash an intel N440BX mobo with an fxp card and the
> > onboard ncr drivers. Lots of network traffic (ping floods) and disk IO
> > (rawio in parallel on two disks) took it down in something like two
> > hours. I know this is a known bug, I'm just offering core dumps and
> > te
> > Imagine: cp file file2, file and file2 reference the same exact blocks,
> > but modified chunks of file2 would be given their own private blocks.
>
> This is not a microsoft innovation, actually, I believe it was a VMS
> innovation. It's called a generational filesystem. the original is
> s
> > Sorry for the lameness of this question...but where can I find the Symbios
> > driver for FreeBSD developed by Gerrard Roudier? I'm having some issues
> > with a Symbios controller that I suspect may be the fault of the NCR
> > driver and not the controller itself.
>
> It's in 4.0-CURRENT ...
We have a News server running on Compaq Proliant 3000 hardware, with
NCR/Symbios 875 based SCSI controllers. This machine ran extremely
stable (but using only one processor) on FreeBSD-2.2.8. Due to the
News server, this machine sees reasonably heavy disk and network
traffic.
On FreeBSD 3.x we ha
> > I agree, *IF* IPv6 ever becomes a reality, we will look at this.
>
> So when will you consider that it became a reality? :-) Or am I just
> dreaming that some operating systems and routers ship with IPv6 and
> that IANA, ARIN, APNIC and RIPE are dishing out IPv6 addresses and
> that we are in
(Warning: Unrelated to FreeBSD except for the fact that FreeBSD-current
and recent -stable traceroute supports the -P option.)
I need to find out if IP protocol 50 (used by IPSec) is being blocked on
the way from Hong Kong to a customer of Telia in Norway. Could somebody
in or near Hong Kong, run
> > That's what BSD just does - see open(2):
> >
> > When a new file is created it is given the group of the directory which
> > contains it.
>
> That's pretty weird (but quite correct). Just checked on NetBSD and found
> the same. I would have expected this behaviour only if the SGID
> Heh... well I've already enabled flags 0xb0ff, which has improved things
> somewhat, but our hardware vendor slipped in some IBM DeskStar drives on
> us, and they've been no end of trouble.
Note that IBM Deskstar drives are very good performers for desktop use
(and highly respected), but they
> Of course its a switched network with full duplex operation. But now
> that the general answer is that it is not a limitation of the nic card
> I am going to look elsewhere. I was not to sure if it was actually a
> limit myself, its just that I observed it on two different machines.
> They how
> This configuration is neccessary because by my estimation I have run
> into a limit on the intel pro 100 netcards of 6,000 packets/second.
> This limit equates to about 30 to 32 megabit/second of web traffic in
> our situation. I am wondering if anyone else has noticed this limit?
The Pro 100B
I have a Compaq Proliant 3000 (2 x PII-333) running 3.3-STABLE which has
crashed several times with the following backtrace:
#0 boot (howto=256) at ../../kern/kern_shutdown.c:285
#1 0xc0144299 in panic (fmt=0xc023eb04 "m_copym") at ../../kern/kern_shutdown.c:446
#2 0xc015ac7e in m_copym (m=0xc
> >However, the problem is, it only works with 3.0-current from
> >around January. It doesn't work with any recent -stable or
> >-current. I suspected it was because of newbus, so I tried
> >to port it, but without success. :-(
>
> It *does* work on recent CURRENT.You need not to patch for CUR
> > 'stats Causes named to dump its statistics to /etc/namedb/named.stats'
> >
> > This also applies for /var/tmp/named_dump.db, that one goes also in
> > /etc/namedb.
>
> Guys, before we fix the manpage on this, could someone please follow
> this up with -hackers? I was under the impression
> > 'stats Causes named to dump its statistics to /etc/namedb/named.stats'
> >
> > This also applies for /var/tmp/named_dump.db, that one goes also in
> > /etc/namedb.
>
> Guys, before we fix the manpage on this, could someone please follow
> this up with -hackers? I was under the impressio
rndcontrol doesn't work very well for SMP systems. I have a system here
with IRQs 16 and 18 for Ethernet and SCSI:
fxp0: rev 0x05 int a irq 18 on
pci0.10.0
ahc0: rev 0x00 int a irq 16 on pci0.12.0
and I'd like to use these with rndcontrol. However, the ioctl chokes on
IRQ >= 16. From i386/i386
rndcontrol doesn't work very well for SMP systems. I have a system here
with IRQs 16 and 18 for Ethernet and SCSI:
fxp0: rev 0x05 int a irq 18 on pci0.10.0
ahc0: rev 0x00 int a irq 16 on pci0.12.0
and I'd like to use these with rndcontrol. However, the ioctl chokes on
IRQ >= 16. From i386/i386
> I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
> on recent versions of -STABLE. Here's an excerpt from messages; kernel
> #3 is a recent -STABLE (yesterday's sources), while kernel #2 is
> 3.2-RELEASE. The config file for both is identical.
I can confirm problems with DMA
> I'm experiencing serious problems with DMA (even normal DMA, not UDMA)
> on recent versions of -STABLE. Here's an excerpt from messages; kernel
> #3 is a recent -STABLE (yesterday's sources), while kernel #2 is
> 3.2-RELEASE. The config file for both is identical.
I can confirm problems with DM
> > If the switch "just has the default setup" I would recommend that
> > somebody sit down and read the manual and try to *understand* what is
> > happening - probably also try to experiment a bit with the switch
> > configuration. Because what you're seeing is definitely not normal.
>
> We
> > Then either there is a hub between your net and the switch, or the switch
> > is badly misconfigured.
>
> Well, the switch came out of the box and just had the default
> setup It just has a IP assigned to it... And there is no hub between
> the net and the switch since all the modem
> No idea, all I know is that people on our LAN without changing MAC
> addresses can see all traffic going on the LAN. Even from our FreeBSD box
> with trafshow, we can see traffic that is destined for the global net from
> the modem dialups.
Then either there is a hub between your net and
> > If the switch "just has the default setup" I would recommend that
> > somebody sit down and read the manual and try to *understand* what is
> > happening - probably also try to experiment a bit with the switch
> > configuration. Because what you're seeing is definitely not normal.
>
> W
> > Then either there is a hub between your net and the switch, or the switch
> > is badly misconfigured.
>
> Well, the switch came out of the box and just had the default
> setup It just has a IP assigned to it... And there is no hub between
> the net and the switch since all the mode
> No idea, all I know is that people on our LAN without changing MAC
> addresses can see all traffic going on the LAN. Even from our FreeBSD box
> with trafshow, we can see traffic that is destined for the global net from
> the modem dialups.
Then either there is a hub between your net and
> > You see the MAC of the switch's port. It's been too long since I've
> > played on a Catalyst... but what does 'sh arp' display? Any arp -> port
> > -> host correlations? Good luck... :)
>
> Even if it did show the arp of the actual host, it's useless if it
> doesn't show the IP of t
> > You see the MAC of the switch's port. It's been too long since I've
> > played on a Catalyst... but what does 'sh arp' display? Any arp -> port
> > -> host correlations? Good luck... :)
>
> Even if it did show the arp of the actual host, it's useless if it
> doesn't show the IP of
> > Please read the documentation.
>
> This is hard since the actual machines and switches are almost
> 6000 miles away from me and the last time I checked, it didn't come with
> manuals. I know my way around the Cisco routers but the switches is still
> a mystery...
All of the Cisco docum
> I'm not sure if it shows the mac address of the cisco's port or
> the actual device connected to it...
>
> FastEthernet0/1 is up, line protocol is up
> Hardware is Fast Ethernet, address is 0090.abea.3bc1 (bia
> 0090.abea.3bc1)
>
> FastEthernet0/2 is up, line protocol is up
> Hardwa
> > Please read the documentation.
>
> This is hard since the actual machines and switches are almost
> 6000 miles away from me and the last time I checked, it didn't come with
> manuals. I know my way around the Cisco routers but the switches is still
> a mystery...
All of the Cisco docu
> I'm not sure if it shows the mac address of the cisco's port or
> the actual device connected to it...
>
> FastEthernet0/1 is up, line protocol is up
> Hardware is Fast Ethernet, address is 0090.abea.3bc1 (bia
> 0090.abea.3bc1)
>
> FastEthernet0/2 is up, line protocol is up
> Hardw
> > Ah, you have a point there. The problem is we have so many wires,
> > we don't know which port goes to what on the Catalyst so we had it on
> > autodetect and FreeBSD does boot up with fxp0 showing 100Mbps Full Duplex.
> >
> Cisco's can show you which mac-adresses are on which port. Proba
> > Ah, you have a point there. The problem is we have so many wires,
> > we don't know which port goes to what on the Catalyst so we had it on
> > autodetect and FreeBSD does boot up with fxp0 showing 100Mbps Full Duplex.
> >
> Cisco's can show you which mac-adresses are on which port. Prob
> > As I said, I used ttcp. ttcp is a "network only" test - it can source
> > or sink traffic itself. This is nice because you avoid other sources of
> > problems (disk bandwidth etc). I tended to run the tests for 30 seconds
> > to one minute.
>
> Oops, must have missed that one. How do I
> Hmmm, how did you do the measurement and how big of a file does it
> need?
As I said, I used ttcp. ttcp is a "network only" test - it can source
or sink traffic itself. This is nice because you avoid other sources of
problems (disk bandwidth etc). I tended to run the tests for 30 seconds
t
> I mean Mega as in 100. 100Mbps Ethernet should be equal to
> about 12500Kbytes/sec which is equal to 12.5Mbytes/sec. 94.93Megabits/sec
> doesn't equal to 100Megabits/sec.
12.5 Mbytes/sec on the wire *is* 94.93 Megabits/sec application to
application using TCP - that's what I'm trying
> It meets the spec when shipped but the bends, curves, temperature
> and other factors do affect the performance. I guess a good way to test
> the cable is with FreeBSD since it's the only real OS I've seen that can
> do like real world speeds. The only thing is that has anyone really saw
> > As I said, I used ttcp. ttcp is a "network only" test - it can source
> > or sink traffic itself. This is nice because you avoid other sources of
> > problems (disk bandwidth etc). I tended to run the tests for 30 seconds
> > to one minute.
>
> Oops, must have missed that one. How do I
> Hmmm, how did you do the measurement and how big of a file does it
> need?
As I said, I used ttcp. ttcp is a "network only" test - it can source
or sink traffic itself. This is nice because you avoid other sources of
problems (disk bandwidth etc). I tended to run the tests for 30 seconds
> I mean Mega as in 100. 100Mbps Ethernet should be equal to
> about 12500Kbytes/sec which is equal to 12.5Mbytes/sec. 94.93Megabits/sec
> doesn't equal to 100Megabits/sec.
12.5 Mbytes/sec on the wire *is* 94.93 Megabits/sec application to
application using TCP - that's what I'm tryin
> It meets the spec when shipped but the bends, curves, temperature
> and other factors do affect the performance. I guess a good way to test
> the cable is with FreeBSD since it's the only real OS I've seen that can
> do like real world speeds. The only thing is that has anyone really saw
> I am benefiting from it for sure. I guess what I was asking
> originally was if the higher frequency rated cables will give it more
> headroom since the 100BaseTX ethernet does push CAT5 to the limit.
100BaseTX is specified to run on Cat5 cabling, and with proper Cat5
cabling you get a a
> I am benefiting from it for sure. I guess what I was asking
> originally was if the higher frequency rated cables will give it more
> headroom since the 100BaseTX ethernet does push CAT5 to the limit.
100BaseTX is specified to run on Cat5 cabling, and with proper Cat5
cabling you get a a
> If this is correct, then solaris is using a VMSPACE = SWAPSPACE
> model. FreeBSD uses a VMSPACE = SWAPSPACE + REALMEM model.
AFAIK it has been stated quite explicitly by the Solaris folks that
Solaris 2.x uses VMSPACE = SWAPSPACE + REALMEM. This is *different*
from SunOS 4.1.x.
Steinar
> If this is correct, then solaris is using a VMSPACE = SWAPSPACE
> model. FreeBSD uses a VMSPACE = SWAPSPACE + REALMEM model.
AFAIK it has been stated quite explicitly by the Solaris folks that
Solaris 2.x uses VMSPACE = SWAPSPACE + REALMEM. This is *different*
from SunOS 4.1.x.
Steina
> Also, your named is badly misconfigured if it grows to 130MB. We never
> allow ours to grow past 30MB.
How do you know what kind of name server configuration kre is running?
Here's an example of a name server running *non-recursive*, serving
11.500 zones:
PID USERNAME PRI NICE SIZE
> Also, your named is badly misconfigured if it grows to 130MB. We never
> allow ours to grow past 30MB.
How do you know what kind of name server configuration kre is running?
Here's an example of a name server running *non-recursive*, serving
11.500 zones:
PID USERNAME PRI NICE SIZ
> I would say it is not _acceptable_. The code shouldn't go into our
> source tree until the known buffer overflow problems have been fixed.
> It's just stupid to add buffer overflow problems to a program that is
> always run as root.
Minor correction: tcpdump will run happily as non-root as lon
> I would say it is not _acceptable_. The code shouldn't go into our
> source tree until the known buffer overflow problems have been fixed.
> It's just stupid to add buffer overflow problems to a program that is
> always run as root.
Minor correction: tcpdump will run happily as non-root as long
> It would make sense except that the last time someone tried, some people
> complained that it made it too easy to sniff passwords etc.
There are plenty of patches to do this available, and plenty of other
packet sniffers that do this. AFAIK even the attitude of the tcpdump
maintainers is changi
> It would make sense except that the last time someone tried, some people
> complained that it made it too easy to sniff passwords etc.
There are plenty of patches to do this available, and plenty of other
packet sniffers that do this. AFAIK even the attitude of the tcpdump
maintainers is changin
> > Another datapoint ot consider, it seems that Linux (at least the derivative
> > version maintained by Alan Cox -- the other one :) ) has now grown an LVM
> > system (probably à la HP or AIX). That's what I've been told yesterday during
> > a small conference about Linux and free software in Fr
> > Another datapoint ot consider, it seems that Linux (at least the derivative
> > version maintained by Alan Cox -- the other one :) ) has now grown an LVM
> > system (probably à la HP or AIX). That's what I've been told yesterday
> > during
> > a small conference about Linux and free software i
> Linux is a Unix clone, while FreeBSD is Unix. Don't confuse people with
> this.
I'm afraid that attitude isn't going to help Unix agains Windows...
I use FreeBSD for all my systems. I still go around and tell people that
Linux is one several Unix variants, and I intend to continue doing this.
F
> "David E. Cross" writes:
>
> > fd=open(argv[1], O_CREAT, 600);
>
> Since this opens the file so that it cannot be written to, not
> to mention the really weird mode it will get if it's created by
> that open(), the rest of the thing doesn't deserve to work.
That may be the case
> > I have found a small problem in nameser.h in the ns_rr structure.
> > This structure has a member named class that causes a compilation
> > problem if you include nameser.h into C++. I suspect that I may be
> > the only person to ever hit up against this (:. Any comments before
> > I summit
> > I still don't see what the fuss is about in any case since soft
> > updates would be SLOWER than the async mode I use during installation
> > and anyone who's actually bothered to benchmark extraction of files
> > with the two systems knows this. Have you ever timed it? If not, why
> > not?
> I don't think that so many collisions are normal! I think there is a
> problem, because at work we nearly only use 3COM 100 Mbit cards and
> don't have much collisions. Even under high load!
Collisions on half-duplex Ethernet are *normal*. Get used to it.
Collisions is the standard flow control
> Has anyone done any performance benchmarking on the TIGON Gigabit
> Ethernet drivers? Curious to see what sort of link saturation can be
> achieved with various boxen/applications...
470 Mbps application to application using ttcp, on a PII-350 back to
back with a Celeron 300A overclocked to 337
> The OpenBSD team does a lot wrt auditing of the complete sourcetree, but
> then the question is: is this valid concern or is this pure paranoia.
> OpenBSD does a lot of valid changes but borders (and sometimes crosses thta
> border) on paranoia, wrt code.
Given the number of postings to BUGTRAQ
> 1: The built-in SCSI ROM is v2.01, there was mention of BIOS 1008 including
>2.11. I applied the 1008 flash and I am still v2.01 (I don't know if
>this matters at all)
At least for the P2B-S, you need 1008B, not 1008. The file I got from
ftp.asus.com is:
rw-r--r--
> Things like DECnet set the MAC address. Don't ask me why though.
Because there is a one to one correspondence between the DECnet (Phase
IV) address and the MAC address. Ie. if you specify the DECnet address,
you have also implicitly specified the MAC address.
Steinar Haug, Nethelp consulting, s
> > Not in any 'standard' card, no. Some cards (in SUN workstations) allow
> > you to swap the EEPROM with the mac address, and I'll bet somewhere
> > someone has designed a card with a programmable mac address, but
> > normally it's not settable.
>
> while ifconfig might miss this functionality,
> Just out of curiosity.
> What is the ``interrupt latency in the FreeBSD kernel'' problem
> and what are the ``Bruce's "fast" interrupt hacks''?
Poul-Henning Kamp made some interesting interrupt latency measurements
for the FreeBSD kernel. See
http://www.freebsd.org/~phk/interruptlatenc
95 matches
Mail list logo
