j-g-
-
Posts
80 -
Joined
-
Last visited
-
Days Won
18
Content Type
Profiles
Forums
Blogs
Posts posted by j-g-
-
-
I have an UEFI system and everything works fine. I can write into the partition but I have to mount it manually every time.
# /etc/fstab: static file system information. # # The root filesystem should have a pass number of either 0 or 1. # All other filesystems should have a pass number of 0 or greater than 1. # # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. # # See the manpage fstab(5) for more information. # # <fs> <mountpoint> <type> <opts> <dump/pass> UUID="2B00-F65A" /boot vfat noauto,defaults 1 2 UUID="d9fb9efe-390e-4ff7-870b-83a532af4c8e" / ext4 defaults,noatime 0 1 UUID="8505b49a-0ab4-4393-82f7-fb67d262906c" swap swap defaults 0 0 UUID="09382c16-b07f-4e5e-b8d5-3cf53ed1edcb" /home ext4 rw,relatime,discard,data=ordered 0 2 tmpfs /var/tmp/portage tmpfs size=3G,uid=portage,gid=portage,mode=775,noatime 0 0 #/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
/dev/sda1: UUID="2B00-F65A" TYPE="vfat" PARTUUID="b0c835f5-2c98-084d-ad6d-80ff784cf3b1" /dev/sda2: UUID="d9fb9efe-390e-4ff7-870b-83a532af4c8e" TYPE="ext4" PARTUUID="fe9efbd9-0e39-f74f-870b-83a532af4c8e" /dev/sda3: UUID="8505b49a-0ab4-4393-82f7-fb67d262906c" TYPE="swap" PARTUUID="33cbeea1-0c09-4243-949d-15488c58e41a" /dev/sda4: UUID="09382c16-b07f-4e5e-b8d5-3cf53ed1edcb" TYPE="ext4" PARTUUID="162c3809-7fb0-5e4e-b8d5-3cf53ed1edcb"
boot { generate grub default "Funtoo Linux Vanilla" timeout 1 } "Funtoo Linux Vanilla" { kernel vmlinuz[-v] initrd initramfs.cpio.gz params root=/dev/sda2 rootfstype=ext4 resume=/dev/sda3 } "Funtoo Linux Debian" { kernel kernel[-v] initrd initramfs[-v] params += real_root=auto rootfstype=auto resume=/dev/sda3 }I tried changing the UUID first, then reformatting the partition, swap the UUID by /dev/sda1 in fstab... I'm out of ideas.
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'.
-
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 minimal make.conf( an empty one will do it fine, the idea is going back to the minimal stuff that came with the stage3)cd /etc/portage mv make.conf make.conf.bak mv package.use package.use.bak touch make.conf
2. change the profile to the core flavor and disable any mixin
3. run emerge -ave @system (and wait, this will rebuild all of @system and all the dependecy tree, doing this is going one step further than using backtrack)
4. restore your personal make.conf, and package.use, flavor and mixins, and proceed to try upgrade world( I'd run emerge --with-bdeps=y -avuND --backtrack=30 world), also check you have not by mistake let any dependencies of packages get into world wich might cause slot conflicts, and delete them from /var/lib/portage/world.
PD: try not to put a PYTHON_SINGLE_TARGET in make.conf, if need you to specify a single target for a package, use package.use and "python_single_target_python_3_4" style useflags for that package, to avoid setting it globally in make.conf.
-
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'd say also that once @system has catched up with unstable you could try 'emerge -e @world'
[1] https://groups.google.com/forum/#!topic/linux.gentoo.user/zcMg38XEWtw -
if you are interested please just post the tutorials online, that way they are available for everyone to see. I think it would give users an ability to customize their workspace and environment and provide meaningful request for development as well as allowing users to develop the kernel and the OS as they see fit.
Thanks
What you want already exist, and this wouldn't be a good forum for it anyway:
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.
-
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 {-test}" CPU_FLAGS_X86="sse sse2" PYTHON_SINGLE_TARGET="python3_5 -python3_3 -python3_4" PYTHON_TARGETS="python3_4 python3_5 -python3_3" 767 KiB Total: 1 package (1 new), Size of downloads: 767 KiB Would you like to merge these packages? [Yes/No] n Quitting.It works, but I was hoping you could do this on your own.
-
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
-
Daniel Robbins guide to Creating Profiles
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.
-
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 want to see the slim installation you get with a binary distro but that won't happen, you will always get more packages when you not only run but also build your packages.
PD: webkits are some of the packages that take the loger to build, but they are getting more and more used with everything going cluod and web these days. so if an application wants to render html internally, it means you will have to compile webkit and be patient about it, or not use that application/ not compile the feature. -
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).
-
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.
-
I have verified that nothing is pinned so I myself was confused about what he meant there.
If I were to manually do:
# USE="-dbus" emerge =app-editors/mousepad-0.3.0
A future world update would still automatically do:
# emerge =app-editors/mousepad-0.4.0
removing the "-dbus" use flag in the process as well. Nothing is pinned/frozen.
Maybe he had the wrong use of words?
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.
-
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.
-
USE="-gpm" emerge =media-libs/aalib-1.4_rc5-r6
This should fix it for you.
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 package.use(and a comment of why might be useful) and report the bug in the build, so it gets either fixed or masked, once that's done (check after reporting and syncing the tree, maybe some days) you can remove what you put in package.use.
Also the correct way of building dependencies manually is to use -1( --oneshot) so it doesn't get added to the world file, also be selective about what packages you might want to pin to a version and have no upgrades for it might cost you not getting security upgrades.
The command should have been
# USE="-gmp" emerge -1av =media-libs/aalib-1.4_rc5-r6 # $EDITOR /etc/portage/package.use -- ... # Temporarily disable gpm for aalib media-libs/aalib -gpm ... --
PD: I disable gpm system wide in make.conf, it's practically useless with tmux and knowing how to use your keyborard, so unless you are using elinks or lynx as your browser(is anyone ?), I don't see the use of having a mouse pointer in console.
-
Got everything working. Here's what I did:
layman -a stuff
Then after sync/update and installation I created /usr/portage/profiles/package.mask/compiz-mask and added:
>dev-python/compizconfig-python-0.8.4-r5 >x11-libs/compiz-bcop-0.8.8 >x11-libs/compizconfig-backend-gconf-0.8.8 >x11-libs/libcompizconfig-0.8.8 >x11-plugins/compiz-plugins-extra-0.8.8 >x11-plugins/compiz-plugins-main-0.8.8 >x11-wm/compiz-0.8.8-r2 >x11-apps/ccsm-0.8.4-r6 >x11-apps/fusion-icon-0.1-r4 >x11-themes/emerald-themes-0.5.2 >x11-wm/emerald-0.8.8-r1
then
layman -d stuff
Everything is working. No glitches or bugs. ;)
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.
-
read emerge(5) about autounmask. this is stuff you shuold know ...
Also try reading the reported error, it is actually instructions about what to do.
-
Try, package.use:
... sys-fs/eudev -gudev ...
and emerge wine with -D and -N, or emerge -1N eudev and emerge wine again.
The problem seems to be dev-libs/gudev doesn't want an udev built with gudev.
-
...
emerge -auv dev-python/pygments dev-python/numpy
Add --oneshot to that, or it may come and bite you in the future
-
I should also ask have you added dependecies of packes to @world? I have had slot conflicts for that before try to purge your world file of any package that you don't really use direclty yourself, and might be being pulled by other package.
-
You went wild in your make.conf with those USE flags, I think is a bad practice to handle the way you seem to have been handling those, and might be causing some of the trouble, do you really want every package building with every possible feature you put in there, you get contratictions by setting gtk3 gtk and qt flags that way, and you have to be deactivating conflicts in package.use rather than putting your prefferences there, first choose an accordin profile if you need a desktop system set a desktop profile, a lot useflags needed/recommended and tested are already set in those profiles, most of the codecs you have put in there and flags like X.
I recommend you to read and try to grasp package atoms(cat/pkg-version:slot::overlay) as quick as posible if you haven't already, (man 5 portage, and /atoms ) also learn about the different file in /etc/portage, specially package.use package.env make.conf accept.keywords, that manual has info about those as well.
If you want to read about expanded use flags like the python ones that seem to be causing you this trouble, search for that in the web and the python eclasses, but this is developer documentation level so if you are just starting try to learn about the variables in make.conf first, for the most part your make.conf looks good already.
The way I do it is I put only flags that I want In every possible package in the USE variable in make.conf wich are just a few, e.g,
USE=" vim-syntax zeroconf -libav -bluetooth -wifi" (It's a desktop that has none of these, and I want ffmpeg not libav wich conflict with each other anyway)
Then I look at the flags every program I want to add into @world before merging it using emerge -av package before each install, and if I want some of the extra useflags the package has I add them in my /etc/portage/package.use and let --autounmask-write resolve the missing ones at the bottom of the file, so it looks like this.
# Use flags set by me catA/package1 use1 use2 use3 catB/packag2 use2 use10 use20 # Flags automatically added by portage # required by catX/pkgY-0.1::gentoo # required by catA/package1 (argument) >=catX/pkgW-0.0 use100 .....
You might want to take out ruby19 from make.conf also, It is being deprecated, It is causing part of the problem.
PD: This was my final choice on how to handle USE flags in a sane way, after a doing a lot of stupid stuff, that was pretty much recipes for disaster, putting everything into the USE variable in make.conf is one of those recipes.
-
The picture doesn't mention udev nor the new systemd-boot which now manages your system before the kernel even loads! I'm wondering how the old LinuxBIOS project is doing ... might be nice to replace my uefi bios with a slim Linux kernel :)
I think you already know this, but you can do away with the bootloader for UEFI, with the CONFIG_EFI_STUB, and boot the kernel directly from the EFI menu, and compile in your command line arguments, but because of the way you wrote that I guess you don't like UEFI either.
About udev I would say I didn't see the need to put it into the systemd repo when it was being being widely used, and In fact was a shady and totally unnecessary thing to do that in the end only hurted systemd anyway, Kay Sievers is not anyones favorite person in the linux world anyway, it's a shame there was not other better hacker at dealing with the community to take the udev maintance(I think it was his project from the beginning anyway, I wish somebody else had made udev first I guess).
By the way, since you think stdin and stdout are so awesome, this might be of your interest, the presentation is quite interesting. and a document to keep around for reference.
-
Don't do that, those python use flags are of a special kind, and I suspect this might be a bug that needs attention from the devs, the last resource I have tried in scenarios like these is doing the following:
emerge -pe @system (to check if all the dependencies can be solved for the entire system and its dependencies)
and run an emerge -ae @system, then try the world upgrade, I think portage might get pulled with @system.I don't think the case here is you having put something python related in make.conf that might be causing this, but post it just to check it out, emerge --info also.
Be careful and do no try to many wild things, unless you really know what you are doing, you can screw up your package manager, and you DO NOT want to do that. you might actually want to emerge --quickpkg portage to have a backup before going any further trying to solve this particular problem, slots confilct are not that much of a big deal, but the fact that they can mess you installing portage is, in this particular instance.
-
Two seperate people. Two seperate opinions.
It's two individuals who have arrived at Funtoo for different reasons so I don't get the point you are trying to make.
I use gas in my car. You use gas in your car. Does that mean we have the same beliefs?
I do hate systemd. FACT. Everything about it. FACT.
Why? This is reason enough:
Invasive and growing. At this rate there will be only one Linux to choose from. Redhat.
My point was and I stated it previously "I have percived funtoo getting pouplarity mainly for not using systemd and taking the position that it will never give support for it, and not the other neat Ideas I think are better than the effort of keeping systmed away and not going the way gentoo did, leaving it to be a choice by the user", I just did't want to keep making this much longer, and I was not talking only about you, but more about other instances I have read around the web also.
Nice picture BTW. I dont hate nor love systemd, I just use it and like some of it's Ideas, the same way I use funtoo and other init systems(BSD) and like some of it's ideas.
PD: Have you looked into the amount of software that gets maintained by people working at redhat that is kind of defacto among many linux distributions ( e.g. A lot gcc, and the complete coreutils, I think the still maintain sysvinit) and they employed the likes of the once 'Second in Command' in the Linux Kernel Alan Cox for most of his career until retirement? I would actually like that to be less but I'm at least glad they follow the open source model, altough I do suspect that if they decided to be more privative a lot of the clever people working ther would leave, like what happened with Oracle and Sun.
-
Try and sync again with the portage tree. Is always better to have the latest updates and fixes, this might be solved, I couldn't look more into it now but seems to me those r1 r100* python ebuilds are the ones causing this mess.
-
try this, to make portage go deeper:
emerge -a -v -p -t --with-bdeps=y --backtrack=30 -D -N -1 portage
If that goes well remove -p, and run it for real.
the important ones are backtrack, with-bdeps, -D -N, for dpendencies and useflags , and -1.
Safe way to access linux file server from a linux laptop
in General Discussion
Posted
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.