Re: cd writer recommendation?
Sorry about that . The emphasis is more on the hardware and second is the software -- I usually get around problems with the software. Is there any support for IDE CD writers or are they not worth bothering with on FreeBSD. Tnks! On Sun, 15 Aug 1999, Amancio Hasty wrote: Any one care to recommend a CD writer for FreeBSD-current since thats typically what I run over here. Are you asking for recommendation about hardware or software? It's not evident from your wording. Tnks -- Amancio Hasty [EMAIL PROTECTED] Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
On Mon, 16 Aug 1999, Amancio Hasty wrote: Sorry about that . The emphasis is more on the hardware and second is the software -- I usually get around problems with the software. Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and dd are a good combination for writing them. Is there any support for IDE CD writers or are they not worth bothering with on FreeBSD. Yes, there is support for them :) Tnks! On Sun, 15 Aug 1999, Amancio Hasty wrote: Any one care to recommend a CD writer for FreeBSD-current since thats typically what I run over here. Are you asking for recommendation about hardware or software? It's not evident from your wording. Tnks -- Amancio Hasty [EMAIL PROTECTED] Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Most Cool! Is there a list of IDE cd writers which work FreeBSD? Tnks Again! On Mon, 16 Aug 1999, Amancio Hasty wrote: Sorry about that . The emphasis is more on the hardware and second is the software -- I usually get around problems with the software. Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and dd are a good combination for writing them. Is there any support for IDE CD writers or are they not worth bothering with on FreeBSD. Yes, there is support for them :) Tnks! On Sun, 15 Aug 1999, Amancio Hasty wrote: Any one care to recommend a CD writer for FreeBSD-current since thats typically what I run over here. Are you asking for recommendation about hardware or software? It's not evident from your wording. Tnks -- Amancio Hasty [EMAIL PROTECTED] Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
Warner Losh wrote: In message [EMAIL PROTECTED] Mike Smith writes: : We're staying away from the term "emulation" because it's being : associated with things like the abominable 'lxrun' and virtual-machine : emulators like VMware. Also, there is a perception that "emulation" is slower than native, which isn't the case for the Linux ABI in FreeBSD. The Linuxulator adds overhead, which does make it slower than native. Take for example the overlaying of /compat/linux. File/dir access-bound applications (such as find) pay the penalty. Other areas of overhead are translations of bitmaps and/or structures. In general, the overhead is minimal, but nonetheless there's overhead and there're cases in which you can definitely see a performance drop as compared to native execution. I qualify the Linuxulator as an emulator. Although we are lucky to not have to emulate an architecture (see /usr/ports/emulators for examples) or a subset of an instruction set (option MATH_EMULATE for example), we do have to emulate an OS interface. The Linuxulator isn't a compatability thingy, because we're not that good an emulator. You cannot replace the one with the other and not see any side-effects. The emotional argument that as to why we stay away from the term "emulation" does not mean that the Linuxulator isn't an emulator, we're just calling it differently... anyway, my Euro 0.02 :-) -- Marcel Moolenaar mailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
I think that emulation usually denotes simulation so I would find another term or invent one to describe the linux emulation layer. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Cyrix/IBM CPU detection
Current CPU detection routine sometimes fails to detect IBM BlueLightning CPU. The problem is caused by failure of Cyrix/IBM CPU detection in sys/i386/i386/locore.s. Our Cyrix/IBM CPU detection code is different from that in Cyrix's BIOS writer's guide because latter code cannot distinguish NexGen CPU from Cyrix CPU. Our locore.s detects NexGen CPU before Cyrix CPU detection. So, there is no reason for not using Cyrix's code. I have made a patch bellow which use Cyrix's code. Please report results on following CPUs: 1. IBM BlueLightning CPU (IBM 486SLC) 2. Cyrix/IBM/TI 486SLC/DLC CPU 3. Cyrix/IBM 486DX/DX4 CPU 4. Cyrix 5x86 CPU (aka M1sc CPU) 5. Cyrix 6x86 CPU (aka M1 CPU) 6. Intel 386 CPU I have already received reports on i486DX2 and AMD Am5x86 CPUs and they work without any problem. Also, if you find a problem on other CPU than above list, please let me know. Thank you. -- BEGIN -- *** locore.s.ORIG Mon Aug 16 14:28:56 1999 --- locore.sMon Aug 16 14:32:33 1999 *** *** 674,685 * Note: CPUID is enabled on M2, so it passes another way. */ pushfl ! movl$0x, %eax ! xorl%edx, %edx ! movl$2, %ecx ! clc ! divl%ecx ! jnc trycyrix popfl jmp 3f /* You may use Intel CPU. */ --- 674,686 * Note: CPUID is enabled on M2, so it passes another way. */ pushfl ! movl$5, %eax ! movl$2, %ebx ! sahf ! divb%bl ! lahf ! cmpb$2, %ah ! je trycyrix popfl jmp 3f /* You may use Intel CPU. */ -- END -- ---+--+ KATO Takenori [EMAIL PROTECTED] |FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. |The power to serve! | Nagoya, 464-8602, Japan| http://www.FreeBSD.org/ | FreeBSD(98) 3.2: Rev. 01 available! |http://www.jp.FreeBSD.org/| FreeBSD(98) 2.2.8: Rev. 02 available! +==+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
hi, there! On Sun, 15 Aug 1999, Amancio Hasty wrote: Any one care to recommend a CD writer for FreeBSD-current since thats typically what I run over here. I use Sony CDU948S-RP more than year. works like a charm If cd-recorder is not MMC-compatible check that cdrdao supports it directly (Sony driver have been implemented recently) I think any SCSI cd-recorder will work perfectly /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
Brian F. Feldman writes: On Sun, 15 Aug 1999, Warner Losh wrote: In message [EMAIL PROTECTED] "Brian F. Feldman" writes: : I suppose, but wouldn't the proper place be under machdep? I agree that : a linux top-level MIB would be easiest to remember. Linux isn't machdep. It is MI since we could have Linux/Alpha or Linux/MIPS emulators... Well then, we need to move it a directory level and take out machine dependencies, and make it machine independent. Linux is actually a little bit machdep: we can't move it all up a directory level because most of the syscall numbers, as well as many flags (to mmap, ioctl, etc) are different between linux/i386 linux/alpha. They bootstrapped themselves off of osf/1 never reverted back to their own flags/syscall numbers, they just grew a new set instead. So I'd suggest moving everything but linux.h the syscall related files up a level. There will need to be some ifdefs in the code, but not many. I've been working a little on getting the Linuxulator running on FreeBSD/alpha. Because linux is such a bloody cludge (the syscall flags differences), its a bit more difficult that I initially thought it would be. The also call some functions (osf1_setsysinfo, for example) which are really osf/1 calls. Luckily, I have my osf/1 compat code which I'm using to field these. Right now it works well enough to install linux_base from ports (good job in keeing it MI, Marcel!) run things like ls, uname, etc. However, its not useful for anything real just yet. My goal is to get em86 (the x86 emulator that lets linux/alpha run linux/i386 binaries) running, as well as the Compaq compilers. Drew PS: Is anybody interested in reviewing my osf/1 compat code so that it can be comitted? It works quite well (SimOS, Netscape, Mathematica, Matlab, S-Plus, emacs, etc all run), but I'd really like somebody to look it over before I commit it. I've left it at http://www.freebsd.org/~gallatin/osf1.tar.gz -- Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: [EMAIL PROTECTED] Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
$B=i$a$^$7$F!"Gp:j$H?=$7$^$9!#(B
$B=i$a$^$7$F!"%$%*%s%IBg3X$NGp:j!!M5;R$H?=$7$^$9!#(B $B%$%*%s%IBg3X!!LM@Gn;N!!?dA0Q0w2q@_N)$N$*CN$i$;$,$"$j(B $B$^$7$F!"%a!%k$rCW$7$^$7$?!#(B $B$3$NEY!"(BIOND University$B!J%O%o%$=#G'2D!"(BWAUC$B2CLA!K$G$O!"(B $BF|K\$N3F3$K$*$$$FB?Bg$J$kR2qE*B@S$r@Q$^$l$?J}!9$KBP(B $B$7Bg3X@_N)$r5-G0$7$F!"LM@Gn;N9f$rxM?$9$k$3$H$HCW$7$^(B $B$7$?!#$=$N$?$a$K3F3$NxM?T$r?dA$9$k3FETF;I\8)?dA0Q(B $B0w2q$r@_N)$9$k$3$H$K$J$j$^$7$?!#(B $BLM@Gn;N?dA0Q0wBP]T$O0J2$NDL$j$G$9!#(B $B!!#1(B. $B3FETF;I\8)?tL(B $B!!#2(B. $BG/NpITLd!"3XNrITLd(B $B!!#3(B. $B?H853NB$JJ}(B $B!!#4(B. $BCOJ}6PL3(B $B!$.$K!"LM@Gn;N$r?dA$7!"K\3X$N3X0LxM?A*9M0Q0w2q!J65(B $Bx#1#0L!K$K$h$j@507hDj$7$^$9!#LM@Gn;N9fxM?BP]T$O(B $B0J2$NDL$j$G$9!#(B $B!!#1(B. $B#4#0:P0Je$K$7$F!"3F3$K$*$$$F==J,$J8y@S$r;D$5$l6H(B $B!!3$HR2q$NH/E8$N$?$a$K4sM?$5$l$?J}!"3F6H3$K$*$$$F(B $B!!!J0eNE!"650i!";:6H!"4k6H!"85f$J$I!K(B $B!!3FETF;I\8)$K#3L0JFb!#(B $B!!#2(B. $B3XLdE*!"$"$k$$$OJ88%E*$K==J,$JB@S$N$"$kJ}!#(B $B!!#3(B. $BK\3X65x$N?dA$N$"$kJ}(B $B!!#4(B. $BK\3X$NH/E8$K==J,$JB@S$N$"$kJ}!J4sIU!"6(NO;Y1g$J$I!K(B $B+ABA$rLd$$$^$;$s$N$G!"1sN8$J$/$4O"Mm2$5$$!#(B $BO"MmJ}K!$O%a!%k$K$F$h$m$7$/$*4j$$CW$7$^$9!#(B * Yuko Kashiwazaki E-Mail:[EMAIL PROTECTED] Faculty Recruiting Department of IOND University URL:http://member.nifty.ne.jp/Iond_Univ/ * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
On Sun, 15 Aug 1999, Matthew Dillon wrote: :2) under "kern.emu.linux" :3) under "linux" : :I vote for 3. : :-- :Poul-Henning Kamp FreeBSD coreteam member :[EMAIL PROTECTED] "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! Ditto. Linux emulation is going to become increasingly important, burying deep would just make everyone's life more difficult. Well, it's also a module, so perhaps we should create the whole subtree for modules (as was already discussed several times..) Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
: :On Sun, 15 Aug 1999, Matthew Dillon wrote: : : :2) under "kern.emu.linux" : :3) under "linux" : : : :I vote for 3. : : : :-- : :Poul-Henning Kamp FreeBSD coreteam member : :[EMAIL PROTECTED] "Real hackers run -current on their laptop." : :FreeBSD -- It will take a long time before progress goes too far! : : Ditto. Linux emulation is going to become increasingly important, : burying deep would just make everyone's life more difficult. : :Well, it's also a module, so perhaps we should create the whole subtree :for modules (as was already discussed several times..) : :Andrzej Bialecki Yes, this is very true. But I think we are fooling ourselves if we believe linux emulation will not become 'standard' in the near future. Then we'll kick ourselves for giving the sysctl's convoluted names :-) -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
On Mon, 16 Aug 1999, Matthew Dillon wrote: : :On Sun, 15 Aug 1999, Matthew Dillon wrote: : : :2) under "kern.emu.linux" : :3) under "linux" : : : :I vote for 3. : : : :-- : :Poul-Henning Kamp FreeBSD coreteam member : :[EMAIL PROTECTED] "Real hackers run -current on their laptop." : :FreeBSD -- It will take a long time before progress goes too far! : : Ditto. Linux emulation is going to become increasingly important, : burying deep would just make everyone's life more difficult. : :Well, it's also a module, so perhaps we should create the whole subtree :for modules (as was already discussed several times..) : :Andrzej Bialecki Yes, this is very true. But I think we are fooling ourselves if we believe linux emulation will not become 'standard' in the near future. Then we'll kick ourselves for giving the sysctl's convoluted names :-) Yeah... Then, the next in line after "linux" are: ibcs2 and svr4 and whatever comes next. Can you live with them as main sysctl categories? Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
: :Yeah... Then, the next in line after "linux" are: ibcs2 and svr4 and :whatever comes next. Can you live with them as main sysctl categories? : :Andrzej Bialecki I think Solaris has a chance, but I doubt any other traditional vendor UNIXes do. So it comes down to Solaris and Linux for the most part. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and dd are a good combination for writing them. This would be true if the worm driver wasn't actually dead. You should at least check on these things before publically recommending obsolete mechanisms. :) In the world of CAM these days, cdrecord from the ports collection is the way to go. "dd" was also never a good way of writing CDs since the faster models may suffer from data starvation when you use dd, you want to use cdrecord and/or team from the ports collection to do this. And yes, I've burned probably thousands of CDs under FreeBSD at this point and do know what I'm talking about, should Brian wish to vigorously defend the indefensible again on these points. :-) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: apm problems.
Hi, My understanding on your problems is: 1. Standby by PM timer in BIOS setting fails with the system activity. 2. No new process can be started after resume. Is it correct? 1. My laptops also fails if the console or window is updating by the output from running commands. But standby on other unused console (ttyv1 or something), monitor blanks. Standby usually never stop disk activities. 2. Do you have `calcru: negative time' messages after resume? One of my laptops has this problem, doesn't restore the countdown register of i8254 on resume. After resume, my laptop is getting very slooow, takes 2 mins to shutdown... If your problem is the same as mine, hack in PAO (i8254_restore() in /sys/i386/apm/apm.c and /sys/i386/isa/clock.c) would be helpful for you. Another possibility is apmd configuration. Is it correctly configured? Please try to disable apmd to make it clear whether apmd causes your problem. Apm does not seem to be behaving correctly on my computer (running yesterday's CURRENT) Is this first time for you? Have you met the problems before or just recently? if more info is needed, just let me know what to do. Thanks =). I'd like to have your dmesg output. Are you using desktop PC, right? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
All of this would be true if your personal definition of "emulator" were the prevailing one, but that is unfortunately just not the case. :) When the average computing public thinks of an "emulator", they think of something like MAME or the SNES emulator. Even the more compute-minded folks tend to think of BOCHS or SIMOS when they hear the word "emulator" and I need only point to the majority of entries in /usr/ports/emulators in support of this. :-) In any case, my point is simply that we need to be careful in our use of terminology if we don't want to lend the majority the impression that our linux "emulation" code goes through the same sorts of gyrations that MAME does to run linux binaries. I do get questions at trade shows all the time about this, and I can state without reservation that none of the people asking about it share Marcel's definition of the term. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Cool, So can we have the manufacture and model of your cd-recorder ? 8) Browsing a little over at http://www.buy.com and noticed that they have quite a few Plextor cd recorders so I am wondering if anyone has any experience with Plextor cd recorders... Tnks! -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
On Mon, 16 Aug 1999, Jordan K. Hubbard wrote: Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and dd are a good combination for writing them. This would be true if the worm driver wasn't actually dead. You should at least check on these things before publically recommending obsolete mechanisms. :) Wormcontrol uses WORM ioctls, handled by both of the ATAPI drivers. In the world of CAM these days, cdrecord from the ports collection is the way to go. "dd" was also never a good way of writing CDs since the faster models may suffer from data starvation when you use dd, you want to use cdrecord and/or team from the ports collection to do this. But ATA and wcd are both not CAM. dd works just fine. You can solve data starvation by using a pipe of two (one to do all the reading, another to do all the writing with the small buffer size.) cdrecord is probably more obvious to most people. And yes, I've burned probably thousands of CDs under FreeBSD at this point and do know what I'm talking about, should Brian wish to vigorously defend the indefensible again on these points. :-) Your points are arguments to a different set of statements ;) - Jordan Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
And whats Whistle market capitilization since becoming part of IBM ? 8) On Mon, 16 Aug 1999, Tom Bartol wrote: I absolutely agree with Jordan on this point. I'm having an increasingly hard time keeping our lab running FreeBSD over Linux due to pressure from higher-ups who aren't in the technical trenches with me and who don't understand the very good technical reasons I have for running FreeBSD here. One constant sticking point is the linux compatibility module. The higher-ups see the word "emulator" and all manner of warning messages go off in their uninformed heads. In a previous e-mail on this or a related thread I saw the term: "Linux image activator" or something close to this pass by. I think this term gave me a much closer feeling to what I imagine is really going on the the "linuxulator" than the term "emulator" and all its baggage. So we could name it the "Linux image activator" or "Lin-Axe" or some such... I'd just like to have it described as running a program in "linux mode" In Linux mode, FreeBSD appears exactly a s alinux muchine would to a Linux program and the program can run un-modified. (Now that Red Hat has a market capitialisation of 5Billion$ there will be a lot more linux stuff available) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
On Mon, 16 Aug 1999, Amancio Hasty wrote: And whats Whistle market capitilization since becoming part of IBM ? 8) Sure, but the last time I heard a Whistle radio comercial, I heard no mention of FreeBSD. Last time I saw a mention of RedHat, it sure as hell included a mention of Linux. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
Well, okay. They are sort of hiding the fact that they are using FreeBSD and you will have to ask them why is FreeBSD is not more prominently advertised. Not too long ago I read a review on various internet appliances and Whistle listed their OS as BSD/UNIX. On the other hand, Juniper does have a nice web article on why they are using FreeBSD 8) And I have to kill this thread lets continue on -chat Cheers -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gnu tar upgrade?
The version of tar that comes with freebsd (v1.11.2 with local freebsd modifications) has a bug: if you attempt to copy large files ( 2GB) it will silently truncate the large file. To reproduce this bug, simply use tar cf - dir | (cd newlocation; tar xvpf -) where dir is a directory that contains a large file. There is a new version of gnu tar (v1.13) that has support for large files. I have tested this new version of tar on a recent snapshot of FreeBSD-STABLE (3.2-19990810), and it works fine with 2GB files. I also looked at the local modifications to the 1.11.2 version of tar, to understand how hard it would be to upgrade. FreeBSD has added the following behavior over the years: the --unlink option: tar 1.13 has equivalent functionality with --unlink-first the --norecurse option: tar 1.13 has equivalent functionality with --no-recursion the --bzip and --unbzip options: tar 1.13 has equivalent functionality with the --use-compress-program option the --fast-read option: tar 1.13 does not have equivalent functionality I looked at the implementation of fast-read, and it doesn't look too hard to adapt to the new version of tar. I could create patches if there is interest Alec To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes
"MI" == Mitsuru IWASAKI [EMAIL PROTECTED] writes: MI Hi, MI I got ASUS P2B M/B ATX case and assembled new box yesterday. With MI my patch, new box successfully transit into suspend state. There is MI no sounds from CPU fun, chassis fun and IDE HDD spin (powered down by MI BIOS setting, Power management setup - PM Timers - HDD Power Down: MI 1 Min.). The power led keeps flashing during suspending. MI Without the patch, suspending system is never successful (standby MI also), message `slept 00:00:00' comes up :-( MI The key release event seems prevent suspend, so some sort of delay MI mechanism would be necessary such as my patch. MI Now I'm wondering why your PC doesn't get quite. I suspect that MI hardware configuration different from yours (I have no SCSI HD on new MI box). Any suggestions? After a new cvsup I tried your patch again. Same result. Here is my dmesg output. It is about the same at boot, but the APM debug output when suspend is tried is completely different. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #9: Mon Aug 16 20:56:59 MET DST 1999 plm@muon:/var/arch/fbsd/src/sys/compile/PLM Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 268423168 (262132K bytes) avail memory = 257990656 (251944K bytes) Pentium Pro MTRR support enabled Probing for PnP devices: CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x1f5ceca5 Comp ID: PNPb02f [0x2fb0d041] Add hook "pcm resume handler" Add hook "pcm suspend handler" pcm1 (SB16pnp SB16 PnP sn 0x1f5ceca5) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f, Data 0xc00fdbd0 apm: Code entry 0x7770, Idling CPU disabled, Management enabled apm: CS_limit=0x, DS_limit=0x apm: Engaged control enabled apm: found APM BIOS v1.2, connected at v1.2 apm: Slow Idling CPU disabled Add hook "default suspend" Add hook "default resume" pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: Matrox model 0521 graphics accelerator irq 11 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 ata-pci0: Intel PIIX4 IDE controller at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: UHCI USB controller at device 4.2 on pci0 chip2: Intel 82371AB Power management controller at device 4.3 on pci0 ahc0: Adaptec 2910/15/20/30C SCSI adapter irq 9 at device 9.0 on pci0 ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs ed0: NE2000 PCI Ethernet (ProLAN) irq 10 at device 11.0 on pci0 ed0: address 00:40:95:00:57:83, type NE2000 (16 bit) isa0: ISA bus on motherboard fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio2 at port 0x3e8-0x3ef irq 4 on isa0 sio2: type 16550A sio3 at port 0x2e8-0x2ef irq 3 on isa0 sio3: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppb0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: Hewlett-Packard OfficeJet Series 700.4.00c MLC,PCL,PML lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: Maxtor 90680D4/PAS23B15 ATA-4 disk at ata0 as master ad0: 6485MB (13281408 sectors), 13176 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata0: slave: setting up UDMA2 mode on PIIX4 chip OK ad1: Maxtor 91000D8/SASX1B18 ATA-4 disk at ata0 as slave ad1: 9543MB (19545120 sectors), 19390 cyls, 16 heads, 63 S/T, 512 B/S ad1: piomode=4, dmamode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: ST39140A/841260 ATA-3 disk at ata1 as master ad2: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 0 depth queue, DMA mode Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0
Re: recent apm changes
Followup: I decided to upgrade my P2B BIOS version. I had 1005, went to 1010. This made a difference! Now suspend works. However still the disks keep spinning until they reach their BIOS timeout. In Linux Windows, there is some hook when going to suspend mode that spins down the (IDE) disks. This is nice, since it is well possible that you go to suspend but do not set a disk spindown timeout. Weird that 1005 did not, but 1010 does suspend with FreeBSD ( your patch, I didn't try without it again), while 1005 did work with Linux Windows. That's why I didn't think of upgrading before. I'll report what happens with the original (non patched) kernel later. "MI" == Mitsuru IWASAKI [EMAIL PROTECTED] writes: MI Hi, MI I got ASUS P2B M/B ATX case and assembled new box yesterday. With MI my patch, new box successfully transit into suspend state. There is MI no sounds from CPU fun, chassis fun and IDE HDD spin (powered down by MI BIOS setting, Power management setup - PM Timers - HDD Power Down: MI 1 Min.). The power led keeps flashing during suspending. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
Okay, I will bite. What would you call the linux emulator to convey the proper meaning to the suits types? -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gnu tar upgrade?
I looked at the implementation of fast-read, and it doesn't look too hard to adapt to the new version of tar. I could create patches if there is interest There is. Upgrading tar is something I've been wanting to do for over a year. Anything to speed me along would be helpful. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
So can we have the manufacture and model of your cd-recorder ? 8) Yes, it's a "Smart and Friendly" (gah!) "Rocket Recorder" - it does 8X CDR, 6X CDRW and 24X CD. I like it. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gnu tar upgrade?
Alec Wolman [EMAIL PROTECTED] wrote: The version of tar that comes with freebsd (v1.11.2 with local freebsd modifications) has a bug: if you attempt to copy large files ( 2GB) it will silently truncate the large file. ... There is a new version of gnu tar (v1.13) that has support for large files. FreeBSD has added the following behavior over the years: the --unlink option: the --norecurse option: the --bzip and --unbzip options: the --fast-read option: A check through the CVS logs reveals lots of other changes and enhancements such as: - the builtin regex() code has been replaced with -lgnuregex - 21-bit minor numbers (same as v1.13) - Support for hard-links to files with long names - FreeBSD-specific knowledge of potential names/locations of rsh(1) - support 8-bit filenames - assorted minor bugfixes and compiler-quietenings If we do import GNU tar 1.13 (which I think is probably a good idea), we need to make sure all the `invisible' fixes go in (if they're not there already), as well as the additional options. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
I take it that the absence of the interface means your cd-recoder uses scsi. Tnks A Lot! So can we have the manufacture and model of your cd-recorder ? 8) Yes, it's a "Smart and Friendly" (gah!) "Rocket Recorder" - it does 8X CDR, 6X CDRW and 24X CD. I like it. :) - Jordan -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
Others have pretty much already listed my preferences: "Linux compatibility" "Linux ABI support" "Linux binary compatibility" or any of the other obvious permutations thereof... - Jordan Okay, I will bite. What would you call the linux emulator to convey the proper meaning to the suits types? -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
Yes, this is very true. But I think we are fooling ourselves if we believe linux emulation will not become 'standard' in the near future. Then we'll kick ourselves for giving the sysctl's convoluted names :-) Yeah... Then, the next in line after "linux" are: ibcs2 and svr4 and whatever comes next. Can you live with them as main sysctl categories? Adding anything at the top level would be a terrible mistake. Given that "ABI" is a bit obscure, kern.compat is the only sensible choice. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
In my case, you should always assume SCSI unless expressly indicated otherwise. I hate ATAPI devices, no insult to Soren's fine work intended. :) - Jordan I take it that the absence of the interface means your cd-recoder uses scsi. Tnks A Lot! So can we have the manufacture and model of your cd-recorder ? 8) Yes, it's a "Smart and Friendly" (gah!) "Rocket Recorder" - it does 8X CDR, 6X CDRW and 24X CD. I like it. :) - Jordan -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
Mike Smith wrote: Yes, this is very true. But I think we are fooling ourselves if we believe linux emulation will not become 'standard' in the near future. Then we'll kick ourselves for giving the sysctl's convoluted names :-) Yeah... Then, the next in line after "linux" are: ibcs2 and svr4 and whatever comes next. Can you live with them as main sysctl categories? Adding anything at the top level would be a terrible mistake. Given that "ABI" is a bit obscure, kern.compat is the only sensible choice. kern.modules seems to be slightly more general in that you can have kern.modules.xxx where xxx is anything under /modules that needs/wants to some tuning via sysctl. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
Okay, I will bite. What would you call the linux emulator to convey the proper meaning to the suits types? You don't. You say "FreeBSD has Linux binary compatibility", or "FreeBSD will run (most) Linux applications out of the box". -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
Given that "ABI" is a bit obscure, kern.compat is the only sensible choice. I think that is too obscure considering the exposure this will get. What "exposure"? It's a backend to a tuning interface for our ABI compatibility... It doesn't really matter much what we feel about it, linux will be a native and 100% normal binary format for us, if we try to marginalize it we loose in perception. I don't see how organising the sysctl namespace in a tidy fashion constitutes "marginalising" anything. We have things to make us posix compatible at the top level already, I don't see why the linux stuff should live under the top level too. One wrong... And as father of sysctl, I think this discussion needs to come to a close rather than waste more bandwidth, so unless Mike can convince us why "Adding anything at the top level would be a terrible mistake" I think the conclusion is "linux.*" For the same reason that fattening any top-level namespace is a bad idea. I mean, why not just put all the Linux libraries in /lib where they expect to be? From the perspective of an integrated namespace, we've already made the wrong moves insofar as vm.* should be kern.vm.*, vfs.* should be kern.vfs.*, etc. Either the entire kernel namespace should have a presumed leading kern. (and the existing kern.* nodes need to move) or we should relocate stuff to reflect a more ubuquitous naming arrangement. (btw, you're not the "father" of sysctl. I might go for "perpetrator" or "culprit" though.) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
On Mon, 16 Aug 1999, Mike Smith wrote: Yes, this is very true. But I think we are fooling ourselves if we believe linux emulation will not become 'standard' in the near future. Then we'll kick ourselves for giving the sysctl's convoluted names :-) Yeah... Then, the next in line after "linux" are: ibcs2 and svr4 and whatever comes next. Can you live with them as main sysctl categories? Adding anything at the top level would be a terrible mistake. Given that "ABI" is a bit obscure, kern.compat is the only sensible choice. One one hand you're right (it is a compatibility stub) but OTOH it is also a kernel module... ;-) Perhaps modules like this will want to have their stuff in BOTH places, i.e. in kernel.compat and in kernel.modules, depending what the given sysctl does. Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
Given that "ABI" is a bit obscure, kern.compat is the only sensible choice. One one hand you're right (it is a compatibility stub) but OTOH it is also a kernel module... ;-) Perhaps modules like this will want to have their stuff in BOTH places, i.e. in kernel.compat and in kernel.modules, depending what the given sysctl does. Tuning parameters should be organised by function, not by implementation. (Otherwise, think for a moment about a parameter that's used in more than one place...) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
On Mon, 16 Aug 1999, Jordan K. Hubbard wrote: Wormcontrol uses WORM ioctls, handled by both of the ATAPI drivers. Utterly irrelevant, not that you seem to let it stop you. You bringing up worm(4) was entirely irrelevant. You implied that wormcontrol does not work because the worm old-SCSI driver is gone. Wormcontrol is simply a utility that allows you to issue WORM ioctls to a device. See /usr/src/share/examples/atapi (yes, in -CURRENT too) for exactly how wrong you are about wormcontrol "not working." But ATA and wcd are both not CAM. dd works just fine. You can solve data See above. dd's unsuitableness for writing CDs has nothing whatsoever to do with CAM. Yes, why would it? I simply used your paragraph style: make one statement, then another that is completely unrelated. Oh wait, you mean your writing style utilizing the exact same strategy was _correct_? Give me a break. Your holier-than-thou attitude is getting old, especially when you use things that are entirely unrelated to try to back up the point your never even had. Your points are arguments to a different set of statements ;) Nope. As usual, you're simply trying to argue your way out of being wrong. Sorry, but being right just isn't the same as being forceful. Perhaps you'll learn that for yourself, given enough time. :) You didn't even reply anything close to what he wanted, and now you're accusing me of the same? What crawled up your pants and died, leaving you chafed and miserable? You see, when you answer someone, try to answer what they asked and they'll appreciate it. - Jordan Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
On Mon, 16 Aug 1999, Jordan K. Hubbard wrote: I kinda like the idea of a top-level compat category; it will keep the top level uncluttered when sysv and iBCS compatibility start requiring their own knobs, and if you put linux at the top level this will later be used as justification for putting all the other "compat" stuff up there too. I think it's a slippery slope. - Jordan This is the most convincing argument so far. It's got my vote. One caveat: let's _please_ not use capitalization in the MIB tree as much as possible. Just like the ports, it makes things easier on everyone if we use lower-case (compat.linux, compat.ibcs2, compat.svr4.) Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
Oh Guys, I simply am trying to get information on which cd-recorder works well on FreeBSD. It will help to avoid confusion and postings if there was a cd-record handbook section explaining all the gory details. Peace -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
In case anyone cares I'd like to put in a vote for compat.linux. From the design standpoint this balances the needs of prominence and clean top level name space nicely. Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
In case anyone cares I'd like to put in a vote for compat.linux. From the design standpoint this balances the needs of prominence and clean top level name space nicely. And in case it's not clear from the exposition in my message to Poul, I would find this most agreeable too. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
I agree with this as well. "Linux compatibility" "Linux ABI support" "Linux binary compatibility" The suggested "linux mode", has a nice non-technical simple ring to it. If we called it this, the non-educated might not come away with the wrong idea. Management(tm) may not understand "ABI" and the exact use of "binary". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
have quite a few Plextor cd recorders so I am wondering if anyone has any experience with Plextor cd recorders... Excellent experience. I have both their 4x and 8x [SCSI] burners. If you check the various CDROM burner FAQs around, you will also find that Plextors perform better than others in digital audio extraction (if that matters to you). Cdrecord and Plextor just work. :-) Also, Jordan prescribes their CDROM drives. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dropping connections without RST
Brian W. Buchanan writes:
Can anyone think of any reason why this feature should
not be implemented?
I like that idea... net.inet.{tcp,udp}.drop_in_vain ?
Why do we need a sysctl knob for this when it can be easily accomplished
with IPFW?
Not that easily.. how are you going to make ipfw dynamically know
which ports have listeners and which don't?
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Existance of /var/backups for periodic/daily
The 200-220 periodic files under daily expect that the directory /var/backups exist when they run to back up various files. If you delete this directory, the "cp" commands will error. There seems to be two ways to fix the files. 1. Add a "if [ ! -d $bak ] ; then exit fi" to the top of the files, or 2. Add a "mkdir -p $bak" to the top. Do others consider this an error, and if so which is the preferred fix? Thanks, -- Stephen J. Roznowski([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can I obtain 'int-cvs-cur' by CTM ?
Last CTM delta in ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur is 'int-cvs-cur.0114.gz' from May 15 1999. There definitely was commits in International depository after 'may 15'. N.Dudorov To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Existance of /var/backups for periodic/daily
1. Add a "if [ ! -d $bak ] ; then exit fi" to the top of the files, or 2. Add a "mkdir -p $bak" to the top. Do others consider this an error, and if so which is the preferred fix? Both. (2) followed by (1), possible logging a warning. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dropping connections without RST
Geoff Rehmet writes:
After the discussions regarding the "log_in_vain"
sysctls, I was thinking about a feature I would
like to implement:
Instead of sending a RST (for TCP) or Port Unreachable
(for UDP) where the box is not listening on a socket,
I would like to implement a sysctl, which disables the
sending of the RST or the Port unreachable. This is
basically for public servers (like DNS servers), which
I want to turn into black holes on ports where they
are not listening. (This confuses things if someone
strobes the machines, and also makes life a little
more difficult for anyone who tries to portscan them.)
In default configuration, everything would behave as per
normal, and you would have to set a sysctl MIB before the
behaviour that I have described is displayed.
Can anyone think of any reason why this feature should
not be implemented?
I like that idea... net.inet.{tcp,udp}.drop_in_vain ?
I kinda like the idea of this, but can't that really just
be done easily with a few ipfw rules, the last two being
the important ones:
for port in "22 53" ; do
ipfw add allow udp from any to ${myip} ${port}
ipfw add allow udp from ${myip} ${port} to any
ipfw add allow tcp from any to ${myip} ${port}
ipfw add allow tcp from ${myip} ${port} to any
done
ipfw add deny udp from any to ${myip}
ipfw add deny tcp from any to ${myip}
Why should we special case this?
--
Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Dropping connections without RST
Brian W. Buchanan writes:
Can anyone think of any reason why this feature should
not be implemented?
I like that idea... net.inet.{tcp,udp}.drop_in_vain ?
Why do we need a sysctl knob for this when it can be easily accomplished
with IPFW?
Not that easily.. how are you going to make ipfw dynamically know
which ports have listeners and which don't?
What you going to do about wild card listners:
udp0 0 *.**.*
--
Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [Fwd: [URGENT] CVS problems]
According to Mark Jaffe: CVS is issuing an "out of memory" message on attempting to checkin a 12MB file. What can I do? There is 300M of swap on the machine, it is running FreeBSD 2.2.8, and CVS says: "Concurrent Versions System (CVS) 1.9.26 (client/server)" I'll post this to the lists, too. Check the limits for the user running the command (datasize stacksize), both locally and remotely. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: yet more TP 600E fun...
I modified the biosdisk.c code as follows
(first part of function)
for (unit=0;unitnbdinfo;unit++)
if (bdinfo[unit].bd_unit == initial_bootinfo-bi_bios_dev)
break;
if ((unit == nbdinfo ) (nbdinfo MAXBDDEV) ) {
unit=initial_bootinfo-bi_bios_dev;
bdinfo[nbdinfo].bd_unit=unit;
bdinfo[nbdinfo].bd_flags=(unit 0x80) ? BD_FLOPPY : 0;
printf("Probiobing for bios disk 0x%02x\n", unit);
/* I did that to make sure my code was being run*/
if (!bd_int13probe(bdinfo[nbdinfo]))
return 0;
printf ("BIOS drive %c is disk%d\n", ...);
nbdinfo++;
}
return 0;
} /*end of function */
With these mods it will not find the "0x8b" device, event though the "probing
got bios disk..." does indeed print.
Suggestions?
--
David Cross | email: [EMAIL PROTECTED]
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself. | WinNT:Linux::Linux:FreeBSD
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Can I obtain 'int-cvs-cur' by CTM ?
On Tue, Aug 17, 1999 at 12:13:33AM -0400, Chuck Robey wrote: On Tue, 17 Aug 1999 [EMAIL PROTECTED] wrote: Last CTM delta in ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur is 'int-cvs-cur.0114.gz' from May 15 1999. There isn't any "int-cvs-cur", so are you referring to maybe the And what is (or was earlier) at the URL I post here ? International Crypto Repository run by Mark Murray out of SA? I refer to the "CTM interface" to "International Crypto Repository run by Mark Murray...". (More precisely about "ftp-ing" CTM deltas from some servers - f.e. 'ctm.freebsd.org'). I can't ftp CTM deltas from internat.freebsd.org directly - there are some problems to connect from Siberia to SA ;-) N.Dudorov If not, then please try again, because you've lost me, and I fix ctm stuff (so I should know your answer). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dropping connections without RST
In message [EMAIL PROTECTED] Archie Cobbs writes: : Not that easily.. how are you going to make ipfw dynamically know : which ports have listeners and which don't? By filtering all RST packets? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can I obtain 'int-cvs-cur' by CTM ?
Last CTM delta in ftp://ctm.freebsd.org/pub/FreeBSD/development/CTM-international/int-cvs-cur is 'int-cvs-cur.0114.gz' from May 15 1999. There definitely was commits in International depository after 'may 15'. Send me the address you want them to go to and I'll add you. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q: Extending the sysctl MIB for Linuxulator variables
* Doug ([EMAIL PROTECTED]) [990817 03:40]: In case anyone cares I'd like to put in a vote for compat.linux. From the design standpoint this balances the needs of prominence and clean top level name space nicely. Count me as another in favor of Mike's explanation. Like Mike said, there were a few mistakes already at the top, and IMHO linux ABI stuff doesn't justify a top-level assignment since in fact it's a remapping of Linux calls to FreeBSD equivalent calls, not a true implementation of Linux. So compat.* sounds way more sensible to shim- like implementations. Just my 0.02 euro's. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai Network/Security SpecialistBSD: Technical excellence at its best Take thy beak from out my heart and take thy form from off my door! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dropping connections without RST
On 17-Aug-99 Warner Losh wrote: : Not that easily.. how are you going to make ipfw dynamically know : which ports have listeners and which don't? By filtering all RST packets? The defeats the purpose of having the computer not generate them in the first place.. Well not totally I suppose, but at least part of the advantage of dropping them completely would be that the machine wouldn't spend any time doing it at all... --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum PGP signature
Re: Dropping connections without RST
Rodney W. Grimes writes : Now what would a box with so much security concern such that it needed this knob be doing running an ftp session though your point is valid and acceptable for low security boxes. And I can see the real benifit that having this knob for those boxes would be, since it would mean not having to spend the care and attention to create a proper firewall rule set. The idea is okay in the general since, this is an easy knob to add, it would increase the security of some boxes, and not require great configuration pains of writting ipfw rules. IMHO, this know would give some folks a false since of security, but not so much that I would argue about keeping it out. I never intended this idea as a replacement for ipfw, but rather as a simple setup, which can be done to make a SMALL improvement in security, and just make the lives of inquisitive or nasty people a little harder. Maybe I will eventually decide I want ipfw on some of the boxes concerned, but that is trickier on machines like public ftp servers. Also, the machines concerned already sit behind a packet filtering firewall setup, which is being slated for a $10 upgrade over the next year anyhow, so this is not for machines that act as any primary line of defense. I'm also making the assumption that the machines concerned are being looked after by competent admins. (A lot to assume sometimes.) It seems, though, that there are no serious objections to this kind of feature. I was thinking of calling it net.inet.tcp.blackhole, and net.inet.udp.blackhole This is an ACK. I like those names, the idea is okay given that the documentation for it reflects what has been discussed here in this thread so folks can understand this is a very simple security measure. And it works just like a blackhole route does... if no more specfic route exists we send the packet to a bit bucket, now someone want to make the routing code under ``port routes'' :-) :-)... rather than "drop_in_vain". Any advances on that. I never quite cottoned onto the "in vain" bit - it seems a bit obscure, personally, I prefer the idea of the machine behaving like a black hole - refused connections no longer "reflect" off it. :-) Perhaps one more word in the mib name to reflect that it applies to sockets without listners is all I can think of, but not sure what to add to the name to make this clear. mib's tend to be breif anyway. -- Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can I obtain 'int-cvs-cur' by CTM ?
There isn't any "int-cvs-cur", so are you referring to maybe the International Crypto Repository run by Mark Murray out of SA? Yes, he is :-). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
