mpg123 weirdness with 4.3-BETA #2
Over the weekend I upgraded hardware and software at the same time. I went from 4.1-stable to 4.3-BETA #2, and upgraded to a 1100 MHz T-bird mobo. Same genuine SB16 sound card. Before the upgrade, mpg123 running under gqmpeg gave the clean, clear sound. Now it's laced with static. The card and wires seem OK - xcdplayer plays CD's static free, it's only mp3 files with a problem. Ideas? Known t-bird problem? Thanks, --- David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Different output from pkg_version
If memory serves me right, Dag-Erling Smorgrav wrote: Martti Kuparinen [EMAIL PROTECTED] writes: [...] The only solution for my problem might be to reinstall the port so that this ORIGIN-entry would be created. I haven't checked the source code so I'm not 100% sure but this seems right so far... Your analysis is correct. Note that bash won't work any differently if you reinstall it, the only difference will be that pkg_version will be better able to tell what version you have. (Sorry for the late reply, I'm working through a two-week email backlog.) DES is correct; the newer pkg_version (which uses the ORIGIN directive) is better able to make a determination about what's current. "up-to-date with index" in more recent versions of pkg_version is the equivalent of "up-to-date" in older versions (the ones that only checked the INDEX file). Martti, you didn't say why this was a problem for you...or was this just simple curiosity? Bruce. PGP signature
Re: CVS_RSH in 4.3-BETA
If memory serves me right, Kris Kennaway wrote: On Wed, Mar 14, 2001 at 11:00:00AM +0100, Michiel Boland wrote: Somewhere between 4.2 and 4.3, someone changed the default for CVS_RSH to 'ssh'. This does not appear to be documented anywhere. The info file still says that 'rsh' is the default. Can the docs be fixed? Or a line added to RELNOTES.TXT? I'm pretty sure this is going to bite a lot of people. It should be added to RELNOTES.TXT once the relevant committer (preferably the person who merged the change) gets off his proverbial and adds it. Can you submit a patch against the info file? The change to RELNOTES.TXT is awaiting approval for a commit (and I just got approval as I was typing this). I once thought of doing the info file, but I won't have time. Bruce. PGP signature
Re: Perl 5.6 merged soon?
I've got a tarball of the port skeleton at http://www.gsicomp.on.ca/oss/perl560.tar for anyone who wants to take a look. Please let me know of any problems (or enhancements) that it needs. [ I haven't looked at the -pthreads / -lc_r issue yet. ] Once it goes through the paces I'll make it into a PR and convince a committer to work their magic. I'm looking at this now. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RELNOTES.txt Update needed
If memory serves me right, "Ken Menzel" wrote: Hi, The RELNOTES.TXT file of freebsd-stable (beta) states in the disk section that DPT V RAID controllers are not supported, when in fact they now are with the new asr0 driver (noted in HARDWARE.TXT). Support for DPT V, and VI as well as adaptec 2100,2200 and 2300 RAID cards. Is this something that can be updated for the new release? For what architecture? My copy of the i386 release notes for RELENG_4 show that the DPT V and VI are supported, as well as the Adaptec 1400, 2100S, 3200S, and 3400S SCSI RAID controllers. The alpha release notes don't reflect this because, to the best of my knowledge, this hardware either isn't supported or hasn't been tested. (Mike Smith's RAID controller page says that they're not supported.) Does this match your view of the world, and if not, can you give me some more data to help me Do The Right Thing (TM)? Thanks, Bruce. PGP signature
microcputime?
Booted this evening on my laptop and now I'm getting warnings that microcputime went backwards? What gives and why would it start suddenly when it was OK at 2pm this afternoon? david To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: BETA induced nervousness
On Mon, Mar 19, 2001 at 03:04:54AM +0100, Dag-Erling Smorgrav wrote: | j mckitrick [EMAIL PROTECTED] writes: | Sounds good to me. It would cut the s/n ratio. | | I really hope you meant the reverse :) Ah, of course! :) jm -- --- Jonathon McKitrick -- [EMAIL PROTECTED] "It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here." --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: microcputime?
Seems to be a problem with FreeBSD and APM on VIA chipsets. Are you using this combination? Tom Veldhouse [EMAIL PROTECTED] - Original Message - From: "David Reid" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 19, 2001 4:10 PM Subject: microcputime? Booted this evening on my laptop and now I'm getting warnings that microcputime went backwards? What gives and why would it start suddenly when it was OK at 2pm this afternoon? david To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ceil and floor?
I'm running into problems in GTK+ with these symbols not being defined. Both -lm and -lc_r are being passed to the linker, so I'm at a loss to explain why they're being missed. Any ideas? BTW, should we still be using -pthread for a threaded build? david To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re:stable-supfile
Thanks for the prompt response, solved the problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: No ping reponse on pccard
In message [EMAIL PROTECTED] Pierre-Gilles Mialon writes: : I have a network at home and since I upgrade to stable 4.3beta, : my Netgear FA410 TXC doesn't answer on the icmp request. I can : nmap localhost from the computer itself but I cannot ping or ssh it The FA410 needs hacks to the ed driver that haven't been MFC'd. There's a program called fa-select that will work around the problem until that can be corrected. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA
FreeBSD-stable doesn't have releases as such, does it? That is, if you cvsup you get the stable track as it exists that minute. It's *called* "stable" most of the time; as a release gets close, it is renamed BETA and then RC (release candidate), until the day it's truly officially blessed and it is named RELEASE and that version number is frozen. The next day (probably the same minute, actually), the label gets switched back to STABLE and the version number is incremented by one. Regardless of the label, though, it's exactly the same animal. Thus, after 4.2-RELEASE, we got 4.3-STABLE, which is now 4.3-BETA and will become 4.3-RC, and finally the same code base will be frozen into 4.3-RELEASE, at which time 4.4-STABLE will come into existance. "[EMAIL PROTECTED]" wrote: When is the next FreeBSD-stable release Regards, JB --- Mensaje Original -- De: Haikal Saadh [[EMAIL PROTECTED]] Para: Mike Meyer [[EMAIL PROTECTED]], Francisco Reyes [[EMAIL PROTECTED]] Cc: Mike Meyer [[EMAIL PROTECTED]], Haikal Saadh [[EMAIL PROTECTED]], [EMAIL PROTECTED] [[EMAIL PROTECTED]] Asunto: Re: 4.3-BETA Fecha: 18/03/2001 23:23:56 Mensaje: --- Mike Meyer [EMAIL PROTECTED] wrote: Francisco Reyes [EMAIL PROTECTED] types: On Fri, 16 Mar 2001, Mike Meyer wrote: Haikal Saadh [EMAIL PROTECTED] types: --- Matthew Emmerton [EMAIL PROTECTED] wrote: What is a BETA system? Is it similiar to CURRENT? Please search through the mailing list archives before asking questions. This has been answered many times over the last two weeks. Or maybe just read the FAQ URL: http://www.freebsd.org/FAQ/admin.html#dmin.html#RELEASE-CANDIDATE , which makes it clear that the name changes just identify what point of the release cycle that particular snapshot of -STABLE is at. I have seen several people tell Haikal to read the FAQ, etc I really have to agree with him. I don't think having a "Beta" label on what is defined in the handbook as "Stable" is a good idea. By definition a "new user" to FreeBSD is someone who doesn't know yet what are the right places to read/check. In that case, where did they find the information needed to upgrade to -STABLE? I think responses like the ones he got are the reason we consistantly over the years get views of sometimes been unfrienly to new users. We're definitely friendlier to people who show evidence of having done some research themselves than to those who don't show that evidence. Personally, I always provide a pointer to existing documentation rather than type it in myself. That saves me typing, and the users should learn about another valuable resource that works faster than the mail lists. Haikal wasn't asking for help, he was suggesting inappropriate changes to the system to try and help people who had gotten past the newbie stage - as demonstrated by managing to update to -STABLE, getting both userland and kernel - past a problem. Perhaps a label of "Pre-Release" may be less confusing. "Beta" sure gives the wrong impression. That suggestion isn't inappropriate. On the other hand the label "-RC" (release candidate) stil generates problems, so I'm not sure it would work. I suspect that *any* change in name will generate "I tried to get -STABLE, and got -FOO" messages. Not changing it would make life difficult for users who *wanted* to know they were getting a BETA or RC version. Possibly this information needs to go in the handbook on tracking -STABLE, rather than a FAQ. Or a Comment in the example supfile saying "This Can Get A Beta Release If A Code Freeze Is In Effect" kinda thing? I read the handbook chapter on CVSUpping, as well as the bit in The Complete FreeBSD, but it really was an information overload, and I just ended up having a go with the given example supfile. __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- "Brian, the man from babble-on" [EMAIL PROTECTED] Brian T. Schellenberger http://www.babbleon.org Support http://www.eff.org. Support decss defendents. Support http://www.programming-freedom.org. Boycott amazon.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA
On Mon, Mar 19, 2001 at 08:33:03PM -0500, The Babbler wrote: Thus, after 4.2-RELEASE, we got 4.3-STABLE, which is now 4.3-BETA and will become 4.3-RC, and finally the same code base will be frozen into 4.3-RELEASE, at which time 4.4-STABLE will come into existance. Almost. 4.2-RELEASE started 4.2-STABLE, just as 4.3-RELEASE will start 4.3-STABLE. Note that cvs-wise, only 4-STABLE exists. We just call everything after 4.3-RELEASE in 4-STABLE, 4.3-STABLE. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me 'Het leven is een stuiterbal, maar de mijne plakt aan t plafond!' - me To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
