| 1 |
On 2022.05.24 12:58, Rich Freeman wrote: |
| 2 |
> On Tue, May 24, 2022 at 6:49 AM <karl@××××××××.se> wrote: |
| 3 |
> > |
| 4 |
> > Is there some hook to emerge I can use where I can attach some code |
| 5 |
> to |
| 6 |
> > run tests after each individual package when doing emerge @world ? |
| 7 |
> > |
| 8 |
> |
| 9 |
> So, Portage has hooks, and that would work for any file being |
| 10 |
> installed normally (so would config protection and that would be a |
| 11 |
> much easier solution). |
| 12 |
> |
| 13 |
> There are a couple of problems though: |
| 14 |
> 1. The only package I'm aware of that directly touches /dev is |
| 15 |
> static-dev (which I hadn't even heard of until you mentioned it). It |
| 16 |
> uses a post-install hook to create device nodes, so there is no |
| 17 |
> opportunity to inspect anything before /dev is modified. This isn't |
| 18 |
> the normal way to install files, but of course it isn't installing |
| 19 |
> normal files. |
| 20 |
> 2. I think it is very unlikely that a package is directly modifying |
| 21 |
> /dev. It seems more likely that a package is installing some daemon |
| 22 |
> that gets run as root and then it modifies /dev, maybe on your next |
| 23 |
> boot. Obviously if you install something like udev you'd expect to |
| 24 |
> end up with /dev getting modified when it runs. Again, there is |
| 25 |
> nothing for a hook to detect. |
| 26 |
> |
| 27 |
> Having a backup (it is static after all), and something like a |
| 28 |
> read-only mount might be your better solutions, if you really want a |
| 29 |
> static dev, or maybe marking files as immutable or something. (You |
| 30 |
> might want to test that - I am assuming you could still write to a |
| 31 |
> device node on a read-only filesystem but it isn't like I've tried. I |
| 32 |
> don't think there is anything special about /dev so you could just |
| 33 |
> create a device node in some other read-only filesystem and test it |
| 34 |
> out.) |
| 35 |
> |
| 36 |
> If you do find a random package touching /dev I think most here would |
| 37 |
> be pretty interested, as that seems rather bizarre. |
| 38 |
> |
| 39 |
> -- |
| 40 |
> Rich |
| 41 |
> |
| 42 |
> |
| 43 |
|
| 44 |
Team, |
| 45 |
|
| 46 |
As a long time static /dev user the only thing I've noticed updates making |
| 47 |
a mess of is /dev/snd. I've not traced that, I know what it is and how to |
| 48 |
fix it. Its faster to fix it now and again that it is to establish the root cause. |
| 49 |
|
| 50 |
-- |
| 51 |
Regards, |
| 52 |
|
| 53 |
Roy Bamford |
| 54 |
(Neddyseagoon) a member of |
| 55 |
elections |
| 56 |
gentoo-ops |
| 57 |
forum-mods |
| 58 |
arm64 |
Archives