Re: ISO IMAGES
On 2003.11.26 22:53:26 +0100, Claus Guttesen wrote: Hi. Will ISO images be released for 5.2-BETA i386? Or is that strictly an -RC thing? Ftp'ed to ftp.freebsd.org using a freebsd-ftp-client but couldn't find the ISO-image for 5.2 beta. Using OS X's finder found the folder and files. Peculiar. Permissions? No, ftp.freebsd.org is actually two servers. At the moment one of them has the images, not the other: [EMAIL PROTECTED]:ISO] host ftp.freebsd.org ftp.freebsd.org has address 62.243.72.50 ftp.freebsd.org has address 204.152.184.73 ftp.freebsd.org has address 2001:4f8:0:2::e [EMAIL PROTECTED]:ISO] ncftpls ftp://62.243.72.50/pub/FreeBSD/ISO-IMAGES-i386/5.2/ ncftpls: Could not change directory: server said: No such directory. [EMAIL PROTECTED]:ISO] ncftpls ftp://204.152.184.73/pub/FreeBSD/ISO-IMAGES-i386/5.2/ 5.2-BETA-i386-disc2.iso 5.2-BETA-i386-miniinst.iso CHECKSUM.MD5 [EMAIL PROTECTED]:ISO] BTW, ftp.se.freebsd.org also has them, which is probably closer to you :-). -- Simon L. Nielsen FreeBSD Documentation Team pgp0.pgp Description: PGP signature
Re: WITHOUT_DYNAMICROOT vs. NO_DYNAMICROOT
On 2003.11.25 12:52:03 +0100, Schuendehuette Matthias wrote: Hi, There's a bug in the release notes of CURRENT: In Chapter 2.3 Userland Changes of the ReleaseNotes of CURRENT I read about the Makefile variable WITHOUT_DYNAMICROOT whereas /usr/src/Makefile.inc1 wants -DNO_DYNAMICROOT. It should be corrected in the ReleaseNotes (IMHO) Yes, that should be changed. I just asked the RE team permission to fix this (since we are in a code freeze at the moment). Thanks for reporting it. -- Simon L. Nielsen FreeBSD Documentation Team pgp0.pgp Description: PGP signature
Re: 4 Clause license?
On 2003.11.17 14:48:08 -0500, Rod Taylor wrote: The PostgreSQL group has recently had a patch submitted with a snippet of code from FreeBSDs src/bin/mkdir/mkdir.c. http://www.freebsd.org/cgi/cvsweb.cgi/src/bin/mkdir/mkdir.c?annotate=1.27 Is this intentionally under the 4 clause license or does the copyright from the website (2 clause) applied to everything that is non-contrib? The license in each file is the one that is authoritative. The file you are refering to has original 'The Regents of the University of California' copyright, so the advertising clause is revoked as per ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change . Hope this helps. Disclaimer: This is my own view of the issue, and I don't speak officially for the FreeBSD project. I'm sure somebody will correct me if I'm wrong :-). -- Simon L. Nielsen FreeBSD Documentation Team pgp0.pgp Description: PGP signature
Re: RB_BOOTINFO not found in sys/boot/i386/boot2/boot2.c
On 2003.11.11 11:15:11 +0200, Anton Yudin wrote: RB_BOOTINFO, defined in reboot.h, not found in sys/boot/i386/boot2/boot2.c .. can somebody fix this? I'm rather sure bde already fixed this some hours ago in src/sys/boot/i386/boot2/boot2.c v 1.66. -- Simon L. Nielsen FreeBSD Documentation Team pgp0.pgp Description: PGP signature
Re: [PATCH] connect bluetooth configs and examples to the build
On 2003.10.21 13:47:16 -0700, Maksim Yevmenkin wrote:
i'd like to commit attached patch. the purpose is to connect etc/bluetooth
and share/examples/netgraph/bluetooth to the build. please review and let
me know if i missed anything.
Index: src/etc/bluetooth/Makefile
===
RCS file: src/etc/bluetooth/Makefile
diff -N src/etc/bluetooth/Makefile
--- /dev/null 1 Jan 1970 00:00:00 -
+++ src/etc/bluetooth/Makefile21 Oct 2003 20:20:03 -
@@ -0,0 +1,10 @@
+# $Id: Makefile,v 1.1 2003/10/20 16:48:45 max Exp $
+# $FreeBSD$
+
+FILESDIR=${DESTDIR}/etc/bluetooth
I'm rather sure that you shouldn't include DESTDIR, since bsd.files.mk
does that. Also you should probably use the style from
style.Makefile(5) for new Makefile's.
--
Simon L. Nielsen
FreeBSD Documentation Team
pgp0.pgp
Description: PGP signature
Re: [PATCH] connect bluetooth configs and examples to the build
On 2003.10.21 16:40:57 -0700, Maksim Yevmenkin wrote: Also you should probably use the style from style.Makefile(5) for new Makefile's. could you please be more specific? i took a quick look at style.Makefile(5) page and could not find anything related to my case. Sorry, I should have been more specific. I was thinking about the whitespace part: o Typically, there is one ASCII tab between VAR= and the value in order to start the value in column 9. An ASCII space is allowed for vari- able names that extend beyond column 9. A lack of whitespace is also allowed for very long variable names. I don't say that you must to follow that (I'm just a doc guy), I just want to point out that it's there :-). -- Simon L. Nielsen FreeBSD Documentation Team pgp0.pgp Description: PGP signature
Re: mounting vfat at boot
On 2003.10.05 18:20:45 +0200, Christer Solskogen wrote: FreeBSD 5.1-RELEASE I got the following lines in my /etc/fstab : /dev/ad1s1 /mnt/dmsdos rw -m 775,user /dev/ad0s2 /mnt/emsdos rw, -m 775,user I think it should be msdosfs on -CURRENT. -- Simon L. Nielsen FreeBSD Documentation Team pgp0.pgp Description: PGP signature
Re: KDE Konsole, crashes, on a SIGABRT...
On 2003.08.23 23:34:53 +0200, Michael Nottebrock wrote: Content-Description: signed data On Saturday 23 August 2003 22:52, Mike Makonnen wrote: As far as I know text attachments are still accepted. So, if the attachment is being stripped either you are sending gziped/uuencoded attachments or your MUA is not describing it as text. Well, it was described as text/x-diff. Not an officially IANA registered MIME-type, but text/* nonetheless... perhaps the mailing list manager should be configured to be a little less anal. FYI, this is actually documented: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAILFILTERING If you think 'text/x-diff' should be allowed, you can ask [EMAIL PROTECTED] (If get it added to the allowed list, please let me or -doc know so the handbook can be updated.) -- Simon L. Nielsen FreeBSD Documentation Team pgp0.pgp Description: PGP signature
Re: 8MB install
On 2003.06.25 21:30:28 -0700, Terry Lambert wrote: Simon L. Nielsen wrote: On 2003.06.25 12:10:42 +0200, Michael Nottebrock wrote: FWIW, the last FreeBSD release I managed to install on an 8mb machine from CD-ROM+bootfloppies was 4.1.1. Can anybody else confirm this ? It seems like the documetation need to be updated to state this. State what? That you should use 4.1.1 on 8M 486 machines, if you intend on installing from media that require the use of a RAM disk for installation? Seems a little specialized... 8-). Hehe yes :-). The documentation should just not indicate that it is possible to install on 8MB, when it isn't. Currently the FAQ says : FAQ 3.5. I have only 4 MB of RAM. Can I install FreeBSD? FreeBSD 2.1.7 was the last version of FreeBSD that could be installed on a 4MB system. FreeBSD 2.2 and later needs at least 5MB to install on a new system. All versions of FreeBSD will run in 4MB of RAM, they just cannot run the installation program in 4MB. [CUT] /FAQ Which doesn't really seem to match any current reality with regards to both CURRENT and STABLE. Have anybody made any recent tests on CURRENT (and STABLE for that matter) with regards to minimum RAM requirements, install and normal runtime? Yes; about two months ago there were a couple of people who installed on an old 386SX. The main issue was that they had to roll their own distribution from sources, specifically with a stripped down kernel without all the weird drivers (which is exactly what I talked about in my previous posting). From what I understood that test was more a test of whether it was possible to run 5.x on a 386, not to actually find out the minium RAM for install/run. I think I will try to dig up my old 486 next week, and try to find the actual requirements for a sysinstall based installation on more recent FreeBSD versions. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: error during buildworld
On 2003.06.26 22:59:32 +1000, David Lodeiro wrote: Last night I CVSupped my system for the first time, It came up with no errors. I then went to make buildworld and I got the following error. Do another cvsup, this has already been fixed. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: 8MB install
On 2003.06.25 12:10:42 +0200, Michael Nottebrock wrote: On Wednesday 25 June 2003 11:44, Terry Lambert wrote: Alternately, you could find a FreeBSD 1.1.5.1 distribution on the net somewhere, and install that, instead; I have personally run that version of FreeBSD on a 4M 386SX, to use it as an X Terminal. 8-). FWIW, the last FreeBSD release I managed to install on an 8mb machine from CD-ROM+bootfloppies was 4.1.1. Can anybody else confirm this ? It seems like the documetation need to be updated to state this. Have anybody made any recent tests on CURRENT (and STABLE for that matter) with regards to minimum RAM requirements, install and normal runtime? -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: /usr/libexec/save-entropy problem
On 2003.06.25 18:38:59 +0200, Rob wrote: I get e-mails from my current boxes saying: hostname: sethostname: Operation not permitted (original message attached). I know this is the random seed saving instance of crontab, but what goes wrong here ? (why does it fail permission) The box is updated today and mergemaster was run (This didn't help a thing ;-)) What does your /etc/rc.conf contain ? Perhaps you have commands which sets the hostname in there ? -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: make.conf and MASTER_SITE_BACKUP
On 2003.06.23 19:42:25 +0200, Byron Schlemmer wrote: Had a quick search around mail archives and problem reports. Did spot anything, but it seems MASTER_SITE_BACKUP?= MASTER_SITE_OVERRIDE?= work in make.conf for 5 however make.conf(5) doesn't seem to mention it? Is this a feature? Partly. They are described in ports(7), which is referenced from make.conf(5). -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: Need acpi-event-d?
On 2003.06.16 07:07:36 -0400, David Gilbert wrote: First, I must say that it's cool that ACPI code can be examined and rewritten. In my laptop's case, this was key to make things fairly happy. Anyways, after a resume, it would appear I need to kill and restart moused. Under 4.x, apmd was used for this purpose ... but this new laptop doesn't support apm at all. /dev/apm seemed to be emulated by acpi for the benifit of battery monitors, but apmd won't run. Is there a facility to run things on resume, or is this reset something better done inside the kernel? I think devd(8) should be used for this, but I havn't tried. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: Way forward with BIND 8
On 2003.06.06 14:36:44 +0100, Paul Robinson wrote: This is almost as bad as OpenBSD sticking with BIND 4... OpenBSD has actually uses BIND 9 now... -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: HD Speed Benchmark
On 2003.06.03 22:20:56 +0200, Sebastian Yepes [ESN] wrote: I have made some Benchmark on my inspiron 8500 (Intel 82801DB (ICH4) - UDMA100) and i am geting very Bad results on the 5.1, i have got beter results on 5.0 Beta2 still had all the debugging options in the kernel, so unless you have removed them, and recompiled your kernel, thats what you are seeing. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: SU not working after CVSUP
On 2003.06.03 02:17:58 -0500, Mike Loiterman wrote: Just cvsup'd to current a few hours ago. Built and installed world and kernel without any errors. Now I get this error when I try to su to any user: Jun 3 01:45:22 enola su: in openpam_load_module(): no pam_wheel.so found Bus error (core dumped) enola# Jun 3 01:45:22 enola kernel: pid 507 (su), uid 0: exited on signal 10 (c ore dumped) Since pam_wheel something must still be referencing it... Have you run mergemaster ? -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: ftp.freebsd.org
On 2003.06.01 14:57:41 -0700, Julian Elischer wrote: This brings up a question.. How do we find out who to contact for each mirror etc.? In the handbook :) http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html or perhaps the hubs mailling list if contact information is out of date. I notice cvsup14 has been unreachable for a month now.. According to the handbook it should be adminitered by: cvsup14.FreeBSD.org (maintainer [EMAIL PROTECTED]), California -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: raidframe
On 2003.06.02 11:18:34 +0300, Petri Helenius wrote: So far I´ve tried asr and aac, both cards end up in kernel panics and/or array hang in a few minutes (multiple hardware platforms so I don´t think the motherboard is to blame) I have an asr based RAID controller (Adaptec 2400A), though it is an IDE RAID controller, it uses the SCSI asr driver. My controller has worked very well with FreeBSD 5.x, and the server is currently running 5.1-BETA. The only thing that doesn't work, is the userland utilities to control / get status from the card, but that's not so important. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: cvs commit: src/share/man/man4 axe.4 mac_portacl.4my.4rndtest.4 rue.4 sbsh.4 src/share/man/man4/man4.i386 pae.4sbni.4 vpd.4
On 2003.05.30 17:36:32 +0300, Ruslan Ermilov wrote: On Fri, May 30, 2003 at 02:28:29PM +0200, Simon L. Nielsen wrote: Or perhaps This driver first appeared in FreeBSD 4.9 and 5.1... or something along those lines. Yes, that will do! I will fix it later today, thank you! Great :) This reminds me that I have seen some manual pages saying: This XXX first appeared in NetBSD 1.5, and so on, without mentioning when it was included in FreeBSD. I'm not sure how much we care about getting the FreeBSD release in there... ? -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: cvs commit: src/share/man/man4 axe.4 mac_portacl.4my.4rndtest.4 rue.4 sbsh.4 src/share/man/man4/man4.i386 pae.4sbni.4 vpd.4
On 2003.05.30 09:21:52 -0300, Daniel C. Sobral wrote: Wilko Bulte wrote: On Fri, May 30, 2003 at 12:31:05AM +0300, Ruslan Ermilov wrote: Now this is real funny: the sbsh(4) manpage says the driver first appeared in FreeBSD 4.9, but 5.1 will be released before 4.9. Something wrong with our release model? ;) Virtualised time? Actually, that attribution is plain wrong. If we say 4.9 was the first because 4.9 5.1, then it is wrong because 5.0 doesn't have it. If we say 4.9 was the first because 4.9 was released before 5.1, well, it isn't. The only way to do it is use the actual order of release, however much trouble that might cause to people running 4.9 that get surprised that a feature was first present in 5.1. :-) Or perhaps This driver first appeared in FreeBSD 4.9 and 5.1... or something along those lines. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
panic: mutex Giant not owned at sys/kern/kern_exit.c:122
Hello When i try to create an RAID array with atacontol I get the following panic when the rebuild is complete. The problem seems to be that exit1 requires that giant is held but it isn't. I have no idea where it should be aquired so it will be released again. #0 doadump () at /data/FreeBSD/CURRENT/sys/kern/kern_shutdown.c:239 #1 0xc0300403 in boot (howto=256) at /data/FreeBSD/CURRENT/sys/kern/kern_shutdown.c:371 #2 0xc0300703 in panic () at /data/FreeBSD/CURRENT/sys/kern/kern_shutdown.c:542 #3 0xc02f743c in _mtx_assert (m=0xc053cc00, what=0, file=0xc04e6095 /data/FreeBSD/CURRENT/sys/kern/kern_exit.c, line=122) at /data/FreeBSD/CURRENT/sys/kern/kern_mutex.c:844 #4 0xc02e9583 in exit1 (td=0xc284a000, rv=4352) at /data/FreeBSD/CURRENT/sys/kern/kern_exit.c:122 #5 0xc02ee946 in kthread_exit () at /data/FreeBSD/CURRENT/sys/kern/kern_kthread.c:135 #6 0xc01cf4c5 in ar_rebuild () at /data/FreeBSD/CURRENT/sys/dev/ata/ata-raid.c:859 #7 0xc02ec8d4 in fork_exit (callout=0xc01cf080 ar_rebuild, arg=0x0, frame=0x0) at /data/FreeBSD/CURRENT/sys/kern/kern_fork.c:796 Btw. the -CURRENT is from today. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Inaccessible ad devices
Hello I have 4 IDE disks that I'm going to use for a small RAID. During my testing with the ata(4) software RAID I had created a RAID0 on two of the disks. I then deleted it and tried to create a new array (different interleave) but I had forgotten to unmounted the filesystem on the RAID I just deleted and I got a kernel panic - at least i think that was the sequence of events. The problem is that the RAID configuration was apparently left in a somewhat undefined state so now there is neither a configured RAID (no ar device) or any normal ad devices for the two disks. When I got the panic I was running a older 4.7-RC but I now run -CURRENT from today on it (dual boot). I have the same problem with the missing disks under 4.7-RC and 4.8-RELEASE. I can still create a new RAID on the two remaining disk. Since updating the -CURRENT today I get a panic when creating the array (on ad8 and ad10) but after reboot the array is configured and works. I'm currently trying to create a proper crash dump for this but i'm rather sure this is unreleated to the missing disks. More information (the missing disks are ad4 and and6) : # uname -a FreeBSD ford.nitro.dk 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Apr 4 16:57:56 CEST 2003 [EMAIL PROTECTED]:/usr/obj/data/FreeBSD/CURRENT/sys/GENERIC i386 Part of dmesg (full boot -v at http://simon.nitro.dk/temp/ataraid/dmesg.boot-verbose) : atapci0: VIA 82C686A UDMA66 controller port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 [CUT] atapci1: Promise PDC20268 UDMA100 controller port 0xcc00-0xcc0f,0xd000-0xd003,0xd400-0xd407,0xd800-0xd803,0xdc00-0xdc07 mem 0xefffc000-0xefff irq 11 at device 13.0 on pci0 ata2: at 0xdc00 on atapci1 ata3: at 0xd400 on atapci1 atapci2: Promise PDC20268 UDMA100 controller port 0xac00-0xac0f,0xb000-0xb003,0xb400-0xb407,0xb800-0xb803,0xbc00-0xbc07 mem 0xefff8000-0xefffbfff irq 12 at device 14.0 on pci0 ata4: at 0xbc00 on atapci2 ata5: at 0xb400 on atapci2 [CUT] ad0: 29314MB IBM-DTLA-307030 [59560/16/63] at ata0-master UDMA66 ad8: 76319MB WDC WD800JB-00CRA1 [155061/16/63] at ata4-master UDMA100 ad10: 76319MB WDC WD800JB-00CRA1 [155061/16/63] at ata5-master UDMA100 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Opened disk ad4 - 16 Opened disk ad4 - 16 Opened disk ad6 - 16 Opened disk ad6 - 16 Mounting root from ufs:/dev/ad0s3a [CUT] # atacontrol list ATA channel 0: Master: ad0 IBM-DTLA-307030/TX4OA60A ATA/ATAPI rev 5 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: ad4 WDC WD800JB-00CRA1/17.07W17 ATA/ATAPI rev 5 Slave: no device present ATA channel 3: Master: ad6 WDC WD800JB-00CRA1/17.07W17 ATA/ATAPI rev 5 Slave: no device present ATA channel 4: Master: ad8 WDC WD800JB-00CRA1/17.07W17 ATA/ATAPI rev 5 Slave: no device present ATA channel 5: Master: ad10 WDC WD800JB-00CRA1/17.07W17 ATA/ATAPI rev 5 Slave: no device present # atacontrol status 0 atacontrol: ioctl(ATARAIDSTATUS): Device not configured -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: Kernel panic - never had one before, what do I do?
On 2003.03.26 13:35:28 +, Jason Morgan wrote: I just got a panic. As I have never had one before, I don't know what to do. It's on another system so I don't have to reboot immediately (that Have a look at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING for information on how to get more information from a panic. -- Simon L. Nielsen pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPDIVERT problem?
On 2003.03.21 14:51:18 -0500, Kevin S. Brackett wrote: ipfw: opcode 50 size 1 wrong getsockopt(IP_FWD_ADD): something something Are you really sure that your kernel/world is in sync? This is the kind of error you can get if they are not in sync. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: Freeze after APIC_IO: Testing 8254 interrupt delivery
On 2003.03.05 20:52:21 +0100, Attila Nagy wrote: Our newly bought Fujitsu-Siemens F250 boots with the GENERIC kernel, but with a recent, SMP-capable CURRENT it freezes after the following line: APIC_IO: Testing 8254 interrupt delivery I had the same problem with a FSC P250 (same motherboard) using 4.7-REL. It works in SMP mode with a recent 4-STABLE (after MFC of HTT). It appears to only work if HyperThreading is enabled. John Baldwin commited changes to -CURRENT a few days ago to disable HTT unless it is explicitly enabled in the kernel config file. That could be the problem. I'm currently trying to get it to work without HTT enabled but so far not succeeding. -- Simon L. Nielsen pgp0.pgp Description: PGP signature
Re: machdep.guessed_bootdev sysctl on i386
On 2003.02.24 01:35:02 -0500, Hiten Pandya wrote:
Okay. I have attached a patch which will nuke the sysctl, and replace
it's use in picobsd's mfs_tree rc scripts with something better, but
which still needs review. I have not tested the patch, but this patch
should not fail, hopefully.
PicoBSD does not necessarily have awk (actually most likely doesn't
since awk is 'big'). cut could be used instead since it much smaller :
mount | grep 'on / ' | cut -f 1 -d ' '
Perhaps somebody has a better way?
I have cc'ed -small, since somebody there might have good idea.
Index: src/release/picobsd/mfs_tree/etc/rc
===
RCS file: /home/ncvs/src/release/picobsd/mfs_tree/etc/rc,v
retrieving revision 1.9
diff -u -r1.9 rc
--- src/release/picobsd/mfs_tree/etc/rc 17 Nov 2002 20:19:34 - 1.9
+++ src/release/picobsd/mfs_tree/etc/rc 24 Feb 2003 06:21:31 -
@@ -7,7 +7,7 @@
HOME=/; export HOME
PATH=/bin; export PATH
-dev=`sysctl -n machdep.guessed_bootdev`
+dev=`mount | grep 'on / ' | awk '{ print $1 }'`
[ -c ${dev} ] || dev=/dev/fd0
trap echo 'Reboot interrupted'; exit 1 3
Index: src/release/picobsd/mfs_tree/stand/update
===
RCS file: /home/ncvs/src/release/picobsd/mfs_tree/stand/update,v
retrieving revision 1.5
diff -u -r1.5 update
--- src/release/picobsd/mfs_tree/stand/update 11 Mar 2002 05:15:44 - 1.5
+++ src/release/picobsd/mfs_tree/stand/update 24 Feb 2003 06:20:08 -
@@ -5,7 +5,7 @@
thefiles=$*
[ -z $thefiles ] \
thefiles=/etc/rc.conf /etc/rc.firewall /etc/master.passwd
-dev=`sysctl -n machdep.guessed_bootdev`
+dev=`mount | grep 'on / ' | awk '{ print $1 }'`
[ -c ${dev} ] || dev=/dev/fd0
mount ${dev} /mnt
if [ $? != 0 ] ; then
[CUT]
--
Simon L. Nielsen
pgp0.pgp
Description: PGP signature
Re: IPFilter
On 2003.02.10 23:37:36 +0100, Coercitas Temet'Nosce wrote: Yes, SPI stands for Statefull Packet Inspection. Wasn't aware IPFW was a SPI Firewall, always thought IPFilter was much better. I used to run iptables on Linux and tried IPFilter (which is very good imho). IPFW pages aren't that explicit or I didn't looked at the right place. From ipfw(8) : HISTORY The ipfw utility first appeared in FreeBSD 2.0. dummynet(4) was intro duced in FreeBSD 2.2.8. Stateful extensions were introduced in FreeBSD 4.0. ipfw2 was introduced in Summer 2002. Any of you can point me some nice pages to learn more about it ? The ipfw manpage has a lot of information... This is getting off-topic for current... -- Simon L. Nielsen msg52174/pgp0.pgp Description: PGP signature
Re: make buildkernel failure
On 2003.02.03 18:52:09 -0600, Nick H. -- Technical Support Engineer wrote: I've now run into this 2 times this week... doing a make buildkernel with pretty much generic (SMP turned on and IPFILTER enabled with logging and default block): From UPDATING : 20030125: The scheduler framework has grown a second scheduler and consequently you must specify one and only one scheduler in your kernel config. The in cvs config files have been updated to use the old scheduler which may be selected via 'options SCHED_4BSD'. If you would like to try the new, much more experimental, scheduler please try 'options SCHED_ULE' and contribute to the arch@ discussion. -- Simon L. Nielsen msg51710/pgp0.pgp Description: PGP signature
Re: Which RELENG_5 for cvsup for RELEASE?
On 2003.01.21 03:13:41 +, Harald Schmalzbauer wrote: I'd like to cvsup from RC1 to RELEASE. Is it still RELENG_5_0 or something else? Yes it is still RELENG_5_0 - RELENG_5 will not be created untill after FreeBSD 5.1 or 5.2. -- Simon L. Nielsen msg50615/pgp0.pgp Description: PGP signature
Re: some 5.0 oddities
On 2003.01.18 13:37:53 +, Dag-Erling Smorgrav wrote: boot2 no longer accepts keyboard input. I'm not sure exactly when this happened, but it was some time late last year. I have -Dh in /boot.config, but sometimes I want to use the vga console instead of the serial console. It used to be possible to interrupt boot2 before it loaded /boot/loader, and type '-h' to switch back to the vga console. This doesn't work any more. Isn't this fixed by the commit on the 13 by imp : imp 2003/01/13 13:28:24 PST Modified files: sys/boot/i386/boot2 boot2.c Log: Fix interactive booting: o Revision 1.38 introduced the -n flag. It conflicted with the RB_BOOTINFO flag, so was in effect always on. Change the -n flag to be bit 0x1c instead of 0x1f. This also had the consequence that a mal-formed /boot.config would render the system unbootable because the user was unable to enter anything at all on the command line. o Remove the initialization of opt to be RB_BOOTINFO since we filter that bit out and do not otherwise use it. I have not tested this but it sounds the it should be working now? -- Simon L. Nielsen msg50472/pgp0.pgp Description: PGP signature
Re: Q) Does perl install libperl.so ?
On 2003.01.05 12:52:03 +, Yamada Ken Takeshi wrote: /usr/ports/lang/perl5 seemingly does not generate libperl.so with FreeBSD-current port as shown below. Is it intended one? Why? This was discussed on the ports list a while ago : http://www.freebsd.org/cgi/getmsg.cgi?fetch=593062+595495+/usr/local/www/db/text/2002/freebsd-ports/20021208.freebsd-ports -- Simon L. Nielsen msg49697/pgp0.pgp Description: PGP signature
Re: Q) Does perl install libperl.so ?
On 2003.01.05 21:23:32 +, Yamada Ken Takeshi wrote: I read through articles you pointed, but couldn't find the conclusion. What was the outcome of the discussion? or, still pending? I think the original submitter of the problem would try to look in to why plperl did not use the .a version, but since I don't use plperl myself I have not looked more at it myself. I am now wrecked at 'plperl' installation as it is mentioned in the discussion. :-( -- Simon L. Nielsen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
