public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Initscripts in 'src/system' with 0755 permissions!?
Date: Sat, 11 Apr 2020 09:44:14 +0100	[thread overview]
Message-ID: <2C5D9C8C-96AA-4DD2-9351-7D39D522E393@ipfire.org> (raw)
In-Reply-To: <5cc80bd6-4c69-79ca-9b5c-45328307b4a2@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

Hi,

No, there is no need for it.

With exception of make.sh everything else should be 644.

It happens that files get 755 in the source when they are being copied after being tested on a development system.

-Michael

> On 11 Apr 2020, at 09:22, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> I just noticed that some initscripts in 'src/system', 'src/packages'
> have '0755' permissions.
> 
> conntrackd
> lvmetad
> vnstat
> ...
> avahi
> bird
> frr
> guardian
> shairport-sync
> 
> Is there a specific reason for this?
> 
> Otherwise I'd like to change them to '0644' - like all the others.
> 
> Best,
> Matthias


      reply	other threads:[~2020-04-11  8:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11  8:22 Matthias Fischer
2020-04-11  8:44 ` Michael Tremer [this message]

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=2C5D9C8C-96AA-4DD2-9351-7D39D522E393@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox