On 21/11/18 at 18:49, k...@aspodata.se wrote:
> Alessandro:
>> On 21/11/18 at 17:34, k...@aspodata.se wrote:
>>> Alessandro:
>>>> On 21/11/18 at 14:35, k...@aspodata.se wrote:
>>>>> Hendrik:
>>>>> ...
>>>>>> Wait a moment.  Haven't we already done this with /boot?  Should we 
>>>>>> perhaps have /boot/sbin, and so forth?
>>>>> /boot is a viable initrd replacement.
>>>>   No, it is not.  An initramfs is needed to perform actions that must be
>>>> done before the / filesystem can be mounted.  /boot does not solve the
>>>> problem of accessing the local storage before it becomes available.
>>> What is the problem you is pointing at ?
>>>
>>> To boot with an uefi system you need a fat partition available before 
>>> even the bootloader is loaded, so what is the reason that you cannot 
>>> use that instead of an initrd ?
>>   I commented about the idea of using /boot in place of the initramfs,
>> not about using the EFI partition for that.
>>
>>   You still cannot (or at least should not) do that due to the fact that
>> that partition is reserved to EFI, you should not put foreign files into
>> it, and initramfs are normally a Unix filesystem, a vfat fiesystem could
>> well not work (would the kernel recognize /init as an executable file,
>> for instance?).
> You can always mount the fat with umask=000 or with showexec and name 
> the scripts/programs like .exe/.bat/.com.


  In an initramfs?


  Seriously?



-- 
Alessandro Selli <alessandrose...@linux.com>
VOIP SIP: dhatarat...@ekiga.net
Chiave firma e cifratura PGP/GPG signing and encoding key:
  BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to