You are not logged in.
so I was trying to make a startup script and in the process I deleted init.d
I created a script called net_load
i then tried to move it to the init.d directory like this.
# mv /home/net_load /etc/init.d
I am pretty sure I screwed up as soon as I hit return...
So, I have a couple options... create a new VM and reinstall Arch Linux (pretty easy, but not much of a learning experience)
Or I can learn how to target this folder and its contents and retrieve it (much better because there is a learning experience).
Can you be so kind and help me figure out how to get init.d back?
Offline
Arch hasn't supported /etc/init.d in a number of years...
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Ah ... what? Is this archlinux? Are you using an alternative init system?
/etc/init.d hasn't existed in archlinux in quite a long time (maybe a couple years). If you are using some non-standard init system, that is fine, but we'd need to know which one.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
What was the output when you ran the command. I';m not sure why you think it would have been a problem if the directory had existed.
"We may say most aptly, that the Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves." - Ada Lovelace
Offline
In addition to above, if you don't have mv aliased to mv -i you should fix that right away.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Was there ever init.d in Arch? There was rc.d, I guess.
Offline
I read in the cores utilites wiki about the aliasing and I will fix mv to mv -iv at once.
Well that probably explains why there was no folder....
Man this learning curve is tough. Sorry guys.
Offline
No point saying sorry. but can you explain why you thought init.d was there? And why you thought it was the right place for a "startup script"? Are you following some very old documentation instead of the current information available to you in man pages and the wiki?
Jumping in at the deep end is OK, but at least try to be prepared.
Offline