I have been going through articles since last night regarding initrd and all of them invariable mention some version of this taken from:
In a nutshell, when your bootloader (GRUB?) loads your Linux kernel, it is of course the kernel's job to finish the boot process. But to do so, it might require particular drivers to be able to work with, say, hardware RAID controllers, or a network, and so on. And depending on where those critically important drivers are, the kernel might not have the ability to load them; hence, the creation of a preliminary root file system that would contain just enough in the way of loadable modules to give the kernel access to the rest of the hardware.
But my question is: well boot loader is passing the kernel initrd, why won't it pass it the whole file system instead? Why this dual process?Intern_MSFT
[link] [1 comment]
Facebook is hiring another Linux kernel engineer to join its growing kernel team. The goal for the new employee will be to make "the Linux kernel network stack to rival or exceed that of FreeBSD" and carry out other improvements to the Linux network stack.
A new preview version of Manjaro 0.8.11, a Linux distribution based on well-tested snapshots of the Arch Linux repositories and 100% compatible with Arch, has been released for the Xfce, Openbox, KDE, and NET flavors.
PCLinuxOS comes with many flavors, but the default is actually KDE. The developers also make a few other versions, like KDE MiniMe, LXDE, or FullMonty, but this is the main one downloaded by most users.
The distribution actually follows a rolling release model, which means that new major features and other changes are introduced regularly through the update channel. Every month, the download ISOs are regenerated with the new update, but if you already have the operating system installed you only have to update it regularly.
KDE has today made the first update to KDE Frameworks 5. Frameworks are our addon libraries for Qt applications which provide numberous useful features using peer reviewed APIs and regular monthly updates. This release has 60 different frameworks adding features from Zip file support to Audio file previews, for a full list see KDE's Qt library archive website Inqlude. In this release KAuth gets a backend so you can again add features which require root access, KWallet gets a migration system from its KDELibs 4 version and support has been added for AppStream files.
We have ~35 linux servers, all sending out emails directly using sendmail.
I would like to create 2 new servers, and use them as a smarthost / relay host so all email will be send from the same two ip's instead of 35 different ip's.
Also i would like redundancy on this.. if one of the new mail servers goes offline, the other will just take over.
My questions are:
- Is it possible in sendmail to specify two smarthosts/relay hosts.
- If i specify two smarthosts/relay hosts, will it load balance? round robin?
- If one of the mail servers go offline, will sendmail be smart enough to try the other one before just dropping the email?
[link] [1 comment]
When we were building towards 5.0, we made the choice to focus all the effort on the core, and not release plasma-addons. It would have been simply too much work and quality of the core would have suffered.
The intention was to start bringing them back from 5.1, which will be in approximately 2 months from now.
The amount of stuff in plasma addons is huge.