Dale wrote:
>
> root@fireball / # equery d sys-apps/systemd-utils
> * These packages depend on sys-apps/systemd-utils:
> sys-apps/systemd-tmpfiles-250 (sys-apps/systemd-utils[tmpfiles])
> sys-fs/udev-250 (sys-apps/systemd-utils[udev,...])
> virtual/libudev-232-r7 (!systemd ? sys-apps/systemd-util
I suggest either taking a full dd|bzip2 style backup of the hardisk to
removable media for the simplest reinstall. Compliment with borgbackup or
dervish for space efficient backups to capture more recent changes. Reinstall
is the reverse .. lay down the dd image update from the backups with r
Julien Roy wrote:
> Hello,
>
> On 6/19/22 21:38, Dale wrote:
>> Anyone have ideas on this? I mess up something? Catch the tree in a
>> bad state? Something else I'm not aware of? It's not making sense to
>> me yet. :/
>
> sys-fs/udev has been replaced by a USE flag on the
> sys-apps/systemd-ut
Dale wrote:
> Howdy all,
>
> Once a month or so, or when told to by a news item, I run emerge with
> the --depclean option. I look at the list in case there something there
> I want to keep or something that shouldn't be removed, like gcc or
> something. I ran it a bit ago and got back this:
>
>
Hello,
On 6/19/22 21:38, Dale wrote:
Anyone have ideas on this? I mess up something? Catch the tree in a
bad state? Something else I'm not aware of? It's not making sense to
me yet. :/
sys-fs/udev has been replaced by a USE flag on the
sys-apps/systemd-utils package. When you updated you
Howdy all,
Once a month or so, or when told to by a news item, I run emerge with
the --depclean option. I look at the list in case there something there
I want to keep or something that shouldn't be removed, like gcc or
something. I ran it a bit ago and got back this:
> >>> These are the pack
Em dom., 19 de jun. de 2022 às 14:33, Michael
escreveu:
>
> On Sunday, 19 June 2022 18:22:34 BST Grant Edwards wrote:
> > On 2022-06-19, Francisco Ares wrote:
> > > Just for the sake of preventing a future failure, besides personal
> > > files (minimum and obvious) the "world" file and the binary
Em dom., 19 de jun. de 2022 às 14:22, Grant Edwards
escreveu:
>
> On 2022-06-19, Francisco Ares wrote:
>
> > Just for the sake of preventing a future failure, besides personal
> > files (minimum and obvious) the "world" file and the binary packages,
> > built along with the package installation,
On Sunday, 19 June 2022 18:22:34 BST Grant Edwards wrote:
> On 2022-06-19, Francisco Ares wrote:
> > Just for the sake of preventing a future failure, besides personal
> > files (minimum and obvious) the "world" file and the binary packages,
> > built along with the package installation, what else
On 2022-06-19, Francisco Ares wrote:
> Just for the sake of preventing a future failure, besides personal
> files (minimum and obvious) the "world" file and the binary packages,
> built along with the package installation, what else should I backup
> so that I would be able to quickly restore the
Good day!
First of all, sorry for the late reply. I had to attend to a course a
bit far away from home and it was pretty intense.
Now, back home, I'll try the suggestions, thanks!
Just for the sake of preventing a future failure, besides personal
files (minimum and obvious) the "world" file and
Alan,
On Saturday, 2022-06-18 23:54:26 -0400, you wrote:
> ...
> At this point in time, if you have a problem, especially on linux, it is
> almost never the problem that existed before a penguin tried to solve it
> for you.
Perhaps Ubuntu would be your friend?
> ...
> Example:
>
> Old way:
>
On Sunday, 19 June 2022 04:54:26 BST Alan Grimes wrote:
[snippage of long prose ...]
> Example:
>
> Old way:
>
> "My boot drive is plugged into this port on the motherboard"
>
> New way:
>
> Spend hours figuring out what your UUID is, create a physical pocket
> folder (which you will subsequ
On 20/12/2021 09:10, Nikos Chantziaras wrote:
Has anyone here noticed that x.org likes to crash sometimes as of late?
Never happened before, going years and years back. The last month or so,
I've got three x.org crashes:
systemd-coredump[204553]: [🡕] Process 453 (X) of user 0 dumped core.
So
On Saturday, 18 June 2022 19:35:54 BST Jack wrote:
> In terms of replying to the list or the person who sent the message to
> which you are replying, look at the "To:" field in your email software
> before you hit "Send." You need to see the list address there. Your
> email software probably has
15 matches
Mail list logo