On 10/26/24 18:10, Samuel Sieb wrote:
On 10/26/24 6:01 PM, ToddAndMargo via users wrote:
On 10/26/24 17:55, Samuel Sieb wrote:
On 10/26/24 5:40 PM, ToddAndMargo via users wrote:
On 10/26/24 17:29, ToddAndMargo via users wrote:
The tune2fs command is used to modify the filesystem mount options
On 10/26/24 6:01 PM, ToddAndMargo via users wrote:
On 10/26/24 17:55, Samuel Sieb wrote:
On 10/26/24 5:40 PM, ToddAndMargo via users wrote:
On 10/26/24 17:29, ToddAndMargo via users wrote:
The tune2fs command is used to modify the filesystem mount options
and settings for ext2, ext3, and ext4
On 10/26/24 17:55, Samuel Sieb wrote:
On 10/26/24 5:40 PM, ToddAndMargo via users wrote:
On 10/26/24 17:29, ToddAndMargo via users wrote:
The tune2fs command is used to modify the filesystem mount options
and settings for ext2, ext3, and ext4 file systems. The option -E
force_fsck enables forc
On 10/26/24 5:40 PM, ToddAndMargo via users wrote:
On 10/26/24 17:29, ToddAndMargo via users wrote:
The tune2fs command is used to modify the filesystem mount options and
settings for ext2, ext3, and ext4 file systems. The option -E
force_fsck enables forced filesystem checks (fsck) on every re
On 10/26/24 17:29, ToddAndMargo via users wrote:
On 10/26/24 16:49, ToddAndMargo via users wrote:
On 10/25/24 15:55, Jonathan Billings wrote:
On Oct 25, 2024, at 08:15, ToddAndMargo via users
wrote:
# tune2fs -E force_fsck /dev/nvme0n1p4
tune2fs 1.47.0 (5-Feb-2023)
tune2fs: Bad magic number
On 10/26/24 16:49, ToddAndMargo via users wrote:
On 10/25/24 15:55, Jonathan Billings wrote:
On Oct 25, 2024, at 08:15, ToddAndMargo via users
wrote:
# tune2fs -E force_fsck /dev/nvme0n1p4
tune2fs 1.47.0 (5-Feb-2023)
tune2fs: Bad magic number in super-block while trying to open /dev/
nvme0n1
On 10/26/24 4:49 PM, ToddAndMargo via users wrote:
Followup question: is there a flag to throw that tells fsck
to "repair"? I never found one in "man fsck".
That depends on what you mean. It will repair if not run in read-only
mode. You can only do it if the filesystem isn't mounted. There
On 10/25/24 15:55, Jonathan Billings wrote:
On Oct 25, 2024, at 08:15, ToddAndMargo via users
wrote:
# tune2fs -E force_fsck /dev/nvme0n1p4
tune2fs 1.47.0 (5-Feb-2023)
tune2fs: Bad magic number in super-block while trying to open /dev/nvme0n1p4
/dev/nvme0n1p4 contains a crypto_LUKS file syste
On 25/10/24 21:31, ToddAndMargo via users wrote:
On 10/23/24 20:56, ToddAndMargo via users wrote:
Hi All,
$ rpm -qa kernel
kernel-6.5.10-200.fc38.x86_64
kernel-6.11.3-100.fc39.x86_64
kernel-6.11.4-201.fc40.x86_64
Problem, only the 38 kernel shows in grub.
How do I get the 40 kernel to show in
On 26/10/24 02:58, Patrick O'Callaghan wrote:
On Fri, 2024-10-25 at 22:30 +1100, Stephen Morris wrote:
On 25/10/24 09:25, Patrick O'Callaghan wrote:
On Fri, 2024-10-25 at 09:09 +1100, Stephen Morris wrote:
I don't want to turn off
sending in html because that will impact all emails I send, and
On 10/25/24 12:45 PM, Jeffrey Walton wrote:
On Tue, Oct 22, 2024 at 8:42 PM home user via users
wrote:
(f-40; gnome; stand-alone dual-boot workstation; kernel 6.11.3)
Selected command output...
-bash.2[~]: rpm -qa kernel
kernel-6.10.12-200.fc40.x86_64
kernel-6.11.3-200.fc40.x86_64
-bash.3[~]
On 10/25/24 05:41, Will McDonald wrote:
On Fri, 25 Oct 2024 at 13:16, ToddAndMargo via users
mailto:users@lists.fedoraproject.org>>
wrote:
> On Fri, 25 Oct 2024 at 11:57, ToddAndMargo via users
I am confused. When I tried using --allowerasing,
I got:
Unknown argument
I've got an old HP 4050 N LaserJet. A couple of years ago it stopped being able
to print without generating an error after the first page.
The error is printed on the second page (then nothing more is printed):
ERROR:
typecheck
OFFENDING COMMAND:
idiv
STACK:
5
--nostringval--
--nostringval--
On Fedora 40, the version of hplip is 3.23.12.
On https://developers.hp.com/hp-linux-imaging-and-printing/gethplip the version
is Version: 3.24.4.
The release notes at the above url seem to indicate that the only changes are
addition kinds of HP printer.
So, is it correct that there is no need t
Andre Robatino wrote:
>> Thanks for this. I thought that dnf5 didn't have either the
>> --skip-broken or --skip-unavailable options (despite dnf5 itself
>> recommending those options when a command failed), but after
>> reading this I retried my install command with those options AFTER
>> my long l
On 10/25/24 15:08, Andre Robatino wrote:
Thanks for this. I thought that dnf5 didn't have either the --skip-broken or
--skip-unavailable options (despite dnf5 itself recommending those options when
a command failed), but after reading this I retried my install command with
those options AFTER
16 matches
Mail list logo
