On Tue, 2009-02-03 at 23:43 +0100, Harald Braumann wrote:
> On Tue, 3 Feb 2009 12:35:48 +0900
> Paul Wise wrote:
>
> > How about letting the person doing the installation write the labels
> > if they want to use LABEL and use UUID by default.
> >
> Or as a third option, put everything in LVM, in
On Tue, 3 Feb 2009 12:35:48 +0900
Paul Wise wrote:
> How about letting the person doing the installation write the labels
> if they want to use LABEL and use UUID by default.
>
Or as a third option, put everything in LVM, including boot and root,
and the problem goes away. GRUB2 would have to be
How about letting the person doing the installation write the labels
if they want to use LABEL and use UUID by default.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@l
William Pitcock dijo [Mon, Feb 02, 2009 at 02:42:11PM -0600]:
> > Still, it is a saner overall system. Of course, if during install d-i
> > finds there is already a partition labeled 'root', it could either ask
> > the user for an alternative name or set it to
> > d-i-${timestamp}-root. Or label al
On Mon, 2009-02-02 at 14:09 -0600, Gunnar Wolf wrote:
> Mike Hommey dijo [Sun, Feb 01, 2009 at 10:46:11AM +0100]:
> > > > A good option would be to use LABEL or UID instead. However I am not
> > > > sure if that has some drawbacks as well:
> > > >
> > > > - for uuid the system is less forgiving i
Mike Hommey dijo [Sun, Feb 01, 2009 at 10:46:11AM +0100]:
> > > A good option would be to use LABEL or UID instead. However I am not sure
> > > if that has some drawbacks as well:
> > >
> > > - for uuid the system is less forgiving if you swap disks
> > > - for label the system is less forgiving
[Florian Weimer]
> * Otavio Salvador:
>
>> See the errata[2] for details and a full list of known issues.
>
> What needs to be done so that these two issues can be fixed?
One solution to this is to stop using device names, and instead of
file system ID, in /etc/fstab and the boot loader configura
Quoting Florian Weimer (f...@deneb.enyo.de):
> * Otavio Salvador:
>
> > See the errata[2] for details and a full list of known issues.
>
> What needs to be done so that these two issues can be fixed?
This has been discussed numerous times in -boot but among the low number of
ppl working on D-I d
* Andrew Deason:
> I believe this still doesn't solve the problem in the case of lilo.conf
> or grub's device.map, when specifying e.g. where to write the MBR. Is
> there any way around that?
The boot loaders would obviously have to scan for UUIDs, which carries
its own risks (like lockup during
On Sun, 2009-02-01 at 10:46 +0100, Mike Hommey wrote:
> On Sun, Feb 01, 2009 at 03:22:07AM -0600, William Pitcock wrote:
> > On Sun, 2009-02-01 at 00:19 +0100, Bernd Eckenfels wrote:
> > > In article <87bptnccj6@mid.deneb.enyo.de> you wrote:
> > > > What needs to be done so that these two issue
On Sun, Feb 01, 2009 at 03:22:07AM -0600, William Pitcock wrote:
> On Sun, 2009-02-01 at 00:19 +0100, Bernd Eckenfels wrote:
> > In article <87bptnccj6@mid.deneb.enyo.de> you wrote:
> > > What needs to be done so that these two issues can be fixed?
> > >
> > > | Disk devices may change on rebo
On Sun, 2009-02-01 at 00:19 +0100, Bernd Eckenfels wrote:
> In article <87bptnccj6@mid.deneb.enyo.de> you wrote:
> > What needs to be done so that these two issues can be fixed?
> >
> > | Disk devices may change on reboot
>
> A good option would be to use LABEL or UID instead. However I am no
On Sun, 2009-02-01 at 03:46 +, The Fungi wrote:
> On Sat, Jan 31, 2009 at 07:56:01PM -0600, Andrew Deason wrote:
> > Label names could be generated to minimize collisions. Something like
> > ${hostname}-/ instead of /, or maybe something even more specific.
>
> The namespace here is, unfortun
On Sat, Jan 31, 2009 at 07:56:01PM -0600, Andrew Deason wrote:
[...]
> Label names could be generated to minimize collisions. Something like
> ${hostname}-/ instead of /, or maybe something even more specific.
[...]
The namespace here is, unfortunately, pretty limited. The manpages
for mkreiserfs
On Sun, 01 Feb 2009 00:19:33 +0100
Bernd Eckenfels wrote:
> In article <87bptnccj6@mid.deneb.enyo.de> you wrote:
> > What needs to be done so that these two issues can be fixed?
> >
> > | Disk devices may change on reboot
>
> A good option would be to use LABEL or UID instead.
I believe th
In article <87bptnccj6@mid.deneb.enyo.de> you wrote:
> What needs to be done so that these two issues can be fixed?
>
> | Disk devices may change on reboot
A good option would be to use LABEL or UID instead. However I am not sure if
that has some drawbacks as well:
- for uuid the system is
* Otavio Salvador:
> See the errata[2] for details and a full list of known issues.
What needs to be done so that these two issues can be fixed?
| Disk devices may change on reboot
|
| On systems with multiple disk controllers, the kernel/udev may
| assign a different device node on reb
17 matches
Mail list logo
