Re: X mailers (was Re: ANNOUNCE: Linux ABI/SDK standards for Ope
On Fri, 10 Sep 1999, Lutz Albers wrote: --On Freitag, 10. September 1999, 10:56 +0930 Daniel O'Connor [EMAIL PROTECTED] wrote: On 09-Sep-99 Nate Williams wrote: VM doesn't do HTML/MIME very well, although I understand in later versions of XEmacs they've incorporated some packages that handle things better. (I'm still using XEmacs 19.16, from the dark ages...) Does it do IMAP? I have only seen *1* emailer which does IMAP properly (xfmail) all the others either don't support it at all, or treat IMAP like POP (ie just fetch mail from INBOX). It claims to do IMAP4, but it just fetches all messages from the server (and by default deleting it from the server). There are very few good IMAP4 clients out there :-( xfmail? Doesn't do that here and I use it daily for all of my internal stuff. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: X mailers (was Re: ANNOUNCE: Linux ABI/SDK standards for Ope
On 10-Sep-99 Daniel J. O'Connor wrote: On 10-Sep-99 Jamie Bowden wrote: :Umm.. welll I'd like to know to enable sub folder support in it then.. :Haveing multiple accounts on different machines would be nice too (then it :could do what xfmail can) In 'Incoming Folders' type 'a' and it will ask you for the server name to add. I don't have an 'Incoming Folders' if I press A in 'Folder List' I get a request for a folder name not a server name.. I'm about to try Pine 4.10 (I have 4.05) You'll need to enable incoming folders in the setup from the main menu. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: X mailers (was Re: ANNOUNCE: Linux ABI/SDK standards for Ope
On Fri, 10 Sep 1999, Lutz Albers wrote: --On Freitag, 10. September 1999, 10:56 +0930 Daniel O'Connor docon...@gsoft.com.au wrote: On 09-Sep-99 Nate Williams wrote: VM doesn't do HTML/MIME very well, although I understand in later versions of XEmacs they've incorporated some packages that handle things better. (I'm still using XEmacs 19.16, from the dark ages...) Does it do IMAP? I have only seen *1* emailer which does IMAP properly (xfmail) all the others either don't support it at all, or treat IMAP like POP (ie just fetch mail from INBOX). It claims to do IMAP4, but it just fetches all messages from the server (and by default deleting it from the server). There are very few good IMAP4 clients out there :-( xfmail? Doesn't do that here and I use it daily for all of my internal stuff. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: X mailers (was Re: ANNOUNCE: Linux ABI/SDK standards for Ope
On 10-Sep-99 Daniel J. O'Connor wrote: On 10-Sep-99 Jamie Bowden wrote: :Umm.. welll I'd like to know to enable sub folder support in it then.. :Haveing multiple accounts on different machines would be nice too (then it :could do what xfmail can) In 'Incoming Folders' type 'a' and it will ask you for the server name to add. I don't have an 'Incoming Folders' if I press A in 'Folder List' I get a request for a folder name not a server name.. I'm about to try Pine 4.10 (I have 4.05) You'll need to enable incoming folders in the setup from the main menu. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: damn ATX power supplies...
On Thu, 9 Sep 1999, Luigi Rizzo wrote: hi, any idea on how to force ATX power supplies to restart after a power outage without having someone press the 'power' button on the front panel ? All the motherboards i can find now have their bios with two options: Disabled no automatic restart on power failure Timer restart at a given time of the day. I have a new machine here (don't recall which BIOS, haven't seen it in awhile) that has the ATX settings in two different places. Only one of them had the option for Last Setting. IIRC one was in power management and one was in either the advanced settings or in someplace stupid like peripheral settings. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: damn ATX power supplies...
On Thu, 9 Sep 1999, Luigi Rizzo wrote: hi, any idea on how to force ATX power supplies to restart after a power outage without having someone press the 'power' button on the front panel ? All the motherboards i can find now have their bios with two options: Disabled no automatic restart on power failure Timer restart at a given time of the day. I have a new machine here (don't recall which BIOS, haven't seen it in awhile) that has the ATX settings in two different places. Only one of them had the option for Last Setting. IIRC one was in power management and one was in either the advanced settings or in someplace stupid like peripheral settings. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Linux StarOffice51 runs on -stable
On Thu, 2 Sep 1999, Mikhail Teterin wrote: Marcel Moolenaar once wrote: I don't think this one is needed anymore ?!? It is. Without it, soffice keeps bringing up setup over and over instead of just starting the damn office. What is everybody doing? I run SO5.1 OOTB. AFAICT, there's absolutely no need for this kind of hackery. Like I said. On my system, the soffice would restart setup over and over without the hack. I don't know why. After I applied the hack, it started the office. Are you running -current, may be? Because I'm on -stable. There was a patch posted on the freebsd.misc newsgroup the other day for procfs that eliminates the need for the "hackery". It's supposed to be already in -current and I don't recall if it's supposed to be in -stable now or just apply cleanly to -stable. I got it to apply to 3.2-CD but had to do some of it manually. Vince. -- ====== Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
On Thu, 2 Sep 1999, Marcel Moolenaar wrote: jack wrote: -rw-r--r-- 1 marcel marcel 72192512 Jul 23 11:47 so51_lnx_01.tar MD5 (so51_lnx_01.tar) = 347ffa68be6c1d7b89fd843591afb0d3 so51a_lnx_01.tar -rw-r--r-- 1 jacko user 70393856 Aug 31 15:47 so51a_lnx_01.tar (libs are all libxxx517x.so) requires jumping throught the hoops (unzip setup.zip, etc.) to install but runs OOTB after that. I havn't tried to do a 'network' install. Sigh... For the record, I'm running the same version as jack and after looking at procfs_status.c in -stable (and current), this version should run with either version. -RELEASE, however, requires the patch. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux StarOffice51 runs on -stable
On Thu, 2 Sep 1999, Mikhail Teterin wrote: Marcel Moolenaar once wrote: I don't think this one is needed anymore ?!? It is. Without it, soffice keeps bringing up setup over and over instead of just starting the damn office. What is everybody doing? I run SO5.1 OOTB. AFAICT, there's absolutely no need for this kind of hackery. Like I said. On my system, the soffice would restart setup over and over without the hack. I don't know why. After I applied the hack, it started the office. Are you running -current, may be? Because I'm on -stable. There was a patch posted on the freebsd.misc newsgroup the other day for procfs that eliminates the need for the hackery. It's supposed to be already in -current and I don't recall if it's supposed to be in -stable now or just apply cleanly to -stable. I got it to apply to 3.2-CD but had to do some of it manually. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Linux StarOffice51 runs on -stable
On Thu, 2 Sep 1999, Marcel Moolenaar wrote: jack wrote: -rw-r--r-- 1 marcel marcel 72192512 Jul 23 11:47 so51_lnx_01.tar MD5 (so51_lnx_01.tar) = 347ffa68be6c1d7b89fd843591afb0d3 so51a_lnx_01.tar -rw-r--r-- 1 jacko user 70393856 Aug 31 15:47 so51a_lnx_01.tar (libs are all libxxx517x.so) requires jumping throught the hoops (unzip setup.zip, etc.) to install but runs OOTB after that. I havn't tried to do a 'network' install. Sigh... For the record, I'm running the same version as jack and after looking at procfs_status.c in -stable (and current), this version should run with either version. -RELEASE, however, requires the patch. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: StarOffice giveaway of source code
On Wed, 1 Sep 1999 [EMAIL PROTECTED] wrote: Heres what suns web page says: "Our aim is to .com office productivity. We are publishing the StarOffice specifications and will make the source code available through the Sun Community Source Licensing program to encourage industry-wide collaboration on future versions of the software. " I have the feeling that "Software Licensing Program" speaks . Also, note there is no place to download this software nor get into the licensing program. Try: http://www.sun.com/communitysource/ Vince. -- ====== Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: StarOffice giveaway of source code
On Wed, 1 Sep 1999 smc...@aol.com wrote: Heres what suns web page says: Our aim is to .com office productivity. We are publishing the StarOffice specifications and will make the source code available through the Sun Community Source Licensing program to encourage industry-wide collaboration on future versions of the software. I have the feeling that Software Licensing Program speaks . Also, note there is no place to download this software nor get into the licensing program. Try: http://www.sun.com/communitysource/ Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
On Mon, 16 Aug 1999, Terry Lambert wrote: On Fri, 13 Aug 1999, Terry Lambert wrote: Has anyone mentioned to them that they will be unable to incorporate changes made to the GPL'ed version of XFS back into the IRIX version of XFS, without IRIX becoming GPL'ed? Given that they say they're dropping IRIX and going with Linux, I don't think it'll be a problem. Can you please site a reference for this, other than wishful thinking by the Linux camp? Here's one: http://www.zdnet.com/pcweek/stories/news/0,4153,1015908,00.html But just about every trade rag covered it. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
On Mon, 16 Aug 1999, Terry Lambert wrote: On Fri, 13 Aug 1999, Terry Lambert wrote: Has anyone mentioned to them that they will be unable to incorporate changes made to the GPL'ed version of XFS back into the IRIX version of XFS, without IRIX becoming GPL'ed? Given that they say they're dropping IRIX and going with Linux, I don't think it'll be a problem. Can you please site a reference for this, other than wishful thinking by the Linux camp? Here's one: http://www.zdnet.com/pcweek/stories/news/0,4153,1015908,00.html But just about every trade rag covered it. Begging your pardon, but: | --- With the help of Veritas Software Corp., SGI will work to add | key features of its Irix operating system to the Linux platform. | Currently, Irix runs on the MIPS platform. Once SGI switches | entirely to Intel Corp.'s IA/64 platform, that will be the end of | Irix. | | SGI is also forming an alliance with NEC Corp. to increase its | market share in Japan. These paragraphs are contradictory. It implies an end to MIPS. Nintendo 64 uses MIPS. It also seems a bit overzealous. No argument here. Perhaps they're just trying to float a few trial baloons in hopes of finding something popular/feasable. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
On Mon, 16 Aug 1999, Terry Lambert wrote: On Fri, 13 Aug 1999, Terry Lambert wrote: Has anyone mentioned to them that they will be unable to incorporate changes made to the GPL'ed version of XFS back into the IRIX version of XFS, without IRIX becoming GPL'ed? Given that they say they're dropping IRIX and going with Linux, I don't think it'll be a problem. Can you please site a reference for this, other than wishful thinking by the Linux camp? Here's one: http://www.zdnet.com/pcweek/stories/news/0,4153,1015908,00.html But just about every trade rag covered it. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
On Mon, 16 Aug 1999, Terry Lambert wrote: On Fri, 13 Aug 1999, Terry Lambert wrote: Has anyone mentioned to them that they will be unable to incorporate changes made to the GPL'ed version of XFS back into the IRIX version of XFS, without IRIX becoming GPL'ed? Given that they say they're dropping IRIX and going with Linux, I don't think it'll be a problem. Can you please site a reference for this, other than wishful thinking by the Linux camp? Here's one: http://www.zdnet.com/pcweek/stories/news/0,4153,1015908,00.html But just about every trade rag covered it. Begging your pardon, but: | --- With the help of Veritas Software Corp., SGI will work to add | key features of its Irix operating system to the Linux platform. | Currently, Irix runs on the MIPS platform. Once SGI switches | entirely to Intel Corp.'s IA/64 platform, that will be the end of | Irix. | | SGI is also forming an alliance with NEC Corp. to increase its | market share in Japan. These paragraphs are contradictory. It implies an end to MIPS. Nintendo 64 uses MIPS. It also seems a bit overzealous. No argument here. Perhaps they're just trying to float a few trial baloons in hopes of finding something popular/feasable. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
On Wed, 4 Aug 1999, Biju Susmer wrote: hi, I tried yesterday to make the kernel understand my CD ROM drive.. but it refused. Here is the dmesg (of boot -v)... is my config wrong or i missed something? The drive is Acer 32X and connected as secondary slave. It is seen by Win98 and BIOS. Can someone help? You have the CD connected as the secondary slave and no secondary master. That's the problem. It's an illegal configuration as the IDE controller is actually on the drive itself. Move the jumper on the CD to master and it'll be recognized. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: IDE quirk in 3.2-STABLE kernel ?
On Wed, 4 Aug 1999, Biju Susmer wrote: hi, I tried yesterday to make the kernel understand my CD ROM drive.. but it refused. Here is the dmesg (of boot -v)... is my config wrong or i missed something? The drive is Acer 32X and connected as secondary slave. It is seen by Win98 and BIOS. Can someone help? You have the CD connected as the secondary slave and no secondary master. That's the problem. It's an illegal configuration as the IDE controller is actually on the drive itself. Move the jumper on the CD to master and it'll be recognized. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Onstream?
Out of curiousity, have there been any successes in the drivers for the OnStream tape drives (SCSI or IDE)? Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD voice synthesis
On Tue, 3 Aug 1999, Julian Elischer wrote: Very impressive. I hope to have a little time to play with it and understand it a bit better. They seem to have support for up to 4.0 in some of the files, so maybe they actually have a freebsd user in their group. It's big and(on my p90) a bit slow, but I hope that I'll be able to get just the bits I need to make it a bit faster. 'festival' itself seems to totoally skip the word "FreeBSD" when I asked it to say (from the manual) I'm using a pIII-450 and it pronounces it "freebs". However if you spell it "Free B S D" it does just fine. Seems to do well with most words I've thrown at it - including some last names (it does mine almost perfect, but blows some real easy ones). [you need..] A Unix machine, Festival has compiled and run on Suns (SunOS and Solaris), FreeBSD, Linux, SGIs, HPs and DEC Alphas but should be portable to any standard Unix machine. Did gmake test work for you in festival? It did for me in speech-tools but not festival even tho it seems to work well. Sure is gonna make some of these boring README files easier! ...wonder how hard it'd be to tie it into the select buffer in X... Vince. -- ====== Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD voice synthesis
On Tue, 3 Aug 1999, Julian Elischer wrote: Very impressive. I hope to have a little time to play with it and understand it a bit better. They seem to have support for up to 4.0 in some of the files, so maybe they actually have a freebsd user in their group. It's big and(on my p90) a bit slow, but I hope that I'll be able to get just the bits I need to make it a bit faster. 'festival' itself seems to totoally skip the word FreeBSD when I asked it to say (from the manual) I'm using a pIII-450 and it pronounces it freebs. However if you spell it Free B S D it does just fine. Seems to do well with most words I've thrown at it - including some last names (it does mine almost perfect, but blows some real easy ones). [you need..] A Unix machine, Festival has compiled and run on Suns (SunOS and Solaris), FreeBSD, Linux, SGIs, HPs and DEC Alphas but should be portable to any standard Unix machine. Did gmake test work for you in festival? It did for me in speech-tools but not festival even tho it seems to work well. Sure is gonna make some of these boring README files easier! ...wonder how hard it'd be to tie it into the select buffer in X... Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: 1373 sound chip
On Thu, 22 Jul 1999, Brian McGroarty wrote: There's a patch for the 1371 floating around that seems to work for the 1373 as well. Search the archive of FreeBSD-questions for 1371. Last I saw, the search page was still confused - you need to put 1371 in the web search field at the top, but still click the mailing list search button down below. Found it and applied the patch. Still no go. The 1373 is IDing as a 1371 from BIOS, but FreeBSD doesn't see it at all. Looking at the other messages, I see some folks using 'device pcm0 at nexus?' but they're also running -current. I tried that under 3.2 and after it told me that pcm0 is only good with ISA it seg-faulted and blew core. There was also mention of another patch from Joachim Kuebart for PCI, but no mention where to find it. Vince. -Original Message- From: Vince Vielhaber [mailto:v...@michvhf.com] Sent: Wednesday, July 21, 1999 6:54 PM To: Brian McGroarty; freebsd-hardware; hackers Subject: 1373 sound chip I sent this to multimedia about a week ago and didn't get a response so I'm trying it here [hackers hardware] (with minor mods): I'm setting up a new machine that has onboard sound in the form of an ES1373 Creative (Ensoniq, probably). Visual config shows an unknown device as ES0 and pcm0 doesn't find anything (tried various forms in the kernel config for that one, the last one was/is: device pcm0 Is there any driver for this chip? Under windows it uses the SoundBlaster AudioPCI 64V driver. So far I haven't found any specs on Creative's or Ensoniq's website. Can someone shed some light on possibly adapting the pcm driver to this chip (like how to ID, etc.) ? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
1373 sound chip
I sent this to multimedia about a week ago and didn't get a response so I'm trying it here [hackers hardware] (with minor mods): I'm setting up a new machine that has onboard sound in the form of an ES1373 Creative (Ensoniq, probably). Visual config shows an unknown device as ES0 and pcm0 doesn't find anything (tried various forms in the kernel config for that one, the last one was/is: device pcm0 Is there any driver for this chip? Under windows it uses the SoundBlaster AudioPCI 64V driver. So far I haven't found any specs on Creative's or Ensoniq's website. Can someone shed some light on possibly adapting the pcm driver to this chip (like how to ID, etc.) ? Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Porting LILO to FreeBSD
On Fri, 2 Jul 1999, Graham Wheeler wrote: Hi all I currently have Linux installed in a DOS partition for one reason only, and that is that I want to use LILO. I would love to be able to get LILO working under FreeBSD so that I can free up all the space used up by Linux. The reason I want to use LILO is because it allows me to swap my C: and D: drives around when booting DOS. This lets me have Win95 bootable on my real C: drive, but lets me boot a Win95-free DOS 6.2 and Windows 3.1 on my D: drive, which gets logically mapped to C:. I haven't found any other freeware boot loaders that have this ability. Has anyone ever attempted to port LILO to FreeBSD? I imagine that it should be possible, but would require some serious changes in low-level disk access code, to map disk files to physical disk locations, etc. If anyone has any experience with this, or has any advice (including pointing me to other boot loaders that can get the BIOS to switch disks that will work purely from DOS or FreeBSD), please let me know... On CD #1 there's a file called osbsbeta.exe. That version allows you to boot from different physical devices whereas osbs135.exe doesn't. I'm using it on one machine that has 95, dos6, os2 and freebsd on different drives. I should mention that CD #1 I'm referring to is from 2.2.6, I haven't looked at any newer versions. Vince. -- == Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Porting LILO to FreeBSD
On Fri, 2 Jul 1999, Graham Wheeler wrote: Hi all I currently have Linux installed in a DOS partition for one reason only, and that is that I want to use LILO. I would love to be able to get LILO working under FreeBSD so that I can free up all the space used up by Linux. The reason I want to use LILO is because it allows me to swap my C: and D: drives around when booting DOS. This lets me have Win95 bootable on my real C: drive, but lets me boot a Win95-free DOS 6.2 and Windows 3.1 on my D: drive, which gets logically mapped to C:. I haven't found any other freeware boot loaders that have this ability. Has anyone ever attempted to port LILO to FreeBSD? I imagine that it should be possible, but would require some serious changes in low-level disk access code, to map disk files to physical disk locations, etc. If anyone has any experience with this, or has any advice (including pointing me to other boot loaders that can get the BIOS to switch disks that will work purely from DOS or FreeBSD), please let me know... On CD #1 there's a file called osbsbeta.exe. That version allows you to boot from different physical devices whereas osbs135.exe doesn't. I'm using it on one machine that has 95, dos6, os2 and freebsd on different drives. I should mention that CD #1 I'm referring to is from 2.2.6, I haven't looked at any newer versions. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Matt's Commit status (was Re: 3.2-stable, panic #12)
On 03-Jun-99 Jaye Mathisen wrote: I second this. Even if it's a bit painful, somebody who has been working diligently at this needs to be able to be make their work usable quickly. I would guess that not too many things hinder progress, or quash desire more than fixes to problems languishing. There has to be some middle ground somewhere that lets Matt get his fixes in quickly, and still doesn't ruffle too many core feathers. I had the opportunity to hear some of the core side recently, and I certainly sympathize or empathize with the issue, but nobody else has stepped up to fix the NFS problems, and I would like to see this opportunity capitalized on. Not knowing the FULL story from both sides, I feel it'd be inappropriate if I were to comment on it. However knowing Matt's coding abilities, having seen the eruption here a few months ago, and the past splits that IIUC were due to core problems, perhaps an oversight board (for lack of a better description) consisting of zero core people and zero committers may help to stop or solve some of these erruptions before they spill out into the public's view. Who does a coder, committer, core member, etc, have to turn to if (s)he feels (s)he's getting the shaft? Not anything aimed at you (Jordan) or David, but let's face it - you two have enough to do without having to worry about the petty crap that seeps out as well. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Matt's Commit status (was Re: 3.2-stable, panic #12)
On 03-Jun-99 Amancio Hasty wrote: It is a nice idea and I have proposed it in the past however most likely such organization will devolve to the current status-quo with core;however, if the oversight committee is composed of individuals from companies using FreeBSD it may actually work for committee should have a vested interest in FreeBSD. My thoughts actually extended beyond oversight committee and into a sort of an appeals role. As far as who, 'individuals from companies' may not provide a broad enough scope. But they should definitely have a vested interest - and no legal degree :) Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Matt's Commit status (was Re: 3.2-stable, panic #12)
On 04-Jun-99 Chuck Robey wrote: [I rearranged the things since these folks can't be bothered to comment at the bottom] Vince Vielhaber wrote: Not knowing the FULL story from both sides, I feel it'd be inappropriate if I were to comment on it. However knowing Matt's coding abilities, having seen the eruption here a few months ago, and the past splits that IIUC were due to core problems, perhaps an oversight board (for lack of a better description) consisting of zero core people and zero committers may help to stop or solve some of these erruptions before they spill out into the public's view. Who does a coder, committer, core member, etc, have to turn to if (s)he feels (s)he's getting the shaft? Not anything aimed at you (Jordan) or David, but let's face it - you two have enough to do without having to worry about the petty crap that seeps out as well. Vince. On Thu, 3 Jun 1999, Amancio Hasty wrote: It is a nice idea and I have proposed it in the past however most likely such organization will devolve to the current status-quo with core;however, if the oversight committee is composed of individuals from companies using FreeBSD it may actually work for committee should have a vested interest in FreeBSD. I'm sorry, these are both crack-pot ideas, it's been explained again and again, and Amancio, for one, knows this, so I can't see why he went on this way. I will restate the obvious again, please read this before exploding, because I'll make it real clear. I am going to explain reality; if you're complaining about reality, go grab a bottle of bourbon, it will work as well. Reality: FreeBSD is written (not run, not administered, really written) by volunteers. These volunteers work on what they want to. Core can say NO, but they can't say YOU WILL, because the volunteers WON'T. People with no intention (and often no ability) to code keep wanting to tell the folks that DO code what to do. Impossible, this IS NOT a paid organization, the volunteers will just go away and code for another group that is less self-desctructive. Some group you're talking about that doesn't code has no authority whatsoever, and in fact no expertise at all to even pretend they know what they're doing, else they WOULD be coding. You cannot code without real experience, this is not some weird TV show with scifi unreality. The only group that these volunteers will listen to or respect is a group of folks that DO code and DO have the expertise. Trying to get together a group of dilettantes may be a marketing man's idea of how to go, but it will not fit FreeBSD's reality, and you cannot force things like that here. Just realize, IF you're loud enough, and succeed, the programmers will all desert you, and you'll have a nice place to argue, but no more software. Core here does an excellent job, with all the problems they face, most committers will agree to that pretty quickly, and they are the only ones with a vote. Look to reality for the reasons why. No need for blowing up, so relax. You may wanna grab that bourbon bottle yourself and take a sip. 1) Noone ever said anything about marketing types trying to run anything. 2) Nothing was ever said about telling volunteers what to do or not do. 3) Nothing was mentioned about the technical abilities of an appeals board or oversight group. 4) Ever do or say something that someone told you that you're out of line? 5) Let's go back to your volunteer thing. You have volunteers willing to work for you - for free. It's no secret that in the past core has been a problem for some (or maybe even many) of these volunteers. They went away. If there's noone they can go to, why should they (or anyone else) bother to volunteer? Earlier in this thread Matt was accused of running rough shod over everyone. Looking over the history and hearing the complaints of some of those involved, I admit not knowing both sides of the FULL story, that core may be partially to blame. But who is there for the *VOLUNTEERS* to turn to? Core? They may have caused the problem. Then once the emotions start to rise there's absolutely NOONE for any of them to look to besides Jordan and/or David. Like they don't already have enough to do. It's obvious there's a problem with the status quo, but if the status quo continues to run rough shod over any possible solution, status quo will end up running out of volunteers and there will be yet another BSD to add to the collection. Maybe the next one can be called ClosedBSD? Now reread your own last paragraph. It goes at least two ways. How much talent and support (technical, financial, advocational[1], etc.) are you willing to lose before anyone's told they're outa line? For all that matter, how much has already been lost? You used the phrase crack pot. Doesn't a cracked pot leak? Isn't that what's already happening? Talent leaking out? Vince. [1
Re: Matt's Commit status (was Re: 3.2-stable, panic #12)
On 04-Jun-99 Chuck Robey wrote: On Thu, 3 Jun 1999, Vince Vielhaber wrote: Just realize, IF you're loud enough, and succeed, the programmers will all desert you, and you'll have a nice place to argue, but no more software. Core here does an excellent job, with all the problems they face, most committers will agree to that pretty quickly, and they are the only ones with a vote. Look to reality for the reasons why. No need for blowing up, so relax. You may wanna grab that bourbon bottle yourself and take a sip. Maybe you're right, but I'm tired to people talking about core like they're some evil overlord group. These guys are longtime FreeBSDers. They've been doing it a long time, and a large part of why they are still doing it is because of a feeling of responsibility. They're doing a great job, even if it's not 100% without error, and FreeBSD would go right down the tubes pretty quickly without coolheaded guidance, just because of the lack of control. You don't have to look hard at all to see several recent (and some ongoing) episodes of folks trying to go off on their own, and the only real restraint is the realization of what kind of limits core will allow. It's got a *great* track record. We can argue specific issues, but attacking core itself, that I'm going to jump up and shout about. 2) Nothing was ever said about telling volunteers what to do or not do. You referred to a group other than core setting policy. No, I did not say setting policy. A place for an appeal or an oversight. I'd never advocate a group other than core for policy - if that's what you got out of it then either you misread or I poorly worded something. If it's the latter then I apologize. 3) Nothing was mentioned about the technical abilities of an appeals board or oversight group. You said that group would have no committers or core on it. Anyone who's shown skill and time has been pretty quickly asked to become a committer, so that pretty much means you're asking for either non-technical folks, or folks without the time to follow things close enough to have any real idea what's going on. Seeing as you did admit you haven't followed the issues closely enough yourself, you're one of the ones you figure would be on that board, right? Actually no. I haven't followed the issues closely enough by choice. I'm not sure I'd really want to get that deeply into the politics of it. Even if asked I can't say that I'd consider doing it. The reason I'd want no core or committers on it is strictly for political reasons. Core *appears* to hold a heavy hand and it's very possible the committers and/or coders are intimidated by them. Now with that scenario would you want either to be on any such committee? I'm trying to look at this from a completely detached viewpoint. 4) Ever do or say something that someone told you that you're out of line? Oh, yeah, sure, I make mistakes. Maybe wrong here, but I said above what keyed me off. It sure isn't bragging if I say here that I'm willing to bet I make more mistakes than you do, but I don't think I'm wrong here. I dunno, I could probably give you a good run :) 5) Let's go back to your volunteer thing. You have volunteers willing to work for you - for free. It's no secret that in the past core has been a problem for some (or maybe even many) of these volunteers. They went away. As has been pointed out endless times, you have to know how to code and be willing to read FreeBSD code enough so that you can contribute well integrated code. If you can't code or don't have the time, no, you can't contribute that way. You can help us by putting in problem reports, but not by trying to gain control, even a small part. The coders control FreeBSD, because they love it. Those are really the only folks who get to directly contribute. Free contributors, out of control, are a mob. Can't the same be said of a closed minded group whether they're core or contributers? If there's noone they can go to, why should they (or anyone else) bother to volunteer? The FreeBSD mailing lists are the most active, quick response groups on the net. Don't you feel silly claiming there's no one they can go to? Not at all. Why should this ever have gotten to the lists? Don't you feel silly that it had to be aired in public? Matt's complaints were expressed just a few months ago in this same forum. silly is a weak term to describe why it was handled the way it was, doncha think? Embarassing for *all* of us (core, user, contributer, bystander, floorsweeper, whoever) is more like it. Earlier in this thread Matt was accused of running rough shod over everyone. Looking over the history and hearing the complaints of some of those involved, I admit not knowing both sides of the FULL story, that core may be partially to blame. But who is there for the *VOLUNTEERS* to turn to? Core
Re: Suggestion...
On 22-May-99 Karl Denninger wrote: On Sat, May 22, 1999 at 02:33:51PM +0100, Brian Somers wrote: One other suggestion, while I'm at it. The dgb driver has been marked alpha quality for a LONG time. I've had a fax server running on a PC/Xe 8 port card (64k shared RAM) for well over a year on one of these cards - and have NEVER had a single problem with it. That server gets a LOT of extremely heavy use, and if there were driver problems I would have found them by now. I'd suggest that someone drop the alpha byline on that one - its definitely stable :-) I plan on doing some work on it and the dgm driver. They're almost the same and should be merged. They both violate style(9) in almost every way too :-[ I know of only one person with an Xem card (dgm driver), but he's promised to send me the specs by snail mail. Once I get them, I'll start the work. Let's leave the `alpha' there for a little longer :-) What are you planning on doing with it? Other than DDB support I can't imagine what could be *added* to the driver; it is one of those just works things right now. Why not merge the two into a *new* driver? Once it's running at an acceptable level, drop support for the two old drivers. That way if something breaks, the current users still have the one that works. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
