Tassie_Tux

I built you a funtoo-stable atom_64 stage3 using Metro: dropbox link. You are welcome to use, but no worries if you do not. I have not tested it of course.

There are plenty of distros that support systemd.  I believe that it's important that someone is doing the work to make a Linux distro that works without systemd.   The developers are tackling a complicated problem with upstream projects that are not always supportive (one might even say they're hostile) to their goal.   Unless the goal is to attract more users for the sake of having more users it makes no sense to compromise that effort by splitting the userbase and the development effort between installs with and without systemd.

I think nrc's original post in reply to OP should be the last word...

Yeah, it's a bit cryptic.  It wants it like this
eselect java-nsplugin set 64bit blah Blah being the name or number of what you want to use.
 

Hi, there's also this:
 
http://www.funtoo.org/System_Administration_Practice
 
Which has a section on just this topic (distfiles).

See eclean-dist --help , it has many useful options.

You nailed it:
 
... yes, and if we are critical or disagree we are apparently 'haters'. :wacko:
 
I did not 'hate' Lennart before, however reading his G+ whine encourages me to start!  :P
 
I am reminded of a child throwing a tantrum because they did not get their own way. Having no intentions to ever talk about this again on a public forum is very arrogant. No right of reply, no debate. I actually find this part the worst. 
 
Obviously I cannot speak of the challenges that our Funtoo Developers have previously faced or currently face. What I can say is that as a Funtoo User, the community that Lennart is describing is not the Funtoo Linux that I have come to know. This is not a 'fortunate' thing. This is instead a reflection of the good people that are together making Funtoo Linux great.  :D

You nailed it:
 
... yes, and if we are critical or disagree we are apparently 'haters'. :wacko:
 
I did not 'hate' Lennart before, however reading his G+ whine encourages me to start!  :P
 
I am reminded of a child throwing a tantrum because they did not get their own way. Having no intentions to ever talk about this again on a public forum is very arrogant. No right of reply, no debate. I actually find this part the worst. 
 
Obviously I cannot speak of the challenges that our Funtoo Developers have previously faced or currently face. What I can say is that as a Funtoo User, the community that Lennart is describing is not the Funtoo Linux that I have come to know. This is not a 'fortunate' thing. This is instead a reflection of the good people that are together making Funtoo Linux great.  :D

Lennart Poettering has posted a whine to G+ about how mean everyone's being to him.
 
https://plus.google.com/app/basic/stream/z13rdjryqyn1xlt3522sxpugoz3gujbhh04
 
He blames this on the open source community and calls out Linus Torvalds specifically for setting a bad example. 
 
Of course Poettering fails to attribute any blame to his own history of being rude, obnoxious, and dismissive of anyone that disagrees with him.
 
I don't condone threats of harm or violence but welcome to the Internet, Lennart.  Yes, there are stupid and immature people in nearly every community, the Open Source community included.   But it's pathetic to suggest that these behaviors are somehow specific to the Open Source community or that Linus Torvalds bears some responsibility. 
 
Yes, Torvalds can be blunt but in all the cases where I've seen him lambaste someone, it's been a judgement on the quality of their work.  Don't develop software for public consumption if you don't want criticism of your work.
 
I think that's really the root of this rant.  Poettering believes that his work should be above criticism.  He feels like the adoption of systemd is proof of that when it's largely the result of funding and political machinations.
 
Thank drobbins we have an alternative.  Hopefully the rest of the Linux world will wake up eventually.

ill second the joe dirt mullet....  that's pretty fun
http://www.classicforwards.com/wp-content/uploads/2012/12/awkward_mullet3.jpg

Solved. (Yes... it was my fault)
 
Whenever I had to manually export and import my pool I did so with the command
zpool import $POOLNAME It turns out that this simply uses actual device names (/dev/sdX) as indicated by my earlier zpool status outputs. The device names are apparently retained within the zpool.cache file and so will be used for the zfs reimport/mount. If udev assigns those specific device names to other devices then the import will of course fail. The advice from the zfsonlinux crowd was to export my pool and then reimport it with the command
zpool import -d /dev/disk/by-id $POOLNAME so that the zpool.cache is set to use the /dev/disk/by-id links instead of the direct device names. I have rebooted with a USB drive plugged in to force udev into assign different device names and sure enough the pool continues to import correctly. The command zpool status now gives
  pool: wd20ears_zfs  state: ONLINE   scan: scrub repaired 0 in 11h33m with 0 errors on Fri Aug 15 11:45:16 2014 config:         NAME                                          STATE     READ WRITE CKSUM         wd20ears_zfs                                  ONLINE       0     0     0           raidz1-0                                    ONLINE       0     0     0             ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1268718  ONLINE       0     0     0             ata-WDC_WD20EARS-60MVWB0_WD-WCAZA4138722  ONLINE       0     0     0             ata-WDC_WD20EARS-60MVWB0_WD-WCAZA4157214  ONLINE       0     0     0             ata-WDC_WD20EARS-60MVWB0_WD-WCAZA4174978  ONLINE       0     0     0 errors: No known data errors This is probably not applicable to those users with root (/) on ZFS as I expect that there is no zpool.cache involved.

I wish I had the graphic talent to provide you with something worthy.  I did a search for appropriate symbols for systemd but this is all I could find...
 

 
Credit: http://www.codekid.net/index.php?itemid=2026

Read my edit, the bellow paragraph was out of ignorance, of the recent events.
I use systemd and I don't think this will affect eudev nor anything using dbus, anyway let's not turn this about it(systemd), I've been reading some about kdbus and from what I've read there will be a userspace daemon that will be a drop-in replacement for dbus but using kdbus in the background, anyway eudev pretty much is just getting udev outside of the systemd source code tree(search the git logs and see for yourself), for building it alone, and kdbus is an IPC system inside the kernel it isn't part of systemd, so you I think you are worrying about nothing in this particular case.

If you are not one of those people allergic to Lennart, here's a good video with *Technical* information about kdbus[1]
 
 
 
[1] https://www.youtube.com/watch?  v=NgR6d54blrU (join the space, the forum grabbed the video embedded with the complete URL)
 
Edit: I hadn't read your link, my bad, Well then there's things to worry about, for eudev, but I bet the the path will be to implement another kdbus userspace, but in my opinion while, this deafinitelly means a lot of work, it may not be a bad thing.

Have you tried booting with System Rescue CD, 'chrooting' into your install and exporting the zpool from within the chroot?

Hi Everyone,
 
As I hope you've probably noticed, I've put a herculean amount of effort into Funtoo Linux over the past couple of months. I' have:
 
Rebuilding our infrastructure from scratch, on new equipment re-launched Funtoo Hosting launched new forums, wrote Funtoo's own LDAP server for authentication upgraded our wiki launched our new ebuild pages Started massively cleaning up our online documentation Fixed GNOME building Launched the kernel-seeds.org wiki Went on a massive bug fixing rampage. And Oleg has also been busy, fixing things when needed (which is often) and migrating Funtoo to eudev.
 
The project is going in a really good direction, and we are now ready to accelerate development and keep moving forward, close more bugs and make Funtoo more and more robust. We need to grow the team and have more people helping out on the wiki, helping maintain ebuilds, and helping with various other things. To learn how you can help, see: 
 
http://www.funtoo.org/How_to_Dev#How_to_Develop_--_The_Quick_Summary
 
That page explains how to get more involved. We're at the point where we're going to be more reliant on your involvement as we grow... our team needs to get a bit bigger yet.
 
See how you can get involved and we will talk to you soon :)

I just completed a marathon session of wiki updates, which included:
 
Updating our incredibly outdated FAQ.... http://www.funtoo.org/Funtoo_Linux_FAQ
Updating our Funtoo Profiles page: http://www.funtoo.org/Funtoo_1.0_Profile
 
And then updating our main wiki page to try to do a better job for people -- linking to the Funtoo Linux Vision, as well as FAQ, and go into detail in the Distinctives section, so people know how Funtoo differs from other Linux distributions in general as well as Gentoo specifically.
 
Overall, I think the main page is shaping up... the goal is to get people up-to-speed quickly and over to useful information on other pages.