Re: [gentoo-user] ssh from linux to Windows
On Sat, 6 Jan 2024 20:09:37 -0700 the...@sys-concept.com wrote: > I installed openssh server on Windows 11 and tried to ssh to it using the > id_rsa.pub key > but I didn't have luck. I copied the key to .ssh\authorized_keys file. > On linux the last line ending with "\" on Windows Notepad replaces it with > the "+" sign. > > ssh with password is working but windows doesn't recognize the public key or > maybe it is wrong directory C:\Users\Garry Server\.ssh\authorized_keys > If ssh with password is working, did you try letting ssh decide for the correct location for your ssh key via ssh-copy-id: ssh-copy-id -i ~/.ssh/my_key usern...@example.com First time it will of course log in via password, but any further login should use the ssh key. If the key is still not accepted, have you tried a different ssh key type (e.g. ed25519). Maybe the server rejects RSA keys?
Re: [gentoo-user] SDDM tmp file goes missing?
On Fri, 5 Jan 2024 08:04:49 +0100 Arve Barsnes wrote: > On Fri, 5 Jan 2024 at 02:49, Spackman, Chris wrote: > > Any thoughts on possible causes or fixes? > > I've also had this happen a few times over the last months, with error > mails about SDDM tmp files from cron. Just wanted to pipe in and say > that I don't have either rkhunter or keepassxc, so they must be > unrelated. Running on openbox. > > I also have the 'unable to open new GUI apps' problem on a Plasma > machine now and then. I had not connected the two, but maybe the same > root cause. > > Regards, > Arve > It's the anacron job in /etc/cron.daily/systemd-tmpfiles-clean that cleans files in the tmp folder. There has also been a news item about the change on November 21st 2022. You might have to adapt the files that should not be cleaned by the automatic cleanup (or disable automatic cleanup). Cheers Andreas
[gentoo-user] Cronie update breaks anacron
The latest update to cronie (sys-process/cronie-1.7.0) seems to have broken anacron functionality. The file /etc/cron.hourly/0anacron tries to source the file /etc/default/anacron, which does not exist. The full error message looks like this: /etc/cron.hourly/0anacron: line 11: /etc/default/anacron: No such file or directory run-parts: /etc/cron.hourly/0anacron exited with return code 1 Of course I could just create an empty file, and it would work again, but I am wondering if there is something broken in the default setup, which was forgotten to bundle in the cronie install package? Anybody else experiencing this? Did I miss something?
Re: [gentoo-user] Controlling emerges
On Tue, 19 Sep 2023 17:14:42 +0800 William Kenworthy wrote: > That is where you set per package compiler parameters by overriding > make.conf settings. > > BillK > > I would argue, that per package compiler parameters is not what is needed, because in the example of chromium 99% of the compile time can be done with -j16 on my machine, but at a very short time I would need to run with -j1, because I otherwise run out of memory otherwise. In short: I want to run with as many jobs as I have cores, as long as I do not run out of memory, and when I run out of memory I want to run with as little jobs as possible until the pressure on the memory is gone. Then I want to continue with as many jobs as possible. And this is not something that make / ninja provide. They have a concept of global number of jobs, which in this concept must be set to the maximum number that your RAM can take at the very short period in time where you have a high watermark on your RAM, but that number would be at 99% of the compilation time way too low. FWIW, I have a hacky solution that I use privately, but I never published it anywhere, because it could break some builds, and at the moment I'm not ready to support it. Basically it tries to run with as many jobs as the number of CPU cores at all times. It watches memory pressure in the background and kills build jobs as soon as a high watermark is reached. At this point, make would normally exit, because a build job failed. However my hacky solution overrides the exec-family of system calls, and if a job fails, it is being retried exclusively, i.e. no other build job is allowed to run at the same time as the failed job. It fails ultimately, when the second and exclusive run fails too. This way, if the job failed only because of lack of memory, it will be retried exclusively and succeeds. If it failed due to a programming error, it will fail also the second time, and then the error is forwarded to make.
Re: [gentoo-user] EMERGENCY: X11 KEYBOARD MAPPING STOPPED WORKING!!!!
On Wed, 5 Jul 2023 16:42:15 -0400 Alan Grimes wrote: > I need a way to get X11 to boot into dvorak layout mode without having > to look up this e-mail to find the command to set the layout to dvorak. > > My current xorg.conf has: but does not do anything useful. > > Section "InputDevice" > # generated from default > Identifier "Keyboard0" > Driver "keyboard" > Option "XkbLayout" "us" > Option "XkbVariant" "dvorak" > EndSection > > > Michael wrote: > > setxkbmap -layout us -variant dvorak > I have this in my config file: Section "InputClass" Identifier "Keyboard" Driver "libinput" MatchIsKeyboard "on" Option "xkbmodel" "evdev" Option "xkblayout" "us" Option "xkbvariant" "altgr-intl" Option "xkbrules" "evdev" Option "xkboptions" "nodeadkeys" EndSection Maybe it helps.
Re: [gentoo-user] guvcview - no video device (/dev/video0) found
On Sat, 13 May 2023 14:50:33 -0600 the...@sys-concept.com wrote: > Getting an error message when trying to start usb-cam: > > guvcview > ENCODER: no video codec detected for VP9 (VP9) > ENCODER: no video codec detected for Theora (ogg theora) > GUVCVIEW: version 2.0.8 > GUVCVIEW: couldn't open /home/joseph/.config/guvcview2/video0 for read: No > such file or directory > V4L2_CORE: ERROR opening V4L interface: No such file or directory > GUVCVIEW (2): Guvcview error >no video device (/dev/video0) found > GUVCVIEW (Qt5): fatal error (0 devices detected) > GUVCVIEW (Qt5): creating error dialog > > dmesg: > > [935066.984348] usb 1-1.4: Product: Vega USB2.0 Camera > [935066.984350] usb 1-1.4: Manufacturer: Vimicro Corp. > [936075.049430] usb 1-1.4: USB disconnect, device number 47 > [936080.312412] usb 1-1.4: new high-speed USB device number 48 using xhci_hcd > [936080.504291] usb 1-1.4: New USB device found, idVendor=0ac8, > idProduct=0331, bcdDevice= 1.00 > [936080.504296] usb 1-1.4: New USB device strings: Mfr=1, Product=2, > SerialNumber=0 > [936080.504297] usb 1-1.4: Product: Vega USB2.0 Camera > [936080.504299] usb 1-1.4: Manufacturer: Vimicro Corp. > Do you have read/write access to /dev/video0? Try with: ls -lh /dev/video*
Re: [gentoo-user] Jobs and load-average
On Thu, 16 Feb 2023 09:24:08 -0500 Rich Freeman wrote: > On Thu, Feb 16, 2023 at 8:39 AM Peter Humphrey wrote: > > > > I've just looked at 'man make', from which it's clear that -j = --jobs, and > > that both those and --load-average are passed to /usr/bin/make, presumably > > untouched unless portage itself has identically named variables. So I wonder > > how feasible it might be for make to incorporate its own checks to ensure > > that > > the load average is not exceeded. I am not a programmer (not for at least 35 > > years, anyway), so I have to leave any such suggestion to the experts. > > > > Well, if we just want to have a fun discussion here are my thoughts. > However, the complexity vs usefulness outside of Gentoo is such that I > don't see it happening. > > For the most typical use case - a developer building the same thing > over and over (which isn't Gentoo), then make could cache info on > resources consumed, and use that to make more educated decisions about > how many tasks to launch. That wouldn't help us at all, but it would > help the typical make user. However, the typical make user can just > tune things in other ways. > > It isn't going to be possible for make to estimate build complexity in > any practical way. Halting problem aside maybe you could build in > some smarts looking at the program being executed and its arguments, > but it would be a big mess. > > Something make could do is tune the damping a bit. It could gradually > increase the number of jobs it runs and watch the load average, and > gradually scale it up appropriately, and gradually scale down if CPU > is the issue, or rapidly scale down if swap is the issue. If swapping > is detected it could even suspend most of the tasks it has spawned and > then gradually continue them as other tasks finish to recover from > this condition. However, this isn't going to work as well if portage > is itself spawning parallel instances of make - they'd have to talk to > each other or portage would somehow need to supervise things. > > A way of thinking about it is that when you have portage spawning > multiple instances of make, that is a bit like adding gain to the > --load-average MAKEOPTS. So each instance of make independently looks > at load average and takes action. So you have an output (compilers > that create load), then you sample that load with a time-weighted > average, and then you apply gain to this average, and then use that as > feedback. That's basically a recipe for out of control oscillation. > You need to add damping and get rid of the gain. > > Disclaimer: I'm not an engineer and I suspect a real engineer would be > able to add a bit more insight. > > Really though the issue is that this is the sort of thing that only > impacts Gentoo and so nobody else is likely to solve this problem for > us. > Given all your explenation and my annoyance a couple of years ago, I hacked a little helper that sits between make and spawned build jobs. Basically what annoyed me is the fact that chromium would compile for hours and then fail, because it would need more memory than memory available, and this would fail the whole build. One possible solution is to reduce the number of build jobs to e.g. -j1 for chromium, but this is stupid because 99% of the time -j16 would work just fine. So I hacked a bit around, and came up with little helper The helper would limit spawning new jobs to SOME_LIMIT, and when load is too high (e.g.g I am doing other work on the PC, that's not under emerge's control). The watcher kills memory hungry build jobs, once memory usage higher than 90%, tells the helper to stop spawning new jobs, waits until the helper reports that no more build jobs are running and then respawns the memory hungry build job (i.e. the memory hungry build job will run essentially as if -j1 was specified) This way I can mix emerge --jobs=HIGH_NUMBER and make -jOTHER_HIGH_NUMBER, and it wouldn't affect the system, because the total number of actual build jobs is controlled by the helper, and would never go beyond SOME_LIMIT, even if HIGH_NUMBER*OTHER_HIGH_NUMBER > SOME_LIMIT. I never published this anywhere, but if there's interest in it, I can probably upload it somewhere, but I had the feeling that it's quite hacky and not worth publishing. Also I was never sure if I break emerge in some way, because it's very low-level, but now it's running since more than a year without any emerge failure due to this hijacking.
Re: [gentoo-user] Jobs and load-average
On Thu, 16 Feb 2023 09:53:30 + Peter Humphrey wrote: > On Wednesday, 15 February 2023 13:18:24 GMT Rich Freeman wrote: > > > First, keep in mind that --jobs=16 + -j16 can result in up to 256 > > (16*16) tasks running at once. Of course, that is worst case and most > > of the time you'll have way less than that. > > Yes, I was aware of that, but why didn't --load-average=32 take precedence? This only means that emerge would not schedule additional package job (where a package job means something like `emerge gcc`) when load average > 32, howwever if a job is scheduled it's running, independently of the current load. While having it in MAKEOPTS, it would be handled by the make system, which schedules single build jobs, and would stop scheduling additional jobs, when the load is too high. Extreme case: emerge chromium firefox qtwebengine --> your load when you do this is pretty much close to 0, i.e. all 3 packages are being merged simultaneously and each will be built with -j16. I.e. for a long time you will have about 3*16=48 single build jobs running in parallel, i.e. you should see a load going towards 48, when you do not have anything in your MAKEOPTS. Cheers Andreas
Re: [gentoo-user] Glibc and binpackages
On Fri, 13 Jan 2023 11:17:29 -0500 John Blinka wrote: > On Thu, Jan 12, 2023 at 12:54 PM Laurence Perkins > wrote: > > > I’m not sure if I’m doing something horribly wrong, or missing something > > blindingly obvious, but I’ve just had to boot a rescue shell yet again, so > > I’m going to ask. > > > > > > > > To save time and effort, I have my big, powerful machine create > > binpackages for everything when it updates, and then let all my smaller > > machines pull from that. It works pretty well for the most part. > > > > I do something quite similar, but have never had a glibc problem. Maybe the > problem lies in differences between the specific details of our two > approaches. > > I have 3 boxes with different hardware but identical portage setup, > identical world file, identical o.s., etc, even identical CFLAGS, CPPFLAGS > and CPU_FLAGS_X86 despite different processors. Like you, I build on my > fastest box (but offload work via distcc), and save binpkgs. After a world > update (emerge -DuNv —changed-deps @world) , I rsync all repositories and > binpkgs from the fast box to the others. An emerge -DuNv —changed-deps > —usepkgonly @world on the other boxes completes the update. I do this > anywhere from daily to (rarely) weekly. Portage determines when to update > glibc relative to other packages. There hasn’t been a problem in years with > glibc. > > I believe there are more sophisticated ways to supply updated portage trees > and binary packages across a local network. I think there are others on > the list using these more sophisticated techniques successfully. Just a > plain rsync satisfies my needs. > > It’s not clear to me whether you have the problem on your big powerful > machine or on your other machines. If it’s the other machines, that > suggests that portage knows the proper build sequence on the big machine > and somehow doesn’t on the lesser machines. Why? What’s different? > > Perhaps there’s something in my update frequency or maintaining an > identical setup on all my machines that avoids the problem you’re having? > > If installing glibc first works, then maybe put a wrapper around your > emerge? Something that installs glibc first if there’s a new binpkg then > goes on to the remaining updates. > > Just offered in case there’s a useful hint from my experience - not arguing > that mine is the one true way (tm). > > HTH, > > John Blinka > > > In case it is not clear what the underlying problem is: Slow machine updates and is on the same set of packages as the fast machine. Fast machine updates glibc to a new version at time T1 Fast machine updates app-arch/xz-utils to a new version at time T2. This version of xz CAN have glibc symbols from the very newest glibc version that was merged at time T1. Everything is fine on the fast machine. Now the slow machine starts its update process at a time T3 > T2. The list of packages includes glibc AND xz-utils, however xz-utils is often pulled in before glibc which ends in a disaster. Now you have an xz decompressing tool on your slow machine that cannot run, because some library symbols from glibc are missing (because glibc was not merged yet), and you're pretty much stuck in the middle of the update with a broken system. I have seen this kind of behaviour only when I have not updated for a very long time the slow machine (i.e. no update for a year). Anyway I think a reasonable default for emerge would be to merge glibc as early as possible, because all other binary packages could have been built with the newer glibc version, and could potentially fail to run on the slow machine until glibc is updated. Hope that clears up what happens, and why it fails to update / breaks the slow machine. Andreas
Re: [gentoo-user] How to produce broken binary packages
On Sun, 15 Jan 2023 12:14:29 +0100 Alexander Puchmayr wrote: > Hi there, > > I just encountered a problem regarding binary packages and got some broken > packages and I don't know how to solve this permanently; On my buildhost I > compile all packages I need for several VMs and install only those packages I > really need on the target machines. > > Problem combination: > > * net-fs/samba-4.15.12-r2 has a direct dependency to sys-libs/liburing. > * dev-db/mariadb does not have a dependency to liburing, but during build, if > liburing is available it will use it for some reason yielding a binary that > links against it: > > Buildhost-server ~ # ldd /usr/sbin/mysqld > linux-vdso.so.1 (0x7ffec5b61000) > libpcre2-8.so.0 => /usr/lib64/libpcre2-8.so.0 (0x7fcfbd704000) > libcrypt.so.2 => /lib64/libcrypt.so.2 (0x7fcfbd6c9000) > liburing.so.2 => /usr/lib64/liburing.so.2 (0x7fcfbd6c2000) > --- > > Installing that package on a target VM does not install liburing, hence > yielding a broken /usr/sbin/mysqld binary because the library is missing, and > the reason why I still have a consistent system on my buildhost is because > samba has it as dependency. > > A quick on-the-fly solution is either manually installing liburing and adding > it to the world profile (@world is required otherwise emerge -c will remove it > again), or install mariadb by compiling it (not using emerge -k). But all of > them are somewhat unclean. > > A) Is this a problem in the ebuild script of mysql because not taking care of > this? > b) Is this a problem of mariadb's configure/make script because of implicitly > using the library without being told so by ebuild? > > Alex > Typically this is something that can be fixed in the ebuild, but ultimately it is a problem with automagic dependencies (check for the many automagic open bugs on bugs.gentoo.org or your described problem here: https://bugs.gentoo.org/878853) However I did not go to the build system of mariadb, and checked whether automatic discovery of a liburing can be explicitly turned on/off.
Re: [gentoo-user] Glibc and binpackages
On Thu, 12 Jan 2023 17:53:55 + Laurence Perkins wrote: > I'm not sure if I'm doing something horribly wrong, or missing something > blindingly obvious, but I've just had to boot a rescue shell yet again, so > I'm going to ask. > > To save time and effort, I have my big, powerful machine create binpackages > for everything when it updates, and then let all my smaller machines pull > from that. It works pretty well for the most part. > > But when there's a glibc update I have to specifically install it first. If > I don't, then about half the time emerge decides that because it doesn't have > to worry about build dependencies for binpackages, it can obviously update > glibc last... Then it updates something that's needed for handling updates > and that's it, stuck. If I'm lucky it's a compile tool, not one for handling > binpackages and I can just tell it to do the glibc package next. Quite often > though it's something like tar that's fundamental to installing anything at > all and I have to ferry the new glibc over on a USB stick and unpack it with > busybox... Occasionally it's something critical for the whole system and > then I have to boot to a rescue shell of some kind. > > Think it's worth a feature request to have emerge prioritize glibc as high up > in the list as it can when installing things? Or am I the only one who runs > into this? > > LMP I was running into this issue too already, but then at some point I started more regularly updating and this problem disappeared. I fully agree, that glibc should be updated rather earlier than later, especially when compression libraries were built with a newer glibc. /Andreas
Re: [gentoo-user] Docker installation issues
On Sat, 10 Dec 2022 15:51:17 -0500 Mansour Al Akeel wrote: > Andreas, > > Thank you very much. In fact I didn't go that deep yet, and not sure if I > should. I just found that the url is not accessible even from a browser. > Googling a bit, tells me there is no clear URL for docker-registry and > possibly this one is outdated. I will continue looking around to confirm > what the current default repo should be. If you have any suggestions, > please let me know. > > > localhost in ~ > ○ → curl -k -v https://registry-1.docker.io/v2/ > * Trying 34.228.211.243:443... > > * connect to 34.228.211.243 port 443 failed: Connection timed out > * Failed to connect to registry-1.docker.io port 443 after 129401 ms: > Couldn't connect to server > * Closing connection 0 > curl: (28) Failed to connect to registry-1.docker.io port 443 after 129401 > ms: Couldn't connect to server You have a a strange DNS resolution. The IP address 34.227.211.243 seems wrong. Here is what I see when I look at the DNS records: andreas@localhost ~$ dig registry-1.docker.io ; <<>> DiG 9.16.33 <<>> registry-1.docker.io ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11419 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;registry-1.docker.io. IN A ;; ANSWER SECTION: registry-1.docker.io. 13 IN A 34.205.13.154 registry-1.docker.io. 13 IN A 44.205.64.79 registry-1.docker.io. 13 IN A 3.216.34.172 ;; Query time: 10 msec ;; SERVER: 79.143.183.251#53(79.143.183.251) ;; WHEN: Sun Dec 11 06:56:50 CET 2022 ;; MSG SIZE rcvd: 97 I am not sure Not sure where you get the wrong IP from, but it is a DNS issue.
Re: [gentoo-user] Docker installation issues
On Sat, 10 Dec 2022 12:30:40 -0500
Mansour Al Akeel wrote:
> I am using Openrc
>
> This was my initial /etc/conf.d/docker
> DOCKER_OPTS="--storage-driver overlay2 --data-root /srv/var/lib/docker"
>
> when I try:
>
> $ docker pull hello-world
>
> Error response from daemon: Get "https://registry-1.docker.io/v2/":
> net/http: request canceled while waiting for connection (Client.Timeout
> exceeded while awaiting headers)
>
> Trying to troubleshoot:
>
> localhost /home/mansour # tail -n 20 /var/log/docker.log
> time="2022-12-10T12:17:03.473550705-05:00" level=info msg="scheme \"unix\"
> not registered, fallback to default scheme" module=grpc
> time="2022-12-10T12:17:03.473566413-05:00" level=info
> msg="ccResolverWrapper: sending update to cc:
> {[{unix:///run/containerd/containerd.sock 0 }] }"
> module=grpc
> time="2022-12-10T12:17:03.473573787-05:00" level=info msg="ClientConn
> switching balancer to \"pick_first\"" module=grpc
> time="2022-12-10T12:17:03.474530993-05:00" level=info msg="parsed scheme:
> \"unix\"" module=grpc
> time="2022-12-10T12:17:03.474545549-05:00" level=info msg="scheme \"unix\"
> not registered, fallback to default scheme" module=grpc
> time="2022-12-10T12:17:03.474563752-05:00" level=info
> msg="ccResolverWrapper: sending update to cc:
> {[{unix:///run/containerd/containerd.sock 0 }] }"
> module=grpc
> time="2022-12-10T12:17:03.474571186-05:00" level=info msg="ClientConn
> switching balancer to \"pick_first\"" module=grpc
> time="2022-12-10T12:17:03.478908716-05:00" level=warning msg="Your kernel
> does not support cgroup blkio weight"
> time="2022-12-10T12:17:03.478927115-05:00" level=warning msg="Your kernel
> does not support cgroup blkio weight_device"
> time="2022-12-10T12:17:03.479037897-05:00" level=info msg="Loading
> containers: start."
> time="2022-12-10T12:17:03.495743563-05:00" level=info msg="failed to read
> ipv6 net.ipv6.conf..accept_ra" bridge=docker0
> syspath=/proc/sys/net/ipv6/conf/docker0/accept_ra
> time="2022-12-10T12:17:03.518761943-05:00" level=info msg="Default bridge
> (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip
> can be used to set a preferred IP address"
> time="2022-12-10T12:17:03.518886881-05:00" level=info msg="failed to read
> ipv6 net.ipv6.conf..accept_ra" bridge=docker0
> syspath=/proc/sys/net/ipv6/conf/docker0/accept_ra
> time="2022-12-10T12:17:03.534616741-05:00" level=info msg="Loading
> containers: done."
> time="2022-12-10T12:17:03.541080189-05:00" level=info msg="Docker daemon"
> commit=a89b84221c graphdriver(s)=overlay2 version=20.10.17
> time="2022-12-10T12:17:03.541122352-05:00" level=info msg="Daemon has
> completed initialization"
> time="2022-12-10T12:17:03.549888103-05:00" level=info msg="API listen on
> /var/run/docker.sock"
> time="2022-12-10T12:17:27.025622231-05:00" level=warning msg="Error getting
> v2 registry: Get \"https://registry-1.docker.io/v2/\": net/http: request
> canceled while waiting for connection (Client.Timeout exceeded while
> awaiting headers)"
> time="2022-12-10T12:17:27.025667054-05:00" level=info msg="Attempting next
> endpoint for pull after error: Get \"https://registry-1.docker.io/v2/\":
> net/http: request canceled while waiting for connection (Client.Timeout
> exceeded while awaiting headers)"
> time="2022-12-10T12:17:27.026851821-05:00" level=error msg="Handler for
> POST /v1.41/images/create returned error: Get \"
> https://registry-1.docker.io/v2/\": net/http: request canceled while
> waiting for connection (Client.Timeout exceeded while awaiting headers)"
>
> time="2022-12-10T12:15:42.036053086-05:00" level=info msg="loading plugin
> \"io.containerd.internal.v1.tracing\"..." type=io.containerd.internal.v1
> time="2022-12-10T12:15:42.036068412-05:00" level=error msg="failed to
> initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint:
> skip plugin"
> time="2022-12-10T12:15:42.036100189-05:00" level=info msg="loading plugin
> \"io.containerd.grpc.v1.cri\"..." type=io.containerd.grpc.v1
> time="2022-12-10T12:15:42.036390695-05:00" level=info msg="Start cri plugin
> with config {PluginConfig:{ContainerdConfig:{Snapshotter:overlayfs
> DefaultRuntimeName:runc DefaultRuntime:{Type: Path: Engine:
> PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[]
> PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir:
> NetworkPluginMaxConfNum:0} UntrustedWorkloadRuntime:{Type: Path: Engine:
> PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[]
> PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir:
> NetworkPluginMaxConfNum:0} Runtimes:map[runc:{Type:io.containerd.runc.v2
> Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root:
> Options:map[BinaryName: CriuImagePath: CriuPath: CriuWorkPath: IoGid:0
> IoUid:0 NoNewKeyring:false NoPivotRoot:false Root: ShimCgroup:
> SystemdCgroup:false] PrivilegedWithoutHostDevices:false BaseRuntimeSpec:
> NetworkPluginConfDir: NetworkPluginMaxConfNum:0}]
Re: [gentoo-user] Libsld, what gives?
On Wed, 16 Nov 2022 02:11:18 -0500 Alan Grimes wrote: > I'm jackhammering the system now and I'm getting about 50% error spew I would suggest a different tool than a jackhammer to fix the problems.
Re: [gentoo-user] Getting maximum space out of a hard drive
On Thu, 18 Aug 2022 13:04:57 -0500 Dale wrote: > Howdy, > > I got my 10TB drive in today. I want to maximize the amount of data I > can put on this thing and it remain stable. I know about -m 0 when > making the file system but was wondering if there is any other tips or > tricks to make the most of the drive space. This is the output of cgdisk. > > > Part. # Size Partition Type Partition Name > > 1007.0 KiB free space > 1 9.1 TiB Linux filesystem 10Tb > 1007.5 KiB free space > > > I'm not sure why there seems to be two alignment spots. Is that > normal? Already, there is almost 1TB lost somewhere. Any way to > increase that and still be safe? Right now, I've ran the short test and > it is chewing on the long test. It will be done around 7AM tomorrow, 19 > or 20 hours to complete. As it is, there's no data on it or even a file > system either. Now is the time to tweak things. > > Any tips or ideas would be appreciated. > > Dale > > :-) :-) > Ah yes, the good old harddisk marketing size calculating in base 1000, while TiB is in base 1024. In short: 1TB=1000^4 != 1TiB=1024^4 Do the math yourself, what 10TB should be in TiB, but it's in the ballpark of 9.1TiB ;)
Re: [gentoo-user] Any way to run multiple commands from single script in parallel?
On Mon, 14 Mar 2022 11:13:13 +0100
"J. Roeleveld" wrote:
> Hi,
>
> I often put multiple commands into a single file/script to be run in sequence.
> (each line can be executed individually, there is no dependency)
>
> Is there a tool/method to execute multiple lines/commands simultaneously? Like
> having 3 or 4 run together and when 1 is finished, it will grab the next one
> in
> the list?
>
> I would prefer this over simply splitting the file as the different lines/
> commands will not take the same amount of time.
>
> Thanks,
>
> Joost
>
>
>
At the end there's a very rudimentary bash script to do this. I did not
do much debugging (probably it fails already if max_jobs>#list_of_jobs).
Anyway it's just making use of sending jobs to the background and
"communicating" through a FIFO pipe (which you might want to delete at
the end).
#!/bin/bash
list_of_jobs=("sleep 3" "sleep 5" "sleep 1" "sleep 10" "sleep 4")
max_jobs=2
my_fifo=/tmp/my_job_fifo
write_to_fifo="yes"
function run_job () {
eval "$@"
if [[ $write_to_fifo == "yes" ]]; then
echo "Writing to fifo ($@)"
echo 1 > ${my_fifo}
fi
echo Finished job "$@"
}
function read_and_start_job() {
next_job_idx=0
while [[ ${#list_of_jobs[@]} -gt $next_job_idx ]]; do
while IFS= read -r line ; do
echo "next_job_idx=${next_job_idx} total=${#list_of_jobs[@]}"
if [[ $next_job_idx -lt ${#list_of_jobs[@]} ]] ; then
job="${list_of_jobs[${next_job_idx}]}"
echo "Executing: ${job}"
run_job ${job} &
let next_job_idx++
else
echo "Set write_to_fifo=no"
write_to_fifo="no"
fi
done < ${my_fifo}
done
write_to_fifo="no"
wait
}
rm -Rf ${my_fifo}
mkfifo ${my_fifo}
read_and_start_job &
while [[ ${max_jobs} -gt 0 ]] ; do
let max_jobs--
echo 1 > ${my_fifo}
done
wait
Re: [gentoo-user] Options for "emerge"
On Tue, 22 Feb 2022 13:21:48 +0100 Dr Rainer Woitok wrote: > And none of the examples to overcome problems provided by others in this > thread ever contained "--changed-deps". Does this mean "--changed-deps" > is a NOOP, a relict from days long gone by, meanwhile without any funct- > ionality, just provided for compatibility in order to not break ancient > scripts? It is kind of a noop. I am not 100% certain, but my interpretation is the following (based on experience with a binary host serving to several clients). I'm at timepoint T1 and I merge package pkg1, which depends on >=dep1:1.2.0 This is all merged at timepoint T1 and these dependencies are remembered in /var/db/pkg and also in $PKGDIR/Packages. Now comes timepoint T2 the ebuild was modified, no revbump whatsoever has been done, but suddenly the dependency reads as >=dev1:1.2.1. Now normally it is a noop to re-emerge because you are already on dev1:1.3, i.e. nothing really changes BUT it makes a difference for binary packaging. When you have a build-host that you to provide binaries, you can end up in situations where your client would reject a package due to unmatched dependencies (your build-host has emerged pkg1 at timepoint T1 and remembered that pkg1 depends on >=dep1:1.2.0), however you try to update the client at timepoint T2 where the >dependency is now >=dep1:1.2.1, and you'll end up in mismatched dependency and the binary will be rejected, i.e. your client must compile itself and cannot merge from the binary host. When you are not worried providing packages as binaries to other clients you probably should not care about --changed-deps.
Re: [gentoo-user] Options for "emerge"
On Mon, 21 Feb 2022 22:26:30 +0100 hitachi303 wrote: > > emerge -av --depclean Stuff like firefox, thunderbird, etc.> > > emerge -a --depclean --with-bdeps=n > > only then when there are as few programs installed as possible I run > emerge --sync > > emerge -Dua --reinstall changed-use @world I think what you really are doing can be simplified by: emerge -auvDN @system emerge -auvDN @world Once @system is updated it is much simpler to get @world to update too. Maybe you have to help with a couple of `--exclude ATOM` when updating world.
Re: [gentoo-user] Update gentoo from live usb?
On Sun, 30 Jan 2022 02:24:32 -0600 Michael Jones wrote: > Going forward, you could consider having your build host take a snapshot / > backup of the binpkgs it builds every 3-6 months, with the associated > portage tree, so that you can use those to update your sporadically updated > machines. Yes, for the future I'm going to take snapshots of the binpkgs+portage. But the first update will not profit from this idea, since they have not been updated for quite some time now. But thanks for the idea to save me some headache in the future :)
[gentoo-user] Update gentoo from live usb?
Hello, I have a couple of systems that I do not update regularily (some not even for years). But then sometimes I feel, hey I should do an update. I have one master build server which builds packages and keeps them as binary packages, annd all my systems pull the gentoo portage tree from this master build server, additionally also the configs in /etc/portage is the same amongst all boxes, i.e. use flags et al are all the same. Now comes the misery when I want to update an old box, because of unsupported EAPI and what not. One way that I used in the past was to extract a stage-3 tarball over the existing root system, and then do the upgrade, which works to some extent, but it does not seem right. Coming now to my question: Is it possible to start a live gentoo system with a recent portage version and then tell portage that it should install the packages in /mnt/gentoo (which is the real system I care about). I have heard about the prefix project, but I'm not sure if this is exactly what I want. Maybe a second approach would be to get the minimal set of binary packages from the master build server and extract them manually, such that I end up with a recent enough portage which supports all EAPIs that are in the tree. But I have no clue how to get the minimal set of packages that I would need to extract. Does anybody have other approaches (besides starting from scratch)?
Re: [gentoo-user] Strange behaviour disconnecting and reconnecting USB-C screen
On Tue, 11 Jan 2022 10:57:28 +0100 Benjamin Blanz wrote: > Hi, > I have the same issue using a usb-c dockingstation. > I have found it is enough to change the resolution of the connected screens > to get them back. > Still annoying, but at least the windows are not redistributed.On 11.01.22 > 10:25, Andreas Fink wrote: > That did not work for me because xrandr complains that any resolution is an unknown mode. Which command do you use to change the resolution of the connected screen?
[gentoo-user] Strange behaviour disconnecting and reconnecting USB-C screen
Hello, I've got a new laptop and see a strange behaviour when disconnecting and reconnecting my USB-C screen. Here are the steps that I am doing. I have a dual screen setup with xrandr, with my notebook screen being the primary screen and a second large external screen connected via USB-C to my notebook directly. Now I disconnect the USB-C cable and do not do anything software wise, i.e. my X-Server is still pretending to run on two screens, I can move the screen outside of my notebook screen (into the area where the external screen). Now I reconnect the USB-C cable but the screens stays blank (the the screen it says "No USB Type-C connection from your computer"). The only way to get a signal again is to first use xrandr to only use my notebook screen, and at the exact time udev gets a DRM event, and suddently my external monitor appears within xrandr as connected (I did not touch the cable, I only ran an xrandr command to use only the notebook screen). Right after the DRM event I can run the xrandr command to use both screens, but it is annoying to degrade first to one screen, because all windows are moved around and I do not end up with the same window setup as before. Using the same screen with the same experiment as described above but with a different notebook the screen is able to pick up the signal again, so it's not purely a problem with the external screen. Any idea what is going on and how I can workaround it? I just want to disconnect the cable and reconnect it without the need to switch any xrandr setup. Thanks for your ideas and help Andreas
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 13:14:26 +0200 n952162 wrote: > On 5/16/21 12:53 PM, Andreas Fink wrote: > > On Sun, 16 May 2021 12:49:26 +0200 > > n952162 wrote: > > > >> On 5/16/21 11:28 AM, Neil Bothwick wrote: > >>> On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: > >>> > >>>>>> There are no use flags defined for any of the packages I did a random > >>>>>> check for, either on the server or the client. I am worried that it > >>>>>> is as you say: that the ebuild has a change of USE flags, which, of > >>>>>> course, has nothing to do with me, the user. > >>>>> As already stated, any USE flag changes would appear in the emerge > >>>>> output, this is most likely caused by --changed-deps. Try with > >>>>> --changed-use but without --changed-deps to see. > >>>>> > >>>>> > >>>> I have introduced that into my build script. But, if it's as you say, > >>>> the one is a subset of the other, it should have no effect on the > >>>> output, right? > >>>> > >>> --changed-use is a subset of --newuse. --changed-deps is separate. > >>> > >>> > >> Ah, I oversaw that. > >> > >> Ah. why would I want to have --changed-deps anyway? That suddenly seems > >> silly. > >> > >> It's unfortunate, if there's no explanatory display if a package got > >> disqualified for that reason. > >> > >> > > Trying to comprehend here... > > > If you want to have a binhost, then --changed-deps will become > > "necessary" at some point. Let me draw you a picture, where a binhost > > would fail to provide the correct package: > > - Binhost builds on day 1 package XYZ(i.e. server updates from internet) > > - computer that would merge with packages from binhost is NOT > > updated(client does NO emerge on that day) > > - the dependencies are changed on day 2(i.e. XYZ is emerged onto server, > > with changed dependencies in the ebuild) > > - Binhost does NOT rebuild, because you do not have --changed-deps > > enabled on day 2*(what is "Binhost" here? The --changed-deps is > > specified on the client)* > > - Computer that merges from the binhost is updated on day 2 but will > > NOT use the binary package from binhost, because the dependencies do > > not match > > There are flags to ignore dependency mismatches, but the default would > > just not use the binary package. > > > > Cheers > > Andreas > > > What does changed-deps mean, actually? > > --changed-deps [ y | n ] > Tells emerge to replace installed packages for which > the corresponding > ebuild dependencies have changed since the packages were > built. ... > > I presume it means that a package needed XYZ before, but now needs > XYZZ. If I don't specify --changed-deps, that I might get a run-time > resolution problem. Changed dependencies means any change in the *.ebuild file with respect to the variables DEPEND/BDEPEND/RDEPEND/PDEPEND, e.g. version of a dependent package has changed, new package was added as dependency, a package was removed as dependency. All are dependency changes. If the changed *.ebuild file is commited to the portage tree WITHOUT a version-bump/revision-bump, then emerge would NOT rebuild the package, unless --changed-deps is given as an argument. > > Or, does it mean that the package specified XYZ.1 in an excess of > precision and the new version specifies XYZ.3? > > I just ran into this: > > --binpkg-changed-deps [ y | n ] > Tells emerge to ignore binary packages for which the > corresponding ebuild > dependencies have changed since the packages were built. > In order to help > avoid issues with resolving inconsistent dependencies, > this option is auto- > matically enabled unless the --usepkgonly option is > enabled. Behavior with > respect to changed build-time dependencies is controlled > by the --with-bdeps > option. > > But I haven't figured out what it means yet. In particular, what all > the stated implications mean. > This would be the option to ignore dependency mismatches of what the binary package claims its dependencies are (which you could see in $PKGDIR/Packages), and what the resolved dependencies are according to the *.ebuild file as portage is seeing it right now. Cheers Andreas
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 05:01:18 -0500 Dale wrote: > n952162 wrote: > > On 5/15/21 7:24 AM, Dan Egli wrote: > >> The R status means REBUILD. Usually, if it's an @world it's pulling > >> that in because something about that package changed and so it needs > >> to rebuild it. The --noreplace option would block that if portage > >> didn't think it was needed. Based on your options, I'd say that it's > >> probably a USE flag was changed. I don't use binpkgs myself, > >> preferring to compile except in certain circumstances (can we say > >> RUST!?) that I need to use a -bin variant. You can try without it, but > >> I recommend leaving your change-use and newuse flags in place and > >> letting the system rebuild xmodmap. > >> > >> > > Yes, thank you, but neither the server nor the client have any USE flags > > for that package defined. And the package has to be pretty stable by > > now ;-) > > > > > > > > > > All packages have USE flags defined somewhere even if you haven't > defined any yourself. Some are defined in profiles, some are defined > elsewhere. When I do updates, I see changes to USE flags all the time > that were changed by the profile, the maintainer in the ebuild or > somewhere else. After all, if a package doesn't have the USE flags > defined somewhere, emerge won't know what USE flags to include or > exclude support for. > > Dale > > :-) :-) > I t hink you are confusing enabled USE flags, with package USE flags. A package can have 0 USE flags (e.g. x11-apps/xmodmap, and many more). Enabled USE flags on the other hand are defined by user config files and profiles and by the package itself (i.e. they could be enabled by default). So there can very well be packages that have 0 USE flags, and xmodmap is one of them. The "problem" here is most probably a changed dependency. The dependencies (as defined in the ebuild) under which the package was built on the binhost have changed in the meantime in the ebuild file (without a revbump/version bump), and if the binhost has not enabled the flag "--changed-deps", it did not update the package to the new dependencies. If you really want to debug this, you could do a diff of the files /var/db/pkg/x11-apps/xmodmap-1.0.10/xmodmap-1.0.10.ebuild /usr/portage/x11-apps/xmodmap/xmodmap-1.0.10.ebuild (or whatever your portage root directory is, I'm still using /usr/portage). That diff should be on the binhost! Cheers Andreas
Re: [gentoo-user] What does emerge status R mean?
On Sun, 16 May 2021 12:49:26 +0200 n952162 wrote: > On 5/16/21 11:28 AM, Neil Bothwick wrote: > > On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: > > > There are no use flags defined for any of the packages I did a random > check for, either on the server or the client. I am worried that it > is as you say: that the ebuild has a change of USE flags, which, of > course, has nothing to do with me, the user. > >>> As already stated, any USE flag changes would appear in the emerge > >>> output, this is most likely caused by --changed-deps. Try with > >>> --changed-use but without --changed-deps to see. > >>> > >>> > >> I have introduced that into my build script. But, if it's as you say, > >> the one is a subset of the other, it should have no effect on the > >> output, right? > >> > > --changed-use is a subset of --newuse. --changed-deps is separate. > > > > > Ah, I oversaw that. > > Ah. why would I want to have --changed-deps anyway? That suddenly seems > silly. > > It's unfortunate, if there's no explanatory display if a package got > disqualified for that reason. > > If you want to have a binhost, then --changed-deps will become "necessary" at some point. Let me draw you a picture, where a binhost would fail to provide the correct package: - Binhost builds on day 1 package XYZ - computer that would merge with packages from binhost is NOT updated - the dependencies are changed on day 2 - Binhost does NOT rebuild, because you do not have --changed-deps enabled on day 2 - Computer that merges from the binhost is updated on day 2 but will NOT use the binary package from binhost, because the dependencies do not match There are flags to ignore dependency mismatches, but the default would just not use the binary package. Cheers Andreas
Re: [gentoo-user] Approx monthly hard lockups
On Wed, 12 May 2021 22:44:56 -0400 "Walter Dnes" wrote: > On Wed, May 12, 2021 at 11:16:56AM -0700, Mark Knecht wrote > > > > Is there nothing in the system logs? What's near the end before whatever > > you get from booting after this issue? > > Where would those logfiles be? "dmesg" starts off with... > > [0.00] Linux version 5.10.27-gentoo (root@i3) (gcc (Gentoo 10.2.0-r5 > p6) 10.2.0, GNU ld (Gentoo 2.34 p6) 2.34.0) #1 SMP Mon Apr 19 20:56:52 EDT > 2021 > [0.00] Command line: BOOT_IMAGE=Experimental ro root=801 noexec=on > net.ifnames=0 intel_pstate=disable ipv6.disable=1 > [0.00] x86/fpu: x87 FPU will use FXSAVE > [0.00] BIOS-provided physical RAM map: > > etc. This has happened with various kernels. Note that "Experimental" > is the latest kernel version. "Production" is the previous working > kernel I've compiled. It serves as a fallback in case I screw things up > on the "make menuconfig" step. It also saved me years ago on the switch > from /dev/hdx to /dev/sdx. > Maybe you can set in /etc/conf.d/bootmisc the variable previous_dmesg="YES" That should preserve the last dmesg after a reboot, i.e. /var/log/dmesg.old would be the file you want to look at after hard reset. Cheers Andreas
Re: [gentoo-user] Re: What is the best way forward?
On Thu, 25 Feb 2021 15:15:55 - (UTC) Grant Edwards wrote: > On 2021-02-25, hitachi303 wrote: > > > I found it to be helpful to de-install as many programs as possible > > before starting the update and the first emerge --sync. This reduces the > > amount of conflicts by a considerable amount. > > Yes, Definitely. If you can, uninstall anything "big" that you can > live without temporarily: LibreOffice, Chromium, Qt, KDE, X11, Gnome, > Cups, etc. > > Leave portage, sshd, Python, your init system, and GCC. > > > Stuff like libreoffice or thunderbird and so on and all of their > > dependencies. Everything your system does not need to run but what > > you need to be productive when you use your system. I use -av > > --depclean for this. > > Can't you, instead of uninstalling anything big, just start with the system set for the upgrade? emerge -auvDN @system Once the system set is updated you can assume of being in a rather sane state, where a world upgrade should just work(TM).
Re: [gentoo-user] [OT] Differences between wget and browser file retrieval?
On Thu, 14 Jan 2021 16:10:09 -0500 Jack wrote: > On 2021.01.14 15:49, Walter Dnes wrote: > > I'm bored, so I do a regular daily report at the DSL Reports > > "CanChat" > > sub-forum, on the Covid-19 case counts for Ontario, using provincial > > data. I download 2 files daily as source data. One of them is a PDF > > file, which is run through "pdftotext" and then parsed by a bash > > script > > (don't ask). Today, the command... > > > > wget https://files.ontario.ca/moh-covid-19-report-en-2021-01-14.pdf > > > > ...returns a zero-byte file. *BUT*, sticking the URL into the URL bar > > of Pale Moon and Google Chrome (and I assume Firefox/etc) brings up > > the > > PDF file just fine. Is "wget" being blocked? I have to do extra > > steps > > to get from the browser-invoked PDF to get the PDF file saved to the > > standard work area where my script expects it to be, so it can work > > its > > magic and parse out the daily breakdown by PHU (Public Health Unit). > > BTW, today's posts requiring the PDF file are... > > https://www.dslreports.com/forum/r33002718- > > https://www.dslreports.com/forum/r33002752- > > > > I've tried setting --user-agent= with my browser's string as shown > > by > > https://www.whatismybrowser.com/detect/what-is-my-user-agent but no > > luck. Is there some way to get around this? I have not updated this > > past week, so I don't think the problem is at my end. > > I just copy/pasted that wget command into my terminal, and it got me a > 1.7M PDF doc. I'm in the US, but I have no idea if location/IP is an > issue or not. > > Jack > I could download the file too with the wget command that you posted. If you still have trouble, you could try using curl and pretend that you're a firefox: curl 'https://files.ontario.ca/moh-covid-19-report-en-2021-01-14.pdf' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8' -H 'Accept-Language: en,de;q=0.7,en-US;q=0.3' --compressed -H 'DNT: 1' -H 'Connection: keep-alive' -H 'Upgrade-Insecure-Requests: 1' -H 'Pragma: no-cache' -H 'Cache-Control: no-cache' > moh-covid-19-report-en-2021-01-14.pdf Andreas
Re: [gentoo-user] Console scrollback
On Wed, 13 Jan 2021 10:55:18 + Peter Humphrey wrote: > On Wednesday, 13 January 2021 10:38:01 GMT Michael wrote: > > On Wednesday, 13 January 2021 10:30:19 GMT Peter Humphrey wrote: > > > Hello list, > > > > > > I see that the kernel code to scroll the console has been stripped out > > > [1]. What do people use instead? > > > > > > This loss is a nuisance while installing a new system, as I am still > > > trying to do on my old laptop. > > > > > > 1. https://soylentnews.org/article.pl?sid=20/09/15/1824233=rss > > > > A relief to see I'm not alone in experiencing this problem - I thought I had > > misconfigured something on my systems. :-) > > > > A way around it would be to use screen or tmux and use their internal > > buffer. However, if you're already logged in a console and suddenly want to > > Shift+PageUp, then it would be too late. This suggestion won't help if you > > want to look at the rc scripts output as the system boots, but you can > > capture these separately in syslog. > > It's a pain in the neck while trying to emerge a base system and being thrown > scores of lines of reasons why it can't be done, with the prime cause long > gone. I tried using "| tee 2>&1 > /tmp/file" and then viewing the file on > another vTTY, but there ought to be a neater way. > How about this (works with bash, not sure about other shells): emerge |& less This should work with all shells: emerge 2>&1 | less Cheers Andreas
Re: [gentoo-user] firefox automatic update???
Hmm, interesting that it shows not the full path on one machine. This
should always show you the full path:
for p in `pgrep firefox` ; do ls -lh /proc/${p}/exe ; done
You could also check with the following command what will be executed:
which firefox
Use `which -a firefox` to see all possible binaries that could be found
in $PATH.
The default is that /usr/bin/firefox is a bash script that would start
the real firefox binary at some point.
To list all packages that are installed matching firefox you could use
qlist -Iv firefox
qlist is part of the app-portage/portage-utils package.
Maybe that will help to see what is actually running on your system and
where it is installed.
On Thu, 12 Nov 2020
09:19:51 +0100 n952162 wrote:
> Ah, that is a good point ... assuming there's not an suid-updater
> squirreled away somewhere. I'm pretty sure that I've run firefox (lots)
> since last rebuilding it on the machine in question.
>
> Your test is good, but yields new questions:
>
> - machine 1:
>
> $ pgrep -a firefox
> *2829 /usr/lib64/firefox/firefox --name firefox -P default*
>
> $ pgrep -V
> pgrep from procps-ng 3.3.16
>
> - machine 2 (with automatic update):
>
> $ pgrep -a firefox
> *6355 firefox*
>
> $ pgrep -V
> pgrep from procps-ng 3.3.16
>
> In both cases, I start by just invoking "firefox" (no aliases)
>
>
>
> On 11/12/20 8:28 AM, Andreas Fink wrote:
> > On Thu, 12 Nov 2020 07:55:18 +0100
> > n952162 wrote:
> >
> >> I was just informed by firefox on one of my gentoo machines that firefox
> >> has updated, I need to restart.
> >>
> >> I no longer find an option to disable automatic update. Is there no hope?
> >>
> >> And do I have to go through another 18 hour firefox emerge to get rid of
> >> their "update"? Or is their binary sitting somewhere different from
> >> "our" binary?
> >>
> >> Oh! Can I just remove their binary and do a resume-emerge?
> >>
> >>
> > When firefox is updated via emerge while it is still running, this
> > update is recognised by the running instance and it will tell you that
> > firefox was updated and needs a restart. No automatic update happened
> > as you assume, it was all done by the package manager.
> > If you insist, you can check the binary that is currently running, and
> > you will most certainly find out that it is not writeable by your user
> > account, i.e. not by the user that is running firefox:
> > pgrep -a firefox
> >
> > Cheers
> > Andreas
> >
Re: [gentoo-user] firefox automatic update???
On Thu, 12 Nov 2020 07:55:18 +0100 n952162 wrote: > I was just informed by firefox on one of my gentoo machines that firefox > has updated, I need to restart. > > I no longer find an option to disable automatic update. Is there no hope? > > And do I have to go through another 18 hour firefox emerge to get rid of > their "update"? Or is their binary sitting somewhere different from > "our" binary? > > Oh! Can I just remove their binary and do a resume-emerge? > > When firefox is updated via emerge while it is still running, this update is recognised by the running instance and it will tell you that firefox was updated and needs a restart. No automatic update happened as you assume, it was all done by the package manager. If you insist, you can check the binary that is currently running, and you will most certainly find out that it is not writeable by your user account, i.e. not by the user that is running firefox: pgrep -a firefox Cheers Andreas
Re: [gentoo-user] tried desktop profile
On Tue, 13 Oct 2020 02:10:04 -0400 Jude DaShiell wrote: > x86_64-pc-linux-gnu-g++: fatal error: Killed signal terminated > program cc1plus compilation terminated. These two lines stongly suggest that you ran out of memory while compilation. You could try to build it with only one job (-j1), currently you are using -j2. Another option would be to buy more RAM ;) And last but not least, you could increase your swap memory, but be prepared that your system becomes unresponsive and compilation will probably take forever. Cheers Andreas
Re: [gentoo-user] binary packages: how to ...
On Wed, 15 Jul 2020 00:46:58 +0100 Ashley Dixon wrote: > On Tue, Jul 14, 2020 at 11:24:31PM +0200, n952162 wrote: > > binary packages: how to: > > > > 1. find out if a package is binary before you install it (e.g. where on > >app-arch/rar does it say it's a binary package) > > RAR is an unusual case, with both the "mirror" and "bindist" flags set in > the > RESTRICT variable (i.e., Gentoo cannot legally mirror the package, and > you're > not allowed to redistribute binaries either). I couldn't find anything in > the > ebuild which suggests it is a binary package; perhaps this is something > that > should be reviewed by the Gentoo developers, as most packages supporting > a > binary distribution provide a separate package with the `-bin` suffix, > although > I suppose this doesn't make much sense when there is no source package. > > The entire RAR business model of free decompression and paid compression > has > caused confusion for many people over many decades. I'd always stick to 7zip > or > one of the classic UNIX compression utilities, if I had a choice. > > > 2. inhibit their installation > > Don't install them. ;-) > > More seriously: there's not that many of them, so it's probably not a > process > worth automating, unless you're on a multi-user machine, in which > untrusted > users can install packages - although I think you'd have more > significant > problems at that point. As you've unfortunately discovered, there isn't much > of > a concrete framework in place to automatically detect binary packages, > which > also makes Point (3) difficult. > > > 3. get a list of the ones installed on a system > > `EIX_LIMIT=0 eix --only-names -I *-bin`, perhaps ? Unfortunately, this > won't > catch the unusual cases, as seen with `app-arch/rar`. > > > Any ideas about that are appreciated. > > [1] might be worth a read; it's quite comprehensive, and gives you a > glimpse > into the inner-workings of Portage, allowing you to fix these issues > yourself. > > Something to note: "bindist", as the USE-flag and RESTRICT option, does not > mean > "use a binary distribution", but rather "compile the package in such a way > that > I can redistribute my build without putting myself in a legal problem with > the > package authors" (this commonly is synonymous with disabling official > branding): > > $ ash-euses -sk bindist > > dev-libs/openssl:bindist - Disable/Restrict EC algorithms (as they seem to be > patented) -- note: changes the ABI > dev-libs/openssl-compat:bindist - Disable/Restrict EC algorithms (as they > seem to be patented) -- note: changes the ABI > dev-qt/qtnetwork:bindist - Disable EC support via dev-libs/openssl > mail-client/thunderbird:bindist - Disable official Firefox/Thunderbird > branding (icons, name) which are not binary-redistributable according to > upstream. > media-libs/freetype:bindist - Disable ClearType support (see > http://freetype.org/patents.html) > net-libs/liboauth:bindist - Alias for the nss USE flag, since there are > license compliancy trouble when using OpenSSL. > net-misc/openssh:bindist - Disable EC/RC5 algorithms in OpenSSL for patent > reasons. > sys-apps/ucspi-ssl:bindist - Disable EC/RC5 algorithms in OpenSSL for patent > reasons. > www-client/firefox:bindist - Disable official Firefox branding (icons, name) > which are not binary-redistributable according to upstream. > > Hope this helps, > Ashley. > > [1] https://wiki.gentoo.org/wiki/Binary_package_guide > Searching for -bin does not help to find binary only packages. Two more examples, which are binary only: zoom, skypeforlinux Searching for -bin mostly (if not always) implies that there would be a possibility to compile it from source. In my experience so far, every binary-only package does not have an open source license. So mostly you'll hit a license issue and you have to accept the license (/etc/portage/package.license) before you will be able to merge the package. Any license issue should start make you thinking what is going on, since it is a potential binary-only package. Installation of these packages is inhibited by emerge, because you have to accept the license first ;) When I look into my /etc/portage/package.license file I get a good idea of which packages are binary only. Not all of them are pure binary packages, but it is a superset as far as I can tell. To conclude: You cannot find out if a package is binary only with emerge. You have to do the research yourself, but /etc/portage/package.license is a good starting point to find potential candidates. Cheers Andreas
Re: [gentoo-user] WARNING: Do not update your system on ~amd64
On Wed, 17 Jun 2020 09:51:13 +0100 Peter Humphrey wrote: > On Wednesday, 17 June 2020 09:29:39 BST Neil Bothwick wrote: > > On Wed, 17 Jun 2020 07:34:41 +0200, Andreas Fink wrote: > > > I've noticed a problem with the current PAM update to > > > sys-libs/pam-1.4.0. > > > The update adds passwdqc USE to sys-auth/pambase, which pulls in > > > sys-auth/passwdqc. However sys-auth/passwdqc fails to build on my > > > system, and leaves me with an installed sys-libs/pam-1.4.0 which is > > > broken and does not allow any new login. > > > The end result is that sys-libs/pam-1.4.0 was successfully merged but > > > sys-auth/pambase will not be merged, due to a build failure in passwdqc. > > > Disabling the USE flag passwdqc for pambase allows an update to pambase > > > too, and logins work again. > > > This is a warning to anyone out there who updates daily and runs an > > > ~amd64. > > > > Thanks for the heads up. To play safe, I emerge passwdqc before emerging > > @world. It actually emerge without complaint on the three systems I > > tried. I also made sure I could SSH in after updating PAM before > > terminating the existing session. > > MAKEOPTS="-j1" emerge -1 passwdqc worked here. Sys-libs/pam had already > installed by the time passwdqc failed the first time. Sys-auth/pam is not in > my > update list, but sys-auth/pambase is, and has installed without protest. > Either USE="-passwdqc" for pambase or MAKEOPTS="-j1" for passwdqc works consistently for me too. I think you just need to make sure that pam+pambase are both updated before logging out ;) One system that I had to rescue from a live system + chroot :(
[gentoo-user] Warning: Do not update PAM on ~amd64
Hello, I've noticed a problem with the current PAM update to sys-libs/pam-1.4.0. The update adds passwdqc USE to sys-auth/pambase, which pulls in sys-auth/passwdqc. However sys-auth/passwdqc fails to build on my system, and leaves me with an installed sys-libs/pam-1.4.0 which is broken and does not allow any new login. The end result is that sys-libs/pam-1.4.0 was successfully merged but sys-auth/pambase will not be merged, due to a build failure in passwdqc. Disabling the USE flag passwdqc for pambase allows an update to pambase too, and logins work again. This is a warning to anyone out there who updates daily and runs an ~amd64. One system that I updated and restarted, I cannot login to it anymore (or ssh into it). Another system that I updated and currently am writing from, I'm still logged in after the broken update. and I can see the following error message (before disabling the USE flag passwdqc for the package pambase): PAM unable to dlopen(/lib64/security/pam_cracklib.so): /lib64/security/pam_cracklib.so: cannot open shared object file: No such file or directory PAM adding faulty module: /lib64/security/pam_cracklib.so After doing a USE=-passwdqc emerge -a1 pambase the error messages disappear from the system logs and I am able to login to my machine again. However if you reboot with the broken state you will have a hard time updating it, since you cannot login to your machine anymore and need a chroot from a live system. The bug report for passwdqc is here: https://bugs.gentoo.org/728528 Cheers Andreas
[gentoo-user] WARNING: Do not update your system on ~amd64
Hello, I've noticed a problem with the current PAM update to sys-libs/pam-1.4.0. The update adds passwdqc USE to sys-auth/pambase, which pulls in sys-auth/passwdqc. However sys-auth/passwdqc fails to build on my system, and leaves me with an installed sys-libs/pam-1.4.0 which is broken and does not allow any new login. The end result is that sys-libs/pam-1.4.0 was successfully merged but sys-auth/pambase will not be merged, due to a build failure in passwdqc. Disabling the USE flag passwdqc for pambase allows an update to pambase too, and logins work again. This is a warning to anyone out there who updates daily and runs an ~amd64. One system that I updated and restarted, I cannot login to it anymore (or ssh into it). Another system that I updated and currently am writing from, I'm still logged in after the broken update. and I can see the following error message (before disabling the USE flag passwdqc for the package pambase): PAM unable to dlopen(/lib64/security/pam_cracklib.so): /lib64/security/pam_cracklib.so: cannot open shared object file: No such file or directory PAM adding faulty module: /lib64/security/pam_cracklib.so After doing a USE=-passwdqc emerge -a1 pambase the error messages disappear from the system logs and I am able to login to my machine again. However if you reboot with the broken state you will have a hard time updating it, since you cannot login to your machine anymore and need a chroot from a live system. The bug report for passwdqc is here: https://bugs.gentoo.org/728528 Cheers Andreas
Re: [gentoo-user] emerge stuck after dovecot upgrade
On Thu, 21 May 2020 12:54:49 +0100
Neil Bothwick wrote:
> On Thu, 21 May 2020 11:20:18 +0100, Neil Bothwick wrote:
>
> > On Thu, 21 May 2020 06:44:35 +0200, Andreas Fink wrote:
> >
> > > recently emerge started to get stuck after an upgrade of dovecot, and
> > > it is somehow related to my /etc/portage/bashrc, which has the
> > > following content: function post_pkg_postinst() {
> > > if test "$CATEGORY/$PN" = "dev-db/mariadb"; then
> > > /etc/init.d/mysql status && /etc/init.d/mysql restart
> > > elif test "$CATEGORY/$PN" = "www-servers/apache"; then
> > > /etc/init.d/apache2 status && /etc/init.d/apache2 restart
> > > elif test "$CATEGORY/$PN" = "net-mail/dovecot"; then
> > > /etc/init.d/dovecot status && /etc/init.d/dovecot restart
> > > echo 'going to sleep'
> > > sleep 5
> > > echo 'finished sleeping'
> > > elif test "$CATEGORY/$PN" = "mail-mta/postfix"; then
> > > /etc/init.d/postfix status && /etc/init.d/postfix restart
> > > elif test "$CATEGORY/$PN" = "net-misc/openssh"; then
> > > /etc/init.d/sshd status && /etc/init.d/sshd restart
> > > fi
> > > }
> > >
> > >
> > > I restart dovecot after an upgrade, in the same way as I restart e.g.
> > > postfix. However for dovecot emerge gets stuck and does not continue
> > > and is sitting there quietly (killable only via `pkill -9 emerge`).
> >
> > I can confirm this. I tried your bashrc (nice idea by the way, I
> > normally manually run needrestart after an update) and the dovecot
> > install completed but then hung. The next step is to add set +x to
> > bashrc to see where the hang occurs.
>
> It seems the final echo is executed, but then the function doesn't exit
> for some reason. I tried rewriting it using case, which looks cleaner to
> me but fails in the same way.
>
>
> function post_pkg_postinst() {
> set +x
> case "$CATEGORY/$PN" in
> "net-mail/dovecot")
> /etc/init.d/dovecot status && /etc/init.d/dovecot
> restart
> echo 'going to sleep'
> sleep 5
> echo 'finished sleeping'
> ;;
>
> "mail-mta/postfix")
> /etc/init.d/postfix status && /etc/init.d/postfix
> restart
> ;;
> esac
> }
>
>
I do not think that it is stuck in the bashrc itself, but something that
happens in the
bashrc makes the emerge python process not realizing that everything finished.
These are
the interesting running processes after the command
`ebuild /usr/portage/net-mail/dovecot/dovecot-2.3.10.1.ebuild qmerge`
gets stuck (I cannot see any bash still running, that's why I assume that the
bashrc itself finishes):
root 5281 2.0 0.7 71060 63412 pts/0SN+ 16:19 0:01
/usr/bin/python3.7 -b /usr/lib/python-exec/python3.7/ebuild
/usr/portage/net-mail/dovecot/dovecot-2.3.10.1.ebuild qmerge
root 5286 8.5 0.0 0 0 pts/0ZN+ 16:19 0:06 [ebuild]
root 5869 0.0 0.0 4284 2388 ?SNs 16:19 0:00
/usr/sbin/dovecot -c /etc/dovecot/dovecot.conf
root 5876 0.0 0.0 4152 2620 ?SN 16:19 0:00 dovecot/log
root 5879 0.0 0.0 6236 4568 ?SN 16:19 0:00 dovecot/config
root 5883 0.0 0.0 19632 8048 ?SN 16:19 0:00 dovecot/auth
Cheers
Andreas
[gentoo-user] emerge stuck after dovecot upgrade
Hello,
recently emerge started to get stuck after an upgrade of dovecot, and it is
somehow
related to my /etc/portage/bashrc, which has the following content:
function post_pkg_postinst() {
if test "$CATEGORY/$PN" = "dev-db/mariadb"; then
/etc/init.d/mysql status && /etc/init.d/mysql restart
elif test "$CATEGORY/$PN" = "www-servers/apache"; then
/etc/init.d/apache2 status && /etc/init.d/apache2 restart
elif test "$CATEGORY/$PN" = "net-mail/dovecot"; then
/etc/init.d/dovecot status && /etc/init.d/dovecot restart
echo 'going to sleep'
sleep 5
echo 'finished sleeping'
elif test "$CATEGORY/$PN" = "mail-mta/postfix"; then
/etc/init.d/postfix status && /etc/init.d/postfix restart
elif test "$CATEGORY/$PN" = "net-misc/openssh"; then
/etc/init.d/sshd status && /etc/init.d/sshd restart
fi
}
I restart dovecot after an upgrade, in the same way as I restart e.g. postfix.
However
for dovecot emerge gets stuck and does not continue and is sitting there quietly
(killable only via `pkill -9 emerge`). These are the last lines in my
/var/log/emerge.log:
1590023821: === (17 of 26) Post-Build Cleaning
(net-dns/bind-tools-9.16.3::/usr/portage/net-dns/bind-tools/bind-tools-9.16.3.ebuild)
1590023821: ::: completed emerge (17 of 26) net-dns/bind-tools-9.16.3 to /
1590023821: >>> emerge (18 of 26) net-mail/dovecot-2.3.10.1 to /
1590023821: === (18 of 26) Cleaning
(net-mail/dovecot-2.3.10.1::/usr/portage/net-mail/dovecot/dovecot-2.3.10.1.ebuild)
1590023821: === (18 of 26) Compiling/Packaging
(net-mail/dovecot-2.3.10.1::/usr/portage/net-mail/dovecot/dovecot-2.3.10.1.ebuild)
1590024325: === (18 of 26) Merging
(net-mail/dovecot-2.3.10.1::/usr/portage/net-mail/dovecot/dovecot-2.3.10.1.ebuild)
1590024331: >>> AUTOCLEAN: net-mail/dovecot:0
1590024331: === Unmerging... (net-mail/dovecot-2.3.10)
1590024334: >>> unmerge success: net-mail/dovecot-2.3.10
So it is missing the "Post-Build Cleaning" and the "completed emerge" line for
dovecot.
Lokking into the temporary build directory of portage I can see see only a
single file
being left (PORTAGE_TMPDIR="/home/portage/tmp):
/home/portage/tmp/portage/net-mail/.dovecot-2.3.10.1.portage_lockfile
There are no build artifacts left, it's clean and empty, only the lockfile is
still there.
Restarting the upgrade process with `emerge -auvDN @world` wouldn't retry to
upgrade
dovecot, so I guess it actually got merged and registered as being successfully
merged.
I'm kind of lost, why upgrading dovecot gets emerge stuck, but upgrading e.g.
openssh or
postfix works correctly and the services are being restarted the same way as
dovecot in
/etc/portage/bashrc.
One last note, doing the merge manually with the commands
ebuild /path/to/dovecot.ebuild compile
ebuild /path/to/dovecot.ebuild install
ebuild /path/to/dovecot.ebuild qmerge
will get stuck in the qmerge step, but it is killable with a regular
SIGINT/SIGTERM.
Any ideas how I can debug this any further? I assume that emerge is waiting for
some
children and the forking in dovecot is different than in openssh, but I'm
unsure how I
can debug this. I even tried to background everything like this:
/etc/init.d/dovecot status && ( ( bash -c '/etc/init.d/dovecot restart &' )
& )
The last successful full upgrade of dovecot was
2020-03-21T14:06:21 >>> net-mail/dovecot-2.3.10: 7 minutes, 15 seconds
The first failed full merge was on April 30th and last night again.
After that portage has been updated to these versions:
2020-03-21T11:15:55 >>> sys-apps/portage-2.3.94: 48 seconds
2020-03-23T18:30:34 >>> sys-apps/portage-2.3.95: 56 seconds
2020-03-26T05:37:17 >>> sys-apps/portage-2.3.96-r1: 47 seconds
2020-03-28T04:23:23 >>> sys-apps/portage-2.3.96-r1: 43 seconds
2020-04-09T10:00:41 >>> sys-apps/portage-2.3.97: 48 seconds
2020-04-11T09:39:30 >>> sys-apps/portage-2.3.98-r1: 43 seconds
2020-04-13T07:05:40 >>> sys-apps/portage-2.3.99-r1: 48 seconds
2020-04-22T03:15:44 >>> sys-apps/portage-2.3.99-r2: 44 seconds
2020-05-01T03:50:56 >>> sys-apps/portage-2.3.99-r2: 57 seconds
2020-05-07T13:44:14 >>> sys-apps/portage-2.3.99-r2: 42 seconds
Any help is appreciated :)
Cheers
Andreas
Re: [gentoo-user] davfs2 suddenly not working properly
On Tue, 07 May 2019 02:25:13 -0400
John Covici wrote:
> On Tue, 07 May 2019 01:58:25 -0400,
> Andreas Fink wrote:
> >
> > On Thu, 18 Apr 2019 10:14:13 -0400
> > John Covici wrote:
> >
> > > On Thu, 18 Apr 2019 03:20:25 -0400,
> > > Neil Bothwick wrote:
> > > >
> > > > [1 ]
> > > > On Wed, 17 Apr 2019 21:41:41 -0400, John Covici wrote:
> > > >
> > > > > Apr 17 18:39:55 ccs.covici.com systemd-coredump[5334]: Process
> > > > > 5332 (umount.davfs) of user 0 dumped core.
> > > > > Apr 17 18:39:55 ccs.covici.com systemd[1]:
> > > > > systemd-coredump@0-5333-0.service: Succeeded.
> > > > >
> > > > > I can't find that coredump, not sure if the process is allowed to
> > > > > do it.
> > > >
> > > > From the systemd-coredump man page:
> > > >
> > > > By default, systemd-coredump will log the core dump including a
> > > > backtrace if possible to the journal and store the core dump itself
> > > > in an external file in /var/lib/systemd/coredump.
> > > >
> > > > You can change this in /etc/systemd/coredump.conf
> > >
> > > Thanks, I found it, but the backtrace has no symbols, even though I
> > > have features set so that everything is compiled with symbols like
> > > this:
> > > FEATURES="${FEATURES} -stricter -distcc -ccache splitdebug buildpkg"
> > > I wonder what is happening here?
> > >
> > > Strange thing si I have seen nothing on bgo for this problem.
> > >
> >
> > I have the same problem on one of my machines. It segfaults somewhere
> > in strcmp with avx2 according to a backtrace.
> > Will try rebuilding my system libraries, since I changed lately from
> > "march=native" to "march=x86-64 mtune=generic". I thought I rebuilt
> > everything but there might be something missing for me.
> > Anyway, for me as a workaround this works: fusermount -u MOUNTPOINT
>
> OK, I will try that and see if it works.
>
> Thanks.
>
I was debugging the issue today, and it's a bug in davfs2 as it seems...
Line 151-153 in src/umount_davfs.c reads the following:
char *pid = NULL;
FILE *file = fopen(pidfile, "r");
if (!file || fscanf(file, "%a[0-9]", ) != 1 || !pid) {
This is something I don't even understand what it is supposed to do, because
there is so
much wrong with it...
%a would read a floating point (we all know, PID's are floating points...)
The [0-9] is completely useless there..
The result is being saved in a char*...
You could write it like this:
char pid[32];
FILE *file = fopen(pidfile, "r");
if (!file || fscanf(file, "%s", pid) != 1) {
This would fix the segmentation fault.
And now the funny part: I wanted to report a bug, so I went to the website and
wanted to
see in the source code repository when this bug was introduced. However in the
source
code repository there is a correct implementation (similar to mine, actually
more safe
than mine) BUT any released version I tested from 1.4.7 until 1.5.5 all have
this wrong
implementation 1.4.7 was released in 2012, and the file src/umount_davfs.c
wasn't changed
since 2 years according to the repository browser.
How the releases are correlating with the source code browser is at the moment
beyound my
understanding of this project.
Anyone in contact with the development team of davfs2, who could shed some
light on the
situation?
Cheers
Andreas
Re: [gentoo-user] davfs2 suddenly not working properly
On Thu, 18 Apr 2019 10:14:13 -0400
John Covici wrote:
> On Thu, 18 Apr 2019 03:20:25 -0400,
> Neil Bothwick wrote:
> >
> > [1 ]
> > On Wed, 17 Apr 2019 21:41:41 -0400, John Covici wrote:
> >
> > > Apr 17 18:39:55 ccs.covici.com systemd-coredump[5334]: Process
> > > 5332 (umount.davfs) of user 0 dumped core.
> > > Apr 17 18:39:55 ccs.covici.com systemd[1]:
> > > systemd-coredump@0-5333-0.service: Succeeded.
> > >
> > > I can't find that coredump, not sure if the process is allowed to
> > > do it.
> >
> > From the systemd-coredump man page:
> >
> > By default, systemd-coredump will log the core dump including a
> > backtrace if possible to the journal and store the core dump itself
> > in an external file in /var/lib/systemd/coredump.
> >
> > You can change this in /etc/systemd/coredump.conf
>
> Thanks, I found it, but the backtrace has no symbols, even though I
> have features set so that everything is compiled with symbols like
> this:
> FEATURES="${FEATURES} -stricter -distcc -ccache splitdebug buildpkg"
> I wonder what is happening here?
>
> Strange thing si I have seen nothing on bgo for this problem.
>
I have the same problem on one of my machines. It segfaults somewhere
in strcmp with avx2 according to a backtrace.
Will try rebuilding my system libraries, since I changed lately from
"march=native" to "march=x86-64 mtune=generic". I thought I rebuilt
everything but there might be something missing for me.
Anyway, for me as a workaround this works: fusermount -u MOUNTPOINT
Cheers
Andreas
Re: [gentoo-user] NVM on Gentoo Linux?
On Sun, 31 Mar 2019 11:53:19 +0100 Wols Lists wrote: > If I'm booting off a live-CD or similar, then I'm not worried about the > system being available for use, and streaming the data at a level BELOW > the file system is far more efficient and quicker. It's only faster if your disk is almost fully used. If you have a lot of free disk space your method is doing a dumb clone of unused space. So it's argueable which method is faster ;) Your method neither allows changing of partition sizes nor a change on the underlying filesystems. Maybe it's worth thinking about about another filesystem, when you switch from classic HDD to SSD. Cheers Andreas
Re: [gentoo-user] NVM on Gentoo Linux?
On Sun, 31 Mar 2019 08:38:43 +0100 Wols Lists wrote: > I'm planning to migrate my system soon, but I'm going to do that a bit > differently. I'll dd my home partition across (I've got hard-links > galore, so a cp or rsync or whatever will have massive conniptions). What's wrong with an "rsync -aH"? This preserves hard links (given that the target system supports them. I honestly don't think that a dd is necessary. I have copied several times from one harddisk to another with different harddis partition sizes, but with enough free space on the target. I do the copying by booting a live usb stick, then I mount the source and the target partitions, and issue the rsync command (If you need extended attributes to be synced too, then there is an option for rsync too, e.g. ACL). rsync -aH --numeric-ids /path/to/source /path/to/target/ Cheers Andreas
[gentoo-user] kworker using 100% cpu
Hello, I have a problem which uses 100% of one cpu core on my HP-15-bs114ng notebook. I figured out already that it is somehow related to ACPI interrupts, since the following command will return the system to normal: echo disable > /sys/firmware/acpi/interrupts/gpe16 The content of this "file" is the following: 3749821 STS disabled unmasked The first column is the number of interrupts, that happened, which is very high, hence the 100% cpu usage in one kworker process. My question would be the following now: 1. What could be the side effects of disabling this interrupt? 2. What could trigger the interrupt? 3. How can this be debugged further and reported, i.e. who would be able to fix it? (This happens on all kernels, since I have the notebook, i.e. >= 4.17) Cheers Andreas
Re: [gentoo-user] chromium-72.0.3626.96 and Java
On Fri, 15 Feb 2019 09:32:15 + Mick wrote: > On Thursday, 14 February 2019 12:36:04 GMT Mick wrote: > > On Thursday, 14 February 2019 12:27:25 GMT Marc Joliet wrote: > > > Am Donnerstag, 14. Februar 2019, 13:12:29 CET schrieb Mick: > > > > Hi All, > > > > > > > > I just noticed chromium-72.0.3626.96 is bringing in Java > > > > packages as dependencies, I'd rather keep off my systems. This > > > > is caused by the new USE flag closure-compile, which I think is > > > > advertised as a good thing. > > > > > > > > Would you know if these Java dependencies are used for chromium > > > > build-time > > > > only and therefore I could unmerge them thereafter, or if they > > > > are for run- > > > > time? > > > > > > The relevant dep is in BDEPEND [0], so yes, you should be able to > > > unmerge them afterwards: > > > > > > BDEPEND=" > > > > > > # snip other deps > > > closure-compile? ( virtual/jre ) > > > > Of course! Why was I searching for 'java' ... O_o > > > > > virtual/pkgconfig > > > > > > " > > > > > > [0] I was going to refer to ebuild(5), but it's currently not > > > documented there (see bug #674932), however you can find a > > > definition in the PMS at [1]. [1] > > > https://projects.gentoo.org/pms/7/pms.html#x1-680008.1 > > > > > > HTH > > > > Thank you Marc, I'll carry on with the emerge now. > > Hmm ... sadly it is not the case that I can remove all java packages > thereafter. When chromium-72.0.3626.96 is emerged with the default > new setting of USE="closure-compile" java seems to be necessary: > > # emerge --depclean -v -a sys-apps/baselayout-java > app-eselect/eselect-java dev-java/java-config dev-java/icedtea-bin > virtual/jdk virtual/jre dev-java/ icedtea-web > > Calculating dependencies... done! > app-eselect/eselect-java-0.4.0 pulled in by: > dev-java/icedtea-bin-3.10.0-r1 requires > >=app-eselect/eselect-java-0.4.0 dev-java/icedtea-web-1.6.2 requires > >>=app-eselect/eselect-java-0.2.0 > > dev-java/icedtea-bin-3.10.0-r1 pulled in by: > virtual/jdk-1.8.0-r3 requires dev-java/icedtea-bin:8 > > dev-java/icedtea-web-1.6.2 pulled in by: > dev-java/icedtea-bin-3.10.0-r1 requires > >=dev-java/icedtea-web-1.6.1:0 > > dev-java/java-config-2.2.0-r4 pulled in by: > dev-java/icedtea-bin-3.10.0-r1 requires > >=dev-java/java-config-2.2.0-r3 dev-java/icedtea-web-1.6.2 requires > >>=dev-java/java-config-2.2.0-r3 > > sys-apps/baselayout-java-0.1.0 pulled in by: > dev-java/java-config-2.2.0-r4 requires sys-apps/baselayout-java > > virtual/jdk-1.8.0-r3 pulled in by: > dev-java/icedtea-web-1.6.2 requires >=virtual/jdk-1.7, > =virtual/jdk-1.8.0- r3 > virtual/jre-1.8.0-r1 requires virtual/jdk:1.8, > =virtual/jdk-1.8.0-r3 > > virtual/jre-1.8.0-r1 pulled in by: > dev-java/icedtea-web-1.6.2 requires >=virtual/jre-1.7, > =virtual/jre-1.8.0- r1 > www-client/chromium-72.0.3626.96 requires =virtual/jre-1.8.0-r1, > virtual/ jre > > >>> No packages selected for removal by depclean > Packages installed: 1231 > Packages in world:111 > Packages in system: 43 > Required packages:1231 > Number removed: 0 > > Am I interpreting the above output correctly? > That's because depclean sets --with-bdeps=y by default, i.e. build dependencies are considered to be crucial to the system. If you update your depclean command and add the flag --with-bdeps=n it should allow you to unmerge java again. Cheers Andreas
Re: [gentoo-user] RAM checks for chromium
On Fri, 07 Dec 2018 10:14:45 + Peter Humphrey wrote: > And today, of course, there's an upgrade. That's another reason I > ditched it. Is there a way to force chromium to be not ~amd64 on a > ~amd64 system? Yes, I do that with this entry in /etc/portage/package.keywords: www-client/chromium -~amd64 Cheers Andreas
Re: [gentoo-user] emerge completly a package but dont install it?
On Wed, 8 Aug 2018 19:12:37 +0200 tu...@posteo.de wrote: > Hi, > > is it possible to go through process of installing a not-installed > package from source to executable ... without actually install the > package - so the system as such is not touched? > > Cheers > Meino > > > You can use ebuild for that. The commands to build without merging would be ebuild /usr/portage/my-package/my-ebuild-file.ebuild install This will download, unpack, build, and install the package into your temporary portage build directory (usually /var/tmp/portage). It will not resolve any dependencies though, this has to be done beforehand. The temporary install directory is called "image" in the temporary directory. You can also go through the whole process step by step, ebuild /usr/portage/my-package/my-ebuild-file.ebuild unpack ebuild /usr/portage/my-package/my-ebuild-file.ebuild compile ebuild /usr/portage/my-package/my-ebuild-file.ebuild install ebuild /usr/portage/my-package/my-ebuild-file.ebuild qmerge ebuild /usr/portage/my-package/my-ebuild-file.ebuild clean the qmerge command will install it into your system, so this is the step, that you do not want to execute ;) Cheers Andreas
Re: [gentoo-user] Multiboot USB - GRUB2 loop device
On Fri, 13 Jul 2018 21:14:07 -0500
Alex Luehm wrote:
> Hello all
>
> I've recently taken it upon myself to create a multiboot USB with isos
> that I tend to frequently use. So far I've been successful in adding
> Clonezilla and the Archlinux live ISOs. I've attempted to add the Gentoo
> install ISO in a similar manner (helped with the grub config within the
> iso itself but can't seem to get GRUB to recogonize the image. My
> DuckDuckGo-foo has returned useless results (a near hit, yet useless
> inquiry being found here:
> https://forums.gentoo.org/viewtopic-p-6527390.html).
>
> My current GRUB menu entry is as follows:
>
> menuentry '[loopback]gentoo amd64' {
> set isofile='/isos/gentoo.iso'
> echo "isofile set"
> loopback loop $isofile
> echo "loopback set"
> linux (loop)/isolinux/gentoo64 root=/dev/ram0 init=/linuxrc
> dokeymap looptype=squashfs loop=/image.squashfs cdroot cdboot
> initrd=gentoo64.xz
> initrd (loop)/isolinux/gentoo64.xz
> }
>
> When booting, I receive the following message:
>
> isofile set
> loopback set
> error: attempt to read or write outside of disk 'loop'
> error: you need to load the kernel first
>
> Thanks in advance!
>
Hello,
I have the following entry to load gentoo from a multiboot USB stick:
menuentry 'gentoo livecd' --id 'gentoolive' {
if test x$grub_platform = xpc; then linux_suffix=16; else linux_suffix= ;
fi
set root='hd1,gpt3'
search --no-floppy --fs-uuid --set=root 6720-75AD
linux$linux_suffix /gentoo/isolinux/gentoo root=/dev/ram0 init=/linuxrc
dokeymap looptype=squashfs subdir=gentoo loop=/gentoo/image.squashfs cdroot
initrd=gentoo.igz vga=791 passwd=myCoolSshPassword dosshd
initrd$linux_suffix /gentoo/isolinux/gentoo.igz
}
I think you need the `subdir` magic here. It's not the same setup as you have.
I just
unpacked each iso into a subdirectory (and as you can guess, gentoo is unpacked
in the
gentoo subdirectory). I do not know, but maybe you can give it a shot with
`subdir=(loop)`. Also the files are called on my bootstick gentoo and not
gentoo64, but
my version is also already 1 year old ;)
Cheers
Andreas
Re: [gentoo-user] PYTHON_SINGLE_TARGET inconsistent?
On Sat, 7 Jul 2018 21:51:31 +0300
Franz Fellner wrote:
> It's not automatically doing magic but using things specified in the
> profile. In this case look at ${PORTDIR}/profile/base/package.use
> Setting PYTHON_SINGLE_TARGET (which is expanded to those USEFlags) in your
> make.conf will shadow those from the profile and spit out an error.
>
> 2018-07-07 21:45 GMT+03:00 Vadim A. Misbakh-Soloviov :
>
> > The package you're referring to have only support of python2 interpreters
> > (python2_7 (CPython) and pypy (not the pypy3)).
> >
> > It seems, by default (if neither of PYTHON_SINGLE_TARGET is set), portage
> > tries to do the "magic" (well, in my opinion, it opposes to the Gentoo
> > Philosophy, and it should throw the same error even with "defaults") and
> > automatically chooses the 2_7 single target for it.
> >
> > But when you explicitly specify the targets in make.conf, it obeys and
> > don't
> > do that magic anymore, so condition of "exactly one of supported
> > single_targets (pypy, pyhton2.7)" is not meeting anymore".
> >
> > That's why you getting the error.
> >
> > В письме от суббота, 7 июля 2018 г. 21:31:48 MSK пользователь Andreas Fink
> > написал:
> > > Hello,
> > > I have a question considering PYTHON_SINGLE_TARGET because it seems to
> > > behave inconsistently on my system and I cannot find any documentation
> > > about it, that would guide me in the right direction how to fix it.
> > > Running emerge --info I see the following (I'm on ~amd64):
> > > ... PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7
> > python3_5"
> > > ...
> > >
> > > This output is the default for ~amd64, neither PYTHON_SINGLE_TARGET nor
> > > PYTHON_TARGETS has been set explicitly.
> > > If I do an emerge -av asciidoc, I see the following output:
> > > ebuild R] app-text/asciidoc-8.6.10::gentoo USE="-examples
> > -graphviz
> > > -highlight {-test}" PYTHON_SINGLE_TARGET="python2_7 -pypy"
> > > PYTHON_TARGETS="python2_7 -pypy"
> > >
> > > Setting PYTHON_SINGLE_TARGET and PYTHON_TARGETS in /etc/portage/make.conf
> > > explicitly to: PYTHON_SINGLE_TARGET="python3_5"
> > > PYTHON_TARGETS="python2_7 python3_5"
> > >
> > > Now emerge --info doesn't show any difference. It's still the same
> > output.
> > > Doing an emerge -av asciidoc I get now this output:
> > > !!! The ebuild selected to satisfy "asciidoc" has unmet requirements.
> > > - app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight
> > > -test" ABI_X86="(64)" PYTHON_SINGLE_TARGET="-pypy -python2_7"
> > > PYTHON_TARGETS="python2_7 -pypy"
> > >
> > > The following REQUIRED_USE flag constraints are unsatisfied:
> > > exactly-one-of ( python_single_target_pypy
> > > python_single_target_python2_7 )
> > >
> > >
> > > This seems for me to be really inconsistent, considering the fact that we
> > > usually request users to provide an emerge --info, which wouldn't show
> > any
> > > difference.
> > > Why am I able to merge in the first case the package, but in the second
> > case
> > > I get an error? I really cannot understand where the
> > > python_single_target_python2_7 is set in the first case.
> > > Anyone who has more insight into that case?
> > >
> > > Cheers
> > > Andreas
> >
> >
> >
> >
> >
> >
That was the file I was looking for. Thank you :)
[gentoo-user] PYTHON_SINGLE_TARGET inconsistent?
Hello,
I have a question considering PYTHON_SINGLE_TARGET because it seems to behave
inconsistently on my system and I cannot find any documentation about it, that
would
guide me in the right direction how to fix it.
Running emerge --info I see the following (I'm on ~amd64):
... PYTHON_SINGLE_TARGET="python3_5" PYTHON_TARGETS="python2_7 python3_5" ...
This output is the default for ~amd64, neither PYTHON_SINGLE_TARGET nor
PYTHON_TARGETS
has been set explicitly.
If I do an emerge -av asciidoc, I see the following output:
ebuild R] app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz
-highlight {-test}" PYTHON_SINGLE_TARGET="python2_7 -pypy"
PYTHON_TARGETS="python2_7 -pypy"
Setting PYTHON_SINGLE_TARGET and PYTHON_TARGETS in /etc/portage/make.conf
explicitly to:
PYTHON_SINGLE_TARGET="python3_5"
PYTHON_TARGETS="python2_7 python3_5"
Now emerge --info doesn't show any difference. It's still the same output.
Doing an emerge -av asciidoc I get now this output:
!!! The ebuild selected to satisfy "asciidoc" has unmet requirements.
- app-text/asciidoc-8.6.10::gentoo USE="-examples -graphviz -highlight -test"
ABI_X86="(64)" PYTHON_SINGLE_TARGET="-pypy -python2_7"
PYTHON_TARGETS="python2_7 -pypy"
The following REQUIRED_USE flag constraints are unsatisfied:
exactly-one-of ( python_single_target_pypy python_single_target_python2_7 )
This seems for me to be really inconsistent, considering the fact that we
usually request users to provide an emerge --info,
which wouldn't show any difference.
Why am I able to merge in the first case the package, but in the second case I
get an
error? I really cannot understand where the python_single_target_python2_7 is
set in the
first case.
Anyone who has more insight into that case?
Cheers
Andreas
