Slashdot Mirror
Linux 4.1 Kernel Released With EXT4 Encryption, Performance Improvements
An anonymous reader writes: The Linux 4.1 kernel has been announced and its release brings expanded features for the Linux kernel including EXT4 file-system encryption, open-source GeForce GTX 750 support, performance improvements for Intel Atom / Bay Trail hardware, RAID 5/6 improvements, and other additions.
In RHEL 9
Read More button gone. Stupid share button in its place.
Building the kernel now.
Very cook feature list, with arguably the best feature being that they managed to keep kdbus and more systemd nonsense from infecting the kernel code. I'm especially looking forward to trying out ext4 encryption on my laptop.
The Future of Human Evolution: Autonomy
You're not expected to read it, but you are expected to work for free by promoting it.
Does it support samsung 840 and 850 pros yet for production?
http://saveie6.com/
Which distro are you using that isn't already infected by systemd? I'm SO glad Gentoo still allows me to use OpenRC...
Me too! I use both funtoo and gentoo, at work and at home, but here's a pretty good sized list of options for those who like debian, arch, and other distributions:
http://without-systemd.org/wik...
If you're stuck with Red Hat, your choices have been pretty much taken from you, and you should probably be looking to change to something else, but otherwise you probably have the choice of using OpenRC or upstart, and someone has probably already figured out how for you.
The Future of Human Evolution: Autonomy
Am a Debian fan, and seriously pissed that Debian decided to slide down the systemd shithole, so I decided to check out the Debian fork, Devuan.. Seems they have taken Jessie and ripped that systemd abortion out.. Am currently running it in a Virtualbox vm, time will tell if I go with Devuan over Debian....
THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
What is amazing is that it didn't take them 15 years to slide down that shit hole.
Heaven forbid they provide a reasonably up to date kernel or gcc, but they have no problems adding this abortion and squelching all complaints.
Makes you wonder what RH is doing behind the scenes and why.
Well, linux isn't necessarily just for servers. Can also be used for desktop and portable equipment. But let's talk servers here.
A couple of years ago, offices here in Austin, Texas were broken into for the company C3 Productions (owners of Austin City Limits and Lollapalooza music festivals). All their servers were taken. Now, I doubt they were hosting their ticketing ecommerce website from within their offices. But those servers probably contained email and files related to contracts with major entertainers. SSN and bank deposit details were likely included therein. It pretty clearly was a targetted attack and I don't think the thieves were looking to fence the hardware.
ext4 encryption has a lot of promise, and I consider this a big feature. It essentially functions like EncFS/CFS, but instead of being a secondary filesystem accessible via FUSE, it is part of the main filesystem. The closest thing it parallels is AIX's EFS.
I'm not surprised that Google coded this part. It makes perfect sense for Android. Encryption of /data can be turned on immediately during a device setup without having to worry about block level items, or if the device crashes during the /data encryption process.
Overall, an add-on which is definitely needed. Since Google mainly uses ext4, this is their best bang for the buck, and I hope the maintainers of other filesystems toss something similar in their code.
This post has no useful content. That said:
I just wanted to say thank you very much for the link FreeUser! It's been slightly frustrating at best trying to keep up with all the partial yet somehow already out of date blogs to get the same information.
It is very much appreciated.
After I fixed my dog, he just sleeps alot and got fat.
The "Ads Disabled" checkbox did elimnate a lot of leg humping.
Have gnu, will travel.
the doc https://docs.google.com/docume... noted in the mailing list post fails.
is it as simple as issuing adding an option to the makefs.ext4 then a mount command for a partition and providing the password to a prompt?
There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
Simple adblock filter of 'slashdot.org###firehose-000' does the trick for me (for now...). Such an eyesore and waste of space otherwise. I'm here for the text, and being able to consume the content quickly and efficiently, I don't have time to watch and listen to video/audio garbage, you can't "skim-read" such type of media to pick out the useful points quickly. Yet another mindless web-2.0-ification waste of time as far as I'm concerned. Sure video/audio has it's places in communicating some forms of information e.g. complex gaming walkthroughs where it's easier to show something in pictures than describe in text, but this place doesn't seem suited for it.
Capcha: dogged
Red Hat is Linux. End of story. What Red Hat says, everyone (that matters) does.
I'm starting to think GNU is the problem with "GNU/Linux" these days.
Does anyone know why you want encryption directly in the filesystem rather than the layered approach being offered for years by the dm-crypt kernel filesystem? The Phoronix article mentions that is intended for Android systems, so my immidiate thinking was that it had something to do with flash storage specifics. Generally I do not like it when a generic, simple solution like dm-crypt gets reimplemented at another layer, increasing complexity, but maybe there is a reason for this?
Another article mentions F2FS (Flash-Friendly File System) as a possible merge target. Suggests it serves needs for flash memory. I guess exposing the filesystem structure/metadata without actually revealing the data itself makes more efficient flash utilization possible. Or maybe it makes it easier for law enforcement to bypass it, if your tinfoil hat is on.
The mailing list entry itself is here: http://thread.gmane.org/gmane....
Links to a design document in the mailing list was dead at time of writing.
I browse in full screen mode on a 30" 2560x1600 monitor. Some would say this is folly, none the less it's what I do.
The article news headline is on the far left 1/4 of my monitor.
The comment quantity per article is over a fucking foot to my right and I have to glance at how many comments there are, per article, left, right, left right.
Put it back below where it belongs.
I don't like or care about a dopey share button - if you keep it, fine but don't make the comments number worse due to it.
I hate to cite fucking reddit of all places but isn't their score, comments and news headline all left focused? All the "important shit" is on the left, grouped together?
Cmon people fucking think would you?
I've got some ideas for a new type of discussion system that has never been implemented before, but which is way better than anything anyone else is using. If someone wants to build a better slashdot, get in touch and let's talk. I'm so sick of this piece of shit. Replacing slashdot is not enough; we need to take down reddit too. Who wants to create the best forum on the internet?
Anyone else think it's stupid for a site to make people wait half a fucking hour between posting comments? Especially when said site could use all the comments it can get? Especially when one has a brand new account and would like to simply begin posting without being nannied and controlled and made to wait? Especially when the sole karma one has been able to earn over the past week is one solitary -1, Flamebait by some prick (or Dice employee) who didn't get the joke? This site is fundamentally broken in so many ways.
My email server is gmail; user is nathan.klein, with a ".17" added on before the 'at.'
(Note: anyone who attempts to argue with anything posted in this comment is wrong, and nobody here has any use for your incorrect and harmful opinion.)
Find your profile directory. It should contain a subdirectory named chrome. Edit or create a text file there named userContent.css (ie., chrome/userContent.css relative to the profile directory). Insert the following:
@-moz-document domain(slashdot.org) {
.comment-bubble { opacity: 0.3 !important; }
}
changing the opacity value as required. Restart Firefox.
(This would be more useful as a Greasemonkey script, but I don't know how to write one of them. Volunteers?)
Lennart frequently blogs about how he could have been a contender and had his own linux if he'd just been born a little earlier - plus his plans of what he's doing behind the scenes to make linux HIS. It's all out in the open, lots of detail and if we don't like it we can just use somebody else's stuff.
I wish him good luck with his "world domination" but I also wish he was a bit more patient and would stop inflicting alpha level shit on us as part of the process. You'd think he would have learnt his lesson with PulseAudio and NetworkManager that crashing pre-alpha shit doesn't belong in a "stable" release and that people using the "stable" release shouldn't have to put up with three years of crashes until he finally gets his shit together.
To Lennart the linux environment has the fatal flaw that it's not under the tight control of anyone. To me that's an advantage. Previous attempts at a one size fits all environment (eg. on the desktop, CDE, supposed to be imposed on all but only really liked by people at Sun) have just demonstrated that people really do not want to be forced into a one size fits all environment.
Oo that's nice. I'll definitely be using this instead from now on!
https://www.flickr.com/photos/...
Here's a Tampermonkey script to fix it:
http://pastebin.com/wZKjNi1S
I used the original HTML and CSS from the Wayback Machine which means they might remove those classes at some point in the future.
Joking, newbie, selling yourself way short or completely and utterly fucking useless - what is it to be? The amusing bit is the condescending crap on the end about home backups when the situation is that if you are responsible for the gear then you are failing in your duty if you cannot do a bare metal restore of critical systems AND talk somebody with minimal experience through it. I've been there and had a complex pile of stuff only I knew how to restore properly, but I did my job and got it all down to a procedure just a few lines long with simple steps and it gets packed in with the tapes.
So you refine the plan so that a monkey can step through it and you document it well enough that you can read it to somebody two minutes after waking or someone with limited experience can read it themselves.
FFS - it's far easier now than it ever was before since we can boot stuff off USB drives and then remotely populate their disks with what was on their before instead of reinstalling before restore.
Since you laid on the condescending crap it's time for me to ask you a question. As a "systems integration engineer" shouldn't you be considering things from an engineering approach of improving the system that is broken instead of an ad-hoc basketweaving approach of the technician just doing what seems sort of OK a different way each time while waiting for someone to write procedures for them to follow? I don't consider myself an engineer anymore since I've been exclusively on the IT side since 2000 but I do still apply the approach that I used on engineering problems, something you self-declared engineers who do not have their title accepted by a professional body should consider if you want to be taken seriously.
Only your stupid strawman is ridiculous, I'm suggesting that if you WORK at a major bank and you are responsible for their backups then part of that is being able to do bare metal recovery AND walk others through the process.
Yes, your strawman is stupid, but I didn't suggest anything remotely like your imaginary friend that you are shouting at and I have to admit that I think it's a very childish way to act.
While perhaps I should have been clearer and stated that with AMANDA you don't have to rely on dd and tar, the system is built in such a way that you can get by with as little as that if you have to in an emergency instead of installing and configuring that AMANDA software on a new machine first. While I wasn't clear enough I very much object to your over-reaction to that misunderstanding.
With respect - professional engineer here, guy with a HR granted title of engineer there. You really should choose your insults a bit more carefully. I'm sure you have plenty of skills I do not have but to me IT in general is a subset of what I was doing last century, so you have only succeeded in making me laugh by puffing yourself up.
It's both potentially a complete showstopper and totally unnecessary in the first place. I don't really understand why you cannot grasp the concept.
I'll restate something above in another way - if you can't work out how to do a bare metal restore on a single system with all the needed data on media that you can read and the right hardware then somebody has seriously fucked up. That guy that worked there should have put something together in such a way as someone with a moderate skillset can work it out, or someone with detailed instructions can do it with very little in the way of skills. Requiring a key that can be lost is a major fuckup waiting to happen. You suggested you wouldn't be able to work it out in a couple of hours - I think you were selling yourself short to try to make a point just as your ridiculous strawman in my name "with no foreknowledge of their systems" WHEN THE ENTIRE POINT is to PROVIDE FOREKNOWLEDGE OF THEIR SYSTEMS by having disaster recovery documents designed to be read by the least skilled person capable of doing the job.
I see the problem now - you didn't even try to understand my example. The point of the example is that with AMANDA the instructions on what to do with the files (eg. how to fall back as far as "dd" and "tar" if that's all you've got and you are in a hurry) are in the header as ASCII text. That's why if you can't work out how to restore a single system from that in a couple of hours you are really selling yourself very short. That's how such things should be. Self-documenting as much as possible. No arbitrary bullshit since it doesn't go down very well when half your time is taken by fending off users who want to know when you'll have things back as they were.