Jump to content

kindofblue

Members
  • Content Count

    32
  • Joined

  • Last visited

Everything posted by kindofblue

  1. The lvm flag didn't work for me. I still see the same messages at boot time as those I posted in my original message. At least I have a working kernel with the manual build of the kernel I described. Thanks again.
  2. Sorry I just saw your answer. I rebuilt the kernel with Device Mapper Support built in (instead of a module) and it's now working. I was not aware of the lvm use flag. I added it and I'm now emerging debian-sources-lts again. I'll let you know how it goes. Thanks a lot.
  3. Correction: the kernel parameter real_root in /etc/boot.conf is /dev/mapper/funtoo-ROOT.
  4. Hello everybody, I just installed Funtoo release 1.4 on an AMD K10 cpu; the kernel is debian-sources-lts version 4.19.67_p2-r1. I used LVM for all the file systems, including the root file system (I used the instructions in the following guide). I used the following kernel parameters in /etc/boot.conf (again from the guide mentioned above): dolvm real_root=/dev/funtoo/ROOT rootfstype=ext4 resume=swap:/dev/mapper/funtoo-SWAP. When booting I see the following messages: I have another box running Funtoo release 1.3 with version 4.19.37_p6 of the Debian kernel. I have the same se
  5. Thanks to all for the replies. I'll upgrade to Funtoo 1.4 as soon as I can.
  6. I tried to build kde-plasma/plasma-meta on two different PCs but they both fail on the same package, sys-apps/accountsservice. The error message is that systemd is required. I added the nosystemd mix-in to my profile but that didn't help. I tried to blacklist the package in package.mask but emerge returns an error saying that it must be unmasked. Would someone know if there's a way to build this package without systemd? Thanks in advance.
  7. Thanks, but that shows the version of the kernel, which I think is not related to the Funtoo release version.
  8. Ok thanks. I see mostly 1.2-release when I run this command so I guess it means I'm running version 1.2. Would that explain why I don't get new updates?
  9. Here it is: denis@euclide(~)$ cat /etc/ego.conf # This is the ego.conf file [kits] # You can set your default kits here. Unset kits will use the Funtoo default prime/master # branch by default. # python-kit = 3.6-prime
  10. I haven't updated my Funtoo systems in a while and now when I run ego sync there's no new packages. I see that there are new releases of Funtoo (1.2, 1.3). Can someone please tell me how to see which release I'm running. Thanks.
  11. I am really sorry, I wasted your time all along. I sudoed to root on the MacBook and looked at the command history. I was root when I changed the profile. I wonder how I can work in that business and be sometimes so confused.
  12. If you read the documentation on profiles, for example here, it doesn't say root privilege is required. I'm only trying to change my own profile, not system wide. I use sudo to emerge. For the rest I set up the two PCs exactly the same way, except for the stage download. Thanks again.
  13. Thanks a lot for your help. Again, they're exactly the same denis@euclide(~)$ sudo cat /etc/sudoers ## sudoers file. ## ## This file MUST be edited with the 'visudo' command as root. ## Failure to use 'visudo' may result in syntax or file permission errors ## that prevent sudo from running. ## ## See the sudoers man page for the details on how to write a sudoers file. ## ## ## Host alias specification ## ## Groups of machines. These may include host names (optionally with wildcards), ## IP addresses, network numbers or netgroups. # Host_Alias WEBSERVERS = www1, www2, www3 ## ## User alia
  14. They're exactly the same: denis@euclide(~)$ groups denis wheel audio cdrom video users denis denis@maxwell(~)$ groups denis wheel audio cdrom video users denis
  15. But the permissions on the system where command epro flavor desktop works are exactly the same as the other system where it doesn't work: denis@euclide(opengl)$ ls -l /etc/portage/make.profile/parent -rw-r--r-- 1 root root 1411 Nov 4 06:56 /etc/portage/make.profile/parent denis@maxwell(~)$ ls -ld /etc/portage/make.profile/parent -rw-r--r-- 1 root root 1365 Nov 4 07:42 /etc/portage/make.profile/parent euclide is the PC where the command works, maxwell the one where it doesn't. Besides, I remember installing Funtoo a year ago or so and epro was also working with my own account.
  16. I don't think I have to be root or use sudo. I didn't have to one my other PC (the MacBook). Thanks anyway for your reply.
  17. I just reinstalled Fundoo on two of my PCs, one being an old MacBook. The MacBook installation worked great, but I hit a problem on the other PC, an AMD 64 based system. I cannot set my profile with epro. Here's what I get: Would someone have a suggestion? Thanks in advance.
  18. Hello everybody, I followed this Funtoo document, http://www.funtoo.org/KDE_Plasma_5, that describes how to install KDE Plasma. I managed to get the login screen, but after logging in the screen stays black. I only see a big arrow cursor for the mouse. I couldn't install kde-apps-meta because there was a slot conflict. I only installed two of the meta packages: kdebase-runtime-meta kdecore-meta Is there other meta packages I should install to get a working desktop? Thanks in advance.
  19. I finally reinstalled from scratch. Hopefully I'll be good for a couple of years without running in the same kind of problems. Thanks again for your help.
  20. I'm sorry I don't really understand your answer. Is there a way to reinitialize Portage to a sane state?
  21. I use KDE but i may have pulled in packages from other desktops inadvertantly. Here's the output of the commands you asked:
  22. Thanks a lot for the help. I use Linux at work and I use Gentoo/Funtoo at home, but unfortunately I don't know the intricacies of Portage well enough. The first emerge command fails with multiple conflicts:
  23. I tried to use the uploader to upload build.log but if fails with the error "You aren't permitted to upload this kind of file". I pasted the content of the file at the end. But first here's the output of emerge --info '=www-client/firefox-47.0.1::gentoo': And here's the content of build.log:
  24. Hi all, I've not been able to build Firefox since version 42; the current version in Portage is 47. It fails with the same error every time: failed to load site script /usr/local/share/config.site. This file exists and is readable. Has anybody encountered this problem? Thanks in advance.
×
×
  • Create New...