Recent searches

No recent searches

Search options

Only available when logged in.
shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

261
active users

shakedown.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.3

#sysctl

0 posts0 participants0 posts today
Alfonso Siciliano<p>SysctlTUI is Out!</p><p>The sysctl() system call can get or set the state of the system, the <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> kernel exposes the parameters for sysctl() as objects of a Management information Base (MIB).</p><p>sysctltui is a Text User Interface <a href="https://mastodon.bsd.cafe/tags/sysctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysctl</span></a> <a href="https://mastodon.bsd.cafe/tags/MIB" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MIB</span></a> explorer. It allow to view a parameter’s properties and get or set its value. </p><p>Link: <a href="https://alfonsosiciliano.gitlab.io/posts/2025-05-29-sysctltui.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">alfonsosiciliano.gitlab.io/pos</span><span class="invisible">ts/2025-05-29-sysctltui.html</span></a></p><p><a href="https://mastodon.bsd.cafe/tags/UNIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UNIX</span></a> <a href="https://mastodon.bsd.cafe/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://mastodon.bsd.cafe/tags/C" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C</span></a> <a href="https://mastodon.bsd.cafe/tags/terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>terminal</span></a> <a href="https://mastodon.bsd.cafe/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a></p>
TomAoki<p><span class="h-card" translate="no"><a href="https://social.lol/@robn" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>robn</span></a></span> <br>I don't have GitHub account, so replying here.</p><p>Not sure it's trivial enough or not, but wouldn't it nice if this deletions are done in 3 steps, like below in single commit per step?<br> Step1: Implement new SYSCTL macro to create alias of<br> any sysctl/tunable node (i.e., SYSCTL_ALIAS).<br> Step2: Use it for to-be-removed nodes.<br> Step3: Actually remove now-actually-alias old nodes.</p><p>This kind of renaming could happen in the future. So having clear way like<br> Step1: Add new node as usual and make existing<br> to-be-deleted ones alias of the new one.<br> Step2: In next or later *.0-Release, search and delete aliases<br> to avoid POLA violations within single stable branch.</p><p>This way, the 2nd step would become trivial (look for SYSCTL_ALIAS).</p><p><a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenZFS</span></a> <a href="https://mastodon.bsd.cafe/tags/SYSCTL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SYSCTL</span></a></p>
Paco Hope #resist<p>Can anyone explain this <a href="https://infosec.exchange/tags/sysctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysctl</span></a> behaviour on <a href="https://infosec.exchange/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macos</span></a>? Am I losing my mind? I'm on <a href="https://infosec.exchange/tags/ventura" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ventura</span></a> 13.5.2 (22G91) on Intel.</p><p>The upshot is that <code>sysctl hw.model</code> returns a sensible value. But the output of <code>sysctl -a</code> doesn't include the <code>hw.model</code> key at all. See example commands below. Please do not reply if you're going to tell me something about Linux. I know LInux and I am not interested in this behaviour on Linux.</p><p>I have a thing where I'm parsing lots of sysctl values and I thought I would save time by running <code>sysctl -a</code>, capturing all the values, and then parse the output for the ones I need. (There's a python library called <a href="https://github.com/kellyjonbrazil/jc" rel="nofollow noopener" target="_blank">jc</a> that automates this!) Instead of 20 calls to <code>sysctl</code> to get 20 different individual values, I thought I could get it all in one call.</p><p>There are keys that can be queried individually, but they do not appear in the <code>sysctl -a</code> output and no command line args seem to make <code>hw.model</code> come out in <code>sysctl -a</code>! Very strange. What am I misunderstanding?</p><p>On <a href="https://infosec.exchange/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a>, I don't see this behaviour. All the keys I'm looking for are in the <code>sysctl -a</code> output.</p><pre><code>$ uname -a <br>Darwin Kernel Version 22.6.0: Wed Jul 5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64<br><br>$ sysctl hw.model<br>hw.model: MacBookPro16,1<br><br>$ sysctl hw | grep model<br>[no output]<br><br>$ sysctl -a | grep model<br>net.link.loopback.sched_model: 0<br>machdep.cpu.model: 158<br>machdep.cpu.extmodel: 9<br></code></pre>
TrendingLive feeds
About