Slashdot Mirror
Linux 3.4 Released
jrepin writes with news of today's release (here's Linus's announcement) of Linux 3.4: "This release includes several Btrfs updates: metadata blocks bigger than 4KB, much better metadata performance, better error handling and better recovery tools. There are other features: a new X32 ABI which allows to run in 64 bit mode with 32 bit pointers; several updates to the GPU drivers: early modesetting of Nvidia Geforce 600 'Kepler', support of AMD RadeonHD 7xxx and AMD Trinity APU series, and support of Intel Medfield graphics; support of x86 cpu driver autoprobing, a device-mapper target that stores cryptographic hashes of blocks to check for intrusions, another target to use external read-only devices as origin source of a thin provisioned LVM volume, several perf improvements such as GTK2 report GUI and a new 'Yama' security module."
Hi,
I've always used Windowz and I consider myself an exceptional Visual Basic programmer, so I know computers pretty good. In fact I got an A- in my programming class last term. But I'm a little wary of how much power Microsoft has in the computer field. Many of my friends use RedHat and I've recently installed it on my machine at home. Although I haven't had as much chance to play with it as I'd like, I've been greatly impressed.
This weekend I gave some thoughts to the things that are wrong with Linux. I hope no one minds having some flaws pointed out. I'd like to help make RedHat stronger so it can conquer MS. Hopefully RedHat will hear this (crossing fingers) and address these. I think with a little effort, RedHat's Linux can defeat Microsoft's Windows! :)
To begin with, there are too many different flavors of RedHat. Browsing a list on Amazon, I saw they made varients under the codenames of Mandrake, Debian and Slackware, just to name a few. I know that I'm very new to RedHat so maybe this is obvious but it seems like RedHat should just sell a few different flavors of its operating system. Perhaps one for the desktop and one for a server? Could someone explain why RedHat produces dozens of different versions of Linux?
Secondly did you know that anyone can view the source code to Linux! I think that RedHat shouldn't make its code available. After all, what keeps Microsoft from stealing RedHat's ideas and putting it into Windows? My friend says that FreeBSD stole the TCP/IP stack from DOS a long time ago and Microsoft is always looking for revenge for that. Plus it seems to me like RedHat is just giving away its ideas for free. And what keeps hackers or terrorists from tampering with the code and putting a virus in every computer?
On a related note, why doesn't RedHat write Linux in assembly? My friend says that's what Microsoft does for Windows, and that's why Windows is faster and more stable than Linux.
Next RedHat definitely should kill -9 (ha, ha!) the command line. Microsoft finally gave up DOS when Windows 2000 came out. I'm suprised that RedHat hasn't migrated away from...whatever its version of DOS is called (Bash, I think?) But maybe this is planned for a future release?
Finally Linux needs games! RedHat will never be successful in the home without games. They should also tell M$ to release a version of Office for Linux too. And Internet Explorer!
Have a nice day! Go Linux!!
I tried btrfs, and ended up going back to ext4. Hoped btrfs might be a good choice for a small hard drive, and it is-- it uses space more efficiently. But it's not a good choice for a slow hard drive or the obsolete computer that the small size goes with.
Firefox ran especially poorly on btrfs. I was told this is because Firefox does lots of syncs, and btrfs had very poor performance on syncs. Maybe this improvement in performance on metadata is just the thing to fix that?
Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
As much as Linux is doing rather well despite the plethora of different versions and security risk from the open code base, using it is rather risky for legal reasons as well. Red Hat stole much of Linux from SCO's Caldera, and are distributing it without paying royalties, meaning users could be on the hook for several hundred dollars a license and casting the future of Red Hat's offerings in jeopardy.. Litigation is ongoing now, and experts expect SCO to win a crushing verdict any day now. Linux has some neat features, but there's a lot of fear, uncertainty, and doubt in the community about its legal future.
Yes! In the last RC! I'm not having that problem any more at all and 3.4 is rock solid on my systems.
At present there are two systems people use for audio, pulseaudio comes with most distributions these days standard (for end users, rather limited and full of latency) and JACK (for professional audio usage, uses a callback interface though)
low latency and low power tend to be at odds with each other, what with low latency frequently waking up the cpu etc. The only reason pulseaudio was went with on the desktop is for some reason they seem to think we care about a fraction of a percent more cpu usage on my plugged in desktop machine over a more useful audio subsystem. (Their reasoning being TABLETS ARE THE FUTURE!, or something along those lines)
They have, pulse for end users and Jack for people who care about their audio.
Why not one interface? Because the low latency goals of jack conflict with the low power goals of pulseaudio (designed for use on netbooks and tablets etc) why desktop users had to suffer so much into the pulse transition just to cater to that crowd I have no idea.
It's a common FUD. Nowaday Linux audio works just fine, PulseAudio as a sound server (mixer) and ALSA to talk to the hardware, the rest (OpenAL, gstreamer, OSS, ESD) are either obsolete or totally different stuff unessential to audio playback. Earlier problems related to closed source softwares (Flash, Skype) or badly written HW drivers are mostly fixed.
"Another" audio subsytem? Today standard is PulseAudio on ALSA, and that it has been like that for at least 4 years. Before ALSA there was OSS but Linux developers disagree with how OSS do the sound mixing and resampling in kernel space (for better latency, they said) and OSS went closed source for awhile. PulseAudio is an effort to unite all the sound server/mixer (ESD from GNOME, aRTs from KDE or ALSA's own dmix) plus some nifty features like better battery life (less wake ups per second).
Update your FUD once in awhile, please.
Achievement Unlocked
Most gratuitous use of the word "fuck" in a serious Slashdot post.
The Pulse/Jack difference isn't power consumption, it's intended use.
Pulse provides a simple API for just making noise.
Jack provides a low-latency API (like you said) for the purposes for music creation and other things that require true low latency audio (and no, that doesn't include games) with a significant trade-off in complexity.
The new x86-64 ABI with 32-bit pointers is cool because it allows you to get the architecture improvements of x86-64, such as extra registers and RIP-relative addressing, without increasing memory usage substantially due to larger data structures. Also, 64-bit operations will just use the 64-bit registers. The vast majority of programs simply do not need the extra address space.
One reason that this ABI works so well is that the majority of the x86-64 instruction set uses 32-bit operations. Some operations involving pointers can be done in one instruction without using a temporary register to load a 64-bit constant.
Windows actually also can support this, in theory, but you're on your own in trying to communicate with the Win32 API. The linker option /LARGEADRESSAWARE:NO causes the NT kernel to limit your program's address space to 2^31 bytes.
"Screw Sun, cross-platform will never work. Let's move on and steal the Java language." - Visual J++ Product Manager
Why do you need low latency for typical music playback on desktop? It is only for audio professional doing mixing from multiple sources. For laptop users like me, saving 1 W means 5~10% more battery life.
It is something the FS should handle. The "Just fix the program," is a bad answer because while maybe one could change Firefox, you'll find another program that can't be changed because the nature of what it does requires many syncs.
The low level systems should be robustly written to do what apps need, they shouldn't be telling apps "You can't do that."
What is the rationale for moving up to 3.4 so soon?
Obviously big tech companies, as well as the Mozilla Foundation play the versioning game aggressively, but the Linux kernel always had a reputation of being conservative.
It's true that most programs won't need 64-bit address space - right now - but that's only as long as their memory requirements are within 2GB.
And a lot of programs this is true, and will "always" be true. Will Emacs ever need more than 2GB for most people?
(And actually it's 4GB on Linux, or at least close to it.)
If that's the case, wouldn't there exist 2 versions of Linux in the tree
It's more like 99% of the code is shared, and changes depending on how you compile it.
wouldn't it make sense for the 32-bit Linux to have a 32-bit ABI, and the 64-bit Linux to have a 64-bit ABI?
That's how it has been, and those configurations will, of course, continue to be supported (in addition to supporting 32-bit apps on 64-bit Linux). They've just added the new x32 option.
You must be new here and not have seen many of my posts.
I think one of them not only used fuck a ton, but also got me a visit from the Secret Service.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
It's a common FUD. Nowaday Linux audio works just fine
My desktop still can't auto-switch between speakers and headphones when the latter are plugged in and out, on any distro (it just plays sound through both of them). The relevant bugs have been in Ubuntu database for years now.
Why is the GNU logo the one that marks this story, when it's specifically about the Linux kernel, and not GNU userland? Among the keywords, GNU shouldn't even be there for this story, and the logo for this story should have just been the penguin logo.
I think one of them not only used fuck a ton, but also got me a visit from the Secret Service.
Inquiring minds want to know. I always fancied inviting the guys in black suits to tea myself.
[Old Man mode]: I remember a time before PulseAudio, and before JACK, and before ALSA: The Linux kernel had some built-in drivers ("OSS-Free"?) which supported adequate functionality for every sound card/chip on the list, and if you wanted more features or support you could just pay 4front for a better driver (and they were always worth the minimal price).
And: Everything. Just. Worked. Always. Hardware settings (back when sound cards still had configurable analog sections(!)) were deterministic and reliable, and getting excellent sound from *random_app* was a foregone conclusion.
Much fun was had, for instance, with "cat /dev/audio > /dev/st0" to dump a radio show (reliably! without problems! in the plain-and-simple way that Unix is supposed to be!) to DDS tape.
Now, this was 17 (or so) years ago. Anything involving further difficulty, at any stage of the game on a user level, on the Linux sound front is a step backward.
Now, get the fuck off my lawn.
[/Old Man mode]
Kid-proof tablet..
That's a bummer.
As a counterpoint: Can you tell me how to turn off that same feature under Windows? I *don't* want it to auto-switch, but it insists upon it.
Kid-proof tablet..
Right, Linux audio works nowadays. Almost. Except when PulseAudio starts corrupting audio. Or stops outputting audio. Or hangs. Or forcibly mutes my headphones, requiring me to call amixer after PulseAudio has started. Or requires me to re-learn something that I learnt to do with ALSA, and now I need to start over. And except when GUI tools decide to hide ALSA devices when PulseAudio is running, ruining my ability to unmute my inputs or fine tune my volume control in many other ways.
And I can't "stop using PulseAudio", because: /etc/apt/preferences.d. I learnt how to use APT pinning solely for getting rid of PulseAudio. That should speak volumes for how broken it is.
1. When somebody asks me for help with their audio, I can't simply go and uninstall it every time.
2. Certain distributions, such as Ubuntu, make it extremely difficult to remove PulseAudio.
3. Even distributions like Debian do install it automatically, so you need to ban it in
Funny enough, I was using PulseAudio long before it became popular, because it was arguably the best network audio server for casual use. I had to stop doing that because it started breaking the sound in many applications, playing with my volume, etc. It was also funny when the authors decided that the mode in which I was using PulseAudio (as a system-wide daemon) was "unsupported", and asked distros to get rid of their init scripts, thereby breaking my dedicated sound server. Not that it isn't trivial to fix, but why would anyone remove a feature in that manner? It was probably the distros fault, since Debian are still keeping the init script, but I wasn't using Debian at the time. One day I had my sound server working, and the other day I was greeted with a message telling me what I was doing is a bad idea and I should stop doing it ASAP.
Actually if I have any complaint about Linux its the fact that most of your assistance comes from google (the same with any os/complex hardware) and there is so much outdated documentation out there.
I agree, that is why I include my distro name and version in my search, plus you can limit results in time (pages update in the las 24 hours, month, year, etc...).
Tomorrow is another day...
I still remember that message, on Oct 1991, from a guy by the name of Linus Benedict Torvalds on comp.os.minix
"Do you pine for the nice days of minix-1.1, when men were men and wrote :-) "
their own device drivers? Are you without a nice project and just dying
to cut your teeth on a OS you can try to modify for your needs? Are you
finding it frustrating when everything works on minix? No more all-
nighters to get a nifty program working? Then this post might be just
for you
Muchas Gracias, Señor Edward Snowden !
This sounds like a driver bug, in which case you shold file a bug upstream. Both my wife's laptop (Ubuntu 12.04) and my laptop (Archlinux) do this without problems, plus you can turn this feature on/off in alsamixer.
for i in `facebook friends "=bday" 2>/dev/null | cut -d " " -f 3-`; do facebook wallpost $i "Happy birthday!"; done
Start Pulseaudio? Never even heard of that. On windows I just chose the recording source Stereo Mix. Why does linux make it difficult?
Starting from Windows 7 Microsoft has hidden the Stereo Mix option (due to pressure from Big Media?), so it's not that easy anymore.
I know this is a funny troll but you are right about the games. The only reason I still use windows as my primary OS is that lack of big titles on Linux.
If the measure of a troll is how seriously people take it, GP's doing very well...
It took about 4 reads before your post didn't say "titties".
the GNU animal
You mean, a gnu?
It's a common FUD. Nowaday Linux audio works just fine
Well, sometimes getting audio to work is beyond the control of the Linux kernel. If the system has integrated audio on the motherboard (e.g. a laptop) the ACPI DSDT (Differentiated System Description Table) supplied by the manufacturer in the ROM can instruct the hardware to behave differently under different operating systems, or provide different descriptions of the hardware (e.g. audio inputs and outputs) to different operating systems. That's why it's common to have little glitches in Linux audio, like not having the right mixer controls.
The DSDT is written in a language called ACPI Source Language (ASL). Intel and Microsoft both provide compilers for ASL, but the MS compiler accepts buggy, non-compliant DSDTs. Since for some vendors (Toshiba) the job is considered done when stuff works under the current version of windows, they ship their laptops with DSDTs that won't work under anything but Windows and might not work in future versions of Windows.
Since the kernel writers have no way of knowing what specific hardware is in your machine except what your machine tells the kernel, they can't fix this. It's entirely the manufacturer's fault, although users blame Linux because everything works in Windows. Getting stuff working isn't exactly a nightmare, but it's beyond most users' capability. You extract the DSDT from ROM, decompile it, fix the bugy ASL, compile it, then put the fixed DSDT in your initramfs (remembering to do this again every time you install a new kernel). Sometimes using a linux boot parameter to masquerade as Windows to the hardware works.
So to recap: the Linux audio system may be fine, the hardware drivers may be fine, but if the manufacturer fails to supply a correct description of what the hardware contains to the Linux kernel, audio might not work.
Disclaimer -- this information is a few years out of date, as I've stopped using Toshiba laptops and use Asus instead. However I'm fairly sure it still exists with certain manufacturer's laptops, which have worked flawlessly for me under Linux.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
No, that would be rms
Except in the old days Microsoft had a version of NT for DEC Alphas.. so I doubt too much was in x86 Assembly as all that code would have to be completely re-written (well not just re-written in the sense of modifying C code for the new platform, but the whole dang thing).
I can't remember if they had any other variants than the Alpha versions though.. it's been too long :)
There were five variants as of NT 4.0 : x86, Alpha, Mips, Sparc, and (I think) PPC.
DEC Alpha was usually served up with ISA slots, and it could execute x86 code to use those.
The recently released (11th May 2011) Pulseaudio 2.0 lists improved jack detection as one of its features so you will probably be waiting longer for a fix to show up in a non-rolling distro...
Yes, the GNU GPL licensed kernel doesn't have anything to do with GNU.
Dilbert RSS feed
Sparc was never there, although Intergraph mulled over the idea for a bit before settling for Wintel. PPC was there very briefly. The only RISC platforms that lasted a while was MIPS and Alpha. OTOH, NT was developed on both an i860 as well as a DECStation 3000 (using MIPS) but never actually supported either of those platforms.
Also, the first DEC Alpha PCs had EISA slots, not ISA, while the OVMS workstations used TurboChannel. Later, w/ the AlphaStations and AlphaServers, DEC switched completely to PCI. As far as the Alpha went, they had something called a Privileged Architecture Layer (PAL) which was the the layer in the OS that interacted w/ the CPU. It was there in all 3 - NT, OVMS and Unix (a.k.a. OSF/1 a.k.a. Digital Unix a.k.a. Tru64). I'm guessing that the AXP versions of Linux and BSD have that as well.