** Tags added: patch
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
To get your fix included in Ubuntu, it would help if you tried
transforming it into a debdiff
(http://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff) and submit it
for review (http://wiki.ubuntu.com/SponsorshipProcess). If you prefer
somebody else to do that, that's fine - please just indicate if y
After again reading Bugreport #105386, i noticed, that this is possibly
the same bug, so i added a comment with a pointer to this report in
#105386.
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Today i have build a patch for evms to solve this problem more elegant
as the quick&dirty solution with "sleep 5". This solutions replaces the
call of /sbin/evms_activate in the script /usr/share/initramfs-
tools/scripts/local-top/evms with a loop which tries to start
evms_activate until $ROOT show
A working patch to fix this issue is contained in the 3rd message about this
problem.
Maybe someone should only commit this change (i am not an Ubuntu developer, and
i don't want to be one because of "lack of time", so i can't do it). The patch
works
without any problems for me. Is there anyone o
I compared the evms scripts from initramfs-tools from dapper und
initramfs-tools from feisty.
They are exactly identical, but with the initramfs-tools from feisty, i have to
wait before
calling evms_activate, because otherwise the root-device on an EVMS-Volume will
not be
found ... What the hell
I can confirm that this bug happens during the upgrade to Feisty for
i386 and amd64 computers, and that the given patch fixes both.
The upgrade from Edgy to Feisty will break any computer that has an EVMS
root. The severity of the bug should be increased because it makes
affected computers unboot
I've never used evms for a root device, but am currently running into
problems on a test I'm using with VMWare, so maybe this is the issue I'm
having.
A thought occurs to me, though. The init system was changed from the
debian system to Upstart beginning with Edgy Eft. Upstart runs startup
scripts
** Changed in: evms (Ubuntu)
Importance: Undecided => High
Status: New => Triaged
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
** Tags added: patch
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
** Changed in: evms (Ubuntu)
Importance: Undecided => High
Status: New => Triaged
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I've never used evms for a root device, but am currently running into
problems on a test I'm using with VMWare, so maybe this is the issue I'm
having.
A thought occurs to me, though. The init system was changed from the
debian system to Upstart beginning with Edgy Eft. Upstart runs startup
scripts
To get your fix included in Ubuntu, it would help if you tried
transforming it into a debdiff
(http://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff) and submit it
for review (http://wiki.ubuntu.com/SponsorshipProcess). If you prefer
somebody else to do that, that's fine - please just indicate if y
I compared the evms scripts from initramfs-tools from dapper und
initramfs-tools from feisty.
They are exactly identical, but with the initramfs-tools from feisty, i have to
wait before
calling evms_activate, because otherwise the root-device on an EVMS-Volume will
not be
found ... What the hell
After again reading Bugreport #105386, i noticed, that this is possibly
the same bug, so i added a comment with a pointer to this report in
#105386.
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Today i have build a patch for evms to solve this problem more elegant
as the quick&dirty solution with "sleep 5". This solutions replaces the
call of /sbin/evms_activate in the script /usr/share/initramfs-
tools/scripts/local-top/evms with a loop which tries to start
evms_activate until $ROOT show
A working patch to fix this issue is contained in the 3rd message about this
problem.
Maybe someone should only commit this change (i am not an Ubuntu developer, and
i don't want to be one because of "lack of time", so i can't do it). The patch
works
without any problems for me. Is there anyone o
I can confirm that this bug happens during the upgrade to Feisty for
i386 and amd64 computers, and that the given patch fixes both.
The upgrade from Edgy to Feisty will break any computer that has an EVMS
root. The severity of the bug should be increased because it makes
affected computers unboot
To get your fix included in Ubuntu, it would help if you tried
transforming it into a debdiff
(http://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff) and submit it
for review (http://wiki.ubuntu.com/SponsorshipProcess). If you prefer
somebody else to do that, that's fine - please just indicate if y
I've never used evms for a root device, but am currently running into
problems on a test I'm using with VMWare, so maybe this is the issue I'm
having.
A thought occurs to me, though. The init system was changed from the
debian system to Upstart beginning with Edgy Eft. Upstart runs startup
scripts
** Changed in: evms (Ubuntu)
Importance: Undecided => High
Status: New => Triaged
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
** Tags added: patch
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
After again reading Bugreport #105386, i noticed, that this is possibly
the same bug, so i added a comment with a pointer to this report in
#105386.
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Today i have build a patch for evms to solve this problem more elegant
as the quick&dirty solution with "sleep 5". This solutions replaces the
call of /sbin/evms_activate in the script /usr/share/initramfs-
tools/scripts/local-top/evms with a loop which tries to start
evms_activate until $ROOT show
A working patch to fix this issue is contained in the 3rd message about this
problem.
Maybe someone should only commit this change (i am not an Ubuntu developer, and
i don't want to be one because of "lack of time", so i can't do it). The patch
works
without any problems for me. Is there anyone o
I compared the evms scripts from initramfs-tools from dapper und
initramfs-tools from feisty.
They are exactly identical, but with the initramfs-tools from feisty, i have to
wait before
calling evms_activate, because otherwise the root-device on an EVMS-Volume will
not be
found ... What the hell
I can confirm that this bug happens during the upgrade to Feisty for
i386 and amd64 computers, and that the given patch fixes both.
The upgrade from Edgy to Feisty will break any computer that has an EVMS
root. The severity of the bug should be increased because it makes
affected computers unboot
** Changed in: evms (Ubuntu)
Importance: Undecided => High
Status: New => Triaged
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
** Changed in: evms (Ubuntu)
Importance: Undecided => High
Status: New => Triaged
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
To get your fix included in Ubuntu, it would help if you tried
transforming it into a debdiff
(http://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff) and submit it
for review (http://wiki.ubuntu.com/SponsorshipProcess). If you prefer
somebody else to do that, that's fine - please just indicate if y
** Tags added: patch
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
After again reading Bugreport #105386, i noticed, that this is possibly
the same bug, so i added a comment with a pointer to this report in
#105386.
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Today i have build a patch for evms to solve this problem more elegant
as the quick&dirty solution with "sleep 5". This solutions replaces the
call of /sbin/evms_activate in the script /usr/share/initramfs-
tools/scripts/local-top/evms with a loop which tries to start
evms_activate until $ROOT show
A working patch to fix this issue is contained in the 3rd message about this
problem.
Maybe someone should only commit this change (i am not an Ubuntu developer, and
i don't want to be one because of "lack of time", so i can't do it). The patch
works
without any problems for me. Is there anyone o
I compared the evms scripts from initramfs-tools from dapper und
initramfs-tools from feisty.
They are exactly identical, but with the initramfs-tools from feisty, i have to
wait before
calling evms_activate, because otherwise the root-device on an EVMS-Volume will
not be
found ... What the hell
I can confirm that this bug happens during the upgrade to Feisty for
i386 and amd64 computers, and that the given patch fixes both.
The upgrade from Edgy to Feisty will break any computer that has an EVMS
root. The severity of the bug should be increased because it makes
affected computers unboot
I've never used evms for a root device, but am currently running into
problems on a test I'm using with VMWare, so maybe this is the issue I'm
having.
A thought occurs to me, though. The init system was changed from the
debian system to Upstart beginning with Edgy Eft. Upstart runs startup
scripts
** Tags added: patch
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
After again reading Bugreport #105386, i noticed, that this is possibly
the same bug, so i added a comment with a pointer to this report in
#105386.
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Today i have build a patch for evms to solve this problem more elegant
as the quick&dirty solution with "sleep 5". This solutions replaces the
call of /sbin/evms_activate in the script /usr/share/initramfs-
tools/scripts/local-top/evms with a loop which tries to start
evms_activate until $ROOT show
A working patch to fix this issue is contained in the 3rd message about this
problem.
Maybe someone should only commit this change (i am not an Ubuntu developer, and
i don't want to be one because of "lack of time", so i can't do it). The patch
works
without any problems for me. Is there anyone o
I compared the evms scripts from initramfs-tools from dapper und
initramfs-tools from feisty.
They are exactly identical, but with the initramfs-tools from feisty, i have to
wait before
calling evms_activate, because otherwise the root-device on an EVMS-Volume will
not be
found ... What the hell
I can confirm that this bug happens during the upgrade to Feisty for
i386 and amd64 computers, and that the given patch fixes both.
The upgrade from Edgy to Feisty will break any computer that has an EVMS
root. The severity of the bug should be increased because it makes
affected computers unboot
To get your fix included in Ubuntu, it would help if you tried
transforming it into a debdiff
(http://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff) and submit it
for review (http://wiki.ubuntu.com/SponsorshipProcess). If you prefer
somebody else to do that, that's fine - please just indicate if y
** Changed in: evms (Ubuntu)
Importance: Undecided => High
Status: New => Triaged
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
** Tags added: patch
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
I've never used evms for a root device, but am currently running into
problems on a test I'm using with VMWare, so maybe this is the issue I'm
having.
A thought occurs to me, though. The init system was changed from the
debian system to Upstart beginning with Edgy Eft. Upstart runs startup
scripts
To get your fix included in Ubuntu, it would help if you tried
transforming it into a debdiff
(http://wiki.ubuntu.com/PackagingGuide/Recipes/Debdiff) and submit it
for review (http://wiki.ubuntu.com/SponsorshipProcess). If you prefer
somebody else to do that, that's fine - please just indicate if y
After again reading Bugreport #105386, i noticed, that this is possibly
the same bug, so i added a comment with a pointer to this report in
#105386.
--
EVMS Boot-Problem
https://bugs.launchpad.net/bugs/106097
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Today i have build a patch for evms to solve this problem more elegant
as the quick&dirty solution with "sleep 5". This solutions replaces the
call of /sbin/evms_activate in the script /usr/share/initramfs-
tools/scripts/local-top/evms with a loop which tries to start
evms_activate until $ROOT show
A working patch to fix this issue is contained in the 3rd message about this
problem.
Maybe someone should only commit this change (i am not an Ubuntu developer, and
i don't want to be one because of "lack of time", so i can't do it). The patch
works
without any problems for me. Is there anyone o
I compared the evms scripts from initramfs-tools from dapper und
initramfs-tools from feisty.
They are exactly identical, but with the initramfs-tools from feisty, i have to
wait before
calling evms_activate, because otherwise the root-device on an EVMS-Volume will
not be
found ... What the hell
I can confirm that this bug happens during the upgrade to Feisty for
i386 and amd64 computers, and that the given patch fixes both.
The upgrade from Edgy to Feisty will break any computer that has an EVMS
root. The severity of the bug should be increased because it makes
affected computers unboot
I've never used evms for a root device, but am currently running into
problems on a test I'm using with VMWare, so maybe this is the issue I'm
having.
A thought occurs to me, though. The init system was changed from the
debian system to Upstart beginning with Edgy Eft. Upstart runs startup
scripts
54 matches
Mail list logo
