This is good news. OT1H, really demonstrates the power of entrenched corporatism ('you know who' ;) to dominate and manipulate markets as they see fit for so many long years. Yet the story also gives optimism that, given time, basic common sense, fairness and consistent pressure, sinister corporatism can be battled and defeated.
sidro@sidro-home ~ $ sudo emerge -uaDN @world Password: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-kernel/linux-firmware-20140603  [ebuild R ] dev-qt/qtcore-4.8.5-r2 USE="-qt3support*" [ebuild U ] net-misc/curl-7.37.1 ...
I'm trying to build up a Funtoo Linux Security Bulletin Mailing List, if any of you would like to help, it would be nice if you give me a note. Cause I think most of us find it useful if they would be getting a note about Security Problems with packages they have installed. So if you have ideas about it pro or contra please let me know. Thinking first about a Weekly thing, if there are volunteers to help perhaps a daily base would be possible, with the ability to add discussion to it.
This is the approved revision of this page, as well as being the most recent. Jump to: navigation, search. Welcome to Funtoo Linux! We are in the process of restoring our infrastructure from backup. All wiki content is currently restored and available. For now, wiki user logins are disabled.
rc boot logging started at Wed Sep 24 09:32:44 2014
* Setting system clock using the hardware clock [UTC] ... hwclock: Cannot access the Hardware Clock via any known method. hwclock: Use the --debug option to see the details of our search for an access method. * Failed to set the system clock [ !! ]
ok. ntp-client got error because my conn is pppoe and start with networkmanger as default in openRC. But hwclock is my problem not ntp. I delete/disable my hwclock script from boot. That don't solve my problem but I don't get the errors at boot. :) Maybe is shomething from my bios. I will check.
I did setup Arch Linux on my laptop, after an update it stopped to work, looked up all the HOWTOs but nothing helped, I went to the the systemd IRC channel and asked for help, they just said read the Arch Linux HOWTOs.
Next I installed Sabayon Linux on the laptop, booted and worked fine, after an update, the same thing.
So I have managed to get two systemd installation to break with update without being able to fix it, during my 17 years with Linux, I never had such problems with openrc or other similar init systems.
Sure you wonder what strange systemd issue I got, the kernel (both cases the official) can't find systemd, even if the file is exactly where it's specified in the grub config.