smb
communism is bad for capitalism.
unconventional approach:
use reverse image search in hope that some other guy on the internet published a picture of the same but with the wires still connected.
when there are actually no exemptions present in a text, stating that a specific (maybe usually too common) exemption is not there, this statement is not only formally correct, but will be seen by archeologists in far future as a hint that such exemptions i.e. in laws were not only common, but also very known to the wide public. they will come to the conclusion that the public society didnt defend themselves against terrorists either due to fear of their terror or due to <censored to not "contaminate" the timeline>. either way they were doomed to what was inevitable to happen.
(i am preparing to write a scifi story where timelines are an important point while the whole story only tells about one of them. thats the context of my comment ;-) )
not sure at what level you are, here are some hints:
take your time to understand what the things do. shells like bash are very powerful and accidentially typing simething wrong could cause data loss or similar. but as you said, take care that you undestand what things are for and how they work.
most tools like sed or bash have a manpage that helps. bash has a huge one as it is very powerull (want to "program" like in C with pointers to variables, bash can do so using eval, which is evil, it really has downsides when doing too much in bash), but anyway learn the tools you use as you try them.
man sed
man bash
you can leave the manpage with pressing "q". pressing "h" shows how to navigate man pages.
the exit code of your script could come from bash itself or from the last command executed, it depends a bit. lets say bash stumbles over invalid syntax in the script while running the code or over a redirection ('<' '>') that points to an empty variable or nonexisting directory, then its bash who exits with its error. so an empty variable could cause such an error. but it usually exits with the exit code of the last run command (see bash "set -e" option which lets bash exit on the first failed command which together with the "-x" switch is very handy, but dont confuse it with other "-e" things in bash's huge manpage)
try in your console:
$ ( exit 34 )
$ echo $?
34
$ /bin/false
$ echo $?
1
$ ( set -e ; /bin/false ; echo bar )
$ echo $?
1
$ ( /bin/false ; echo foo )
foo
$ echo $?
0
using () in a terminal opens a subshell so that what you do there (set -e, setting variables etc) does not affect your current shells environment (unless you change files on disk or such) in the last case the exit code was from the "echo foo" command which succeded and returned 0 while the exit code of /bin/false was ignored (other than in that 'set -e' example)
i use exit codes a lot in bash scripts to control script flow also together with functions.
some programs have a bit mask of what went wrong ('man fsck' explains that they use a bitwise OR to determine the resulting exit code of the program to include multiple possible errors at once) so when dealing with an exit code other than 0 you likely first want to know which program caused it (maybe using the "-x" switch i.e.) and then consult man page or online help what it means.
as ocamlfuseStartup.sh is a shellscript you likely find what happens inside of it.
good luck
i would install cron if its not installed, then add a file under
/etc/cron.d/someNiceToRememberName
and with an editor write the following in it:
@reboot root /bin/bash -x /usr/local/bin/ocamlfuseStartup.sh >> /tmp/output 2>&1 ; echo returncode=$? >> /tmp/output
where root is the user it should run with and the redirection (>> /tmp/output 2>&1) is for seeing what is wrong, and echo returncode= prints the exit error indicator.
you might be able to do this with systemd too, but it often messes things up and i like i.e. clean log outputs.
for testing you can add a line that would start it without a reboot.
22 * * * * root /path/to/your/command parameters >> /tmp/output 2>&1
where the 22 is the next minute it should run. with this cronjob it would be run at every x:22 after each hour 09:22 pm 10:22 pm aso. i do this sometimes for testing
as systemd starts cron with a broken environment too, it might as well not work using cron, but then you know its the broken environment systemd starts it with. if thats your problem, you might want to add: PATH=$PATH:/usr/sbin:/usr/local/sbin
somewhere at the top of the shellscript depending on what is missing, which by itself would be the directories the commands executed are in. in terminal use :
$ which sed
/sbin/sed
for example to find where the "sed" binary is located (if the script cannot find it) you could change every occurance of "sed" in the script with the full path to it, or add the directory using the PATH variable as a colon separated list of directories to search commands in (where order matters)
to maybe more easy see what is missing i added the -x as a parameter to bash which makes it print out a line for every command it executes to sdterr so you can see what the last commands were. you can try it in the terminal (if your terminal is bash or compatible
$ set -x
$ echo foo
+ echo foo
foo
$
i'ld guess systemd starts the shellscript with a broken environment and thats maybe why it doesnt work, maybe try adding this to the script too:
echo PATH: $PATH
somewhere at the top of the script and use the redirection i showed for the cron job. run it once in your terminal and compare the output with what it prints during automated script run.
good luck.
transition to linux. One of the first things I have hit a wall on is getting a file to execute on boot using systemd.
I am trying to use this package to be
that bash thing is the interpreter. the script ocamlFuseStartup.sh is written as bash (possibly the same as your terminal) if that script has a "shebang" (#!/bin/bash) as the very first line AND the file has the execute permission set (chmod +x /path/to/file), then you dont need /bin/bash at the beginning to start it.
yes!, i knew polishing it would attract customers !
you'll have to scratch off the label i put there saying its mine, but you can try if you want, there are no lawyers on mars yet, however a rent has to be payed to me for just keeping it or claiming in public that this pebble was yours and as soon as lawyers arrive, we'll enforce the due payments to be collected ;-)
you're late, its already sold out that little planet lol
a ~~th~~ i ~~ng~~ is bad
hey there, i did something similar, but i run my own email server and setup the alias system by myself using postfix and dovecot. cost for domain depends in the domain, the cheapest one i have is 7$ per year. running a mailserver on a vm is like 5$/month or more. i also immediately move my emails from that vm to a raspberry pi running in my home, so i have physical access at any given time and i can literally use the cheapest vm as data is only stored on it for a few seconds.
i currently maintain my list of aliases in the "tables" app on a nextcloud instance on that same raspberry pi, so i can add or remove postfix virtual aliases from my cell, i use a pythkn script to read that mysql table and extract what is needed to create the virtual alias for postfix which is then synced to the vm via csync2
whenever spam arrives, i just change the address at the page/newsletter/shop where it was leaked, change my password there and tell the pageowner that they had a data leak.
i nearly get no spam at all, but when, i know who leaked my data, so i consider this sort of an advantage.
in my database i have the (automatic) creation date, switch if its enabled or disbaled, the date of deactication, i also added a 'notes' column for things like why i disabled it, when i asked for a password reset but didnt get an email so that when i finally deacticate it, i have sort of a documentation when and how i tried to delete the account (when the page is sort of dead for example) i also have a switch to which of my real accounts (not aliases) that alias belongs, so i have a postbox for important emails (server administration, access to providers management systems) and i.e. one for less important things like shops, newsletters etc.
creating single aliases for each newsletter was over the years a lot of work but always only when setting it up a few seconds, so no big deal. however after decades of doing so, i figured out that this is a very good documentation of where i have accounts etc. it WAS a big deal however when i wanted to clean things up, move those aliases from multiple domains to a single one, delete accounts i dont need any more, change passwords (possibly to better ones) and add passkeys or totp where possible in one go. that was a lot of work and i only have few aliases left, one company i.e. that lets me reset the password, login with it, but when i try to delete my account, they claim they witnessed "suspicious behaviour" and lock my account again, i guess they never implemented account deletion and try to cover that with abuse of their so cslled "security concerns". well, some providers are more difficult than others. those are the main reason why my cleanup still isnt done completely yet
i don't use kde, but the tray clock i used had its own timezone settings independently from system settings. maybe try looking into the settings of the tray clock instead of system settings.
so they reinvented the (steering) wheel and failed 🤣
there hasn't been a single solution for all problems since humans sort of know that solutions can exist. a bit of every step towards a better situation, and a bit more and more until it fits. i cannot say when it will fit, but destroying the future of whole generations is more like the definition of unfit than an achievement. it might be seen as glory by some confused and rich, but its filthyness in reality.
reduce demand-producers, reduce overall irrelevant work, that is i.e. all work done solely for increasing numbers on bank accounts that don't even change anything for that account owner any longer. we do ship things around the world that really should get processed locally. there are many things that are wrong only for keeping the pyramid schemes of the rich active.