[gentoo-user] ruby and package.use
It seems like ruby regularly wants to stuff ruby_targets_rebyNN entries into package.use on my machines - is this normal? Now that ruby3 is out it wants to add a bunch of ruby_targets_ruby30 entries to the ruby_targets_ruby27 crud that's already there.
Re: [gentoo-user] xf86OpenConsole: Cannot open virtual console 1 (Permission denied)
On 2/9/21 5:04 PM, the...@sys-concept.com wrote: On 2/8/21 9:59 PM, the...@sys-concept.com wrote: On 2/8/21 9:44 PM, cal wrote: [snip] When I'm directly in front of the PC and I have a log-in screen and type user ID + passwords I was under impression that "startxfce4" would run automatically when from .xinitrc ~/.xinitrc exec startxfce4 but it doesn't, when I log-in the XFCE4 is not starting automatically, I have to type manually: startxfce4 I see you have already solved your problem. But it bears mentioning: .xinitrc is executed by runing `startx`, not by the login shell. I see, so instead of going around and calling .xinitrc from .bash_profile why not call startxfce4 directly from .bash_profile Instead of: if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then exec startx; fi start as: if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then exec startxfce4; fi It should work. With the above setup starting "startxfce4" from .bash_profile, I get an error when ssh: "No xauth data; using fake authentication data for X11 forwarding." This error does not show up when "startxfce4" is run from .xinitrc I don't know what difference it makes how xfce4 is started. startx does some additional work besides just running the .xinitrc script. If you are not using a display manager, startx is the correct way to start X, with .xinitrc containing the commands to launch your window manager. My .xinitrc: if [ -d /etc/X11/xinit/xinitrc.d ]; then for f in /etc/X11/xinit/xinitrc.d/*; do [ -x "$f" ] && . "$f" done unset f fi exec dbus-launch --exit-with-session i3
Re: [gentoo-user] xf86OpenConsole: Cannot open virtual console 1 (Permission denied)
On 2/8/21 9:59 PM, the...@sys-concept.com wrote: > On 2/8/21 9:44 PM, cal wrote: > [snip] >>> >>> When I'm directly in front of the PC and I have a log-in screen and type >>> user ID + passwords >>> I was under impression that "startxfce4" would run automatically when from >>> .xinitrc >>> ~/.xinitrc >>> exec startxfce4 >>> >>> but it doesn't, when I log-in the XFCE4 is not starting automatically, I >>> have to type manually: startxfce4 >>> >> I see you have already solved your problem. But it bears mentioning: >> .xinitrc is executed by runing `startx`, not by the login shell. > > I see, so instead of going around and calling .xinitrc from .bash_profile > > why not call startxfce4 directly from .bash_profile > > Instead of: > if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then exec startx; fi > > start as: > if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then exec startxfce4; fi > > It should work. With the above setup starting "startxfce4" from .bash_profile, I get an error when ssh: "No xauth data; using fake authentication data for X11 forwarding." This error does not show up when "startxfce4" is run from .xinitrc I don't know what difference it makes how xfce4 is started.
[gentoo-user] apache 2.4 - .htaccess IP's limit
Does apache 2.4 have a limit of how many individual entries like: " Require not ip xxx.xxx.xxx.xx" I can have in Apache .htaccess file? I have over 500-subnets and I've notices some IP's are being blocked even though they are not on the list.
Re: [gentoo-user] Sharing printers via Cups
On 2/9/2021 3:20 AM, Michael wrote: Actually tried that. Got LPD installed, sent a test page. Test page appeared in the Windows Queue, then disappeared without any acknowledgement from the printer. This would need some troubleshooting/configuring on the Windows end. It's a long time ago I tried this and don't recall what I had configured to allow clients to print via the Windows PC. It was relatively simple and lightweight though, unlike Samba which I wouldn't bother with just for printing. If it was JUST for printing I'd agree. But the whole samba setup is for more than that. There's also file sharing (since Windows 10 home doesn't support NFS), central authentication, things like that. I finally got it working in samba mode so I'm good with that. And that, again, would skip the whole point of having a central print server. :) Not really. Athena would remain the CUPS server for itself and any Linux or additional OS clients, sending jobs over IPP:// to the Windows print server running on the Windows PC. Okay, I could see that one. Although I'm totally lost when it comes to IPP. I've looked but apparently my google-fu is still weak because I can't find any good documentation on how to setup IPP, how to format the URLs, etc 3. If the current setup is the right thing for you, increase CUPS log verbosity and check the logs on Athena to find out what it isn't happy with when Janus sends a print job to it. First check the CUPS driver and printing protocol is the same on Janus as on Athena and the CUPS' config on Athena allows inbound connections from your LAN, or your Janus' IP address. I can check on those. Thanks. I do notice one thing strange. Maybe a cups bug. In the web interface when I created the printer in Athena, I checked the box to say it was a shared printer. But when I look at the status it says "not shared". Hmm ... what follows the commented line: # Restrict access to the server... Order Deny,Allow ... ? in the '/etc/cups/cupsd.conf' of Athena? Here's the entire file. Although I fail to see what the allow/deny could mean for a printer showing on Athena. It's not that Janus says it's not a shared printer. It's ATHENA saying it's not shared, right after I checked the box to make it shared. # Configuration file for the CUPS scheduler. See "man cupsd.conf" for a # complete description of this file. # # Log general information in error_log - change "warn" to "debug" # for troubleshooting... LogLevel debug PageLogFormat # Only listen for connections from the local machine. Listen 192.168.10.2:631 Listen /run/cups/cups.sock # Show shared printers on the local network. Browsing On BrowseLocalProtocols # Default authentication type, when authentication is required... DefaultAuthType Basic # Web interface setting... WebInterface Yes # Restrict access to the server... Order allow,deny allow 192.168.10.0/24 # Restrict access to the admin pages... Order allow,deny allow 192.168.10.0/24 # Restrict access to configuration files... AuthType Default Require user @SYSTEM Order allow,deny # Restrict access to log files... AuthType Default Require user @SYSTEM Order allow,deny # Set the default printer/job policies... # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... Order deny,allow Allow 192.168.10.0/24 Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document> Require user @OWNER @SYSTEM Order deny,allow # All administration operations require an administrator to authenticate... CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices> AuthType Default Require user @SYSTEM Order deny,allow # All printer operations require a printer operator to authenticate... Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs> AuthType Default Require user @SYSTEM Order deny,allow # Only the owner or an administrator can cancel or authenticate a job... Require user @OWNER @SYSTEM Order deny,allow Order deny,allow # Set the authenticated printer/job policies... # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... AuthType Default Order deny,allow Purge-Jobs Set-Job-Attributes Create-Job-Subscription
Re: [gentoo-user] No news on kernel upgrade?
On Tuesday, 9 February 2021 08:43:13 GMT n952162 wrote: > Are extra administrative steps necessary when --sync brings in a new > kernel, as in: > > https://wiki.gentoo.org/wiki/Kernel/Upgrade > > I currently have this situation: > > $ uname -a > Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 > GNU/Linux > > $ eselect kernel list > Available kernel symlink targets: >[1] linux-5.4.72-gentoo >[2] linux-5.4.80-gentoo-r1 >[3] linux-5.4.92-gentoo > > If an update requires additional steps, shouldn't that have appeared in > the news? It may help if I describe my approach to kernel upgrades. This is an ~amd64 system, but I have 'sys-kernel/gentoo-sources -~amd64' in my keywords file because I prefer to stick with stable kernel sources. I keep the latest kernel plus the one that was latest until I upgraded. When a new gentoo-sources comes in, I switch to it straight away, knowing that it's been proved to be sound. I could use eselect to change the /usr/src/linux symlink to the new kernel source tree, but instead I have 'sys-kernel/gentoo- sources symlink' in /etc/portage/package.use/kernel, which has the same effect. (This is for historical reasons.) Then I cwd to /usr/src/linux, copy .config from the previous version and 'make oldconfig'. Then I run this script [1]: $ cat /usr/local/bin/kmake #!/bin/bash mount /boot cd /usr/src/linux time (make -j12 && make modules_install && make install &&\ /bin/ls -lh --color=auto /boot &&\ echo ) &&\ echo && echo "Rebuilding modules..." && echo &&\ emerge --jobs --load-average=48 @module-rebuild @x11-module-rebuild echo && echo "Remaking microcode images..." && rm -f /boot/ early_ucode.cpio.new &&\ iucode_tool -S --write-earlyfw=/boot/early_ucode.cpio.new \ -tr /boot/early_ucode.cpio -tb /lib/firmware/intel-ucode &&\ mv -v /boot/early_ucode.cpio.new /boot/early_ucode.cpio &&\ echo That takes care of anything that might otherwise break wnen the kernel is upgraded. It picks up virtualbox-modules in passing, so you can forget about it yourself. HTH. 1. It's a very simple script, nothing like as clever as some others we see here. :) -- Regards, Peter.
Re: [gentoo-user] No news on kernel upgrade?
On 2/9/21 3:55 PM, Neil Bothwick wrote: On Tue, 9 Feb 2021 14:25:01 +0100, n952162 wrote: gentoo policy is that administrators need to keep their systems up-to-date. The promise is, if they do so, the dependency system will be reliable. The kernel version is apparently an exception to this. The updating mechanism does not require that this track the synchronization of the portage tree. Administrators are free to decide what kernel they want to use. This works - except for virtualbox-modules. Portage should check that the kernel pointed to by the /usr/src/linux symlink is of a suitable version and has the necessary configuration settings. Lots of ebuilds already do this. If the virtualbox-modules ebuild is failing in this respect, it may well be a bug. what is the most efficient way for an administrator to known when a new kernel is available and advisable? You'll know because you'll see it in the list of packages to install when upgrading. Additionally, there is an elog message when a new set of kernel sources is installed, If you have PORTAGE_ELOG_SYSTEM="save mail" PORTAGE_ELOG_MAILURI="you@..." in make.conf, you will be emailed this info. See man make.conf for more on this. Excellent. I'll use that.
Re: [gentoo-user] No news on kernel upgrade?
On Tue, 9 Feb 2021 14:25:01 +0100, n952162 wrote: > gentoo policy is that administrators need to keep their systems > up-to-date. The promise is, if they do so, the dependency system will > be reliable. > > The kernel version is apparently an exception to this. The updating > mechanism does not require that this track the synchronization of the > portage tree. Administrators are free to decide what kernel they want > to use. This works - except for virtualbox-modules. Portage should check that the kernel pointed to by the /usr/src/linux symlink is of a suitable version and has the necessary configuration settings. Lots of ebuilds already do this. If the virtualbox-modules ebuild is failing in this respect, it may well be a bug. > what is the most efficient way for an administrator to known when a new > kernel is available and advisable? You'll know because you'll see it in the list of packages to install when upgrading. Additionally, there is an elog message when a new set of kernel sources is installed, If you have PORTAGE_ELOG_SYSTEM="save mail" PORTAGE_ELOG_MAILURI="you@..." in make.conf, you will be emailed this info. See man make.conf for more on this. -- Neil Bothwick When companies ship Styrofoam, what do they pack it in? pgpqeCJXXcF7r.pgp Description: OpenPGP digital signature
Re: [gentoo-user] No news on kernel upgrade?
On Tue, 9 Feb 2021 11:01:04 +0100, n952162 wrote: > Ah, maybe I have a theory what's going on ... maybe there's no news that > it's time to upgrade the kernel, because it's not meant that the kernel > necessarily needs to be upgraded ... except that it seems that the > virtualbox-modules package might have a (unfortunate) dependency on > that... gentoo-sources is not a kernel, it only installs the kernel sources. It is up to you to configure, compile and install the kernel from the sources. This is different from how Gentoo handles other packages. You may have three sets of sources installed, but only one kernel. -- Neil Bothwick We all know what comes after 'X', said Tom, wisely. pgpv6zCuIUvjB.pgp Description: OpenPGP digital signature
Re: [gentoo-user] No news on kernel upgrade?
On 2/9/21 2:56 PM, Michael wrote: On Tuesday, 9 February 2021 13:25:01 GMT n952162 wrote: On 2/9/21 12:57 PM, Michael wrote: On Tuesday, 9 February 2021 10:01:04 GMT n952162 wrote: On 2/9/21 10:05 AM, Dale wrote: n952162 wrote: Are extra administrative steps necessary when --sync brings in a new kernel, as in: https://wiki.gentoo.org/wiki/Kernel/Upgrade I currently have this situation: $ uname -a Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 GNU/Linux $ eselect kernel list Available kernel symlink targets: [1] linux-5.4.72-gentoo [2] linux-5.4.80-gentoo-r1 [3] linux-5.4.92-gentoo If an update requires additional steps, shouldn't that have appeared in the news? It depends I think. I say think because there may be a binary kernel available which will upgrade itself. I seem to recall reading about it on a mailing list somewhere. I have no experience with it tho. That said, if you use the old method, you have to upgrade the kernel yourself. There are scripts you can use to help automate it a good bit but some of us still do it the manual way. When you do updates, emerge will pull in the new sources but the rest is up to you. I suspect most that do it the old way, copy .config over to the new kernel directory, run make oldconfig and answer the questions, compile the new kernel, copy it to /boot using the right method which there is a few of and then configure your bootloader if needed. The link you posted explains this in more detail, and may be more complete too. I'm trying to remember what that binary kernel thing is called. I just skimmed the messages so it could be something else or not even in the tree yet. Dale :-) :-) Ah, maybe I have a theory what's going on ... maybe there's no news that it's time to upgrade the kernel, because it's not meant that the kernel necessarily needs to be upgraded ... except that it seems that the virtualbox-modules package might have a (unfortunate) dependency on that... I'm not sure I understand completely why there should be a news item from portage whenever new kernel sources are updated and downloaded. It is up the system administrator to configure and build the new sources if desired. gentoo policy is that administrators need to keep their systems up-to-date. The promise is, if they do so, the dependency system will be reliable. The kernel version is apparently an exception to this. The updating mechanism does not require that this track the synchronization of the portage tree. Administrators are free to decide what kernel they want to use. This works - except for virtualbox-modules. Each time you upgrade your kernel on the host, external modules will require updating/rebuilding. The set '@module-rebuild' does that instead of having to re-emerge manually each external module. Yes, in another context, your tip about this helped me to solve a separate problem with vbox. A quick survey didn't find mention of this facility in the handbook. Perhaps I missed it. Yes, I just found it in the Handbook here: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Post-install. 2Fupgrade_tasks and in the wiki here: https://wiki.gentoo.org/wiki/Kernel/ Upgrade#Reinstalling_external_kernel_modules Okay, good. Thank you. Or you could shoot for the latest stable 5.4.92, which works fine here, also on a host which runs VBox. Yes, I'll do that.
Re: [gentoo-user] No news on kernel upgrade?
On Tuesday, 9 February 2021 13:25:01 GMT n952162 wrote: > On 2/9/21 12:57 PM, Michael wrote: > > On Tuesday, 9 February 2021 10:01:04 GMT n952162 wrote: > >> On 2/9/21 10:05 AM, Dale wrote: > >>> n952162 wrote: > Are extra administrative steps necessary when --sync brings in a new > > kernel, as in: > https://wiki.gentoo.org/wiki/Kernel/Upgrade > > I currently have this situation: > > $ uname -a > Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 > GNU/Linux > > $ eselect kernel list > > Available kernel symlink targets: > [1] linux-5.4.72-gentoo > [2] linux-5.4.80-gentoo-r1 > [3] linux-5.4.92-gentoo > > If an update requires additional steps, shouldn't that have appeared > in the news? > >>> > >>> It depends I think. I say think because there may be a binary kernel > >>> available which will upgrade itself. I seem to recall reading about it > >>> on a mailing list somewhere. I have no experience with it tho. That > >>> said, if you use the old method, you have to upgrade the kernel > >>> yourself. There are scripts you can use to help automate it a good bit > >>> but some of us still do it the manual way. When you do updates, emerge > >>> will pull in the new sources but the rest is up to you. I suspect most > >>> that do it the old way, copy .config over to the new kernel directory, > >>> run make oldconfig and answer the questions, compile the new kernel, > >>> copy it to /boot using the right method which there is a few of and then > >>> configure your bootloader if needed. The link you posted explains this > >>> in more detail, and may be more complete too. > >>> > >>> I'm trying to remember what that binary kernel thing is called. I just > >>> skimmed the messages so it could be something else or not even in the > >>> tree yet. > >>> > >>> Dale > >>> > >>> :-) :-) > >> > >> Ah, maybe I have a theory what's going on ... maybe there's no news that > >> it's time to upgrade the kernel, because it's not meant that the kernel > >> necessarily needs to be upgraded ... except that it seems that the > >> virtualbox-modules package might have a (unfortunate) dependency on > >> that... > > > > I'm not sure I understand completely why there should be a news item from > > portage whenever new kernel sources are updated and downloaded. It is up > > the system administrator to configure and build the new sources if > > desired. > gentoo policy is that administrators need to keep their systems > up-to-date. The promise is, if they do so, the dependency system will > be reliable. > > The kernel version is apparently an exception to this. The updating > mechanism does not require that this track the synchronization of the > portage tree. Administrators are free to decide what kernel they want > to use. This works - except for virtualbox-modules. > > > Each time you upgrade your kernel on the host, external modules will > > require updating/rebuilding. The set '@module-rebuild' does that instead > > of having to re-emerge manually each external module. > > Yes, in another context, your tip about this helped me to solve a > separate problem with vbox. A quick survey didn't find mention of this > facility in the handbook. Perhaps I missed it. Yes, I just found it in the Handbook here: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Post-install. 2Fupgrade_tasks and in the wiki here: https://wiki.gentoo.org/wiki/Kernel/ Upgrade#Reinstalling_external_kernel_modules > > You seem to be running an old kernel. VBox and its modules changed > > recently so these will need to be updated - there may be a conflict with > > older host kernels and as you report you've come across it. > > what is the most efficient way for an administrator to known when a new > kernel is available and advisable? I don't know of a generic recommended way to go about this, but I have 'sys- kernel/gentoo-sources' in my world file, so the latest stable version is downloaded once available. Then I build the kernel when convenient and run '@module-rebuild' to update any external module packages. The problem could arise when some package, in this case VBox, requires a later kernel than the one you've been running. I guess things will break and upon investigating the kernel version issue will come up in troubleshooting. For major breakages of the core system I'd expect the devs would have spotted it and highlighted it with a news item. > > The eselect list you showed does not have a selected kernel source. What > > is linked to /usr/src/linux on your system? > > > > $ ls -l /usr/src/ > > It is properly linked considering the configuration: > > $ ll /usr/src/linux > lrwxrwxrwx 1 root root 20 Nov 8 2019 /usr/src/linux -> > linux-4.19.72-gentoo Right, this particular kernel version is no longer in the tree. The two versions closest to it
Re: [gentoo-user] No news on kernel upgrade?
On 2/9/21 12:57 PM, Michael wrote: On Tuesday, 9 February 2021 10:01:04 GMT n952162 wrote: On 2/9/21 10:05 AM, Dale wrote: n952162 wrote: Are extra administrative steps necessary when --sync brings in a new kernel, as in: https://wiki.gentoo.org/wiki/Kernel/Upgrade I currently have this situation: $ uname -a Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 GNU/Linux $ eselect kernel list Available kernel symlink targets: [1] linux-5.4.72-gentoo [2] linux-5.4.80-gentoo-r1 [3] linux-5.4.92-gentoo If an update requires additional steps, shouldn't that have appeared in the news? It depends I think. I say think because there may be a binary kernel available which will upgrade itself. I seem to recall reading about it on a mailing list somewhere. I have no experience with it tho. That said, if you use the old method, you have to upgrade the kernel yourself. There are scripts you can use to help automate it a good bit but some of us still do it the manual way. When you do updates, emerge will pull in the new sources but the rest is up to you. I suspect most that do it the old way, copy .config over to the new kernel directory, run make oldconfig and answer the questions, compile the new kernel, copy it to /boot using the right method which there is a few of and then configure your bootloader if needed. The link you posted explains this in more detail, and may be more complete too. I'm trying to remember what that binary kernel thing is called. I just skimmed the messages so it could be something else or not even in the tree yet. Dale :-) :-) Ah, maybe I have a theory what's going on ... maybe there's no news that it's time to upgrade the kernel, because it's not meant that the kernel necessarily needs to be upgraded ... except that it seems that the virtualbox-modules package might have a (unfortunate) dependency on that... I'm not sure I understand completely why there should be a news item from portage whenever new kernel sources are updated and downloaded. It is up the system administrator to configure and build the new sources if desired. gentoo policy is that administrators need to keep their systems up-to-date. The promise is, if they do so, the dependency system will be reliable. The kernel version is apparently an exception to this. The updating mechanism does not require that this track the synchronization of the portage tree. Administrators are free to decide what kernel they want to use. This works - except for virtualbox-modules. Each time you upgrade your kernel on the host, external modules will require updating/rebuilding. The set '@module-rebuild' does that instead of having to re-emerge manually each external module. Yes, in another context, your tip about this helped me to solve a separate problem with vbox. A quick survey didn't find mention of this facility in the handbook. Perhaps I missed it. You seem to be running an old kernel. VBox and its modules changed recently so these will need to be updated - there may be a conflict with older host kernels and as you report you've come across it. what is the most efficient way for an administrator to known when a new kernel is available and advisable? The eselect list you showed does not have a selected kernel source. What is linked to /usr/src/linux on your system? $ ls -l /usr/src/ It is properly linked considering the configuration: $ ll /usr/src/linux lrwxrwxrwx 1 root root 20 Nov 8 2019 /usr/src/linux -> linux-4.19.72-gentoo Upgrading your kernel and any external modules (inc. VBox's) should fix whatever is currently giving you trouble. Okay, thank you.
Re: [gentoo-user] Gentoo on rpi
On 9/2/21 8:29 pm, Wols Lists wrote: On 09/02/21 11:29, Andrew Lowe wrote: On 8/2/21 11:36 pm, Peter Humphrey wrote: Hello list, I have a Pi 400, on which I'd like to install Gentoo if I can. I've tried a few approaches so far, but each one has fallen foul of some obstacle. For instance, today I tried installing a small Gentoo system into a chroot, to do the compiling there. It seemed to be going well until time came to upgrade openssl. It stopped when it couldn't cope with the ARM platform. Zlib also failed, needing static compilation, I think. I see references to using crossdev, wine and taking a prebuilt system from various sources, but I haven't found a way through yet. What setup do people use for compiling for Raspberry Pi? I'm about to try this: https://github.com/sakaki-/gentoo-on-rpi-64bit for a couple of 3's and then some 4's when they turn up. Have you tried it and it fails? Bear in mind apparently a normal pi boot setup doesn't work on the 400. Don't know anything about it except apparently if you stick a card for the pi 3 or 4 in a 400, it won't boot. It needs to be optimised for the 400. Cheers, Wol Sorry, forgot about those thingies... Took the "400" to be a typo of "4", ie just the board Andrew
Re: [gentoo-user] lightdm - keeps looping
On Tuesday, 9 February 2021 02:23:26 GMT the...@sys-concept.com wrote: > On 2/8/21 7:01 PM, the...@sys-concept.com wrote: > > On 2/8/21 6:59 PM, the...@sys-concept.com wrote: > >> The slim is no longer maintain, so I tried "lightdm" but when I try to > >> login, it keeps looping, I'm back into login screen. I can post a > >> log-file but it is long. > >> > >> Any suggestion. Have a look at the wiki page, the Troubleshooting section. It mentions a networkmanager conflict if hostname is set. > > I forgot to mention the error: > > cat .xsession-errors > > > > /etc/X11/Sessions/Xsession: line 106: exec: xsm: not found > > emerging xsm start something but not my xfce4. > Gentoo wiki does not mention anything how to start xfce4 with lightdm I don't know what this "something" is your lightdm starts, because I am not seated in front of your monitor. I haven't used lightdm for a while now, but there is a line where you set your preferred 'user-session' in /etc/lightdm/ lightdm.conf. Have you done this? signature.asc Description: This is a digitally signed message part.
[gentoo-user] how to maintain and successfully compile inn
Hi. I see that inn is no longer in the tree and I have a local ebuild for inn2.6.3, but it won't work because of the following line PYTHON_COMPAT=( python2_7 ) The error I get is: * ERROR: net-nntp/inn-2.6.3::local_ebuilds failed (depend phase): * No supported implementation in PYTHON_COMPAT. * * Call stack: * ebuild.sh, line 609: Called source * '/usr/local/portage/net-nntp/inn/inn-2.6.3.ebuild' * inn-2.6.3.ebuild, line 8: Called inherit * 'autotools' 'eutils' 'multilib' * 'python-single-r1' 'toolchain-funcs' * ebuild.sh, line 314: Called __qa_source * '/var/db/repos/gentoo/eclass/python-single-r1.eclass' * ebuild.sh, line 112: Called source * '/var/db/repos/gentoo/eclass/python-single-r1.eclass' * python-single-r1.eclass, line 269: Called * _python_single_set_globals * python-single-r1.eclass, line 209: Called _python_set_impls *python-utils-r1.eclass, line 156: Called die * The specific snippet of code: * die "No supported implementation in * PYTHON_COMPAT." I still have python 2.7 probably because of issues in building chrome, so how do I fix things to keep portage happy and what should I do going forward because I obviously don't want to depend on python2.7 for actually running things. I have mailman which I have to do something about as well, so I will have to use their new ecosystem or switch to another mailing list manager. Thanks for any advice and thoughts on this subject. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
Re: [gentoo-user] No news on kernel upgrade?
On Tuesday, 9 February 2021 10:01:04 GMT n952162 wrote: > On 2/9/21 10:05 AM, Dale wrote: > > n952162 wrote: > >> Are extra administrative steps necessary when --sync brings in a new > >> > >> kernel, as in: > >>https://wiki.gentoo.org/wiki/Kernel/Upgrade > >> > >> I currently have this situation: > >> > >> $ uname -a > >> Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 > >> GNU/Linux > >> > >> $ eselect kernel list > >> > >> Available kernel symlink targets: > >>[1] linux-5.4.72-gentoo > >>[2] linux-5.4.80-gentoo-r1 > >>[3] linux-5.4.92-gentoo > >> > >> If an update requires additional steps, shouldn't that have appeared > >> in the news? > > > > It depends I think. I say think because there may be a binary kernel > > available which will upgrade itself. I seem to recall reading about it > > on a mailing list somewhere. I have no experience with it tho. That > > said, if you use the old method, you have to upgrade the kernel > > yourself. There are scripts you can use to help automate it a good bit > > but some of us still do it the manual way. When you do updates, emerge > > will pull in the new sources but the rest is up to you. I suspect most > > that do it the old way, copy .config over to the new kernel directory, > > run make oldconfig and answer the questions, compile the new kernel, > > copy it to /boot using the right method which there is a few of and then > > configure your bootloader if needed. The link you posted explains this > > in more detail, and may be more complete too. > > > > I'm trying to remember what that binary kernel thing is called. I just > > skimmed the messages so it could be something else or not even in the > > tree yet. > > > > Dale > > > > :-) :-) > > Ah, maybe I have a theory what's going on ... maybe there's no news that > it's time to upgrade the kernel, because it's not meant that the kernel > necessarily needs to be upgraded ... except that it seems that the > virtualbox-modules package might have a (unfortunate) dependency on that... I'm not sure I understand completely why there should be a news item from portage whenever new kernel sources are updated and downloaded. It is up the system administrator to configure and build the new sources if desired. Each time you upgrade your kernel on the host, external modules will require updating/rebuilding. The set '@module-rebuild' does that instead of having to re-emerge manually each external module. You seem to be running an old kernel. VBox and its modules changed recently so these will need to be updated - there may be a conflict with older host kernels and as you report you've come across it. The eselect list you showed does not have a selected kernel source. What is linked to /usr/src/linux on your system? $ ls -l /usr/src/ Upgrading your kernel and any external modules (inc. VBox's) should fix whatever is currently giving you trouble. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Gentoo on rpi
On 09/02/21 11:29, Andrew Lowe wrote: > On 8/2/21 11:36 pm, Peter Humphrey wrote: >> Hello list, >> >> I have a Pi 400, on which I'd like to install Gentoo if I can. I've >> tried a >> few approaches so far, but each one has fallen foul of some obstacle. For >> instance, today I tried installing a small Gentoo system into a >> chroot, to do >> the compiling there. It seemed to be going well until time came to >> upgrade >> openssl. It stopped when it couldn't cope with the ARM platform. Zlib >> also >> failed, needing static compilation, I think. >> >> I see references to using crossdev, wine and taking a prebuilt system >> from >> various sources, but I haven't found a way through yet. >> >> What setup do people use for compiling for Raspberry Pi? >> > > I'm about to try this: > > https://github.com/sakaki-/gentoo-on-rpi-64bit > > for a couple of 3's and then some 4's when they turn up. Have you tried > it and it fails? > Bear in mind apparently a normal pi boot setup doesn't work on the 400. Don't know anything about it except apparently if you stick a card for the pi 3 or 4 in a 400, it won't boot. It needs to be optimised for the 400. Cheers, Wol
Re: [gentoo-user] Gentoo on rpi
On 8/2/21 11:36 pm, Peter Humphrey wrote: Hello list, I have a Pi 400, on which I'd like to install Gentoo if I can. I've tried a few approaches so far, but each one has fallen foul of some obstacle. For instance, today I tried installing a small Gentoo system into a chroot, to do the compiling there. It seemed to be going well until time came to upgrade openssl. It stopped when it couldn't cope with the ARM platform. Zlib also failed, needing static compilation, I think. I see references to using crossdev, wine and taking a prebuilt system from various sources, but I haven't found a way through yet. What setup do people use for compiling for Raspberry Pi? I'm about to try this: https://github.com/sakaki-/gentoo-on-rpi-64bit for a couple of 3's and then some 4's when they turn up. Have you tried it and it fails? Andrew
Re: [gentoo-user] Gentoo on rpi
On Tuesday, 9 February 2021 05:14:25 GMT William Kenworthy wrote: > Use a standard Gentoo aarch64 (arm64 ) package. Add a pi kernel, the > /lib/modules directory and the /boot directory from a raspian tarball. > > I did this on a pi 3B running in 64bit mode. Once I had a bootable > system it was easy to modify and a fork from my first image is also > running on a couple of odroid 64bit systems (using the odroid boot and > kernel) and as an lxc image on a 64bit odroid n2. > > Getting the /boot directory and uBoot config files sorted was the main > problem. Interesting... I'll give that a shot. Thanks William. -- Regards, Peter.
Re: [gentoo-user] Sharing printers via Cups
On Tuesday, 9 February 2021 00:59:01 GMT Dan Egli wrote: > On 2/8/2021 5:01 PM, Michael wrote: > > On Monday, 8 February 2021 19:08:11 GMT Dan Egli wrote: > >> On 2/8/2021 2:14 AM, Wols Lists wrote: > >>> This is typical. In my linux setup, the printer is always busy. Stuff > >>> still prints fine, though. > >> > >> Mine won't print. Says the printer is busy, and nothing else happens. It > >> just sits there. Let me give better names because even I can get > >> confused. So, we have three machines. Win10 Home = IRIS, Linux Server = > >> Athena, Linux Workstation = Janus > >> > >> If I print directly from Iris, it obviously works fine. If I print from > >> Athena it works fine. If I print from Janus, it never goes anywhere. > >> > How can I set this up correctly? To describe exactly what I'm trying to > do, let's just use four computers in this example. A is the central > print server. B is the windows client with the printer. C and D are > linux machines. What I want is if either C or D print something, they > both send it to A, and then A sends it to B. > >>> > >>> I'd try moving the printer to A, or configuring C & D to print directly > >>> to B. I dunno how you set up smbprint, but that should send straight to > >>> a shared printer on B no problem. > >> > >> Unfortunately, moving the printer is a no-go right now, for various > >> reasons. Otherwise I'd just move it to be a network printer. The printer > >> itself is designed to be network capable. But Iris is technically not MY > >> Computer, and the printer isn't technically MINE either. They belong to > >> someone else in the house, and I simply have permission to use them. So > >> my only two options are 1) Configure EVERYTHING to print to Iris. That's > >> doable I suppose, but really not what I want, or B) Use Athena as a > >> central print server just as it already acts as a central file server. > >> That is FAR more preferable because then if something changes instead of > >> updating EVERY computer I update ONE. > >> > >> -- > >> Dan Egli > > > > Some ideas: [snip ...] > > 2. Last time I set up a Windows XP as a printer-server, I > > installed-enabled > > Unix Print Service Windows Component (really an LPD/LPR service). Then > > Linux PCs were able to print directly to it. No need to configure SMB > > and what not, just for printing. This randomly selected article > > describes the principle: > > > > https://support.printmanager.com/hc/en-us/articles/202835449-Linux-printin > > g-via-the-Windows-Print-Server- > > Actually tried that. Got LPD installed, sent a test page. Test page > appeared in the Windows Queue, then disappeared without any > acknowledgement from the printer. This would need some troubleshooting/configuring on the Windows end. It's a long time ago I tried this and don't recall what I had configured to allow clients to print via the Windows PC. It was relatively simple and lightweight though, unlike Samba which I wouldn't bother with just for printing. > I finally got it working in samba mode > so I'm good with that. And that, again, would skip the whole point of > having a central print server. :) Not really. Athena would remain the CUPS server for itself and any Linux or additional OS clients, sending jobs over IPP:// to the Windows print server running on the Windows PC. > > 3. If the current setup is the right thing for you, increase CUPS log > > verbosity and check the logs on Athena to find out what it isn't happy > > with > > when Janus sends a print job to it. First check the CUPS driver and > > printing protocol is the same on Janus as on Athena and the CUPS' config > > on Athena allows inbound connections from your LAN, or your Janus' IP > > address. > I can check on those. Thanks. I do notice one thing strange. Maybe a > cups bug. In the web interface when I created the printer in Athena, I > checked the box to say it was a shared printer. But when I look at the > status it says "not shared". Hmm ... what follows the commented line: # Restrict access to the server... Order Deny,Allow ... ? in the '/etc/cups/cupsd.conf' of Athena? Similarly, check the "hosts allow" directive in the Samba configuration to include Janus' IP address. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] No news on kernel upgrade?
On 2/9/21 10:05 AM, Dale wrote: n952162 wrote: Are extra administrative steps necessary when --sync brings in a new kernel, as in: https://wiki.gentoo.org/wiki/Kernel/Upgrade I currently have this situation: $ uname -a Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 GNU/Linux $ eselect kernel list Available kernel symlink targets: [1] linux-5.4.72-gentoo [2] linux-5.4.80-gentoo-r1 [3] linux-5.4.92-gentoo If an update requires additional steps, shouldn't that have appeared in the news? It depends I think. I say think because there may be a binary kernel available which will upgrade itself. I seem to recall reading about it on a mailing list somewhere. I have no experience with it tho. That said, if you use the old method, you have to upgrade the kernel yourself. There are scripts you can use to help automate it a good bit but some of us still do it the manual way. When you do updates, emerge will pull in the new sources but the rest is up to you. I suspect most that do it the old way, copy .config over to the new kernel directory, run make oldconfig and answer the questions, compile the new kernel, copy it to /boot using the right method which there is a few of and then configure your bootloader if needed. The link you posted explains this in more detail, and may be more complete too. I'm trying to remember what that binary kernel thing is called. I just skimmed the messages so it could be something else or not even in the tree yet. Dale :-) :-) Ah, maybe I have a theory what's going on ... maybe there's no news that it's time to upgrade the kernel, because it's not meant that the kernel necessarily needs to be upgraded ... except that it seems that the virtualbox-modules package might have a (unfortunate) dependency on that...
Re: [gentoo-user] No news on kernel upgrade?
On Tue, 9 Feb 2021 at 10:05, Dale wrote: > I'm trying to remember what that binary kernel thing is called. I just > skimmed the messages so it could be something else or not even in the > tree yet. I believe you're thinking of sys-kernel/gentoo-kernel-bin (also available without -bin, which I believe is also automatically built and installed for you). Regards, Arve
Re: [gentoo-user] No news on kernel upgrade?
n952162 wrote: > > Are extra administrative steps necessary when --sync brings in a new > kernel, as in: > > https://wiki.gentoo.org/wiki/Kernel/Upgrade > > I currently have this situation: > > $ uname -a > Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 > GNU/Linux > > $ eselect kernel list > Available kernel symlink targets: > [1] linux-5.4.72-gentoo > [2] linux-5.4.80-gentoo-r1 > [3] linux-5.4.92-gentoo > > If an update requires additional steps, shouldn't that have appeared > in the news? > > It depends I think. I say think because there may be a binary kernel available which will upgrade itself. I seem to recall reading about it on a mailing list somewhere. I have no experience with it tho. That said, if you use the old method, you have to upgrade the kernel yourself. There are scripts you can use to help automate it a good bit but some of us still do it the manual way. When you do updates, emerge will pull in the new sources but the rest is up to you. I suspect most that do it the old way, copy .config over to the new kernel directory, run make oldconfig and answer the questions, compile the new kernel, copy it to /boot using the right method which there is a few of and then configure your bootloader if needed. The link you posted explains this in more detail, and may be more complete too. I'm trying to remember what that binary kernel thing is called. I just skimmed the messages so it could be something else or not even in the tree yet. Dale :-) :-)
Re: [gentoo-user] No news on kernel upgrade?
> On 2021-02-09, at 03:43, n952162 wrote: > > If an update requires additional steps, shouldn't that have appeared in the > news? No because how it's done is totally dependent on your needs. There's no one correct way to do it. Even in common cases, some may choose to use certain kinds of file systems or other things that cannot be covered. Gentoo is all about customisability. Shameless plug: use upgrade-kernel from my upkeep package[1] (which is on tatsh-overlay)[2] . It supports updating/rebuilding the kernel plus MBR|UEFI/GRUB/Dracut and systemd-boot+UEFI/Dracut/kernel signing (latest HEAD only). 1. https://github.com/Tatsh/upkeep#automatic-kernel-update-process 2. https://github.com/Tatsh/tatsh-overlay#installation
[gentoo-user] No news on kernel upgrade?
Are extra administrative steps necessary when --sync brings in a new kernel, as in: https://wiki.gentoo.org/wiki/Kernel/Upgrade I currently have this situation: $ uname -a Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 GNU/Linux $ eselect kernel list Available kernel symlink targets: [1] linux-5.4.72-gentoo [2] linux-5.4.80-gentoo-r1 [3] linux-5.4.92-gentoo If an update requires additional steps, shouldn't that have appeared in the news?
