Re: C coding editor
On Sun, Feb 23, 2003 at 10:17:16AM -0800, Wes Peters wrote: I completely utterly fail to understand why some young developers attach some sort of romance to writing code on an 80x25 screen, when all the haxxors my age or older waited (or slaved away) for years, even decades, to get something better and more flexible. Maybe it's cause some of us use something other than 80x25 for a text console :-D Of course I'm still waiting for a console port of DESQView. *giggle*. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sendmail + auth + ssl + freebsd
On Wed, Dec 19, 2001 at 09:26:54PM -0500, Leo Bicknell wrote: If no one else has figured this mess out, I'll do it and write a page for the handbook. If someone else has, please clue me in, and if necessary I'll still write that handbook page. :-) It would be very nice if it was simple to make FreeBSD sendmail SSL and authenticate against the password file. Well, my first suggestion would be to use postfix. It's *very* easy to setup with SASL auth and SSL. It uses the Cyrus libraries and OpenSSL. Go out and use your favorite search engine. I just used google and turned up instructions on the sendmail.org site for configuring it to use the Cyrus SASL libs. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Finding filesizes in C++ for files greater than 4gb
On Wed, Aug 01, 2001 at 10:31:22PM -0400, Joseph Gleason wrote: Alright, I made a mistake. But I did read the man page. Where does it say off_t is 64bits? My mistake was not digging through the include files enough to see what was going on. off_t st_size; /* file size, in bytes */ All it takes is a printf(%d\n, sizeof(off_t)); to figure out how large that is. :^) Or, sure, you could dig thru the headers. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: helping Wietse help postfix on FreeBSD
On Tue, Jul 03, 2001 at 07:42:57PM -0400, Felix-Antoine Paradis wrote: Is /etc/sysctl.conf what you are looking for? No, because that only holds the runtime tuneables. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 2nd ata drive, and resolv.conf options
On Fri, Jun 22, 2001 at 10:43:44AM -0400, Bill Moran wrote: ad1: 73308MB IBM-DTLA-307075 [148945/16/63] at ata0-slave UDMA100 If it's any help, I'm using that exact same drive currently and it's sort of working. I'm having trouble with random panics on this system, but I haven't yet isolated as to what's causing them. There may be a problem with this drive, but I haven't isolated it yet to be sure. Well I've got this: ad0: 29314MB IBM-DTLA-307030 [59560/16/63] at ata0-master tagged UDMA33 and it's working just peachy. Well, it's spitting out read errors, so I'm assuming it's almost dead.. but it's still yet to cause any real fbsd problems. You aren't by any chance running an HPT366 based controller are you? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 2nd ata drive, and resolv.conf options
On Fri, Jun 22, 2001 at 07:39:16PM -0400, Bill Moran wrote: It's on an ASUS A7V133 mobo. The controller is Promise ATA100. The one that I'm having trouble with is running in UDMA100. Is it possible that UDMA100 doesn't work right? Thoughts? I imagine it's possible, but it would seem unlikely to me, since the drives are otherwise pretty high quality. Perhaps it's a buggy firmware revision. Then again, I've never tried anything at ATA66, and that was with the buggy HPT366. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Your new web site
On Thu, Jun 21, 2001 at 04:40:44PM +1200, David Preece wrote: 1-877-230-7268 Is anyone close enough to drive round and have a quiet word? Netiquette for instance. Or asking for trouble. Well if you're in the US, why not call him? The further away the better. :^) - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Article: Network performance by OS
On Sat, Jun 16, 2001 at 04:31:41PM -0400, Albert D. Cahalan wrote: I guess it's fair to shove Linux deep into swap (as pro-FreeBSD benchmarkers always do), but not fair to make FreeBSD handle a large directory? Well... no. This test did stress FreeBSD's ability to handle large directories, and that's fine. Especially since they didn't even bother to compare it to ReiserFS, which should be much better. However, they could have / should have leveled the playing field with one very simple tweak: *Mount all filesystems async* The tests merely tested the effect of the disk's ability to handle tagged queuing and the disk's ability to cache stuff. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD ld.so performance ?
On Wed, May 09, 2001 at 08:02:08AM -0700, Arun Sharma wrote: http://www.suse.de/~bastian/Export/linking.txt Has anyone done a comparative study ? Not really, however even with the recent rtld patches.. KDE apps aren't very quick on their feet. This leads me to believe that the most room for improvement is left in g++ and/or gnu ld, not the rtld. Of course reducing the number of shlibs that KDE requires would go a long way towards creating faster startup as well.. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Trouble with HPT366
On Mon, Apr 30, 2001 at 12:08:47AM +0200, Torbjorn Kristoffersen wrote: Yes, I'm using the 80-conductor cable I got with the motherboard (ABIT BE6 with HPT366 onboard). Is the cable connected properly? The blue connector must be on the motherboard end.. Are you sure Leenuchs is using ATA66 speeds? Anyhow, I'd be careful with the HPT366, I've had nothing but trouble with my HPT366 based card. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Mounting partitions with RO flag
On Sun, Apr 08, 2001 at 09:13:15PM +0200, Attila Nagy wrote: So I am wondering, why the unices block mounting an already mounted partition read only again. Have you considered using ACLs perhaps? Sure it's not in -STABLE, but it's a thought.. - alex 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
On Tue, Mar 13, 2001 at 12:51:19PM -0800, Alfred Perlstein wrote: Well... when you 'gzip -9' something, it just takes longer, it doesn't sometimes corrupt your data (afaik). Hmm. gzip seems to be pretty good about those things. I guess it's one of the few GNU programs to be that way. :^) So it sort of makes sense for people to assume that when the compiler advertises certain things that it's going to do it perhaps not in the most effecient manner, but at least correctly. Yes, hello pipe dream. However, even the pgcc web page describes -O2 as safe. I guess I'll be playing around to see which bits generate incorrect code soon, since this is all so tempting. What just popped into my mind was that maybe some sort of check for stuff like "-fomit-frame-pointer" in CFLAGS should be made in buildworld, since it will cause failure if you build profiling libs. Other thoughts include how -O2 is bombing out make world. I know in my dealings with kde I've had lots of trouble getting gcc to emit decent debug info (depending on the code, -gstabs+, -ggdb3, etc would spit out internal errors). SO are the gcc developers i imagine. :) Pfft. Damnit I want software that I don't have to pay for, to work perfectly every time, and that I don't have to contribute to erm.. Yes, scanning thru the ML leads me to believe some of these optimizations are pretty much untested. Which is kinda funny, since the ia32 bits are the most used ones or so it seems. - alex 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
On Wed, Mar 14, 2001 at 02:58:40AM -0800, David O'Brien wrote: I won't even to there... Well, the only reason I mentioned it.. was that the pgcc folks don't seem to be too delusioned about the dangers. -ON (N 2) is regarded as at least possibly in danger of generating incorrect code. Not untested -- but you should go grab a graduate text on compiler optimizations and familiarize yourself with the complexity of the problem. Care to recommend any starting places. You've piqued my interest. If hello_world.c showed a problem with an optimization, I guarantee it would be fixed. Of course depending on the problem. The current test case of holding up the entire FreeBSD kernel as showing an optimization problem doesn't cut it. If you care to trim it down to a single module showing the problem Well I've just made buildworld with CFLAGS = "-O2 -march=pentiumpro -malign-double" from a world built with the same flags. Not so sure of any performance impact however. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
On Thu, Mar 08, 2001 at 02:48:12PM -0500, Dennis wrote: No. Keeping supported drivers up to date is part of the business of distributing an OS. Thats what "supported" implies. The driver is out of date. Noone is looking for a feature here. We just want it to work. Dennis, dear Dennis. I recently re-subbed to -hackers and one of the first posts I caught was the beginning of one of your more recent threads. Go away. I kept telling myself I wasn't going to comment, but I will. Stop attacking people. You're not contributing code, you're not contributing help, you're just out there attacking people and proclaiming you know the only direction that FreeBSD should go in. Go away. Publically blaring your vague rants is really becomming irritating. Go away. If you feel you are obligated out of some misguided sense of greater good to rant, by all means do so. However, there *ARE* some of us who aren't intimate with your fxp problems. Like me: zippy:~#dmesg|grep fxp fxp0: Intel InBusiness 10/100 Ethernet port 0xec00-0xec3f mem 0xdb00-0xdb0f,0xdb10-0xdb100fff irq 11 at device 10.0 on pci0 fxp0: Ethernet address 00:90:27:d1:83:6a Works well for me. However you rant, and then state the people who should know already know the details. You rant that this shouldn't be brought up again. Okay, so don't do it Dennis. That's fine if the people who should know already know, so why bother the other half? Go away. You've got a valid problem. Go away. As such, you must learn to properly express this problem. Go away. Perhaps you just haven't realized that people won't care what you want if you demand it in a childish way. For the majority of the fxp consumers out there, the fxp driver works just fine. Go away. You're not obligated to use FreeBSD, nor are you obligated to harass the people who spend their time working on it. If you've got a problem, open a PR, submit appropiate details, leave out the heartfelt emotion, and let those who can fix it. Go away. Or maybe you should take up kernel hacking in your spare time and put up some code. Go away. Or you could go away. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
On Thu, Mar 08, 2001 at 01:03:48PM -0800, Brooks Davis wrote: If it becomes a problem, the most expensive 10/100 nic you could possiably buy is less the $100 bucks so worry about it then. You've never tried to find a NuBus 100baseTX adapter have you? About $150 a pop, new. The Asante doesn't do full duplex, is based on the original SMC chipset, not sure about the only other option, the Farallon card. But you were referring to PCI cards, right? ;^) - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How to make *real* random bits.
On Tue, 1 Aug 2000, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED] e, Paul Herman writes: But, if you are gathering a geek lobby to convince Intel to have an onboard geiger counter, you just might have a new member ;-) "Cesium-137 inside" Yeah, it does have a ring to it, doesn't it ? :-) Or a glow... - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ELF rtld and environment variables...
On Mon, 24 Jul 2000, John Polstra wrote: Glad you liked the idea! :-) Well imagine if Joe user gets a Linux binary or a.out binary to run. Bam, it doesn't run, and one'd have to check each file, and unset the variables. Or forgo any user-feedback. :( Well, there is a different reason for each of the dynamic linkers. FreeBSD ELF: It's required by the ELF specification. FreeBSD a.out: Backward compatibility. Linux ELF: Because it's part of Linux and that's just what it does. I can understand the logic for using said variables for FreeBSD ELF stuff, but for the rest of them, I figure we're not actually the native environment. Hmm. Anywho the topic of caching shlib symbols came up in discussion as a possible way speed up loading of programs. Makes me wonder if it would be worth it.. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
ELF rtld and environment variables...
So I find myself playing more and more with KDE, and more and more enjoying the nifty little hacks it does. But, most of the hacks depend on shlibs, including the requisite libtool horrors. Anyhow, one of the more "useful" features involves "pre-loading" a shared lib to replace a few X functions, so that once an application starts, you get an icon in the task bar that spins until the application maps its first window. Their other hack is for loading various applications contained in shared lib form, and involves setting LD_LIBRARY_PATH. This works great if you're using your average ELF binary. However, if you're like me and still somewhat attached to the idea of using Navigator which is an a.out binary (perhaps the only one I still have left), you're SOL as the variables tweak the a.out RTLD too. This perhaps doesn't sound too bad, until one realizes that the said shlib objets are ELF, and the a.out rtld doesn't grok any of them, meaning that one has to fire up an xterm, unset the said variables to start netscape. My question is this: is there any way to make the a.out rtld ignore these variables? 'Course after I figured this out, I realized I should have just used konqueror, and well I did (damn it's gonna give mozilla a run for its money... SSL equiped too). - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ELF rtld and environment variables...
On Mon, 24 Jul 2000, John Polstra wrote: No, there isn't. I don't plan to do anything more with the a.out dynamic linker, as I consider it obsolete at this point. I'd suggest making a script "run_aout" that looks something like this (untested): Uck. BTW, it's generally not a good idea to set either of those environment variables globally. You should only set them in scripts which run specific executables that need them to be set. Besides the a.out problem, they affect programs run under Linux emulation too. Yes, but this is intended to be used for all programs (not an awful idea IMO, questionable implementation, but what other alternatives are there?). It's designed to give the user feedback that an application has been started so one doesn't double click on an icon multiple times. I'm curious, why do a.out/FreeBSD-elf/Linux-elf programs all respond to the same variables? Sure it's perhaps a consistant interface, but wouldn't somthing like LINUX_LD_LIBRARY_PATH and/or AOUT_LD_LIBRARY_PATH make more sense? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Whatever happened to TenDRA?
Hmm. So I've compiled the TenDRA port, and I'm toying around with it, trying to get it to compile Qt (and perhaps gnu's libstdc++), but not suprisingly it seems to dislike some of the more basic (QList and QString and other template stuff) code in Qt, meaning even something as simple as moc can't be compiled. So off I went to the TenDRA web page, but it seems to be down (can't connect, etc). Has development on this compiler stopped or what? - alex who would like to see tcc as the base compiler someday... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Missing keyboard symbols
On Fri, 24 Mar 2000, Doug Barton wrote: Heh... You know, I started to type out something to the effect of, "... space bar. FreeBSD has been mapping the Space Bar to the Any key combination since about 1992 to get around the restrictions of modern PC keyboards." But I thought there was an outside chance that this was a serious question, and I didn't want to run the risk that the poor doofus would repeat that statement in front of someone with a clue... A serious question from Mr. Override? Uh yeah :) - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Re/Fwd: freebsd specific search
On Thu, 3 Feb 2000, Mike Bristow wrote: True; but linux has support for a bigger variety of soundcards (my Win98^H^H^H^H^H^HEverQuest machine now has a Live! in it; supported under Linux but not under FreeBSD AFAIK; so the other half of the disk may turn turn into ext2 rather than ffs) Well if you buy esoteric or just cheap hardware... I generally get the feeling that `Workstation Hardware'[1] has a better chance of being supported under Linux than FreeBSD. I may be talking rubbish, though ;-) Cheap hardware has a better chance of being supported. If you stick with the name brand stuff, you could piece together a box that'll work great and work great with FreeBSD. Me, I've got my Micron PC (which was a pretty good deal when I bought it), and the onboard sound is AFAIK supported by that comercial Linux sound driver, but nothing else. The box also came with an AWE64, therefore I'm happy. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Re/Fwd: freebsd specific search
On Wed, 2 Feb 2000, Michael Bacarella wrote: Not to start a flame-fest or anything (but who doesn't love em?), I hear the above quite a lot. I'm under the firm belief that a decent sys admin can rub either system to do whatever they want it to do. Not that I am questioning your abilities. I just get the "yeah, Linux is good, but just try to use it in a production environment and you'll understand" a lot. Needless to say I think that FreeBSD makes a great desktop environment too. What contributes to server sanity also makes things much less confusing for a desktop user too :) - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Learning the FreeBSD Kernel
On Sun, 23 Jan 2000, Jeroen Ruigrok/Asmodai wrote: A possibly better alternative is to find a device which isn't currently supported by FreeBSD and write a driver for it. This would have the advantage that the work would also be a contribution to FreeBSD. The question that I can't answer here is: what would be an appropriate device? Definately not an ethernet card. *g* Seems no-one can keep up with Bill Paul in that aspect. =) You could try usb devices and contact Nick Hibma for his expertise on that area. Also make sure the vendor is not problematic with handing out documentation. Intel and Motorola are good examples of companies who have pdf's available for download. Well hey. If you're looking for something rather esoteric, I've got an ancient Logitech handheld scanner that I wouldn't mind seeing a driver for. There's supposed Linux drivers out there (didn't try too hard, but it didn't work for me) and a Win 3.1 driver that doesn't work on Win95 or newer. I'd be willing to FedEx it somewhere in the states if you're hard up for something to write a driver for :^) - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kstat - an API for gathering kernel stats
On Thu, 4 Nov 1999, Matthew N. Dodd wrote:
On Wed, 3 Nov 1999, Arun Sharma wrote:
A user program makes a system call with this string "cpu.system" to get
the current value of user/system/nice time etc.
How is this different from doing:
# sysctl -a | grep load
vm.loadavg: { 0.15 0.09 0.04 }
How is that different from doing:
sysctl vm.loadavg?
- alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Whither makefiles for src/crypto/telnet/* ?
On Sun, 15 Aug 1999, Bill Fumerola wrote: On Sat, 14 Aug 1999, Wilko Bulte wrote: Yeah... isn't it time you Yanks got together and stormed that Trade Dept? I mean, if you can get excited over a few wooden crates containing tea... The federal agents carry sub-machine guns, this is less workable now-a-days. And we have a reliable postal service now too. So you could either push a bunch of employees over the edge, or start a letter writing campain. E-mail is much easier to ignore than say a barrage of letters. - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: cvs
On Thu, 5 Aug 1999, Chuck Robey wrote: Can someone tell me how to make a cvs archive work for users that aren't the owner of the archive, the way that it works on Freefall? I *am* doing this for a cvsup maintained FreeBSD archive, but not freefall, and I need to get one user, who is not the archive owner, to be able to be able to do checkouts and diffs (no source changes, but it needs to be able to lock directories for checkouts). Uhm, I think the CVSROOT/writers and CVSROOT/readers file might do what you're looking for. But this only works with the pserver. - alex Experience something different With our new imported dolly She's lovely, warm, inflatable And we guarantee her joy - The Police To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: quad_t and portability
On Fri, 6 Aug 1999, Don Lewis wrote: Why not off_t, which should be portable and scale properly with the maximum system file size. Then the only problem is figuring a portable means of printing the result ... sizeof() perhaps? - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: m68k Support in FreeBSD (old thread)
On Fri, 6 Aug 1999, James Howard wrote: I realize this. The comment stems from the fact the guy I am doing this for would prefer FreeBSD for his Macs if the opportunity arose. I think I'll bring it into work on Monday and install NetBSD over the net then. Ehm, this isn't possible in the same way that it is w/ FreeBSD. Basically, you need to grab the booter, the installer, and mkfs (all MacOS programs), then download the appropiate kernel, base distrib, and etc distrib. Not quite as slick, but it works. P.S. I don't think it's really called MacBSD anymore, rather NetBSD, or OpenBSD, or Linux (depending, obviously, on what you're running). - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: m68k Support in FreeBSD (old thread)
On Fri, 6 Aug 1999, James Howard wrote: Yeah I know, it is just easier to download those chunks over the T1 than it is over a 28.8. Which is what I was refering too :) Unless you've actually tried this on a Mac, you have no idea how much of an understatement this actually is. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs
On Thu, 5 Aug 1999, Chuck Robey wrote: Can someone tell me how to make a cvs archive work for users that aren't the owner of the archive, the way that it works on Freefall? I *am* doing this for a cvsup maintained FreeBSD archive, but not freefall, and I need to get one user, who is not the archive owner, to be able to be able to do checkouts and diffs (no source changes, but it needs to be able to lock directories for checkouts). Uhm, I think the CVSROOT/writers and CVSROOT/readers file might do what you're looking for. But this only works with the pserver. - alex Experience something different With our new imported dolly She's lovely, warm, inflatable And we guarantee her joy - The Police To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: quad_t and portability
On Fri, 6 Aug 1999, Don Lewis wrote: Why not off_t, which should be portable and scale properly with the maximum system file size. Then the only problem is figuring a portable means of printing the result ... sizeof() perhaps? - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: m68k Support in FreeBSD (old thread)
On Fri, 6 Aug 1999, James Howard wrote: I realize this. The comment stems from the fact the guy I am doing this for would prefer FreeBSD for his Macs if the opportunity arose. I think I'll bring it into work on Monday and install NetBSD over the net then. Ehm, this isn't possible in the same way that it is w/ FreeBSD. Basically, you need to grab the booter, the installer, and mkfs (all MacOS programs), then download the appropiate kernel, base distrib, and etc distrib. Not quite as slick, but it works. P.S. I don't think it's really called MacBSD anymore, rather NetBSD, or OpenBSD, or Linux (depending, obviously, on what you're running). - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: m68k Support in FreeBSD (old thread)
On Fri, 6 Aug 1999, James Howard wrote: Yeah I know, it is just easier to download those chunks over the T1 than it is over a 28.8. Which is what I was refering too :) Unless you've actually tried this on a Mac, you have no idea how much of an understatement this actually is. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: m68k Support in FreeBSD (old thread)
On Thu, 5 Aug 1999, James Howard wrote:
Prior to posting to -hackers, I had emailed him, I tried again after
receiving this message and again, no response. (I used [EMAIL PROTECTED])
Is there a better way to contact this individual? Does anyone have a copy
of the port?
I really don't want to have to install NetBSD on this Mac :)
Worse things could happen :^)
I haven't heard from him either (since I sent out my first inquiry July
19th). But all things considered it should be a bit easier to port
NetBSD/mac68k to FreeBSD than it would with the Alpha bits, considering
that you can setup a m68k-aout cross compiler pretty easily ('course easy
is a relative term).
FWIW, NetBSD works quite well on mac68k, but the biggest problem so far is
the lack of virtual consoles (dt is awful).
- alex
You better believe that marijuana can cause castration. Just suppose your
girlfriend gets the munchies!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: m68k Support in FreeBSD (old thread)
On Thu, 5 Aug 1999, James Howard wrote:
Prior to posting to -hackers, I had emailed him, I tried again after
receiving this message and again, no response. (I used gus...@alaska.net)
Is there a better way to contact this individual? Does anyone have a copy
of the port?
I really don't want to have to install NetBSD on this Mac :)
Worse things could happen :^)
I haven't heard from him either (since I sent out my first inquiry July
19th). But all things considered it should be a bit easier to port
NetBSD/mac68k to FreeBSD than it would with the Alpha bits, considering
that you can setup a m68k-aout cross compiler pretty easily ('course easy
is a relative term).
FWIW, NetBSD works quite well on mac68k, but the biggest problem so far is
the lack of virtual consoles (dt is awful).
- alex
You better believe that marijuana can cause castration. Just suppose your
girlfriend gets the munchies!
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: Solution for mail pseudo-users?
On Tue, 3 Aug 1999, Markus Stumpf wrote: I just don't see any justification in hacking away at all of your software to bypass the passwd database. What is gained? If you have 10+ users you'll run out of UIDs (see recent thread). I find it hard to believe that handling 100,000 users on one box is a good idea in the first place. Also you'll have to run the script to allow users to change passwords as root, which you probably will NOT want to do (same for adding/ deleting/changing users) So with your setup, any user can add/delete/modify existing users? Yeah, that's secure. Also with 3+ (maybe even with 1+) users each rebuild of the passwd database will become SLOW and you have to take care about locking and such ... been there, tried it, didn't like it. Yes, but with 100k+ users, a database (that requires slow rebuilding) is faster to find random records in than a flat text file. In fact, perhaps you should have instituted some sort of cron'd rebuild (once every 30 minutes for instance), and then queued the changes, so as to prevent users from frobbing in an incorrect manner. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Solution for mail pseudo-users?
On Sun, 1 Aug 1999, Mike Hoskins wrote: As usual, there's more than one way to skin a cat. And as always a bloodless vegetarian way too :) I just don't see any justification in hacking away at all of your software to bypass the passwd database. What is gained? - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Solution for mail pseudo-users?
Oh yeah, and check out the jail code (sections 2 and 4, I *think* -CURRENT only). - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Solution for mail pseudo-users?
On Sat, 31 Jul 1999, Alex Povolotsky wrote: I'm going to implement a large mail-box, with several hundreds of mail-only users. They should never access anything besides their POP3 mailboxes and change password via (SSLed) web interface. So, I don't want to add all of them to /etc/passwd. The easiest way I can think of would be to add them to /etc/passwd and set their shell and home dir to /nonexistant. Ideally you wouldn't be running any other daemons, so there'd be no real way for them to access files; but the stock ftpd, as well as sshd offer ways to disable access to specific users. Dealing with real users IMO is quite a bit less hackish. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Hey kernel hackers, this is worth a read.
On Fri, 30 Jul 1999, Jordan K. Hubbard wrote: http://features.linuxtoday.com/stories/8191.html A story on upcoming plans for the Linux 2.4 kernel. Since they're going after a lot of the same performance goals we are, it's worth a read. It seems to me that a lot of the features mentioned are already in -CURRENT and some in -STABLE. Hmm. I rather liked this paragraph: Users who connect to Windows shares via SMB will be pleased that there is no longer a compile time option for enabling bug workarounds for Win9x. Instead, Linux 2.4 will be able to detect the type of machine it is connected to and react accordingly. This will make Linux a much better option overall in homogenous networks. :^) - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unsubscribe
On Sat, 31 Jul 1999, kylee wrote: Unsubscribe No. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Hey kernel hackers, this is worth a read.
On Fri, 30 Jul 1999, Jordan K. Hubbard wrote: http://features.linuxtoday.com/stories/8191.html A story on upcoming plans for the Linux 2.4 kernel. Since they're going after a lot of the same performance goals we are, it's worth a read. It seems to me that a lot of the features mentioned are already in -CURRENT and some in -STABLE. Hmm. I rather liked this paragraph: Users who connect to Windows shares via SMB will be pleased that there is no longer a compile time option for enabling bug workarounds for Win9x. Instead, Linux 2.4 will be able to detect the type of machine it is connected to and react accordingly. This will make Linux a much better option overall in homogenous networks. :^) - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Unsubscribe
On Sat, 31 Jul 1999, kylee wrote: Unsubscribe No. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: What good PII/PIII Motherboards for FreeBSD and Celeron CPU's
On Thu, 22 Jul 1999, Adrian Filipi-Martin wrote: I know a lot of people like the ASUS P2B boards, but I've noticed a tendency for the systems to reset occasionally when plugging in a keyboard. I've seen this with both FreeBSD and NT, so I'm considering it a property of the board. If this is a PS/2 style keyboard, don't plug and unplug them when the host is powered up. The PS/2 style stuf seems to be very sensitive to that sort of thing. If it was a USB keyboard doing that... then that would be odd. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: KDE on FreeBSD (missing symbols)
On Wed, 21 Jul 1999, eT wrote: Hi, I noticed that my ld path was using the old libqt in /usr/X11R6/lib and not the new one I have in /usr/local/qt/lib. That would do it too :^) Problem I am getting now is libstdc++ problem: ld.elf complains: libstdc++.so.3: undefined symbol __ti9exception You're compiling something without exceptions (-fno-exceptions). Check again Qt, kdelibs, kdebase. And possibly if you built world recently, check the CFLAGS and CXXFLAGS that were used to build world too. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KDE on FreeBSD (missing symbols)
On Wed, 21 Jul 1999, eT wrote: Hi alex, thanks for the speedy response. I can't find any 'fno-rtti' to start with in the freebsd-g++-shared/static? So, I compiled it without that flag anyway. I will compile qt-1.42 and then recompile the kde sources and see what happens. Any other ideas? The only other thing I can think of is that for some reason your application and your libraries were compiled with different name mangling schemes, usually this indicates different compilers being used (but not always). Make sure to use the same compiler and same flags for the application and libraries. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: KDE on FreeBSD (missing symbols)
On Wed, 21 Jul 1999, eT wrote: Hi, I noticed that my ld path was using the old libqt in /usr/X11R6/lib and not the new one I have in /usr/local/qt/lib. That would do it too :^) Problem I am getting now is libstdc++ problem: ld.elf complains: libstdc++.so.3: undefined symbol __ti9exception You're compiling something without exceptions (-fno-exceptions). Check again Qt, kdelibs, kdebase. And possibly if you built world recently, check the CFLAGS and CXXFLAGS that were used to build world too. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: glibc
On Tue, 20 Jul 1999, Alexander Voropay wrote: glibc has better POSIX locale and I18N / L10N support : - localedef(1) and locale(1) utilities - nl_langinfo(3) XPG-4 function - gettext built-in into glibc Again this is just a handful of functions, that IMO are best not put into libc. Take the dl*() functions. They're not in fbsd's libc, but they're ing glibc. Doesn't mean they're not easily available. Hell gettext *is* a port. Not every app is going to need to be internationalized, not every app *should* be penalized. If you think it'd be easier to port the whole glibc than to port a hand ful of functions, nobody is stopping you :) - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KDE on FreeBSD (missing symbols)
On Tue, 20 Jul 1999, Doug Rabson wrote: You've gotta choose between the lesser of two evils. First, Qt 1.44 is *not* recommended you should use Qt 1.42. Second of all, TT's support of FreeBSD sucks, the FreeBSD port of Qt sucks. TT has enabled -fno-rtti which causes problems for applications (such as KDE apps) that aren't compiled with -fno-rtti. The FreeBSD port still suffers from this, as well as depending on Mesa(?!). With whatever Qt version you're using go into the appropiate configs/freebsd-... file and remove -fno-rtti. Who maintains the FreeBSD qt port? Perhaps you should fix the problems in the port and submit them as patches to the maintainer (and TT). I've been down that road before, and found that it was much less stressful and quite a bit easier to simply add a note to the README file included with the KDE modules; which is what I've done with the rtti issue too. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: glibc
On Tue, 20 Jul 1999, Alexander Voropay wrote: glibc has better POSIX locale and I18N / L10N support : - localedef(1) and locale(1) utilities - nl_langinfo(3) XPG-4 function - gettext built-in into glibc Again this is just a handful of functions, that IMO are best not put into libc. Take the dl*() functions. They're not in fbsd's libc, but they're ing glibc. Doesn't mean they're not easily available. Hell gettext *is* a port. Not every app is going to need to be internationalized, not every app *should* be penalized. If you think it'd be easier to port the whole glibc than to port a hand ful of functions, nobody is stopping you :) - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: KDE on FreeBSD (missing symbols)
On Tue, 20 Jul 1999, eT wrote: Greets .. I decided to compile KDE-1.1.1 for my 4.0-CURRENT. After compiling all (kde-1.1 and qt-1.44) I get the following errors when startx'ing: ld-elf.so complains about not finding these symbols: __ti6QFrame __ti7QObject __ti7Qblahblahblah I pressume there is something wrong with the way I compiled qt-1.44? You've gotta choose between the lesser of two evils. First, Qt 1.44 is *not* recommended you should use Qt 1.42. Second of all, TT's support of FreeBSD sucks, the FreeBSD port of Qt sucks. TT has enabled -fno-rtti which causes problems for applications (such as KDE apps) that aren't compiled with -fno-rtti. The FreeBSD port still suffers from this, as well as depending on Mesa(?!). With whatever Qt version you're using go into the appropiate configs/freebsd-... file and remove -fno-rtti. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: KDE on FreeBSD (missing symbols)
On Tue, 20 Jul 1999, Doug Rabson wrote: You've gotta choose between the lesser of two evils. First, Qt 1.44 is *not* recommended you should use Qt 1.42. Second of all, TT's support of FreeBSD sucks, the FreeBSD port of Qt sucks. TT has enabled -fno-rtti which causes problems for applications (such as KDE apps) that aren't compiled with -fno-rtti. The FreeBSD port still suffers from this, as well as depending on Mesa(?!). With whatever Qt version you're using go into the appropiate configs/freebsd-... file and remove -fno-rtti. Who maintains the FreeBSD qt port? Perhaps you should fix the problems in the port and submit them as patches to the maintainer (and TT). I've been down that road before, and found that it was much less stressful and quite a bit easier to simply add a note to the README file included with the KDE modules; which is what I've done with the rtti issue too. - alex You wear guilt, like shackles on your feet, Like a halo in reverse - Depeche Mode To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: glibc
On Mon, 19 Jul 1999, Per Lundberg wrote: I need a libc 100% compatible with glibc to make porting (from Linux) easier. And, as a side note, I think both FreeBSD and Linux would benefit of having compatible libc:s. I seriously doubt this will make porting any easier. 99% of the porting issues you'll run into, are from a.) lack of sys/types.h being included, or order of headers being included. b.) dependencies on Linux-specific ioctls or syscalls, such as clone, which are not really libc related. c.) dependencies on bugs in glibc. Perhaps porting BSD libc to Linux would be easier? I doubt it. The glibc has been designed with portability in mind (hell, it's purported to run on Irix), FreeBSD's with security and speed. - alex What I am is what I am, What you are is what you are - Edie Brickell (ain't she profound?) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: glibc
On Mon, 19 Jul 1999, Per Lundberg wrote: You think so? Yes. I experience a lot of this when I try to recompile stuff for FreeBSD (most of it are due to lack of a real getopt routine). *sigh* It's quite easily argued that depending on a *NON STANDARD* getopt routine is a bug. AFAIK *ONLY* glibc has the long-getopt crap, and if that's the only thing you're running into, it should be easy enough to rip out the long getopt code, and add a few proper defines and have the standard libc coexist peacefully with the GNU getopt. c.) dependencies on bugs in glibc. What bugs have you found in glibc 2.1.1? Have you reported those to the GNU folks? I personally haven't found any, but I've seen for instance, kcalc is riddled with ifdefs and warnings about floating point precision stuff and RH 5.something due to glibc bug(s). - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: m68k Support in FreeBSD
On Mon, 19 Jul 1999, Brian F. Feldman wrote: Isn't it more a question of whether a proper cross-build system will be available within the time frame that m68ks aren't completely obsolete? Bah! An 040 or 030 powered Mac w/ MacOS makes a decent web browsing, word processing machine; it's an actually useable alternative to an e-machine. Similarlly a 386 or 486 powered FreeBSD machine can still be quite useful even as a small server (admittedly the 68k Mac hardware makes for a piss poor server.. but still). I can't see a 486 or 040 powered machine becomming entirely obsolete until X is required to buildworld. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: glibc
On Mon, 19 Jul 1999, Per Lundberg wrote: I need a libc 100% compatible with glibc to make porting (from Linux) easier. And, as a side note, I think both FreeBSD and Linux would benefit of having compatible libc:s. I seriously doubt this will make porting any easier. 99% of the porting issues you'll run into, are from a.) lack of sys/types.h being included, or order of headers being included. b.) dependencies on Linux-specific ioctls or syscalls, such as clone, which are not really libc related. c.) dependencies on bugs in glibc. Perhaps porting BSD libc to Linux would be easier? I doubt it. The glibc has been designed with portability in mind (hell, it's purported to run on Irix), FreeBSD's with security and speed. - alex What I am is what I am, What you are is what you are - Edie Brickell (ain't she profound?) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: glibc
On Mon, 19 Jul 1999, Per Lundberg wrote: You think so? Yes. I experience a lot of this when I try to recompile stuff for FreeBSD (most of it are due to lack of a real getopt routine). *sigh* It's quite easily argued that depending on a *NON STANDARD* getopt routine is a bug. AFAIK *ONLY* glibc has the long-getopt crap, and if that's the only thing you're running into, it should be easy enough to rip out the long getopt code, and add a few proper defines and have the standard libc coexist peacefully with the GNU getopt. c.) dependencies on bugs in glibc. What bugs have you found in glibc 2.1.1? Have you reported those to the GNU folks? I personally haven't found any, but I've seen for instance, kcalc is riddled with ifdefs and warnings about floating point precision stuff and RH 5.something due to glibc bug(s). - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: glibc
On Mon, 19 Jul 1999, Warner Losh wrote: In message 19990719080712.a15...@holly.dyndns.org Chris Costello writes: : getopt other than --foo-bar flags that everyone I know hates? Not everyone hates them... Sure, I don't hate them either... until I try and port something that depends on them. Then I get annoyed. Some sort of compatible extension should be devised, so that a small block of code could be ifdef'd to provide support for long options, and the rest would work with a standard getopt routine. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: m68k Support in FreeBSD
On Mon, 19 Jul 1999, Brian F. Feldman wrote: Isn't it more a question of whether a proper cross-build system will be available within the time frame that m68ks aren't completely obsolete? Bah! An 040 or 030 powered Mac w/ MacOS makes a decent web browsing, word processing machine; it's an actually useable alternative to an e-machine. Similarlly a 386 or 486 powered FreeBSD machine can still be quite useful even as a small server (admittedly the 68k Mac hardware makes for a piss poor server.. but still). I can't see a 486 or 040 powered machine becomming entirely obsolete until X is required to buildworld. - alex You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: glibc
On Mon, 19 Jul 1999, Per Lundberg wrote: Has anybody done a port of glibc to FreeBSD? (I'm not interested in opinions about how poor it is or how evil the FSF are; I'm only asking to avoid duplicate work. Thanks.) Perhaps if you explain what it is you're trying to accomplish, there might be an easier option than porting *shudder* glibc? - alex The sheep bleated twice. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: matcd on an SB16
On Fri, 16 Jul 1999, Wes Peters wrote: Uh, no, that's the way it's supposed to be. They support every stupid dongle and widget on the planet, remember? ;^) Execpt this dongle happens to be reasonably useful and common, and ignored by FreeBSD :^) - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: matcd on an SB16
On Fri, 16 Jul 1999, Wes Peters wrote: Uh, no, that's the way it's supposed to be. They support every stupid dongle and widget on the planet, remember? ;^) Execpt this dongle happens to be reasonably useful and common, and ignored by FreeBSD :^) - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: hardware
On Fri, 9 Jul 1999, Jake Burkholder wrote: Nvidia cards are already supported. The GL xlock savers look awesome. Really? Wow. The xscreensaver GL savers looked like crap, the xlockmore ones worked for about oh two seconds, before slowing down to unaccelerated speeds. This at 640x480x16 too. Hmm. At least 2D works great at 1152x864x32. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hardware
On Fri, 9 Jul 1999, Jake Burkholder wrote: Nvidia cards are already supported. The GL xlock savers look awesome. Really? Wow. The xscreensaver GL savers looked like crap, the xlockmore ones worked for about oh two seconds, before slowing down to unaccelerated speeds. This at 640x480x16 too. Hmm. At least 2D works great at 1152x864x32. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: DVD-ram
On Tue, 6 Jul 1999, Kenneth D. Merry wrote: IMO, DVD drives are probably best handled through the CD driver, and Optical drives are probably best handled through the DA driver. The CD driver doesn't currently handle writes, but it's a one-line fix to change that. From what I can tell, some of the DVD-RAM drives are actually treated as disks (would use the da driver). For example, check out http://mpeg.openprojects.net/panasonic.html to see the Linux "driver" for the Panasonic LF-D100. The comments outnumber the code. I'd like to hear what your rationale for a separate driver is, though. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 'rtfm' script
On Tue, 6 Jul 1999, Brian F. Feldman wrote: RTFM isn't a newby-apparent term. Name it help(1). Sure it is. Some hapless newbie wanders into #FreeBDS on efnet, and asks an already answered question. Aside from a kick, and a possible ban, they're likely to be met with a chorus of rtfm, which in all likelyhood would prompt the inquisitive newbie to try and run rtfm. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: DVD-ram
On Tue, 6 Jul 1999, Kenneth D. Merry wrote: IMO, DVD drives are probably best handled through the CD driver, and Optical drives are probably best handled through the DA driver. The CD driver doesn't currently handle writes, but it's a one-line fix to change that.
Re: 'rtfm' script
I propose an rtfm(1) command, and I've got some Perl code that works. If people are interested, I will continue with it, and write a man page. [...] (-s = simple, don't search sections 3, 4, or 9, and 'e' means 'exact', or 'use whatis instead of apropos') If rtfm(1) is really for newbies and other clueless people, perhaps it should be made interactive. I mean, this whole idea sounds like it's geared towards people who wouldn't know what sections 3, 4, or 9 are. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: 'rtfm' script
On Mon, 5 Jul 1999, Chris Costello wrote: If rtfm(1) is really for newbies and other clueless people, perhaps it should be made interactive. I mean, this whole idea sounds like it's geared towards people who wouldn't know what sections 3, 4, or 9 are. It'll probably have a lot of changes in the actual interface if people accept it as useful or not. I may have 'simple' (default to don't search 3, 4, and 9) on as default. This sounds like a good idea. Now, ideally, I'd love to see something that could take an english phrase and figure out where to go from there. Sort of like an Ask Jeeves (ask.com) for FreeBSD newbies. This is not to say that the more advanced options wouldn't be useful; I could personally find a use for something to search the handbook, FAQs and man pages at once. I think I'll volunteer a few of my newbie friends once this progresses a bit further. P.S. If you're looking for an easy to use regexp implementation, and aren't afraid of C++, check out Qt; if you're looking for more of a challenge, there's always the need for an rtsl(1) ;) - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Lizard...
Feel free, just don't ask me questions about it since I honestly don't have time right now to explain to many hundreds of people how to build this stuff. In a nutshell, use egcs to compile everything from the following list: turbovision 0.7, qt 1.42, libh 0.1 (see below). libh is the code in question and can be obtained from ftp://zippy.cdrom.com/pub/libh.tar.gz. It will work with either gmake or make. FWIW it seems to want GNU make. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Lizard...
On Thu, 1 Jul 1999, Josef Grosch wrote: I have done installs on FreeBSD, Redhat, HP/UX, and Solaris and I have to say that Redhat is very confusing. FreeBSD does have it's warts but it is better than Redhat. HP/UX and Solaris also have their problems, just ask Nicole Harrington how she liked installing Solaris on an X86 box, but they are better than FreeBSD but not by as much as you would think. HP/UX install looks a lot like FreeBSD but not as limited as FreeBSD. The ability to have more than 2 buttons on the screen and too be able to backup is a major blessing. Uh, the Solaris packaging crap *is* a wart. It won't even work on a tarball.. The FreeBSD makefile mess could be extended to be about as flexible as the Solaris gunk. - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Lizard...
Feel free, just don't ask me questions about it since I honestly don't have time right now to explain to many hundreds of people how to build this stuff. In a nutshell, use egcs to compile everything from the following list: turbovision 0.7, qt 1.42, libh 0.1 (see below). libh is the code in question and can be obtained from ftp://zippy.cdrom.com/pub/libh.tar.gz. It will work with either gmake or make. FWIW it seems to want GNU make. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: [Fwd: Good news from NVIDIA]
On Thu, 3 Jun 1999, Daniel O'Connor wrote: On 03-Jun-99 Chris Piazza wrote: Just downloading the XFree86 source right now and I'm going to build it overnight assuming it works. If not I'm sure it'll be fun (heh) to track down. Yeah.. Building X is a bit of a dog I've found.. Well if you're interested in binaries the bzip2'd binary of XF86_SVGA seems to be a little over 1 meg. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: [Fwd: Good news from NVIDIA]
On Thu, 3 Jun 1999, Daniel O'Connor wrote: On 03-Jun-99 Alex Zepeda wrote: On Thu, 3 Jun 1999, Daniel O'Connor wrote: Yeah.. Building X is a bit of a dog I've found.. Well if you're interested in binaries the bzip2'd binary of XF86_SVGA seems to be a little over 1 meg. Hmm.. well I wouldn't mind a copy :) Do they work OK? It seems to work, but I have no real way of testing any added functionality as I've got a TNT based card (which a stock XFree86 supported already). I've put a copy up at: http://redwood203.marin.k12.ca.us/alex/XF86_SVGA.bz2 - alex who realized firsthand how stupid it is to try and switch to -current remotely How long, how long must we sing this song? - U2 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: [Fwd: Good news from NVIDIA]
On Thu, 3 Jun 1999, Daniel O'Connor wrote: Do they work OK? MD5 (XF86_SVGA.bz2) = 2502eb1d8b48a052ffe831b147094fbd -rwxr-xr-x 1 root wheel 1286643 Jun 2 23:27 XF86_SVGA.bz2 - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IPv6 and -current?
On Sun, 23 May 1999, Jeroen Ruigrok/Asmodai wrote: I already mailed Itojun-san about the status of the KAME/Inria merger and hope to hear from him soon. Well, I finally got the userland shit working! This would make an awesome port, it compiles out of the box, and works with bpf to do ipv6 in ipv4 tunneling :) - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
IPv6 and -current?
Out of a perhaps morbid curiosity, I'm somewhat interested in setting up an IPv6 stack on my computer. From what I can tell there are two well supported stacks. Kame and Inria, and both support 2.2.8, Kame also supports 3.x. Has anyone tried to port either to -current? I tried playing around with the Kame release for 3.0, and it generated quite a few rejects... - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Native Applixware for FreeBSD -- When?
On Tue, 11 May 1999, Andreas Braukmann wrote: Hmmm. I relly dislike the StarOffice GUI and never in my life had real contact to WordPerfect. (AppleWorks - Apple Writer 2e - MS WORD 4 (crap compared to AW2e) - MS WinWord 2 - Tex/LaTex - MS Office '95 [still using LaTex for complex tasks, of course]) Bah, you missed out on the best word processor of all time WordPerfect 5.1 (Well, if you count something without an operating system, the IBM Selectric II...) - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Native Applixware for FreeBSD -- When?
On Mon, 10 May 1999, Amancio Hasty wrote: Hi, xls and xml are markup languages which means you need an engine to render -- they do solve very nicely the document construct , or grammar and syntax. It would be great to have a word processing system based upon XML, XSL and a low level api (DOM) to manipulate documents 8) You've seen KOffice, right? - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Native Applixware for FreeBSD -- When?
On Mon, 10 May 1999, Amancio Hasty wrote: I am sorry . Isn't that a linux thingy ?? 8) Well most of KDE is. But hey, if I come across something that is Linux only, I try and commit a fix (as does the other resident FreeBSD nut Hans Petter Bieker). If you've got a post-egcs -CURRENT, KDE KOffice should at least compile. Well, okay since I haven't seen KOffice and from my recollection is a collection of applications. Yes. And you can find more information about it at http://koffice.kde.org What can you tell us about the underlying properties of koffice documents? Does use a standar markup language like XML and styling markup like XSL , does it use word style document format, etc...?? It uses XML natively, but there are a few filters included. It's very much a work in progress. http://koffice.kde.org/faq/faq-5.html#ss5.3 (File format) http://koffice.kde.org/faq/faq-6.html (KWord in general) The only downside (besides the fact that it's not even in its alpha phase), is that it uses MICO, which means that it will take a few hours at least (on a single PII/450) to compile everything - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
