Lazy SPLs
Hi! I'm reading http://www.BSDI.COM/products/internet/40-qna.mhtml#Q5 and found the following peice of text: Lazy SPLs - The kernel no longer masks hardware events unless a hardware event actually occurs, avoiding many expensive operations. Does anyone know what this is? Also, maybe a related question, when turning on/off interrupts using the ICU, is it still necessary to flush the out stream by doing an out to a unused port? === Regards, Tommy Hallgren Briljantg. 31, SE-421 49, Göteborg Tel.: 031 - 770 5232 (Work: Telia Prosoft) Tel.: 0709 - 312 404 (GSM) Tel.: 031 - 47 65 28 (Home) _ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: c9x (new ANSI C)
At 5:08 pm -0500 19/5/99, G. Adam Stanislav wrote: [...] I just downloaded it, and thought I'd share the fact with you - anyone interested in the upcoming changes to ISO C may want to download it now as well. Get the text version as the pdf version appears corrupt. Text, PostScript and PDF are available at: http://anubis.dkuug.dk/JTC1/SC22/WG14/www/docs/n869/ -- Bob Bishop (0118) 977 4017 international code +44 118 r...@gid.co.ukfax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Lazy SPLs
Tommy Hallgren wrote: Hi! I'm reading http://www.BSDI.COM/products/internet/40-qna.mhtml#Q5 and found t he following peice of text: Lazy SPLs - The kernel no longer masks hardware events unless a hardware eve nt actually occurs, avoiding many expensive operations. Does anyone know what this is? Exactly what it says.. We've been doing it for as long as I can remember, at least as far back as 2.0.5, probably as far back as 1.x. What it means is that in a section of code like this: s = splbio(); foo(); splx(s); .. the hardware interrupt masks in the icu's are not changed unless an interrupt happens that should have been masked. The handler checks the mask and finds that it isn't allowed. The hardware is then masked for real and the interrupt handler returns without going further. When a lowering of the priority causes a previously deferred interrupt to become unmasked then it's handler will be executed. revision 1.7 date: 1994/04/02 07:00:50; author: davidg; state: Exp; lines: +94 -102 ^^ New interrupt code from Bruce Evans. [..] /usr/src/sys/i386/isa/icu.s: o Software interrupts (SWIs) and delayed hardware interrupts (HWIs) are now handled uniformally, and dispatching them from splx() is more like dispatching them from _doreti. The dispatcher is essentially *(handler[ffs(ipending ~cpl)](). In fact, it even looks like rev 1.1 of these files had lazy spls: revision 1.1.1.1 date: 1993/06/12 14:58:01; author: rgrimes; state: Exp; lines: +0 -0 Initial import, 0.1 + pk 0.2.4-B1 .. that's even before FreeBSD 1.0. Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: timeconsuming processes on FreeBSD 3.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I could add another one, top(1) frequently does that on this machine.. so whatever answers you get, be sure to forward them to me :). On Wed, 19 May 1999, Luigi Rizzo wrote: These programs are mostly tin and lynx and such interactive programs. ... ee and pico are two more. ee is particularly annoying since it is one of the supported editors... luigi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-bugs in the body of the message -BEGIN PGP SIGNATURE- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBN0OR8tGMB8VPlu8bEQL+BQCff4avQlzKP31XOIdO2tZ7zqz1840AoODY C8dkgIiGnfIBg+Nc/QHq+k1U =6Rxx -END PGP SIGNATURE- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: boot troubles in 3.1
Sergey Babkin wrote: Hi! I have tried to install 3.1 on two machines but on both of them I was not able to boot it after installation. The 3.0-snapshot from May-98 worked fine on both of them. But 3.1 did not boot. First, the MBR boot manager was not able to boot any partition, nor FreeBSD nor UnixWare. After I replaced it with boot manager from 3.0 it worked but then some later stage of the boot was not able to find the kernel. Both machines have Phoenix BIOS (one is Intel, another Unisys). One has IDE disk, another has SCSI. I'm about to look at the problem but want to make sure first that it's not a known bug that was fixed long ago (sorry, I have not tracked -hackers for about half a year). Any information will be appreciated. 3.0 boot blocks won't boot 3.1 kernel, and since you didn't provide any information about the problem you had with 3.1 boot blocks, we can't help you at this point. I'm cc'ing Nordier, since the boot manager is his. Keep him cc'ed (or reply directly to him, I suppose) when you provide further details. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org If at first you don't succeed, skydiving is not for you. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Dumb IP alias confusion.
I didn't notice this until recently, but on our production web servers I use IP aliasing to host multiple sites on one box. Pretty normal stuff. Here's an ifconfig on one of these boxes: xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 208.156.59.51 netmask 0xff00 broadcast 208.156.59.255 inet 208.156.59.10 netmask 0xff00 broadcast 208.156.59.255 ether 00:10:5a:e4:87:22 media: 100baseTX full-duplex supported media: autoselect 100baseTX full-duplex 100baseTX half-dupl ex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP half-duplex 10baseT/UTP xl1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 10.0.0.3 netmask 0xff00 broadcast 10.0.0.255 ether 00:10:5a:e4:87:0d media: 100baseTX full-duplex supported media: autoselect 100baseTX full-duplex 100baseTX half-dupl ex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP half-duplex 10baseT/UTP lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 Looks pretty good. The only problem is that connections from the local machine will only connect to the _first_ (or real) IP address for an interface. A connection, for example, from this machine to 208.156.59.10 just hangs ... I'm assuming that I've simply forgotten some configuration step. This box is running 3.1-STABLE/May-9. Chuck Youse Director of Systems cyo...@cybersites.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Dumb IP alias confusion.
Hi, You need to either set the netmask of the alias address to 255.255.255.255, or add a manual route statement: route add alias_address 127.1 That will do it. Then you will be able to get to the alias address from the aliased machine. On a side note: 1. Does anyone know how to get this same thing to work with natd?? i.e. is there a way for the natd box to see ports that it is redirecting as they would be seen from the outside world?? I am pretty sure that the Cisco PIX firewalls will do this, but I was wondering if it was possible with FreeBSD. Thanks, Ben Gavin At 12:04 PM 5/20/99 -0400, you wrote: I didn't notice this until recently, but on our production web servers I use IP aliasing to host multiple sites on one box. Pretty normal stuff. Here's an ifconfig on one of these boxes: xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 208.156.59.51 netmask 0xff00 broadcast 208.156.59.255 inet 208.156.59.10 netmask 0xff00 broadcast 208.156.59.255 ether 00:10:5a:e4:87:22 media: 100baseTX full-duplex supported media: autoselect 100baseTX full-duplex 100baseTX half-dupl ex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP half-duplex 10baseT/UTP xl1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 10.0.0.3 netmask 0xff00 broadcast 10.0.0.255 ether 00:10:5a:e4:87:0d media: 100baseTX full-duplex supported media: autoselect 100baseTX full-duplex 100baseTX half-dupl ex 100baseTX 10baseT/UTP full-duplex 10baseT/UTP half-duplex 10baseT/UTP lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 Looks pretty good. The only problem is that connections from the local machine will only connect to the _first_ (or real) IP address for an interface. A connection, for example, from this machine to 208.156.59.10 just hangs ... I'm assuming that I've simply forgotten some configuration step. This box is running 3.1-STABLE/May-9. Chuck Youse Director of Systems cyo...@cybersites.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message /--/ Benjamin Gavin - Senior Consultant *** NO SPAM!! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Database holywars?
Greetings, I've taken up a project that will rely very heavily on remote database access. Naturally, the choice as to which database engine to use is a crucial one. I'd like to stay away from the commercial database suites (i.e. Oracle) for the time being, however I will eventually move to it once the database grows to over 100M records. In the meantime however, I'm debating heavily between MySQL and Berkeley DB with a multi-threaded socket frontend. Suggestions and comments? Dan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Database holywars?
On Thu, 20 May 1999, Dan Moschuk wrote: Greetings, I've taken up a project that will rely very heavily on remote database access. Naturally, the choice as to which database engine to use is a crucial one. I'd like to stay away from the commercial database suites (i.e. Oracle) for the time being, however I will eventually move to it once the database grows to over 100M records. In the meantime however, I'm debating heavily between MySQL and Berkeley DB with a multi-threaded socket frontend. Suggestions and comments? What's more important, flexibility to make changes, or speed? Anything that implements sql has to be far slower, but if you make many changes, you're going to heavily regret choosing a set of C language functions as the base of your DB. +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: timeconsuming processes on FreeBSD 3.1
On Wed, 19 May 1999, Andre Rikkert de Koe wrote: We are an ISP and we recently installed FreeBSD 3.1 on our main logonserver. Since than almost every day we find timeconsuming processes running while the user isn't even logged in (anymore). These programs are I believe the easiest solution to this problem is to install idled - it will (I gather) kill off processes owned by users no longer logged in, etc. Also a good way to prevent them running those infernal bots that are the bane of system administrators everywhere. Steve. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Database holywars?
| I'd like to stay away from the commercial database suites (i.e. Oracle) for | the time being, however I will eventually move to it once the database grows | to over 100M records. In the meantime however, I'm debating heavily between | MySQL and Berkeley DB with a multi-threaded socket frontend. | | Suggestions and comments? | | What's more important, flexibility to make changes, or speed? Anything | that implements sql has to be far slower, but if you make many changes, | you're going to heavily regret choosing a set of C language functions | as the base of your DB. I think a proper equilibrium between the two would be most desirable, but, if I had to choose one over the other it would definately be speed. The actual structure of the database isn't going to change much, if at all, I would imagine. Assuming it changes once a year, writing a conversion program to read in the old structure and write out the new one doesn't seem quite so horrendous. On the other hand, its a lot more annoying than a simple ALTER .. ADD statement. :-) Dan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: netbooting a freebsd kernel with 3c905B (fwd)
amo...@allstor-sw.co.uk writes: | Doug Ambrisko came up with some patches, you can find an early version | attached to PR 9480, there may be more recent versions around now. I need to update it to the latest version. Another one just came out and I see some more 905b bugs fixes are in. However, I won't be able to get to it until mid next week if things go well. Doug A. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
REQ: Review inetd internal wrapping fix
Hi folks, I'm looking for feedback on the fix that is attached to PR 11651, which I believe fixes wrapping for inetd's internal services. I found the code quite intense, so I'm not entirely convinced that my approach is sound. Thanks, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
What does VOP_WHITEOUT() do?
Can anyone tell me what does VOP_WHITEOUT() do? I can not find it in the hypertext manual pages. Thanks. -- Zhihui Zhang. Please visit http://www.freebsd.org -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Database holywars?
On Thu, 20 May 1999, Dan Moschuk wrote: | I'd like to stay away from the commercial database suites (i.e. Oracle) for | the time being, however I will eventually move to it once the database grows | to over 100M records. In the meantime however, I'm debating heavily between | MySQL and Berkeley DB with a multi-threaded socket frontend. | | Suggestions and comments? | | What's more important, flexibility to make changes, or speed? Anything | that implements sql has to be far slower, but if you make many changes, | you're going to heavily regret choosing a set of C language functions | as the base of your DB. I think a proper equilibrium between the two would be most desirable, but, if I had to choose one over the other it would definately be speed. The actual structure of the database isn't going to change much, if at all, I would imagine. Assuming it changes once a year, writing a conversion program to read in the old structure and write out the new one doesn't seem quite so horrendous. On the other hand, its a lot more annoying than a simple ALTER .. ADD statement. :-) It's one step more complicated than that. Moving an sql database from a free implementation to a commercial implementation, while not perfect, isn't all that terrible a thing to do. Moving it from a C language implementation to sql is going to be harsh, because it's a working database, so you can't afford any bugs. The DB implementation is going to be at least an order of magnitude faster (depending on the sql database, maybe 2 orders), but if it's a money oriented thing, do it via sql, not C. If it's machine control thing, often C is better. I have a personal prejudice I'm trying hard to mask, in favor of C language implementations, you should know that while you read this. Notice your client is going to matter vary much here. As an example, if you tell a stockbroker that you've saved him a huge amount of money at an added .001% risk, that stockbroker will fire you, because they don't care about money, they want to have it work, and they don't want to hear about details. Save him *time*, however, and you can count on a huge bonus! +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Database holywars?
On Thu, 20 May 1999, Dan Moschuk wrote: Greetings, I've taken up a project that will rely very heavily on remote database access. Naturally, the choice as to which database engine to use is a crucial one. I'd like to stay away from the commercial database suites (i.e. Oracle) for the time being, however I will eventually move to it once the database grows to over 100M records. In the meantime however, I'm debating heavily between MySQL and Berkeley DB with a multi-threaded socket frontend. Suggestions and comments? ¿Have you considered PostgreSQL? It is on the ports collection, and is a heavy duty database engine, with transactions, subqueries (only partial support), etc. Version 6.5 will be released in about two weeks, and it adds MVCC (multi-version concurrency control), which will improve a lot its multi-user capabilities. And, I know of some projects that are using it for multi-GB databases. I've been using it for or student database for more than two years (since version 6.0), and am quite happy with it. See www.postgresql.org for more information. -- --- Pedro José Lobo Perea Tel:+34 91 336 78 19 Centro de Cálculo Fax:+34 91 331 92 29 E.U.I.T. Telecomunicación e-mail: pjl...@euitt.upm.es Universidad Politécnica de Madrid Ctra. de Valencia, Km. 7E-28031 Madrid - España / Spain To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Database holywars?
On Thu, 20 May 1999, Pedro J. Lobo wrote: On Thu, 20 May 1999, Dan Moschuk wrote: Greetings, I've taken up a project that will rely very heavily on remote database access. Naturally, the choice as to which database engine to use is a crucial one. I'd like to stay away from the commercial database suites (i.e. Oracle) for the time being, however I will eventually move to it once the database grows to over 100M records. In the meantime however, I'm debating heavily between MySQL and Berkeley DB with a multi-threaded socket frontend. Suggestions and comments? ¿Have you considered PostgreSQL? It is on the ports collection, and is a heavy duty database engine, with transactions, subqueries (only partial support), etc. Version 6.5 will be released in about two weeks, and it adds MVCC (multi-version concurrency control), which will improve a lot its multi-user capabilities. And, I know of some projects that are using it for multi-GB databases. I've been using it for or student database for more than two years (since version 6.0), and am quite happy with it. See www.postgresql.org for more information. And it has Java bindings (JDBC). I found Java makes *great* front ends. Postgresql + Java are a fine mixture. +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Database holywars?
| ¿Have you considered PostgreSQL? It is on the ports collection, and is a | heavy duty database engine, with transactions, subqueries (only partial | support), etc. Version 6.5 will be released in about two weeks, and it | adds MVCC (multi-version concurrency control), which will improve a lot | its multi-user capabilities. And, I know of some projects that are using | it for multi-GB databases. I've been using it for or student database | for more than two years (since version 6.0), and am quite happy with | it. See www.postgresql.org for more information. If I recall correctly, isn't postgresql *based* off of the Berkeley DB engine? -Dan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
error 6: panic : cannot mount root(2) with PicoBSD current
Help I'm trying to get the PicoBSD code on -current compiling again as it has got a bit stale. But I get a kernel Panic. I brought the kernel config files up to date. Booting with the 'dial' disk (build without ssh) panics with error 6: panic: cannot mount root (2) This comes just ater the sio and ie0 probes. I wonder if it has anything to do with the old entry config kernel root on wd0 which the new config program ignores. Any suggestions? Bye Roger To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Database holywars?
On Thu, 20 May 1999, Dan Moschuk wrote: | ¿Have you considered PostgreSQL? It is on the ports collection, and is a | heavy duty database engine, with transactions, subqueries (only partial | support), etc. Version 6.5 will be released in about two weeks, and it | adds MVCC (multi-version concurrency control), which will improve a lot | its multi-user capabilities. And, I know of some projects that are using | it for multi-GB databases. I've been using it for or student database | for more than two years (since version 6.0), and am quite happy with | it. See www.postgresql.org for more information. If I recall correctly, isn't postgresql *based* off of the Berkeley DB engine? I don't know, but it's irrelevant. The point is, do you use an intervening compatibility layer (sql) for your database, or not. There has to be a low level layer, but if postgresql uses any particular one isn't of any importance here, you understand? It's just figuring the costs, on the one hand, what you gain in speed, on the other hand, what you give up in reconfigurability and portability. You won't find the commercial db having a Berkeley DB interface. If you want that final move to be as painless and bug free as you can make it (if that's of real importance, and you just can't keep the db in C and move it as C code) then you're going to want sql. There isn't any one right answer here. Note your requirements, and see which method meets your goals closest. If you want to argue this further, we should take it offline, it's ceased to be interesting to the list at large. -Dan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Database holywars?
:| ¿Have you considered PostgreSQL? It is on the ports collection, and is a :| heavy duty database engine, with transactions, subqueries (only partial :| support), etc. Version 6.5 will be released in about two weeks, and it :| adds MVCC (multi-version concurrency control), which will improve a lot :| its multi-user capabilities. And, I know of some projects that are using :| it for multi-GB databases. I've been using it for or student database :| for more than two years (since version 6.0), and am quite happy with :| it. See www.postgresql.org for more information. : :If I recall correctly, isn't postgresql *based* off of the Berkeley DB :engine? : :-Dan No, Berkeley DB doesn't have much to do with anything. Postgres or MySql are both good choices. Postgres has many more features but is also much bulkier. MySql is slim and fast, but not feature-rich enough to handle realtime operations on complex or large datasets. If the original poster intends to ultimately upgrade to a commercial database, I would probably use Postgres rather then MySql. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
PNP Soundcards w/ diskless booting.
I'm using /usr/ports/net/etherboot, to boot diskless workstations. Everything is working quite well. Now some of the stations need sound, and there are an abundancy of pnp soundcards that workfine, but with the network boot I'm immediately in the kernel, no cli to config the PNP. Now if I include the INTRO_USERCONFIG, of course I get the cli but because /boot doesn't exist I can't save the info, and adds un-neccesary complication to machines that doen't need it. Any thoughts... -- Email: ska...@worldgate.com Voice: +780 413 1910Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 ---- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Lazy SPLs
On Thu, 20 May 1999, Peter Wemm wrote: Tommy Hallgren wrote: Hi! I'm reading http://www.BSDI.COM/products/internet/40-qna.mhtml#Q5 and found t he following peice of text: Lazy SPLs - The kernel no longer masks hardware events unless a hardware eve nt actually occurs, avoiding many expensive operations. Does anyone know what this is? Exactly what it says.. We've been doing it for as long as I can remember, at least as far back as 2.0.5, probably as far back as 1.x. My earliest memory of it was as Bruce's new interrupt code for 386bsd. It was part of the 386bsd patchkit I think. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: PNP Soundcards w/ diskless booting.
I'm using /usr/ports/net/etherboot, to boot diskless workstations. Everything is working quite well. Now some of the stations need sound, and there are an abundancy of pnp soundcards that workfine, but with the network boot I'm immediately in the kernel, no cli to config the PNP. Now if I include the INTRO_USERCONFIG, of course I get the cli but because /boot doesn't exist I can't save the info, and adds un-neccesary complication to machines that doen't need it. Any thoughts... Help us write network drivers for the loader. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msm...@freebsd.org \\-- Joseph Merrick \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Cyclom Ye panics 3.1's SMP kernel
Subject: Cyclades Cyclom-Ye panics with 3.1's SMP Sent:5/20/99 3:33 PM To: freebsd-...@freebsd.com freebsd-hack...@freebsd.com SUMMARY: My cyclades cyclom-Ye panics the kernel when I am running with release-3.1's smp options. Turning off SMP allows the card to work fine. Unplugging the SM-II pod also allows normal operation of the machine in SMP mode (of course then there are no serial ports to access). If anyone has suggestions, advice, or sympathy to offer it will be welcomed. DETAILS: occurs when a serial port on the cyclom board first accessed panic message = Panic: rslock: cpu 0: addr: 0xf026a3ec, lock 0x0001 mp_lock = 0001: cpuid = 0: lapic.id = stack trace = #10 bsl1 () #11 cyopen (dev=12416, flag=5, mode=8192, p=0xf8ceae60) at ../../i386/isa/cy.c:755 further tracing has revealed that the panic actually occures in the commctl function in cy.c likely when a call is made to disable_intr() at line #2453. hardware = Tyan S1832DL Tiger 100 with dual Pentium II 350's 256 MB RAM, 18 GB IDE drive other: happens with both the isa and pci version of the card. -- Michael Scott Boers Datacomp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: c9x (new ANSI C)
In message 19990519180151.a...@whizkidtech.net G. Adam Stanislav writes: : And the MS book was outright lying (gee, surprise): It claimed that : one of the biggest advantages of C++ over C is that if you change : the C++ class, you need not recompile the code using it. What a : piece of bunk. In C++ the caller allocates the memory called by the : class. Some SGI compilers get around this somehow. They are really much nicer to work with than the cfront based compilers and their descendants. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: c9x (new ANSI C)
In message 199905192354.taa17...@whizzo.transsys.com Louis A. Mamakos writes: : Truly and example of the less is more concept in action. I've done : some non-trivial development in Objective-C, and I can assure you that : I haven't missed C++'s operator overloading. That's one failing of C++. It is hard to know which of the many tools in your toolbox are right to use. Inexperienced C++ coders and designers tend to use them all, because they can. Not because they are needed. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: error 6: panic : cannot mount root(2) with PicoBSD current
Roger Hardiman wrote:
Help
I'm trying to get the PicoBSD code on -current compiling again
as it has got a bit stale. But I get a kernel Panic.
I brought the kernel config files up to date. Booting
with the 'dial' disk (build without ssh) panics with
error 6: panic: cannot mount root (2)
This comes just ater the sio and ie0 probes.
I wonder if it has anything to do with the old entry
config kernel root on wd0
which the new config program ignores.
In a kernel with only mfs, MFS_ROOT means _no_ rootdev.
This breakage was caused by phk when he changed src/sys/kern/vfs_conf.c
for his jail implementation. The problem is that with MFS_ROOT,
the cpu_rootconf() function in src/i386/i386/autoconf.c correctly chooses
mfs, but doesn't set the global rootdev variable that phk's code
requires. I've reported this problem to current (got no response)
and to phk (with a patch which he responded to with what am I missing?).
Here is the patch I sent (cut'n'pasted from my copy of the email.
so tabs are smashed).
NB: I have an axe too. Mine is an Oz version though, so if I turn it
over, it works like a hammer. I'll use it on Sunday (23rd) and commit
this patch if nobody fixes the MFS_ROOT problem before then.
Index: vfs_conf.c
===
RCS file: /home/ncvs/src/sys/kern/vfs_conf.c,v
retrieving revision 1.26
diff -c -r1.26 vfs_conf.c
*** vfs_conf.c 1998/09/14 19:56:40 1.26
--- vfs_conf.c 1999/05/11 09:53:33
***
*** 52,57
--- 52,58
*on SMP reentrancy
*/
#include opt_bootp.h
+ #include opt_mfs.h
#include sys/param.h/* dev_t (types.h)*/
#include sys/kernel.h
***
*** 136,141
--- 137,145
/*
* Attempt the mount
*/
+ #ifdefMFS_ROOT
+ err = VFS_MOUNT(mp, NULL, NULL, NULL, p);
+ #else
err = ENXIO;
orootdev = rootdev;
if (rootdevs[0] == NODEV)
***
*** 154,159
--- 158,164
if (err != ENXIO)
break;
}
+ #endif
if (err) {
/*
* XXX should ask the user for the name in some cases.
--
John Birrell - j...@cimlogic.com.au; j...@freebsd.org
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: What does VOP_WHITEOUT() do?
According to Zhihui Zhang: Can anyone tell me what does VOP_WHITEOUT() do? I can not find it in the hypertext manual pages. You can find a small documentation in the 4.4BSD daemon book. It is used when stacking filesystems (especially unionfs). Imagine you have 2 FS mounted on above the other with unionfs. This gives you FS1. Note that when stacking FS, the underlying ones are R/O (FS2 in this case). FS file Ait appears here. 1 - FS --- file A the real file 2 File A is seen as part of the whole unified FS1. Now, imagine you rm file A from FS1. The file won't be actually removed from FS2 but a whiteout entry will appear inside FS1 to mask the file from it. More (and better) explanations on page 236 of the new daemon book. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: What does VOP_WHITEOUT() do?
New daemon book? I must have missed that. Do you have the full title? Chuck -Original Message- From: Ollivier Robert robe...@keltia.freenix.fr To: freebsd-hackers@FreeBSD.ORG freebsd-hackers@FreeBSD.ORG Date: Thursday, May 20, 1999 5:32 PM Subject: Re: What does VOP_WHITEOUT() do? According to Zhihui Zhang: Can anyone tell me what does VOP_WHITEOUT() do? I can not find it in the hypertext manual pages. You can find a small documentation in the 4.4BSD daemon book. It is used when stacking filesystems (especially unionfs). Imagine you have 2 FS mounted on above the other with unionfs. This gives you FS1. Note that when stacking FS, the underlying ones are R/O (FS2 in this case). FS file Ait appears here. 1 - FS --- file A the real file 2 File A is seen as part of the whole unified FS1. Now, imagine you rm file A from FS1. The file won't be actually removed from FS2 but a whiteout entry will appear inside FS1 to mask the file from it. More (and better) explanations on page 236 of the new daemon book. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #71: Sun May 9 20:16:32 CEST 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: What does VOP_WHITEOUT() do?
Chuck Youse cyo...@cybersites.com writes: New daemon book? I must have missed that. Do you have the full title? McKusick, Bostic, Karels, and Quarterman, The Design and Implementation of the 4.4BSD Operating System, Addison-Wesley, Reading, MA, 1996. ISBN 0-201-54979-4 -matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: What does VOP_WHITEOUT() do?
Oh, nevermind. I must have misinterpreted the previous post. I thought that a _newer_ book had arrived. Chuck -Original Message- From: R. Matthew Emerson r...@nightfly.apk.net To: Chuck Youse cyo...@cybersites.com Cc: freebsd-hackers@FreeBSD.ORG freebsd-hackers@FreeBSD.ORG Date: Thursday, May 20, 1999 6:11 PM Subject: Re: What does VOP_WHITEOUT() do? Chuck Youse cyo...@cybersites.com writes: New daemon book? I must have missed that. Do you have the full title? McKusick, Bostic, Karels, and Quarterman, The Design and Implementation of the 4.4BSD Operating System, Addison-Wesley, Reading, MA, 1996. ISBN 0-201-54979-4 -matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: What does VOP_WHITEOUT() do?:
On 20 May 1999, R. Matthew Emerson wrote: :Chuck Youse cyo...@cybersites.com writes: : New daemon book? : I must have missed that. Do you have the full title? :McKusick, Bostic, Karels, and Quarterman, The Design and Implementation :of the 4.4BSD Operating System, Addison-Wesley, Reading, MA, 1996. :ISBN 0-201-54979-4 Not exactly new. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: PNP Soundcards w/ diskless booting.
this has got it THANKS Quoting Eivind Eklund (eiv...@freebsd.org) On Subject: Re: PNP Soundcards w/ diskless booting. Date: Fri, May 21, 1999 at 01:35:08AM +0200 On Thu, May 20, 1999 at 01:21:10PM -0600, Greg Skafte wrote: I'm using /usr/ports/net/etherboot, to boot diskless workstations. Everything is working quite well. Now some of the stations need sound, and there are an abundancy of pnp soundcards that workfine, but with the network boot I'm immediately in the kernel, no cli to config the PNP. Now if I include the INTRO_USERCONFIG, of course I get the cli but because /boot doesn't exist I can't save the info, and adds un-neccesary complication to machines that doen't need it. Any thoughts... If the BIOS supports PnP: Put the PCs in question in working mode. The switch for non-working mode is usually labelled 'PnP OS', and setting it to 'YES' will make the BIOS not work, while setting it to 'NO' will make the BIOS work correctly (and your sound card work without any mess). Don't ask me why they include a crappy labelled do-not-work button - it is probably a result of lacking clue, as so much else in this world. Eivind. -- Email: ska...@worldgate.com Voice: +780 413 1910Fax: +780 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 ---- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Lazy SPLs
Lazy SPLs - The kernel no longer masks hardware events unless a hardware event actually occurs, avoiding many expensive operations. We've been doing it for as long as I can remember, at least as far back as 2.0.5, probably as far back as 1.x. My earliest memory of it was as Bruce's new interrupt code for 386bsd. It was part of the 386bsd patchkit I think. Why mask out the interrupts at all, instead of queuing them in handler level? joelh -- Joel Ray Holveck - jo...@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Lazy SPLs
Lazy SPLs - The kernel no longer masks hardware events unless a hardware event actually occurs, avoiding many expensive operations. We've been doing it for as long as I can remember, at least as far back as 2.0.5, probably as far back as 1.x. My earliest memory of it was as Bruce's new interrupt code for 386bsd. It was part of the 386bsd patchkit I think. Why mask out the interrupts at all, instead of queuing them in handler level? Level-triggered interrupts are persistent conditions, not queueable events. They typically require device-driver level intervention to be cleared. This is a major error in the PCI design (no surprises there). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msm...@freebsd.org \\-- Joseph Merrick \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: Lazy SPLs
On Thursday, May 20, 1999 7:18 PM, Joel Ray Holveck [SMTP:jo...@gnu.org] wrote: Lazy SPLs - The kernel no longer masks hardware events unless a hardware event actually occurs, avoiding many expensive operations. We've been doing it for as long as I can remember, at least as far back as 2.0.5, probably as far back as 1.x. My earliest memory of it was as Bruce's new interrupt code for 386bsd. It was part of the 386bsd patchkit I think. Why mask out the interrupts at all, instead of queuing them in handler level? Because only the device's driver knows how to stop the device from interrupting again and again, but calling its handler is prohibited. Lazy SPLs is an optimization. Drivers play with SPLs very often, so it would be unefficient to program the interrupt controller each time when somebody wants to increment a counter. However, if the device has indeed interrupted, there is no choice left except disabling it in the interrupt controller. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Humour: Microsoft Announces Improved Blue Screen of Death
Newswire 5/12/99 --- Microsoft Announces Improved BSOD In a surprise announcement today, Microsoft President Steve Ballmer revealed that the Redmond based company will allow computer resellers and end-users to customize the appearance of the Blue Screen of Death (abbreviated BSOD), the screen that displays when the Windows operating system crashes. The move comes as the result of numerous focus groups and customer surveys done by Microsoft. Thousands of Microsoft customers were asked, What do you spend the most time doing on your computer? A surprising number of respondents said, Staring at a Blue Screen of Death. At 54 percent, it was the top answer, beating the second place answer Downloading Pornography by an easy 12 points. We immediately recognized this as a great opportunity for ourselves, our channel partners, and especially our customers. explained the excited Ballmer to a room full of reporters. Immense video displays were used to show images of the new customizable BSOD screen side-by-side with the older static version. Users can select from a collection of BSOD Themes, allowing them to instead have a Mauve Screen of Death or even a Paisley Screen of Death. Graphics and multimedia content can now be incorporated into the screen, making the BSOD the perfect conduit for delivering product information and entertainment to Windows users. The Blue Screen of Death is by far the most recognized feature of the Windows (tm) operating system, and as a result, Microsoft has historically insisted on total control over its look-and-feel. This recent departure from that policy reflects Microsoft's recognition of the Windows desktop itself as the ultimate information portal. By default, the new BSOD will be configured to show a random selection of Microsoft product information whenever the system crashes. Microsoft channel partners can negotiate with Microsoft for the right to customize the BSOD on systems they ship. Major computer resellers such as Compaq, Gateway, and Dell are already lining up for premier placement on the new and improved BSOD. Balmer concluded by getting a dig in against the Open Source community. This just goes to show that Microsoft continues to innovate at a much faster pace than open source. I have yet to see any evidence that Linux or OpenBSD even have a BSOD, let alone a customizable one. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: c9x (new ANSI C)
On Thu, May 20, 1999 at 01:41:37PM -0600, Warner Losh wrote: In message 19990519180151.a...@whizkidtech.net G. Adam Stanislav writes: : And the MS book was outright lying (gee, surprise): It claimed that : one of the biggest advantages of C++ over C is that if you change : the C++ class, you need not recompile the code using it. What a : piece of bunk. In C++ the caller allocates the memory called by the : class. Some SGI compilers get around this somehow. They are really much nicer to work with than the cfront based compilers and their descendants. I'm glad to hear that. That would make the code much more robust. I was only exposed to MS VC++, and I am very glad I always examine the assembly language output of anything I write in a high-level language! It was a mess. Of course, everything from MS is Adam To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: dlopen failure
In article 373c3f3f.a99db...@cablenet.net, Damian Hamill dam...@cablenet.net wrote: I have a program that is dumping core. --- Here's the gdb output; Program terminated with signal 6, Abort trap. #0 0x800b728 in _kill () (gdb) bt #0 0x800b728 in _kill () #1 0x800b34c in abort () #2 0x8004aa2 in __assert () #3 0x8003b4b in map_object () #4 0x8002e9e in find_symdef () #5 0x800334d in dlopen () #6 0x8049a68 in Get_SQL_Driver (name=0x804c7e4 mysql) at Vdb.c:150 #7 0x8049ff9 in GetDefaultDriver () at Vdb.c:254 #8 0x804a141 in VdbInit (user=0x804bfb1 nobody, passwd=0x0) at Vdb.c:329 #9 0x8049316 in main () #10 0x8048be5 in _start () I don't know what's going on here, but this stack trace can't be right. dlopen doesn't call find_symdef, and find_symdef doesn't call map_object. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
