[Bug 305837] [NEW] No dots in script filenames?

[Radu C]

Public bug reported:

Binary package hint: initramfs-tools

Hi,

Files placed in the scripts directory can no longer have a dot in their
names (i.e. no script.sh files in there). This worked in Hardy. Is there
a reason for this?

A friend pasted me this patch, but I think it may need more than just
the dot in the expression (spacing may be badly messed up):

--- /usr/sbin/mkinitramfs.orig  2008-07-16 12:09:55.000000000 +0200
+++ /usr/sbin/mkinitramfs       2008-11-29 23:09:09.000000000 +0100
 -232,7 +232,7 @@
                "${DESTDIR}/scripts/$(dirname "${b}")/"
 done
 for b in $(cd "${CONFDIR}/scripts" && find . \
-       -regextype posix-extended -regex '.*/[[:alnum:]_]+$' -type f); do
+       -regextype posix-extended -regex '.*/[[:alnum:]_.]+$' -type f); do
        [ -d "${DESTDIR}/scripts/$(dirname "${b}")" ] \
                || mkdir -p "${DESTDIR}/scripts/$(dirname "${b}")"
        cp -p "${CONFDIR}/scripts/${b}" "${DESTDIR}/scripts/$(dirname "${b}")/"
--- /usr/share/initramfs-tools/scripts/functions.orig   2008-10-01 15:15:48.000000000 +0200
+++ /usr/share/initramfs-tools/scripts/functions        2008-11-29 23:50:52.000000000 +0100
 -110,7 +110,7 @@

                # only allow variable name chars
                case ${si_x#${initdir}/} in
-               *[![:alnum:]_]*)
+               *[![:alnum:]_.]*)
                        [ "${verbose}" = "y" ] \
                        && echo "$si_x ignored: not alphanumeric or '_' file"
                        continue

Hardy didn't seem to use regular expressions at all.

I think a bug report like LP:78348 that prompted such a change, but I
can't see anything specific to this change in the changelog.

** Affects: initramfs-tools (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  Binary package hint: initramfs-tools
  
  Hi,
  
  Files placed in the scripts directory can no longer have a dot in their
  names (i.e. no script.sh files in there). This worked in Hardy. Is there
  a reason for this?
  
  A friend pasted me this patch, but I think it may need more than just
  the dot in the expression (spacing may be badly messed up):
  
  --- /usr/sbin/mkinitramfs.orig  2008-07-16 12:09:55.000000000 +0200
  +++ /usr/sbin/mkinitramfs       2008-11-29 23:09:09.000000000 +0100
   -232,7 +232,7 @@
                  "${DESTDIR}/scripts/$(dirname "${b}")/"
   done
   for b in $(cd "${CONFDIR}/scripts" && find . \
  -       -regextype posix-extended -regex '.*/[[:alnum:]_]+$' -type f); do
  +       -regextype posix-extended -regex '.*/[[:alnum:]_.]+$' -type f); do
          [ -d "${DESTDIR}/scripts/$(dirname "${b}")" ] \
                  || mkdir -p "${DESTDIR}/scripts/$(dirname "${b}")"
          cp -p "${CONFDIR}/scripts/${b}" "${DESTDIR}/scripts/$(dirname "${b}")/"
  --- /usr/share/initramfs-tools/scripts/functions.orig   2008-10-01 15:15:48.000000000 +0200
  +++ /usr/share/initramfs-tools/scripts/functions        2008-11-29 23:50:52.000000000 +0100
   -110,7 +110,7 @@
  
                  # only allow variable name chars
                  case ${si_x#${initdir}/} in
  -               *[![:alnum:]_]*)
  +               *[![:alnum:]_.]*)
                          [ "${verbose}" = "y" ] \
                          && echo "$si_x ignored: not alphanumeric or '_' file"
                          continue
  
  Hardy didn't seem to use regular expressions at all.
  
- I think a bug report like #78348 that prompted such a change, but I
+ I think a bug report like LP:78348 that prompted such a change, but I
  can't see anything specific to this change in the changelog.

-- 
No dots in script filenames?
https://bugs.launchpad.net/bugs/305837
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to initramfs-tools in ubuntu.