Re: Pentium and NO_F00F_HACK = kernel panic
On Thu, 2002-02-28 at 20:57, Johann Frisch wrote: F00F hack works around the CPU bug; the NO_F00F_HACK option disables the workaround.) I knew that and I have no problem using this option. I am just curious if this kernel behaviour is intented or not? No, it shouldn't panic. You should have it on as it wouldn't save you very much space.. Could you get a stack trace (enable crash dumps etc..) and file a PR about it? :) --- 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: usb printer support broken?
Ceri wrote: On Wed, Feb 27, 2002 at 10:14:28PM -0600, Mike Meyer wrote: On a system cvsupped three days ago, trying to print to the USB system reliably generates a page fault panic on an otherwise reliable system. I know there was some problems with renaming USB structures in the week before that. Could this be related? Anyone else seeing such panics, or do I need to install a debugging version of the kernel and chase it down. I'm getting them too. I'd like to see the changes backed out for the time being. Have you tried his next patch set at http://www.josef-k.net/misc/ You store it in /usr/src and gunzip it and patch the_patch. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: usb printer support broken?
On Thu, Feb 28, 2002 at 03:41:01AM -0800, Kent Stewart wrote: Ceri wrote: On Wed, Feb 27, 2002 at 10:14:28PM -0600, Mike Meyer wrote: On a system cvsupped three days ago, trying to print to the USB system reliably generates a page fault panic on an otherwise reliable system. I know there was some problems with renaming USB structures in the week before that. Could this be related? Anyone else seeing such panics, or do I need to install a debugging version of the kernel and chase it down. I'm getting them too. I'd like to see the changes backed out for the time being. Have you tried his next patch set at http://www.josef-k.net/misc/ No, I haven't, but -stable is broken and I'd rather see the changes that have been made backed out. Once that is done then people willing to test patches can try them (and I am one of those willing to test patches; I just don't want to see this breakage in -stable). Ceri -- keep a mild groove on To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: usb printer support broken?
* Kent Stewart [EMAIL PROTECTED] [020228 04:29]: Ceri wrote: On Wed, Feb 27, 2002 at 10:14:28PM -0600, Mike Meyer wrote: On a system cvsupped three days ago, trying to print to the USB system reliably generates a page fault panic on an otherwise reliable system. I know there was some problems with renaming USB structures in the week before that. Could this be related? Anyone else seeing such panics, or do I need to install a debugging version of the kernel and chase it down. I'm getting them too. I'd like to see the changes backed out for the time being. Have you tried his next patch set at http://www.josef-k.net/misc/ You store it in /usr/src and gunzip it and patch the_patch. I'm still getting the core dumps accessing uplt that I got a few weeks back. That's on latest STABLE, with or without Joes patches. With the patchset, the kernel hung while initialising the card. AFAICT, the lpt coredump problem is related to the STABLE changes only, so maybe a rollback would be feasible. I was having trouble with ulpt and STABLE before any of the recent commits, so I'm more than happy to test patches, whether or not they're in the tree. Not being more than an enthusiastic user, it's not my call, is it? -- Pure drivel tends to drive ordinary drivel off the TV screen. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: running securelevel 2 and X
* Randy Kunkee [EMAIL PROTECTED] [020228 01:17]: I just upgraded to 4.5-stable and it reset my securelevel to 2 and enabled. Of course, X would not come up, x86OpenConsole failed with this KDENABIO error. The documentation I found on this suggests two solutions, both of which advise using XDM. First, running XDM from /etc/ttys, did not work, producing the same error. The second one, running as a full daemon from /usr/local/etc/rc.d does work, as long as I add a short sleep to give XDM time to start before securelevel is changed by init after finishing the startup scripts. The downside of this is that if I ever abort XDM for some reason, I won't be able to restart it, nor will I be able to start X directly (and playing with XDM is enough fun in itself anyway). No, the idea behind running XDM is that if that opens /dev/io before the securelevel is raised, it will be allowed to keep it open. Since xdm only starts once, you don't have trouble getting into an X session once you log out like you would using startx. Perhaps I have a conflict of interest. I want to run X and be secure. Is running X such a big gaping security hole that I'm left with my current solution (to restart X, I must reboot!)? In a word, yes. X needed direct access to /dev/io last time I looked. Is there no reasonable change that could be made to the OS to grant access to let the X server do its thing (ie. allow running startx) without disarming the securelevel feature completely? There was a patch out about a year ago to use the 'aperture driver', which basically opens a hole for X to squirt through. Search the lists, not sure if it would apply to STABLE cleanly. -- Be braver -- you can't cross a chasm in two small jumps. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: usb printer support broken?
Morgan Davis [EMAIL PROTECTED] types: With all the trouble people are having with this, perhaps the previous (working) USB/ulpt code should be put back in, and leave the newer code for testing under -current until it is truly ready for -stable. It would certainly get my agreement. I'd be much more willing to work on the problem on my -current box, which doesn't disturb users if it crashes, than on any of my -stable boxes, which also need to print. Thanx, mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Mini-HEADS UP: Minor rc.firewall{,6} Change
I just made a few _minor_ changes to the rc.firewall{,6} scripts. The
vast majority of users will not be affected. However, since a few may
be, and this is a security issue with the potential to cause some
subtle breakage, I felt a mini-HEADS UP was in order. (For the very
security conscious and paranoid, note that this change can only
fail-safe if people apply it blindly. You'll be more secure, but
it may break stuff.)
If you do not use firewalling or rc.firewall{,6} at all (that is, you
do not have 'firewall_enable=YES' and/or
'ipv6_firewall_enable=YES') or if you use custom rc.firewall{,6}
scripts, you are not affected. Two groups of people who use the
provided firewall scripts are affected:
1) Those who put a rules file in the 'firewall_type' variable, or
2) Those who put a non-existent type in the 'firewall_type' variable.
In both cases, you will no longer get the rules,
100 pass all from any to any via lo0
200 deny all from any to 127.0.0.0/8
300 deny ip from 127.0.0.0/8 to any
In rc.firewall, and,
100 pass all from any to any via lo0
200 pass ipv6-icmp from :: to ff02::/16
300 pass ipv6-icmp from fe80::/10 to fe80::/10
400 pass ipv6-icmp from fe80::/10 to ff02::/16
In rc.firewall6 added to your firewall by the system scripts.
If you are in group (1), you should add whatever rules like these
_you_ want for _your_ site into your rule file. If you are in group
(2), use of 'firewall_type=closed' (which now works as advertised)
will give you the same effect as your previous configuration.
The motivation for the change was mainly for the people in group
(1). Up until now, those rules were added _unconditionally_ by the
rc.network{,6} scripts. For people who want to define their own
rulesets outside of the simple ones provided in the rc.firewall{,6}
scripts, the system should make NO assumptions about their site's
policy and be adding rules.
--
Crist J. Clark | [EMAIL PROTECTED]
| [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Re: usb printer support broken?
On Thu, Feb 28, 2002 at 08:16:29AM -0600, Mike Meyer wrote: Morgan Davis [EMAIL PROTECTED] types: With all the trouble people are having with this, perhaps the previous (working) USB/ulpt code should be put back in, and leave the newer code for testing under -current until it is truly ready for -stable. It would certainly get my agreement. I'd be much more willing to work on the problem on my -current box, which doesn't disturb users if it crashes, than on any of my -stable boxes, which also need to print. Good. Then consider yourself co-opted to help on -current. I've just backed out the ulpt.c patch on -stable. I'll reroll the usb patch on my web site later today to take this into account. Joe msg41967/pgp0.pgp Description: PGP signature
Problems with package repository
FYI, Where does one report problems with the package repository? On ftp.freebsd.org and ftp6.freebsd.org, there are a number of truncated packages (incomplete package .tgz files). I have a cron job that downloads selected new packages, and it's noticing that a number of new freebsd packages are MUCH smaller than before; spot-checking some from ftp.freebsd.org shows that these files are obviously truncated (and are thus unusable). Here's a partial list output from my cron job; the number before (remote) is the size on ftp.freebsd.org, and the number before (local) is the old size (the size of an older copy of the file on my local disk): Size diff: dist/All/AbiWord-0.9.6.1_1.tgz: 8704 (remote) vs 7621132 (local) Size diff: dist/All/ddd-3.3.tgz: 16896 (remote) vs 2495234 (local) Size diff: dist/All/dictd-database-20010416_1.tgz: 80384 (remote) vs 29214892 (local) Size diff: dist/All/emacs-21.1_5.tgz: 39424 (remote) vs 15567029 (local) Size diff: dist/All/gcc30-3.0.2.tgz: 37376 (remote) vs 11245857 (local) Size diff: dist/All/gimp-1.2.2_1,1.tgz: 6656 (remote) vs 7809660 (local) Size diff: dist/All/lesstif-0.91.8.tgz: 80384 (remote) vs 2525874 (local) Size diff: dist/All/qt-2.3.1_1.tgz: 8704 (remote) vs 9869728 (local) Size diff: dist/All/qt-static-2.3.1_1.tgz: 27136 (remote) vs 7489599 (local) Size diff: dist/All/teTeX-1.0.7.tgz: 18944 (remote) vs 38717508 (local) As much as I'd love to think that gcc and emacs can each be compressed to under 40KB, it's wishful thinking. ;-( For that matter, what happened to all of the kde and gnome packages (the main ones are missing)? Thanks, -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Fwd: Re: ifconfig aliases
Title: Fwd: Re: ifconfig aliases Date: Thu, 28 Feb 2002 11:14:45 -0500 To: [EMAIL PROTECTED] From: David A. Koran [EMAIL PROTECTED] Subject: Re: ifconfig aliases Cc: Bcc: X-Attachments: On Wed, Feb 27, 2002 at 07:48:11PM -0800, Michael Sierchio wrote: Crist J. Clark wrote: ifconfig_fxp0=inet AAA.BBB.CCC.190 netmask 255.255.255.128 ifconfig_fxp0_alias0=inet AAA. BBB.DDD.209 netmask 255.255.255.248 ifconfig_fxp0_alias1=inet AAA. BBB.DDD.210 netmask 255.255.255.248 ifconfig_fxp0_alias2=inet AAA. BBB.DDD.211 netmask 255.255.255.248 ifconfig_fxp0_alias3=inet AAA. BBB.DDD.212 netmask 255.255.255.248 ifconfig_fxp0_alias4=inet AAA. BBB.DDD.213 netmask 255.255.255.248 ifconfig_fxp0_alias5=inet AAA. BBB.DDD.214 netmask 255.255.255.248 This was never legal. It has always been a misconfiguration. However, depending on what you were doing, it may still have worked in spite of not making any sense. Care to expand a little bit? Looking at this more... it's a little weird. This machine has all of the addresses on this AAA.BBB.DDD.208/29 subnet? If you are using this as I imagine you are, perhaps putting them on the loopback device would be better. The scenario is as such. My ISP gives each machine you lease an IP address on the network AAA.BBB.CCC.YYY. For extra IPs for any of the machines you lease, they give you a block on AAA. BBB.DDD.ZZZ. The mask for my block of extra IPs was 255.255.255.248. (I've also done this config on ed0 and xl0 devices besides the fxp0). And as I mentioned in my previous response, this configuration has worked for a number of years, of which it just stopped working yesterday when I brought this topic up. All the aliased addresses are on the /29 but the base address is on another subnet entirely, go fig. The most obvious question that arises when you want to reach another system on the same subnet as the aliases. Which address should be the source? Actually I can HTTP, SSH, and any other TCP/IP protocol to get to another box (another FreeBSD with a similar config, aliases and all) via any of those addresses on that interface. Depending on how the code works, (1) you might get predictable behavior (it's always the first alias), (2) unpredictable behavior (it might be any one of them), or (3) broken behavior (it doesn't work at all or only works sometimes). It looks like you are seeing (3) at the moment. I'm betting it was broken behaviour that was mysteriously fixed.. and thus, I had to clean my config. (BTW, the NAT and Firewall instructions at FreeBSDDiary.org also list this way of aliasing interfaces, so I'm to wonder where the bad info may have started... maybe a kludge that worked for ages...) -- Crist J. Clark | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/ | [EMAIL PROTECTED] -- David A. Koran ([EMAIL PROTECTED]) - http://www.solo.net/~dak/ PGP Key ID: 0x8AC39F65 -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT/CS/SS d- s+: a- C+++$ UBLHSX$ P+++$ L- E--- W+++ N- o-- K-? w--- O- M+++$ V-- PS++ PE- Y+++ PGP t--@ 5 X+ R- tv b+ DI D G e*+++ h++ r y+ --END GEEK CODE BLOCK-- -- David A. Koran ([EMAIL PROTECTED]) - http://www.solo.net/~dak/ PGP Key ID: 0x8AC39F65 -BEGIN GEEK CODE BLOCK- Version: 3.1 GIT/CS/SS d- s+: a- C+++$ UBLHSX$ P+++$ L- E--- W+++ N- o-- K-? w--- O- M+++$ V-- PS++ PE- Y+++ PGP t--@ 5 X+ R- tv b+ DI D G e*+++ h++ r y+ --END GEEK CODE BLOCK--
Re: Galeon port configure error
On Thu, 28 Feb 2002, Sumanth Peddamatham wrote: hi joe, what should my PATH_SEPARATOR be set to? i don't think i have it set. when i: set PATH_SEPARATOR : You would need to setenv PATH_SEPARATOR. In any event, Stan didn't have PATH_SEPARATOR set, and the configure is failing as if he had it set to ';'. As soon as he did a make PATH_SEPARATOR=':' it worked. I'm baffled as to why the configure test is setting it to ';'. Joe it still fails to compile. sumanth p. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
hang when booting from 4.5R boot floppies
hi i tried to install 4.5R using boot flopies. the machine hangs always when it tries to detect the HP CD-Writer 9300. i tried to attach the cd-writer as a slave on the first ide channel (like it was when running linux / win98). after that i moved the cd writer the second ide channel (master, slave) where the cdrom is. then i removed the cdrom so that the cd writer is the only device on the second ide channel. but nothing helped the machine hangs. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
gnomecontrolcenter won't build
I'm at 4.5-STABLE (as of late last week), and my existing ports have all been upgraded via portupgrade -a, or at least as many as can be upgraded without upgrading sysutils/gnomecontrolcenter This is what I get in the build just before it borks: file-types-capplet-dialogs.c: In function `populate_default_applications_list': file-types-capplet-dialogs.c:225: warning: implicit declaration of function `gnome_vfs_application_is_user_owned_application' file-types-capplet-dialogs.c: In function `add_or_update_application': file-types-capplet-dialogs.c:1110: structure has no member named `expects_uris' file-types-capplet-dialogs.c:1112: structure has no member named `supported_uri_schemes' file-types-capplet-dialogs.c: In function `handle_invalid_application_input': file-types-capplet-dialogs.c:1198: warning: implicit declaration of function `gnome_vfs_is_executable_command_string' file-types-capplet-dialogs.c: In function `run_edit_or_new_application_dialog': file-types-capplet-dialogs.c:1311: structure has no member named `expects_uris' *** Error code 1 After this, it just dies. I'm at a loss, anyone have any suggestions? Aaron Mildenstein UNIX Systems Administrator SME Hosting, NTT/Verio __ Do not meddle in the affairs of Dragons, for you are crunchy and taste good with ketchup. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
