On 4/14/24 14:20, Tim via users wrote:
On Sun, 2024-04-14 at 09:49 -0400, Fulko Hew wrote:
Then in corporate life, I needed to ensure a stable development
environment.
This is one of the big problems with computers in the work place. You
may have single-task computers which you want to work,
On 4/15/24 20:04, Tim via users wrote:
Samuel Sieb:
The only reason this is a problem for some manufacturers is because they
want to keep it proprietary. Printers and scanners (and any other
hardware) that use open standards or provide open-source drivers work
great with Linux. Compare the
Tim:
>> Let's be clear, we're not talking about annoying changes to how the
>> desktop looks, that can be put up with. But when you find essential
>> software and/or hardware doesn't work anymore, or doesn't exist
>> anymore, and support libraries are incompatible, that's a deal-breaker.
>>
>>
On 4/14/24 11:20, Tim via users wrote:
Let's be clear, we're not talking about annoying changes to how the
desktop looks, that can be put up with. But when you find essential
software and/or hardware doesn't work anymore, or doesn't exist
anymore, and support libraries are incompatible, that's
On 4/14/24 06:49, Fulko Hew wrote:
Thanks for giving me the guts to do a brute force power cycle
in the apparent middle of an upgrade in progress.
(FYI. The upgrade to F39 also hung at the boot message,
and it too needed a power-cycle to successfully boot.)
If it's still at the boot
On Sun, 2024-04-14 at 09:49 -0400, Fulko Hew wrote:
> Then in corporate life, I needed to ensure a stable development
> environment.
This is one of the big problems with computers in the work place. You
may have single-task computers which you want to work, and not mess
around with. You may
On Sun, Apr 14, 2024 at 9:49 AM Fulko Hew wrote:
> On Sun, Apr 14, 2024 at 7:16 AM Patrick O'Callaghan
> wrote:
> Then it was back to are-install for F33 because it was a hardware
> replacement, and Linux/Fedora does not have a one-true backup/restore
> process that I have ever seen. [...]
On Sun, Apr 14, 2024 at 7:16 AM Patrick O'Callaghan
wrote:
> On Sat, 2024-04-13 at 17:37 -0400, Fulko Hew wrote:
> > > On Sat, 2024-04-13 at 13:29 -0700, Fulko Hew wrote:
> > > > I don't update my Fedora systems unless I have a real need,
> > > > so yesterday I started updating from F35 to F38
>
On Sat, 2024-04-13 at 17:37 -0400, Fulko Hew wrote:
> > On Sat, 2024-04-13 at 13:29 -0700, Fulko Hew wrote:
> > > I don't update my Fedora systems unless I have a real need,
> > > so yesterday I started updating from F35 to F38
Just as an aside: leaving a two year old Fedora system without
On Sat, Apr 13, 2024 at 6:05 PM Jeffrey Walton wrote:
>
>
> On Sat, Apr 13, 2024 at 4:30 PM Fulko Hew wrote:
>
>>
>> I don't update my Fedora systems unless I have a real need,
>> so yesterday I started updating from F35 to F38
>> I used the:
>>
>> dnf system-update download --releasever=xx
>>
On Sat, Apr 13, 2024 at 4:30 PM Fulko Hew wrote:
>
> I don't update my Fedora systems unless I have a real need,
> so yesterday I started updating from F35 to F38
> I used the:
>
> dnf system-update download --releasever=xx
> process.
>
Related, you should follow <
On Sat, Apr 13, 2024 at 5:04 PM Patrick O'Callaghan
wrote:
> On Sat, 2024-04-13 at 13:29 -0700, Fulko Hew wrote:
> > I don't update my Fedora systems unless I have a real need,
> > so yesterday I started updating from F35 to F38
> > I used the:
> >
> > dnf system-update download --releasever=xx
On Sat, 2024-04-13 at 13:29 -0700, Fulko Hew wrote:
> I don't update my Fedora systems unless I have a real need,
> so yesterday I started updating from F35 to F38
> I used the:
>
> dnf system-update download --releasever=xx
> process.
>
> - My first update from F35 to F36 worked.
> - Then I did
I don't update my Fedora systems unless I have a real need,
so yesterday I started updating from F35 to F38
I used the:
dnf system-update download --releasever=xx
process.
- My first update from F35 to F36 worked.
- Then I did the F36 to F37 update.
KDE wouldn't work until I uninstalled
14 matches
Mail list logo