Re: Kernel Dump
On Mon, 8 Mar 2004, Doug White wrote: > null pointer offset deref. > > thats not too unsuprising. Can you follow the instructions in the handbook > to get a crashdump and use gdb to get a backtrace? There is a backtrace and more detail in another message I posted to the list within the last few hours (subject is "-STABLE panic (usually) in vm_fault") I still have the dump laying around so if you'd like me to pinpoint some of the callpoints in the traceback, let me know (but again, this has been cvsupped in the last 48 hours or so so the line numbers should be fairly close). - Forrest W. Christian ([EMAIL PROTECTED]) AC7DE -- The Innovation Machine Ltd. P.O. Box 5749 http://www.imach.com/Helena, MT 59604 Home of PacketFlux Technologies and BackupDNS.com (406)-449-3345 -- Protect your personal freedoms - visit http://www.lp.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bug-fixing previous -RELEASE, was Re: speaking of 3.4...
Hmm, this brings up another interesting question. First, to put this in context: Jordan K. Hubbard wrote: > Actually, the -missioncritical branch is sort of provided for > now as a function of -previousstable. There are plenty of people still > running 2.2.x, for example, and you even still occasionally see commits > to the 2.2.x branch. And, Colin wrote: > My point is, if a new release every quarter scares you, upgrade > once/year (except bugfixes/security patches) and get on with your life. > I used 3.0 for several months and life was good, and it still runs on > one of my machines. I upgraded this one for several reasons that were > specific to me, your requirements will vary. Ok, so, let's assume I JUST want to incorporate bugfixes into the -RELEASE (be it 3.x or whatever) that I have on a particular machine. How would I go about doing this? I have machines all the way from 2.2.2-RELEASE through 3.3-RELEASE, and even one I track -STABLE on (for both development of a PicoBSD-based "product" I am doing and also to keep the OS up to date). It would be nice to leave the 3.x machines "alone" except for bugfixes. The 2.2.2-RELEASE machine has been ignored for a LONG time as it would be a pain to upgrade/rebuild. I plan on replacing it this month. - Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ -- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
edquota problem
I'm not sure exactly what list this should really be on. Please enlighten me for next time. I just got nailed by an "implementation detail" in edquota. Specifically the code which determines whether the parameter is a username or a range of uids only checks for a) whether the first character of the parameter is a number and b) whether there is a dash in the parameter. Of course, I have a system with a user with the username of 2-xhibit (no I can't get the user to change), which makes edquota think that that username parameter is actually a uid range which it interprets as meaning the range of 2-0, which it errors out on. IMHO, I think that either fixing this to actually check to see if the parameter is ONLY numbers and a single hyphen would be a good idea. Of course, this then doesn't permit usernames of like 10-4 or something like that. The other option would be to check the parameter FIRST against the password file and if the parameter is a valid username, then use it as a username instead of a range. Alternatively, providing a switch to force one way or the other would be ok also. I would patch the code and submit a fix if I knew what people thought the best way to fix this is, or if even people think that it should be changed at all. - Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ -- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: fbsdboot.exe can't load elf kernels
On Tue, 11 Jan 2000, R Joseph Wright wrote: > Which brings up the question that keeps nagging at me: How possible is > it to create a pc bios that is geared towards BSD/linux? This would > include its own lightweight repair shell. Couldn't this solve a lot of > problems with pc hardware, to have a unix-oriented bios? My take on this is: Possible != Portable. Or better put, Writing a "FreeBSD-cool" bios would be relatively easy. Trying to keep it updated and/or make it work on a whole bunch of different vendor's computers wouldn't. - Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ -- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: fbsdboot.exe can't load elf kernels
On Tue, 11 Jan 2000, Mike Smith wrote: > In a very few cases, you'll find disk 'emulators' that offer BIOS > interfaces to the emulated disk. These are rapidly declining in > popularity because they offer very poor performance for Windows-using > customers. They also typically fare very poorly or not at all under > other operating systems, as they tend to require timer interrupts in a > very hostile fashion. I agree with your statement in general. However, in the "truly" embedded PC world, the most popular off-the-shelf Flash Disk solution (M-Systems DiskOnChip-Millenium) is actually of this type. However, this solution also provides native drivers for Windows and a whole host of other OS'es. If there isn't a FreeBSD driver available, expect one from me in a few weeks. However, in the "truly" embedded world, you generally do not want a multiple-stage boot process. In fact, I have spent a fair bit of time eradicating (sp?) most of the "unneccesary" multi-stage boot from the PicoBSD stuff I'm doing for a product of mine. The idea of actually putting a DOS "partition" on the system seems crazy. > Please; take it from me that "booting DOS to boot another operating > system" is so far beyond a joke in most situations that we don't even want > to pretend in public that it's done, let alone talk about supporting it. There is only one circumstance in which this might be acceptable, and that is to support co-habitation with an OS which REQUIRES it's own MBR which doesn't support dual-booting to a FreeBSD partition. I can't think of any modern OS that works this way. And even if there was, I can think of a million other ways to get around this than writing a DOS-based loader. A few byte program which basically executes the FreeBSD bootstrap program comes to mind. - Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ -- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Warner's PCI Modem Driver
On Wed, 26 Jan 2000, Jason C. Wells wrote: > I am told that the modem is not a winmodem, but I don't know how to tell > by looking at it. The modem is a Phoebe. The documentation for it is > sparse. I took a gander at the Phoebe web page at http://www.phoebemicro.com/modems/pci.htm and I dont see ANY of the modems which I would trust to NOT be a winmodem. On the modem itself, there should be some numbers on the largest chip or chips. Could you provide us with those, represented as well as you can off of the modem? (this should tell us if it's a winmodem, if someone can identify the chipset.) Also, if you could try to figure out which phoebe modem it is, it would also be helpful. Alternatively, save yourself some time and go buy a USRobotics (now 3com) Sportster (NOT winmodem) Modem. I have personally used the USR part number 5687 for an internal ISA modem and it works well (http://www.3com.com/client/pcd/products/prod-faxmod5687-int.html). I have also used the 5686 external modem as well. (http://www.3com.com/client/pcd/products/prod-faxmod5686-ext.html) It appears that the 5610 PCI versions would work also. (The other advantage is that USR is really good about saying "WINMODEM" in most cases). HINT: When looking at modem specs you want to see something like the following: - Minimum System Requirements: IBM Compatible 486DX or Pentium Processor with available 2.1 PCI Slot. DOS, Microsoft Windows 95, 98 or Windows NT 4. - The key here is 486 and DOS. If it will work under DOS on a 486 it should work under freebsd. (Yes I know there are a couple exceptions, but they are few and far between) Occasionally, a vendor will only list Pentiums or higher, or will only list Windows OS'es. This isn't a guarantee that any given modem will work, but as a general rule, a Winmodem needs BOTH a pentium and Windows 95+ to work. Be very very wary of ANYTHING which says "Pentium 120 or higher" or the like. Geez. Life would be much easier if people would just say "Compatible with most Unix-based operating systems on the PC" on the box. - Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ -- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: User ppp question (fwd)
On Tue, 15 Feb 2000, Roman Shterenzon wrote: > Perhaps I'm missing something, but it happends in the middle of set login > script, not before.. it says Waiting for RING and then Phase - disc.. > Look in the previous mail. What I believe is occuring is that it "enables" carrier detection before the start of the login script. Thus, when the script hangs up the modem, ppp sees the carrier transition and exits the login script. - Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ -- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: named & log_in_vain
On Mon, 21 Feb 2000, Gregory Bond wrote: > Feb 21 16:24:28 ns /kernel: Connection attempt to UDP 192.168.128.49:1617 from >192.168.128.49:53 > Feb 21 16:41:03 ns /kernel: Connection attempt to UDP 192.168.128.49:1772 from >192.168.128.49:53 > This IP address is on one of the ether cards. The first port varies, the second > is always 53 (DNS). These machines run local secondary name servers and > Can someone explain what's going on, and how I can stop it? This looks suspiciously like responses to named queries and/or named-xfer's. You might want to set named to only use port 53 for outbound queries and see if the log entries change (or go away, since named is listening on 53). - Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ -- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3.4-stable to 4.0-stable wedge
On Wed, 5 Apr 2000, Warner Losh wrote: > You left it on the sofa when you dropped by. The refund check is > under it. Sadly, after the first 5 beers, we started using it as a > coaster. I sure wish AOL would send me another coaster soon, or I'll > run through all my Win95 disks given the amount of entertaining I do. The new aol coasters are much cooler than the old ones. The old ones were kinda small to set a drink on... 3.5" isn't that big. I like the fact the newer ones are shiny on the one side and they fit much bigger "drink containers". On a semi-serious note I have a friend who is actually going to shingle his dog's doghouse with (mostly) old AOL and Microsoft CD's. If I remember I will post a url for the picture to the list when it is done - Forrest W. Christian ([EMAIL PROTECTED]) KD7EHZ -- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
