Become a fan of Slashdot on Facebook


Forgot your password?
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Re:Is XFCE going the bloat-path? What happened to (Score 1) 91 91

I've always been under the impression that all of the 'bloat' is packaged as additional packages in XFCE. At least in my experience, if you install just the minimum of xfce packages, you get no bloat, but also *SHOCK* are completely lacking in any features beyond the basic window management, task bar, and program launcher.

Comment: Re:Small phone for First World (Score 1) 167 167

I have a S4 Mini, it is slightly larger than my Aria was, and around the size of my Old Evo3d. It's about as big as I want to have in my pocket (and not even skinny jeans, just regular old pants). It's an 'old' generation, but I got 4.4.2 working on it fine (yes, I, I did the actual build and released it on Xda), and will eventually get around to getting 5 working on it. It's a dual core snapdragon 1.7ghz with 1.3gb of ram(probably 1gb and something messing with it in my CM rom). I've been happy with it for the year I've had it, and won't upgrade until something else this size comes out.

My only complaint is it's a Spring 'Spark' device, which is tri-band LTE, but doesn't support SVDO/SVLTE (Simultaneous Voice and Data) so when I get a call and I'm tethered, the data drops.

Comment: Re:Why do Windows programs just run? (Score 2) 126 126

I missed the key point of it being keyboard backlight, lol....

Yes, it is very safe to assume that it's the bios vendor (Lenovo in my case, acer, hp, dell, you name it in the other cases). It boils down to there not being a consistent way to control backlights across laptops.

Comment: Re:Why do Windows programs just run? (Score 1) 126 126

Actually, with VERY few exceptions, you can run very old userspaces with new kernels. There have been a few 'fixes' that broke old userspaces (by exposing bugs in userspace that weren't triggered pre-fix), but there's a very strict, never break userspace rule. Sometimes you have to set the correct kernel build time options, but it's expected of a person doing that to know what they're doing, or to trust their distro to know what they're doing.

Look at the recent Linux Wireless mailing list... A few weeks ago, the ability to use 'Wireless Extension Compatability' to control wireless was made unselectable. They have been marked deprecated for YEARS(2008), and are now causing problems with supporting newer wifi features. This was very firmly 'NACKED' by Linus, and the wireless tree has to continue supporting an old, broken, way to control wireless devices.

There are also options you can configure in the kernel like 'COMPAT_VDSO' which work around 1 released version of GLIBC (2.3.3), which was also backported to OpenSuse 9.

I know that it may not have been until the 2.6 era that this became truly 'written in stone' law, but it's always been a pretty firm 'rule'. Hence I can still run a.out binaries on my 64bit system. 'ELF' binaries were added around 2.0 (15-20 years ago?), and have been the default since some time between then and now. Still, a.out support will always live on, because you don't break the kernel to userspace abi.

Comment: Re:Why do Windows programs just run? (Score 2) 126 126

This has been a perpetual problem on my Lenovo W510. In one release, it did multiple steps, in the next one, no backlight control at all. I add some kernel command line options and get a crappy 4 step backlight. In the next release, I have to remove those options because my backlight didn't turn on at all with them. Now no working backlight controls (using the FN+Home/End combo on my laptop keyboard). I poke in the /sys sysfs mount at the backlight control that's registered, and can control the backlight that way. I've been following the ACPI development mailing list and this is a perpetual topic of confrontation.

There are lots of proposed fixes that would just resolve it, but they can't be accepted because they break userspace. The whole problem stems from the Laptop bios. In some cases, the bios will advertise ACPI methods to control the backlight, while the GPU driver exposes the controls as well. Depending on the particular bios version (and sometimes even bios settings), the keypress might, in bios, change the brightness, then report the keypress, or it might report the keypress and depend on the OS to use the ACPI interface to control the backlight, or it might depend on the OS to use the GPU driver interface to control the backlight. On some of the systems, the ACPI interface is sometimes broken, and on some, there are multiple controls (for display port and all the other possible display connections built into the system) with no clear way to determine which one to actually use. Some bioses report to work with 'Windows 2012' but actually completely don't. Some ONLY work with that, but report they work with older ones.

From what I recall of the discussion, Windows 8 deals with this by punting the actual event handling to the GPU drivers, expecting them to know how to handle the hardware.

Similar bugs can be seen in Windows if your run a newer version on hardware designed for a previous version (I saw this running Windows 7 on hardware designed for Windows XP, an old Dell laptop).

I find it kinda crazy that every single other feature of my laptop works perfectly (FIngerprint reader, color calibration, wimax radio {none of which I actually ever use}) while backlight which seems so simple (Press button, change brightness) is in a perpetual state of brokenness.

Comment: Re:Joyent unfit to lead them? (Score 1) 254 254

These 'trivial' changes often cause merge conflicts with other trees. If people are developing against the 'pre change' tree, any changes around the comments might need manual merging. Manual merging introduces additional opportunities for mistakes. I see trivial comment patches like this bounced on these exact grounds in watching active linux driver changes; particularly if you watch a new vendor driver submitted to the staging tree, and then watch it get cleaned up to be in-line with the kernel's coding style.

As far as this PARTICULAR patch being dropped, it probably could have been handled more in line with 'NACK: We'll set a date in the future to do a comment cleaning and have everyone rebase on that', but my first reaction isn't that the developer who declined it is sexist (or whatever the particular flavor of discrimination is). From my PERSONAL Point of view, a change should provide value, and I *PERSONALLY* don't see value in a change like this. A typo fix maybe, but this is not a typo.

Comment: Re:The US slides back to the caves (Score 1) 528 528

The reason I've always heard is pure cost to convert. All the signs, all the cars, everything that uses distances (all the laws would have to be 'amended' to the new units), etc, etc. There is a LOT of infrastructure in the US. It's a physically large country. Even 'phasing' it in is a HUGE undertaking and would take years if not decades to complete.

I am 100% in support of us converting, but I'm glad I don't have to be one of the people that's going to coordinate the madhouse it's going to be when it's finally decided upon and started.

Comment: Re:Unsafe at any speed (above 100 MPH)... (Score 1) 443 443

the difference is, it doesn't take the same energy. In the kinetic energy equation, look at the V^2 term. If you start at velocity X, and increase your speed A, your resultant velocity component will be (X + A)^2. Multiplying that out, you get X^2 +2AX + A^2. To go from 0 to 10 mph, you have to add 2 * 10 * 0 + 10 ^ 2 = 100 units (I don't remember the American unit applicable here). To go from 90 to 100, you have to add 2 * 10 * 90 + 10 ^ 2 = 1900 energy units. It takes 19x as much energy to increase speed 10 mph at 90mph IGNORING DRAG.

The X^2 gets ignored because we're only considering the amount of energy we have to ADD to go from X to X + A, and the KE at Vx will end up canceling out the X^2 in the resulting equation subtractions.

Getting the job done is no excuse for not following the rules. Corollary: Following the rules will not get the job done.