1. Forum
  2. FidoNet
  3. RBERRYPI

  • rpi4 kernel btrfs/configs

    From Ralph Spitzner@3:770/3 to All on Wed Mar 24 12:45:25 2021
    normally btrfs and configs (/proc/config.gz) are built as modules.
    Iwant to have / on a btrfs, if I change both from M to * (builtin), no modules are built,
    but there's no /proc/config.gz an a btrfs partition is a "unknown filesystem". Any idea why these are not working, when compiled into the kernel ?

    regards
    -rasp

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Theo@3:770/3 to Ralph Spitzner on Wed Mar 24 23:26:55 2021
    Ralph Spitzner <rasp@spitzner.org> wrote:
    normally btrfs and configs (/proc/config.gz) are built as modules.
    Iwant to have / on a btrfs, if I change both from M to * (builtin), no modules are built,
    but there's no /proc/config.gz an a btrfs partition is a "unknown filesystem".
    Any idea why these are not working, when compiled into the kernel ?

    /proc is not on your storage, it's a virtual filesystem provided by the
    kernel.

    # mount -t procfs proc /proc

    will mount it, assuming you have an empty directory at /proc. Perhaps your root volume doesn't have that directory?

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Ralph Spitzner@3:770/3 to Theo on Fri Mar 26 09:41:46 2021
    Theo wrote on 3/25/21 12:26 AM:
    # mount -t procfs proc /proc

    Theo

    sorry. but /proc itself is fine...
    the question was: why does the config access and btrfs work as modules,
    but noy when built _into_ the kernel

    -rasp

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Tauno Voipio@3:770/3 to Ralph Spitzner on Sat Mar 27 18:13:03 2021
    On 26.3.2021 10:41 AM, Ralph Spitzner wrote:
    Theo wrote on 3/25/21 12:26 AM:
    # mount -t procfs proc /proc

    Theo

    sorry. but /proc itself is fine...
    the question was: why does the config access and btrfs work as modules,
    but noy when built _into_ the kernel

        -rasp

    Just a guess: the built-in file system starts up before
    the /proc filesystem is mounted.

    You should return to a module and set it up into the initrd.

    --

    -TV

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Ralph Spitzner@3:770/3 to Tauno Voipio on Sat Mar 27 22:33:43 2021
    Tauno Voipio wrote on 3/27/21 5:13 PM:

    Just a guess: the built-in file system starts up before
    the /proc filesystem is mounted.

    Still doesn't explain why the exact same options are working on a x85-64 system


    You should return to a module and set it up into the initrd.

    on my laptop (t430) I'm using slackwares Kernel, which has almost everything compiled in,
    there's no initrd, there root (/) is on a btrfs and /proc is fine.
    So I'm guessing I may miss some 'helper' / glue option in the kernel config to make this work as
    builtin ... (I don't like initrds as I tend to forget to update them :-) )

    -rasp

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)