On 08.03.2012 23:51, Richard Laager wrote:
> I believe the following change is still needed to support pool names
> with spaces. That said, maybe we shouldn't care about pool names with
> spaces. If a pool name has spaces, then we need some way to escape it
> when building the linux_entry command line.
HAve you tried simply putting single quotes around it
>  Then the initrd needs to
> unescape it.
If it uses /proc/cmdline then yes. If it gets arguments from init then
it wouldn't be a problem.
>  That seems like a lot of hassle for a configuration that's
> likely to be extremely uncommon even if GRUB does support it.


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko