From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: 66: clean default $PATH, change system-dir.
Date: Wed, 24 Feb 2021 16:16:14 +0100 [thread overview]
Message-ID: <20210224151614.dokhprqg54X53Zpq100BaU7S1i_RgbuqtB_Gfii2bVw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28783@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
There's a merged pull request on the void-packages repository
66: clean default $PATH, change system-dir.
https://github.com/void-linux/void-packages/pull/28783
Description:
<!-- Mark items with [x] where applicable -->
#### General
#### Have the results of the proposed changes been tested?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
There are two significant changes in the commit.
1. The default $PATH 66 uses for the services contains too many dirs. This reduces it to just /usr/bin:/usr/sbin, which is what runsvdir uses by default.
2. The default directory for the system-dir, which is where 66 stores the trees created and information about enabled services, is `/var/lib/66`. But 66 can be used to boot a system and /var may not be in the root filesystem or mounted early, so boot will fail. This update, changes service-dir to `/usr/lib/66`. Users that upgrade from an earlier version or revision should either copy the contents of the old system-dir to the new or create trees again and enable services.
@gspe @flexibeast @Obarun
prev parent reply other threads:[~2021-02-24 15:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 19:23 [PR PATCH] " mobinmob
2021-02-15 19:30 ` [PR PATCH] [Updated] " mobinmob
2021-02-16 16:03 ` ericonr
2021-02-16 16:20 ` mobinmob
2021-02-16 18:55 ` [PR PATCH] [Updated] " mobinmob
2021-02-16 18:58 ` mobinmob
2021-02-16 18:59 ` mobinmob
2021-02-24 4:21 ` [PR REVIEW] " ericonr
2021-02-24 4:21 ` ericonr
2021-02-24 9:47 ` [PR PATCH] [Updated] " mobinmob
2021-02-24 9:49 ` [PR REVIEW] " mobinmob
2021-02-24 9:51 ` mobinmob
2021-02-24 12:41 ` [PR PATCH] [Updated] " mobinmob
2021-02-24 12:48 ` mobinmob
2021-02-24 12:49 ` [PR REVIEW] " mobinmob
2021-02-24 13:32 ` mobinmob
2021-02-24 14:15 ` [PR REVIEW] " mobinmob
2021-02-24 15:04 ` ericonr
2021-02-24 15:16 ` ericonr [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=20210224151614.dokhprqg54X53Zpq100BaU7S1i_RgbuqtB_Gfii2bVw@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).