All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Kochetkov <fido_max@inbox.ru>
To: buildroot@busybox.net
Subject: [Buildroot] - Question: How to change safely /var/log --> /tmp in buildroot
Date: Thu, 8 Apr 2021 18:08:53 +0300	[thread overview]
Message-ID: <5b302df4-b83b-f46b-28cd-235c2779e851@inbox.ru> (raw)
In-Reply-To: <02af48b6-e128-6b75-5f38-220ff4b6ed67@gmail.com>

1. You can implement your own skeleton (based on your current skeleton)
2. You can modify your target rootfs by rootfs-overlay (BR2_ROOTFS_OVERLAY)
3. You can modify your target rootfs by BR2_ROOTFS_POST_BUILD_SCRIPT

The easiest way is 2.
I would recommend you to create your own skeleton.

08.04.2021 17:39, Marko Stanisic ?????:
> Thank you for the fast response,
> 
> is it possible to overwrite that behaviour by introducing an overlay 
> filesystem and
> 
>  ??? (1) create a "relative" symlink /var/log --> ../tmp/LOG", and 
> afterwards
> 
>  ??? (2) mount /tmp/LOG --> /mmcblk0p9
> 
> I already? testet it manually on the board, but still not sure how to 
> implement (2) :
> 
>  ?? 2.1) postimage.sh (which i use to create the images)
> 
>  ??? 2.2) or as an init script in init.d
> 
> 
> (3) take your solution and chnage behaviour in skeleton-init-sysv or 
> skeleton-init-openrc package
> if that is possible
> 
> 
> Thanks again for everyy support!!!
> 
> 
> 
> On 08/04/2021 16:32, Maxim Kochetkov wrote:
>> Hi, Marko
>>
>> 08.04.2021 16:41, Marko Stanisic ?????:
>>> Hello,
>>>
>>> I have no clue how? the symlink? /var/log --> ../tmp is statically 
>>> defined. (in buildroot)
>>>
>>
>>
>> This link is created by skeleton-init-sysv or skeleton-init-openrc 
>> package
>>

  reply	other threads:[~2021-04-08 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 13:41 [Buildroot] - Question: How to change safely /var/log --> /tmp in buildroot Marko Stanisic
2021-04-08 14:32 ` Maxim Kochetkov
2021-04-08 14:39   ` Marko Stanisic
2021-04-08 15:08     ` Maxim Kochetkov [this message]
2021-04-09 13:07       ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5b302df4-b83b-f46b-28cd-235c2779e851@inbox.ru \
    --to=fido_max@inbox.ru \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.