I asked on the Netapp list ([EMAIL PROTECTED]), and received a copy
of postmark-1.01. Note that this is *not* the latest version (which is
1.11, according to the Netapp web site), but at least it should give you
an idea of what the code is like. The 1.01 source is now available from
If _we_ don't start to do something about it, big brother _is_ going
to do something about it. Trust me on this one, being a member of the
USPA I know that we are far better off implementing our own (as ISP's)
set of safe gaurds that help eliminate certain undesirable behavior.
[.]
Does anybody successfully use ports/sysutils/{lmmon|chm}
with the Abit's BP6 motherboard ?
snip
II only receive:
IOCTL: device not configured
from lmmon and chm.
I have the same problem with the 'wmhm' port. I also have Abit BP6 with two
450 Mhz Celerons.
Ditto. BP6 with
Current as of 8. october attached USB, Power Mgmt, sound just fine.
Current as of today no longer does. Here are the relevant bits of a
dmesg diff:
usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2
pcm0: unable to map register space
device_probe_and_attach: pcm0 attach returned 6
This is an Abit BP6 board with two Celeron 366, 256 MByte memory, one
Soundblaster PCI 128 (pcm0) and one Hoontech (pcm1) sound card. Below is
the complete dmesg from today's current, and the kernel
I get high numbers too:
FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun
Jun 13 20:31:43 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys
/compile/mailtoaster1 i386
Read the original message. It says:
I would appreciate it if people running -current would run a
I see this:
Root mount failed: 22
This suggests you may have an old loader, or the loader's parsing of
your /etc/fstab file may be failing. I probably need to add a
diagnostic to it to help us track this down.
Okay, here's another one. I have 3.3-STABLE on wd0s1a, and -current
If there are problems, the authors would like to hear
about it directly, instead of reading it in some mailing
list by accident...
It's an editorial complaint. I don't like the breaking the
program into seperate programs by function. IMO, DJB is wrong,
and this does nothing to enhance
I believe you can also configure policy based routing on the Cisco to ship
the traffic to your caching server - without GRE encapsulation - and
achieve the same results.
You can achieve *almost* the same results. What the policy based routing
doesn't give you is detection of a dead cache
The cooling theory sounds the most plausible so far. I'm not over clocking
my CPUs (Celeron 366s) and have appropriate cooling installed. But the
machine is kept in a small room, with a bunch of other machines and gets
a bit warm at times.
I have seen a couple of suggestions that this may
The following patch fixed the problem for me. For extra points,
rename the function.
That fixed the problem for the me too. Thanks!
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Actually I think this is an indication of really old boot blocks.
The old bootblocks passed in a Bmajor number for the root device.
Could you try to update your bootblocks with the disklabel
program and see if that stops the warning Manfred ?
I can't speak for this case, but the one I
I get this in boot mesgs and I don't know how to fix it.
Device char-major=13 minor=0 opened in block mode, convert to char mode
with /dev/MAKEDEV before 2000-07-01
There is a bug somewhere in the rootmount code.
It's the following VFS_MOUNT call at line 215 of vfs_mountroot_try()
No, I havn't tracked down the last couple of causes of this, but I
will try to reproduce it as you describe it with some debugging added.
How hard would it be to print the filename (or the device/inode) that
triggers the warning?
Not at all (warning: cutpasted patch, tabs are screwed
All my disks have bootblocks and (spare) boot partitions. All the
bootblocks are DD mode. I don't see any point in using obsolete fdisk
tables. (There's IMHO only one purpose obsolete fdisk tables are good
for, co-operation with other operating systems in the same machine.
None of my
has anyone gotten freebsd (current or other) running on one of these?
Which Proliant model are you talking about?
i've tried 4.0, 4.1, and -current, and the kernel panics on me with
the following:
sym0: 895a port 0x1000=0x10ff mem
0xb110-0xb1101fff,0xb140-0xb14003ff irq 11 at
BTW, these IBM 75GXP drives off of the HPT-370 are amazingly fast for
IDE.
From my own measurements I'd say these drives are amazingly fast, period.
They compete rather well with SCSI drives.
A big thanks to sos for the HPT-370/UDMA100 support!
Steinar Haug, Nethelp consulting, [EMAIL
Anyone know the history on the '#ifdef FSIRAND' code?
Randomized file generation numbers to make NFS attacks more difficult,
as far as I can remember.
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
Rant second: FreeBSD *violates* years of traditions with it's
treatment of /usr/local. /usr/local is for *local* things, not add-on
software packages! Coopting /usr/local for non-local software creates
needless complexity and confusion, which of course leads to needless
pain.
Agreed. It
Agreed. It would be nice if FreeBSD could use the same system as NetBSD,
storing the packages/ports under /usr/pkg.
That's why PREFIX exists.
Okay, let me rephrase: It would be nice if FreeBSD *by default* stored
the packages/ports under /usr/pkg, like NetBSD (and the corresponding
Actually, last time I checked, I think stable did not install with a RO
/usr/src either. Anyone know if this is still the case?
I have installed -stable many times with /usr/src mounted readonly
via NFS.
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to
I have a KT7 with an athlon 1.1, no problems with ATA66, don't have a 100
drive though. Works fine, does make worlds in a little over an hour with
384mb of pc133, but I do have to downclock the pc133 to 100 because these
via chips have some problem with agp and pc133 at the moment.
Another
I think the fact is that most direct users of RCS use it in a very
simple way, and
it works just fine for that. with no real need for any updates or any
change.
With all due respect Julian, The more we discuss this more this really
points to the problem that FreeBSD appears to be a
The fact that we have so many people who are radically change-averse, no
matter how rational the change; is a bug, not a feature.
This particular bug is complicated dramatically by the fact that the
majority view seems to lean heavily towards If I use it, it must be the
default and/or
I want to ask some serious questions here, because I genuinely want to
understand your thought process.
1. Do you install *any* ports/packages on a new system before you update
the source?
Answering just for myself here...
Going back a bit, in many cases I didn't need to install any
Seconded; but compare to Linux which has mutiple different commands to
do networking, as well as 'net'. :-)
we do too -- we have arp, route, ifconfig, sysctl and possibly
more that i am not aware of.
Note that at least arp, route and ifconfig have been there since very
early BSD releases
Now all users that want to profile anything need to build their own custom
FreeBSD? That seems even more nuts to me.
So that all users that do not want to profile anything need to build
their own custom FreeBSD?
No. It simply means these users will have profiled libraries available
that
If tcsh could be updated to version 6.18.00 set autorehash would be
really nice. With that you'll never have to type rehash again. :)
Yes please!
Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
freebsd-current@freebsd.org mailing list
However, if you always want to use tmpfs instead of stable storage,
please do not. Some people expect /tmp to be persistent. This is why
/etc/defaults/rc.conf has clear_tmp_enable=NO. Changing this would break
the POLA.
This is a mistake.
The default should be clear_tmp_enable=YES
The default should be clear_tmp_enable=YES
if only to uncover those broken configurations that expect /tmp to be
persistent.
If you want to break POLA and make a lot of people angry, sure.
Otherwise no.
I would very much like an example of where /tmp is expected to persist.
I
MM ... and as far as I can tell none of them is currently usable
MM on an IPv6-only FreeBSD (like protecting a host with sshguard),
MM none of them supports stateful NAT64, nor IPv6 prefix translation :(
IPv6 prefix translation?! AGAIN!? FML. I've thought, that IPv6 will
render all that
Also, the openbsd stack has some essential features missing in freebsd,
like mpls and md5 auth for bgp sessions.
I use MD5 auth for BGP sessions every day (and have been doing so for
several releases). One could definitely wish for better integration -
having to specify MD5 key both in
Also, the openbsd stack has some essential features missing in freebsd,
like mpls and md5 auth for bgp sessions.
I use MD5 auth for BGP sessions every day (and have been doing so for
several releases). One could definitely wish for better integration -
having to specify MD5 key both
I have a server with an Intel X520-LR1 Ethernet card, which is a
10GBase-LR card:
...
The problem is that this card is shown by ifconfig as a 10GBase-SR card:
...
I made a 1-line patch to the 8.2-RC1 code, enclosed below, and now have
ifconfig showing the expected value:
Problem report and
I have a server with an Intel X520-LR1 Ethernet card, which is a
10GBase-LR card:
http://ark.intel.com/Product.aspx?id=41164
The card contains the Intel 82599ES controller:
http://ark.intel.com/Product.aspx?id=41282
pciconf -lv shows:
ix0@pci0:28:0:0:class=0x02 card=0x00068086
as far my knowledge goes, radiation from multi-frequency subcarriers in
a multi-path
system such as a wireless network (802.11 a/g/n) or a microwave oven
is something
you definitely want to avoid sitting in while hacking FreeBSD...
https://gthc.org/wiki/Advisories/OFDM_20110315
I may
In other words, ada isn't the problem here, it's that we all still think in
terms of the 1980's when systems didn't autoconfigure and device names were
important hints to system functionality. That time has thankfully passed,
and it's time for us to catch up.
If this is important for disk
It looks like they distribute RSA to everyone, including the US mirrors,
and it's not built by default unless you take explicit action to enable it
(i.e. it just builds a subset of the full distribution). Last time I
Hmm, according to their own press, there's some mechanism more clever
Whatever it is, results in ping times being 1000ms then 10ms then 1000ms
then 10ms...when it responds.
i.e. it's a mistake to use FreeBSD 3.x with the 3c589d.
FWIW, I'm using the 3c589d with 3.2-STABLE + PAO, and it's working just
fine.
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
unfortunally no core dump, but I'm able to reproduce it (I just have to
enable softupdates).
---snip---
panic: softdep_disk_write_complete: lock is held
Debugger("panic")
Stopped at Debugger+0x36: mocb $0,in_Debugger.354
db trace
Debugger(x027c6a3) at Debugger+0x36
panic(c028a900,
If somebody _really_ want to ping forever, let them use -t0, and
defend the rest of us from our blunders of forgetting a ping, keeping
the line open infinitely.
I use ping for precisely this purpose. Yes, I could change my setup,
but so could you :-)
I used SunOS (and later Solaris)
Second, a domain name can at most a single CNAME record associated
with it, and other other record types. BIND will (should) barf on a
zone file containing the example you listed.
It does not. It will round-robin over the CNAME's.
See the documentation for the multiple-cnames option in
Just was presented the following panic by my FreeBSD/alpha Miata box that
was doing a make release:
initiate_write_inode_block() at initiate_write_inode_block() +0x40
softdep_disk_io_initiation() at softdep_disk_io_initiation() + 0xac
spec_strategy() at spec_strategy() +0x48
Ok ... we all know what exactly should be theoretical maximum and all ...
but that wasn't exactly my question ... I have having weird problems with
the network performance permanently dropping to below 100 kB/s (while still
in 100 Mbps/FDX). Is there anybody that could give a plausible
No, it is not. It is 100Mbps upstream and 100Mbps downstream. You cannot get
200Mbps in one direction. FDX (Full Duplex) simply means that the RX and TX
cables are used simultaneous. Due to the small ethernet frame size, it is
next to impossible to get the full speed for data transmission.
Are you sure ssh requires a host key? I could have sworn this was
entirely related to sshd and could thus be lumped into the same
"if sshd_enable=YES" clause.
The code does not lie :-)
From ssh.c:
/*
* If we successfully made the connection, load the host private
If you want to tinker with the file permissions, can't you deal with the
fact that the startup scripts will create a host key for you the first
time you boot with it installed?
As long as there is an easy way of running ssh without any special privs,
I'm happy.
Steinar Haug, Nethelp
j...@zippy- dmesg|grep Freeing
Freeing (NOT implemented) redirected ISA irq 11.
Freeing (NOT implemented) redirected ISA irq 10.
Nowhere near as annoying as tagged openings now xx.
Agreed. They are confusing to those who don't know what it means. As for
me, I just ignore them - ie. they
I really don't understand the problems that everyone is having,
myself. I've been running netscape (communicator 4.5) in -current for
ages now and just switched to 4.0 without any problems. My netscape
still continues to function just fine and has never crashed any of
my system so much as
I believe an upgrade to the eventlib is coming Real Soon Now.
I'm not sure about this - it might have been the logging module.
BIND 8.2 is currently in alpha testing, and has some changes in
eventlib compared to BIND 8.1.2. As far as I can see, there are minor
differences in
eventlib.c
In what sense do ye think VM_STACK is related to the Netscape issue? I'd
love to hear what ye think causes it to bomb...
I haven't really messed with it too much, so right now I think it's related
because testing makes it appear to be. i.e. if I have a kernel with VM_STACK
Netscape will
I agree.. and same thing goes for Ethernet drivers. I actually
like the way Linux always has eth0, eth1, ... (which we could
Yeagh... what is wrong with ed0, de0, fxp0 etc that needs changing? Is this
just a matter of taste or is there more to it? I for one don't see any
advantage in
To insert some reality into this discussion, a quick survey at the
office shows:
Platform Has DHCP
Irix 6.5 Yes
Solaris 2.5.1 No
... and Solaris 2.6 has DHCP.
HP/UX 10.20 Yes
Linux (RH 5.x)
Initially I though /etc/defaults/rc.conf stored the default settings and then
we could override some of the settings in /etc/rc.conf, but after a close
look at how they are used in /etc/rc*, I am confused:
if [ -f /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
Sorry it's been so long for me to get back to you about the patch you sent.
The machine is located accross country 3 time zones away, so coordinating
with the people at the console has been tedious.
In any case, the patch worked brilliantly. The machine is now running a 4.0
generic
Jeroen Ruigrok/Asmodai once stated:
= -rw-r--r--1 4294967294 wheel 389120 Feb 14 23:54 pdksh.core.xclink
=this is exactly what I got when I tried to compile some things over NFS.
=The created directory and files were also like this:
=
=1 drwxr-xr-x 3 4294967294 wheel - 512 Feb
Just some results of testing the comparison of wd and ata:
Both bonnie tests were run on a freshly booted machine, P133,
64M RAM, running X and netscape, but only Bonnie active:
---Sequential Output ---Sequential Input--
--Random--
-Per Char-
I don't remember who suggested it a couple of days ago, but I thought it
was a good idea: to simply extend the wiring-down scheme that we already
have to support ATA devices too. He also suggested a more universal device
name like drv0, drv1, drv2, etc rather than deliniating between whether
For quite some time now Netscape 4.5 has been very unstable on my
-current system. I've cvsup'ed and made world many times in the hope the
problem would go away.
Today I decided to ktrace it, and see where it would stop.
Of course it now refuses to crash. Even on java stuff that would
Uh, no. Invariants are for developers who want to make sure their code
is correct. There is no reason why an end user would want to build a
kernel with invariants enabled. Invariants will *not* increase data
safety. If they have any effect at all (i.e. if they actually catch a
bug), the
Boot from an ata disk on major# 30, device name ad, plain and simple.
Does this mean ata disks won't come under CAM/da ?
If not, can we PLEASE rename SCSI disks back to ``sd''?
Agreed. I see no justification for the sd - da change if the ATA disks
won't (eventually) be included.
Steinar
What do think about add new version of BIND to -current?
There have been some error reports against 8.2-REL, and I think we
should let it have a few more weeks to stabilize before it is brought
into -current.
(We're running 8.2 at some important name servers here, for instance
one which is
I have since corrected it so if you cvsup again and make world again
(actually just make install in src/share/mk), all will be well. As
a workaround, echo 19990328 /var/db/pkg/.mkversion will work
equally fine.
Now that make world do something in /var/db/pkg, shouldn't /var/db/pkg
be
... because usr.bin/colldef/data/de_DE.DIS_8859-15.src has been updated:
# $Id: de_DE.DIS_8859-15.src,v 1.3.2.1 1999/04/22 08:34:03 foxfair Exp $
without the corresponding update to scan.l and parse.y in the colldef
source. End result:
=== usr.bin/colldef/data
colldef -I
Finally learned enough about routing to understand this. Which router
program does OSPF? Gated?
Yes.
Since OSPF seems to have a lot of good features, and it's hardly new,
why isn't a router using OSPF installed with FreeBSD?
Probably because:
- OSPF *is* more complex, and you need to
I can't quite figure why they stuck the word open in there, because it
couldn't possibly be more open than RIP.
Probably because it was (at the time) in heavy competition with the OSI
IS-IS routing protocol. Those standards were *not* openly available. (I
believe they are now.)
Steinar Haug,
I consider ISIS dead these days, though I'm sure there are people who
still swear by it.
As far as I know, there is *active* development of IS-IS these days, see
for instance:
IS-IS Optimized Multipath (ISIS-OMP), Tony Li, Curtis Villamizar,
02/23/1999,
You didn't read what I said. I don't have a gigabit ethernet switch.
I only have cards. Therefore the *only* way I can test the operation
of the driver and adapters is to connect two machines with gigabit
cards back to back with a patch cable. This automatically implies 'using
gb
[1]: FreeBSD really needs to move away from the base system as a
concept, as I've ranted about in the past.
Strongly disagree.
Or if it cannot, the base
system needs to start using pkg_* (somehow) for use, and src.conf
WITHOUT_xxx (where xxx = some software) removed. Concept being: I
No, my intension is not to compare IPv4 and IPv6 here. We have never
enable L3 address autoconfiguration without explicit configuration
before. This is reasonable and should be kept for IPv6, too.
Agree 100%. Having IPv6 SLAAC as the default is a bad idea.
On the other hand, I *do* like
No, my intension is not to compare IPv4 and IPv6 here. We have never
enable L3 address autoconfiguration without explicit configuration
before. This is reasonable and should be kept for IPv6, too.
Agree 100%. Having IPv6 SLAAC as the default is a bad idea.
On the other hand, I
When you disable journaling it also disables soft-updates. You need to
re-enable it. I could decouple this. It's hard to say which is the POLA.
I would vote for decoupling. If I have SU on, then enable journaling,
then disable journaling, I would expect SU to still be on.
Fully agreed.
No. host(1) is a dns specific tool.
*sigh*. So how does one figure out what amd and sendmail are seeing as
they try to resovlve addresses?
tcpdump -ns 1500 -i INTERFACE udp port 53
Interface may be lo0 if you're running a name server on the same machine.
Steinar Haug, Nethelp
I have always hated the three lines in /etc/syslog.conf which spams
root with far too many and far too irrellevant syslog messages, in
some cases even with several copies of them.
Amen to that. You got my vote. Usually when I set up a FreeBSD box, it's
the first thing I turn off.
For the benefit of packet sniffers and other things that only want
read-only access to /dev/bpf*, what do people think of adding a 'bpf'
group for those programs? This allows bpf devices to be read by
programs running with an effective gid of 'bpf' instead of the current
requirement
maybe we should fix our SERVER apps..
e.g. telnetd, sshd, etc. to have 1 week timeouts
IIRC, it is not possible to specify how long the keepalive interval
should be, using the socket interface. Do you suggest we add a new
interface not present in other Unix implementations, or that we
:Huh? I was just considering writing the patch for this. What
:application problems would this create?
:
:The worst thing I can see is that it would mean that changing the
:timeout value on a running system wouldn't affect already opened
:sockets. Even that may be changable by an external
The poor sod in this situation deserves something untoward,
IMNSHO. Protocols like ssh do send something periodically whereas
telnet doesn't. Telnet is a well-known security problem. As others
have pointed out, this is an endemic problem in applications
generally speaking, where a long-term
I would vote for decoupling. If I have SU on, then enable journaling,
then disable journaling, I would expect SU to still be on.
Fully agreed. I see no reason why these sould be coupled.
It does not look like it is a prerequisite to have SU enabled when you
want to enable SUJ. So I
Personally, I think the whole base and ports thing is an artificial
divide that is rapidly losing utility. I think we're past due for
stripping the FreeBSD base down to a much more bare minimum, and
having a lot more of the bells and whistles live in the ports tree.
Strongly disagree. One
Seems 10.1 is on the pipeline now, but as far as I know none of these
fixes have been applied to -STABLE. Any chances to do it yet? As far as I
know, the oce driver is currently unusable in -STABLE. I managed to
cause a panic reliably within 30 seconds.
Was there any conclusion to
> > There is soft-fail, configure just marks that locales are not supported
> > and use "C". Sorry I don't remember port names where I saw it right now
> > and don't have a time to search for them right now too. Soft-fails (like
> > in tcl with nl_langinfo) are almost impossible to detect
> >> There's also a common
> >> problem that users view -15 documents with -1 accidently. So there was
> >> a conscience decision to have either ISO8859-1 or ISO8859-15 but not
> >> both. For western Europe this means the ISO8859-1 versions were dropped.
>
> It is pure user problem choosing its
Hijacking a thread here,
> Turns out, you can't install FreeBSD using a USB stick image because the
> BIOS only support MBR. No idea why MBR support was dropped for the USB images.
>
> In the end I had to find a CD burner, and after a couple of tries managed to
> install from CD.
On a somewhat
There is a 64-bit integer overflow computing user cpu time in calcru1()
in kern_resource.c. This was discovered because CPU statistics from
the PowerDNS-recursor name server stopped working (essentially, got
"stuck") after a while:
time_t milliseconds
1547818832 301274008.418503
>>> Any workarounds in the meantime? This must affect a lot of people,
>>> including those who use 12-:
>>>
>>> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
>>> pkg: repository FreeBSD contains packages with wrong ABI:
>>> FreeBSD:12.0:amd64
>>
>> Still broken for
>> I think a lot of people are waiting for some kind of guidance on how
>> to fix these problems, if the repos are supposed to be okay now.
>
> It would be really great if someone in the know would send something to
> -announce or similar, with an ETR. Maybe even with suggestions for
>
> On my FreeBSD 13.0-CURRENT amd64 r359631M system:
>
> $ sysctl -a | grep net.inet.tcp.cc
> [...]
> net.inet.tcp.cc.available: newreno
> net.inet.tcp.cc.algorithm: newreno
>
> So it's more recent than the patch, but it does not offer anything
> besides newreno ?
Quoting an email here:
You can
> FTP is (becoming?) a legacy protocol, and I think it may be time to
> remove the ftp server from the FreeBSD base system - with the recent
> security advisory for ftpd serving as a reminder.
>
> I've proposed adding a deprecation notice to the man page in
> https://reviews.freebsd.org/D26447 to
> PCIID? I’m not sure how to get that information. Will the bootup info help?
> Here’s a picture.
You want the output from "pciconf -lv". Example from a system here:
igb0@pci0:2:0:0:class=0x02 card=0x3380103c chip=0x15218086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
>> I have to report to my superiors (we're using 14-STABLE and CURRENT
>> and I do so in private),
>> so I would like to welcome any comment on that.
>
> No it does not affect FreeBSD.
>
> The autoconf script checks that it is running in a RedHat or Debian
> package build environment before
91 matches
Mail list logo
