RE: Anyone using pptp?
Dear Thomas, > > Well - I'm still trying to get pptp to cooperate and set up > a VPN connection to a Microsoft VPN server. > > I'm just wondering - is there _anyone_ out there that has > met with success using pptp - and, if so, could you share > your /etc/ppp/ppp.conf settings? > http://kjkoster.org/?page=content/adsl.jsp It's specific for my provider, though. Kees Jan = You can't have everything. Where would you put it? [Steven Wright] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: compare and contrast vmware and jail ?
Dear Trent, > > (Yeah, ok, I'll keep going. My Linux VM actually builds our > work system up to ten minutes quicker than running Linux na- > tively on the same machine. Make of that what you will!) > Umm. Have you tried to build it under linux-compat in FreeBSD? Sounds like it's worth the experiment. :) Kees Jan $DEITY bless $NATION. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: linux JVMs not handling SEGV well.
[ CC'd to freebsd-java, please followup there too ] Dear Andrew, This question is better asked on -java, so I forwarded you question. There are many hardcore JVM hackers on that list. > > I'm using 4.x-stable, linux-base-6.x, and am encountering a lot of > turbulence with both Sun's jdk1.3.x HotSpot JVM and IBM's > linux jdk1.3.x JVM. > Well, considering that technically we don't actually have any Java VM post 1.1.8... :-) > > I have a buggy 3rdparty java app that occasionally causes a > null pointer > exception to be thrown. While not fatal for the app (the exception is > correctly caught), it's most often fatal for the JVM. The SUN > jvm SEGV's ( > doesn't correctly catch the SIGNAL ), while the IBM jvm seems to get > locked in kernel mode - only responding to SIGKILL and > chewing up tons of > 'system' cpu time. The common denominator here is that both > JITs utilize > linux threads. When I use a non-threaded JIT, the problem > doesn't occur. > > The problem is readily reproducible, but I'm not sure how to debug it. > I've played with truss and ktrace, but I think it's time to > begin thinking > about using the kernel debugger. > Could you perhaps provide a simple code sample that allows us to reproduce the problem? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Please commit this port: ports/31188: New port: www/orion-cur rent
Dear Mike, > > > I am fully aware that -hackers is not the right forum for > this discussion, > > and I apologise for the noise. I tried the appropriate > mailing lists first > > and got ignored. You are the second person to respond to > two mails to > > -ports, one to -java and one to -hackers. > > > > I'm open to other ideas on how to get this port committed. > > The best advice I can give is to just be patient. > Thanks for your advice. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Please commit this port: ports/31188: New port: www/orion-current
Dear Mike, > > > Guys, please. Is there noone with a tiny bit of time on > their hands and > > -ports commit privs? I've been bugging -java -ports and now > -hackers and get > > no reaction at all. What happened to the close-a-PR drive? > > This is inappropriate discussion for -hackers so you're unlikely to > find a response here. > I am fully aware that -hackers is not the right forum for this discussion, and I apologise for the noise. I tried the appropriate mailing lists first and got ignored. You are the second person to respond to two mails to -ports, one to -java and one to -hackers. I'm open to other ideas on how to get this port committed. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Please commit this port: ports/31188: New port: www/orion-current
Dear All, Guys, please. Is there noone with a tiny bit of time on their hands and -ports commit privs? I've been bugging -java -ports and now -hackers and get no reaction at all. What happened to the close-a-PR drive? Kees Jan You are only young once, but you can stay immature all your life. > -Original Message- > From: Kees Jan Koster [mailto:[EMAIL PROTECTED]] > Sent: vrijdag 9 november 2001 22:45 > To: [EMAIL PROTECTED] > Subject: Re: ports/31188: New port: www/orion-current > > > Dear All, > > I've tried to get someone to commit this port over on -ports, but > I got no response. Is there someone who could commit this port, > please? > > Thanks in advance. > > Yours, >Kees Jan > > --- > Kees Jan Koster e-mail: kjkoster "at" kjkoster.org >www: http://www.kjkoster.org/ > --- >File not found. Should I fake it? [Y/N] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: FreeBSD on vmware
[ Picking any one to reply to... ] > > I have been running -current under vmware 2.x up until about August.. > (it didn't stop working, but I vmware stopped running on -current > due to KSE changes (patches now available I believe)).. > > i.e I was running -current under -current > Thanks to all who responded. The fact that it works for some reassures me that it might work for me too. :-) I'm still at a loss what to do about the vmware and kernel panics. The vmware tools port is not a big help, since I have no FreeBSD to install it into. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: FreeBSD on vmware
Dear Rohit, Thanks for the response and your suggestion. > > > Fatal trap 12: page fault in vm86 mode > > The following change helped me get rid of a similar panic. > > - device atkbd0 at atkbdc? irq 1 > + device atkbd0 at atkbdc? irq 1 flags 0x1 > When I look at the keyboard in the visual kernel configuration this flag is already set. Just out of curiousity, are there any people who actually have FreeBSD running inside a vmware VM? Evidence from the mailing list archives seems to suggest that it worked up to FreeBSD 3.2 and then stopped, never to work again. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
FreeBSD on vmware
Dear All, We have a rather beafy server here and we're experimenting with putting a number of vmware sessions on it. To avoid Windows and Linux becoming the only OS'es here in the lab I've volunteered to help out and install FreeBSD. :) I have tried installing on a few configurations; SCSI and IDE, with and without LAN. First: FreeBSD gets a SCSI disk and LAN. The bt0 driver picks up on the disk and proceeds to panic the vmware environment. The main error message is: VMWare GSX Server Panic BUG F(562): 1703 bugnr=4935. Second: FreeBSD gets an IDE disk and LAN. The FreeBSD kernel panics right after detecting the keyboard. The panic is (typed from screen): Fatal trap 12: page fault in vm86 mode fault vir. addr.= 0x1000 code= user read, page not present instr. ptr. = 0x0:0xa03 stack ptr = 0x0:0xffe frame ptr = 0x0:0x0 code seg. = base 0x0, lim 0x0, type 0x0 dpl 0, pres 0, def32 0, gran 0 cpu efl = interrupt enabled, vm86, iopl=0 currproc= 0 (swapper) int mask= net tty bio cam trap= 12 The same panic occurs when I boot up without LAN. This was using FreeBSD version 4.4 from the (ATAPI) cdrom. Detailed logs are available on request and I'm willing to try any experiments you may suggest. Anyone have any suggestions as to what I could try? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: dmesg behaviour
Dear, > > On the supermicro > systems, we may see the information from the last 3 boots! I see the > lines: > > syncing disks... done > Rebooting... > > and then we go right into the next boot. At present, one of > the machines shows all the detail from 2.75 reboots. > > How and why is it doing this, and how do I make it stop? > FWIW, FreeBSD/alpha also exhibits this behaviour. Perhaps it's better to adapt your tools to cope to improve their portability between FreeBSD-supported architectures? Kees Jan = You can't have everything. Where would you put it? [Steven Wright] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Suggestions for sysinstall / disklabel
Dear All, > > The Alpha's root *must* be the first partition > (starting at the > "begining" of the disk). People often know how much swap > they want, and > take what is left for other things. So they allocate swap first. > Sysinstall's disk editor gives no feedback on how it is going > to lay out > the disk. There have been numerious install failures reported to > freebsd-alpha@ because of this. > I've submitted a rather feeble patch (PR alpha/23064) that makes sysinstall whine when someone is found aiming at his/her foot. If someone would be so kind as to review/submit this patch. Kees Jan = You can't have everything. Where would you put it? [Steven Wright] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: What makes it FreeBSD...
Dear All, > > > >It's reasonable to want to control what get's called FreeBSD. > > > > Certainly. But I think it has to go beyond the installer. We > should define an environment that third party applications can > depend on being available in any installation that claims to > be FreeBSD. Without this, you have the same environement that > Linux does where third party apps are only qualified on distribution > U and X and have no hope of working on distributions Y and Z. > To me, what makes it FreeBSD is the fact that it came straight off cvsup.*.freebsd.org. We are fortunate to have a centralised distribution schema, so we can actually distinguish what is freebsd and what is (technically) not (darwin, trustedbsd). Kees Jan = You can't have everything. Where would you put it? [Steven Wright] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Athlon MP / AMD 760MP Chipset (Athlon SMP question)
Dear All, > > The new iTanic (aka Itanium) processor... > TiTanic? Hmm, no wonder they get such bad press over this thing. Kees Jan = You can't have everything. Where would you put it? [Steven Wright] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: recent 4.3-stable freezes my SMP box
> > > >I just upgraded one of my boxes to FreeBSD 4.3-stable with > >cvsup. Unfortunately the machine now freezes. > > If you are tracking -stable, then there is a lot of good reason > to keep an eye the freebsd-stable mailing list. Particularly > when something like this comes up. > *blush* I've been running FreeBSD since 2.1.0 and only now I learn that there is a -stable list as well as a -current list. Why didn't anyone tell me? :) The SMP box is happily churning away on a new installation. Problem solved. Thanks to all involved. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
recent 4.3-stable freezes my SMP box
Dear All,
I just upgraded one of my boxes to FreeBSD 4.3-stable with cvsup.
Unfortunately the machine now freezes. I can ping it and it responds to
[ctrl][alt][esc] on the console ("No debugger in kernel") and I can switch
consoles [alt][F1..4], but it does not respond to other keyboard events. For
example [ctrl][alt][del] does not work.
The machine is a Compaq Proliant, dual 550MHz Xeon, with a hardware raid
SCSI box that comes up as sym0 (875).
I powercycled the box, since I cannot actually log in to see what's up. The
system boots, gives me a login prompt and subsequently freezes again.
Booting into single user more allows me to fsck and mount and look around
for a bit until is also freezes. A verbose boot gives me one message that I
worry about a bit (from memory:)
APIC_IO: MP table broken 8259->APIC entry missing
Should I worry? What SMP related stuff went into -stable in the last month
or so? Anything that might freeze my box?
I have two very similar Proliant uniprocessor boxes that appear to work
fine, but the SMP box is their NFS home dir server. This prevents me from
logging in remotely at this moment to check. It's after hours here.
The machine has been stable for a few months, and I upgrade -stable every
first week of the month. This box is the buildbox that I built all -stables
on so far, so I'm quite sure this box is a-ok.
More tomorrow, when I get access to the actual server console again. Any
hints appreciated. In particular: how do I get back to last week's -stable?
:-)
Kees Jan
You are only young once,
but you can stay immature all your life.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
RE: Query: How to tell if Microsoft is using BSD TCP/IP code?
Dear Jordan, Bill Gates has jumped in to clarify "OS vs. GPL" surprisingly quickly after the publication in WSJ. Lee is my hero. > > Sort of the other way around. We were the "several FreeBSD > volunteers" referenced in the article. Lee's my press contact at the > WSJ and he's done a number of pieces favorable to us in the past. > Perhaps Lee can consider tracking down how much GLP lisenced software is used in companies in close proximity to Microsoft. While Microsoft is not going to be caught dead using it, there must be companies that are married to Microsoft on one end, but happily use Linux on the other. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Mergemaster killed symlink (was RE: Mergemaster bug + new feature [patch])
Dear James, > > > I had a mergemaster problem a while back, but I haven't debugged it > > properly. I had my /etc/ppp symlinked into /home/root/ppp. > Then, after a > > mergemaster run I ended up with a file named /etc/ppp, which had the > > contents of the new version of /etc/ppp/ppp.conf. > > I symlinked /etc/ppp to /usr/ppp and mergemaster updated > fine. I then removed > /usr/ppp making the symlink invalid and mergemaster overwrote > the bad symlink > with ppp.conf. Is there any chance when you ran mergemaster > that one time your /home was not mounted? > Well, now that you mention it I think that I just blew away /home/root/ppp since the box was not going to dial out anymore. Best not have passwords lying around for no reason. :) Glad you could reproduce it. Should I submit a PR or is this a "doctor, it hurts when I press here"--thing? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Injecting a packet with explicit route.
Dear Karsten, > > > Definition of Windows 95: A 32-bit extension and graphical > > shell for a 16 Bit patch to an 8 Bit OS originally coded > > for an 4 Bit CPU, written by a 2-Bit Company that can't > > stand 1 Bit of competition. > That would make Windows 2000 the 64-bit sauce on the 32-bit extension and graphical... Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Mergemaster bug + new feature [patch]
Dear James, I had a mergemaster problem a while back, but I haven't debugged it properly. I had my /etc/ppp symlinked into /home/root/ppp. Then, after a mergemaster run I ended up with a file named /etc/ppp, which had the contents of the new version of /etc/ppp/ppp.conf. This box used to dial out, but no longer does so I did not care about/pursue the problem. Sorry about the scetchy information. Kees Jan PS. I initially read the subject line as "mergemaster has one fewer bug and one newly discovered feature". :) You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: import NetBSD rc system
Dear All,
>
> To do some of the hierarchal start/stop at runtime stuff, you
> really need
> a stateful rc system that stores its start/stop state in
> /var/run/rc.d or
> the like. In this way, the system could track various
> activities and know
> which dependencies were already started.
>
How about /var/run/{$deamon}.pid?
Kees Jan
You are only young once,
but you can stay immature all your life.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
RE: Preliminary Tuning man page (was Re: Benchmarking FreeBSD (was ...))
Dear Michael, > > Actually, it had never occurred to me that soft-updates was a > property of a > file-system and not a global flag in the kernel. That is why > I suggested a more prominent note about soft-updates. > Until you suggested it, it never ocurred to me that it could be anything but a per-filesystem property. When you run the 4.3 /stand/sysinstall it specifically allows you to change soft-updates setting per filesystem. I would oppose dmesg output on soft-updates enabling, because it does not say "mounting /usr, mounting /var" either. How do I know my MFS /tmp is mounted? How do I even know that /usr/local is mounted? Simple: by typing "mount", which, conveniently, also tells me about mount options such as soft-updates. As a counter-proposal, the soft-updates option should be made a mount option (which it is going to be IIRC), and described in the mount manual page. Maybe the GENERIC and LINT kernels could have a text reading "man mount for more info". Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Preliminary Tuning man page (was Re: Benchmarking FreeBSD (was ...))
Dear All, > > Perhaps there should be a message somewhere prominent > encouraging people to > check whether their drives really have soft updates enabled. > It would also > be useful if something during boot showed whether a mount > would be using soft updates. > Have you typed "mount" at the command line lately? :-) Kees Jan You are only young once, but you can stay immature all your life.> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
cvsup problems
Dear All, Over the past few days I've been getting this error when I "make update": ... Checkout ports/www/hypermail/files/patch-docs::Makefile.in Delete ports/www/jakarta-tomcat/files Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. makalu# The error message is correct in the sense that that directory is not empty. It's got two patch fiels and a shell script in it. Permissions look fine (read-write for root). Manually deleting /usr/ports/www/jakarta-tomcat will allow me to run cvsup, but next time it will have recreated the files it tries to delete, triggering the error again next time I run cvsup. I've set SUP* in /etc/make.conf and the supfiles are stock 4.3-stable. I run cvsup with a "make update" from /usr/src. This problem occurs on both my build servers, which have nothing in common except the fact that they are PC's running FreeBSD-stable. What am I doing wrong? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: technical comparison
Dear All, An interview with Reiser just appeared on http://www.slashdot.org/ Just to add a little oil to the fire. :-) Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Linux getcwd problems
Dear Alfred, > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=24315 > > > > The summary is that getcwd(3) under Linux emulation will fail really > > hard after a rmdir. > > > I've looked at your email and the PR, the problem that I have is that > I have no clue as to what it should return. Can you give a suggestion > and possibly site a refernece? Basically, WWLD (what would linux do)? > Umm. I'm confused. WLWD is give me a useful value for cwd, given that my cwd actually exists. What I see is this: % touch build.xml % mkdir gen % rmdir gen % ant Buildfile: build.xml BUILD FAILED java.io.FileNotFoundException: iÉ/build.xml (No such file or directory) ^^- note this It looks like that after a directory was removed from the cwd, the Linux getcwd command returns garbage. The JDK uses getcwd routinely, to set the user.dir (or some such) property. Ant uses that property to determine what file to open, i.e. it opens (in a mix of C, Java and pseudocode): new FileInputStream(linux_getcwd() + "/build.xml") Since getcwd() returns garbage after a directory was deleted from the cwd, the above fails with the exception mentioned earlier. I think it is safe to assume that on a Linux system, getcwd() returns meaningful information every time, under normal circumstances. :-) This is about as clear as I can describe the problem. Hope this helps. > > Instead of asking why a piece of software is using "1970s technology," > start asking why software is ignoring 30 years of accumulated wisdom. > Because today I know better. [Ghandi] :-) Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Linux getcwd problems
Dear All, I just ran into a problem with the linuxulator, triggered by the Linux JDK that I use for my development. Markus kindly pointed me to this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=24315 The summary is that getcwd(3) under Linux emulation will fail really hard after a rmdir. Does anyone have time to sit down and fix this? You would be my hero (or heroin, as the case may be). Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: [jkh@osd.bsdi.com: ANNOUNCE: Status update on ftp.freebsd.org A KA ftp.freesoftware.com]
Dear Jessem, > > A) A poor excuse for a coverup (for some unknown reason) > Need a reason? See item C. > > B) Major incompetence (in which someone should resign) > Does this mean you're volunteering? In case you don't: I hereby resign from the position of Major Incompetence. I have proudly held this position for the past eigthteen seconds. However, in honest and open talk with General Protection Failure we have come to the conclusion that it's best for me to let the younger generation move up and fill my shoes in this department. I have learned a lot from working with you in this position and it hurts me to make this decision. Still, my life goes on, and so does yours. > > C) Aliens have landed > Ah. All is explained. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: VPN
Dear Thomas, > > > Any advantages or disadvantages of using one or other?. > > What is better (is the first > > time I set VPN on a UNIX system).? > > If your requirements are not too complicated, you can use pipsecd > (from ports/net), which is an implementation of ipsec that requires > only very limited setup. Besides, pipsecd has been successfully > tested for interoperation with other ipsec products. > Does "other ipsec products" include stuff from Microsoft? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: No route to host problems on 5.0-CURRENT
Dear Andrew, > > And arp -a call shows that my gateway arp address is > "incomplete", now Im > wondering if there is something left out of my kernel build > or if there is > some other problem I can possibly resolve. > Just a stab in the dark: is your firewalling correctly configured? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: non-working fxp cards
Dear Jonathan, > > I would like anyone who has a fxp card which doesn't work with > the current driver to contact me in order to test out an alternate > driver. > I've (finally!) sat down with a few machines and my collection of fxp cards, only to find that the problem seems to have been fixed. I'm confused. %-) Before testing the alternate drivers I wanted to see the problem again, so I cvsupped to 4.3-RC2 about three hours ago. Plop in the cards, reboot and ... everything works fine. Ping, ftp chunky files, mount NFS. No errors. I have three more cards that I'd like to test, but they are in someone else's server at the moment and people in the lab are a little hard to get hold of at nine o'clock at night. |-) Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: vm balance
Dear Matt, > : > :Well, if that's the case, yank all uses of v_id from the nfs code, > :I'll do the namecache and vnodes can be deleted to the joy > of our users... > : > > If you can yank v_id out from the kern/vfs_cache code, I > will make similar > fixes to the NFS code. I am not particularly interesting > in returning > vnodes to the MALLOC pool myself, but I am interested in > fixing the > two bugs I noticed when I ran over the code earlier today. > > Actually one bug. The vput() turns out to be correct, I > just looked at > the code again. However, the cache_lookup() call in > nfs_vnops.c is > broken. Assuming no other fixes, the vpid load needs to > occur before > the VOP_ACCESS call rather then after. > I'm just curious: would this be the "redundant call/non-optimal performance"--type bug or the "panics or trashes the system in dark and mysterious ways"--type bug? If it is the latter, do you think it may be an opportunity for you to close some NFS-related PR's? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: system slows down to a crawl
Dear Andrew, > > I just went out and bought that book. It is titled "System Performance > Tuning," by Mike Loukides, published by O'Reilly, with a swordfish on > the cover. > > It's 11 years old, which means it was pre-FreeBSD (indeed, even > pre-Linux!), but the main focus is 4.3BSD, which makes many aspects > still relevant. I am finding it to be an interesting read. > And after eleven years not only is the information in the book relevant and useful (even on Windows), the command line examples still work (though not on Windows). This book is a prime example of teaching a man how to fish. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: system slows down to a crawl
Dear Peter, > > not a big pain, but rather puzzling. when i play heretic on > 4.2 stable (no > sound) after i get killed couple of times and reload the > previously saved > game system gets slower and slower (pIII, 128 RAM). just > wandering if there > is some memory leak in heretis, since when i kill the game > system goes back > to its normal speed. > It sounds more like something that belongs on -questions, rather than -hackers. If I were you, I'd have a look at a book named "System Performance Tuning". I forget the author, but it's one of the Nutshell handbooks. After reading through that you will be able to answer your own question, and know how to squeeze a little extra oompf out of your box. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: A novel idea....
Dear Andrew, > > 18) Ports. 'ya can't forget them. > More importantly, ports that are going to work on all free BSD's. If you haven't been keeping track of Open Packages, those guys have put the pedal to the metal. > > Just my ramblings. I don't evangelize much, but it strikes me > as odd that some of this info isn't on the homepage of > FreeBSD. FWIW -sc > I think that's part of the "try it, and see for yourself" mentality. If you like FreeBSD, you use it, and you don't need FreeBSD evangelism. If you don't like FreeBSD, you go away and you don't need FreeBSD evangelism. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: pmap bomb on 4.0-STABLE
Dear Mahlon, > > Can anyone tell me what this means - and even better, a fix? It's > my understanding that pmap concerns shared memory, is it possible > I have a bad stick of ram floating around? > Bad memory sticks are easy to find. Just rip out half the RAM and let the box run for a few days, then let it run off the other half for a while. Check case cooling too. Kees Jan PS. Please notice that crossposting is generally frowned upon. People tend to ignore you if you do this. You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: JDK1.2 build
Dear Alwyn, > > > > I find this to be rather strange. I'm well into day two of > staring at it > > so help is definitely needed. I considered doing the entire > build by hand, > > following the instructions given online but was pinning my > hopes on you > > guys before doing that. > The complete JDK build process is outlined in ridiculous detail on http://kjkoster.org/java/index.jsp?page=content/howto.jsp The instructions are cut'n paste ready, and there's a lot on why you have to do what you're doing. If you have any trouble following my instructions, please feel free to mail me directly. Kees Jan PS. Just to prove that it Can Be Done(tm), those web pages are served up from a native FreeBSD JDK. :-) You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Readdir() unlink() interaction
Dear All, I'm curious what the specified behaviour is of readdir() after and unlink(). The manual pages of these functions do not specify this. I'm asking this in relation to PR kern/26142, where you will infd a little test program to reproduce the problem. I've just done so on FreeBSD 4.3 RC and and Solaris. FreeBSD NFS mounts cause problems, Solaris NFS or FreeBSD local mounts show expected behaviour. Is there any documentation that specifies unlink()/readdir() interaction? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Intel driver doc's Take 2.
> > Its not a "proprietary tree". I dont have time to clean it up > and submit patches. > Please mail me your pci/if_fxp* just as they are and I wil clean up and submit patches in your name. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
OP make import?
Dear All, In the interest of a unified BSD ports tree, is anyone working to integrate the diffs for the make from openpackages into the FreeBSD codebase? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: optimizing apache with php and nfs mounts
> > _ _ > __/\_____ (_) __ _ | |__ __/\__ > \/ / __| | | / _` | | '_ \\/ > /_ _\ \__ \ | | | (_| | | | | | /_ _\ >\/ |___/ |_| \__, | |_| |_| \/ > |___/ > > :-) > > Where did you even get the idea "-O6" did *_ANYTHING_*?? Don't people > ever read the documentation anymore. > On top of that: the subject line suggests that NFS is involved in the equation. Are you sure you're cpu-bound and aren't losing lots of time getting files from the NFS server? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: non-working fxp cards
Dear Dennis, > > > > in case you havent read my posts, I've fixed the problem > > > with mine. > > > >Glad to hear it. In that case, I expect you _NOT_ to use my > >new driver. > > And why is that? I thought you just might like some guidance. > Feel free to beat on it on your own. > I think John made what some cultures would refer to as a "joke". You're supposed to laugh (you know, the "ha, ha"--kind'a sound). Yours, Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: if_fxp status?
Dear All, > > >> > Harrruummm. (Gong!) > >> > Harrruummm. (Gong!) > :-) > > > > its been discussed several times on this list. No need to > > > go into it again. > > > > Then why the hell are you posting if there is no need to go > > into it again? > > It is extremely bad form to post asking for something > > without supplying > > details or at least a pointer to where they are (msgid's etc). > http://www.geocrawler.com/archives/3/159/2000/12/0/4775943/ There are other threads, of course, but this is the longest and contains all the technical information you may need. > > > There are other people who can fix it, but they cannot do > > anything if you > > refuse to supply all the precise details in an easy to access form. > I am willing to ship an offending fxp card to whoever offers to fix this problem. We have about 9 useless cards left, IIRC. The 10th is currently on David Greenman's desk. > > > If you are unwilling to do that, then stop bothering us! > > Indeed, I think Dennis could solve two problems by just dropping > FreeBSD right away. > Dennis seems to have a knack for rubbing everyone else the wrong way, David said he'd fix this and hasn't. We all know this, so let's please leave it at that. Let's separate the technical issues from the personal ones. I'd love to see this fixed and I offer all I can to help: hardware and testing time. If someone could detail the problem in highly technical terms this might trigger someone else to offer another piece of the puzzle. What does the message "unsupported PHY" mean? How would one go about tracking down the properties of the PHY? How does Linux/NetBSD/OpenBSD/Windows/Solaris solve this? What halfassed fixes or pointers do we have already? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Missing support in FreeBSD for large file sizes?
Dear All, > > http://news.cnet.com/news/0-1003-200-5009496.html?tag=lh > Microsoft adjusted its licensing terms for the Maxtor system, Wilkins noted. Unlike general-purpose servers, a Maxtor machine doesn't require that customers pay for client access licenses--the fees often required for computers that use the server. "That's the first time Microsoft has done this," Wilkins said. This is a victory for the Open Source community, not a defeat. Microsoft is willing to bleed for real big customers, because they realize that Maxtor had a choice. At some point in the future Microsoft is going to be willing to bleed for little customers also. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: make bug? (dependency names with '$')
Dear All, > > This bug does not occur with NetBSD make. I spent a couple of hours > diffing the sources (there are a lot more differences than I expected) > There was some talk on the OpenPackages list about differences in the makes of the three BSD's. I've only followed the discussion with half an eye, but it would be nice for them too to see the makes converge, or at least iron out differences here and there. http://openpackages.org/pipermail/op-tech/ Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: make bug? (dependency names with '$')
Dear Jason, > > I want to construct a portable Makefile to build a java application. > I've played with Java and Make in the past, but I found that spawning a new instance of the Java compiler is more expensive than compiling a pretty big bunch of files. gcc starts up a lot quicker than a JVM. My solution (ahem) is to compile per (sub)package of my application and simply let the JAR file depend on all of the source files. Compiling this way is quicker in the majority of cases that I have. Have you looked at Apache's Ant project? I don't like it myself, but if you want a portable make, you might as well use a Java one. :) Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: isa/pnp modem not in sio.c
> > I constantly wonder why on earth the !#%$!^%!# modem vendors > dont use the > 'compatid' field to say 'this is compatable with a COM port' - and > everything would work nicely. > Because the drivers and the fluff they come with are rather excellent advertising platforms. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: syscall kernel modules on 3.0-release
> > Hmm, I have exactly the same situation, a mission-critical server that > can't be taken offline to do an upgrade. It's running 3.4, > but with a few binaries from 4.0 that I needed to make our CGIs work > (development is done on 4.2 :). > Euh... Mission Critical(tm) without a backup machine? Your boss did sign the "will not whine when it dies"--agreement, right? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Realtek card support
Dear All, > > I usually don't recommend the 8139/29 for anything that is > expected to work consistently. The cards work alright, but > I prefer to stick to Digital or Intel based NICs for > important tasks. > While it's obviously well established that these cards should be used as doorstops (and they would even suck at that) my idea was that there may be someone out there who can make the driver at least not hang up the line. Force it hard to 10mbit, or even reset the card for each and every packet sent, fork the code for this chip into src/pci/if_sucks.c, but at least make it work. I don't intent to use this brand for anything but toilet paper, but I keep running into people who have these cards. If people in the store and have to choose between a us$20 realtek and a us$100 3com they go for the realtek. Right now we're sending them back to the store to spend the extra us$80. I'd find the person who'd make the driver work around this card a hero. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Realtek card support
> > > This particular card is branded "TP-Link", chip reads RTL8139B. > > > > It detects, configures and runs for a while, but drops the > > line after a while. (PPTP to my ADSL modem) > > I got exactly this chip (RTL8139b) on a Realtek card working here 24/7 > since about two months. I also got problems with dropped > lines, but this > is because the ISDN "modem" drops the connection when the line quality > gets too bad. With a previous ISDN "modem" the darn box went > into jabber > mode, the only thing helping after that was power cycling the "modem", > then ifconfig rl0 down; ifconfig rl0 up again. After changing the > "modem" to a small CISCO 1000, the line is stable. > I had the line drop away from under me when I used this card in two PC's with a crosscable. I did an NFS-based FreeBSD install, but I had to replace the card before I was able to install the whole thing. What version of FreeBSD are you using? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Realtek card support
> > > > > I have two RealTek network cards that I'm willing to send > > to someone who is > > going to update the FreeBSD realtek driver to support them. > > > > what card is that and what is broken ? > both the ne and the rl driver works reasonably well with the 8029 > and 8139 chips. > This particular card is branded "TP-Link", chip reads RTL8139B. It detects, configures and runs for a while, but drops the line after a while. (PPTP to my ADSL modem) Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Realtek card support
Dear All, I have two RealTek network cards that I'm willing to send to someone who is going to update the FreeBSD realtek driver to support them. I know it's supposed to be broken in the hardware, but the sad fact is that in the Netherlands this is the *only* card they sell in many smaller stores. If you say "network adaptor" they give you realtek. If you ask for another brand, they look at you funny and give you realtek. If you *insist* on another brand they give you more funny looks, and give you realtek with the words that it's the OEM version of . (Calm down, deep breath ... there, much better) Anyway: send me your snail mail address, and I'll send you the realtek card. Kees Jan PS. for the record: I also still have an SMC EtherEZ 10Mb UTP and a 3Com 3c503 for those who want to work on drivers for them. You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Kernel Hacking (i tried not to make it lame)
> > > I think Yahoo! is using still on 2.2.8. > > Don't let your imagination run away with you. :) > Ok, ok. I just tried to say that there are still 2.2.8 users around with Yahoo! as an example. :-) Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Kernel Hacking (i tried not to make it lame)
Dear Ariff, > > I remembered porting back cd9660 to 2.2.x tree, and now look > forward porting softupdates (If anybody can give me some light > I really appreciate that). I'm reviewing sources from current, > stable and from other BSD project such OpenBSD to pick all > the good stuffs. > I'm a happy 2.2.x user. > I think Yahoo! is using still on 2.2.8. There are some people on this list who work for Yahoo!, so you could try to drop them a line. I can imagine that they are interested in softupdates. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Pseudo ethernet interface
Dear Suma, > > Is it possible to provide pseudo ethernet interfaces? > Can we associate an IP and MAC address with a psuedo ethernet > interface > to facilitate data packet transmission & reception through that? > If so, how does it work? > Pointers to any documentation in this regard will be appreciated. > Have you looked at the tun device? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: if_fxp driver info
> > 2) I don't have any boards that don't work correctly. > I have several. If you send me your surface-mail address, I can ship one to you. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Clustering FreeBSD
> > | Doh! I mean 9.8 m/s/s, of course. > > That's acceleration not velocity :-) > > The terminal velocity of a PC case is probably a lot lower than the > velocity of an outer edge of a 1 RPM drive. > Hmm. That would make a FreeBSD cluster quite useful as a garden shredder, even with lower disc rotation speeds I'd imagine. Mind you, taking the covers off the disks void your warranty. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: psmintr: out of sync
> > There is a workaround, if not a fix, for this problem in -CURRENT. > > Apply the following patch to /sys/isa/psm.c and add flags 0x8000 > to psm driver in your kernel config file as follows. > I had this problem (without moused) and I used this hack before I switched to XFree86 4.x from 3.3.6. Now I've run for months without seeing it. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: waiting for new files in a directory
Dear All, What you'd really want is some kind of message queueing system for this kind of work. What message queueing systems are (non-commercially) available on UNIX systems? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: kqueue microbenchmark results
> > > A simple way to keep the kernel simple: > > > http://linuxtoday.com/news_story.php3?ltsn=2000-12-09-013-20-NW-GN-KN > > Device drivers in Perl. What a spectacularly bad idea. ;^) > That's what people used to say about writing kernels in C. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: yet another unsupported PHY in fxp driver
Dear David, > >All of the above is caused by the SEEPROM not being read > properly. Since it doesn't work with 4.1, this probably indicates that > you're using an on-motherboard NIC (Supermicro?). > These are not on-board NICs, but PCI cards. (Do you know of a motherboard that comes with four on-board NICs?) > > I'm running out the door to the airport, however, and won't be able to > get a fix to you until next week. > Sorry to hear that you're in a hurry. I was secretly hoping that you'd have time. :-) Anything we can do in the mean time? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: yet another unsupported PHY in fxp driver
Dear All, I found this thread, but no real resolution, so pardon me for dragging this back up. Relevant dmesg output: fxp0: Ethernet address 00:08:c7:7b:05:bd bpf: fxp0 attached fxp1: Ethernet address 00:b4:c0:91:d2:9c, 10Mbps bpf: fxp1 attached fxp2: Ethernet address 00:b4:c0:91:d2:9c, 10Mbps bpf: fxp2 attached fxp3: Ethernet address 00:b4:c0:91:d2:9c, 10Mbps Say what? I lived under the impression that MAC addresses were unique. Here I have three cards that have identical MAC adresses. Finally, we finish off with: bpf: fxp0.0 attached fxp1: warning: unsupported PHY, type = 0, addr = 0 bpf: fxp1.0 attached fxp2: warning: unsupported PHY, type = 0, addr = 0 bpf: fxp2.0 attached fxp3: warning: unsupported PHY, type = 0, addr = 0 bpf: fxp3.0 attached fxp3: link media DOWN 10Mb / half-duplex fxp2: link media DOWN 10Mb / half-duplex fxp0: link media DOWN 10Mb / half-duplex fxp1: link media DOWN 10Mb / half-duplex The dmesg is from FreeBSD 2.2.8 (boot -v) by the way, but booting 4.1 yields the same results. Now (finally) my question: how do we get this particular PHY supported? This seems to have remained unanswered back in October. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: nslookup deprecation [was 4.2 complaint]
> > > Public Enemy said it before: don't believe the hype. In > > this case, the hype that an Internet year is only a few weeks of > > wallclock time. > > I'm sure there must be some meaning to what you write, but it keeps > eluding me. > I don't think that a year and a half is a long time for nslookup to be marked as deprecated but still being in wide use. I know that the current fad is to think that the Internet is a fastpaced environment. For some it may be, for nslookup it is not. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: nslookup deprecation [was 4.2 complaint]
> > > Recently there was a message indicating that ISC is deprecating > > nslookup. > > "Recently"? nslookup has been officially deprecated for about a year > and a half, I believe. > Public Enemy said it before: don't believe the hype. In this case, the hype that an Internet year is only a few weeks of wallclock time. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: sfork() ??
> > I've reached the point where I re-evaluate my design if I ever find > myself saying "..and then I can spawn a thread to.." > There is a Javathreads implementation I have never worked with threads in C++, but in Java it's almost trivial to use threads. Too easy, perhaps. Anyway, the people at OOC have created a C++ wrapper that should allow you to do Java-style threads in C++. Never used it myself, but perhaps it's of use to you. Have a look and http://www.ooc.com/jtc/ Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards inFreeBSD)
Dear Bill, I've cvsupped, which gave me the patched version of the pcn driver. Thanks for the prompt response. I've build various kernels. Kernel with pcn and lnc compiled in: trap 12 Kernel with lnc only:trap 12 Kernel with pcn only:works, but no network Kernel with neihter: works, but no network A backtrace reveals that the box dies with trap 12 in the function: __set_videodriver_set_sym_vga_driver() alloc_scp() scopen() cnopen() spec_open() spec_vnoperate() ufs_vnoperatespec() vn_open() open() syscall2() Xint0x80_syscall() The last thing that the box prints is "Addtional TCP options: ." and then the date. *beng* trap 12 etc Yes, it does print the "." in the end, so it completes the additional TCP options successfully. I'm lost here. If anyone has any suggestions I will happily try them on Monday. Otherwise I'm moving down a version or two. Right now I'm going home for the weekend (to a system that actually *works*). Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards inFreeBSD)
> > *ahem* How about compiling a kernel *without* the pcn driver? > I want to know why you didn't consider this combination. (Well, I > know why: because giving me the answer straight away rather than > making me drag it out of you would have been too easy. I would never > be that lucky.) > I did not consider a kernel without pcn compiled in is because you asked me to use the pcn driver. If you want straight answers, ask straight questions. :) For your information, I did hack the kernel for the lnc driver to *not* probe for the card, because I (wrongly) guessed that perhaps the lnc probe was screwing things up for the pnc probe. I figured that disabling the lnc driver in the visual config would do the trick, but as I type this it occurs to me that that might only disable the ISA card probe. I've tried a kernel without the pnc driver compiled in. Clean build directory and cvsupped to RELENG_4 as of 30 minutes ago. (typed from the screen, names may be misspelled, number are corrent, dmesg output attached) Fatal trap 12: page fault in kernel mode fault virtaul address: 0x616776 fault code: supervisor read, page not present instruction ptr:0x8:0x616776 stackprt: 0x10:0xc5d1bc4c frameptr: 0x10:0xc5d1bd0c code segment: base 0x0, limit 0xf, type 0x1b DPL 0, pres 1, def32 1 gran 1 processor eflagsinterrupt enabled, resume, IOPL 0 current proc. 1 (init) interrupt mask none trap nr 12 It just keeps getting better and better. *sigh* This is the first out of three machines that are to move up to 4.2. I planned a day for the first and an hour for each next one. I'm pretty sure the hardware is good. It survived a couple of buildworlds. It works in 4.0. I will see if I have time later today to rebuild the beast with kernel debugging stuff enabled to give more details. Right now I have other work to do. Are there any specific things that I should try? I'm a little lost. Kees Jan You are only young once, but you can stay immature all your life. This is my own custom kernel (4.2) Nov 17 12:38:52 dl6101 /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Nov 17 12:38:52 dl6101 /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Nov 17 12:38:52 dl6101 /kernel: The Regents of the University of California. All rights reserved. Nov 17 12:38:52 dl6101 /kernel: FreeBSD 4.2-BETA #0: Fri Nov 17 12:24:14 CET 2000 Nov 17 12:38:52 dl6101 /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/QUAM Nov 17 12:38:52 dl6101 /kernel: Timecounter "i8254" frequency 1193182 Hz Nov 17 12:38:52 dl6101 /kernel: Timecounter "TSC" frequency 25039 Hz Nov 17 12:38:52 dl6101 /kernel: CPU: Pentium Pro (200.01-MHz 686-class CPU) Nov 17 12:38:52 dl6101 /kernel: Origin = "GenuineIntel" Id = 0x616 Stepping = 6 Nov 17 12:38:52 dl6101 /kernel: Features=0xf9ff Nov 17 12:38:52 dl6101 /kernel: real memory = 67108864 (65536K bytes) Nov 17 12:38:52 dl6101 /kernel: avail memory = 62468096 (61004K bytes) Nov 17 12:38:52 dl6101 /kernel: bios32: Bad BIOS32 Service Directory Nov 17 12:38:52 dl6101 /kernel: Preloaded elf kernel "kernel" at 0xc02e6000. Nov 17 12:38:52 dl6101 /kernel: Pentium Pro MTRR support enabled Nov 17 12:38:52 dl6101 /kernel: npx0: on motherboard Nov 17 12:38:52 dl6101 /kernel: npx0: INT 16 interface Nov 17 12:38:52 dl6101 /kernel: pcib0: on motherboard Nov 17 12:38:52 dl6101 /kernel: pci0: on pcib0 Nov 17 12:38:53 dl6101 /kernel: lnc0: port 0x7000-0x701f irq 5 at device 11.0 on pci0 Nov 17 12:38:53 dl6101 /kernel: lnc0: PCnet-32 VL-Bus address 00:80:5f:fa:a0:82 Nov 17 12:38:53 dl6101 /kernel: lnc0: driver is using old-style compatability shims Nov 17 12:38:53 dl6101 /kernel: amd0: port 0x7100-0x717f irq 10 at device 12.0 on pci0 Nov 17 12:38:53 dl6101 /kernel: pci0: at 13.0 Nov 17 12:38:53 dl6101 /kernel: rl0: port 0x7200-0x72ff mem 0x430-0x43000ff irq 9 at device 14.0 on pci0 Nov 17 12:38:53 dl6101 /kernel: rl0: Ethernet address: 00:e0:4c:68:5c:0c Nov 17 12:38:53 dl6101 /kernel: miibus0: on rl0 Nov 17 12:38:53 dl6101 /kernel: rlphy0: on miibus0 Nov 17 12:38:53 dl6101 /kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Nov 17 12:38:53 dl6101 /kernel: isab0: at device 15.0 on pci0 Nov 17 12:38:53 dl6101 /kernel: eisa0: on isab0 Nov 17 12:38:53 dl6101 /kernel: mainboard0: on eisa0 slot 0 Nov 17 12:38:53 dl6101 /kernel: isa0: on isab0 Nov 17 12:38:53 dl6101 /kernel: chip0: at device 20.0 on pci0 Nov 17 12:38:53 dl6101 /kernel: fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Nov 17 12:38:53 dl6101 /kernel: fdc0: FIFO enabled, 8 bytes threshold Nov 17 12:38:53 dl6101 /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Nov 17 12:38:53 dl6101 /kernel: atkbdc0: at port 0x60,0x64 on isa0 Nov 17 12:38:53 dl6101 /kernel: atkbd0: flags 0x1 irq 1 on atkbdc0 Nov 17 1
More detail on Deskpro XL6200 NIC (was: Legacy ethernet cards inFreeBSD)
Dear Bill, others, I've been working on getting my Deskpros to use their NIC under 4.2, but no luck. The problem is as follows: I installed 4.0, and the NIC came up under the lnc driver, reports its MAC address and works fine. -- FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC ... lnc0: port 0x7000-0x701f irq 5 at device 11.0 on pci0 lnc0: supplying EUI64: 00:80:5f:ff:fe:fa:a0:82 lnc0: PCnet-32 VL-Bus address 00:80:5f:fa:a0:82 lnc0: driver is using old-style compatability shims -- In 4.2, the lnc driver still probes and finds the NIC, but does not report finding a MAC address, and the NIC remains dead. -- FreeBSD 4.2-BETA #0: Thu Nov 16 11:03:15 CET 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/QUAM ... lnc0: port 0x7000-0x701f irq 5 at device 11.0 on pci0 lnc0: driver is using old-style compatability shims --- Compiling a kernel with the pcn driver does not help. Booting a lnc+pcn kernel causes the behaviour described above, booting a pcn-only kernel makes the NIC show up as an unknown device, vendor 0x1022, device 0x2000. -- pci0: (vendor=0x1022, dev=0x2000) at 11.0 irq 5 -- Looking in the source shows that the pcn driver knows about this vendor/device combination. Booting -v does not show any attempts on pcn's part to take the card into its arms. -- avail memory = 62328832 (60868K bytes) bios32: Bad BIOS32 Service Directory Other BIOS signatures found: ACPI: Preloaded elf kernel "kernel" at 0xc0308000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03080a8. Pentium Pro MTRR support enabled pci_open(1):mode 1 addr port (0x0cf8) is 0xa06c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 1 2 3 4 5 6 7 8 9 10 11 [class=02] [hdr=00] is there (id=20001022) npx0: on motherboard npx0: INT 16 interface pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 1 2 3 4 5 6 7 8 9 10 11 [class=02] [hdr=00] is there (id=20001022) pcib0: on motherboard found-> vendor=0x1022, dev=0x2000, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=b, irq=5 map[10]: type 1, range 32, base 7000, size 5 found-> vendor=0x1022, dev=0x2020, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 7100, size 7 found-> vendor=0x102b, dev=0x0519, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=255 map[10]: type 1, range 32, base 0420, size 14 map[14]: type 1, range 32, base 0480, size 23 found-> vendor=0x10ec, dev=0x8139, revid=0x10 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base 6000, size 8 map[14]: type 1, range 32, base 4000, size 8 found-> vendor=0x0e11, dev=0x0001, revid=0x07 class=06-02-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found-> vendor=0x8086, dev=0x84c5, revid=0x04 class=05-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found-> vendor=0x8086, dev=0x84c4, revid=0x04 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 pci0: on pcib0 lnc0: port 0x7000-0x701f irq 5 at device 11.0 on pci0 lnc0: driver is using old-style compatability shims -- What am I missing? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Legacy ethernet cards in FreeBSD
> > Ok, "seem to have lost support" is about the vaguest thing you could > have said. I've killed people for less. > I'm too young to die. Sorry for the lack of detail. I should have known better. > > Please explain in detail how > you arrived at the conclusion that the card was no longer supported. > Show us the dmesg output from your machine. Explain what you tried to > do and what results you observed. Don't just say "it doesn't work." > You've not going to help anyone that way. > 4.0 detects my card, prints the ethernet address during the probe, and actually transmits data when asked to do so. DHCP configures the card, etc. 4.2 detects the card, but does *not* find its ethernet address and the DHCP probe simply never returns, although the machine responds to keypresses to break the installation. > > Did you check to see if a pcn0 device was detected? Did you attempt > to use it? > No. > > If not, why not? > I did not know it was there. > > > SMC EtherEZ ISA > > Should also work with the ed driver, though you may have to turn off > plug and play mode using the SMC EZSetup utility. > I will try this. > > > RealTek "TP-Link" PCI > > If this is a 10mbps card, it should be an NE2000 clone, and will work > with the ed driver. If it's a 100Mbps card, it should work with the > rl driver. > Like I said: it probes, works for a bit, then drops the line and needs a power-cycle. I have two, one of them is available for an individual who wants to hack at it, the other one will serve as a cupholder after I've stomped on it for a bit, otherwise the cups keep falling over. > > > I'll be happy to try out patches for the lnc driver to fix > the problem of > > the Deskpro, or to give remote access to it if you want to > work on it. > > I'd be happier if you told me whether the pcn driver works or not. > Will try. Please hold ... Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Legacy ethernet cards in FreeBSD
Dear All, Last night I cvsupped my trusty old Compaq Deskpro XL 6200 from 4.0-release to 4.2-beta. As part of that process, I seem to have lost support for the on-board NIC (lnc0: PCNet/PCI Ethernet Adapter, PC-net-32 VL-Bus). What is the newest version of FreeBSD that will propely support that card? If there are people who are cleaning up the support for older network cards in FreeBSD I'd like to help out by sending you my old NICs. It's not like they're any good to me without OS support. Please contact me off-list for any of the following cards: 3Com 3c503ISA DEC EtherworksISA DEC DE205 ISA SMC EtherEZ ISA RealTek "TP-Link" PCI As far as I've been able to determine, none of these work properly. In particular, the RealTek card gets detected and pretends to work, but loses the link after a bit (The link status LED goes out, and I need to reboot the box.) I'll be happy to try out patches for the lnc driver to fix the problem of the Deskpro, or to give remote access to it if you want to work on it. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: daemon()
> > No one with any brains uses bash 1 for anything > anymore. > Then why is it there? To help up the port count? If it's not good, it should be nuked, IMHO. Kees Jan PS. Interesting to use the words "nuke" and "humble" in the same sentence. I should go into politics. You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Broken PCI-IDE RZ1000 & ata
Dear All, > > > > Well, that chip is so broken by design, no software workaround > > > can help its misery, a hardware fix exists, but cant (easily) be > > > > As Volker notes; Linux can work round it. So can OS/2. I > > don't know the details, but there ARE modes where it works. > > Nope, there are not, even the manufacturer agrees to that > As much as I like ... err ... technical discussion, perhaps it's time that either side came up with something solid. "Linux can" and "Manufacturer agrees" are not solid, IMHO. The Linux code states that the workaround is perfect in what source file? The manufacturer agrees in what e-mail/article/knowledge base? Kees Jan PS. I'm glad I don't have that particular chip in my box. :-) You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: PPP patch (CHAP81 + MPPE)
Hello, > > With all these ppp can participate in MS VPN. > Euh. Right now I'm running ppp over pptpclient to connect to my ISP over an ADSL modem. Using your patch, can I ditch pptpclient? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
KPN ADSL Mxstream howto
Dear All, It's interesting to hear the reactions when you ask for FreeBSD support at helpdesks. (and not just KPN's) They used to say: "I'm sorry, you cannot use anything but Windows", nowadays they apologize for not knowing enough about UNIX to help. :-) We're getting there. For all you Dutchies out there: here's how I set up my Mxstream connection under FreeBSD. http://web.inter.nl.net/users/kjkoster/content/adsl.html Kees Jan Disclaimer: Yes, I work for KPN, but that is a coincidence. This e-mail is from me personally, and KPN may or may not agree with me. You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: irq
> > compiled a kernel on 4.1.1 STABLE and after exiting X I saw a message > stating something about /kernel stray irq 7 > http://www.FreeBSD.org/cgi/search.cgi?words=stray+irq+7&max=25&sort=score&in dex=recent&source=freebsd-questions Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: About imp
> > Answer me, please: what do imp in your FreeBSD logo? > > P.S. I like FreeBSD but imp... It main trouble for me. It > very bad. > Read this first, then see if you still think it's bad. http://www.freebsd.org/copyright/daemon.html Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Executable packages (long, sorry)
Dear All, While we're on the subject of packaging formats, I would like to present an idea that has been running around in the back of my head. Years ago I had the pleasure of playing with a new RiscPC by Acorn. If you create a directory on RiscOS and stick a little BASIC script in with exactly the right name, RiscOS will treat that directory as an executable. You can use the directory to stick in whatever the application needs, and the user never needs to bother. Uninstalling it is as easy as the RiscOS equivalent of "rm -rf". Riding on the wave of the unified BSD packages effort, this might be a good time to rekindle that idea. Say that we agree on some form of uniform package layout. You'd say that man pages go into $PKG_BASE/$PKG_NAME/man, and that libraries go into $PKG_BASE/$PKG_NAME/lib, and that there is probably a script named $PKG_BASE/$PKG_NAME/etc/rc that takes the arguments "start" and "stop" for system startup. A script named $PKG_BASE/$PKG_NAME/bin/run is invoked when a user types $PKG_NAME at the command prompt (triggered by a script in /usr/local/bin, which is symlinked to $PKG_NAME. We are already doing this now, but instead we scatter packages across the filesystem, keeping file lists of where we left the various body parts of the port. So is this a bad idea? I don't think so. Some programs already install themselves in a similar fashion. If you'll allow me to use Tomcat as an example. After you have installed it, only /usr/local/tomcat new on your system. It has its own bin/, conf/ and lib/ directory. Deinstalling is as simple as it is on a RiscPC. There are other places too, where you see this self-containment crop up. The executable JAR files from Java, for example. And someone over at KDE or Gnome (or some desktop kit like that, I can't tell them apart) mentioned that they were going to do a ZIP archive abstraction, much like they did with the file system. You could easily make a zip archive behave like an executable. I do not think that this is the perfect solution to system clobbering. In fact, there are some good examples of stuff that should really not be installed in an executable directory. The GNU tools spring to mind. They were written according to a UNIX utility philosophy, and should be treated as such. Other things, such as a web server, or a word processor are much more self contained. I hope that you will remember this idea when you find yourself staring at traces of an old port, unsure if you should delete it or not. :-) Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: diskless workstation
> > if by -stable you mean whatever i get when i do a 'cvs co > -rRELENG_4' src/sys > then there are some things missing. > i386/i386/autoconf.c does not have the stuff for pxe. > if i compile a kernel with the BOOTP_ stuff, then i can mount > nfsroot, but > [mount_]mfs is broken, i get 'bad address' when trying to > mount_mfs ... /conf/etc. > > if i see (or think i see :-) a bug in the diskless stuff who > do i inform? > I think the "bad address" messages indicate that your kernel and your "world" are out of sync. Do a make world and install a freshly compiled kernel. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: HELP: Disk/file-systems are loused up
> > The fsck was operating on and reporting on the hard > disk; the floppy > was not even mounted while I was booting. Since fsck in > all the variations with which I am familiar didn't fix the > disk, I am trying to find another variation or another > program to run which will complete the job without causing > any disasters. > "The job"? Which job finding or fscking? "the disk"? The floppy or the harddisk? Please be specific. If it's an MSDOS floppy, use Windows to find files on it. Windows cares a whole lot less about broken sectors than FreeBSD does. You could have a look at mtools (somewhere in the ports), it will allow you to access the floppy without mounting it, so your system is not going to die when you use a broken floppy. Mtools do not mount the floppy, so it will just give you hard sector errors on the console in case of trouble. If the problem is to restore a broken harddisk filesystem after a crash, and fsck can't help you, you're in a pile of it (if you'll pardon the expression). If this is indeed your problem, that is not clear from the original post you did. I have little experience with restoring screwed filesystems (I just rebuild and restore backups). Try posting the output of fsck, or at least the error it's giving you. > I also think that the find program should be checked > to see why it > crashed and fix it to keep it from doing similarly in the > future; I don't know whom to contact as yet. > No matter how broken, a program is unable to crash the OS (well, very, very unlikely :). If you mount a broken filesystem, FreeBSD will die, find or no find. I'll bet that you could 'cd' into the broken directory and do 'echo *' to crash the box. Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Microtime acting up again
Dear All, Last night my machine drowned in "microtime going backwards" errors. It was there when I installed FreeBSD 4.0-release, and it went away when I cvsupped to -stable immediately after. However, it is back again. My box is an AMD Athlon on an Asus k7v motherboard. I had cvsupped to 4.1-stable this monday night. I was dialed into my ISP, when my machine became sluggish. The console was spitting "microtime going backward" messages as fast as my video board would allow. Under the flood I was able to shut down most applications and type "reboot" in a root shell I happened to have open. The machine came back up, but my mouse (logitech cordless) was crippled and spitting out psmintr out of sync errors at me. An hour of power off eventually cured the problem. Anyone on this list who can explain what this microtime problem is about? I used to be able to reproduce it by running bonnie on my disks. I might do that again this weekend, if I find the time. Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. [Douglas Adams] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: audiofs mixing audio and data tracks
> > that way you could mount each track with whatever fs it > supported. > Same thing as I proposed, I guess. Am I right in thinking that a cdrom can have at most one data track? In that case, I'd suggest assighing that track a standard device node. That way I could just mount the data track of a cdrom, without worrying if that's track 4 or track 1. Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: audiofs mixing audio and data tracks
> > I can't think of any way of accomplishing this without > either: > 1) Combining the code for AudioFS and CD9660, as both > require access to the mounted device, and hacking them > to respect each other, or > 2) Hacking the ATAPI-CD and SCSI-CD drivers to bits and > teaching them about the various regions on the CD. > I'm a little surprised that the functionality of accessing a track on a digital storage medium and doing stuff like getting a directory listing out of a track are in the same chunk of code. I lived under the impression that there were some layers of abstraction between those two. I guess not. I learn a little every day. Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
audiofs mixing audio and data tracks
Dear All, I'm not sure if I'm off into the woods on this one, but I'm sure you will correct me. :-) Could you perhaps make it so that all the audio tracks appear als slice 1, while the data track appears as slice 2. Mount data-only cdrom: mount -t cd9660 /dev/cd0s1c -or- mount -t cd9660 /dev/cd0c Mount audio and data part of audio/data cdrom: mount -t cd9660 /dev/cd0s1c mount -t audio /dev/cd0s2c Mount audio-only cdrom: mount -t audio /dev/cd0s2c -or- mount -t audio /dev/cd0c Or, another idea, make the data appear a /dev/cd0c and the audio as /dev/cd0a. (Although I'd agree that this breaks partition conventions, perhaps /dev/cd0d is better for data tracks, "c" referring to the whole disk) This way, as a sysop you would not care if it's an audio or data only cdrom, or if it has both. Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. [Douglas Adams] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: CRACK - Dreamweaver
Hi Richard, > > Can you tell me where I can get Crack for Dreamweaver 3 ?/ > http://www.macromedia.com/software/dreamweaver/buy/ They'll even send you a pretty box and some books. Kees Jan PS. I think you're confusing the terms "cracker" and "hacker". = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Funky scheduler stuff under heavy I/O.
> > both the Master and Slave drives on the first channel of > each controller are about 200MB's ahead of the master > and slave drives on the second channel of each > controller, and the gap is growing. > Umm. This sounds more like your controllers are doing this. You could stick in another two IDE controllers and see if that cures the problem. You have one of those 10 PCI bus boards, right? :-) Come to think of it, that would still not show if it's the hardware or FreeBSD dropping the bucket. Just curious, but is using vinum actually improving performance? (Assuming that's what you're trying to achieve) I've bonnied two Maxtor DiamondMax 15GB drives in my box, and I found that when I stripe them, performance drops to 15MB/s, whereas a single Maxtor will fling 25MB/s onto the platter. Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: mbuf re-write(s): v 0.2: request-for-comments
> > Its not really "wonderful" to those that have already > implemented something using the old method. > Unless you get to rip out your own workarounds for the missing functionality and get someone else to support those for you. I think I'll call it delegation through innovation. :-) Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: VM coloring description in NOTES
> > > > currently -> candidate > > > PQ_HUGECACHE PQ_CACHE1024 > > > PQ_LARGECACHE PQ_CACHE512 > > > PQ_MEDIUMCACHEPQ_CACHE256 > > > PQ_NORMALCACHEPQ_CACHE64 > Hmm. At boot time, the BIOS displayes this square box with a lot of grub in it that FreeBSD then proceeds to rediscover. Is there no way to whack the BIOS into submission and have it cough up the cache size? It's probably going to be BIOS-vendor specific *sigh*. Then again, perhaps it would be nice to have an interface to some of the more widely used bioses. I image you could pry all sorts of tuning information about the machine from its clammy little hands. Cache size, cache scheme, memory type. There were earlier comments on FreeBSD taking over the task of the BIOS. Food for thought. :-) Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
FW: Cooperative site-sitting
Hi Colman, I'm replying to you through -hackers, because I got the following when I e-mailed you personally: The original message was received at Fri, 23 Jun 2000 13:20:35 GMT from hermes.research.kpn.com [139.63.192.8] - The following addresses had permanent fatal errors - <[EMAIL PROTECTED]> - Transcript of session follows - 554 5.0.0 MX list for antonio.office.thecia.ie. points back to online.thecia.ie 554 5.3.5 <[EMAIL PROTECTED]>... Local configuration error > > Sounds like a good idea: I'd probably be able to set-up a > front end for it if we got some interest. I'm sure I have > some old dating agency code around here! > That would be ideal. Perhaps you could dig it up and sort'a set it up, so that we can see if there's interest? There's good irony in using dating agency code to team up sysops. :-) > > We're a small ISP in Dublin, Ireland. > You should be selling the monitoring service to your customers, not host a cooperative one. :-) Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Cooperative site-sitting
Dear FreeBSD Hackers, I've been walking around with a wild idea again. I'm worried that this mail is going to be a bit of a long rant. Sorry in advance. I've been looking at those sites that can monitor the availability and performance of your web site. For a few bucks per URL, you can receive a monthly e-mail about how much your site has been visible across the 'net. Someone wrote a HTML/cgi wrapper around ping and traceroute and is making good money on that. Good for them of course. The better ones will have pingservers at strategic locations on the 'net, so they can even tell you in more detail why your site was not reachable. The clever ones don't actually have much hardware, but pay you a few bucks if you run their ping server daemon, that watches other sites. Anyway, we have many bigger and smaller web admins on this mailing list. Perhaps some of us could engage in a joint effort to watch eachother's sites, instead of having others make money off all of us. If my site goes down, you send me an e-mail, or a fax or a page or whatever, and if yours goes down, I do you the same favour. No money involved. You'd team up with three or four web masters in different time zones, so that you have 24-hour human-assisted coverage. You exchange phone/fax/page numbers and agree to be friends even if someone screws up. After a while, when you're comfortable with your new-found web-pals, you may even give them ssh access to a rebootaccount. This may save you a wakeup call to frob that big red knob. For bigger companies, this is a bad idea, because they are already doing their own monitoring. *cough* Home users don't participate because they have a life. :-) Ideal candidates are for example schools and smaller, pressed-for-cash companies or non-profit organisations. Companies that have a sysop for eight hours a day, but none during off-hours. Places where webmasters come in in the morning to discover whether their site is up or down. Just a thought. I will go back to work now. :-) Kees Jan = TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. [Douglas Adams] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: ACPI project progress report
> > Just a moment. You talk about doing a `Save-to-Disk' (incl. > system halt), turning power off, maybe adding some hardware or > moving the machine to another location, then switching on again, > restoring the system context, and the machine will proceed as if > nothing had happened, do you? > I think FreeBSD supports something similar already. It's a little outdated by modern computing standards, but it used to be called a "halt" or a "reboot". Advantage of those outdated concepts used to be that you could replace your /kernel, adding for example a new driver for the new hardware, or after a cvsup. Just curious, but are you planning to add such functionality to S4? :) Kees Jan == Everyone is responsible for his own actions, and (people tend to forget this) the effect they have on others. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: [Oz-ISP] FreeBSD and the forces of darkness. Real religious w ars!(fwd)
> > "Even the site talks about a deamon being 'unleashed' in you > computer blah." > Have you perhaps pointed out that Linux is full of daemons too? If you listen closely to the box you can hear them chitter amongst eachother. Inetd for example, a.k.a. "The Mother of All Deamons". Phew, they don't come much worse than that. It's even known to spawn others. I won't even mention the http deamon and maybe even the talk daemon. No telling who it talks to. At least BSD puts a clear warning sticker on the box, whereas Linux daemons tend to hide in animal guises. Penguins, I believe. Anyway, there's nothing to worry about. If your box is CE compliant it will shield the outside world quite efficiently from what's inside. Kees Jan == Everyone is responsible for his own actions, and (people tend to forget this) the effect they have on others. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Looking for a way to test Performance.
> > I'm installing alot of squid proxy servers with Freebsd > my servers config is like this > Intel 600MHz Dual > 1G Ram > 3*18G Ultra2 (seagate Cheetah) disks.. > > I'm using vinum, and it is running transparent proxy with wccp V1 > > I want to make sure that I'm getting all of the power the box > can provide.. > is there a tool that can help me in determining that.. > Hmm. Tools? Sure, your own eyes. Have a peek in "System Performance Tuning". Amazon.com, $25,=. Old as it is, it will teach you how to watch a BSD system, and how to interpret the output of top and vmstat and friends, down to the HDD led that's on the front of your box. IIRC, the examples assume SunOS 4 or VAX. Fact is that it gives you a fundamental understanding of measuring performance of BSD systems. It covers CPU, memory, disk and network performance each in their own section. I found that I could use the book even for Windows machines. Kees Jan == Everyone is responsible for his own actions, and (people tend to forget this) the effect they have on others. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Comments on Athlon [motherboards] sought..
> > > EPoX == trash. Avoid like the plague. > > Buy EPoX. They're good. > > > ASUS K7v == good. > > ASUS K7v == slow. > > May 3 08:00:02 wantadilla /kernel: microuptime() went > backwards (65202.831743 -> 65202,804412) > In fact, I've seen the microuptime stuff doing bonnies on FreeBSD 4.0-release with my Asus K7v. I've cvsupped to 4.0-stable, rebuild and not seen the problem since. (and yes, I have run bonnie) I like my Asus. I've always used Abit before this. The Asus is just more complete. A few jumper caps and all the cabling you need. It comes with four USB ports. Too bad I don't have any USB hardware yet. Kees Jan == Everyone is responsible for his own actions, and (people tend to forget this) the effect they have on others. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
PnP OS (was: S5933 PCI Adapter..??)
Hi Mike, > > If you don't have "PnP OS" set, and the card doesn't get > resources assigned, this means that there's a resource > conflict that prevents the card from being configured. > That leaves me wondering, would FreeBSD qualify as a "PnP OS"? I mean, in my BIOS setup, would I answer "yes" or "no" to the question "PnP OS?". (Asus K7V, Award BIOS, if that makes a difference). Kees Jan == Everyone is responsible for his own actions, and (people tend to forget this) the effect they have on others. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: system hangs...
> > We have made some kernel changes. And accordingly we are > testing the changes using some user level daemon. After > sending some packets, the system hangs. The number of > packets sent before the system hangs varies from time to > time. > What kind of changes? What kind of packets? What kind of deamon? What kind of kernel? > > Could some body tell me how to know what is happening? How > do I find out the reason for hanging? Is there anyway to get > such information through some core dump? I have enabled > taking dumps and it is dumping when the system panics but > not when it hangs. > You can make the system panic manually, and then you have your kernel core. As for how to know what's happening: printf() is your friend. > > Is memory leakage can cause a system hang? If so how do I > find out that there is a memory leakage? > There are many good books and web sites that cover basic debugging techniques. You have to provide a *lot* more information than this. We can only help you if you are able to produce some detailed description of your problem. If you can't tell sitting behind the box, how are we supposed to know what you've done wrong? Kees Jan == Everyone is responsible for his own actions, and (people tend to forget this) the effect they have on others. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: 4.0 - Isa devices not being probed
Hi Dennis, I can see that you disagree with some of the design decisions that have been made. However, your tone makes that people will not listen to what you say, but hammer into your person instead. I'm not quite sure what you are trying to achieve by trampling all over people's shoes like this. I'm quite surprised you haven't gotten yourself filtered yet. As for the technical discussion: I'm not knowledgeable in that area. Since FreeBSD implements it the way it does, I have all confidence that it is a good way. Kees Jan == Everyone is responsible for his own actions, and (people tend to forget this) the effect they have on others. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Creating a system to boot 4 different OS types.
Hmm. I think booteasy will allow you to put FreeBSD on a second disk. That way you can have n-way booting, where n is limited only by the number of OS's on the market today. :-) Kees Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: smb printer trouble
Perhaps there are some invisible spaces after some of the backslashes? Kees Jan == You are only young once, but you can stay immature all your life > -Original Message- > From: Charlie Root [mailto:[EMAIL PROTECTED]] > Sent: dinsdag 16 mei 2000 20:39 > To: [EMAIL PROTECTED] > Subject: smb printer trouble > > > I wrote a simple filter to print to an nt print queue through > the smbclinet. It tests to see if the file is postscript or > text, and if it is text it sends a control code to tell the > printer to do the lf->crlf conversion. > > My problem is that the '\' escapes in the first line get clobbered. > for example, if I print this printcap: > > begin printcap > lp:\ > :sh:\ > :lp=/dev/lpt0:\ > :sd=/var/spool/output/lpd/lp:\ > :lf=/var/log/lpd/lpd.log: > > lplaser:\ > :sh:\ > :lp=/dev/null:\ > :if=/root/filters/smb-filter:\ > :sd=/var/spool/output/lpd/lplaser:\ > :lf=/var/log/lpd/lpd.log: > end printap > > the entire entry for "lp" will be on one line, but the "lplaser" > entry will print out like it is supposed to. > > I know why it is doing it, however I don't know how to fix it. Any > help will be appreciated (script is below). > > Thanks, > James > > begin smb-filter > #!/bin/sh > > # Input filter to print to a NT print queue, requires smbclient. > # > # Author: James Halstead, e-mail: [EMAIL PROTECTED] > # > # Read stdin to a temp, make sure to determine the print > type, then use > # smbclient to print to the nt queue. > > > SERVER= > PRINTER=cw > TEMP=/tmp/smbprint > > TEMP=`mktemp -q $TEMP.XX` > > read firstline > first_two=`expr "$firstline" : '\(..\)'` > > if [ "$first_two" != "%!" ]; then > printf "\033&k3G" > $TEMP > fi > > #lets see, copy the firstline to temp, cat the rest to the temp, > # make one ugly command to print the file to the smb printer then > # rm the temp file. > > echo "$firstline" >> $TEMP && cat >> $TEMP &&\ > /usr/local/bin/smbclient $SERVER\\$PRINTER -UGUEST -N\ > -c"print $TEMP" &&\ > rm -f $TEMP >/dev/null && exit 0 > > exit 1 > end smb-filter > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
3.4 make world dies on groff
Dear Hackers, I have the problem that make world does not grok groff. Please find the final messages of the compilation at the end of this e-mail. I've cvsupped last night, just before the "make world", so I guess my source tree must be sane. I've disabled softupdates, and -pipe, but that makes no difference. I assume that something in my box is seriously broken. I don't think it's hardware, because it dies reproducably at the exact same spot under different loads (i.e. I ran some other compiles in parallel with the make world, and I saw no other strangeness.) What can I do to get groff to build for me? Kees Jan == You are only young once, but you can stay immature all your life c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/env.cc c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/node.cc c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc: In function `static void input_stack::end_file()': /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:56 6: Internal compiler error. /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:56 6: Please submit a full bug report to `[EMAIL PROTECTED]'. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Motif porting discussions on -java
Just to let the non-java hackers know, there is some Motif porting discussion going on on freebsd-java. You may want to have a looksee there if you're working on Motif too. :) Kees Jan == You are only young once, but you can stay immature all your life To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Can we use this for the JDK? (was: Motif goes open source)
Dear all, Is there someone on this list who's into the finer points of copyrighting? I would like to know what the implications are of this for the soon-to-be-coming native FreeBSD JDK port. In what form is Motif going to be available to the general FreeBSD developer? Am I going to find /usr/ports/x11-toolkits/motif anytime soon, or is this going to be more complicated than that? In what form would we have to distribute this with our JDK port (Java/SCCL-legalities aside)? Kees Jan == You are only young once, but you can stay immature all your life To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
