FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 03-31-2010, 10:45 AM
Justin B Rye
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.pla in/templates}

Christian PERRIER wrote:
> (I didn't review the package description)

The descriptions in the linux-2.6 family don't obey the d-l-e "house
style" (they talk about flavoUrs, doublespace their sentences, and
so on) but I don't see anything that matters.

> Template: linux-base/disk-id-convert-auto
[...]
> The new Linux kernel version provides different drivers for some
> + PATA (IDE) controllers. The names of some hard disk, CD-ROM and
> tape devices may change.

There's one opportunity for me to add a serial comma ----------^

In my case the name of my IOmega Zip drive changed too. Yes, I
only had it installed on that machine to see if it would cause
trouble, and it still worked as /dev/sdc1. Mind you, I imagine it
would be a bit of a pain assigning labels to a pile of 100MB
removable zip-disks if dosfslabel's still buggy (#506786).

You missed an id here:
> Template: linux-base/disk-id-convert-plan-no-relabel
[...]
> The device ids will be changed as follows:
ID

> Template: linux-base/disk-id-manual-boot-loader
[...]
> + You should identify these devices by UUID or label, with the
> + noticeable exception of the root device for MIPS systems.
> +

Make that "notable exception" (and lose the trailing blank line).
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- ../linux-2.6-2.6.32.pristine/debian/linux-base.templates 2010-03-31 10:33:56.000000000 +0100
+++ debian/linux-base.templates 2010-03-31 11:38:20.000000000 +0100
@@ -1,20 +1,23 @@
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
-Description: Update disk device ids in system configuration?
+_Description: Update disk device IDs in system configuration?
The new Linux kernel version provides different drivers for some
- PATA (IDE) controllers. The names of some hard disk, CD-ROM and
+ PATA (IDE) controllers. The names of some hard disk, CD-ROM, and
tape devices may change.
.
- You are recommended to identify disk devices in configuration files
+ It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
- which will work with both old and new kernel versions. Your system
- configuration can be updated automatically in most cases.
+ which will work with both old and new kernel versions.
+ .
+ The system configuration can be updated automatically in most cases.
+ Please choose whether you want this action to be performed.

Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
-Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5,7
+_Description: Apply configuration changes to disk device IDs?
These devices will be assigned UUIDs or labels:
.
${relabel}
@@ -23,26 +26,40 @@
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}

Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
-Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5
+_Description: Apply these configuration changes to disk device IDs?
These configuration files will be updated:
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}

Template: linux-base/disk-id-manual
-Type: note
-Description: Please check these configuration files before rebooting
- These configuration files still use some device names that may
+Type: error
+#flag:translate!:3
+_Description: Configuration files still contain deprecated device names
+ The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}
+
+Template: linux-base/disk-id-manual-boot-loader
+Type: error
+_Description: Boot loader configuration check needed
+ The boot loader configuration for this system was not recognised. These
+ settings in the configuration may need to be updated:
+ .
+ * The root device ID passed as a kernel parameter;
+ * The boot device ID used to install and update the boot loader.
+ .
+ You should identify these devices by UUID or label, with the
+ notable exception of the root device for MIPS systems.
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
_Description: Update disk device IDs in system configuration?
The new Linux kernel version provides different drivers for some
PATA (IDE) controllers. The names of some hard disk, CD-ROM, and
tape devices may change.
.
It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
which will work with both old and new kernel versions.
.
The system configuration can be updated automatically in most cases.
Please choose whether you want this action to be performed.

Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
#flag:translate!:3,5,7
_Description: Apply configuration changes to disk device IDs?
These devices will be assigned UUIDs or labels:
.
${relabel}
.
These configuration files will be updated:
.
${files}
.
The device IDs will be changed as follows:
.
${id_map}

Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
#flag:translate!:3,5
_Description: Apply these configuration changes to disk device IDs?
These configuration files will be updated:
.
${files}
.
The device IDs will be changed as follows:
.
${id_map}

Template: linux-base/disk-id-manual
Type: error
#flag:translate!:3
_Description: Configuration files still contain deprecated device names
The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}

Template: linux-base/disk-id-manual-boot-loader
Type: error
_Description: Boot loader configuration check needed
The boot loader configuration for this system was not recognised. These
settings in the configuration may need to be updated:
.
* The root device ID passed as a kernel parameter;
* The boot device ID used to install and update the boot loader.
.
You should identify these devices by UUID or label, with the
notable exception of the root device for MIPS systems.
 
Old 03-31-2010, 04:26 PM
Justin B Rye
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.pla in/templates}

Ben Hutchings wrote:
>> I feel like "ID" is more appropriate than lowercas "id" as acronyms
>> are generally using uppercase. However, the current practice and
>> existing documentation may lead to keep "id".
>
> 'id' is short for 'identifier' and there is no reason to capitalise an
> abbreviation of a single word. I believe 'ID' in capitals originally
> stood for identity document, and while it is commonly used simply for
> 'identifier' it annoys my pedantic nature.

Here the dictionaries agree with Christian - some of them
(especially US ones) allow for "I.D.", but I can't find any that
recognise the existence of your abbreviation "id". There's an
English word "id" (pronounced /ɪd/, as in "creatures from the"), but
that's not the one we mean; the standard spelling for the word
/ɑɪdi/ is ID.

The word you're thinking of that stands for "Identity Document" is a
phantom. It would give the expression a nice tidy etymology, but
what really seems to have happened is that people just trimmed
"identification" down to its first syllable and read that out as
letters! The result is a quasi-acronym - just like KFC, which
officially doesn't stand for anything either. It irritates me too,
but if we let ourselves get annoyed by English spellings we'd never
get any work done.

>> - We recommend that you identify these devices by UUID or label, except that
>> - on MIPS systems this is not supported for the root device.
>> + You should identify these devices by UUID or label, with the
>> + noticeable exception of the root device for MIPS systems.
[...]
>>
>> Drop the use of first person. Rewrite the last sentence that looks
>> awkward to me (Germish? :-))
>
> No, I wrote that. While it was slightly awkward, it was correct and
> your change after the comma would make it ambiguous. MIPS users *must
> not* use UUID or label for the root device id.

"We" isn't too bad (it obviously means "some set of developers")
but how about:

The recommended solution is to identify these devices by UUID or label,
except that on MIPS systems this is not supported for the root device.
or maybe
except on MIPS systems, which do not support this for the root device.

--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100331162646.GA25516@xibalba.demon.co.uk">http://lists.debian.org/20100331162646.GA25516@xibalba.demon.co.uk
 
Old 04-01-2010, 01:00 AM
Justin B Rye
 
Default templates://linux-2.6/{linux-base.templates,templates/temp.image.pla in/templates}

Ben Hutchings wrote:
> On Wed, 2010-03-31 at 11:45 +0100, Justin B Rye wrote:
>> In my case the name of my IOmega Zip drive changed too. Yes, I
>> only had it installed on that machine to see if it would cause
>> trouble, and it still worked as /dev/sdc1. Mind you, I imagine it
>> would be a bit of a pain assigning labels to a pile of 100MB
>> removable zip-disks if dosfslabel's still buggy (#506786).
> [...]
>
> Also reported and fixed as #559985. You're welcome.

If it's fixed in 3.0.7-1, shouldn't dosfslabel agree with mlabel,
blkid, mount, etc on what label a vfat file system has? Because
that's not what I'm seeing:

jbr@xan:~$ /sbin/blkid /dev/sdb4
/dev/sdb4: SEC_TYPE="msdos" LABEL="ZM3" UUID="15F9-2C71" TYPE="vfat"
jbr@xan:~$ ls /dev/disk/by-label/
FREEBSD LENNY SWAP SQUEEZE ZM3
jbr@xan:~$ /sbin/dosfslabel --version
dosfslabel 3.0.9, 31 Jan 2010, FAT32, LFN
jbr@xan:~$ /sbin/dosfslabel /dev/sdb4
Z100A
jbr@xan:~$ sudo mount LABEL=Z100A /media/zip
mount: special device LABEL=Z100A does not exist
jbr@xan:~$ mlabel -s z:
Volume label is ZM3
jbr@xan:~$ sudo mount LABEL=ZM3 /media/zip
jbr@xan:~$ mount -l | grep zip
/dev/sdb4 on /media/zip type vfat (rw) [ZM3]

I can use mlabel or mkdosfs to set a label that can then immediately
be used by mount, but dosfslabel still seems to be modifying some
ID-string not connected to the file system label or UUID.

(I should probably be testing this on something less arcane.)
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100401010019.GA6019@xibalba.demon.co.uk">http://lists.debian.org/20100401010019.GA6019@xibalba.demon.co.uk
 

Thread Tools




All times are GMT. The time now is 03:22 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org