Jump to content
funtoo forums

funfool

Members
  • Content Count

    14
  • Joined

  • Last visited

  • Days Won

    1

funfool last won the day on July 4 2015

funfool had the most liked content!

1 Follower

About funfool

  • Rank
    Member

Personal

  • Location
    Albuquerque New Mexico USA
  1. Thanks oleg, masking 10.2 fixed it for me. And gentoo install has same issue and will mask there also.
  2. I used gentoo for a few years before switching to funtoo. I found that a great advantage to knowing why I love funtoo. Switched to funtoo in 2011, and never looked back.
  3. and that looks good, but are you booting into your system as uudruid74 sugested? Or are you chroot into it and trying to startx? Is no reason to startx in a chroot, just fix it to boot, and then go from there.
  4. gcc is a good example, I sent a link to you on forked packages in funtoo in your other thread. http://www.funtoo.org/Compare_Forked_Packages_To_Gentoo When updating ebuilds, we do want to look at Gentoo's most recent changes. Some of our ebuilds are mild variations of Gentoo's ebuilds, while others are complete rewrites. In general, we like to make our work as easy as possible, so we don't want to duplicate work, although sometimes there are exceptions where we will rewrite complex core ebuilds to make them more maintainable and easy to understand (our sys-devel/gcc ebuilds are an example of this.) What this means, funtoo ripped the guts out of gcc and re-wrote it to make sense. So the version number of gcc comparing funtoo to gentoo really does not count. There are several times that funtoo does go ahead of gentoo and grab something from upstream, have it before gentoo.
  5. Indeed it is forked, you can see the list here http://www.funtoo.org/Compare_Forked_Packages_To_Gentoo I would suggest creating a bug on it here https://bugs.funtoo.org/secure/Dashboard.jspa Just request the package update, or to include the new feature you want/need. Packages are forked for many reasons, usually to keep them from breaking other packages. If your package can be updated, I am sure it will be.
  6. the log is Xorg.0.log with a capital X not a small x and of course the .0 is a zero and not the letter o
  7. If you follow the install guide, you will get a binary kernel that should work for you as is, out of the box. Now that kernel gives you a working booting system, you can in your free time, build a custom kernel. You can have as many kernels, as you have room for on your hard drive. So keep your working kernel, and if your new kernel does not turn out so well, you can boot the old working kernel and try again. Just not the end of the world, if you do not get it right the first time.
  8. Am I the only one that still puts this in make.conf? :P INPUT_DEVICES="evdev keyboard mouse"
  9. I wish I knew what was going on with qt5 at the moment. As far as I know qt5 should be enabled on a per package basis at this time. But if it works, then leave it. I have USE="qt4" and per package as needed I add qt5. Here is the line you are looking for that is important. The following REQUIRED_USE flag constraints are unsatisfied: exactly-one-of ( qt4 qt5 ) And this is simply informational and telling you what you need, is normal. Sorry it does not always just give you one option. Sometimes the first option such as qt4 above is the best choice and the one I try. Sometimes is the second option that ends up working. I often install kde before xorg-x11, only because it happens to be late and going to bed, so let the big package run over night while sleeping. So the order does not really matter.
  10. I never have tried systemd. The problem with systemd is it tries to be to big and do to much all at once. I was totally perplexed as the distros started jumping on board with this. It is another of Lennart Poterings pet projects, he has started several and somehow he seems to lose interest and never completes his work. Pulseaudio is one of these projects and has open bugs for a very long time, I wonder if he is even still involved with it? Dont get me wrong, I think pulseaudio is a very complicated wrapper for alsa, and it serves a area that alsa just cant do by itself. There are music lovers everywhere that worship pulseaudio. But why did all the distros jump on board, and start adding pulsaudio like it was the next greatest invention since sliced bread. I have had my own frustrating experiences with pa, spent hours trying to solve them, with help from friends on irc. Never could solve the annoying issue. And I never needed pa, simple alsa sounded just as good and did everything I needed. How many hours I wasted over the years helping some collage student on irc try to fix pa issues, when all they need is alsa for their school laptop. But all the distros like to advertise the latest greatest and force a huge complex audio system on you, when maybe only 15% of users actually need the features pa offers. Same thing happened with systemd, Pottering works for redhat, so they said they would adopt it in x amount years, and of course fedora where is being tested. Sabayon who wants to claim to be bleeding edge could not wait to use it as a advertising tool, so did arch .... but wait guys! this is barely from alpha to beta, and they all start jumping on it. Arch lost a lot of users over it, was a sad day when debian said it would use it, They lost a lot of their main devs over it. Look at the devuan project, they forked debian and stayed systemd free. All of this excitement happened in such a short time, with a project that has not been tested. It continues to try and grow larger and more complex, it wants to take over your whole system including the kernel. It is not the linux way. The dev are so arrogant, they claimed it was a kernel bug, when their code in userspace did not work, and it had no business being there in the first place. Those were some fun mails to read :) I do not think it is settled yet, as people learn what they jumped into, and will be searching for another way out. I do not think openrc will ever be truly accepted by the masses, it is uniquely gentoo. It is the tool that allows users to easily open the hood on the race car and tune things up. imho, people like debian or redhat, really do not want their users under the hood mucking things up, making things unstable. And it is one of the biggest features of *ntoo systems to me. If I did not have openrc, I may as well just install ubuntu.
  11. Not sure what all is old in funtoo means. I know some of the core system packages are older by design, and that is what will help make your funtoo stable. While the rest of the packages are pulled from the ~gentoo arch, so should be the same. While some packages are forked to keep a better working older version or some are simply masked as being broken. And of course you have overlays available and other avenues to get newer packages. One way is to put in a package request on https://bugs. funtoo.org/ if it is possible to do so without breaking things for others, is a very good chance will be done. I do not know your experience with gentoo / funtoo, I honestly think a good comparison is to use both. At one time I had several machines all on gentoo, and I loved it. I had several friends that had switched to funtoo, I really had no plans to change. One day I finally did give funtoo a try, and within 6 months I switched everything from gentoo to funtoo. I am very happy I did finally make the change. But using gentoo for some time, I noticed the differences between the two, and how much time funtoo had saved me from fixing broken packages. I liked that it had some older packages. To be fair though, you should do a clean install with any distro to try it out and compare it with others. I am a big fan of, use the distro that works best for you. I still use windows on my htpc because of netflix. This is no longer needed, but at the time, it was the best os for the job. Just want to be clear, if you think gentoo works best for you, then by all means use gentoo. But if you just have some problems with a few out dated packages, there are ways to fix that.
  12. CHOST="x86_64-pc-linux-gnu" CFLAGS="-mtune=generic -O2 -pipe" CXXFLAGS="-mtune=generic -O2 -pipe" ACCEPT_LICENSE="*" MAKEOPTS="-j4" PORTAGE_NICENESS=16 INPUT_DEVICES="evdev keyboard mouse" VIDEO_CARDS=" vesa mesa nvidia" ABI_X86="32 64" USE="spell gtk3 gtk cpu_flags_x86_mmxext" EMERGE_DEFAULT_OPTS="${EMERGE_DEFAUT_OPTS} --quiet-build=y"
  13. I was just remembering the old days when portato was still active and supported. I said portato was great. And it did work well for me, I was just learning portage in those days. But since portato died, I have tried kuroo and porthole and they just did not work well for me. It only seemed they had partial functionality, and might as well do the job without them.
  14. GENTOO_MIRRORS="http://mirrors.rit.edu/gentoo/http://mirror.lug.udel.edu/pub/gentoo/ http://gentoo.mirrors.pair.com/" With gentoo you would want to select a fast mirror. With funtoo that does not apply. And your emerge --sync looks perfect, so yeah I assume the mirror you have listed above is just being ignored by your system. Just made me curious is all, that is a gentoo option that is not available on funtoo since it uses git. And it was after I posted here, that I ran into your post in portage. By all means, if it works for you, stick with it.
  15. sorry, I read this wrong, thinking you wanted to move from gentoo to funtoo either way, why not a clean install? will still have to recompile everything.
×
×
  • Create New...