Re: [gentoo-user] A couple of problems with systemd
On Fri, May 27, 2022 at 6:51 PM John Covici wrote: > [...] > Thanks. I am not usingsystemd-network or anything like that.I > created a service called network and use the %i and links in > /etc/systemd/system/multi-user-target.wants to start my two cards. > Maybe this is not the normal way, but when I first started using > systemd, this is the best I could come up with at the time. > Have you tried using .network files? You can setup it static: $ cat /etc/systemd/network/enp2s0.network # Ethernet [Match] Name=enp2s0 [Network] Address=192.168.1.1/24 Gateway=192.168.1.254 DNS=192.168.1.254 or with DHCP: # /etc/systemd/network/30-bond1.network [Match] Name=bond1 [Network] DHCP=ipv6 Even with wpa_supplicant[1]. Regards. [1] https://wiki.somlabs.com/index.php/Connecting_to_WiFi_network_using_systemd_and_wpa-supplicant -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] compton got masked?
On Tue, Oct 12, 2021 at 2:32 PM caveman رَجُلُ الْكَهْفِ 穴居人 < toraboracave...@protonmail.com> wrote: > why? > >From [1]: Development stopped by upstream. Switch to its actively developed fork, x11-misc/picom. Regards. [1] https://gitweb.gentoo.org/repo/gentoo.git/tree/profiles/package.mask#n77 -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] apache 2.4.50 or php
On Thu, Oct 7, 2021 at 2:44 PM wrote: > I just ungraded to apache 2.4.50 but I'm getting an error with my php. 8 > Or it could be related to newer PHP Version 8.0.11 > > When I try to login apache is giving me error code 500 > I masked dev-lang/php:8, for the time being. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd boot timer
On Fri, Oct 1, 2021 at 5:24 PM antlists wrote: [...] > Ouch. Dunno if that would work. Bear in mind I'm running this BEFORE > fstab, so / is read-only ... > You can store the timestamp in /run and then have another unit that updates the timestamp in /var after remounting root (/) read/write. Again, you have all the flexibility of scripts+systemd units. I will have to see if the timer can set up the oneshot service, and if > it really is one shot per activation ... > It's one shot per activation, but the activation is set either by timer, or by unit dependency (After= and/or Before=), AFAIU. I don't think the granularity you want is there: the timer will elapse once a week, whether you are booting or running the system (if using timers); or it will run at boot, whether a week has passed or not (if using a normal service). I don't think you can mix and match; the precise state you want is beyond what systemd offers (I think). I think the simpler answer is to write a script and handle the state yourself; but knock yourself up. It's possible I'm wrong and you can do that with only systemd units/timers. Regards. [1] https://man7.org/linux/man-pages/man5/systemd.timer.5.html -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd boot timer
On Fri, Oct 1, 2021 at 3:37 PM antlists wrote:
> I'm trying to get a systemd unit to fire on boot once a week. Reading up
> on timer units, I can't work out how to get it to work.
>
> This is tied up with my earlier systemd mount post - I've now got that
> sorted - I've got dm-integrity to fire before fstab.
>
> I now want to run lvm snapshot on the first boot of the weekend. Writing
> a unit to do the snapshot seems pretty easy, but obviously I don't want
> it firing every boot, if I stick the date in the volume name I don't
> want it colliding with an earlier run the same day, etc etc.
>
> The question really is - if I have a weekly timer fire and activate the
> unit, is the activation going to survive the reboot to run on the next
> boot?
>
> The problem I'm having is that all the stuff I've seen about timers says
> you have two lines - activate on Saturdays, and activate on boot. Snag
> is, they seem to be independent such that EITHER condition will activate
> the service. As I say, I want BOTH. I don't want the service running
> while the system is up and running.
>
I'm not sure timer units have enough flexibility to do what you want.
I think it would be much simpler to have a Type=oneshot service at boot,
and the Exec= line to call a script. You can store the timestamp of the
last time it was called someplace in the filesystem (say,
/var/lib/my-script or something), and if the timestamp doesn't exists or is
older than one week, the scripts executes lvm snapshot and updates the
timestamp; otherwise it ends without doing anything.
The timer units are very similar to cron, and I believe what you want
cannot be done with cron either; you need special logic and state ("I'm
booting AND haven't run this in at least a week"), so a script is necessary
(I think). Luckly, systemd allows you to smartly manage your scripts and
impose dependencies on them (you need /var in my example, and you can set
it to run before starting X).
Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd mount - what on earth is it doing ...
On Sat, Sep 25, 2021 at 1:48 PM antlists wrote: [...] > Bear in mind, integritysetup is not in my initrd, so ... > I think you would need to put it in your initrd. > It looks to me like grub switches to the real root partition read-only > before firing stuff off, so if I tell my integritysetup.service to run > before local-fs.target, does that mean everything should be working > before systemd runs fstab? > > Bear in mind dm-integrity is on my raw partitions, and I'm running lvm > and md-raid, I'm guessing they're part of local-fs-pre.target? So I > really need to run dm-integrity before that? Or preferably add > dm-integrity TO that - how do I do that? > > The problem is this isn't all that discoverable - even digging around > /etc/systemd, it's hard to find clues ... > As Rich already mentioned it, noauto != remove mount point from fstab. That's the first thing. Then you need to specify that home.mount should run *after* md/LVM, which in turn runs after your integrity setup service. The problem is: you have root (/) on md/LVM too; I know they are different RAIDs/volumes, but there is one *service* for RAID and LVM, at least out-of-the-box, in systemd. You could try to split different instances using templates (the units with @ in their names), but the simplest solution is to put your integrity logic in the initrd (with the added benefit that you can mount it in emergencies if something goes wrong with root). If you have the integrity logic in early boot, then your integrity setup service should have: Before=mdmonitor.service lvm2-lvmetad.service And I think that should be enough? The home.mount unit depends on the underlying device being available, and that will happen only after md and LVM have done it's thing. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd mount - what on earth is it doing ...
On Fri, Sep 24, 2021 at 2:25 PM antlists wrote: > This is weird ... > > My /home directory is set up somewhat strangely, as in I've got two raw > partitions, I've put dm-integrity on them, raided them together, then > put lvm on top of that. > > Which got me into a bind with fstab. I've created a systemd service, > which fires up dm-integrity on those two partitions. But I get the > impression it doesn't run until fstab completes. Catch-22 - fstab tries > to mount /home, but it can't until dm-integrity has made the volume appear! > Have you tried using Before=local-fs.target in the service? Or even Before=local-fs-pre.target? So I created a systemd mount unit for /home, which only runs after > dm-integrity. Great - I enabled it and it appeared to work! > You removed the /home entry from fstab, right? > Only problem, startplasma-wayland now dumped me at a blank screen. > > Now for the weirdo. I disabled it, thinking I would have to log in as > root, mount /home, and go from there. Except that, when I logged in, > /home was mounted and startplasma-wayland worked! > That sounds like /home was still on fstab... > systemctl tells me mount.home is disabled, but also tells me that it ran > and mounted the drive. > That should be home.mount. What does systemctl status home.mount says? > So what on earth is going on, and more importantly, what am I > misunderstanding or doing wrong. I would very much like to know why it's > working, when I think it shouldn't be! > Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Official support for the s6 init on Gentoo
On Sun, Sep 19, 2021 at 12:16 PM wrote: [...] > Of course, some extra work will require from Gentoo. > That's great; when you have found enough people willing and able to do that work specifically for Gentoo, including maintenance, updates, bug reporting, triage and fixes for the foreseeable future, then a reasonable proposal could be made. An alternative is to start and maintain an oficial overlay (note: it would also require enough people willing and able to do that work); if, as you suspect, s6 has enough qualities, it would attract a large number of users and then requesting a merge of the overlay to the official tree should be easier. But really, you are asking for other people to do the work in something that interests you. No matter how many Gentoo users could share your interest (which, BTW, I suspect there are not that many), if there are not enough of them *WILLING* and *ABLE* to do the work to satisfy that interest, then their number is irrelevant. That's how Free Software and Open Source works: someone has to be willing and able to do the work for anything to be implemented. If you are really interested, *you* start doing the work. Code talks. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Wed, Sep 8, 2021 at 9:14 AM Tamer Higazi wrote: [...] > I think the problem is somewhere deeper > > I wish I knew what it might be. > Yeah, I don't understand it either. Have you tried using the other network card? With the corresponding change in the .network file, of course. Just to test. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Tue, Sep 7, 2021 at 3:21 PM Tamer Higazi wrote: [...] > Sep 07 22:15:19 tux systemd[1]: Starting Network Configuration... > Sep 07 22:15:19 tux systemd-networkd[958]: lo: Link UP > Sep 07 22:15:19 tux systemd-networkd[958]: lo: Gained carrier > Sep 07 22:15:19 tux systemd-networkd[958]: Enumeration completed > Sep 07 22:15:19 tux systemd[1]: Started Network Configuration. > Sep 07 22:15:20 tux systemd-networkd[958]: eth0: Interface name change > detected, renamed to enp6s0. > Sep 07 22:15:20 tux systemd-networkd[958]: eth1: Interface name change > detected, renamed to enp7s0. > The message "enp6s0: Link UP" never appears? My log is very similar: Aug 31 17:24:12 graphite systemd[1]: Starting Network Configuration... Aug 31 17:24:12 graphite systemd-networkd[453]: lo: Link UP Aug 31 17:24:12 graphite systemd-networkd[453]: lo: Gained carrier Aug 31 17:24:12 graphite systemd-networkd[453]: Enumeration completed Aug 31 17:24:12 graphite systemd[1]: Started Network Configuration. Aug 31 17:24:12 graphite systemd-networkd[453]: eth0: Interface name change detected, renamed to eno1. Aug 31 17:24:14 graphite systemd-networkd[453]: eno1: Link UP Aug 31 17:24:17 graphite systemd-networkd[453]: eno1: Gained carrier Aug 31 17:24:19 graphite systemd-networkd[453]: eno1: Gained IPv6LL The change from eth0 to eno1 happens *after* "Started Network Configuration", like yours, but my connection goes up immediately. Can you please do me a favour and execute on your machine: > systemctl list-dependencies --after systemd-networkd > > my one outputs this: > > tamer@tux ~ $ systemctl list-dependencies --after systemd-networkd > systemd-networkd.service > ● ├─-.mount > ● ├─system.slice > ● ├─systemd-journald.socket > ● ├─systemd-networkd.socket > ● ├─systemd-sysctl.service > ○ ├─systemd-sysusers.service > ○ ├─systemd-udev-settle.service > ● ├─systemd-udevd.service > ○ └─network-pre.target > Mine is: aztlan ~ # systemctl list-dependencies --after systemd-networkd systemd-networkd.service ● ├─-.mount ● ├─system.slice ● ├─systemd-journald.socket ● ├─systemd-networkd.socket ● ├─systemd-sysctl.service ○ ├─systemd-sysusers.service ● ├─systemd-udevd.service ● └─network-pre.target ○ └─iptables-restore.service In one machine, and kodi ~ # systemctl list-dependencies --after systemd-networkd systemd-networkd.service ● ├─-.mount ● ├─system.slice ● ├─systemd-journald.socket ● ├─systemd-networkd.socket ● ├─systemd-sysctl.service ○ ├─systemd-sysusers.service ● ├─systemd-udevd.service ○ └─network-pre.target In another. The only difference I see is the systemd-udev-settle.service, do you have it enabled it? What systemd-* services do you have enabled? I have: aztlan ~ # find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/multi-user.target.wants/systemd-networkd.service /etc/systemd/system/sockets.target.wants/systemd-networkd.socket and kodi ~ # find /etc/systemd/system -name "systemd-*" -type l /etc/systemd/system/sockets.target.wants/systemd-networkd.socket /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service /etc/systemd/system/multi-user.target.wants/systemd-resolved.service /etc/systemd/system/multi-user.target.wants/systemd-networkd.service Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Tue, Sep 7, 2021 at 2:35 PM Tamer Higazi wrote: > > [Unit] > After=systemd-udev-settle.service > I think that's the problem; in my machines, that service is never run. When did you add the override? What happens if you delete it? (Also remove the [Link] section in your .network file). Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Tue, Sep 7, 2021 at 1:03 PM Tamer Higazi wrote: > Dear Dr. Valdés, > I am sorry to tell you that the result still remains the same. > That is weird. I am also not a systemd expert > but somebody in the mailing list told me, that the "order" of process > might not be right ? > I'm not an expert either, but I use systemd in all my desktops, laptops and servers (3 desktops, 2 laptops and several servers). I have never had any trouble with systemd-networkd.service. Drop-In: /etc/systemd/system/systemd-networkd.service.d > └─override.conf > I hadn't seen that. What's included in the override? cat /etc/systemd/system/systemd-networkd.service.d/override.conf Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Mon, Sep 6, 2021 at 4:01 PM antlists wrote: [...] > > /etc/systemd/network/20-wirded.network: > ^ > > Typo? Unimportant? Significant? > The filename is only used to lexicographically sort the .network files; it doesn't make a difference. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Mon, Sep 6, 2021 at 2:46 PM Tamer Higazi wrote: [...] > /etc/systemd/network/20-wirded.network: [...] That looks fine to me. for enp7s0 there is no other network file. > That is as it should be. I think with THIS systemd version, the whole problem is, that the > configuration will be done before the devices are made and renamed to > enp6s0 and enp7s0. > I don't think so; the renaming of ethernet devices happens really early, and systemd-networkd detects it automatically (journal -b -g enp6s0 should show "enp6s0: renamed from eth0" as first log line, and then systemd-networkd detecting it). The problem is, how to solve it > Try adding this to /etc/systemd/network/20-wirded.network, at the end: [Link] RequiredForOnline=false but this is a workaround; everything should work automagically. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Sun, Sep 5, 2021 at 1:36 PM Tamer Higazi wrote: [...] > × systemd-networkd-wait-online.service - Wait for Network to be Configured > Loaded: loaded > (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; > vendor preset: disabled) > Active: failed (Result: exit-code) since Sun 2021-09-05 20:22:19 > CEST; 11min ago > Docs: man:systemd-networkd-wait-online.service(8) > Main PID: 984 (code=exited, status=1/FAILURE) > Sep 05 20:20:18 tux systemd[1]: Starting Wait for Network to be > Configured... > Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred > while waiting for network connectivity. > Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service: > Main process exited, code=exited, status=1/FAILURE > Sep 05 20:22:19 tux systemd[1]: systemd-networkd-wait-online.service: > Failed with result 'exit-code'. > Sep 05 20:22:19 tux systemd[1]: Failed to start Wait for Network to be > Configured. > There's your problem: systemd-networkd-wait-online.service is timing out: Sep 05 20:22:19 tux systemd-networkd-wait-online[984]: Timeout occurred while waiting for network connectivity. The systemd-networkd-wait-online service runs relatively early and waits for *ALL* interfaces it is aware of to be fully configured or failed[1], so it probably one of your interfaces is taking too long to be ready. Between timing out and you restarting systemd-networkd.service, the interface reaches the ready state (or fails), and systemd-networkd-wait-online.service doesn't time out anymore. By your logs, you have two ethernet interfaces: enp6s0 and enp7s0, the latter not in use. Do you .network files in /etc/systemd/network/ or /run/systemd/network/? Any changes (uncommented lines) in /etc/systemd/networkd.conf? Regards. [1] https://man7.org/linux/man-pages/man8/systemd-networkd-wait-online.8.html -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] network do not come up after booting, only manual reloading (systemd-networkd)
On Sun, Sep 5, 2021 at 2:46 AM Tamer Higazi wrote: > Hi people, > > After upgrading my gentoo box i see a new behavior, that my machine > after boot doen't configure my network. My network is configured through > systemd-network, > > Only if I manually after login execute: "systemctl restart > systemd-network" it gets configured. > Can somebody tell me why this is the case and how to fix it ? > Could you please tell us the output of: systemctl status systemd-networkd.socket systemd-networkd-wait-online.service *before* you restart systemd-networkd.service? Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] X11 without udev/eudev
ut find out where the > new /dev file is and reopen and reinitialize it. > That is what udev+libinput solves, *exactly*. You answered yourself why it is needed *IN GENERAL* (not in your particular case). What you say about complexity etc., is true; but most developers care about servicing the *majority* of users (in this case, USB and Bluetooth users included), so if you want to use their software, that means accepting udev. If you don't like it, you need to stop using their software and either write your own or find someone else who does it (again, check the alternatives). In any case, complaining is useless: most sane developers always want to cover the majority of users. That's why udev is mandatory in most major and medium distros; in Gentoo it is used by default (BTW, they are preparing the deprecation of eudev in Gentoo[2]). Regards. [1] https://man7.org/linux/man-pages/man7/udev.7.html [2] https://archives.gentoo.org/gentoo-dev/message/dff4bf35636efef95f6d7926823b4e8d -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] X11 without udev/eudev
On Sun, Aug 22, 2021 at 6:18 PM antlists wrote: [...] > What you're missing, is that this code IS NOT USED. > > The OP wants to delete a load of code from his system precisely to > ELIMINATE vulnerabilities. If the code ain't there, it don't need fixing. > Where do you get that impression from? The OP needs handling keyboard and mouse (as per his first email), and to do that in Linux these days, you basically need udev, because xf86-input-mouse and xf86-input-keyboard are going the way of the dodo. Where does the "ELIMINATE vulnerabilities" come from? The OP is just complaining that to use keyboard and mouse, now he needs udev. My point is that it's not his call; it's the call of the developers of the software that he decided to use. > Yes I take your point, but bloat is bloat, and bloat is a liability. > There is no bloat; the developers *need* to handle the dynamic hardware case *and* the static hardware case. With udev, they handle both; otherwise there would be two code routes: one for static and another for dynamic hardware. THAT would be bloat; using udev solves all the cases and bloat is averted. Is exactly the contrary of what you are saying. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] X11 without udev/eudev
On Sun, Aug 22, 2021 at 3:32 PM wrote: [...] > I'll be looking into that, but on some level, why should I be forced to > go around udev. Can't programs be compiled without udev today... > Yes, they can, if you (or someone else) write the necessary code, debug it, maintain it and keep it up to date and fix vulnerabilities and other errors that inevitably will appear, as it does with every piece of software. > Udev should be an optional deamon, utilized when the local administrator > decides to do so. Wrong: the use of udev is to be decided by the developers of the code that uses it. If you don't like it, then you write your own. The code is free and open. Udev solves a very real problem, because most modern PCs have dynamic hardware; we connect and disconnect multiple devices from it all the time, and the vast majority of users prefer it when it simply works automagically. Moreover, it *also* works with static hardware, so it hits two birds with one stone. You want developers to write code that only benefits the simplest and most boring case: a PC that never changes hardware. Any sane developer will obviously prefer to depend on udev, which solves every case and it has the most users (and therefore feedback for detecting and correcting bugs, and also to ask for new features and capabilities). > I don't want things to automatically pop up unless I say so. > Then write yourself the corresponding software, or pay someone to do it. Otherwise, complaining (while cathartic and the preferred hobby of most of the internet) is completely useless. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] 32GB RAM and Swap
On Fri, May 1, 2020, 14:50 Raphael MD wrote: > Hello! > > Could I turn my Linux swap off. > I have 32 GB of RAM memory, I suppose my system don’t need swap, because > I’vea lot of RAM, is this true? > > Thanks > I have 3 desktop machines with 32 GB of memory. In all 3 I still have swap (32 GB, I stopped using the "twice the amount of RAM" rule years ago). I don't think I have ever used one single byte from the swap; it always sits with "0 bytes used" when I check top. So I don't think you need the swap; I keep using it in case I need to ever hibernate the machines, bit I never do. Also, it's always on the mechanical disks, so it's dirty cheap. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] USB sound
On Wed, Apr 29, 2020 at 10:24 AM Peter Humphrey
wrote:
[...]
> Have I to go the PulseAudio route after all?
>
Hi Peter; I had refrained to comment in this thread since I had nothing to
contribute regarding your original question. However, since you now ask if
you should go to the PA route, I'm going to put my two cents on the issue.
I moved to PulseAudio with Gnome 2.26 more than a decade ago, in 2009. I've
some small issues with it through the years, but the worst case scenario
always has been resolved with a quick "pulseaudio -k", and even that has
happened four or five times in all these years. Also, I do not work with
audio professionally, but I do use several audio sources and sinks
(including Bluetooth headphones and USB microphones) and since the
quarantine I had to record video for online courses, using the USB
microphone integrated to my webcam. PulseAudio usually just works™,
specially if you use its own tools, like pavucontrol.
(It also works incredible well with flatpak and Valve Proton in Steam,
which allows me the play Windows games in Linux almost flawlessly.)
For me, the most annoying thing I had to do with PulseAudio has been that
sometimes I need to plug and unplug a headphone jack connector so the sound
automatically goes through it. That's it.
However this easy of use (specially with plug-and-play) comes with a cost:
you are surrendering control of the audio stack to PulseAudio *completely*.
You can configure it inside the confines that PulseAudio itself defines;
but if you enable PulseAudio and you try to fight it, you ARE going to
lose. This is a feature; not a bug.
I use my Gentoo machines to work (and sometimes to play a video game); not
to learn the intricacies of ALSA. I'm fine with PulseAudio making the shots
regarding anything sound related; it's the same reason I use Gnome and
systemd. But I know a lot of people (specially Gentoo users) have *very*
strong feelings about the control they believe they have over the software
they use and that they usually didn't wrote nor contributed to it. As a
professional programmer and a college programming professor, I like to
think I know better.
If you want to keep 100% control on the audio in your system (or to believe
you have said control), in my experience what will happen is exactly your
current scenario: the moment your hardware is a little more dynamic than an
integrated or PCIe sound card, everything goes off the rails. Then is time
for the litany of searching the web and asking for help until it kinda
works, sometimes, except on Wednesdays and when it's raining... and then
you change a little your system and you need to start all over again.
Or you can try to trust a piece of software specifically written to handle
this kind of scenarios. But then you have to truly trust it; and with the
knowledge that it *WILL* sometimes fail, because no software is perfect.
I choose the second.
Now some concrete advise, if you choose to go the PulseAudio route:
1. Remove your user from the audio group.
2. Delete any /etc/asound* files
3. Delete any ${HOME}/.asoundrc file
4. Don't modify any file on /etc/pulse
It should just work™. Otherwise there is a piece of software or user/system
configuration trying to fight PulseAudio. That will not turn out OK.
Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] enlightenment experience
On Fri, Aug 16, 2019 at 6:58 AM Raffaele Belardi wrote: > I'm considering switching from Gnome to Enlightenment. Looks very nice but > has very few > native applications, I was wondering why since it's been around since '97. > Then I found > this [1] and, as a sw programmer, got a little bit scared... > > Are there any Gentoo enlightenment users who could share their experience > with this DE? > Some native (EFL) applications are available only via the > enlightenment-live overlay, how > stable is this? > I need a session manager to temporarily switch user without logging out, > suggestions? > I'd go with openRC, non-wayland if possible. I never got accustomed to > systemd. > Have you considered using Xfce? I think it has all the features you want, and it's pretty lightweight. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: USE flag 'split-usr' is now global
On Tue, Aug 6, 2019 at 5:54 PM Grant Taylor < gtay...@gentoo.tnetconsulting.net> wrote: [...] > > Arguing against this trivial (and IMHO, elegant) solution is tilting at > > windmills. Specially if it is for ideological reasons instead of > > technical ones. > > Please clarify what "this trivial solution" is. Are you referring to > initramfs / initrd or the 'split-user' USE flag? The trivial solution (IMO) is to use an initramfs. Rich gave a much more elaborated answer. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: USE flag 'split-usr' is now global
On Mon, Aug 5, 2019 at 9:38 PM Grant Taylor < gtay...@gentoo.tnetconsulting.net> wrote: [...] > I don't have any current first hand experience with /usr being a > separate file system without using an initramfs / initrd. So I'm going > to have to take what you, and others, say on faith that it can't > /currently/ be done. But I've got to say, that I find that idea > disturbing and highly suspicious. If it's computable it can be done, of course. Therefore it can be done, currently. I don't think nobody has said it absolutely cannot be done. The thing is: 1. How much work implies to get it done. 2. Who is gonna do said work. The answer to 1 is "a lot", since (as someone mentioned in the thread) it involves changing not only the init (nevermind systemd; *ALL* init systems), but all applications that may require to use binaries in /usr before it's mounted. The answer to 2 is, effectively, "nobody", since it requires a big coordinated effort, stepping into the toes of several projects, significantly augmenting their code complexity for a corner case[1] that can be trivially be solved with an initramfs, which it just works. Arguing against this trivial (and IMHO, elegant) solution is tilting at windmills. Specially if it is for ideological reasons instead of technical ones. Regards. [1] I firmly believe that's the situation nowadays. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: Experiences with Flatpak?
On Fri, Jan 25, 2019 at 1:30 PM Grant Edwards wrote: > On 2019-01-25, Canek Peláez Valdés wrote: > > On Fri, Jan 25, 2019 at 12:48 PM Grant Edwards < > grant.b.edwa...@gmail.com wrote: > >>[...] > >> > >> Is it practical to use flatpak apps on Gentoo? > > > > In my experience is amazing. Gentoo sometimes takes a lot of time to > > stabilize some packages; flatpak usually have them immediately. For > nightly > > builds is even better, since you don't need to pollute your stable > system. > > [...] > > > Also, I run systemd; I *think* it's necessary to run flatpak. > > Ouch. I don't, so that's a bit of a blocker for me. > I'm not sure anymore; flatpak doesn't need systemd and ostree has it as an optional dependency[1]. It may work with OpenRC. [1] https://github.com/fosero/flatpak-overlay/blob/master/sys-fs/libostree/libostree-2019.1.ebuild#L37 Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: Experiences with Flatpak?
On Fri, Jan 25, 2019 at 1:17 PM Nikos Chantziaras wrote: > On 25/01/2019 20:48, Grant Edwards wrote: > > But, flatpak isn't in the standard portage tree, so you have to use an > > overlay or local repo. > > > > This is beginning to look like a lot of work. > > > > Is it practical to use flatpak apps on Gentoo? > > I was using it for a while. Not anymore. > > It does exactly what it says on the box. However, GUI applications > installed in flatpak will completely ignore your desktop settings. > flatpak comes with its own gtk/qt/gnome/kde libraries and its own > completely separate settings for the desktop environment. > > This is why I'm not using it anymore. GUI apps look like ass. > That's weird; they look fine for me [1,2]. As yo say, they have different configurations (every application runs in an individual container), but the both look normal. Regards. [1] https://aztlan.fciencias.unam.mx/~canek/inkscape-gentoo.jpg [2] https://aztlan.fciencias.unam.mx/~canek/inkscape-flatpak.jpg -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Experiences with Flatpak?
On Fri, Jan 25, 2019 at 12:48 PM Grant Edwards wrote: > I'm shopping for an IMAP email client that does a decent job of > handling HTML. After doing a bit of reading I decided the first one > to try would be Geary. > > Bzzt! > > Though it's in the portage tree unamasked and marked stable, you can't > actually _build_ it, since it requires an old, vulnerable version of > webkit-gtk that _isn't_ in the portage tree. > > So I thought maybe I'd try it out using a flatpak "package": > > https://flathub.org/apps/details/org.gnome.Geary > > But, flatpak isn't in the standard portage tree, so you have to use an > overlay or local repo. > > This is beginning to look like a lot of work. > > Is it practical to use flatpak apps on Gentoo? > In my experience is amazing. Gentoo sometimes takes a lot of time to stabilize some packages; flatpak usually have them immediately. For nightly builds is even better, since you don't need to pollute your stable system. I'm using git://github.com/fosero/flatpak-overlay.git (I don't use layman) The only keyworded package I have is flatpak-builder; everything else is stable. I regularly run in flatpak Inkscape, GNOME Builder, Glade, Pitivi, and Steam (Cities: Skylines runs really well in Linux); but you can use it to test new software too. It's trivial to install, update and remove software. With all these packages, my flatpak repositories are using 13Gb, which is nothing for my hard drive; but it will duplicate libraries from your regular Linux distribution. Also, I run systemd; I *think* it's necessary to run flatpak. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] A question regarding building Gentoo and UEFI vs Non UEFI
On Mon, Nov 19, 2018 at 10:51 PM Andrew Lowe wrote: > > Dear all, > In the past I had a non UEFI motherboard setup for my Gentoo machine. > The motherboard started failing so I took the opportunity to replace the > motherboard & CPU and also to buy a new SSD thingy to become the home of > my Gentoo install. > > I'm currently running, on a day to day basis, the older hard disk, on > the new motherboard, but want to speed up the process of getting the new > SSD set up so I can swap over. Rather than booting into the SSD, > starting an emerge, and walking away, in other words, making my machine > useless for any number of hours, am I correct that there is no problem, > vis a vis, old hard disk built on non UEFI machine Vs new SSD built on > UEFI machine, of chrooting[1] from the old environment into new > environment and doing the building whilst I"m doing something productive > within the old environment? > > I just have this little niggling doubt, probably baseless, in the back > of my mind that there maybe something that may cause a problem for the > newly built stuff due to it not being natively booted in UEFI or > something like that when it was built. > > Anyone built their new machines like this who can allay my, probably > baseless, fears? I've done this exact same scenario two or three times by now. However, I don't recompile anything, I just rsync the old drive into the new one, and then I chroot (or, more often, I systemd-nspawn) into it and update the old configuration where necesary. Unless you change from Intel to AMD it should be fine (and even then it could be fine, depending on your CFLAGS). Also, have a live USB around to boot into it for emergencies. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] /boot filesystem, SSDs, TRIM
On Wed, Aug 22, 2018 at 10:58 PM Adam Carter wrote: > > For a long time people recommended ext2 for /boot. The Gentoo wiki still does. Is there any compelling reason to use ext2 for /boot (on a system whose other filesystems are ext4) these days? AFAIK for systems that have /boot on an SSD, ext4 makes more sense due to discard support, and for non-SSD it doesn't matter either way. Have I missed something? AFAIU, UEFI systems need a boot partition, and it has to be VFAT. Most motherboards support a "legacy mode" to boot using the MBR; but it will eventually go away, and good riddance; UEFI is so much easier and saner to use. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] is anyone using Nouveau graphics driver ?
On Mon, Jul 23, 2018 at 9:18 PM Davyd McColl wrote: > > Definitely Nouveau. I tried (really hard) to stick to proper open-source > all the way. But the culprit became abundantly clear when I switched to > proprietary and never again had a lockup. Ever. > > And there are plenty of other users on the interwebs with the same sad story. That may very well be true, but it's certainly not the rule. I've been using Nouveau on Linux on a GTX 960, and I haven't had a single problem with GNOME. Perhaps the combination is the problem; nouveau + Plasma may have issues. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] is anyone using Nouveau graphics driver ?
On Mon, Jul 23, 2018 at 8:37 PM Davyd McColl wrote: > > Dr Valdés, I'd really like to know more. Are you using a compositor; what desktop environment? I use GNOME 3.24.2, with gnome-shell (which uses a compositor). Also, I run Wayland, not "classic" X. > If I had had the positive experience you speak of, I would adopt Nouveau in a heartbeat. Nvidia has clearly shown their lack of interest in the Linux community by shunning higher console resolutions, leaving a display port blanking bug unresolved for about 2 years and haphazardly fixing bugs with features reported to be working on miscellaneous branches of the driver, unreleased to the unwashed masses (read up about Vulkan support, esp vs Rise of the Tomb Raider). I do not play modern AAA games on Linux. Nouveau works with 2D acceleration and basic OpenGL, but I don't think it can handle something like Tomb Raider or Mad Max. > I would accept a framerate hit for an open-source driver. But rebooting my main machine daily is off the cards. If I wanted that, I'd use that other OS. I develop on that other OS, but my development machine can be rebooted any time. My home machine has shit to get done. Nouveau (in my experience) is rock solid and fast for desktop use. However, it doesn't work for gaming, AFAIK. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] is anyone using Nouveau graphics driver ?
On Mon, Jul 23, 2018 at 12:17 PM Philip Webb wrote: [...] > (1) What are people's experiences with Nouveau ? > -- does it work easily with various kernels ? Usually without any intervention from my part. > -- does it manage graphics stably & reliably ? Much more than with the NVidia binary driver, at least in my case. > -- I don't do much with video (a few newsreels) & don't use sound. I watch video (both desktop and YouTube), listen to music and edit some video. Also I edit some images with Inkscape and/or Gimp. And normal desktop use. > (2) If I install it, how do I switch between Nouveau & Nvidia ? Basically "eselect opengl set xorg-11" or "nvidia". Also, for NVidia you must add a Xorg.conf snippet in /etc/X11/xorg.conf.d/ so you set the NVidia device for the binary driver. > (3) Sadly, I didn't make a Quickpkg of the Nvidia version I was using > when my scanner was working with Gentoo (last time 180626). > I have the distfiles, but not the ebuilds : > is there anywhere I can find ebuilds for Nvidia-Drivers 390.42 390.48 ? Git to the rescue: https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-drivers/nvidia-drivers?id=9a52478a2329ffce09c4c1a400934499fcb5ae93 I should mention that I use GNOME. The nouveau drivers have been working like a charm for GNOME for several years. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] secure programing language?
On Tue, May 8, 2018 at 4:33 PM <mad.scientist.at.la...@tutanota.com> wrote: > > So are there currently any languages (currently in use/supported) designed to avoid the problems with C and other languages? > > Something with strong types and provisions for automatic input validation beyond typing, i.e. range limitation? > > Something that compiles, something that doesn't self optimize (math may be good, but just like encryption the implementation can be flawed/exploitable due to various errors). Because you can't validate a moving target. > > something that strongly isolates data from code, something that protects the heap and stack aggressively (other than just os implemented mechanisms like stack canaries). > > Any suggestions? I'm going to be picking up programming again and I'd greatly prefer spending my time using a language that has security built in rather than depend on the application programmer adding protections after the fact. > > I'll still have to learn C as well, so I can understand/modify existing code but I'd like to be as proactive as possible about security and reliability in what I write. And again, something that compiles. Not specificly looking at writing web apps per say, though i'd also be interested in any well secured/proactive languages for some internet/LAN usage. I think Go and Rust would fit the bill. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] chromium build failure
On Wed, Jan 31, 2018 at 1:29 PM, allan gottlieb <gottl...@nyu.edu> wrote:
[snip]
> I have two questions, one trivial, one hopefully easy.
>
> 1. (trivial) In your recipe did you mean "rsync", not "sync"?
I sync ("emerge --sync") only one machine, and then I rsync from there to
my other computers. After the rsync is done, you need to do "emerge
--metadata" in the recipient machine (--sync does that for you
automatically).
> 2. I have a number of quickpkgs built. Is it needed that
>they all be updated and some removed or can I just do
>the following command
>
>rsync -Pvase ssh machine1:/var/portage/packages/www-client \
> /var/portage/packages
>
>Notes: I use /var not /usr for portage
> machine2 has no dir /var/portage/packages/www-client
I honestly don't know. There is a /usr/portage/packages/Packages with a lot
of meta information, and I'm not 100% sure whether is absolutely required.
Then again, creating binary packages is so fast that I usually delete
/usr/portage/packages after updating my non-compiling machines. I know of
people who maintain a large repository of binary packages (they can be
built automatically with FEATURES="buildpkg" in make.conf), but I just
create them when needed.
Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] chromium build failure
On Wed, Jan 24, 2018 at 10:11 PM, allan gottlieb <gottl...@nyu.edu> wrote: > > I ran the build failed twice, each time with MAKEOPTS="--jobs=1" and the > build logs are essentially identical. After about 12 hours compiling and > 36MB of build.log, the error shown below occurs > > I have two laptops with *very* similar gentoo distributions. The newer > machine had a successful build first try. The second older (4 years) > machine had both failures. Each machine has profile > default/linux/amd64/17.0/desktop/gnome/systemd If the USE flags for chromium on both machines are the same, simply create a binary package from the machine that already built it. machine1: $ quickpkg --include-config=y www-client/chromium machine2 $ sync --delete -Pvase ssh machine1:/usr/portage/packages/ /usr/portage/packages/ $ emerge --nodeps -1Kv www-client/chromium I have two powerful desktop computers (home and office) and a laptop. Their USE flags are identical; I just compile in one of them and generate binary packages for the other two. It helps (but it's not 100% required) if the /usr/portage tree is identical (I sync only with one and rsync the others, followed by emerge --metadata). Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: Is gnome becoming obligatory?
On Sun, Dec 10, 2017 at 3:55 PM, Jorge Almeida <jjalme...@gmail.com> wrote: [...] > Yes, it seems appropriate for Windows refugees and linuxers suffering > from Apple-envy. When I said I didn't understand why it would be > useful, I meant that the documentation in the site is all but clear > about the goodness of its product. Lots of freedesktop/dbus > mumbo-jumbo, though. The documentation for udisks is not intended for end-users; it's intended for developers that whish to use its benefits for their projects, GNOME and KDE included. When used right (which implies a good integration done by the distro), the software depending on it just works™, which makes documentation for the end user program also redundant. You just don't notice udisks, it's quietly running in the background doing its thing without taking either much disk space, memory, nor CPU usage. For the *general case*, its benefits outweigh the almost negligible amount of resources it consumes (BTW, build time of udisks in Gentoo is about 21 seconds). Up to a point, the same can be said about systemd; although many of its programs can be and are used by end users, most of it is for distro builders, programmers and administrators. And having a couple of Gentoo boxes running Apache doesn't make anyone an administrator, BTW. That's why most of Gentoo systemd users (and we are *a lot*; Gentoo has great systemd support with several Gentoo devs collaborating with the project) usually just ignore this kind of threads. Most of the time is a lot of people which don't use it badmouthing a really cool piece of technology that has been adopted by all large (and heavily used) Linux distributions because the people that understand its technical merits realize that, for the *general case*, its benefits outweigh whatever costs (in many cases imaginary) it may have. And besides, for us it just works™, quietly running in the background. Just my two cents. I will not answer any reply to my little contribution to this thread; but of course don't hesitate to explain to me why I'm completely wrong, or a Lennart fanboi, or that I don't know what I'm talking about. I just will not partake in such a joyful and enlightening "discussion" (sadly the same conclusion I have arrived for the lasts few years regarding this mailing list). Enjoy your echo chamber. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: Systemd
On Sat, Nov 4, 2017 at 12:17 PM, Nikos Chantziaras <rea...@gmail.com> wrote: > > On 04/11/17 18:15, siefke_lis...@web.de wrote: >> >> I have a short question to systemd. I would like to ask your experience >> in the changeover. Was it easy? Were there problems? >> Change or reinstall? What mean the profis here? > > > I did both. Changed one system to systemd, re-installed one from scratch with systemd. > > Both worked. The only problem I have with systemd is that it's unable to reliably restore the ALSA mixer volumes/settings on startup. It fails 50% of the time. Which is very annoying, but not the end of the world. Do you have PulseAudio installed? What's the output of 'systemctl status alsa-restore.service'? Do you have /var/lib under a "special" (RAID, LUKS, whatever) partition? Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: systemd: "local system does not support BPF/cgroup based firewalling"
On Sat, Oct 28, 2017 at 1:44 PM, Nikos Chantziaras <rea...@gmail.com> wrote: > > There is no such kernel option. Yes, there is[1]. However, there is no such option for kernel version 4.9[2], although there is for 4.10[3]. I think that's the problem, for using the firewall BPF options of systemd, you'll need to use kernel version >= 4.10. Regards. [1] https://github.com/torvalds/linux/blob/master/init/Kconfig#L848 [2] https://github.com/torvalds/linux/blob/v4.9/init/Kconfig [3] https://github.com/torvalds/linux/blob/v4.10/init/Kconfig#L1157 -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd: "local system does not support BPF/cgroup based firewalling"
Do you have CONFIG_CGROUP_BPF enabled? Regards. On Sat, Oct 28, 2017 at 1:03 PM, Nikos Chantziaras <rea...@gmail.com> wrote: > I'm getting these at startup: > > systemd[1]: File /lib/systemd/system/systemd-journald.service:33 > configures an IP firewall (IPAddressDeny=any), but the local system does > not support BPF/cgroup based firewalling. > systemd[1]: Proceeding WITHOUT firewalling in effect! > systemd[1]: File /lib/systemd/system/systemd-udevd.service:32 configures > an IP firewall (IPAddressDeny=any), but the local system does not support > BPF/cgroup based firewalling. > systemd[1]: Proceeding WITHOUT firewalling in effect! > systemd[1]: File /lib/systemd/system/systemd-logind.service:34 configures > an IP firewall (IPAddressDeny=any), but the local system does not support > BPF/cgroup based firewalling. > systemd[1]: Proceeding WITHOUT firewalling in effect! > > What do I need to make this work? I found this: > > https://github.com/systemd/systemd/issues/7188 > > But CONFIG_BPF_SYSCALL is enabled and I still get that message. > > This is on kernel 4.9.59 with systemd 235. > > > -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Why I can't I build systemd without ipv6?
On Fri, Oct 13, 2017 at 12:29 PM, Daniel Frey <djqf...@gmail.com> wrote: > > I switched ISPs a couple months back and have been struggling with networking issues (not LAN, just WAN.) > > I have discovered that something is broken with my ISP's ipv6 support, every time I go to a website there's a 10-second delay. When syncing portage today I saw what the delay is: apparently it tries ipv6 twice, fails, then resorts to ipv4 which works fine. > > Most of my systems now have ipv6 support removed, and viola! no more delays. > > Except for the three systems I have that run systemd. I went in the kernel config to disable ipv6, and it won't let me - looking at the dependency list, it's systemd blocking this. > > So *why* on earth is it a dependency when (from what I've been reading after discovering this) many ISPs don't seem to support it properly yet? > > And is there a way to build systemd without ipv6? Or am I going to have to revert these three systems back to openrc? Have you tried to boot the systems with the "disable_ipv6=1" kernel parameter? Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gentoo on SSD
On Sat, Sep 23, 2017 at 2:04 PM, Stefano Crocco <po...@stefanocrocco.it> wrote: > > Hello to everyone, > I just bought a 250 GB SSD and I'm planning to install Gentoo on it. I've read > the Gentoo Wiki page on this and searched Google for hints on this, but since > I found out that much information was either contradictory or outdated, I'm > asking anyone with first-hand experience on this for advice. > > My system is as follows: > > - 250GB SSD > - 1TB HDD > - 16GB RAM > > I'm planning to partition the SSD this way: > > - 100 GB -> / (on my current system, / is about 70GB) > - 100 GB -> /home > - 16 GB -> swap (mainly for hibernation) > - 200 MB -> /boot > > /var/tmp/portage should go into a tmpfs (12GB). > > I've read that someone suggested putting also /tmp on a tmpfs. Right now, on > my system /tmp is less than 100 MB, so I believe this should cause no > problems, but is it necessary? > > Large files, such as Steam games and maybe distfiles should instead go on the > 1TB HDD. > > I have some doubts about the swap partition. With 16 GB of RAM I shouldn't > usually need swap except for hibernating (that's the reason I'm putting it on > the SSD); however, I fear that compiling some large packages could fill all > that space. Would it be bad to have the swap partition on the SSD used this > way every now and then? Should I create another swap partition on the HDD and > give it higher priority? > > What do you think? Do you have any advice on how to best set up such a system? I use a similar setup. Several top-level directories in my $HOME are bind mounts to a large mechanical drive. My swap (16GB) is on that drive also. I've found that 100MB is enough for the EFI /boot partition (but I clean old kernels immediately after updating). For the /tmp I use tmpfs (I use the size=100% option), and then in /etc/portage/make.conf I have: PORTAGE_TMPDIR="/tmp" This way I fully use /tmp when compiling large packages, and don't wear down my SSD. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] wireless software config problem
On Wed, Sep 6, 2017 at 6:31 PM, allan gottlieb <gottl...@nyu.edu> wrote: > > My system runs gnome3/systemd. I use NetworkManager, which is mostly > working fine. > > At work the desired network is named "nyu". The sysadmins say I need to > change at least one security parameter. When I open the gui it shows > the network configuration parameters (by clicking the gear) and lets me > select different values. However the "Apply" button never becomes > active so I can only "Cancel". > > If I try to select the "nyu" network it asks for the password, which I > know and enter. I then click the appropriate button (something like > "apply" or "ok"). As expected the window goes away but I am not > connected and the window reappears. > > A "tip" from the sys admins at work is to somehow tell my system to > forget all it knows about the network "nyu", but neither I nor they know > how to do it (they don't "fully support" linux). I would try this: 1. Select the system menu (top right corner) 2. Select settings (lower left corner of the menu) 3. Select Network 4. Click the gears icon for the wireless network 5. Select the "Reset" option (last option available) 6. Click the "Forget" button This should allow you to start from the beginning. You should not need to muck around around with permissions, it should Just Work™. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Rename /dev/nvme0n1 to /dev/sda
On Mon, Sep 4, 2017 at 6:26 AM, J. Roeleveld <jo...@antarean.org> wrote: > On 3 September 2017 20:11:51 GMT+02:00, "Canek Peláez Valdés" < can...@gmail.com> wrote: [ ... ] > >The label by itself works at boot since it's just another kernel > >parameter; > >for example in my latop (that uses NVME, by the way) uses the following > >in > >the kernel command line: "root=LABEL=Dell". > > Since when does the kernel support labels? Last time I checked, you need an initramfs to make that work. You are absolutely right; the kernel only supports "PARTUUID=" out-of-the-box (/usr/src/linux/init/do_mounts.c:218), the "LABEL=" ids are implemented by the initramfs, dracut in my case (/usr/lib/dracut/modules.d/98dracut-systemd/rootfs-generator.sh:87). The "LABEL=" id gets translated to the corresponding /dev/disks/by-label link, so those are the ones that should be used all the time. Thanks for the clarification. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Rename /dev/nvme0n1 to /dev/sda
On Sun, Sep 3, 2017 at 7:59 PM, Grant <emailgr...@gmail.com> wrote: > > >> My new laptop uses /dev/nvme0n1 instead of /dev/sda which conflicts > >> with the script I use to manage about 12 similar laptops running > >> Gentoo. Is there a udev method for renaming the disk that will work > >> well with any USB disks that happen to also be attached? > >> > >> crw--- 1 root root 252, 0 Aug 31 11:34 /dev/nvme0 > >> brw-rw 1 root disk 259, 0 Aug 31 11:34 /dev/nvme0n1 > >> brw-rw 1 root disk 259, 1 Aug 31 11:34 /dev/nvme0n1p1 > >> brw-rw 1 root disk 259, 2 Aug 31 11:34 /dev/nvme0n1p2 > > > > Isn't so much easier to use labels? Those are automatically available on > > /dev/disk/by-label, and you can use them in basically any type of partition, > > including Windows (NTFS and vfat) and swaps. > > > Do labels work with root= in grub and stuff like dd, fdisk, and mkfs? The label by itself works at boot since it's just another kernel parameter; for example in my latop (that uses NVME, by the way) uses the following in the kernel command line: "root=LABEL=Dell". For all the other utilities you mention the label by itself probably doesn't work, but the links in /dev/disk/by-label are just symlinks to the corresponding disks and partitions, so every single Unix utility works with them. My links are like so: dell ~ # ll /dev/disk/by-label/ total 0 lrwxrwxrwx 1 root root 15 Aug 29 06:20 Dell -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Aug 29 06:20 EFI -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Aug 29 06:20 Swap -> ../../nvme0n1p3 And so /dev/disk/by-label/Dell is just the second partition of the first NVME disk (or chip, or wathever). They work with anything, execept with fdisk because there are no labels for whole disks, only for partitions. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Rename /dev/nvme0n1 to /dev/sda
On Fri, Sep 1, 2017 at 11:10 AM, Grant <emailgr...@gmail.com> wrote: > > My new laptop uses /dev/nvme0n1 instead of /dev/sda which conflicts > with the script I use to manage about 12 similar laptops running > Gentoo. Is there a udev method for renaming the disk that will work > well with any USB disks that happen to also be attached? > > crw--- 1 root root 252, 0 Aug 31 11:34 /dev/nvme0 > brw-rw 1 root disk 259, 0 Aug 31 11:34 /dev/nvme0n1 > brw-rw 1 root disk 259, 1 Aug 31 11:34 /dev/nvme0n1p1 > brw-rw 1 root disk 259, 2 Aug 31 11:34 /dev/nvme0n1p2 Isn't so much easier to use labels? Those are automatically available on /dev/disk/by-label, and you can use them in basically any type of partition, including Windows (NTFS and vfat) and swaps. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] certbot confusion
On Sat, Aug 26, 2017 at 1:40 AM, Ian Zimmerman <i...@very.loosely.org> wrote:
>
> I don't understand the letsencrypt certbot renewal process, specifically
> the hooks.
>
> I have two certificates: one for webserver, one for mailserver. I got
> them only very recently so I until now the renewal cronjob has always
> been a no-op, but the real thing will happen very soon. When it does,
> presumably I need to have both daemons restarted so that they read the
> renewed certificates. So, how do I do this? Right now my cronjob is
> just
>
> certbot renew -n --standalone --preferred-challenges tls-sni
>
> which should renew any and all certificates when they're "close" to
> expiring. But the documentation doesn't say if I can have multiple
> --pre-hook and --post-hook options and what the semantics would be. The
> closest it comes is:
>
> When renewing several certificates that have identical pre-hooks, only
> the first will be executed.
>
> which doesn't make any sense: what does it mean for a certificate to
> "have" a pre-hook? The pre-hook is just there on the command line,
> there is no association with a particular certificate that a machine
> could infer.
>
> The cop-out solution is to have a single pre-hook and a single
> post-hook, which stop (resp. start) both daemons, but that is ugly. How
> do people handle this?
I just need to restart apache, so my daily cron job is:
certbot renew --standalone --quiet \
--pre-hook 'systemctl stop apache2.service' \
--post-hook 'systemctl start apache2.service'
With systemd, I just need one command to stop/start/restart several
services. With OpenRC I suppose you could do:
certbot renew --standalone --quiet \
--pre-hook '/etc/init.d/apache2 stop && /etc/init.d/postfix stop' \
--post-hook '/etc/init.d/apache2 start && /etc/init.d/postfix start'
The documentation says that the hooks are "command to be run in a shell",
so it should work.
Another solution is to have a simple script:
# Controls apache and postfix: /usr/local/bin/certbot-aux
if [ $# != 1 ]; then
echo 'Need a parameter'
exit 1
fi
/etc/init.d/apache2 ${1}
/etc/init.d/postfix ${1}
And then the cron job is:
certbot renew --standalone --quiet \
--pre-hook '/usr/local/bin/certbot-aux stop' \
--post-hook '/usr/local/bin/certbot-aux start'
Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] new hi-res display won't work at top res
You don't need the Intel graphics driver, they are actually deprecated [1]. Just set your VIDEO_CARDS to: VIDEO_CARDS="intel i965" and do emerge -uDNvp @world; when you do emerge --depclean, xf86-video-intel will be uninstalled. The built-in modesetting driver is the one recommended; I'm pretty sure it will support the maximum res of your new monitor. Regards. [1] https://wiki.gentoo.org/wiki/Intel#Drivers, check the "Important" note. On Fri, May 19, 2017 at 10:58 AM, allan gottlieb <gottl...@nyu.edu> wrote: > Dell latitude E7450 with intel 915 graphics, gnome 3, systemd. > > lspci: > VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) > > I just bought a new dell 34" curved monitor (U3417). > It's max res is 3440X2560, but at that res it complains that no signal > is coming. It works fine at other res (including 2560x1440). > > The dell manual says to get new drivers and I am indeed running an old > kernel, 3.18.16-gentoo. The highest stable is 4.9.16 and I am planning > to build and employ it this summer. > > Has high res support been added to the intel graphics driver? > > thanks, > allan > > -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] plain copy of root disk won't work
On Fri, Nov 18, 2016 at 9:30 AM, Raffaele BELARDI <raffaele.bela...@st.com> wrote: > > I want to move the main disk contents (hda, PATA) to another, larger > disk (sda, SATA). > > hda contains 4 ext3 partitions (root, home, data, swap). > I created 4 ext3 partitions on sda and copied the data over from the > corresponding hda partitions using 'cp -ax'. > Then I chroot into sda1, 'grub-install /dev/sda', grub-mkconfig and edit > fstab to use sda instead of hda. > Reboot, from the non-UEFI bios change the disk boot order and try to > boot from sda. > grub from the sda starts, loads the kernel from sda1, the kernel finds > the root file system and mounts it RO but then the process stops at the > end of the kernel boot. No kernel panic, just hangs there with the last > kernel message before openrc. Openrc is not started. > > What might I be missing? Perhaps some permissions and special files. I would use rsync for such a task: rsync -Pvas /source/directory/ /target/directory/ I've used that commend in the past for exactly the same motives as you. It works; also, it's faster I think. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] no sound through headphones (OK through speakers)
On Wed, Jul 13, 2016 at 12:55 PM, allan gottlieb <gottl...@nyu.edu> wrote: > Hardware: Dell Latitude E7450 laptop > > Gentoo essentially all stable > Gnome / Systemd > > When I play a movie using totem it sounds fine if no headphones are > plugged it. > > No sound at all with headphones (I tried three different ones). > > The sound settings gui recognizes that headphones are in. The sound > test is silent. If I select the internal speakers in the gui (with the > headphones still in) sound is fine. > > Is there some headphone option I must enable in the kernel or elsewhere? The volume is probably muted for the headphones. Install pavucontrol, and execute it while the movie is playing. In the "Output Devices" tab look for your sound card (probably something like "Built-in Audio"), and in port select "Headphones". Then adjust the volume. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gnome 3 and wifi credentials
On Wed, Jun 22, 2016 at 12:44 PM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 2016-06-22 um 06:50 schrieb J. García: > >> Apparently they are stored in the gnome-keyring if you set up the >> conection to >> 'Store the password for this user' when using nm-applet, but stored in >> /etc/NewtorkManager/system-connections/ as plain text when you select >> 'all >> users may connect to this network' (I don't know the exact options >> name, I'm >> using networkd, so I couldn't check) but look at this[1] >> I guess there should be a way to backup and restore the gnome-keyring. >> >> [1] https://wiki.archlinux.org/index.php/NetworkManager#Encrypted_Wi-Fi >> _passwords > > > added one ESSID today, with "share with others" (or similar, german here) > ... nothing in /etc/NetworkManager/system-connections > > If I open my keyring-application I can't see any SSIDs/PSKs. > > What ever. I can re-add them step by step. > > Ah, nm-connection-editor shows them! > But which files does it read/write? > > using Neil's suggestion with the "find -newer" ... > > /home/sgw/.local/share/keyrings/user.keystore looks suspicious. > > I will backup that one and sync it over from another laptop. > > Is that what they call "hacking" already? :-P Stefan, could you please show us the contents of /etc/NetworkManager/NetworkManager.conf? In the early stages of systemd's integration in Gentoo, it was necessary to disable some plugins that tried to set /etc/conf.d/network as configuration file for NetworkManager. I don't know if it's related to your system connections not appearing in /etc/NetworkManager/system-connections. Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gnome 3 and wifi credentials
On Tue, Jun 21, 2016 at 3:43 PM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 2016-06-21 um 12:05 schrieb Tom H: >> On Tue, Jun 21, 2016 at 3:57 AM, Stefan G. Weichinger <li...@xunil.at> wrote: >>> >>> Does anyone have a pointer to where Gnome 3 (3.20 in my case) stores my >>> wifi credentials? >>> >>> I would love to sync that over to my new laptop without re-entering PSKs >>> at customers. >> >> Unless Gnome changes the default (which I doubt), it's >> >> /etc/NetworkManager/system-connections/ > > I had found that info as well, but that directory is simply *empty* on > my laptops. So there has to be something in $home somewhere. > > gnome-keyring? > > I could simply rsync all dotfiles/directories in $home .. but that is > not cool and puts cruft onto the new system. Go to the network settings, and set the wireless connection as "shared with other users". Then it will appear in /etc/NetworkManager/system-connections. If you don't want to share the connection with other users, do something like find $HOME/.config -name "*ESSID*" where ESSID is the ESSID you are interested in. The prefix '*' is because a while ago NM added the name "Auto" to all wireless networks that were set to automatically connect. If ~/.config does not work, use ~/.local (I don't have my laptop with me, so I cannot check which one it is). Regards. -- Dr. Canek Peláez Valdés Profesor de Carrera Asociado C Departamento de Matemáticas Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Gentoo and texlive
On Sun, Feb 7, 2016 at 5:18 PM, <k...@aspodata.se> wrote:
> I can install the complete texlive with:
> wget http://mirror.ctan.org/systems/texlive/tlnet/install-tl-unx.tar.gz
> tar zxf install-tl-unx.tar.gz
> cd install-tl-20160204/
> ./install-tl
>
> But I don't understand how to do that with the portage version.
> If I do a naive
>
> cd /usr/portage
> emerge -auqDN *te*/*texlive*
>
> I get e.g.:
>
> [blocks B ] dev-texlive/texlive-langdutch
> ("dev-texlive/texlive-langdutch" is blocking
> dev-texlive/texlive-langeuropean-2014)
>
> If I do
>
> emerge -auqDN app-text/texlive
>
> I don't get everything in texlive.
It's not supposed to give you everything; only what you need. You set
up your USE flags accordingly.
You can get most TeXLive related packages (maybe all, I don't know) with:
USE="X cjk context detex dvi2tty epspdf extra games graphics
humanities jadetex luatex metapost music omega pdfannotextractor png
pstricks publishers science tex4ht texi2html truetype xetex xindy xml"
emerge app-text/texlive
or adding the USE flags to /etc/portage/package.use. But you probably
don't need all of that.
Several packages in the TeXLive distribution are merged, splitted or
replaced. That's why you get blocks; perhaps you could try:
emerge -auqDN *te*/*texlive*2014*
But, again, probably you don't want that either, and there will be
other conflicts with -r1 versions. You can also search with ebuilds
with the same slot, and emerge those.
But really, you should set your USE flags and install app-text/texlive.
Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] [OT] Canek's youtube channel
On Fri, Sep 25, 2015 at 2:44 AM, Neil Bothwick <n...@digimed.co.uk> wrote: > On Thu, 24 Sep 2015 20:54:12 -0500, Canek Peláez Valdés wrote: > >> I've got my tenure track at UNAM (which is kinda big deal here in >> Mexico). > > Congratulations, well done. Thanks. >> Also, and since I will have an stable job until I die/retire > > I hope that means long term stability and not a short lifespan. After > all, the same could be said of Kamikaze pilots... The former, not the later. I hope. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] [OT] Canek's youtube channel
On Thu, Sep 24, 2015 at 8:07 PM, walt <w41...@gmail.com> wrote: [ ... ] > Canek, are you still lurking here? Please come back to us :) (This is personal and definitely off-topic, so please skip if you are not interested). I'm still here, and I sill read almost all top posts (but I don't follow most threads). Thanks for the concern. I've got my tenure track at UNAM (which is kinda big deal here in Mexico). I've been swamped in work for the last five months, and it's gonna be that way for at least until the end of the year, probably more. As for my lack of participation on the list, if you have noticed almost no GNOME/systemd questions are asked on the list anymore, and I attribute it to the excellent work done by the corresponding teams of Gentoo devs. The growing pains we had when systemd was introduced are basically over, and running Gentoo with it is easy as pie nowadays. And I still maintain that for years it was easier to run systemd on Gentoo than on many other distributions. Certainly I haven't had any problems at all since a very long time. On top of that, and because of my workload, I set almost all the packages in all my machines to stable; basically I only have vanilla-sources and dracut in ~amd64. Therefore, I cannot be of much help to someone running systemd 227 when I myself run 218. The same applies to GNOME; I just updated to 3.16 on September 13. At some point my workload will stabilize (I hope!), and I intend to get back to experiment with unstable packages and participating on the list. Also, and since I will have an stable job until I die/retire (for almost all practical purposes), I hope to finally start the process to become a Gentoo developer myself. Thanks again for asking. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd-224 Look out for new networking behavior
On Mon, Aug 3, 2015 at 8:30 AM, gottl...@nyu.edu wrote: On Sun, Aug 02 2015, Canek Peláez Valdés wrote: On Sun, Aug 2, 2015 at 10:03 AM, walt w41...@gmail.com wrote: I've been running systemd for a long time without needing to enable the dhcpcd service at boot time. Starting with systemd-224 that is no longer true. Today I had to enable dhcpcd.service specifically or the network interface didn't get an ip address during boot. Seems like this might be especially important for those of you who need to update remote machines. If you enable systemd-networkd.service, and your .network file has DHCP=yes in its [Network] section, then it will use the DHCP client included with systemd-networkd. In my servers I not longer use any net-misc/*dhcp* package. Regards. Is this server-related? I have only simple workstations/laptops and I don't enable systemd-networkd at all. It seems that NetworkManager takes care of both wired and wireless without assistance (including dhcp). In latptops/workstations NetworkManager takes care of everything. However, I still enable systemd-networkd and systemd-resolved in my laptop and workstations. If enabled without any configuration, it just monitors the network interfaces and keeps them in the loop for the rest of the system to know about them from a central registry. It doesn't interfere with NetworkManager (or any other network management program for that matter). It's not mandatory to enable them either. However, there were advantages to doing so; for example, in my laptop, systemd-timesyncd would try to sync the clock only if there was a network connection available. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Some update yesterday broke my system - which one
On Mon, Aug 3, 2015 at 5:21 AM, Helmut Jarausch jarau...@skynet.be wrote: Hi, some update yesterday which was not yet available on August, 1st, complete broke my system. (Probably systemd-224) I couldn't do anything, especially no downgrading a package. I had to revert to a backup from July, 29th. It turned out that something has installed /lib/udev while removing the symlink /lib - /lib64 on my machine. Therefore /lib did contains nothing but udev which broke my system completely. Has anybody made a similar experience or does anybody have explanation for that? I have 2 versions on systemd in different machines: 218 and 222. Both of them install files in /lib and in /lib64. None of them touch the symbolic link, and I don't see how they could do it. That pertains to portage; when a package gets installed, it installs into /var/tmp (or wherever PORTAGE_TMPDIR points to), and then portage merges the files from PORTAGE_TMPDIR into the filesystem. I don't see how the symbolic link from /lib to /lib64 could be modified. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] systemd-224 Look out for new networking behavior
On Sun, Aug 2, 2015 at 10:03 AM, walt w41...@gmail.com wrote: I've been running systemd for a long time without needing to enable the dhcpcd service at boot time. Starting with systemd-224 that is no longer true. Today I had to enable dhcpcd.service specifically or the network interface didn't get an ip address during boot. Seems like this might be especially important for those of you who need to update remote machines. If you enable systemd-networkd.service, and your .network file has DHCP=yes in its [Network] section, then it will use the DHCP client included with systemd-networkd. In my servers I not longer use any net-misc/*dhcp* package. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] installing gentoo with a systemd profile
On Mon, Jul 20, 2015 at 8:02 PM, gottl...@nyu.edu wrote: On Sat, Jul 18 2015, Canek Peláez Valdés wrote: On Sat, Jul 18, 2015 at 8:00 PM, gottl...@nyu.edu wrote: I am installing gentoo on a new laptop. I am a gnome, hence systemd, user. I also use lvm (I have / and /usr combined on a non-lvm partition). At the point where you choose a profile (// wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Choosing_the_right_profile ) I selected [5] default/linux/amd64/13.0/desktop/gnome/systemd * But now I get merge conflicts since I have sys-fs/udev installed. I can't depclean udev. Should I have just used the default/linux/amd64/13.0 profile and switched later after the installation is complete. Fortunately, I don't need to used the new machine immediately so I don't mind starting the installation over from the beginning In a similar vein, my systems have PORTDIR=/var/portage. Am I correct in now believing that it is better to do the install with the default PORTDIR=/usr/portage and then switching after the dust settles What I usually do is: 1. Extract the stage 3 tarball 2. Sync the portage tree 3. Switch to the systemd profile 4. emerge -uDNvp world (this usually solves the systemd/udev conflicts) 5. emerge --depclean 6. Switch to the GNOME/systemd profile 7. Emerge gnome-base/gnome In my experience, if you switch directly to the GNOME/systemd profile, you get many conflicts. I certainly did. I will try your indirect root to gnome/systemd. If it works (and given the source I strongly suspect it will), I will try to get it included in the systemd wiki. You'll probably still get some circular dependencies by USE flags, but those should be few and portage will tell you how to break the cycle. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] installing gentoo with a systemd profile
On Sat, Jul 18, 2015 at 8:00 PM, gottl...@nyu.edu wrote: I am installing gentoo on a new laptop. I am a gnome, hence systemd, user. I also use lvm (I have / and /usr combined on a non-lvm partition). At the point where you choose a profile (// wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Choosing_the_right_profile ) I selected [5] default/linux/amd64/13.0/desktop/gnome/systemd * But now I get merge conflicts since I have sys-fs/udev installed. I can't depclean udev. Should I have just used the default/linux/amd64/13.0 profile and switched later after the installation is complete. Fortunately, I don't need to used the new machine immediately so I don't mind starting the installation over from the beginning In a similar vein, my systems have PORTDIR=/var/portage. Am I correct in now believing that it is better to do the install with the default PORTDIR=/usr/portage and then switching after the dust settles What I usually do is: 1. Extract the stage 3 tarball 2. Sync the portage tree 3. Switch to the systemd profile 4. emerge -uDNvp world (this usually solves the systemd/udev conflicts) 5. emerge --depclean 6. Switch to the GNOME/systemd profile 7. Emerge gnome-base/gnome In my experience, if you switch directly to the GNOME/systemd profile, you get many conflicts. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Don't disable 'introspection'
On Thu, Jul 16, 2015 at 3:53 PM, walt w41...@gmail.com wrote: I don't understand 'introspection' enough to know why we need it, but apparently we do, so don't use the -introspection useflag like I did. The trouble I introduced a few weeks ago when I disabled introspection was subtle enough that I didn't realize until yesterday that I even had a problem. Portage had been doing mildly insane things that other people were not seeing, so as a test I removed the -introspection useflag and spent the entire day rebuilding packages. My portage problem appears to be fixed. I hope. If anyone can splain what introspection does I'd be grateful. Alan did a fine job explaining what introspection is in general. In Gentoo, the introspection flag is only used by GObject based libraries; all the languages that natively supports introspection does it inconditionally, and (as far as I am aware) GObject is the only C object oriented library that provides introspection. Some years ago, you could get away without activating it, but nowadays is for all practical purposes mandatory. At least this is the case for GNOME 3; but I would not be surprised if it's also the case for basically any GObject based software; that covers all GTK+ 2 and 3 applications. The instrospection infrastructure is not only used (as Alan mentioned) to look inside a compiled class; it's also part of the automatic binding generation for other programming languages used by all GObject libraries (or at lest that's what I understand, please correct me if I'm wrong). Therefore, if you use Inkscape, for example, you'll need introspection since Inkscape is wrote in C++ using the gtk-- bindings. In general, I would recommend not to set USE=-* (an opinion shared by basically all Gentoo devs and most rational people), and let the default use flags to do their magic. But everyone is free to break their systems as they please. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] distcc apparently doesn't work
On Thu, Jun 18, 2015 at 7:47 PM, João Matos jaon...@gmail.com wrote: Dear list, I'v installed gentoo in my notebook, and I'm trying to setup distcc, to share the 8 cores from my gentoo desktop. Both systemd systems. I followed this: https://wiki.gentoo.org/wiki/Distcc . Situation: 1) systemctl start distccd gives me no erro, no log file, and according to nmap, there is no new ports opened. When I start to compile in the client, no unusual cpu usage here. 2)distccd --allow 127.0.0.1 10.10.10.25 10.10.10.102 --daemon --log-level notice --log-file /var/log/distccd.log --port 3632 same result as 1) what should be wrong? Use systemctl, and edit /etc/systemd/system/distccd.service.d/00gentoo.conf. This is only necessary in the *servers*; in the clients you just need to use distcc-config, and set the necessary environment flags for portage and/or your gcc. Obviously each client can also be a server, but from your email I understand you don't want this (I also don't let my laptop to participate; my desktop is several times faster). Finally, using journalctl -f -u distccd.service you can check if it's working. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: webkit-gtk-2.4.8 fails to compile
On Wed, Jun 17, 2015 at 5:47 PM, walt w41...@gmail.com wrote:
On 06/17/2015 01:54 PM, ddjones wrote:
On Friday, March 27, 2015 04:05:16 PM walt wrote:
On 03/27/2015 02:56 AM, ddjones wrote:
I seem to be hitting this bug:
https://bugs.gentoo.org/show_bug.cgi?id=513386
webkit-gtk fails:
gtk-2.4.8/work/webkitgtk-2.4.8/.libs/libwebkitgtk-3.0.so: undefined
reference to `_ZNSt6chrono3_V212steady_clock3nowEv@GLIBCXX_3.4.19'
I don't know if you understand the concepts discussed in that bug
report,
but this this is basic idea:
You see that the undefined symbol includes the string GLIBCXX. From
this
you can tell that the program uses the well-known c++ standard library,
which happens to be installed separately by each version of gcc you
have on
your computer.
The error you are seeing is caused by using a different version of gcc
to
compile webkit-gtk than you used to compile some other package that
webkit-gtk depends on.
The tedious but necessary fix is to find every package on your
computer that
needs libstdc++ and then recompile all of them with the same version of
gcc. Yup, boring.
I am still fighting this. Yes, I've been fighting it since March.
emerge -e world
fails with this error. I've done it at least a half dozen times.
emerge -e
world starts out with over 1400 packages. When webkitgtk fails, this is
what's left:
root@kushiel /etc/conf.d # emerge --ask --resume
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] net-libs/webkit-gtk-2.4.8 [2.4.7]
[ebuild R] media-libs/phonon-gstreamer-4.7.2
[ebuild U ] net-libs/webkit-gtk-2.4.8-r200 [2.4.7-r200]
[ebuild NS] net-libs/webkit-gtk-2.6.5 [2.4.7, 2.4.7-r200] USE=egl
geoloc
gstreamer introspection jit opengl spell webgl -coverage -doc
-libsecret {-
test}
[ebuild R] net-libs/libproxy-0.4.11-r2
[ebuild R] dev-java/swt-3.7.2-r1
[ebuild R] net-libs/glib-networking-2.42.1
[ebuild R] media-video/cheese-3.14.2
[ebuild R] net-p2p/vuze-4.8.1.2-r1
[ebuild R] net-p2p/vuze-coreplugins-4.8.1.2
Any suggesting other than format the hard drive and start over greatly
appreciated, because I've tried everything else I can think of or find
suggested online.
This is a trick that works occasionally: (Don't ask me why. I try it only
out
of desperation when I don't know what else to try)
#quickpkg =webkit-gtk-2.4.7-r200
#quickpkg =webkit-gtk-2.4.7
#emerge -C =webkit-gtk-2.4.7-r200 =webkit-gtk-2.4.7
Removing webkit will break any other packages that depend on it, but now
that
you've saved your existing webkit packages with quickpkg, you can
reinstall them
using emerge -K if my trick doesn't work for you.
Here's another desperation move I make sometimes when I'm out of ideas:
#cd /usr/lib
#ls -lSr (this sorts your libraries with the oldest ones at the end)
Nitpicking, but isn't -S for sorting by size? The -t flag is for
modification time.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] Can't boot using UEFI
On Sun, Jun 14, 2015 at 8:40 AM, João Matos jaon...@gmail.com wrote: Hi list, I've bought me a ultrabook dell vostro 5470, and I'm trying to get gentoo running on it. I'm having a few problems, but I'd like to correct the boot one first. I'm installing it from ubuntu live cd, and the comand: efibootmgr --create --disk /dev/sda --part 7 --label Gentoo --loader \boot\efi\boot\bootx64.efi seems to work. It put a entry on bios - Gentoo - but when I select it, the windows start (second boot). The handbook is not that clear, so I'm not sure if I should call /dev/sda7 of --part 7. Other difference is I'm not using a separate /boot. Its everything at /, so I'm also not not sure if this path is ok. This seems to be the very simple, and I'd like to have it on my system. But I've also tried grub2, and got the following error: grub2-install: error: cannot find EFI directory. What should I do? Have you tried gummiboot? AFAIR, it's a simple matter of doing: gummiboot --path=/boot install /boot should be yout EFI System Partition (ESP). Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] bash completions missing
On Wed, Jun 10, 2015 at 4:44 PM, Justin Findlay jfind...@gmail.com wrote: After a recent reboot all of my bash completions have seemed to have disappeared. Is this a sign that I should finally switch to ZSH? # eselect bashcomp list Available completions: (none found) I am unsure what to do at this point as it seems that all the appropriate packages and USE flags are installed/have not changed. Did you read the news item about them in november[1]? Regards. [1] https://www.gentoo.org/support/news-items/2014-11-25-bash-completion-2_1-r90.html -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] problems debugging a systemd problem
On Thu, May 28, 2015 at 2:11 PM, cov...@ccs.covici.com wrote: Also, as Rich said, if you wait it's possible that systemd (and/or dracut) will drop you into a rescue shell anyway. Unfortunately, thanks to very slow hardware in the wild, the timeout has been increased to three minutes, and I believe those are *per hardware unit*. So if you have five disks, in theory it could take fifteen minutes to get you to a rescue shell. Thanks much. Does the rescue target try to mount all the disks? Also, I would still like to get in touch with the dracut devs -- although I may never make that particular mistake again, but maybe other things will happen. As I said in my previous mail: emergency mounts the root filesystem read-only; rescue mounts all the filesystems read/write. If dracut cannot mount the root filesystem, it *WILL* drop you to a shell, but it will take some time while all the timeouts expire. This could be *several* minutes depending on hardware. The dracut mailing list is in [1]. Regards. [1] http://vger.kernel.org/vger-lists.html#initramfs -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] problems debugging a systemd problem
On Thu, May 28, 2015 at 1:36 PM, Rich Freeman ri...@gentoo.org wrote: On Thu, May 28, 2015 at 2:11 PM, Canek Peláez Valdés can...@gmail.com wrote: Actually, it does work (see attached screenshot). I set my root= kernel command line parameter wrong on purpose, and systemd (inside dracut) dropped me inside a rescue shell. Interesting. Perhaps it just enables shell access. There is a separate option that configures whether dracut drops to a shell at all, or if it just hangs on failure. The latter might be desirable for security purposes in some cases. Are you sure that you don't get a shell if you don't pass emergency on the command line, but still have an invalid root=? I wasn't sure, I did a couple of tests more. I comment them below. Usually when somebody wants a rescue shell, they want it in their root filesystem, and not in their initramfs before it has pivoted. That is why dracut has options like rd.break. But that doesn't help you at all when the problem is exactly that you cannot mount your root filesystem. With the rescue shell of systemd (inside dracut), you can analyze the problem, or perhaps even mount your root filesystem and continue the boot process; the initramfs should have all the necessary tools to do that. rd.break DOES give you a shell before root is mounted, if you tell it to. rd.shell tells dracut to give you a shell if something fails rd.break forces a shell at the specified point, whether something fails or not. The official docs do not list emergency as a valid dracut option. Obviously systemd uses it, but again the fact that you had to mangle your root= option sugests that systemd within dracut ignores it if it can mount your root. No, if you set emergency or rescue, systemd will go to emergency.target and rescue.target, respectively. If the problem were with systemd/services/etc in the actual root filesystem (once the actual distro has started booting), then putting emergency on the command line should get you a rescue shell. Again, what if the problem is before *that*? Then you tell dracut to drop to a shell. I wasn't aware that the emergency option actually made a difference, though I'm still not 100% sure that was what did it. I'm now pretty sure it DOESN'T make a difference when the problem is before you can mount root. The same generally applies to openrc - if the initramfs isn't mounting your root filesystem, then passing instructions to openrc won't do anything since in that case openrc isn't even running. But in this case, systemd *is* inside the initramfs: # ls usr/lib/systemd/ network systemd-cgroups-agent systemd-journald systemd-shutdown systemd-vconsole-setup system systemd-fsck systemd-modules-load systemd-sysctl system-generators systemd systemd-hibernate-resume systemd-reply-password systemd-udevd That's my initramfs. With dracut, systemd *is* the initramfs init system. Sure, and that is how mine works as well. But, obviously systemd in dracut is configured to ignore that parameter when root= is valid, No, it doesn't ignore it, even if root= is valid. otherwise you'd get a shell every time. I'd have to check the docs, but I suspect that the behavior is configurable, and systemd within the initramfs is configured differently. If nothing else they could just make the rescue target launch the default target/etc. As I said, I did the following tests: 1. Adding emergency to the kernel command line, with a valid root=. 2. Adding rescue to the kernel command line, with a valid root=. 2. Leaving root= invalid without adding neither emergency nor rescue. If root= is valid, with emergency systemd drops you to a shell with your root filesystem mounted read-only. With rescue, systemd drops you to a shell with all your filesystems mounted read-write. If root= is invalid, it doesn't matter if you use emergency, rescue, or neither, *dracut* drops you to a shell, still inside the initramfs obviously. It takes a while; I didn't took the time, but I think it was 3 minutes. Inside this shell, you can use systemd normally, and if you manage to mount the root filesystem, I'm sure you could continue the normal boot process. You'll have to pivot root manually, though. Hope that makes it clear. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] problems debugging a systemd problem
On Thu, May 28, 2015 at 5:23 PM, Rich Freeman ri...@gentoo.org wrote: On Thu, May 28, 2015 at 5:32 PM, Canek Peláez Valdés can...@gmail.com wrote: As I said, I did the following tests: 1. Adding emergency to the kernel command line, with a valid root=. 2. Adding rescue to the kernel command line, with a valid root=. 2. Leaving root= invalid without adding neither emergency nor rescue. If root= is valid, with emergency systemd drops you to a shell with your root filesystem mounted read-only. With rescue, systemd drops you to a shell with all your filesystems mounted read-write. If root= is invalid, it doesn't matter if you use emergency, rescue, or neither, *dracut* drops you to a shell, still inside the initramfs obviously. It takes a while; I didn't took the time, but I think it was 3 minutes. Inside this shell, you can use systemd normally, and if you manage to mount the root filesystem, I'm sure you could continue the normal boot process. You'll have to pivot root manually, though. That was basically my understanding of how dracut behaved. I think we're just having a communication gap or something, because you seem to be disagreeing with me when I'm basically trying to describe the behavior you just listed above. It's possible; I was wrong about emergency doing anything when root= is invalid, but I did not understood the above behavior from your previous mails. Anyway, if dracut cannot mount the root filesystem, it will drop you into a shell with a functional systemd. Eventually. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] problems debugging a systemd problem
On Thu, May 28, 2015 at 4:55 PM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: [...] As I said, I did the following tests: 1. Adding emergency to the kernel command line, with a valid root=. 2. Adding rescue to the kernel command line, with a valid root=. 2. Leaving root= invalid without adding neither emergency nor rescue. If root= is valid, with emergency systemd drops you to a shell with your root filesystem mounted read-only. With rescue, systemd drops you to a shell with all your filesystems mounted read-write. If root= is invalid, it doesn't matter if you use emergency, rescue, or neither, *dracut* drops you to a shell, still inside the initramfs obviously. It takes a while; I didn't took the time, but I think it was 3 minutes. Inside this shell, you can use systemd normally, and if you manage to mount the root filesystem, I'm sure you could continue the normal boot process. You'll have to pivot root manually, though. Hope that makes it clear. How do you pivot route manually? Basically, with pivot_root(8) [1]. Be aware that systemd does some things before and after pivot_root'ing; in particular, it switches from the instance running inside the initramfs to an instance running in the real filesystem. I'm not sure how it does it, but the switching code is relatively simple [2]. Regards. [1] http://linux.die.net/man/8/pivot_root [2] http://cgit.freedesktop.org/systemd/systemd/tree/src/shared/switch-root.c -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] problems debugging a systemd problem
On Thu, May 28, 2015 at 3:30 AM, cov...@ccs.covici.com wrote: Stefan G. Weichinger li...@xunil.at wrote: On 28.05.2015 09:39, cov...@ccs.covici.com wrote: No, the journal is gone, it was only in /run which is on a tmpfs file system. I can boot from a cd all day long, but it would not help one bit. Hm, I think it could help for sure as you could chroot in and do something. For example build a new kernel or initrd or ... You removed openrc? Otherwise boot via openrc and (try to) fix stuff. You could even reinstall openrc from within chroot ... just to get bootin again etc etc I still have openrc, but Dracut won't work with it, at least maybe because I have systemd use flag enabled. Also, in retrospect, that would not have solved my specific problems, because it was related to an rd.lv command which is specific to dracut. But thanks for your suggestion. I wonder what the rescue target is -- I have never seen that before -- maybe I could configure it so I could boot into a shell and fix things and it would be sort of like a little system of its own. Others have already answered, but I will add that if you put emergency anywhere in the kernel command line, then systemd will boot to the rescue target; that's why I suggested to do it in my first answer. Also, as Rich said, if you wait it's possible that systemd (and/or dracut) will drop you into a rescue shell anyway. Unfortunately, thanks to very slow hardware in the wild, the timeout has been increased to three minutes, and I believe those are *per hardware unit*. So if you have five disks, in theory it could take fifteen minutes to get you to a rescue shell. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] General weirdness - a tale of woe.
On Wed, May 27, 2015 at 8:02 AM, Alan McKinnon alan.mckin...@gmail.com wrote: On 27/05/2015 14:31, Canek Peláez Valdés wrote: On Wed, May 27, 2015 at 6:59 AM, Peter Humphrey pe...@prh.myzen.co.uk mailto:pe...@prh.myzen.co.uk wrote: Hello list, Hi. Over the last few weeks I've been having odd things go bump in the night. This is a KDE amd64 system with /usr under / and no initrd. I have no idea what your problem can be. But as a friendly reminder, your setup (/usr under / and no initrd) hasn't been supported since at least a year and a half. I read what Peter said to mean that he doesn't have /usr as a separate volume - it is directly under / Oh, sorry, I understand the opposite. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] General weirdness - a tale of woe.
On Wed, May 27, 2015 at 6:59 AM, Peter Humphrey pe...@prh.myzen.co.uk wrote: Hello list, Hi. Over the last few weeks I've been having odd things go bump in the night. This is a KDE amd64 system with /usr under / and no initrd. I have no idea what your problem can be. But as a friendly reminder, your setup (/usr under / and no initrd) hasn't been supported since at least a year and a half. From [1]: If you have / and /usr on separate file systems and you are not currently using an initramfs, you must set one up before this date. Otherwise, at some point on or after this date, upgrading packages will make your system unbootable. It is of course possible that your problem has nothing to do with not using an initramfs. Then again, *IT IS* also possible that you NEED an initramfs, and that's one of the many reasons the council decided to stop supporting such a configuration. Regards. [1] https://www.gentoo.org/support/news-items/2013-09-27-initramfs-required.html -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] problems debugging a systemd problem
On Thu, May 28, 2015 at 12:09 AM, cov...@ccs.covici.com wrote: Hi folks. I spent a very frustrating time last night trying to figure out why my systemd would not boot using systemd. I am using dracut and its version is 041r2. Now what was happening is that the system would get to the pre-init-queue -- and I even set the rd.break there, but after that the system would not boot -- when I used debug it endlessly said calling setl forever. Now it turned out that the problem was that I had mistyped an rd.lv= line -- instead of ssd-files/usr I had ssd-files/-usr . Now, what I would like to know is how could I tell that it was trying to look for a non-existent lv? At the point of the break. no lvm volumes were active, although strangely enough I saw a e2fsck for the real root file system which was an lvm volume. I am finding its generally hard to debug systemd problems, several other times the system just sat there till I figured it out some other way. Any observations on this would be appreciated, but I don't want to get into a flame war, I just want to minimize the down time. Usually if you can get an emergency shell by adding emergency to the kernel command line (both GRUB and Gummiboot allow you to edit the kernel command line), then is easy to see what the problem is. My experience with LVM has been consistently pretty awful, which is why I don't use in any of my machines, but I suppose a systemctl --all --full will tell you what unit files have failed, and then you can journalctl -b -u them. Also journalctl -b by itself would tell you many times what the problem is. The only problem with the emergency shell is that sometimes is too early in the boot process for the keyboard drivers to have been loaded, but that is easily solved by adding a drivers+= line to a conf file in /etc/dracut.conf.d. Also, and I cannot stress this enough, you never delete your old (and working) kernel+initramfs until you have tested the new one. I would also recommend to leave the entries for the old kernel+initramfs in the GRUB/Gummiboot menu, but you can manage without them. Finally, and this is tooting my own horn, maybe you could try kerninst[1]? It's a little script I started a couple of years ago to automatically compile and install my kernels and generate my initramfs'. I use it in all my machines, and now my kernel update is just a matter of eselecting the new version, and running kerninst. I follow ~amd64 vanilla-sources, so this is roughly every week or two. Beware, though, that I don't use LVM nor RAID nor Luks, but in theory if you have a working kernel+dracut+[grub|gummitboot] configuration, it should also work with them. Regards. [1] https://github.com/canek-pelaez/kerninst -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Tips for fresh install with GRUB2+RAID1+LVM2
occasion. Often booting from a rescue CD or such caused something like this to happen. One of the advantages of using an initramfs is that they can be a lot smarter about finding your partitions. You can identify them by UUID or label, and not care as much if mdadm or the kernel renames your device nodes. I'd seriously take a look at dracut, though I don't know if it works with eudev. It certainly should support openrc, and I know that it did back when I was running openrc. It can also mount /usr for you, and in fact it should automatically do so. It also respects your fstab - it uses its internal logic and the kernel boot line to initially find filesystems, but then it reads your /etc/fstab and remounts everything as you define it there just in case something has changed since the last time you built the initramfs/etc. You can define your own modules for it which makes it reasonably easy to get it to do anything at all during early boot, and it doesn't require anything to be built static (it finds required shared objects anywhere on the filesystem and includes them in the initramfs). It can also give you a rescue shell if something goes wrong, and depending on your settings you can make that rescue shell reasonably well-featured (using either dash or bash as you prefer inside, and I imagine you could tell it to install the other on the side). A while ago I needed to run some btrfs tools that aren't in dracut by default and it was trivial to tell dracut to include them, and I forced a shell on next boot which gave me the latest tools and kernel without having to build a rescue CD with them, and a bash shell to run them from. It certainly isn't necessary to use an initramfs to use Gentoo, and I used to be among the more minimalist crowd that avoided them. However, once I took the time to examine dracut it went from being a blob that looked unnecessary to a tool that is often useful. Last time I tried to use dracut with openrc, it failed, I can't remember exactly what happened, I think udev did hang, but its been a while since this happened. Dracut uses systemd internally, so maybe this is part of the problem. Dracut only uses systemd optionally and (AFAIR) not by default. If you don't specify it, dracut will use its own scripts as init. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] How do kernel modules load automatically during boot?
On Wed, Apr 22, 2015 at 2:17 PM, walt w41...@gmail.com wrote: I just did a huge update on an older ~amd64 machine, and now only three out of a dozen or so kernel modules load during bootup, which leaves a lot of hardware in an unusable state. What mystifies me is how those three kernel modules managed to get loaded while all the others didn't. (It's the same three modules every time, BTW.) I grepped through /etc for the names of those modules, thinking maybe I listed them in modprobe.conf.d sometime in the past, but no, those modules are not listed anywhere in /etc, nor are any of the others listed either. I can modprobe all of the unloaded modules manually after bootup, which shows that all of the modules exist and load without error, so the problem lies elsewhere, but where? Any clues would be most welcome. If you are using systemd, there are a few modules that it always loads (ipv6, autofs4, stuff like that). Everything else is loaded automatically, by udevm, as-needed. My guess (but I could be wrong); you are using an initramfs, and didn't included the modules in it. In that case, the modules are not loaded because they are not available. I have no idea if OpenRC tries to load modules. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummiboot does not display new kernel
On Thu, Apr 2, 2015 at 3:06 PM, Stefan G. Weichinger li...@xunil.at wrote: On 09.03.2015 09:16, Stefan G. Weichinger wrote: # ls -l loader/entries/ total 2 -rwxr-xr-x 1 root root 329 9. Mär 09:04 e55a6b6a09bd2b1c50216272545a8d1f-3.19.0-gentoo.conf -rwxr-xr-x 1 root root 329 9. Mär 09:01 e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf -rwxr-xr-x 1 root root 311 9. Mär 09:06 e55a6b6a09bd2b1c50216272545a8d1f-4.0-rc2.conf -rwxr-xr-x 1 root root 329 8. Mär 17:34 stefan.conf And the 3.19.1 still does not get displayed at boot time! ;-) just as additional info: same behavior with 4.0-rc6 ... moving e55a6b6a09bd2b1c50216272545a8d1f-4.0-rc6.conf to stefan4.conf makes it appear at boot time Stefan, this is kinda stupid, but have you tried to re-emerge gummiboot? Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] openrc-systemd command comparison
On Wed, Apr 1, 2015 at 1:55 AM, Marc Joliet mar...@gmx.de wrote: Am Tue, 31 Mar 2015 20:05:50 -0600 schrieb Canek Peláez Valdés can...@gmail.com: [...] With systemd you don't need this, since it can track the real state of its services thanks to cgroups. And kill *really* kills all the processes associated to a service, something that OpenRC, by design, cannot do. [...] I wonder if that's accurate. I know that OpenRC also uses cgroups for grouping services, but how much does it actually exploit them? According to [1]: # If you have cgroups turned on in your kernel, this switch controls # whether or not a group for each controller is mounted under # /sys/fs/cgroup. [...] # Set this to YES if yu want all of the processes in a service's cgroup # killed when the service is stopped or restarted. # This should not be set globally because it kills all of the service's # child processes, and most of the time this is undesirable. Please set # it in /etc/conf.d/service. # To perform this cleanup manually for a stopped service, you can # execute cgroup_cleanup with /etc/init.d/service cgroup_cleanup or # rc-service service cgroup_cleanup. # rc_cgroup_cleanup=NO So it's available if you have cgroups turned on, and then you need to set it up globally (which is not recommended), or by service. That wasn't available when I stopped using OpenRC; but then again, that was almost five years ago. Is nice to see OpenRC catching up to systemd. Regards. [1] https://github.com/OpenRC/openrc/blob/master/etc/rc.conf.Linux -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] openrc-systemd command comparison
On Wed, Apr 1, 2015 at 3:18 AM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 01 Apr 2015 10:57:33 +0200, Volker Armin Hemmann wrote: Btw, if you need a 'cheat sheet' for INIT the whole thing is broken beyond repair. You don't *need* it, it's just a convenience when switching from one syntax to the other. The order of the switch doesn't matter, the notes would be just as useful for someone switching from systemd to openrc. Don't feed the troll Neil. Almost nobody does. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] openrc-systemd command comparison
On Wed, Apr 1, 2015 at 8:28 AM, Rich Freeman ri...@gentoo.org wrote: On Wed, Apr 1, 2015 at 4:04 AM, Canek Peláez Valdés can...@gmail.com wrote: # If you have cgroups turned on in your kernel, this switch controls # whether or not a group for each controller is mounted under # /sys/fs/cgroup. [...] # Set this to YES if yu want all of the processes in a service's cgroup # killed when the service is stopped or restarted. # This should not be set globally because it kills all of the service's # child processes, and most of the time this is undesirable. Please set # it in /etc/conf.d/service. # To perform this cleanup manually for a stopped service, you can # execute cgroup_cleanup with /etc/init.d/service cgroup_cleanup or # rc-service service cgroup_cleanup. # rc_cgroup_cleanup=NO As pointed out in the comments, using this feature is apparently unrecommended - probably because most init.d scripts were never written with it in mind. A few notes that might be helpful for anybody trying this out, based on my systemd experiences (where this is standard functionality, but units are written with this in mind). Please note that I'm not 100% sure about how this is implemented in openrc, so some potential issues below may be mitigated. Also note, I'm not trying to make any value statements here (foo is better than bar) - the purpose of my email is to help educate sysadmins about some of the possible unintended consequences of using features like these. 1. As far as I'm aware, openrc still doesn't have any concept of scripts stopping/failing unless you explicitly tell it to stop them. With systemd if the main process dies, the unit stops (and possibly fails), and the child processes are killed automatically if this is not overridden. So, don't expect the behavior to be exactly the same. I think (I could be wrong) that most of the detection magic in systemd is thanks to the use of cgroups. If that's the case, then OpenRC should be able to do the same (if someone cared to code it). 2. Some scripts like apache might attempt to do graceful shutdowns. I have no idea how the kill behavior of openrc interacts with this. With systemd care had to be taken in the script to ensure that kills were only sent after a suitable timeout to allow graceful shutdown a chance to complete - otherwise an apache2 graceful completes instantly and SIGTERMs get sent almost immediately afterwards. The openrc init.d script already does its own attempts at polling/killing for a restart, so you might get issues with how these features interact. 3. Sometimes leaving orphan processes around might be considered intended behavior. Any screen launched from an ssh session is going to be a child of sshd and in its cgroup. If you completely kill the cgroup, then you'll kill any user sessions inside unless they were given some kind of special handling. I'm actually not 100% sure how this is done in systemd (logind may put these in a different cgroup already), but you'll certainly want to think about things like this. As you correctly guessed, logind takes care of that: $ systemd-cgls ├─1 /usr/lib/systemd/systemd --switched-root --system --deserialize 17 [...] └─user.slice └─user-1024.slice ├─session-1395.scope │ ├─13984 sshd: canek [priv] │ ├─13989 sshd: canek@pts/0 │ ├─13994 -bash │ ├─14012 systemd-cgls │ └─14013 /usr/bin/less └─user@1024.service ├─13986 /usr/lib/systemd/systemd --user └─13987 (sd-pam) So OpenRC should implement something similar to logind (which would be actually awesome, since GNOME, KDE and other sutff is starting to depend on it) to be able to work like systemd. 4. Not really an issue for openrc, but if you're running systemd timer units keep in mind that anything you fork from the main process dies when the main process dies, so be careful about a cron shell scripts that runs stuff in the background without waiting at the end. I'd think that this is a feature openrc would want to make the default at some point. However, for that transition to be made maintainers need to take another look at their scripts to make sure they still work correctly. That was never an issue for systemd since the behavior was there from the start. One thing I will say is that doing this sort of thing in the service manager makes a LOT more sense than doing it in individual scripts. No argument from me here ;) Look at the apache2 init.d script sometime and compare it to the systemd unit. Most of the complexity in the init.d script is just implementing stuff that systemd does natively, like graceful restarts with cleanup of orphans and all that. I'm not criticizing the apache2 script, but rather pointing out that one of the advantages of systemd is that all of its units benefit from that kind of care without the need to implement it in each script. And, of course, killing child processes can be configured per
Re: [gentoo-user] openrc-systemd command comparison
On Mar 31, 2015 7:55 PM, Daniel Frey djqf...@gmail.com wrote: On 03/17/2015 10:20 AM, Rich Freeman wrote: The cheat sheets are useful for reference, but I'd strongly encourage anybody using systemd to get a decent understanding of the fundamentals. Oh, certainly - but going in completely blind and being stuck for 15 minutes trying to do a simple task sucks. I'm not saying that a cheatsheet is enough to avoid reading manpages, but at least it's a start where users can find information to do basic stuff with systemd. I'm also not talking about a cheatsheet about writing units/services/etc. When I did the switch there wasn't anything in the gentoo-related wikis for even things like starting kdm. This is what I'm talking about - how to list services, start and stop things - basic stuff. Anyway, I've finally gotten around to putting together a short cheatsheet @ https://wiki.gentoo.org/wiki/OpenRC_to_Systemd_Cheatsheet . Thanks for doing this, I think it will help all the people switching to systemd from OpenRC in Gentoo. However, I think the zap command is a little misleading, even with the note stating that is no exactly the same. AFAIR, zap doesn't do anything to the processes of a service; it just zaps back the internal state of OpenRC as if the service is stopped. It's needed because OpenRC cannot really follow the status of its services, so sometimes they die and OpenRC is none the wiser, and you need to zap the service because trying to stopping them would fail. With systemd you don't need this, since it can track the real state of its services thanks to cgroups. And kill *really* kills all the processes associated to a service, something that OpenRC, by design, cannot do. I believe the difference is substantial enough that it should not be stated that they are equivalent. But except for that minor nitpick, it looks great. Thanks again. Regards.
Re: [gentoo-user] OK, so not everything works properly with systemd
On Sat, Mar 21, 2015 at 11:21 AM, Daniel Frey djqf...@gmail.com wrote: Hi list, Hi. In one of my earlier posts I mentioned I wasn't having any issues with systemd. Well, I guess I lied, although I didn't know about it at the time. My laptop works fine, no issues. My desktop, however, has an issue, but only while rebooting. I use mdadm to access my IMSM raid, and during the reboot process, the last message I see is (from memory, so it's not exact): Stopping mdmon... And it hangs there. The journal shows this: = -- Reboot -- Mar 18 20:48:42 osoikaze systemd-journal[485]: Journal stopped Mar 18 20:48:42 osoikaze systemd-shutdown[1]: Sending SIGTERM to remaining processes... Mar 18 20:48:41 osoikaze systemd[1]: Shutting down. = mdmon is normally stopped right at the end, so it should be a part of 'Sending SIGTERM to remaining processes'. The Journal stops, then from what I gather, it hangs on the next one, which is mdmon. I have left it for a half an hour and it doesn't do anything. When rebooting: = Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: active with 4 out of 4 devices Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: not clean -- starting background reconstruction Mar 18 20:49:39 osoikaze kernel: md: bindsdi Mar 18 20:49:39 osoikaze kernel: md: bindsdh Mar 18 20:49:39 osoikaze kernel: md: bindsdg Mar 18 20:49:39 osoikaze kernel: md: bindsdf Mar 18 20:49:39 osoikaze kernel: md: bindsdi Mar 18 20:49:39 osoikaze kernel: md: bindsdg = Indicating that mdmon was not stopped properly. (The array starts a rebuild.) Checking /proc/mdstat confirms this. Now this is the odd thing: `systemctl poweroff` works fine! It shuts everything down, and turns my workstation off without corrupting the RAID array! So why does `systemctl reboot` not want to work? I'm a little confused. What kind of initramfs are you using? Supposedly, the only difference between poweroff and reboot is that the former turns off the machine and reboot does a reset. In either case, systemd pivots back to the initramfs before umounting everything, so perhaps there lies the problem. I also noticed this in the USE flags for systemd: - - sysv-utils : Install sysvinit compatibility symlinks and manpages for init, telinit, halt, poweroff, reboot, runlevel, and shutdown Should I enable that USE flag? No. In Gentoo in particular the SysV compatibility is completely useless. (By the way, KDE shows the same behaviour. If I shutdown with the K Menu, it works. Reboot from the K Menu hangs.) KDE (as GNOME, Xfce, and everything else) uses logind, so it's equivalent to do systemctl poweroff or click Power Off in your DE. I would bet on the initramfs. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] How to poweroff the system from user?
On Sat, Mar 21, 2015 at 1:47 PM, Rich Freeman ri...@gentoo.org wrote:
On Sat, Mar 21, 2015 at 3:39 PM, German gentger...@gmail.com wrote:
No, I am trying to shutdown from a console
Well, the old answer would be that you need to use sudo to run it, as
shutting down is a privileged operation.
I suspect that the new answer is that with appropriate
policykit/consolekit/etc settings you can probably allow somebody
sitting at a physical console to shut down the system, or any
logged-in user if you prefer. However, I haven't actually set that up
myself.
logind does that for you automagically™. The first seat has the rights to
poweroff or reboot the machine, and it can differentiate between local and
remote logins. You can check if your user session has the permissions to
poweroff/reboot via dbus:
$ gdbus call --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanPowerOff
('yes',)
$ gdbus call --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanReboot
('yes',)
But you need systemd to use logind1. There has been some attempts to
reimplement logind outside systemd, but I'm not sure how advanced they are.
This kind of problems were one of the reasons for creating logind.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] OK, so not everything works properly with systemd
On Sat, Mar 21, 2015 at 3:38 PM, Daniel Frey djqf...@gmail.com wrote: [...] I was using genkernel, but it was whining about not supporting systemd, so I tried dracut for the first time. However, the initramfs created by genkernel has the same issue. I didn't do any special configuation of dracut, I read that just running it can usually create a initramfs without any additional configuration. It did detect I have mdadm of course, or my system wouldn't have booted at all. That's weird. [...] I was wondering more about the symlinks to the regular shutdown/reboot/etc commands. I never actually checked to see if they're already systemd-aware. They are; basically everything nowadays is systemd aware. Even OpenRC can now use some of its configurations. Could you run this immediately after booting: systemd-delta Just to check that the unit files you are using are not being overridden by something. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] openrc-systemd command comparison
On Mon, Mar 16, 2015 at 7:47 PM, Daniel Frey djqf...@gmail.com wrote: Hey all, I've now converted two systems to systemd and so far haven't had too much issues with systemd itself, other than me constantly forgetting commands. Is there a nice table or chart somewhere that lists openrc commands with equivalent systemd commands? That would really help me from bashing my head and then wandering through man pages for a while trying to figure out what I want to do. I'll eventually remember but it would be nice to have something to help me along. My memory sure isn't what it used to be. I remember seeing a table like that in the wiki a long time ago, but I can't find it now. Anyway, the translatable commands are obvious: /etc/init.d/service start → systemctl start service /etc/init.d/service stop → systemctl stop service and the rest are usually are not translatable. There is nothing like systemctl mask service in OpenRC, AFAIK, and there is no equivalent for /etc/init.d/service zap in systemd (the whole idea of systemd is that an ugly hack like zap will never be necessary). Not sure if this will help you. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Screen: Cannot open your terminal '/dev/tty1' - please check
On Fri, Mar 13, 2015 at 10:06 AM, German gentger...@gmail.com wrote: On Fri, 13 Mar 2015 15:59:04 + Neil Bothwick n...@digimed.co.uk wrote: On 13 March 2015 15:52:41 GMT+00:00, German gentger...@gmail.com wrote: This is very strange. When I boot up my box and login as a user I can use screen. But if I booted up and logged in as root first and then su user, the user have the error message displayed in the subject line. Any ideas? -- German gentger...@gmail.com Try su - l user. The same error Are you using logind? Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] Screen: Cannot open your terminal '/dev/tty1' - please check
On Fri, Mar 13, 2015 at 10:22 AM, German gentger...@gmail.com wrote: [ ... ] Are you using logind? Good question. What is logind? How I can find out what am I using? If you are using systemd, you are using logind. Otherwise you are not. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummiboot does not display new kernel
On Wed, Mar 11, 2015 at 1:11 AM, J. Roeleveld jo...@antarean.org wrote: [...] Canek, I don't see these long filenames in your filetree-listing. You have a directory with the UUID, but then just the kernel-version numbers. Or am I looking at the wrong email? You are: # tree -l /boot/loader/ /boot/loader/ ├── entries │ ├── db93dd0e1382198eb26650c05430b171-3.18.9.conf │ ├── db93dd0e1382198eb26650c05430b171-3.19.0.conf │ └── db93dd0e1382198eb26650c05430b171-3.19.1.conf ├── gentoo.bmp └── loader.conf 1 directory, 5 files # tree -l /boot/db93dd0e1382198eb26650c05430b171/ /boot/db93dd0e1382198eb26650c05430b171/ ├── 3.18.9 │ ├── initrd │ └── kernel ├── 3.19.0 │ ├── initrd │ └── kernel └── 3.19.1 ├── initrd └── kernel Here it works. What's more, Stefan said it worked in another machine of his. Seems like a heisenbug. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummiboot does not display new kernel
On Sun, Mar 8, 2015 at 1:57 PM, Stefan G. Weichinger li...@xunil.at wrote: On 08.03.2015 19:10, Stefan G. Weichinger wrote: But no big problem, I can edit that conf-file whenever I install a new kernel. Sure, would be nice to solve. fun fact: compiled and installed 4.0.0-rc2 ... visible at boot time at first try I hate heisenbugs. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummiboot does not display new kernel
On Sun, Mar 8, 2015 at 9:59 AM, Tom H tomh0...@gmail.com wrote: On Sun, Mar 8, 2015 at 11:34 AM, Stefan G. Weichinger li...@xunil.at wrote: I compiled the latest gentoo-sources-3.19.1 with Canek's kerninst tool. It is configured to generate a loader-entry for the gummiboot bootloader. That bootloader is the default entry in the UEFI boot order and it works ... I can boot the older kernels ... but it does not show me the latest kernel 3.19.1 but why? I edited /boot/loader/loader.conf ... a changed timeout gets read ... but 3.19.1 is never displayed. Are the ownership and mode of e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf the same as the two others (although I'd assume that it wouldn't matter) and is it formatted correctly? The /boot partition in UEFI systems needs to be vfat. Permissions are not gonna matter that much in that. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummiboot does not display new kernel
On Sun, Mar 8, 2015 at 10:37 AM, Stefan G. Weichinger li...@xunil.at wrote: On 08.03.2015 17:10, Stefan G. Weichinger wrote: On 08.03.2015 16:59, Tom H wrote: Are the ownership and mode of e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf the same as the two others (although I'd assume that it wouldn't matter) and is it formatted correctly? Yes, I think so: # ls -l /boot/loader/entries/ total 2 -rwxr-xr-x 1 root root 329 16. Feb 16:01 e55a6b6a09bd2b1c50216272545a8d1f-3.18.6-gentoo.conf -rwxr-xr-x 1 root root 329 24. Feb 12:55 e55a6b6a09bd2b1c50216272545a8d1f-3.19.0-gentoo.conf -rwxr-xr-x 1 root root 329 8. Mär 15:20 e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf moved e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf to simply stefan.conf ... then it gets displayed (and boots fine as well) maybe we should name the conf-files in a different way? I just followed the examples in the gummiboot homepage[1]. It's weird that you need to change the name. Regards. [1] http://freedesktop.org/wiki/Software/gummiboot/ -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummiboot does not display new kernel
On Sun, Mar 8, 2015 at 10:51 AM, Tom H tomh0...@gmail.com wrote: [ ... ] version?! I've never seen this and I don't use it. From [1]: The entry configuration files understand the following keywords: title text to show in the menu version version string to append to the title when the title is not unique machine-id machine identifier to append to the title when the title is not unique efi executable EFI image options options to pass to the EFI image / kernel command line linux linux kernel image (gummiboot still requires the kernel to have an EFI stub) initrd initramfs image (gummiboot just adds this as option initrd=) splash BMP image file to show during bootup Regards. [1] http://freedesktop.org/wiki/Software/gummiboot/ -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummiboot does not display new kernel
On Sun, Mar 8, 2015 at 11:05 AM, Neil Bothwick n...@digimed.co.uk wrote: On Sun, 8 Mar 2015 10:51:38 -0600, Canek Peláez Valdés wrote: Are the ownership and mode of e55a6b6a09bd2b1c50216272545a8d1f-3.19.1-gentoo.conf the same as the two others (although I'd assume that it wouldn't matter) and is it formatted correctly? The /boot partition in UEFI systems needs to be vfat. Permissions are not gonna matter that much in that. But filename lengths may do. What is the maximum length for FAT32? Is it possible both files are considered the same? In that case, it would not work in my case, and it does (see my last reply). Besides, it has been working with those filenames for months now. FAT32 supports (IIRC) 256 long filenames. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummibootx64.efi OR bootx64.efi?
On Mon, Mar 2, 2015 at 2:27 AM, German gentger...@gmail.com wrote: On Mon, 2 Mar 2015 02:10:33 -0600 Canek Peláez Valdés can...@gmail.com wrote: On Mon, Mar 2, 2015 at 2:03 AM, German gentger...@gmail.com wrote: On Mon, 2 Mar 2015 01:41:19 -0600 Canek Peláez Valdés can...@gmail.com wrote: On Sun, Mar 1, 2015 at 11:11 PM, German gentger...@gmail.com wrote: Out of curiosity I looked into my /boot partition and found two .efi files. One is /boot/efi/gummiboot/gummibootx64.efi and another is /boot/efi/boot/bootx64.efi. I remember I've created /boot/efi/boot/bootx64.efi during install by copying kernel image file to it and supposedly it was for efibootmng. I think gummiboot has created its own gummibootx64.efi. Is that safe to delete */boot/bootx64.efi? Thanks They are the same image; do an md5sum of both, you'll see that they have the same checksum. I believe Boot/BOOTX64.EFI is the default location where the BIOS (or whatever is called in UEFI systems) looks for an image to boot, and gummiboot/gummibootx64.efi is just a copy. I'm not sure, but I would not delete it: gummiboot creates both copies of the file. Well, no, I have created */boot/bootx64.efi manually and */gummiboot/gummibootx64.efi was created by gummiboot install. In my machines boot/bootx64.efi was created by gummiboot, and it's the same ile as gummiboot/gummibootx64.efi (same checksum). I just did md5sums and yes, gummibootx64.efi and bootx64.efi are the same Mmmh. So it was gummitboot and not created by hand? Anyway, as I said earlier; I think boot/bootx64.efi is the default location, and the other one is kinda a backup. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummibootx64.efi OR bootx64.efi?
On Mon, Mar 2, 2015 at 2:18 AM, German gentger...@gmail.com wrote: On Mon, 2 Mar 2015 02:10:33 -0600 Canek Peláez Valdés can...@gmail.com wrote: On Mon, Mar 2, 2015 at 2:03 AM, German gentger...@gmail.com wrote: On Mon, 2 Mar 2015 01:41:19 -0600 Canek Peláez Valdés can...@gmail.com wrote: On Sun, Mar 1, 2015 at 11:11 PM, German gentger...@gmail.com wrote: Out of curiosity I looked into my /boot partition and found two .efi files. One is /boot/efi/gummiboot/gummibootx64.efi and another is /boot/efi/boot/bootx64.efi. I remember I've created /boot/efi/boot/bootx64.efi during install by copying kernel image file to it and supposedly it was for efibootmng. I think gummiboot has created its own gummibootx64.efi. Is that safe to delete */boot/bootx64.efi? Thanks They are the same image; do an md5sum of both, you'll see that they have the same checksum. I believe Boot/BOOTX64.EFI is the default location where the BIOS (or whatever is called in UEFI systems) looks for an image to boot, and gummiboot/gummibootx64.efi is just a copy. I'm not sure, but I would not delete it: gummiboot creates both copies of the file. Well, no, I have created */boot/bootx64.efi manually and */gummiboot/gummibootx64.efi was created by gummiboot install. In my machines boot/bootx64.efi was created by gummiboot, and it's the same ile as gummiboot/gummibootx64.efi (same checksum). What does bootctl says? bootctl: command not found. How to use bootctl? Sorry, my bad; bootctl comes with systemd. I thought it came with gummiboot. However, gummiboot status shows almost the same information. In my case: Boot Loader Binaries: ESP: /dev/disk/by-partuuid/b4abf4dc-abfc-45c5-b356-30db1e0b15b3 File: └─/EFI/gummiboot/gummibootx64.efi (gummiboot 45) File: └─/EFI/Boot/BOOTX64.EFI (gummiboot 45) Boot Loader Entries in EFI Variables: Title: UEFI OS ID: 0x0001 Status: active, boot-order Partition: /dev/disk/by-partuuid/b4abf4dc-abfc-45c5-b356-30db1e0b15b3 File: └─/EFI/BOOT/BOOTX64.EFI As you can see, Boot/BOOTX64.EFI is actually gummiboot. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummibootx64.efi OR bootx64.efi?
On Mon, Mar 2, 2015 at 2:03 AM, German gentger...@gmail.com wrote: On Mon, 2 Mar 2015 01:41:19 -0600 Canek Peláez Valdés can...@gmail.com wrote: On Sun, Mar 1, 2015 at 11:11 PM, German gentger...@gmail.com wrote: Out of curiosity I looked into my /boot partition and found two .efi files. One is /boot/efi/gummiboot/gummibootx64.efi and another is /boot/efi/boot/bootx64.efi. I remember I've created /boot/efi/boot/bootx64.efi during install by copying kernel image file to it and supposedly it was for efibootmng. I think gummiboot has created its own gummibootx64.efi. Is that safe to delete */boot/bootx64.efi? Thanks They are the same image; do an md5sum of both, you'll see that they have the same checksum. I believe Boot/BOOTX64.EFI is the default location where the BIOS (or whatever is called in UEFI systems) looks for an image to boot, and gummiboot/gummibootx64.efi is just a copy. I'm not sure, but I would not delete it: gummiboot creates both copies of the file. Well, no, I have created */boot/bootx64.efi manually and */gummiboot/gummibootx64.efi was created by gummiboot install. In my machines boot/bootx64.efi was created by gummiboot, and it's the same ile as gummiboot/gummibootx64.efi (same checksum). What does bootctl says? Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] gummibootx64.efi OR bootx64.efi?
On Sun, Mar 1, 2015 at 11:11 PM, German gentger...@gmail.com wrote: Out of curiosity I looked into my /boot partition and found two .efi files. One is /boot/efi/gummiboot/gummibootx64.efi and another is /boot/efi/boot/bootx64.efi. I remember I've created /boot/efi/boot/bootx64.efi during install by copying kernel image file to it and supposedly it was for efibootmng. I think gummiboot has created its own gummibootx64.efi. Is that safe to delete */boot/bootx64.efi? Thanks They are the same image; do an md5sum of both, you'll see that they have the same checksum. I believe Boot/BOOTX64.EFI is the default location where the BIOS (or whatever is called in UEFI systems) looks for an image to boot, and gummiboot/gummibootx64.efi is just a copy. I'm not sure, but I would not delete it: gummiboot creates both copies of the file. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] logs in the browser?
On Tue, Feb 24, 2015 at 10:33 AM, Stefan G. Weichinger li...@xunil.at wrote: [ ... ] Maybe I could set up some other web-app that (a) looks at the link pointing to the postfix.service-logs and (b) filters them? (With my programmer's hat on): I think the easiest way would be to create a little client that downloads the logs in JSON format, and then do the filtering off-site. If I'm not mistaken, libmicrohttpd supports Accept-Encoding: gzip, and therefore the used bandwidth should not be a lot. Also, you can get the last cursor from the journal the first time, and next time you download logs, you start from that cursor on, so you don't download everything again. I don't see many advantages on doing the filtering on-site. Specially if, after a while, you are handling several servers. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] syslog-ng: how to read the log files
On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] syslog-ng: how to read the log files
On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. Regards. https://github.com/balabit/syslog-ng/issues/314 -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] syslog-ng: how to read the log files
On Mon, Feb 23, 2015 at 1:31 PM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 12:10:18 -0600 schrieb Canek Peláez Valdés can...@gmail.com: On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. I remember getting a small number of messages like that, too, on my laptop. However, it's at the university, so I can't check now to see what types of messages were missed (if any; if I understand [1] correctly, those messages are most likely bogus?). But yeah, that's any idea, Covici: see what's in /var/log/messages, compare that to the journalctl output, and check if any messages were actually missed (diff -U might be of help here). And if/once you did that, what kinds of messages were missed, if any? If those messages really are bogus, you shouldn't see any differences between the two
Re: [gentoo-user] logs in the browser?
On Mon, Feb 23, 2015 at 4:20 PM, Stefan G. Weichinger li...@xunil.at wrote: As I see that syslog-thread ... I think of setting up something for apache that allows a client to browse and search through the postfix-logs for his domain. Any good hints what to use for that purpose? Stefan, if you already have systemd (which I believe you do), why don't you compile in the support for microhttpd and use the journal? This is the exact scenario for which systemd-journal-gatewayd[1] was written. Regards. [1] http://www.freedesktop.org/software/systemd/man/systemd-journal-gatewayd.service.html -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
