ifconfig VLAN cloning, renaming, configuring in rc.conf.local
[Please CC: me on any replies, as I check my inbox more frequently
than I check this list.]
I have three servers running 9.3-STABLE which are designed to be
able to exchange jails so that a virtual host can be readily moved
to a different physical host. Because physical NIC names could
differ, the ezjail config files are set up to use an interface name
of 'public' or 'private' depending on which of the two physical NICs
each jail wants to use, and the rc.conf system is responsible to
configure the physical NICs with the correct 'public' and 'private'
NICknames (pardon the expression).
The hitch is that one of the three machines is on a trunked switch
port, so that it can access multiple (two) VLANs through a single
physical NIC.
This works fine once I manually configure it, but I can't find a way
to adapt my rc.conf.local model to handle the VLAN setup
automatically at boot time. I want to end up with a 'public'
interface on vlan 1 of the main physical NIC (and multiple IPs
configured), a 'vlan100' interface on vlan 100 of the main physical
NIC (with IPs configured), and a 'private' interface on the
secondary physical NIC (with IPs configured).
I use an identical rc.conf on the servers, and keep the nitty gritty
details in rc.conf.local, as follows:
rc.conf:
# most machine-specific stuff is in rc.conf.local
#
# these settings are common to all
#
moused_enable="YES"
gateway_enable="YES"
inetd_enable="YES"
sshd_enable="YES"
sshd_flags='-o "PermitRootLogin=without-password" -o "ListenAddress=$IP:22"'
zfs_enable="YES"
ezjail_enable="YES"
##eof##
Here is the problematic rc.conf.local:
hostname="trunked-server.example.com"
# vlan trunking on interface bce0:
# physical interface bce0 just needs to be up
ifconfig_bce0="up"
# We will clone two vlan interfaces:
cloned_interfaces="vlan1 vlan100"
# The details for those two cloned interfaces:
ifconfig_vlan1="vlan 1 vlandev bce0"
ifconfig_vlan100="vlan 100 vlandev bce0"
# Some interfaces get renamed, so that jails can find
# the "public" and "private" interfaces:
ifconfig_vlan1_name="public"
ifconfig_bce1_name="private"
# primary public IP:
IP="10.158.10.18"
MASK="/25"
defaultrouter="10.158.10.1"
# public interface IPs:
ipv4_addrs_public="
${IP}${MASK}
10.158.10.10/32
10.158.10.31-47/32
"
ipv4_addrs_vlan100="
10.158.2.5/27
"
# private interface IPs:
#ipv4_addrs_private="10.0.0.7/24"
firewall_enable="YES"# Set to YES to enable firewall functionality
firewall_script="/root/fw.sh"
# jail settings:
jail_set_hostname_allow="NO"
# jail_jail1_parameters="allow.raw_sockets=1 allow.sysvipc=1"
jail_parameters="
allow.raw_sockets=1
allow.mount.devfs=1
allow.set_hostname=0
"
##eof##
Some things I have found:
As given above, the vlan interfaces don't get set up the way I want
them. public gets created and has all the IPs, but is on vlan 0
with no parent device:
bce0: flags=8843 metric 0 mtu 1500
options=c01bb
ether 00:1f:29:e1:22:f6
inet6 fe80::21f:29ff:fee1:22f6%bce0 prefixlen 64 scopeid 0x1
nd6 options=29
media: Ethernet autoselect (100baseTX )
status: active
private: flags=8802 metric 0 mtu 1500
options=c01bb
ether 00:1f:29:e1:22:f4
nd6 options=29
media: Ethernet autoselect
lo0: flags=8049 metric 0 mtu 16384
options=63
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x9
inet 127.0.0.1 netmask 0xff00
nd6 options=21
public: flags=8003 metric 0 mtu 1500
ether 00:00:00:00:00:00
inet 10.158.10.18 netmask 0xff80 broadcast 10.158.10.127
inet 10.158.10.10 netmask 0x broadcast 10.158.10.10
inet 10.158.10.31 netmask 0x broadcast 10.158.10.31
inet 10.158.10.32 netmask 0x broadcast 10.158.10.32
inet 10.158.10.33 netmask 0x broadcast 10.158.10.33
inet 10.158.10.34 netmask 0x broadcast 10.158.10.34
inet 10.158.10.35 netmask 0x broadcast 10.158.10.35
inet 10.158.10.36 netmask 0x broadcast 10.158.10.36
inet 10.158.10.37 netmask 0x broadcast 10.158.10.37
inet 10.158.10.38 netmask 0x broadcast 10.158.10.38
inet 10.158.10.39 netmask 0x broadcast 10.158.10.39
inet 10.158.10.40 netmask 0x broadcast 10.158.10.40
inet 10.158.10.41 netmask 0x broadcast 10.158.10.41
inet 10.158.10.42 netmask 0x broadcast 10.158.10.42
inet 10.158.10.43 netmask 0x broadcast 10.158.10.43
inet 10.158.10.44 netmask 0x broadcast 10.158.10.44
inet 10.158.10.45 netmask 0x broadcast 10.158.10.45
inet 10.158.10.46 netmask 0x broadcast 10.158.10.46
inet 10.158.10.47 netmask 0x broadcast 10.158.10.47
nd6 options=29
vlan: 0 parent interface:
vlan100: flags=8843 metric 0 mt
Re: impossible rc.d ordering problem with stf and pf ?
On Wed, Jan 31, 2007 at 09:30:56AM +0200, Stefan Lambrev wrote: > Hello, > > >>pass out on (stf0) inet6 from any to any keep state > >> > > > >Just for my edification, what is the point of "keep state" on an > >"any-to-any" rule? > > > > > imagine that you have only 2 rules - > block in on $if all > pass out on $if from any to any keep state > > - with "keep state" you have internet, without it you do not have ;) Thank you. I must read more closely. I did not grok the "out." Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: impossible rc.d ordering problem with stf and pf ?
> Date: Mon, 29 Jan 2007 12:02:52 + > From: Pete French <[EMAIL PROTECTED]> > Subject: Re: impossible rc.d ordering problem with stf and pf ? > To: freebsd-stable@freebsd.org, [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > > > 1) You use the interface name as address w/o dynamic lookup. > > i.e. "... from stf0 ..." > > Yes, thats it - I hadn't come across this 'dynamic lookup' thing before > though, so I didn't realise what it was. I still cant find it in the PF > manual, aside from a reference that you need to do it for NAT. > > > To 1 and 2 there is a simple sollution: Don't do that then! 1 can easily=20 > > be defused by adding parentheses. i.e. "... from (stf0) ...". > > pass out on (stf0) inet6 from any to any keep state Just for my edification, what is the point of "keep state" on an "any-to-any" rule? Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Failover-HA-Setup
> Date: Wed, 17 Jan 2007 13:47:37 +0100 > From: Richard <[EMAIL PROTECTED]> > Subject: Failover-HA-Setup > To: freebsd-stable@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain > > Hi there! > > I am looking for a solution for a small problem regarding a high > availability setup. > I am running heartbeat on a STABLE-system, the failover works fine for > IP-adresses and I am able to see that a > '/usr/local/etc/rc.d/mysql-server start' statement is issued. BUT since > the variables for mysql are not set in rc.conf (Otherwise it would be > started at startup), it isn't starting at all. > > So my question: How to set those rc.conf-variables in order to start > services in such an setup? Or is there a better solution? > > > cu! > > Richard export mysql_enable="YES" && /usr/local/etc/rc.d/mysql-server start ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: loader freezes system during timer autoboot
> Date: Sun, 17 Dec 2006 13:44:05 +0100 (CET) > From: patrick <[EMAIL PROTECTED]> > Subject: loader freezes system during timer autoboot > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > > Hi, > > I have a supermicro system which freezes during the timer before autoboot. > It freezes most of the times. > > System : Supermicro 5014C-T > : Super P8SCi > : P4 630 / 3.0 GHz / 2MB cache - 2 Logical CPUs > : 2048 (2x1GB) PC2-400 ECC REGISTERED > : Broadcom BCM5721 Dual Gigabit Ethernet > : 3ware 3W8006-2LP Storage Controller > > 6.2-RC2, cvsup'd 17 dec 1200 CEST running GENERIC kernel > > setting autoboot_delay="-1" and beastie_disable="YES" in loader.conf make the > system most of > the time boot correctly, but sometimes also freezes but then directly after > start of the autoboot/kernel boot. > > I have an identical system running 6.1 without this problem. > > Anyone have any suggestions? My suggestion would be to try some elementary troubleshooting. Swap the disk arrays between the two machines, for instance. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CPUTYPE=athlon-xp and loader
> Date: Sun, 16 Apr 2006 17:43:58 +0300 > From: Evren Yurtesen <[EMAIL PROTECTED]> > Subject: CPUTYPE=athlon-xp and loader > To: freebsd-stable@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > > Hello, > > I have a problem which I have found out from mailing lists that some > other people had. However there is no clear solution. > > The CPUTYPE=athlon-xp in make.conf breaks /boot/loader that system > instant reboots. I am using 6-stable and from what I can see the problem > goes back till about 5.3... Sometime between Oct 12-15, 2005 > > http://archive.netbsd.se/?ml=freebsd-current&a=2004-10&m=435817 > > I wonder if this will ever be fixed or I shouldnt use CPUTYPE=athlon-xp > anymore on FreeBSD because of this? > > Thanks, > Evren I don't propose this as a solution, but as far as I know, the best practice is: CPUTYPE?=athlon-xp Note the question mark. I don't know that this will solve your problem, just pointing out the correct syntax, for whatever CPUTYPE you decide to use. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New ports on older stable (4.11)
> Date: Wed, 01 Mar 2006 11:05:13 + > From: Pete French <[EMAIL PROTECTED]> > Subject: New ports on older stable (4.11) > To: freebsd-stable@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > > I dont know how backward compatible ports are ggenerally, but I > have a 4.11 machine that I really want to upgrade the ports on. > But I dont know if they will alla ctually compile, and I dont wnat to > start doing the process only to find that I cant build one of them > possibly. Does anybody know if this is likely to work, or is it > simply unsupported ? > > I;d love to upgrade the machine to 6.1 - but I have no physical access to > it, nor am I likely to get any for the forseeable future, and upgrading > across the 4/5 boundary isn't something I would be happy doing remotiley > in multi-user mode (if it's even possible!) > > -pcf. This is rather a case of the extremely near-sighted leading the blind, but I recently inherited the care of some older boxen, and in fact, recently deployed a new 4.11 installation, and proceeded to build up-to-date ports on it. I still share a part of your trepidation about getting oneself into a bind with uncooperative dependencies, etc. However, I have had more success than I would have imagined. Here are some suggestions, and I certainly welcome corrections to my advice from more expert sources. Start by backing up your /usr/ports and your /var/db/pkg and /var/db/ports and anything else you can think of. Heck, back up the whole samn dystem if you can. To paraphrase Douglas Adams, the universe is a lot safer if you have a backup. I should think portaudit would be the first thing you'd want to install, so that you can find out if other ports have security problems. Go slow, read Makefiles first, that sort of thing. You can probably install portupgrade without too much trouble, as it doesn't have a lot of dependencies. Then a lot of use of portupgrade -nR (portname) will tell you which ports have the fewest dependencies, and -nr (portname) will tell you which ports depend on any given port you may be thinking about upgrading. Just for prurient interest, would you care to post your pkg_info? If you have portupgrade installed, or can install it, how about the output from "portupgrade -na" also. Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Trouble with mounting USB stick as user
> Date: Wed, 8 Feb 2006 06:46:37 -0600 > From: Michael Ekstrand <[EMAIL PROTECTED]> > Subject: Re: Trouble with mounting USB stick as user > To: freebsd-stable@freebsd.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII > > On Wed, 8 Feb 2006 22:40:04 +1100 > Rob <[EMAIL PROTECTED]> wrote: > > Can anyone shed some light on what is happening here? > > AFAIK, only root can mount things under FreeBSD, period. I could be > wrong on this... but I looked around a while ago for something to do > the job of the Linux 'user' option, and found nothing. I kinda remember > trying changing permissions too. > > If I'm wrong, I'd love to be corrected :-). > > - Michael # portupgrade -N security/sudo # man sudo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nVidia RAID + FreeBSD 6.0
> Date: Sun, 29 Jan 2006 15:08:21 + (GMT) > From: Gavin Atkinson <[EMAIL PROTECTED]> > Subject: Re: nVidia RAID + FreeBSD 6.0 > To: Christian Brueffer <[EMAIL PROTECTED]> > Cc: freebsd-stable@freebsd.org, [EMAIL PROTECTED] > > On Sun, 29 Jan 2006, Christian Brueffer wrote: > > On Sun, Jan 29, 2006 at 04:46:52PM +1030, Daniel O'Connor wrote: > >> I am looking at getting a motherboard based on nForce 3 or 4, and I am > >> wondering if the RAID will be usable? > > > > Be aware though that there have been reports on the lists of data loss > > in connection with NVIDIA RAIDs. This seems to also happen on other > > operating systems. > > In my experience, they seem to be reliable while both disks work, but when > a disk needs to be rebuilt the RAID BIOS seem to pick the source disk at > random, as opposed to something radical like using the only valid disk as > the source. Gee, no RAID at all is reliable when both disks work! A RAID solution that has problems when one disk fails is pretty darn worthless as a RAID solution. ... > Indeed, on the hardware I was using (a Sun X2100 server), Solaris had the > same problem, and about 50% of the time you'd end up with corrupted or > blank disks after a rebuild. Sun have now stopped claiming in the > specifications that these machines support RAID ... "Doctor Sun, it hurts when I do this." "Well, don't do that." Not the best response one might hope for. Regards, Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to get custom release CD to boot without floppies?
I am trying to create bootable installation media for 6.0-RELEASE. This is my first attempt at doing this, so I am learning a lot and fumbling even more as I go. First, I wish to thank Masafumi Watari for his helpful step-by-step procedure, based on RELENG_4, found at http://www.sfc.wide.ad.jp/~watari/FreeBSD/boot.html. It has gotten me much farther than any other resource that I've found on the web. Actually, I think I'm building a snapshot release of 6-STABLE, since I started by cvsup-ing: cvsup -g cvs-supfile with this cvs-supfile: --- snip *default host=cvsup4.FreeBSD.org *default base=/var/db *default prefix=/home/ncvs *default release=cvs *default delete use-rel-suffix *default compress src-all cvsroot-all --- snip I am intentionally omitting ports and docs because I believe I do not require them for my purposes. I then went into /usr/src and did 'make -j4 buildworld' which ran without errors. The 'make release' was done thus: export NODOC=1 export NOPORTS=1 cd /usr/src/release make release CHROOTDIR=/usr/tmp/CHROOTDIR BUILDNAME=6.0-REL-TEST CVSROOT=/usr/home/ncvs RELEASETAG=RELENG_6 Watari's document talks about customizing install.cfg, but in my limited understanding, this file automates installation tasks. I don't think I need this. I will be happy to just have a custom release which boots into a standard sysinstall. Watari also discusses modifying sysinstall itself, again, beyond the scope of my needs. So I proceeded directly to burning the CD-R. I don't have a burner on the build machine, nor do I have mkisofs installed. So I tarred up the release CHROOTDIR: cd /usr/tmp tar cf CHROOTDIR.tar CHROOTDIR and un-tarred on my burner-equipped machine: cd /work/ tar xpf ~/CHROOTDIR.tar Finally, I made an ISO image: cd CHROOTDIR export CHROOTDIR="." mkisofs -d -D -N -R -T -V "FreeBSD6.0-RELEASE" \ -P "Test Distribution" \ -o ~/tinn.iso -b floppies/boot.flp \ -c floppies/boot.catalog $CHROOTDIR/R/cdrom/disc1 # /* -V is your CD name */ # /* -P is for some comments */ # /* -o is your image name */ # /* -b and -c should be left how it is. It's set for auto boot. These paths should not be a full path */ I then took an md5 of the iso file, burned it to disc, and got a disc with the same md5 value. The disc does boot, but asks for kernel floppies: Insert disk labelled "Kernel floppy 1" and press any key... I want to make a CD which doesn't require floppies to boot. In diff'ing the CD against a genuine 6.0-RELEASE I find that the boot.catalog didn't make it on the disc (apparently because there just plain isn't one anywhere in the CHROOTDIR tree I built), but I can't find anything by Googling that definitively points to that being the problem. I have compared some files between my release and 6.0-RELEASE (/boot/*boot*, /boot/defaults/loader.conf, /boot/loader.rc, etc.), and in general, binaries are the same size, and text files have trivial differences. But perhaps I have overlooked some key files somewhere. The mkisofs option "-b floppies/boot.flp" makes me squint a lot, but my searches haven't led me to a file which seems a more likely El Torito boot image. So I'm going to go rustle up some floppies -- I don't think I have any around -- and see if my release at least does boot via the floppy method. That will be valuable knowledge to have before attempting a second "release candidate." I should make diskettes from the images $CHROOTDIR/R/cdrom/disc1/floppies/kern1.flp and kern2.flp, yes? In the meantime, can anyone shed light on why my CD asks for floppies in the first place? If it is the lack of the boot.catalog file, can I simply copy the boot.catalog from the official 6.0-RELEASE disc, and place it in $CHROOTDIR/floppies/ as per where mkisofs was told to find it? If it is the wrong choice of boot image with the "-b" switch, which file should I use instead? In case it helps, $(ls -lR) of $CHROOTDIR is at: ftp://www.umpquanet.com/pub/make-rel-chrootdir-ls-lR.txt $(ls -lR) of burned CD is at: ftp://www.umpquanet.com/pub/make-rel-cd-ls-lR.txt Thank you very much! Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: rpcbind lingering on IP no longer specified on command line
On Fri, Jan 06, 2006 at 10:22:43AM -0500, Vivek Khera wrote: > > On Jan 6, 2006, at 4:40 AM, James Long wrote: > > >>Yeah, I noticed that little tiny "UDP requests" note in the -h docs > >>too. There's no reason to bind to all tcp addresses, and it is > >>causing me heartburn for getting the server certified... > > > >Good grief, why not just firewall off the undesired UDP ports and call > >it good? > > I guess we could take that band-aid approach... however, how do you > know what port RPC decides to listen on other than the 111 port? It > is more or less random. That makes it very difficult to firewall. P-shaw. If you're enduring "heartburn for getting the server certified" then firewall off the rpcbind service from unwanted IPs and voila, you get your get your server certified and business goes on. Then you'll have the luxury of time to debug the true problem with rpcbind, and your testing is done behind the privacy of your firewall. As far as unpredictable listening ports opened by rpc, that is exactly why a secure firewall opens only selected ports on selected IPs, and blocks everything else. It doesn't matter if it listens on port X of IP y when your firewall doesn't permit incoming connections on that port and IP in the first place. Jim ># sockstat | grep rpcbind >root rpcbind11382 5 stream /var/run/rpcbind.sock >root rpcbind11382 6 dgram -> /var/run/logpriv >root rpcbind11382 7 udp4 127.0.0.1:111 *:* >root rpcbind11382 8 udp4 192.168.100.200:111 *:* >root rpcbind11382 9 udp4 *:664 *:* >root rpcbind11382 10 tcp4 *:111 *:* ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: rpcbind lingering on IP no longer specified on command line
> Date: Thu, 5 Jan 2006 10:31:33 -0500 > From: Vivek Khera <[EMAIL PROTECTED]> > Subject: Re: rpcbind lingering on IP no longer specified on command > line > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > > On Jan 5, 2006, at 6:06 AM, Gavin Atkinson wrote: > > >> Can anyone explain why rpcbind will still bind to all tcp interfaces? > > > > Although I believe this is a bug, it is actually working as > > documented: > > > > from rpcbind(8): > > -h bindip > > Specify specific IP addresses to bind to for UDP > > requests. > > Yeah, I noticed that little tiny "UDP requests" note in the -h docs > too. There's no reason to bind to all tcp addresses, and it is > causing me heartburn for getting the server certified... Good grief, why not just firewall off the undesired UDP ports and call it good? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Reboots under 6.0 while exercising md device
For some reason, this script:
#!/bin/sh
DEV=$(md_config -a -t malloc -s 500m)
newfs -i 512 -U /dev/$DEV
mount /dev/$DEV /mnt
cp -Rp /usr/src /mnt/
will kill my machine. I get zillions (well, hundreds at
least, without a serial console I can't count them)
of:
Dec 21 19:16:27 test kernel: g_vfs_done():md0[WRITE(offset=352649216,
length=16384)]error = 28
Dec 21 19:16:27 test kernel: g_vfs_done():md0[WRITE(offset=352665600,
length=12288)]error = 28
with varying offsets and lengths, but seemingly always error 28
The system does not panic orderly, but rather spontaneously reboots after
spewing a lot of the above error messages (5-20 secs worth).
This is on a Compaq Proliant ML370 with 1 GB RAM, dmesg below.
What do I need to fix to be able to use a RAM-backed filesystem?
Jim
FWIW, this script does not seem to freak out my machine, This led
me to consider inode starvation, but '-i 512' results in over 6
inodes for what I estimate to be < 4 files in /usr/src.
#!/bin/sh
DEV=$(mdconfig -a -t malloc -s 500m)
newfs -i 512 -U /dev/$DEV
mount /dev/$DEV /mnt
dd if=/dev/zero of=/mnt/1M bs=1024 count=1024
for j in $(jot 450); do {
cp -p /mnt/1M /mnt/1M.$(printf "%03d" $j)
} done
After that, df -h /mnt shows:
/dev/md0 484M458M-13M 103%/mnt
Here's the dmesg:
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 6.0-RELEASE #0: Wed Dec 21 15:40:38 PST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel Pentium III (996.85-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x686 Stepping = 6
Features=0x383fbff
real memory = 1073725440 (1023 MB)
avail memory = 1041682432 (993 MB)
MPTable:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 1
cpu1 (AP): APIC ID: 0
ioapic0: Changing APIC ID to 8
ioapic0: Assuming intbase of 0
ioapic0 irqs 0-34 on motherboard
npx0: [FAST]
npx0: on motherboard
npx0: INT 16 interface
cpu0 on motherboard
cpu1 on motherboard
pcib0: pcibus 0 on motherboard
pci0: on pcib0
sym0: <1510d> port 0x2000-0x20ff mem
0xc6effc00-0xc6ef,0xc6efe000-0xc6efefff irq 11 at device 1.0 on pci0
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: [GIANT-LOCKED]
sym1: <1510d> port 0x2400-0x24ff mem
0xc6efdc00-0xc6efdfff,0xc6efc000-0xc6efcfff irq 15 at device 1.1 on pci0
sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym1: [GIANT-LOCKED]
fxp0: port 0x2800-0x283f mem
0xc6efb000-0xc6efbfff,0xc6d0-0xc6df irq 5 at device 2.0 on pci0
miibus0: on fxp0
inphy0: on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:02:a5:64:d5:4e
pci0: at device 3.0 (no driver attached)
pci0: at device 4.0 (no driver attached)
isab0: at device 15.0 on pci0
isa0: on isab0
atapci0: port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x3000-0x300f at device 15.1 on pci0
ata0: on atapci0
ata1: on atapci0
pcib3: pcibus 3 on motherboard
pci3: on pcib3
ida0: port 0x4000-0x40ff mem
0xc6fff000-0xc6ff irq 10 at device 6.0 on pci3
ida0: [GIANT-LOCKED]
ida0: drives=1 firm_rev=1.18
idad0: on ida0
idad0: 17363MB (35561280 sectors), blocksize=512
eisa0: on motherboard
mainboard0: on eisa0 slot 0
eisa0: unknown card @@D9004 (0x00049004) at slot 2
pmtimer0 on isa0
orm0: at iomem
0xc-0xc7fff,0xc8000-0xcbfff,0xe8000-0xedfff,0xee000-0xe on isa0
atkbdc0: at port 0x60,0x64 on isa0
atkbd0: irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: on ppc0
plip0: on ppbus0
lpt0: on ppbus0
lpt0: Interrupt-driven port
ppi0: on ppbus0
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 1.000 msec
acd0: CDROM at ata0-master PIO4
Waiting 5 seconds for SCSI devices to settle
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/idad0s1a
WARNING: / was not properly dismounted
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /var was not properly dismounted
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: puzzling "ipfw show" output
> Date: Mon, 12 Dec 2005 09:39:44 +0100 (CET) > From: Trond Endrest?l <[EMAIL PROTECTED]> > Subject: Re: puzzling "ipfw show" output > To: FreeBSD stable > Message-ID: <[EMAIL PROTECTED]> > Content-Type: TEXT/PLAIN; charset=ISO-8859-1 > > On Mon, 12 Dec 2005 19:09+1100, Graham Menhennitt wrote: > > One last question: > > Why do you need rule 65530 when the built-in rule 65535 does the same > job? Having rule 65530 there allows the ruleset to function consistently on systems configured to accept by default or deny by default. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
On Tue, Nov 15, 2005 at 07:56:33PM -0800, David Wolfskill wrote:
> On Tue, Nov 15, 2005 at 07:49:10PM -0800, James Long wrote:
> >
> > ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found
> >
> > and investigated the Makefile to find why the odd package
> > name of "xterm>0".
>
> Looks as if the thing to do would have been to run "pkgdb -F" and delete
> that dependency.
Again, at that time, xorg-clients was not installed, thus
that dependency was not in the package database. Notice
that the portupgrade output with that "xterm>0" line is
a "portupgrade -N" invocation, to install a new port, not
to upgrade an existing port. I always welcome and try to
learn from corrections, but I can't see that pkgdb -F would
be able to remove a dependency for a port that is not (yet)
installed.
That dependency is actually verbatim in the Makefile, I quote:
RUN_DEPENDS=xterm>0:${PORTSDIR}/x11/xterm
Hence my patch. Or if the above syntax is correct, perhaps
someone can point me towards an explanation of the syntax found
in that RUN_DEPENDS= line for my edification. Once I removed
the ">0" from the Makefile, and since portupgrade had already
built (but failed to install) xorg-clients, I was able to
simply "make install" in the xorg-clients ports directory,
and all the previously-built stuff got installed, along
with xterm-206_1.
I'm just asking someone (my original post cc'ed $MAINTAINER)
to review the accuracy of that RUN_DEPENDS line. portupgrade
certainly seems to parse the ">0" as part of the port name,
rather than as some sort of conditional operator.
Regards,
Jim
>
> Peace,
> david
> --
> David H. Wolfskill[EMAIL PROTECTED]
> Prediction is difficult, especially if it involves the future. -- Niels Bohr
>
> See http://www.catwhisker.org/~david/publickey.gpg for public key.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
On Tue, Nov 15, 2005 at 07:32:45PM -0800, David Wolfskill wrote: > On Tue, Nov 15, 2005 at 07:26:16PM -0800, James Long wrote: > > After hours of head-banging over the past couple of days, > > I have finally succeeded in installing EITHER > > xorg-clients-6.8.2_1 OR xterm-206_1. Previously, > > installing either port told me that it conflicted > > with the other, in spite of having cvsupped my > > ports tree twice to ensure I was getting the most > > recent version of the ports, hopefully including a > > fix to the chicken-and-egg problem noted in > > /usr/ports/UPDATING > > It mentioned a conflict; I don't recall a chicken-and-egg issue. Forgive me for not including enough background. Due to an improper procedure on my part in converting from XFree86 to Xorg, plus a complete rebuild of all ports as part of upgrading to 6.0-STABLE, and a bit of ignorance on my part, I wound up in a situation where I had pkg_deleted both xorg-clients and xterm. I was then in a situation where I couldn't install xorg-clients because it depended on xterm, but xterm couldn't be installed because it con- flicted with xorg-clients. That was my chicken-and-egg dilemma. pkgdb -F was dutifully showing several packages with dangling dependencies to those two, but I couldn't install either of them. cvsupping to the most recent ports tree didn't change the problem. Then I noticed: ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found and investigated the Makefile to find why the odd package name of "xterm>0". I then patched the Makefile as I posted, and I was able to "make install" in xorg-clients and pkgdb -F and everything installed. Further documentation of the state of my pkg_info and dependencies is below. Jim [pkg_info | egrep "xorg|xterm" # note lack of xorg-clients and xterm] t21 : 19:04:41 /root# pkg_info | egrep "xorg|xterm" xorg-6.8.2 X.Org distribution metaport xorg-documents-6.8.2 Documentation of X11 protocol and libraries from X.Org xorg-fonts-100dpi-6.8.2 X.Org 100dpi bitmap fonts xorg-fonts-75dpi-6.8.2 X.Org 75dpi bitmap fonts xorg-fonts-cyrillic-6.8.2 X.Org Cyrillic bitmap fonts xorg-fonts-encodings-6.8.2 X.Org font encoding files xorg-fonts-miscbitmaps-6.8.2 X.Org miscellaneous bitmap fonts xorg-fonts-truetype-6.8.2 X.Org TrueType fonts xorg-fonts-type1-6.8.2 X.Org Type1 fonts xorg-fontserver-6.8.2 X font server from X.Org xorg-libraries-6.8.2 X11 libraries and headers from X.Org xorg-manpages-6.8.2 X.Org library manual pages xorg-nestserver-6.8.2 Nesting X server from X.Org xorg-printserver-6.8.2_2 X Print server from X.Org xorg-server-6.8.2_6 X.Org X server and related programs xorg-vfbserver-6.8.2 X virtual framebuffer server from X.Org [Initial state of ports dependencies:] [EMAIL PROTECTED] pkgdb -F ---> Checking the package registry database Stale dependency: kde-3.4.2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): xorg-vfbserver-6.8.2 (score:27%) ? ([y]es/[n]o/[a]ll) [no] New dependency? (? to help): Skip this? ([y]es/[n]o/[a]ll) [yes] Skipped. Stale dependency: kde-3.4.2 -> xterm-205_1 (x11/xterm): New dependency? (? to help): Skip this? ([y]es/[n]o/[a]ll) [yes] Skipped. Stale dependency: kdeadmin-3.4.2 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdeadmin-3.4.2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdebase-3.4.2_2 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdebase-3.4.2_2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdegames-3.4.2_1 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdegames-3.4.2_1 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdelibs-3.4.2_1 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdelibs-3.4.2_1 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-3.4.2_1 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-3.4.2_1 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-akode-3.4.2 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-akode-3.4.2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-mpeglib_artsplug-3.4.2 -> xterm-205_1 (x11/xterm): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdemultimedia-mpeglib_artsplug-3.4.2 -> xorg-clients-6.8.2_1 (x11/xorg-clients): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdetoys-3.4.2 -> xterm-205_1 (x11/xterm): Skip th
xorg-clients conflicts with xterm (patch)
After hours of head-banging over the past couple of days,
I have finally succeeded in installing EITHER
xorg-clients-6.8.2_1 OR xterm-206_1. Previously,
installing either port told me that it conflicted
with the other, in spite of having cvsupped my
ports tree twice to ensure I was getting the most
recent version of the ports, hopefully including a
fix to the chicken-and-egg problem noted in
/usr/ports/UPDATING
Once I spotted an odd bit of output in the portupgrade
dialogue, I made a change to xorg-clients Makefile
which allowed everything to install. pkgdb -F afterwards
and all my dependencies are tidied up.
May I suggest the following patch to
/usr/ports/x11/xorg-clients/Makefile:
--- MakefileSun Nov 13 21:47:34 2005
+++ foo Tue Nov 15 19:19:37 2005
@@ -18,7 +18,7 @@
MAINTAINER=[EMAIL PROTECTED]
COMMENT= X client programs and related files from X.Org
-RUN_DEPENDS= xterm>0:${PORTSDIR}/x11/xterm
+RUN_DEPENDS= xterm:${PORTSDIR}/x11/xterm
LIB_DEPENDS= png.5:${PORTSDIR}/graphics/png \
Xft.2:${PORTSDIR}/x11-fonts/libXft
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
> On Fri, 28 Oct 2005 10:05, James Long wrote: > > > Date: Thu, 27 Oct 2005 13:05:23 +0930 > > > From: "Daniel O'Connor" <[EMAIL PROTECTED]> > > > Subject: Re: RFC: proposed patch for > > > /usr/src/usr.sbin/wicontrol/wicontrol.c > > > > > > > The command I use most is wicontrol -L > > > > > > Try ifconfig ath0 list scan > > > > # ifconfig ath0 list scan > > ifconfig: list: bad value > > # > > Er weird.. > Is this in 6.0 or 5.x? FreeBSD t21.museum.rain.com 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon Oct 24 12:49:5 5 PDT 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/T21 i386 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
> Date: Thu, 27 Oct 2005 13:05:23 +0930 > From: "Daniel O'Connor" <[EMAIL PROTECTED]> > Subject: Re: RFC: proposed patch for > /usr/src/usr.sbin/wicontrol/wicontrol.c > > > The command I use most is wicontrol -L > > Try ifconfig ath0 list scan # ifconfig ath0 list scan ifconfig: list: bad value # ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
> wicontrol is obsolete and you should not need to use it, particularly > for ath(4) devices. Why are you using it? Is some feature you need > missing from ifconfig? The command I use most is wicontrol -L ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RFC: proposed patch for /usr/src/usr.sbin/wicontrol/wicontrol.c
wicontrol.c defaults to the "wi" interface. I used to have a
wi device, but it eventually took a dump and I bought a new
ath-based card, which works flawlessly AFAIK, after four months
or so.
But I grow weary of having to specify "-i ath0" every time I
run wicontrol.
Please review the following patch to /usr/src/usr.sbin/wicontrol/wicontrol.c
which modifies wicontrol to look for an environment variable
WI_IFACE and if set, take the interface name from that variable.
If unset, the interface name defaults to "wi0" just as before,
which hopefully will make this POLA compliant. Googling for
"WI_IFACE" I find no indications that this variable name already
is in use for anything else.
Apologies in advance for the simple diff output patch.
Jim
t21 : 15:13:58 /usr/src/usr.sbin/wicontrol# diff wicontrol.c.orig wicontrol.c
1092c1092,1094
< iface = "wi0";
---
> if ((iface = getenv("WI_IFACE")) == NULL) {
> iface = "wi0";
> }
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bzegrep behaviour not consistent with egrep?
> > > Should these two commands produce identical output? > > > > > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l > > >0 > > > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l > > > 121 > > Can you try the patch for src/gnu/usr.bin/grep/grep.c? The patch appears to fix my problem. Thank you! Jim ns : 15:00:10 /usr/src/gnu/usr.bin/grep# bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l 121 ns : 15:01:23 /usr/src/gnu/usr.bin/grep# bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l 121 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bzegrep behaviour not consistent with egrep?
Should these two commands produce identical output? $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l 0 $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l 121 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question about Sec. Adv. FreeBSD-SA-03:11.sendmail
On Tue, Aug 26, 2003 at 10:03:25AM -0700, James Long wrote: > > So I'm conffused as to why sendmail would need to be patched > on 8/25 when 8.12.9 has been in the base distribution since > April. D'oh! "4-STABLE prior to Mar 29 19:33:18 2003 UTC" > Thanks for shedding some light, Don't mention it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Question about Sec. Adv. FreeBSD-SA-03:11.sendmail
The advisory states that the problem was fixed on 8/25 approx. 22:35. The security also states that the problem afflicts sendmail 8.12.0 through 8.12.8. However, I have a system which had its world built on April 9, 2003, and it is running sendmail 8.12.9, according to the 220 banner it gives when I telnet into port 25. So I'm conffused as to why sendmail would need to be patched on 8/25 when 8.12.9 has been in the base distribution since April. Thanks for shedding some light, Jim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sudden and unexplained reboots
On Thu, Jun 05, 2003 at 06:37:55AM +0200, Noor Dawod wrote: > > The panic's details are as follows: > > Fatal trap 12 = page fault while in kernel mode I'd test memory thoroughly next. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Zoltrix modem
On Sun, Jan 26, 2003 at 08:58:32AM +0100, Zoran Kolic wrote: >Dear FreeBSD! >Hope that someone on the list has > expirience with external Zoltrix modem > named Rainbow. It should change my > nightmare: lucent winmodem. Maker > has a lot of data about windows com- > pability, but freeBSD is not even men- > tioned. Should I buy it? (Modem on the > machine? Yes, gonna be RELEASE. I have > no possibility to cvs or some other fancy > thing.) If it is based on the Lucent Winmodem chipset, as you say, it might be supported by the /usr/ports/comm/ltmdm port. Should you buy it? Only if you can return it for a refund should you find that it won't work with FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: LSI (nee AMI) MegaRAID on Compaq ML310
Please pardon the top-posted follow-up to my own message, but I want to get the solution into the archives. Many thanks to emoore for providing a driver update disk containing mide-4.7.ko to add support for the LSI Logic MegaRAID embedded RAID controller under FreeBSD 4.7-RELEASE. dmesg now shows: [snip] avail memory = 255733760 (249740K bytes) Preloaded elf kernel "kernel" at 0xc054e000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc054e09c. Preloaded elf module "mide.ko" at 0xc054e0ec. [snip] pcib0: on motherboard pci0: on pcib0 mide1: port 0x2030-0x203f,0x2028-0x202b,0x2020-0x2027,0x2018-0x201b,0x2010-0x2017 irq 5 at device 2.0 on pci0 mide1: BIOS 2.5.03181648 mide1: LD 0 RAID1 status = ONLINE sectors = 78161263 capacity = 38164 MB drives = 2 bge0: mem 0xf7ff-0xf7ff irq 10 at device 3.0 on pci0 bge0: Ethernet address: 00:08:02:ef:b8:56 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto [snip] pcib128: on motherboard pci128: on pcib128 pcib1: on motherboard pci1: on pcib1 eisa0: on motherboard mainboard0: on eisa0 slot 0 orm0: at iomem 0xc-0xc7fff,0xc8000-0xc8fff,0xee000-0xe on isa0 [snip] da0 at mide1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 100.000MB/s transfers (16bit), Tagged Queueing Enabled da0: 38164MB (78161265 512 byte sectors: 255H 63S/T 4865C) Mounting root from ufs:/dev/da0s1a On Mon, Jan 20, 2003 at 02:08:29PM -0800, James Long wrote: > I have a Compaq ProLiant ML310, with an integrated ATA RAID controller > controlling two 40G Seagate ST340016A drives. > > >From some Googling, I have learned: > > The ML310 uses the ServerWorks GC SL chipset -- see > http://h18004.www1.hp.com/products/servers/proliantml310/description.html > > ServerWorks appears to be in cahoots with LSI -- see > http://www.enterprisestorageforum.com/hardware/news/article/0,,10559_1480661,00.html > > LSI bought AMI's MegaRAID technology -- see > http://people.freebsd.org/~msmith/RAID/ami/notes.html > > My dmesg shows some unidentified hardware, but does not recognize the RAID > controller as an amr device. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Buildworld Error building libpam.a
On Wed, Jan 22, 2003 at 11:05:15AM -0800, Glendon M. Gross wrote: > > I am getting the following when attempting "make buildworld". Is there > a known fix for this error? Please reply to me directly, as I am not > currently subscribed to the list. > > > cc -O -pipe > -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/openpamo > building static pam_deny library > > ranlib libpam_deny.a > > cc -fpic -DPIC -O -pipe > -I/usr/src/lib/libpam/modules/pam_deny/../../../../cono > make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libpam.a. > Stop > *** Error code 2 > > > > Stop in /usr/src/lib/libpam/modules. > > *** Error code 1 I was getting a specific buildworld error yesterday also, although not in the same spot you are. Re-cvsupping fixed mine. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Partial kernel log lines in security output
In the security run output notifications from most nearly every machine I monitor, I see lines in the kernel log messages section similar to: example.com kernel log messages: > .14.232:48342 506.29.618.239:80 in via dc0 That's just a reconstructed example, but the pattern is that first, the log message is not from the appropriate time frame, and has the first part of the line clipped off. Another typical example is a 'file system full' message which is several weeks old, and similarly omits the first part of the log entry. What is causing these, and how can I be rid of them? Thank you! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
mergemaster: what if I want both left and right?
In doing some merges lately, I've gotten into situations where mergemaster gives me a choice between old lines I want to keep on the left, and new lines which I want to add on the right. A specific example was in merging my /etc/group and /etc/passwd files, I had the choice between some existing groups which I need to retain on the left, and some newly-added system groups which I want to incorporate, on the right. How can I tell mergemaster something like, "insert the left alternative first, followed by the right alternative" or vice versa, right first, then left? Must I just edit the file(s) manually? And I suppose if we're going to add some flavor of a 'both' option, it's only a matter of time before a need for 'neither' arises. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
