Softpedia was informed today, February 24, 2017, by Entroware, a UK-based hardware manufacturer known for building and selling desktops, laptops, and servers with the popular Ubuntu Linux operating system pre-installed, about a brand-new product.
This article explains what network bonding is in Linux.
Linux never sleeps. Linus Torvalds is already hard at work pulling together changes for the next version of the kernel (4.11). But with Linux 4.10 now out, three groups of changes are worth paying close attention to because they improve performance and enable feature sets that weren’t possible before on Linux.
Here’s a rundown of those changes to 4.10 and what they likely will mean for you, your cloud providers, and your Linux applications.
VIA unveiled an SODIMM-style COM based on its Cortex-A9 WM8850 SoC, with 512MB RAM and 8GB eMMC, plus Ethernet, CSI, graphics, USB, and serial ports.
The 68.6 x 43mm “SOM-6X50” computer-on-module appears to be VIA’s second-ever ARM COM. Back in Sept. 2015, the company released a 70 x 70mm Qseven form factor QSM-8Q60 COM, based on a 1GHz NXP DualLite SoC.
At ELC Europe, Intel MinnowBoard SBC evangelist John Hawley surveyed open hardware trends, and their impact on OS-enabled device and system development.
We had an incident on our storage array recently, that caused random (but not fatal) corruption in a number of LUNs used by our Oracle databases. Some database files were in a state where the database could access them, but any filesystem or app operations that attempted to read a certain block on the file, would result in I/O errors. Our current action plan has been to take each DB down, and run a badblocks scan on the affected filesystems. In our first case, we ran fsck with badblocks enabled, performing a full read-write test (fsck -cc -v /path/to/screwed/volume).
The scan found and repaired a number of blocks, which made the affected files readable again at the filesystem level- but the test took 18 hours to complete, which freaked out management. Some of our other affected database LUNs are much larger, and they don't like the idea of multi-day business impact while we perform filesystem scans.
When discussing the incident with our storage vendor, their SME mentioned that we shouldn't have to perform a full read-write test on the LUN's (logical) blocks, and that a read-only test would be good enough. To paraphrase, he said: "If you can't write to the (logical) block on your filesystem, you wouldn't be able to read from it either... so there is no point spending the time to test for writes against our LUN."
This just doesn't sound right to me. It seemed like he was suggesting that a write test on the logical blocks would be redundant, if the underlying physical blocks are writable according to the storage array. I was interested if anyone else had experiences / opinions on this? Some of our database LUNs are very large, and I don't want to run a check that requires multiple days of downtime if it isn't necessary. In those cases, I would likely do something different, like creating another LUN + filesystem, and using dd to export the files into a new, clean filesystem.submitted by /u/feistypenguin
When organizational rules exist, people will try to game them.
Quickserve is a simple http server that allows you to share files quickly between Arch Linux systems and/or other operating systems.
So here is a weird thing. I'm running Fedora 24 with kernel 4.79.200fc24x86_64. This morning I launched terminal to see steve@renees-iphone instead of steve@home the same thing has changed when I log in as root.
My problem is I have no idea what renees-iphone is, how it got there and what would have installed it. Other than deleting some cache a few days ago I have not logged in as root, and I have not made any changes to the system or installed any software in weeks. Other than switching to Xfinity wifi yesterday, nothing has changed with my computer, and even then I simply connected to a different network.
Any help would be greatly appreciatedsubmitted by /u/vertdeferk