-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathLab3 ex1&2
15 lines (10 loc) · 928 Bytes
/
Lab3 ex1&2
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Compiling and packaging
Will we still be able to run \u201chellopenguin\u201d from any directory if we packaged it into \u201c/usr/share\u201d instead of \u201c/usr/bin\u201d?
No, I try to rename the "bin" to "share" and create the package again and when I try to use "hellopenguin" there is "bash: cd: ex1: No such file or directory". To solve this I use "export PATH=$PATH:/usr/share" and it work.
What is your rationale for the previous answer?
I'm not very sure, but I think "/usr/bin" is generally used for PATH sothat the "fpm" tool make it a "FPM tool defaults to using /usr/bin when creating a package and adds /usr/bin to the PATH during installation.
Debugging
What package was missing after trying to install ocfspy?
The complied file of ocfdocs.c and the folder structure of where the executable shall reside in.
What is the password that ocfspy outputs after fixing the dependency problem?
Passwork is Cyclone