Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won

  1. SFTP, you do know ssh right? man 1 sftp, and a web search should give you the info you need to use it, many graphical file explorers will even accept: Ctrl+L -> sftp://[user@]host:[$PATH] And have to the option to add it as a 'bookmark', and give you and interface that works just like a normal directory on a graphical file explorer, if you setup public key authentication for sshd on the server, it works with just a click after you have 'bookmarked' it.
  2. It doesn't mount automatically because you configured it to not mount automatically: UUID="2B00-F65A" /boot vfat noauto,defaults 1 2 the option 'noauto', means to not mount automatically that partition, but since you have it /etc/fstab, you can quickly manually mount it by simple running: $ sudo mount /boot If you want it automatically mounted, just delete 'noauto'.
  3. Just leaving some ideas here, if you want to try some slightly different approach, trying to upgrade @system as a first step is good if you haven't done upgrades in a while, but sometimes all the configurations (e.g. USE flags), make it so if you want to try to upgrade only what came with the stage3 you get more packages and thus potential conflicts, so IMHO its better to try to get a basic and clean @system, from which you can then try upgrade your @world, I would suggest you to try the following steps, as to get a basic clean @system : 1. back up make.conf and package.use. and put a minim
  4. Packages are stablilized in gentoo by changing the keyword form '~arch' to 'arch', e.g. if the ebuild has in KEYWORDS "~amd64" it means the ebuild is not stable, if it has "amd64" it has been stabilized. I remember a question like this was posted some years ago on gentoo's user ML, it is not trivial to do this, basically the advice was: make the change, and wait for stable to catch up, using package.accept_keywords to restrict new versions for your packages from world already installed(and maybe some deps ), this will take a few months. here's a link to the thread from the mailing list[1]. I
  5. j-g-


    What you want already exist, and this wouldn't be a good forum for it anyway: http://wiki.osdev.org Though, I hardly see that much people wanting to tune their kernel and base user-space to the code level, and dealing with up-streaming changes and all that, also when you get into OS internals, tutorials won't be enough, you will need books or more theory for that matter, and study a lot more.
  6. I just gave you the explanation of the flags, and hoped you would catch the working and solve it yourself, anyway look: my gloabal variables for single target are python3.4, but lets try make lensfun use python3.5 I put this in /etc/portage/package.use: media-libs/lensfun python_single_target_python3_5 -python_single_target_python3_4 python_targets_python3_5 And then: $ sudo emerge -av lensfun These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild N ] media-libs/lensfun-0.3.2::gentoo USE="-doc {-tes
  7. You can also set this in /etc/portage/package.use, those environment variables are of a special kind that 'expands' into a use flag. e.g.: media-libs/lensfun python_single_target_python3_4
  8. eselect profile was removed on funtoo, so that wiki page is outadated, and there is no way to use overlay profiles with epro(The script assumes you only want profiles from $PORTDIR), but actually manually putting togheter the profile isn't hard, just take a look at /etc/portage/make.profile/parent, and edit the file, is pretty obvious. I'm trying to get epro to read overlay profiles, but I've been too lazy these days, and only got the start of it.
  9. Then asciidoc isn't pulling texlive, my suspicion would be some package wants to build documentation and it has/generates the sources in latex for it and then a pdf(tipically), check if any package has the doc USE flag this is tusually what causes latex to get pulled by random packages that you wouldn't think need it. Also if an ebuild requires a specific version of ruby to build a package there should be a reason for it, so you are wasting your time trying to avoid it, I told you how to avoid webkit so portage won't ask for ruby but if you want webkit you will have to get ruby, I think you wa
  10. Do you have the test USE flag enabled in make.conf or package.use?, I was reading the ebuild for asciidoc and only when the test use flag is enabled texlive-latex is pulled, I suspect you might have enabled too many USE flags you don't really need. Regarding ruby, the thing is webkit-gtk uses it for generating some files during build, and you got wxGTK with the webkit USE flag, disable that, but It might be actually needed by some application(portage will complain in that case).
  11. 2 factor authentication with passoword + public keys, also the google authenticator is anther nice options for 2 factor, there's tutorials out there on how to do this. But basically is about to set the AthenticationMethods variable in sshd_confing in the order in wich you require them, you can also use 2 public keys. Also reevaluate if you really need 80, and maybe setup some authentication at the http server level so It's more private.
  12. I remmeber some time ago, I was pruning my world file, and saw a version number in there, but maybe I'm remembering incorrectly this( It was some time ago). but as you tested my assertion about pinning the package version in @world is incorrect, so ignore that. (What I meant is portage will think you want X version every time you upgrade and thus not get anymore upgrades for the package, but seems package.mask is still the right file to do this) Anyway, the main problem is adding dependencies to world, it really gets portage confused sometimes when you upgrade and the output isn't pretty.
  13. Here are some, the easiness of USE flags and how you use them, not having to cd into $PORTDIR for every package, basically the toolset is a lot better( eix, equery), python+bash instead of Makefiles(this is very much an opinion, and bash is almost a dirty word on *BSD), sandboxed builds(I'm not sure about this one). PD: I have FreeBSD on a laptop, but I usually use pkg and not the ports, and pkg is awesome, I wish you could get something like that with portage, binary packages are not something portage does very well.
  14. There's 3 things going wrong here: 1. You are pinning the version portage will install for aalib to a specific one into your @world and you'll want upgrades for that. 2. You are adding a dependency to @world, bad idea, you only want programs you directly use in world, and let dependencies be solved by portage 3. You are making a temporary fix, a quick fix that will come and get you in the future again in the next @world upgrade, if gpm build is failing for that package, it's OK to chage the USE environment variable to check if you can build a package without gpm but you add this to pack
  15. j-g-

    compiz, emerald

    Do NOT put anything inside $PORTDIR yourself, this is why /etc/portage and overlays exist, also you shouldn't remove that 'stuff' overlay if that's where you installed stuff from.
  • Create New...