Messages in this thread | | | Date | Thu, 27 Mar 2014 09:25:57 +0100 | From | Alexander Holler <> | Subject | Re: [PATCH v2] initramfs: print error and shell out for unsupported content |
| |
Am 26.03.2014 23:37, schrieb Alexander Holler: > Am 26.03.2014 22:55, schrieb Alexander Holler: >> Am 26.03.2014 22:38, schrieb Levente Kurusa:
>>> This is walkable but probably not worth the effort. Besides, why would >>> anyone want to put spaces, colons and arbitrary characters to filenames >>> in the initramfs? > > I've already suggest an example for that. If you have a machine with > bluetooth, look at /var/lib/bluetooth and you will discover directories > with colons. So, guess what happens if you want to have (preset) > link-keys in an initramfs to avoid an otherwise necessary pairing. > > And spaces in filenames are used by a lot of people for various reasons. > And you might wonder, but there exists software one might want to use in > an initramfs which needs some file(s) with an hardcoded name wich > contains spaces.
Just that this problem exists at least since the dawn of git doesn't mean nobody has suffert through it.
E.g. I know the bug with colons since several years, but just feared to post a simple patch (for legitimate reasons as this thread shows).
Alexander Holler
| |