Jump to content
funtoo forums

Leaderboard


Popular Content

Showing content with the highest reputation since 05/29/2014 in all areas

  1. 7 points
    drobbins

    1.4-release efforts starting

    Everyone, I have just started getting kit-fixups ready for 1.4-release development. Some key changes that are coming in 1.4-release: move away from eselect opengl and to libglvnd. official support of container-based solution for steam, etc. updates to pam and pambase 1.4-release will be tracking "current" gentoo for a while and will freeze sometime this summer, likely in June 2019. If you want to get involved, chat on #funtoo and look at the latest commits to kit-fixups on code.funtoo.org. I'll also be doing some introductory videos on how to get involved with the new release of Funtoo. -Daniel
  2. 6 points
    drobbins

    Funtoo release model

    We are not doing rolling release for the following reasons: Too much time is spent on fixing various breakages coming in from Gentoo, which takes time away from other things... other things are more important such as new technology like fchroot and the upcoming containerization solution... If users are interested in certain packages being updated, I am encouraging them to submit a pull request and maintain these ebuilds themselves, so I am going to focus on helping YOU maintain ebuilds rather than have a few people (this has generally been Oleg) maintaining them for everyone. This model doesn't scale -- we all need to do a little bit rather than a few people doing a lot. See the YouTube channel here: https://www.youtube.com/channel/UCKmOY6p3c9hxv3vJMAF8vVw for tutorials Short-term, this means development slows down. But in reality, it will speed up development greatly. For those hanging out on IRC, you know that Oleg who has helped to maintain Funtoo for years has moved on to a new chapter in his life, so he is no longer active on Funtoo. But even though I am not slaving away over here, thanks to incoming pull requests Funtoo is continuing to move forward and be responsive to user needs. So think of it as a course correction as we become more agile and community-oriented, and be part of the solution. If you are reading this, it means you are part of the Funtoo community and just as able to contribute to Funtoo as anyone else (maybe with some tutorials/videos to help). When I work on technologies, I am trying more to work on key tools that help the community be more productive (like fchroot) rather than focusing on specific ebuilds, which I am leaving to the community to manage using pull requests. Best, Daniel
  3. 6 points
    The 1.0 release of Funtoo Linux is not going to be maintained after September 30, 2018. So please be sure to upgrade your systems to Funtoo Linux 1.2 using https://www.funtoo.org/Upgrade_Instructions so that you will continue to get updates! We will also be starting development on Funtoo Linux 1.3 in a few days, on August 31. We are moving to a new agile (scrum) process, where we will be doing 1-week sprints (time-constrained sets of work). Our work will include some portion of fixes for 1.2 and some new work on 1.3. When we as a team decide that 1.3 is ready for various milestones (alpha, beta, release candidate) we will mark it as such. Thus, we have no hard deadline for 1.3 as I do not want to try to hit arbitrary dates that are not based on the actual work. But we will get there, sooner rather than later!
  4. 4 points
    Hi all, Please test ego-2.6.0, which is currently masked for testing. As many of you have noticed, there have been significant changes to kit generation and currently, ego is less "flexible" about mixing and matching kits from different releases. This is a side-effect of massively improved merge scripts, which now leverage python's asyncio, use a thread pool for database operations, and have much better internal design. I have put a lot of work into this new codebase and the new design is much better foundation for future development. Currently, it is possible to select a custom xorg-kit or gnome-kit, but all other branches are locked down to the release. For those who may be upset -- We have never "officially" supported anything but the standard collection of release kits anyway, with some tweaks of xorg-kit and gnome-kit, so users who push the limits of mixing and matching kits right now have been using Funtoo in a way that is beyond the scope of what we intended to deliver, likely without realizing it. So if you want to use an unusual combination of kits -- awesome -- we want to support this officially in time, but we are working on getting there the right way rather than committing to supporting all these unusual combinations all at once. If you have gotten accustomed to this flexibility in the past, know that this lack of flexibility is only temporary as we continue to build out our next generation of innovative technologies for managing kits. Re-enabling support for any old combination of kits is going backwards, in my opinion, and instead we need to move forward to OFFICIALLY support more combinations of kits. For the time being, you may need to write a small script to get things exactly how you want in meta-repo. We encourage people to use combinations we officially support if possible -- 1.2 with some variation of gnome-kit or xorg-kit. Things will be easier that way for the time being. Also, we now have the 1.3-release kit names and definitions finalized, so this will allow us to move forward with 1.3 release development. Best, Daniel
  5. 4 points
    drobbins

    Welcome to the new forums!

    I just fixed login-related issues. Funtoo users who had not used the forums before were unable to log in. I've also fixed the password reset link to go to our official password reset page, as well as the create account link. So logins should be working well. One note is that if you were are user of the old forums, and you changed your 'displayname' to show something other than your username, then your forums account username will be your displayname. You can alternatively try logging in with your email as your username instead. Everyone else should be good to go using their funtoo username (and password, of course) to log in here.
  6. 3 points
    lazlo.vii

    Is Funtoo dying?

    Funtoo isn't dying. Funtoo is changing just like it always has. You know far better than we do what you want from your Linux distro so ask yourself if you have liked all of the past changes to Funtoo. Then stick with it and have some faith in the wisdom of our BDFL. If you don't like what you see in a year or two you can go to another distro and have not lost anything. I originally switched to Funtoo because too many things in Gentoo and Debian stayed the same. Having bleeding edge packages wasn't why I used Gentoo. It was because it gave me a greater degree of control than any other OS. The reason I love Debian is because the stable release is always stable but unfortunately I have to give a lot of control to use it. Funtoo can give me the control that I want and at the same time give me the stability that I need so I am keeping an open mind. If you have the skills to contribute to the code base and improve things for all of us I encourage you to get involved. If you are like me and couldn't write a program if your life depended on it then I encourage you donate a bit of money to Funtoo every month.
  7. 3 points
    drobbins

    Wiki Improvements

    Hello Everyone -- I want to highlight some improvements that have been made to the wiki besides our new FAQ (https://www.funtoo.org/FAQ) We now have a new Subarches page that is a lot easier to navigate: https://www.funtoo.org/Subarches And the look of various things like notes, tips, warnings, etc. have been improved for a cleaner, more consistent look. This is a good sample page to browse the new look. Note that you may need to "hard reload" the page to get the new CSS: https://www.funtoo.org/Upgrade_Instructions Enjoy! -Daniel
  8. 3 points
    morgareth

    Screenshots

    My current desktop
  9. 3 points
    drobbins

    Ryzen stages available for download

    Ryzen stages are now available for download at the following links: https://build.funtoo.org/funtoo-current/x86-64bit/amd64-zen/ https://build.funtoo.org/funtoo-current/pure64/amd64-zen-pure64/ A new pure64 stage is building right now. Also, many thanks to CDN77 for sponsoring Funtoo -- our downloads now use a combined funtoo/CDN77 infrastructure for world-wide speed rather than a mirroring infrastructure. This applies to stage3 downloads as well as fastpull downloads.
  10. 3 points
    drobbins

    Funtoo improves Dropbox

    Hi All, I've just massively reworked the net-misc/dropbox ebuild to provide a much better experience in Funtoo and you should see this showing up in the next few hours. I couldn't get the Gentoo dropbox working reliably. Here is a list of all the changes: Updated to dropbox-39.4.49.ebuild No longer has an initscript It now sets up ~/.dropbox-dist for each user who sets up dropbox (rather than having a system dropbox install) You don't need to be in the "dropbox" group to use the dropbox nautilus (gnome file browser) extension gnome support is built-in (as long as "gnome" is set in USE, which it is if you are using the GNOME mix-in.) Reworked the python 'dropbox' script to provide a better user experience and be optimal for Funtoo: if you start "dropbox" for the first time from GNOME, it will start a GTK+ installer to set up dropbox for you. if you don't have a GUI, you can still install dropbox The above two features are existing features of dropbox that were somewhat borked in Gentoo. At the end of the setup process, you are given instructions on how to enable dropbox on startup. dropbox command-line tool is also included. Please note that if you have nautilus-dropbox installed, you will need to remove it. This should result in a really nice experience for dropbox users. Use as follows: # emerge dropbox (make sure it's 39.4.49 -- this is the new version.) (as regular user:) $ dropbox start -i This will initialize the ~/.dropbox-dist directory for the user via a command-line or GTK+ interface. Once this is done, dropbox start should be added to your .bash_login and/or .xprofile and can be run immediately to start dropbox in your current session. Since the ebuild is completely new, the possibility of bugs exist. Please report bugs at https://bugs.funtoo.org . Thanks. -Daniel
  11. 3 points
    I'd rather it be opt-in, myself. One of the main reasons for my using Linux over other OS's is that data is specifically NOT sent by default.
  12. 2 points
    You and I are on the cusp of a political discussion here 🙂 but I would argue that even "reputable" sites these days are spewing propaganda, so there is no substitute for critical thinking. We do not live in an ethical age. Whether intentional or the result of our modern echo chamber, there is misleading information EVERYWHERE online and I couldn't really tell you ANY trustworthy source of information that I would tell you that you could trust implicitly. Even Associated Press and Reuters seem horribly compromised and full of spin! Every journalist seems to want to write an atomic bomb of a news story and go though such extreme lengths to try to inject bias while remaining 'factual' -- it would be comical if it weren't so sad. Assuming a posture of skepticism and "it's probably not as bad as it sounds" is highly recommended when looking at sources of information online. Politics is the art of getting a ton of people pissed off and then leveraging that energy -- and doing this online is known to be extremely effective. So you just have to be wary. Don't be a pawn. Now, as for the other issues you raised, I guess I can read and think about those now that I've vented 🙂
  13. 2 points
    Hey Everyone, I recently upgraded to a newer Thinkpad Laptop (P1) and decided this was a good time to upgrade Funtoo's graphics stack to sort of finish the work that TemptorSent had started. You'll recall that if you tested 1.4, media-libs/mesa could be quite picky with USE vars/VIDEO_CARDS settings. This should now be fixed. One thing that bugged me when I installed Funtoo on my P1 was that video acceleration wasn't working well. So I've tried very hard to address this so that "out of the box" with minimal/no configuration, you will have good video acceleration support in Funtoo. New documentation on this system that is now in 1.4 can be found here: https://www.funtoo.org/Make.conf/VIDEO_CARDS In particular, see here: https://www.funtoo.org/Make.conf/VIDEO_CARDS/Mix-ins (This table is also included in the main page linked above.) You'll also see extensive documentation on the new VIDEO_CARDS settings that are available and all map directly to a particular graphics driver now (eliminating confusion between gallium and DRI drivers that existed.) The workstation and desktop flavors will now auto-enable Open Source Intel integrated graphics (DRI) and Radeon Gallium graphics (Gallium) -- enabling Vulkan for both. I did not enable nvidia or nouveau by default as I leave this choice of proprietary vs. open source to the user (for Intel and Radeon, the best choices are obvious so safe to enable these.) This should be a big step towards getting everyone optimal video performance in Funtoo without significant work! Be sure to give https://www.funtoo.org/Make.conf/VIDEO_CARDS/Mix-ins and the parent page a good read. And if you use firefox, play around with the h264ify plugin to optimize YouTube video playback and see if it helps reduce your CPU usage. Enjoy!
  14. 2 points
    cardinal

    xfce terminal input/output error

    Your processor doesn't support aes which is in your CPU_FLAGS_86 and CFLAGS="- march=westmere" Building nettle with aes cpu flag set on gcc when your processor doesn't support aes could be the cause of the error. Reference: https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html ‘westmere’ Intel Westmere CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, AES and PCLMUL instruction set support. Set to native and add the proper flags to match your processor. Install cpuid2cpuflags Follow my directions here starting at Remove any gcc override settings you've made previously. After you've finished configuring gcc to match your processor rebuild nettle.
  15. 2 points
    drobbins

    Funtoo release model

    And to expand on this some more -- While it's true that we don't have a dedicated security team and rely on users to report CVE's, this doesn't mean that we trail behind Gentoo in all areas. For example, we have a fix in gettext for CVE-2018-18751 that gentoo does not appear to have. We also had important fixes for avahi remote exploits before Gentoo. In general this means that our ability to be up-to-date with CVEs depends upon our users' ability to report these. In areas where we have had good reports, we have sometimes had things fixed sooner.
  16. 2 points
    greenzap

    Feeling good with Funtoo

    Got a (new to me) Thinkpad T420s and decided Funtoo would be the primary OS. I'm happy to say I went through the install today and I now have Funtoo installed and booted. Just need to setup everything I want on it now.
  17. 2 points
    Hi, everyone! mysql-community-8.0.12 added in 1.3-release. This is Oracle's MySQL-8 major release. Please, notice, that this package cannot be installed with mysql (replacing). It also has certain incompatibilities with older versions of mysql and databases, created. https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-12.html
  18. 2 points
  19. 2 points
    Looks great -- good work!
  20. 2 points
    drobbins

    why do we have such outdated packges?

    Good questions. The issues with blockers due to not having the correct version available will be disappearing with 1.3-release when it is available. It currently happens because we are using different snapshot dates for different parts of the tree, and we are not going to to do that anymore with 1.3+. 1.3-release will be a 'frozen' release when it is released, meaning it will gradually become out-of-date, though we will be bumping critical packages and backporting security fixes. But the process we use to create 1.3 will be used to launch 1.4 development immediately, so we are getting better at this and releases will come a lot more often ? The goal is to have a very stable and tested release that doesn't have unanticipated changes, until you want to pull them in by moving to the next release. So this is the pattern we are trying to establish. Hopefully we can get releases to the point where they are coming frequently enough people do not feel like packages are "stale". That is the goal. With the improvements in our tools, I think we will be able to achieve it. It is actually easier to do releases often rather than infrequently -- right now we are just in the "growing pains" stage where we are in the process of moving to a more rapid release schedule. As funtoo's team grows, we will have the person-power to actually move ahead of Gentoo in more areas. Right now, these areas are limited due to us only having a ~4 person team and Gentoo having several hundred developers.
  21. 2 points
    drobbins

    New Funtoo Wiki

    Just wanted to let everyone know if you don't visit www.funtoo.org often that we've updated our wiki with a new version of mediawiki (finally) and a new skin! Enjoy, everyone.
  22. 2 points
    drobbins

    Funtoo Stages and Release 1.2

    Hi All, By default, we are now building stage3's using Funtoo Linux 1.2 release as default. This means that new installs will have this in their /etc/ego.conf: [global] release = 1.2 If you are still using release 1.0, that's fine -- your system will continue to use 1.0. When you upgrade to ego 2.4.1 or later, you will be able to set the release as above in your ego.conf, re-run "ego sync", and you will be upgraded to the 1.2 release. The release= setting is simply a short-hand for setting the various 1.2-related kits individually in the [kits] section, so many of you are already running 1.2. Best, Daniel
  23. 2 points
    Oleg Vinichenko

    LLVM updates

    New kit, lllvm-kit now added. It consist of small numbers of ebuilds that are directly related to the sys-devel/llvm. The rationale behind this is that ebuilds for llvm had no update for very long time and are problematic to maintain due to those ebuilds were spread all over different kits. Now they are from one kit. This kit is enabled by default and involves following update steps: ego sync emerge -C llvm:0 clang:0 emerge -1 llvm mesa emerge -auDN @world emerge @preserved-rebuild
  24. 2 points
    dkg

    Getting eix to work with kits

    This was very helpful. Your output... open("/etc/portage/repos.conf/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 3 My output... open("/etc/portage/repos.conf/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 EACCES (Permission denied) It turns out that /etc/portage/repos.conf/ is owned by root:root. Presumably, eix is using the portage user, and in combination with my default umask=077, it did not have permission. It's not a problem for /var/git/meta-repo/ because it is owned by portage:portage. I had adjusted the permissions of /var/git/meta-repo/ and one point, but never touched /etc/portage/repos.conf/. Occasionally, umask=077 does lead to some oddities. I have it working now. Thank you.
  25. 2 points
    drobbins

    New ebuild: turbovnc

    Hi All, I have just committed net-misc/turbovnc to the Funtoo tree. Turbo VNC is a very good VNC (https://en.wikipedia.org/wiki/Virtual_Network_Computing) client and server. As a client, it will allow you to connect to remote systems and is very fast and feature-rich, with a ton of security options. As a server, it integrates with X and supports VirtualGL. VirtualGL is functionality that overcomes some inherent limitations of VNC, which traditionally does not support OpenGL or forces applications to use non-hardware rendering. With VirtualGL, you can remotely access a Funtoo system with hardware-accelerated OpenGL and benefit from its GPU (graphics will render on the remote system using hardware acceleration and then the rendered images will be transmitted to your client.) Learn more about VirtualGL here: https://en.wikipedia.org/wiki/VirtualGL As a client, I've found turbovnc to be significantly faster than tigervnc, and the client has a lot of very useful configuration options -- see screenshots below. Please give the ebuild a try and let me know how it works for you.
  26. 1 point
    bcowan

    nvidia modules not installing.

    For now you can use the 390.129 in my overlay: https://github.com/bradlyatc/funtoo-overlay/tree/master/x11-drivers
  27. 1 point
    jhan

    overlays again

    It works but you might have misunderstood me. The problem is that you don't have virtual/mysql and dev-db/mysql yet. Your tree should look like: /opt my-overlay dev-db mysql Manifest metadata.xml mysql-8.0.16.ebuild metadata layout.conf profiles repo_name virtual mysql Manifest metadata.xml mysql-... As @cardinal also said, you need the category level as well, otherwise it won't work. The structure in general is always: overlay_root category1 package1 package2 package3 category2 package1 package2 package3 . . .
  28. 1 point
    So, it turns out I had a few little things I needed to fix -- currently running through continuous integration to ensure everything is good. Will post here when I've confirmed this.
  29. 1 point
    drobbins

    1.4 now in BETA

    Been doing automated tests all day today, adding fixes as I find things, and also added a fix so kde-plasma-5 should merge fine now.
  30. 1 point
    savasten

    Is Funtoo dying?

    I believe that Funtoo has switched to a more stable release cycle (Not exactly, more like a break less stuff cycle). @drobbins has also released some great videos on his youtube channel for submitting put requests to have the community start helping with the updates.
  31. 1 point
    lazlo.vii

    USE flags? Why so necessary?

    When I did a fresh Funtoo 1.3 install on my desktop PC I just set my profile with epro and installed the KDE meta package and it worked (nearly) flawlessly. I did something like this: #epro flavor desktop # epro mix-ins kde-plasma-5-new # epro mix-ins no-systemd # epro mix-ins gfxcard-nvidia # emerge -vauND --with-bdeps=y @world # (say yes to any USE flag changes) # dispatch-conf # emerge -vauND --with-bdeps=y @world #emerge -va xorg-server nvidia-drivers nvidia-settings # emerge -va plasma-meta # (say yes to any USE flag changes) # dispatch-conf # emerge -va plasma-meta I have zero USE flags set in my make.conf and in package.use I only have what portage added.
  32. 1 point
    konspiracy

    Opinion* Best way to run Steam?

    Sweet, I still have had no issues running with flatpak. I use it for anything that's a dependency nightmare, thanks for the feedback though.
  33. 1 point
    I'm just glad that we have this awesome distro to avoid all that garbage. Thanks to everyone who contributes!
  34. 1 point
    Reference: Funtoo Linux Live CD
  35. 1 point
    drobbins

    Testing 1.3

    Glad to hear @mantas -- we hope to get 1.3 released officially in another week. Still a lot of issues to fix which you'll get automatically via updates.
  36. 1 point
    Hey, so I think no one is really telling you the obvious -- you found a small bug, and I'm going to fix it with a commit to the profiles so that pclmul is added to CPU_FLAGS_X86 for skylake and skylake-avx512. ?
  37. 1 point
    Thank you Cardinal. https://bugs.funtoo.org/browse/FL-5837
  38. 1 point
    There is nothing wrong with some branches having "detached head". You will see this when there has been a recent update to our 1.3 development branch. If you see this at the end: Sync successful and kits in alignment! :) Then it means things are OK.
  39. 1 point
    mauricev

    why do we need pam?

    The reason is explained here https://bugs.funtoo.org/browse/FL-5318?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel The profile overrules the make.conf
  40. 1 point
    yes, I know that one exactly. ... Once it will be fixed :)
  41. 1 point
    gissf1

    ego trouble

    @cardinal Thanks for that strace, that did help alot! I noticed one major difference while initializing. It seems that on my system its using: /usr/lib/python-exec/python3.4/../../../lib64/python3.4/encodings/ascii.py and on your system its using: /usr/lib/python-exec/python3.4/../../../lib64/python3.4/encodings/utf_8.py Using ascii instead of utf_8 in python is not completely unexpected on my system since I try to avoid building anything outside en_US locale with ISO-8859-1 encoding. Later, (on both yours and mine) it reads the file: /var/git/meta-repo/kits/core-kit/profiles/base/make.defaults In that file, it finds non-ascii (code points >0x7e) characters in the file contents as part of a utf-8 sequence in one of the first author's names in a comment, and mine dies immediately after, because the python ascii parser does not attempt to handle any extended characters and throws exceptions instead. So this brings up the next question of why my system is using ascii instead of utf_8. I do have utf-8 support enabled in some places, and I have the referenced "utf_8.py" file (the one yours loaded earlier) in my system, but it's not choosing to load it for some reason. I guess I'll dig in deeper and see where the rabbit hole leads. Thanks again cardinal!
  42. 1 point
    glsa-check doesn't provide an up-to-date information for Funtoo. Funtoo also backports lots of security fixes for the forked packages, so the information that you get with --list affected could be inaccurate or wrong. There is a open bug for glsa-check tool for funtoo in BFO https://bugs.funtoo.org/browse/FL-3832?jql=text ~ "glsa" so you can subscribe to the bug and get update once such a tool is ready for funtoo. Until then you will have to check gentoo's GLSA list and check the README.rst in the kit of the package for example here: https://github.com/funtoo/core-kit/blob/1.0-prime/README.rst Funtoo also tries to audit forked ebuilds every 30 days. You can see all stale packages on this webpage: http://ports.funtoo.org/stale/ If you want to help and use any of the packages that are listed as "stale" you can check if they are affected by any know vulnerabilities and report those on https://bugs.funtoo.org where they will be squashed as fast as possible. Thank you in advance.
  43. 1 point
    palica

    Please define user commands

    this has to be fixed in the translations, it has been corrected in English original. Since it is a wiki you can edit it yourself. Please do so if you have time to make the experience for all users better.
  44. 1 point
    drobbins

    Dropbox changes

    Yes, sorry for the inconvenience of this change -- dropbox is supposed to be set up under each user's home directory rather than installed centrally. While this fixes quite a few other complications it does make things more complicated for you. Fortunately there is a pretty good way to get dropbox working the way you want -- using /etc/local.d. See if this works for your needs. Try creating an /etc/local.d/dropbox.start script that will start dropbox as the user of your choice when the system boots: #!/bin/bash su username -c "/usr/bin/dropbox start" Then... # chmod +x /etc/local.d/dropbox.start This will run dropbox as user "username" when the system starts.
  45. 1 point
  46. 1 point
    i remember this problem and will fix now
  47. 1 point
    I already have a bug open and waiting for me to add the functionality to specify a kit from the command-line rather than having to edit the config file, so that will be appearing in ego shortly :)
  48. 1 point
    I'm a big fan of trying anything new, but the cardinal rule for me is this: Don't mess with the data. If you don't what to lose those irreplaceable pics of grandma, keep it on a separate drive. This is my mantra. I love playing with my system, updating, tweaking, and exploring. But this can be dangerous to your data. This is also the reason why I chosen to use zfs as my storage for all my data. I can get to it from just anywhere. If it's unix(-like), I can download the kernel modules and access it. I feel like zfs is the becoming the unix(-like) version of fat32. Let me explain. I just did some consulting on a smartos job, but I had to p2v an existing Windows 2k3 server, with a dying hard drive. Smartos is great an all, but it is really not setup to virtualise an existing machine. So I place the failing drive into my setup, created a zvol the same size as the failing drive, dd the old drive to the new zvol. Created a new KVM instance, and booted the thing up. After some general cleanup and a massive amount of defragging, I had a good image ready for production. Smartos side of things was fine, json took a little getting used to, helps finding a good validating editor, zfs send | zfs receive, brought up the zvol, and away I went with the client configuration, igmadm create and all. Now the setup is in production, and all seems to be well. But the real point of this endeavour is this, ZFS is getting to the point of being truly cross platform. The only thing that can't read ZFS is windows, and that access is a samba share away. As much as I like Smartos, I love Funtoo. If I was going to roll out a data centre with clean installs, then Smartos is a great base. But p2v a small business client, not so sure. That's why I'm thinking about a Smartos like Funtoo usb bootable read-only install, and keeping with the way Funtoo is, basically a recipe for using the existing tools to create it, because that is the right way to do it. Our BDFL gives us the tools to do anything we want with his creation, we as users of Funtoo, get to assemble it as we need to get the job done. This is my idea, bootable usb Funtoo minimal, bare essential tools, read only root, builtin zfs kernel and xen hypervisor. Now just to figure out how to do it........
  49. 1 point
    sounds like a nice dream. i see an ecological advantage of making the internet much more eficient by avoiding unnecessary data transfers.
  50. 1 point
    Andrew Hobden

    First Toast!

    Look mom, it works!
×
×
  • Create New...