not all dirs visible under Linux emu
Hello everybody! Although I konw that this thread has moved to -emulation but I would like to throw in just a last piece of information... I think we are looking at different issues here... the thing that several files are not shown in the *same* filesystem and directory is the part I do not understand. However, the fact that the file selector dialogs seemingly do not show all dirs is a different matter, at least here. If you cd to a dir which also exists under /usr/compat/linux then you will be taken there instead of the "real" one. So, if you cd to /usr, which is shown in the file selector panel, then you will be immediately and transparently placed into /usr/compat/linux/usr. This behavior has been observed here since at least 3.3 or so... the odd thing is that install scripts and programs often see the paths the correct way now, so eg earlier you could install StarOffice only to /usr/compat/linux/whatever, because the install program did not see the other dirs. Now it does. So does the install shield of RealPlayer7. So, I would say, a partial improvement over previous behaviour already... (Using 4.0-STABLE of April 3rd, linux_base is the one from ports, which is current now.) Just a datapoint, in case someone is interested... Regards: Szilveszter ADAM Szeged University Szeged Hungary -- --- * Szilveszter ADAM * JATE Szeged * email: [EMAIL PROTECTED] * * Homepage : none * alternate email: [EMAIL PROTECTED] * * Finger [EMAIL PROTECTED] for PGP key. * * I prefer using the door instead of Windows(tm)... * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Quickie question on UDMA/33
Western Digital Caviar hard drives that should support UDMA/33, as should the Chipset. Both boot up, trying UDMA mode, throwing ICRC READ ERROR's then kick back down to PIO mode 4. Bios's are set to do auto-chose pio/dma modes. There may be a BIOS option that will disable DMA entirely. I've resolved to simply adding in the rc to reset them to pio mode, to get it over with (but I still get the errors at boot-up prior to the rc doing them). I simply use 'device ata' etc. forms in the knerel config. You might try commenting out this option (if you're using it): options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices __ Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The world ain't building
Hi, With USA_RESIDENT=NO and -DNOCRYPT: cc -O2 -pipe -I/usr/obj/source/cleansrc/lib/libipsec -DIPSEC_DEBUG -DIPSEC -DINE T6 -I/usr/obj/source/cleansrc/i386/usr/include -c policy_token.c -o policy_token .o /source/cleansrc/lib/libipsec/policy_token.l: In function `__libyylex': /source/cleansrc/lib/libipsec/policy_token.l:88: `__libipsecyylval' undeclared ( first use in this function) /source/cleansrc/lib/libipsec/policy_token.l:88: (Each undeclared identifier is reported only once /source/cleansrc/lib/libipsec/policy_token.l:88: for each function it appears in .) *** Error code 1 Stop in /source/cleansrc/lib/libipsec. -- Bob Bishop +44 118 977 4017 [EMAIL PROTECTED]fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Fri, 14 Apr 2000, Joe Greco wrote: In other words, if we're going to be replacing sendmail with an alternative MTA, I'd prefer postfix over qmail, and I believe I can marshall some pretty strong arguments for that position. Perhaps it's time to revisit something I proposed several years ago. Remove Sendmail from the base system - or, at least, make it a "package" that is removable with the package management tool. Then be able to add another mailer (or an updated Sendmail) in its place. Ideally, Sendmail would be available as a package for installation as part of the base system, just like games or info or proflibs. I would love to see this happen with other components of the system as well, such as BIND. While it is fantastic that FreeBSD comes out of the box so fully functional, it does make it a bit of a pain for those of us who intend to build servers - we have to disable the original before installing a new package. :-/ I always keep hearing the same line. You guys *know* perfectly well how to do it, and it's not a big thing to you, you even admit it's only "a bit of a pain". To most of the rest of the world, it's a huge thing, and they don't have the least clue how to do it. If you guys want so desperately to make things 1% easier, why have I never seen anyone bring out a parallel "sparse" FreeBSD? It wouldnt' be a large thing to do, and you who keep on asking for it, you know that very well. Just have a reasonable bit of compassion for everyone else. That's not to say the huge hurt it would do to FreeBSD to all reviewers and the public at large, just to save you "a bit of a pain". Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Fri, 14 Apr 2000, Joe Greco wrote: In other words, if we're going to be replacing sendmail with an alternative MTA, I'd prefer postfix over qmail, and I believe I can marshall some pretty strong arguments for that position. Perhaps it's time to revisit something I proposed several years ago. Remove Sendmail from the base system - or, at least, make it a "package" that is removable with the package management tool. Then be able to add another mailer (or an updated Sendmail) in its place. Ideally, Sendmail would be available as a package for installation as part of the base system, just like games or info or proflibs. I would love to see this happen with other components of the system as well, such as BIND. While it is fantastic that FreeBSD comes out of the box so fully functional, it does make it a bit of a pain for those of us who intend to build servers - we have to disable the original before installing a new package. :-/ I always keep hearing the same line. You guys *know* perfectly well how to do it, and it's not a big thing to you, you even admit it's only "a bit of a pain". To most of the rest of the world, it's a huge thing, and they don't have the least clue how to do it. If you guys want so desperately to make things 1% easier, why have I never seen anyone bring out a parallel "sparse" FreeBSD? It wouldnt' be a large thing to do, and you who keep on asking for it, you know that very well. Just have a reasonable bit of compassion for everyone else. That's not to say the huge hurt it would do to FreeBSD to all reviewers and the public at large, just to save you "a bit of a pain". Uh, Chuck, can you tell me how many BIND and Sendmail advisories there have been in the last five years? Wouldn't it be nice if we could just tell newbies, "hey, yeah, that Sendmail has a known security issue, pkg_delete it and then add this new one here". Or would you prefer to explain to someone who doesn't "have the least clue how to do it" how to upgrade BIND and Sendmail to the latest? The concept is beneficial from _many_ angles, not just the one I gave. Despite my tendency to promote the traditional BSD distribution style, that does not mean that I feel that everything in FreeBSD should arrive as it did on the 4.4BSD tape. I think that the ability to be able to select modules for inclusion or exclusion would be particularly useful. ... Joe --- Joe Greco - Systems Administrator [EMAIL PROTECTED] Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sat, 15 Apr 2000, Joe Greco wrote: Uh, Chuck, can you tell me how many BIND and Sendmail advisories there have been in the last five years? Wouldn't it be nice if we could just tell newbies, "hey, yeah, that Sendmail has a known security issue, pkg_delete it and then add this new one here". Or would you prefer to explain to someone who doesn't "have the least clue how to do it" how to upgrade BIND and Sendmail to the latest? The concept is beneficial from _many_ angles, not just the one I gave. Despite my tendency to promote the traditional BSD distribution style, that does not mean that I feel that everything in FreeBSD should arrive as it did on the 4.4BSD tape. I think that the ability to be able to select modules for inclusion or exclusion would be particularly useful. If you want to pick another one and by default install that, fine. If you want to force new users to read all about mailers just to get their first mail working, no, that's just too much, Joe, you're asking too much of folks. If you've got a bone to pick with sendmail, that's ok, but you have to pick a better one. If you can't decide on the best one, then how in the heck do you expect Joe Public to do better? ALWAYS provide sensible default values, not a bunch of expert questions. Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sat, 15 Apr 2000, Joe Greco wrote: Uh, Chuck, can you tell me how many BIND and Sendmail advisories there have been in the last five years? Wouldn't it be nice if we could just tell newbies, "hey, yeah, that Sendmail has a known security issue, pkg_delete it and then add this new one here". Or would you prefer to explain to someone who doesn't "have the least clue how to do it" how to upgrade BIND and Sendmail to the latest? The concept is beneficial from _many_ angles, not just the one I gave. Despite my tendency to promote the traditional BSD distribution style, that does not mean that I feel that everything in FreeBSD should arrive as it did on the 4.4BSD tape. I think that the ability to be able to select modules for inclusion or exclusion would be particularly useful. If you want to pick another one and by default install that, fine. If you want to force new users to read all about mailers just to get their first mail working, no, that's just too much, Joe, you're asking too much of folks. If you've got a bone to pick with sendmail, that's ok, but you have to pick a better one. If you can't decide on the best one, then how in the heck do you expect Joe Public to do better? ALWAYS provide sensible default values, not a bunch of expert questions. Chuck, Please go back and read what I _wrote_. Your response assumes I made statements that I certainly did not, and suggests to me that you missed every third word in my previous messages. :-( In particular, I advocated including Sendmail in the base system in a manner that would allow it to be trivially removed (or, alternatively, not including it but making it a selectable package, like X11). This could, for example, be done in the very same way that we currently do loads of other crap, like /usr/games, proflibs, etc. More ideally, it would be done in a format compatible with the package management system, so that one could simply "pkg_delete" Sendmail and install a new one. Am I getting through now? :-) -- ... Joe --- Joe Greco - Systems Administrator [EMAIL PROTECTED] Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
How will this affect this /etc/mail/mailer.conf "thing" (and I wonder why that was put there to begin with). If we're going to use a mailer.conf, then it should be able to work with other MTAs; which it probably won't because they perform their respective tasks differently. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CS4236b on Inspiron 3200
I have a dell inspiron 3200 with a cs4236b isa non-pnp soundcard. It works in 3.4 with the folowing kernel lines: device snd0 device css0 at isa? port 0x530 irq 9 drq 1 flags 0x13 device mpu0 at isa? with a hack to /src/sys/i386/isa/sound/sound_config.h changing #define DSP_DEFAULT_SPEED 8000 to #define DSP_DEFAULT_SPEED 32000 Question 1: what's the implication of changin that for other soundcards? Should it be changed in -current? Question 2: What do I have to do to get this card to work with pcm? I want to get rid of the isa compatability shims before they're removed. I've already tried device pcm0 at isa? irq 9 drq 1 flags 0x0 and device pcm0 at isa? port0x530 irq 9 drq 1 flags 0x0 with and without pnp code compiled in (not that I think it's relevant). Trivia that might help out: Card only works with the linux 4232 driver if it's already been initialized in Windows. ALSA works fine. any help would be apreciated. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sat, 15 Apr 2000, Joe Greco wrote: Chuck, Please go back and read what I _wrote_. Your response assumes I made I've got your message, I quoted it fully in my first response. You asked to "Remove Sendmail from the base system", and that's a direct quote, Joe. statements that I certainly did not, and suggests to me that you missed every third word in my previous messages. :-( In particular, I advocated including Sendmail in the base system in a manner that would allow it to be trivially removed (or, alternatively, not including it but making it a selectable package, like X11). No, you said remove it, or at least make it removeable. I responded that you can't just remove it. Go to your sent mail message folder, I'm not making this up. I said don't remove it (not "don't make it removeable"). You're the one who's sticking new words in. This could, for example, be done in the very same way that we currently do loads of other crap, like /usr/games, proflibs, etc. More ideally, it would be done in a format compatible with the package management system, so that one could simply "pkg_delete" Sendmail and install a new one. Am I getting through now? :-) You asked in your mail to remove it, I said you can't leave ordinary users without a good default. Your context in what you said was that it was a minor pain to have to remove the default mailer. I stand by what I said. You changed your message, and if you want, I can send your message back to you. If you argue *only* that some easier method be arranged so that mailers can be swapped out, that I fully approve of. I never said otherwise, and I don't like much the way you changed things. In fact, what the heck, here's your original message, cut out of my reply (where I quoted all of your part of the exchange): Perhaps it's time to revisit something I proposed several years ago. Remove Sendmail from the base system - or, at least, make it a "package" that is removable with the package management tool. Then be able to add another mailer (or an updated Sendmail) in its place. Ideally, Sendmail would be available as a package for installation as part of the base system, just like games or info or proflibs. I would love to see this happen with other components of the system as well, such as BIND. While it is fantastic that FreeBSD comes out of the box so fully functional, it does make it a bit of a pain for those of us who intend to build servers - we have to disable the original before installing a new package. :-/ Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Sat, 15 Apr 2000, Joe Greco wrote: Chuck, Please go back and read what I _wrote_. Your response assumes I made I've got your message, I quoted it fully in my first response. You asked to "Remove Sendmail from the base system", and that's a direct quote, Joe. Yes. That doesn't mean that it can't come with FreeBSD... manpages, games, proflibs, even X11, none of those are part of the base system, but people find their way to installing them. Somehow. Also, you've completely ignored that there was a latter half to that sentence. "Hmm." I love creative quoting, and I really have an aversion to being made to say something that I didn't, like "let's force users to choose a mailer". -- ... Joe --- Joe Greco - Systems Administrator [EMAIL PROTECTED] Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sysctl
On Tue, Apr 04, 2000 at 06:43:03PM +1000, Omachonu Ogali wrote: I don't know whether to hand this to -doc or here, so I'll take the risk of here, patch simply adds comments to sysctl variables. Before you get too enthusiastic about adding description strings to the declarations, you might like to work out: 1) How to store the descriptions so they are accessible to sysctl(8), but don't bloat the loaded kernel image. 2) How sysctl(8) should locate the descriptions. Note that your solution needs to include support for dynamically loaded sysctls. This issue tends to come up regularly. The last thread I recall was at the end of November last year in a thread on cvs-all. Have a look at http://people.freebsd.org/~green/sysctl.descr.patch for one implementation. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrating QMAIL in the world
On Fri, Apr 14, 2000 at 05:21:24PM -0500, Joe Greco wrote: Remove Sendmail from the base system - or, at least, make it a "package" that is removable with the package management tool. Then be able to add another mailer (or an updated Sendmail) in its place. Ideally, Sendmail would be available as a package for installation as part of the base system, just like games or info or proflibs. Sounds all basically like a good idea to have different choices for a MTA. But I don't like _basic_ system functionalities to be out sourced completely to ports. Two examples: If I give people a FreeBSD-STABLE snapshot CD, I'd like to give them a complete Unix, and for me a MTA belongs to a basic package. If I want to do a complete upgrade of all of my system ports, because I come to the conclusion - I installed to much experimental crap and don't get it sorted out manually - or I want to upgrade everything to the latest and greatest I don't want to kill my MTA (sendmail) by performing a rm -rf /usr/local/* action. FreeBSD - as is - has all the basic system functionality in the base system and I wouldn't like to have a "neutral" "castrated" Unix just for the sake, that you can start later to customize things like sendmail and maybe other things I would love to see this happen with other components of the system as well, such as BIND. definitively not. I hate the Linux way to have a puzzle system. Could we please still agree on a base system that is complete, so that SNAP CD's still represent a complete BSD without having to create additional ports ??? Again FreeBSD != Linux. While it is fantastic that FreeBSD comes out of the box so fully functional, it does make it a bit of a pain for those of us who intend to build servers - we have to disable the original before installing a new package. :-/ Well ... for that purpose I'd vote for the following: a) make more NO_ (sendmail, bind, whatever) knobs in /etc/make.conf as needed b) make the Makefiles in the install target more complete by removing (old) occurrencies of sendmail, bind, if such a NO_XXX knob has been set. Then you get such an ISP server as you like after a make world session c) Split FreeBSD packaging any further (bin, man, doc, compat,...) Add something like a package internet (sendmail, bind, ...) Then you can install a sendmail, DNS free system as you like. But I wouldn't for a generally castrated BSD. -- Andreas Klemm http://people.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD New APSFILTER 533 and songs from our band - http://people.freebsd.org/~andreas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Quickie question on UDMA/33
At 05:53 AM 4/12/00 -0400, Trevor Johnson wrote: Western Digital Caviar hard drives that should support UDMA/33, as should the Chipset. Both boot up, trying UDMA mode, throwing ICRC READ ERROR's then kick back down to PIO mode 4. Bios's are set to do auto-chose pio/dma modes. There may be a BIOS option that will disable DMA entirely. I've resolved to simply adding in the rc to reset them to pio mode, to get it over with (but I still get the errors at boot-up prior to the rc doing them). I simply use 'device ata' etc. forms in the knerel config. You might try commenting out this option (if you're using it): options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices That would apply only to the DVD, not the hard drives of course, but still there is no reason that reasonably modern equipment shouldn't work in UDMA/33 mode. Are the IDE cables new and in good shape? Using each end connector before attaching a device to the middle one... Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
