search for: _until_

Listmates, I am experiencing some quirks with the new ATI 8.1 (8.452) driver and compiz-fusion on 10.3. Of note are: (1) Invoking the run command with Alt+F2 correctly opens the run dialog, but the cursor is frozen and will not take any input _until_ the "Options" button is clicked or activated with Alt+o. Then the cursor begins blinking normally and input is possible. If the options pane is closed before a character is input the cursor freezes again and disables and keyboard input. If any input is made in the command line input field...

Dear List, I'm running NUT 2.4.1 on openSUSE 11.3 64 bits, kernel 2.6.34. The UPS is an Eaton Ellipse ASR 1500 USBS. With driver usbhid-ups NUT works perfectly _until_ I turn off IPv6. By default IPv6 is turned on in openSUSE 11.3. I visited YaST -> Network Settings -> Global options and deselected "Enable IPv6". I then restarted the box. When I entered the command "rcupsd start" to start NUT, I received the reply: Starting NUT UPS...

> How's forever work for you? ;-> Absolutely FINE thank you! When your WizWonder package is housebroken, let me try it if I'm interested. Until then, a (stubbornly) broken distro will persuade me to try something else. That's why I left Windows, I guess, if you prognosticate correctly, it will be why I leave RedHat/CentOS. btw this has nothing to do with Firewalls at

Has anyone installed Linux (CentOS or other) on a Tyan K8SE (S2892) motherboard? I'd really like to hear your experiences -- with this board or Nvidia's nForce Pro chipset in general. I'm looking to build a new server using this board but would like to find some other experiences first. I've googled myself blue but haven't found any reviews or postings regarding this

After searching the mailing list archive (I forgot to do that before posting, sorry!) I found the solutions: 1) The documentation has a mistake: The bit terminator is NOT set automatically! (I'm using the latest speex version!) It has to be set manually using speex_bits_insert_terminator(&bits); 2) speex_decoder_int() has to be called as long, as it returns -1. After that, all frames

...lace where to reserve disk geometry, Microsoft choose part of Cylinder 0 where it's MBR doesn't reside. Unfortunately, many 3rd party boot managers, including GRUB, do use part of that space. I've run into this first-hand where I had no problems dual-booting on even a 800GB disk array _until_ I upgraded to NT5.1SP2 (XPSP2). After the upgrade, GRUB was broken. After re-installing GRUB, it would no longer boot XP, because GRUB overwrote the hidden geometry info in Cylinder 0 that XP needed for boot-time support. After a few more systems, I discovered that XP only wrote it if the boot v...

1: e-mail is a people skill, you affect people with it. The value of your presentation rises or falls with your skill at presentation. 2: My embedded headless linux targets live in isolated networks, even relative to other computer or network equipment at the target site. At times, the nearest land is 2 miles straight down (ocean floor). 3: These targets are also without

Bryan J. Smith b.j.smith at ieee.org wrote: >Not only that, but people forget that SPARC is not sold by just Sun. >SPARC is an IEEE standard licensed under "fair and non-discriminatory" >terms. The SPARC ISA and most architectural details are freely >available. Yep - but what is your point with bringing that up? >The _majority_ of my Solaris/SPARC experience in more

...y added NTPL, but there have always been a few changes from a .0 to a .1 as things are more finalized. Every .0 revision has made some poor considerations in a few regards, and after the "early adopters" start using it, they are exposed. The reality is that most things are _not_ exposed _until_ people actually start using things. Even Red Hat Linux 7[.0] was regression tested to the anal power with GCC 2.96 and its ANSI C++ requirement, and it wasn't until after Red Hat released it that the projects that weren't writing ANSI C++ compliant software took note. People like to throw...

...ter all this, am I just an asshole? Or am I merely trying to explain the realities of Red Hat's _real_ history? People who believed that Red Hat would support .2/.3 releases more than 2 years, or every little .0/.1 release more than 1 year were lying to themselves. Red Hat never ran into that _until_ they tried to introduce Red Hat Linux 8.0 and drop support for at least 6.2, 7 and 7.1, as well as 7.2 now that 7.3 had been out. Not even SuSE promised to support their releases more than 2 years, and have typically fallen short. And only the Debian project seems to have a history of support on-...

...(UnixWare 8) as a competitor so it squashed it while it could. Caldera-SCO tried to continue for 18 months, but their entire future was built on low-volume, but high-end sales of UnixWare 8 while their Linux volumes increased. The result was the March 2003 filing, one that I questioned at first, _until_ I read items #50-55. That's when I realized Caldera-SCO was suing for: A) Breach of Contract: Withholding Monterey/IA-64 B) Breach of Non-Compete: Developing Linux/IA-64 Caldera-SCO figured IBM would want the rights to UNIX(R), and IBM would settle in short order. When IBM didn't,...

...ng and not understand why. I strive to understand why, what it affects and how that affects things. Again, I have explained many things, Fedora Core, enough times now that I know the regulars are sick. But understand I am _not_ the only one in these threads, and some people seem to wait to point _until_ they come up -- and not bother to help people with other questions. They can't complain about me without being hypocrites in return. Now I experimented with only helping people off-list at the end of last week and over the weekend. I think I'll go back to that for the sanity of everyone...

hey fletcher, thanks for your input here. :+) and -- quite obviously -- your program will be whatever it is that _you_ think that it should be. of course. the thing is, i am certain that i have been clear that the feature that i believe will be "killer" is on-the-fly formatted display. that's my stand. and i'd say my reasoning has been equally clear, namely that this

Dear FreeBSD users and system administrators, While the FreeBSD Security Team has traditionally been very good at investigating and responding to security issues in FreeBSD, this only solves half of the security problem: Unless users and administrators of FreeBSD systems apply the security patches provided, the advisories issued accomplish little beyond alerting potential attackers to the