That's generally what I do, but IIRC, that breaks rather a lot if you're using custom compile options for ports. For packages, metaports don't make much sense unless they're intended for use by the masses, as in one of the metaports included in the port tree.
Either way works fine. Good point if you are building your own ports, but to me that would assume you have a complete pkg build environment and all your systems point internally not externally so should pick up all your custom options
Where do you place your scripts? My first useful shell script will be configuring my phone as my network interface which i was manually doing everyday.
have a look at the examples in devd.conf()
attach 0 {
device-name "ue[0-9]+";
action "/etc/usb_tethering.sh start $device-name";
};
detach 0 {
device-name "ue[0-9]+";
action "/etc/usb_tethering.sh start $device-name";
};# nc -U /var/run/devd.pipe# cat /usr/local/etc/sudoers
%network ALL = NOPASSWD: /etc/rc.d/netif onerestart
%network ALL = NOPASSWD: /etc/rc.d/routing onerestart
%network ALL = NOPASSWD: /sbin/dhclient *
%network ALL = NOPASSWD: /sbin/ifconfig *
%network ALL = NOPASSWD: /sbin/ifconfig * up
%network ALL = NOPASSWD: /sbin/route *
%network ALL = NOPASSWD: /sbin/umount -f *
%network ALL = NOPASSWD: /usr/bin/killall -9 dhclient
%network ALL = NOPASSWD: /usr/bin/killall -9 ppp
%network ALL = NOPASSWD: /usr/bin/killall -9 wpa_supplicant
%network ALL = NOPASSWD: /usr/bin/killall *
%network ALL = NOPASSWD: /usr/bin/tee -a /etc/resolv.conf
%network ALL = NOPASSWD: /usr/bin/tee /etc/resolv.conf
%network ALL = NOPASSWD: /usr/local/sbin/vm switch address *
%network ALL = NOPASSWD: /usr/sbin/ppp *
%network ALL = NOPASSWD: /usr/sbin/service squid onerestart
%network ALL = NOPASSWD: /usr/sbin/wpa_supplicant *
# cat /usr/local/etc/doas.conf
permit nopass :network as root cmd /etc/rc.d/netif args onerestart
permit nopass :network as root cmd /etc/rc.d/routing args onerestart
permit nopass :network as root cmd /usr/sbin/service args squid onerestart
permit nopass :network as root cmd dhclient
permit nopass :network as root cmd ifconfig
permit nopass :network as root cmd killall
permit nopass :network as root cmd killall args -9 dhclient
permit nopass :network as root cmd killall args -9 ppp
permit nopass :network as root cmd killall args -9 wpa_supplicant
permit nopass :network as root cmd ppp
permit nopass :network as root cmd route
permit nopass :network as root cmd tee args -a /etc/resolv.conf
permit nopass :network as root cmd tee args /etc/resolv.conf
permit nopass :network as root cmd umount
permit nopass :network as root cmd vm args switch address
permit nopass :network as root cmd wpa_supplicantNo.
I had some of those settings you mentioned enabled from the start but only the screen thing... i didn't want that because i can't leave my phone unlocked for how long I'll be sitting on the computer, It will certainly affect the battery life along being it in charge mode through the usb, now i just have to unlock my phone before i plug to usb that's it.
notify 0 {
match "system" "IFNET";
match "subsystem" "ue0";
action "dhclient ue0";
};
attach 0 {
match "system" "IFNET";
match "subsystem" "ue0";
action "dhclient ue0";
};That's not my recollection other than in couple of very specific spots. That's looking back to Fortran 77 anyhow.
Yeah, but how do I monetise ...
Indentation had a simple role, no big semantic meaning. See "Fixed layout and punched Cards" in:
Not in any Fortran I know. Here is the 77 and 90 syntax:
if (some condition) then
true statement
else
false statement
end if
if (another condition) statementNot more awful than other languages.
YAML is a perfect example of semantic whitespace gone wrong. There are so many links I could use here. My personal experience with it has been dismal. Yes, I've run into weird number-parsing bugs (you meant to give that one CPU? You just gave it 1,000.) Yes, I've spent hours chasing an indentation error buried deep in a giant file.
Did you mean Guido? I think you got two people with Dutch-sounding names mixed up.
I used to actually indent Fortran IV source code. It doesn't violate the rules, makes things easier to read. Makes the code narrower, since you only have from column 8 to 72. But back then, we had fewer variables, therefore shorter variable names.
Was it Mortran? That was a genius language. Terrible hack, hard to debug (because the generated Fortran code was ugly it times), but pleasant to code in. Sort of Fortran IV with modern structured tooling, like good loops.
So sorry! You are absolutely correct, I mean Guido not Theo.Did you mean Guido? I think you got two people with Dutch-sounding names mixed up.
OT, or maybe not, this reminds me of pkl available in ports and pkgs. For those that don't know, it's from Apple and is intended to be used as something that you can write in that can be used to generate JSON, YAML and a couple other configuration formats. I've been meaning to give it a go, but the only use I have for it right now would be for stuff that I already coded for JSON.
