The latest release of Black Lab Linux, an Ubuntu 16.04-based distribution, adds a Unity desktop option. You will not find Unity offered by any other major -- or nearly any minor -- Linux distributor outside of Ubuntu.
Black Lab Linux 8.0, the consumer version of PC/OpenSystems' flagship distro, also updates several other prominent desktop options.
Black Lab Linux is a general purpose community distribution for home users and small-to-mid-sized businesses. PC/OpenSystems also offers Black Lab Enterprise Linux, a commercial counterpart for businesses that want support services.
Black Lab Linux is an outgrowth of OS4 OpenLinux, a distro the same developers released in 2008. Both the community and the commercial releases could be a great alternative for personal and business users who want to avoid the UEFI (Unified Extensible Firmware Interface) horrors of installing Linux in a computer bought off the shelf with Microsoft Windows preinstalled.
Black Lab offers its flagship releases with a choice of self or full support, and both come at a price upon launch. However, you can wait 45 days and get the same release with the self-support option for free. Black Lab Linux 8.0 became available for free late last year.
The GeForce GTX 1080 Ti is NVIDIA's newest, most powerful graphics card for gamers not only on Windows but also under Linux. I only received the GeForce GTX 1080 Ti this morning so here are my initial Linux performance figures for this new high-end Pascal graphics card compared to other NVIDIA and AMD Radeon graphics cards. Linux VR tests, CUDA/OpenCL compute benchmarks, and additional GeForce GTX 1080 Ti results will be published in the days ahead when having more time to spend with this graphics card.
Mesa 17.1.0 release plan
Here is the current tentative 17.1.0 release schedule.
Apr 14 2017 - Feature freeze/Release candidate 1
Apr 21 2017 - Release candidate 2
Apr 28 2017 - Release candidate 3
May 05 2017 - Release candidate 4/final release
Mesa 17.1 Expected In Early May, Feature Freeze In One Month
Collabora's Emil Velikov is continuing as the Mesa release manager and has laid out plans for getting the Mesa 3D 17.1 release to happen in early May.
Mesa 17.1 release is now scheduled for May
The latest and greatest Mesa release 17.1 is due for release on May 5th, so not long for everything to get polished up.
I have Fedora on my laptop and am considering putting something on my gaming PC. I am sick of windows 10 and having no privacy. I am looking for a recommendation of which linux os to use, as well as if I use WINE to game if it's functional enough, and if it would cause any security issues, such as it having the same privacy issues as actually using Windows 10 and the tracking.submitted by /u/Greenman8291
I know: Ubuntu has its problems, too. Nothing's perfect. And for some people, WIndows is just a better fit than Linux.
Still, I admit that I've been happy, in a kind of way, by my frustrations working with Windows. Ever since I switched to Linux, I have always been afraid that Windows will get much better, without my knowledge. Using a recent version of Windows and finding it quite annoying is pleasant affirmation that Linux is still the better option for me.
The last release of the 16.12 branch brings a few, but important improvements, like fixing a couple of crashes and avoiding a possible corruption as well as a overnight render bug along with other minor stability improvements. All in all 16.12 was a great release and the best is still to come.
We continue our focused effort in the timeline refactoring which will bring professional grade tools, stay tuned for more info on that soon!
Italo Vignoli from The Document Foundation (TDF) is informing Softpedia today, March 9, 2017, about the general and immediate availability of the sixth maintenance update to the LibreOffice 5.2 open-source and cross-platform office suite.
Reddit: Petition on r/AMD to sticky a post relating to open-sourcing the AMD PSP code + working with Coreboot / Libreboot
There is currently a thread on r/AMD suggesting one of the mods there sticky a post about open sourcing the AMD PSP, and working with Coreboot / Libreboot. I would highly recommend leaving a comment there voicing your agreement to this idea.
We can't let up on this guys, keep the pressure on and AMD will be forced to do something. Especially with the recent Wikileaks release detailing CIA backdoors.
Courtesy of /u/G4nfAnspNDW8, here are some other ways you can contact AMD to voice your concern with PSP, and your wish of it being open-sourced (or at the very least giving us the ability to disable it entirely).
AMD’s contact page (You can find details on AMD in your country)
Best number for North America: (877) 284-1566
You can also reach them on Facebook.
For those of you who don't know what the AMD PSP Chip or Coreboot are, or why this is important, please read this post I made over at r/AMD.
Alternatively, give this video a watch.submitted by /u/RatherNott
So I have an ext4 formatted RAID1 array using 2x4TB drives. It looks like this:# mdadm --detail /dev/md0 /dev/md0: Version : 1.2 Creation Time : Fri Nov 4 22:48:12 2016 Raid Level : raid1 Array Size : 3906784064 (3725.80 GiB 4000.55 GB) Used Dev Size : 3906784064 (3725.80 GiB 4000.55 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Thu Mar 9 23:02:43 2017 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : myhost:0 (local to host myhost) UUID : c26bf590:ccf6c6ce:ba5445a7:ba0a9d73 Events : 6434 Number Major Minor RaidDevice State 0 8 33 0 active sync /dev/sdc1 1 8 17 1 active sync /dev/sdb1
I've connected 2 more 4TB disks (/dev/sda and /dev/sde) and I want to use them to build a 4 disk RAID10 array with 8TB usable capacity, without losing data.
First, I copied the partition layout of one of the existing disks (/dev/sdb) to the new disks:# sgdisk -R=/dev/sda /dev/sdb # sgdisk -R=/dev/sde /dev/sdb
Then used sgdisk again to randomize the GUIDs of the new disks:# sgdisk -G /dev/sda # sgdisk -G /dev/sde
Now, here's my plan for the next part and this is where I could really use some feedback.
First, I'll create a new array with 2 disks missing:# mdadm -v --create /dev/md1 --level=raid10 --raid-devices=4 /dev/sda1 missing /dev/sde1 missing
Then, I'll rsync the data from the old array to the new one:# rsync -avP /mnt/old-array /mnt/new-array
Once that's done (it'll probably take more than a day), I'll move the disks from the old array one by one, by failing and removing them:# mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1
Then adding it to the new array:# mdadm /dev/md1 --add /dev/sdb1
I'll repeat it for /dev/sdc1 as well. Finally, I'll stop the old array:# mdadm --stop /dev/md0
So, is this a good strategy? Am I missing anything? What could go wrong? Thanks for the feedback!submitted by /u/callcifer