On Sun, Aug 18, 2024 at 9:33 AM User of Fedoras via users <
users@lists.fedoraproject.org> wrote:
> Hi,
> I had changed from Fedora to openSUSE due to an error on LUKS during
> boot (it would not see the correct devices, dracut would timeout). I
> could boot using an older k
On Sun, Aug 18, 2024 at 9:43 AM Roger Heflin wrote:
> I don't know specifically on this bug. But the 2 common mistakes fall
> into some piece failing and causing dracut to not properly detect what
> modules the boot device needs to use. And when that happens dracut
> times out
bottom-posting, somewhat manually.
On Sun, Aug 18, 2024 at 1:43 PM Roger Heflin wrote:
>
> I don't know specifically on this bug. But the 2 common mistakes fall
> into some piece failing and causing dracut to not properly detect what
> modules the boot device needs to us
I don't know specifically on this bug. But the 2 common mistakes fall
into some piece failing and causing dracut to not properly detect what
modules the boot device needs to use. And when that happens dracut
times out looking for root. I have also seen bugs where the
necessary module need
Hi,
I had changed from Fedora to openSUSE due to an error on LUKS during
boot (it would not see the correct devices, dracut would timeout). I
could boot using an older kernel but couldn't figure out what the
issue was/hadn't had the patience.
Yesterday it happened on openSUSE and, in tha
On Tue, 2024-07-30 at 14:49 -0700, Samuel Sieb wrote:
> > Tried that and this time it did get the correct UUID in the boot
> > command line (verified from the grub menu). However the boot failed
> > with some 'not found' errors. I can't completely discount the
> > possibility of some errors in copy
On 7/30/24 2:45 PM, Patrick O'Callaghan wrote:
On Tue, 2024-07-30 at 14:13 -0700, Samuel Sieb wrote:
A logical place to look is in /etc/dracut.d. The manpage for
dracut.cmdline says you can specify a "root=UUID=..." parameter,
but
not where you put it ('dracut root=...
On Tue, 2024-07-30 at 14:13 -0700, Samuel Sieb wrote:
> > A logical place to look is in /etc/dracut.d. The manpage for
> > dracut.cmdline says you can specify a "root=UUID=..." parameter,
> > but
> > not where you put it ('dracut root=...' and 'd
7;ll eventually change it,
but
shouldn't affect root).
Not sure what to do other than manually editing the loader entry.
I think you have to edit the loader entries. They won't be
regenerated.
Nope, didn't work. I edited the current entry, reran grub2-mkconfig
etc. and dracut.
The idea is to edit the files to get the system booted correctly, and
then use grub2-mkconfig and dracut to re-auto-generate the files. But
I agree the manual editing is a last resort.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsu
g the loader entry.
>
> I think you have to edit the loader entries. They won't be
> regenerated.
>
Nope, didn't work. I edited the current entry, reran grub2-mkconfig
etc. and dracut. I checked the entries and they are regenerated from
somewhere with the changes reverted, so
On 7/30/24 5:48 AM, Patrick O'Callaghan wrote:
The loader entry is still pointing to the SSD:
# cat
/boot/loader/entries/63f58eeb1e8640c79ad45bdc9261a2bb-6.9.11-200.fc40.x86_64.conf
title Fedora Linux (6.9.11-200.fc40.x86_64) 40 (KDE Plasma)
version 6.9.11-200.fc40.x86_64
linux /vmlinuz-6.9.11-
rebuild initramfs. FWIW, I have never
> needed to use --fstab with dracut.
I'd definitely not edit the grub.cfg files directly. They both have a
commentary saying they are autogenerated. I assume /etc/kernel/cmdline
is also autogenerated (rpm says it doesn't belong to any package).
How
/boot/grub2/grub.cfg,
/etc/kernel/cmdline, and /etc/fstab to make sure everything is using
the correct UUIDs, then get everything booted (manually addressing
issues as required), and then rebuild initramfs. FWIW, I have never
needed to use --fstab
*but* root is still being mounted from the SDD.
I've run "dracut --fstab --force" (which supposedly should generate an
initramd with root on the NVMe) and "grub2-mkconfig; grub2-install" but
it makes no difference. The fstab does have the correct root line
pointing to the
On Sun, May 19, 2024 at 09:42:46PM GMT, Barry Scott wrote:
>
>
> > On 19 May 2024, at 15:58, Frédéric wrote:
> >
> > Is it because F38 is past end of support or is it just related to dracut?
>
> You can query the EOL date like this:
>
> $ host
> On 19 May 2024, at 15:58, Frédéric wrote:
>
> Is it because F38 is past end of support or is it just related to dracut?
You can query the EOL date like this:
$ hostnamectl
Static hostname: armf38.chelsea.private
Icon name: computer-vm
Chassis: vm 🖴
On Sun, 2024-05-19 at 16:58 +0200, Frédéric wrote:
> Hi,
>
> I get this strange message when I boot:
> [ ↑↑ ] This OS version (Fedora Linux 38 (Thirty Eight)
> dracut-059-5.fc38 (Init ramfs)) is past its end-of-support date
> (2024-05-14).
>
> Is it because F38 is past
Hi,
I get this strange message when I boot:
[ ↑↑ ] This OS version (Fedora Linux 38 (Thirty Eight)
dracut-059-5.fc38 (Init ramfs)) is past its end-of-support date
(2024-05-14).
Is it because F38 is past end of support or is it just related to dracut?
Thanks
On Sat, 6 Aug 2022 10:59:06 -0500
Ian Pilcher wrote:
> Anyone know the trick to getting dracut to include the udev rules in
> /etc/udev/rules.d in the initramfs that it builds?
>
> I'm sure that there's a way to include a specific file, but it really
> seems like t
Anyone know the trick to getting dracut to include the udev rules in
/etc/udev/rules.d in the initramfs that it builds?
I'm sure that there's a way to include a specific file, but it really
seems like there ought to be a way to include all of the udev rules.
(Frankly, it seems like tha
> On 9 Jul 2022, at 06:49, francis.montag...@inria.fr wrote:
>
>
> Hi.
>
> On Thu, 07 Jul 2022 17:16:00 +0100 Barry wrote:
>
>>> I wonder if there is a single case where nm-online is useful :-(
>
>> Yes there are use cases where this is needed.
>> Some times network is need to complete boot
Hi.
On Thu, 07 Jul 2022 17:16:00 +0100 Barry wrote:
>> I wonder if there is a single case where nm-online is useful :-(
> Yes there are use cases where this is needed.
> Some times network is need to complete boot in I tire before switching the
> the main disk.
Of course, but to be clearer: do
> On 6 Jul 2022, at 11:52, francis.montag...@inria.fr wrote:
>
>
> Hi.
>
> For information, I made this buzilla this morning:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2104398
>
> (I did similar for Fedora-34).
>
> I wonder if there is a single case where nm-online is useful :-(
Ye
Hi.
For information, I made this buzilla this morning:
https://bugzilla.redhat.com/show_bug.cgi?id=2104398
(I did similar for Fedora-34).
I wonder if there is a single case where nm-online is useful :-(
--
francis
___
users mailing list -- users@
Hi Experts,
how much space should you reserve for /var/tmp/dracut when upgrading Fedora?
Background:
My upgrade from Fedora 34 to Fedora 35 failed due to insufficent space on /var
in the way that reboot failed due to missing initramfs-*.
I could recover but at first I was shocked.
Stay
> On 2/1/21 3:27 PM, sixpack13 wrote:
>
...
>
> As it does appear that you are posting from HyperKitty given the header
> someone else showed and the lack of quote headers in the emails, did you
> happen to enter a last name somewhere and not a first name? That could
> possibly explain the ex
On Mon, 1 Feb 2021 12:59:56 -0500 sean darcy wrote:
> Running scriptlet: kernel-core-5.10.11-200.fc33.x86_64
> 174/174
> dracut-install: No SOURCE argument given
> Usage: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -a
>
On 2/1/21 3:27 PM, sixpack13 wrote:
On 2/1/21 3:02 PM, sixpack13 wrote:
Yes, but I don't see why that's a problem:
...
the problem is one is complaining, but I can't do anything against that spaces.
there are none in my profile
Did they give a reason for the complaint? There's nothing wrong
On 02/02/2021 08:39, Tim via users wrote:
If you're getting extra spaces where they're not expected, that could
be coming from your mail client, check how you've entered your name and
address. Or it could be coming from a profile setting on the mailing
list.
Headers indicate
From: " sixp
" sixpack13" wrote:
> confusing
> I've checked that in my profil: no spaces, nowhere
>
> thanks for quick response(s) !
I see them, too. I can't see it actually causing any technical
problem, though. If someone sorts their mail by from addresses, that
may cause some unusual sorting.
Email ad
> On 2/1/21 3:02 PM, sixpack13 wrote:
>
> Yes, but I don't see why that's a problem:
...
the problem is one is complaining, but I can't do anything against that spaces.
there are none in my profile
dito: thanks for quick response
___
users mailing li
> On Mon, Feb 1, 2021 at 4:02 PM sixpack13
> The From: line in your email looks like this:
>
> From: " sixpack13"
> so yes, there are two spaces in front of sixpack13.
confusing
I've checked that in my profil: no spaces, nowhere
thanks for quick response(s) !
___
On 2/1/21 3:02 PM, sixpack13 wrote:
On 2/1/21 2:04 PM, sixpack13 wrote:
That was a different error. This one looks pretty fatal. I also
suggest checking the size of the initramfs and if it even exists.
- OT -
@Samuel
a user of this list is sending me emails complaining that are spaces in fr
On Mon, Feb 1, 2021 at 4:02 PM sixpack13 wrote:
> - OT -
>
> @Samuel
> a user of this list is sending me emails complaining that are spaces in from
> of my email address.
> I checked my profile and can't find a space neither in my name nor my email
> address.
>
> Q.:
> do you see spaces in my em
> On 2/1/21 2:04 PM, sixpack13 wrote:
>
> That was a different error. This one looks pretty fatal. I also
> suggest checking the size of the initramfs and if it even exists.
- OT -
@Samuel
a user of this list is sending me emails complaining that are spaces in from of
my email address.
I che
On 2/1/21 2:32 PM, sean darcy wrote:
dracut-install: No SOURCE argument given
Usage: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -a
SOURCE...
or: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... SOURCE DEST
or: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -m
On 2/1/21 5:12 PM, Samuel Sieb wrote:
On 2/1/21 2:04 PM, sixpack13 wrote:
Running scriptlet: kernel-core-5.10.11-200.fc33.x86_64
174/174
dracut-install: No SOURCE argument given
Usage: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -a
SOURCE
On 2/1/21 2:04 PM, sixpack13 wrote:
Running scriptlet: kernel-core-5.10.11-200.fc33.x86_64
174/174
dracut-install: No SOURCE argument given
Usage: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -a
SOURCE...
or: dracut-install -D DESTROOTDIR
> Running scriptlet: kernel-core-5.10.11-200.fc33.x86_64
> 174/174
> dracut-install: No SOURCE argument given
> Usage: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -a
> SOURCE...
> or: dracut-install -D DESTROOTDIR [-r S
Running scriptlet: kernel-core-5.10.11-200.fc33.x86_64
174/174
dracut-install: No SOURCE argument given
Usage: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... -a
SOURCE...
or: dracut-install -D DESTROOTDIR [-r SYSROOTDIR] [OPTION]... SOURCE
Found the answer:
https://discussion.fedoraproject.org/t/dracut-install-error-installing-lz4-compress/21604/4
On Tue, Sep 8, 2020 at 8:01 PM Neal Becker wrote:
> I guess I had tried to add lz4_compress to kernel install, but must have
> done something wrong. Now with every kernel update
I guess I had tried to add lz4_compress to kernel install, but must have
done something wrong. Now with every kernel update I get:
Running scriptlet: kernel-core-5.8.6-201.fc32.x86_64
127/127
dracut-install: ERROR: installing 'lz4_compress'
dracut: FAILED: /usr/
Any ideas about this one? Sounds a bit scary, but system seems to be working:
[ 8040.319826] dnf[848]: dracut-install: ERROR: installing 'lz4_compress'
[ 8040.323817] dnf[848]: dracut: FAILED: /usr/lib/dracut/dracut-install -D
/var/tmp/dracut.vt8aLI/initramfs --kerneldir
/lib/mod
e' and found that:
>
>
> dracut: FAILED: /usr/lib/dracut/dracut-install -D
> /var/tmp/dracut.ReYjXp/initramfs -H --kerneldir /lib/modules/5.0.3-
> 200.fc29.x86_64/ -o -m =drivers/net/phy =drivers/ net/team
> =drivers/net/ethernet ecb arc4 bridge stp llc ipv6 bonding 8021q ipvl
kmod-
> > nvidia-
> > 340xx-340.107-5.fc29.x86_64. It was not there, so I looked more
> > closely at the output of the 'dnf upgrade' and found that:
> >
> >
> > dracut: FAILED: /usr/lib/dracut/dracut-install -D
> > /var/tmp/dracut.ReYjXp/initramf
y at the output of the 'dnf upgrade' and found that:
>
>
> dracut: FAILED: /usr/lib/dracut/dracut-install -D
> /var/tmp/dracut.ReYjXp/initramfs -H --kerneldir /lib/modules/5.0.3-
> 200.fc29.x86_64/ -o -m =drivers/net/phy =drivers/ net/team
> =drivers/net/ethernet e
After a dnf upgrade that included the new 5.x kernel I did my regular
check to make sure that the nvidia driver got built via akmod-nvidia-
340xx-340.107-5.fc29.x86_64. It was not there, so I looked more closely
at the output of the 'dnf upgrade' and found that:
dracut: FAILED: /usr/
... - I'm getting old - ...
/etc/fstab needs adjustments (UUID) too !!!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-cond
orks cause no
experience with PCIe-adaptor -
open question:
===
- sudo grub2-install ... ?
- sudo dracut -f /boot/initramfs-$(uname -r).img $(uname -r) with parameter of
the root partition on the nvme ?
=> man dracut
___
users mailing list --
" SSD.
Something is obviously missing there in this simplistic approach,
although kernel boots from this new small SSD it does not load the rest
of the whole system.
I am stuck with dracut.
That would be grub or/and dracut need tweaking?
Or any other way to boot a system off a NVMe via a SSD/HDD?
m
Hi! Does anybody know _exactly_ how dracut-initqueue search for "real
root" ? is there a method to help this service to find the root faster?
i looked over
/usr/lib/dracut/modules.d/98dracut-systemd/dracut-initqueue.sh
but it is not clear to me why it takes 2+ seconds on ssd (EFI) to
gt; or
>
> * hostonly=no
>in a dracut configuration file
>
> or
>
> * by installing the dracut-config-generic rpm
Wow, that's the biggest package I've ever installed! (Not!) But it does
the trick. I confirm that a package built this way works as intended.
--
Dave Cl
g of all of them fails in exactly the same way: dracut
>>> says it can't find the disk filesystems. The kernel boots as it
>>> should, and of course that comes from the disk, but then dracut comes
>>> along and says it can't find any of the filesystems. No
On 04/19/2016 06:07 PM, CLOSE Dave wrote:
I wrote:
I have five machines which were fresh-installed with F23 back in
February and all have been booted successfully a few times since.
Today, booting of all of them fails in exactly the same way: dracut
says it can't find the disk filesystems
I wrote:
> I have five machines which were fresh-installed with F23 back in
> February and all have been booted successfully a few times since.
> Today, booting of all of them fails in exactly the same way: dracut
> says it can't find the disk filesystems. The kernel boots as it
On 04/07/16 05:56 PM, Rick Stevens wrote:
> Glad to help. Did the rebuild of the ramdisk work? Are you running
> the new kernel? Just curious as this may happen on the next update,
> too.
I hope to have time for that tomorrow.
--
Dave Close
--
users mailing list
users@lists.fedoraproject.org
To
On 04/07/2016 05:21 PM, CLOSE Dave wrote:
I wrote:
I have five machines which were fresh-installed with F23 back in
February and all have been booted successfully a few times since.
Today, booting of all of them fails in exactly the same way: dracut
says it can't find the disk filesystems
I wrote:
> I have five machines which were fresh-installed with F23 back in
> February and all have been booted successfully a few times since.
> Today, booting of all of them fails in exactly the same way: dracut
> says it can't find the disk filesystems. The kernel boots as it
On 04/07/2016 04:50 PM, CLOSE Dave wrote:
I have five machines which were fresh-installed with F23 back in
February and all have been booted successfully a few times since. Today,
booting of all of them fails in exactly the same way: dracut says it
can't find the disk filesystems. The k
I have five machines which were fresh-installed with F23 back in
February and all have been booted successfully a few times since. Today,
booting of all of them fails in exactly the same way: dracut says it
can't find the disk filesystems. The kernel boots as it should, and of
course
I tried a lot of things but finally saw in the rdsosreport.txt that the kernel
was seeing the array but refusing to use it. It was several months ago so
that's
about all I remember.
Bill
On 10/4/2015 5:01 PM, Alex wrote:
Hi,
I ran into this or something similar. My system would boot fine
Hi,
> I ran into this or something similar. My system would boot fine on
> an older kernel but fail on a new oue. Can't remember which one worked
> and which didn't. The solution I found was remove the bitmap, re-boot on
> the newer kernel, and add the bitmap back.
>
> # remove
> mdadm --grow --
and / on RAID1. The rdsosreport.txt that dracut produces shows
no indication of md RAID support in /proc/mdstat and no RAID devices
listed with blkid or in /dev.
I've tried rebuilding the initramfs images manually on the running
system and it still doesn't include RAID support.
What cou
Oct 4, 2015 at 1:03 AM, Alex wrote:
> HI,
>
> I have a fedora22 system that's been working fine for some time, but
> any new kernels fail to boot properly. The system is configured with
> /boot and / on RAID1. The rdsosreport.txt that dracut produces shows
> no indication of
HI,
I have a fedora22 system that's been working fine for some time, but
any new kernels fail to boot properly. The system is configured with
/boot and / on RAID1. The rdsosreport.txt that dracut produces shows
no indication of md RAID support in /proc/mdstat and no RAID devices
listed with
is just regular MBR/GPT
> partitioned USB stick with ext234 format? No LVM? The blkid command
> should work in the dracut shell and tell you what is where.
Yes, just an ext3 format. I've since learned it appears to be
necessary to have the USB stick inserted into the working system being
u
ble, I do it regularly. This is just regular MBR/GPT
partitioned USB stick with ext234 format? No LVM? The blkid command
should work in the dracut shell and tell you what is where.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription op
Hi,
>>>> I have a fc22 system that's been working fine and now for some reason
>>>> kernel updates result in an unbootable system. It appears to be
>>>> related to dracut failing to build a proper initramfs image.
>>>>
>>>> I h
> On Sep 10, 2015, at 3:22 PM, Alex wrote:
>
> Hi,
>
>>> I have a fc22 system that's been working fine and now for some reason
>>> kernel updates result in an unbootable system. It appears to be
>>> related to dracut failing to build a prope
Hi,
>> I have a fc22 system that's been working fine and now for some reason
>> kernel updates result in an unbootable system. It appears to be
>> related to dracut failing to build a proper initramfs image.
>>
>> I have a default initramfs from 4.0.4-300 that
On Wed, Sep 9, 2015 at 8:51 AM, Alex wrote:
> Hi,
>
> I have a fc22 system that's been working fine and now for some reason
> kernel updates result in an unbootable system. It appears to be
> related to dracut failing to build a proper initramfs image.
>
> I have a de
On 09.09.2015, Shaheen Bakhtiar wrote:
> What is the exact error message(s) you are getting?? Where in the boot
> process is it failing?
It's not me having problems..
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject
015, Alex wrote:
> >
> >> I have a fc22 system that's been working fine and now for some reason
> >> kernel updates result in an unbootable system. It appears to be
> >> related to dracut failing to build a proper initramfs image.
> >
> > I've
AM, Heinz Diehl wrote:
>
> On 09.09.2015, Alex wrote:
>
>> I have a fc22 system that's been working fine and now for some reason
>> kernel updates result in an unbootable system. It appears to be
>> related to dracut failing to build a proper initramfs image.
&g
On 09.09.2015, Alex wrote:
> I have a fc22 system that's been working fine and now for some reason
> kernel updates result in an unbootable system. It appears to be
> related to dracut failing to build a proper initramfs image.
I've never used any distribution kernel, and on
Alex wrote:
> Hi,
>
> I have a fc22 system that's been working fine and now for some reason
> kernel updates result in an unbootable system. It appears to be
> related to dracut failing to build a proper initramfs image.
>
> I have a default initramfs from 4.0.4-300
Hi,
I have a fc22 system that's been working fine and now for some reason
kernel updates result in an unbootable system. It appears to be
related to dracut failing to build a proper initramfs image.
I have a default initramfs from 4.0.4-300 that works fine, but using
dracut to build
Hello,
In fedora20:
I get dracut failed to create symbolic link /dev/resume
and then cannot fing VolSysUsr0
and I cannot boot
I do not know if these 2 issues are correlated.
Any this what I did:
I cloned /boot and / and a new disk and I removed the old disk
/boot is on an ext4 partition
On Fri, 2014-10-24 at 18:24 -0600, Chris Murphy wrote:
> Companies do not spend hundreds of millions of dollars (conservatively
> estimated at this point) completely retooling firmware to something
> that has about as many lines of code as the linux kernel, and
> *requiring* manufacturers to enable
Chris Murphy writes:
>
> That is correct, but it is a prerequisite for being able to even trust
> userspace if kernel space is already compromised then it's a problem.
I dont trust the Companies that their proprietary Bioses and UEFIs are
not itself a rootkit. So the only solution to fix this pr
On Oct 25, 2014, at 7:35 AM, Stefan Huchler wrote:
> Chris Murphy writes:
>
> I try to not answer to much, because I dont want to argue to much, I
> just wanted a solution for my problem and this had nothing to do with
> secure boot, but I give my 2 cents to it.
Indeed, it's completely on me
Maybe it was back then no GPT problem, this tool doenst support gpt, but
uefi is the next thing, you need to install the right 64bit uefi grub
version or something.
The point is it adds much more complexity and I personaly gain NOTHING
of it, so why the hell should I use it?
Yes because at some
Chris Murphy writes:
I try to not answer to much, because I dont want to argue to much, I
just wanted a solution for my problem and this had nothing to do with
secure boot, but I give my 2 cents to it.
Did you really happen to see such a exploit in the wild that somebody
used kvm to start window
On Oct 22, 2014, at 3:14 PM, Stefan Huchler wrote:
> Chris Murphy writes:
>
>
> So first of all, I am thankful that u helped me to understand the
> problem I was shure I somehow on a interupted dnf process or something I
> damaged something in fedora, because I did not remember or notice that
Mickey writes:
> I don't have uefi on my box and I'am getting the same error message
> that pops up in the Notification Jobs in my system tray.
Did you answer to the wrong thread or to what message do you refer?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subsc
On 10/22/2014 05:14 PM, Stefan Huchler wrote:
Chris Murphy writes:
So first of all, I am thankful that u helped me to understand the
problem I was shure I somehow on a interupted dnf process or something I
damaged something in fedora, because I did not remember or notice that
it did not updat
Chris Murphy writes:
So first of all, I am thankful that u helped me to understand the
problem I was shure I somehow on a interupted dnf process or something I
damaged something in fedora, because I did not remember or notice that
it did not update grub from the beginning.
Maybe I make a switch
On Oct 22, 2014, at 10:48 AM, Stefan Huchler wrote:
> Chris Murphy writes:
>
>>
>> Again if you're using modern utilities, you don't have to know any of
>> these things, alignment is a solved problem. My point is that Btrfs
>> doesn't do anything differently than other filesystems in this reg
Chris Murphy writes:
>
> Again if you're using modern utilities, you don't have to know any of
> these things, alignment is a solved problem. My point is that Btrfs
> doesn't do anything differently than other filesystems in this regard,
> which is exactly nothing. It all depends on an earlier to
On 21.10.2014 04:30, Chris Murphy wrote:
>
> On Oct 20, 2014, at 9:42 PM, poma wrote:
>
>> On 21.10.2014 03:26, Chris Murphy wrote:
>>>
>>> On Oct 20, 2014, at 8:53 PM, poma wrote:
>>>
On 20.10.2014 17:14, Chris Murphy wrote:
>
> The bug is in grubby, which is what's called fr
On 21.10.2014 16:17, Chris Murphy wrote:
>
> On Oct 21, 2014, at 8:07 AM, Stefan Huchler wrote:
>
>> Chris Murphy writes:
>>
>>> Where you get bad results is with, e.g. a pre-existing legacy OS like
>>> Windows XP, where it's not aligned and any subsequent partition is
>>> also not aligned. In
On Oct 21, 2014, at 8:07 AM, Stefan Huchler wrote:
> Chris Murphy writes:
>
>> Where you get bad results is with, e.g. a pre-existing legacy OS like
>> Windows XP, where it's not aligned and any subsequent partition is
>> also not aligned. In that case, even a Btrfs volume wouldn't be
>> align
Chris Murphy writes:
> Where you get bad results is with, e.g. a pre-existing legacy OS like
> Windows XP, where it's not aligned and any subsequent partition is
> also not aligned. In that case, even a Btrfs volume wouldn't be
> aligned.
I dont want to care at all, I dont want to know if to use
On Oct 20, 2014, at 9:42 PM, poma wrote:
> On 21.10.2014 03:26, Chris Murphy wrote:
>>
>> On Oct 20, 2014, at 8:53 PM, poma wrote:
>>
>>> On 20.10.2014 17:14, Chris Murphy wrote:
>>>
The bug is in grubby, which is what's called from within kernel packages
to update bootloade
On 21.10.2014 03:10, Matthew Miller wrote:
> On Tue, Oct 21, 2014 at 02:53:42AM +0200, poma wrote:
>>> The bug is in grubby, which is what's called from within kernel
>>> packages to update bootloader configuration scripts: GRUB legacy,
>>> GRUB2, syslinux, yaboot, and probably a bunch of other boo
On 21.10.2014 03:26, Chris Murphy wrote:
>
> On Oct 20, 2014, at 8:53 PM, poma wrote:
>
>> On 20.10.2014 17:14, Chris Murphy wrote:
>>
>>>
>>> The bug is in grubby, which is what's called from within kernel packages to
>>> update bootloader configuration scripts: GRUB legacy, GRUB2, syslinux,
On Oct 20, 2014, at 8:53 PM, poma wrote:
> On 20.10.2014 17:14, Chris Murphy wrote:
>
>>
>> The bug is in grubby, which is what's called from within kernel packages to
>> update bootloader configuration scripts: GRUB legacy, GRUB2, syslinux,
>> yaboot, and probably a bunch of other bootloade
On Oct 20, 2014, at 5:56 PM, Stefan Huchler wrote:
>
> Chris Murphy writes:
>> There should be packages somewhere on http://czarc.org but I'm not
>> sure where. If you can't find them lemme know and I'll go dig around.
>
> thank you is that the file?
> http://czarc.org/fedora/repo/20/x86_64/g
On Tue, Oct 21, 2014 at 02:53:42AM +0200, poma wrote:
> > The bug is in grubby, which is what's called from within kernel
> > packages to update bootloader configuration scripts: GRUB legacy,
> > GRUB2, syslinux, yaboot, and probably a bunch of other bootloaders
> > are all supported by grubby. It
1 - 100 of 216 matches
Mail list logo
