get_machine.1 1.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
  1. .\"Made with Love
  2. .TH get_machine 1 "JULY 2019" Linux "User Manuals"
  3. .SH NAME
  4. get_machine - identify running hardware architecture
  5. .SH SYNOPSIS
  6. get_machine [ --exact --override OVERRIDE --OS ]
  7. .SH DESCRIPTION
  8. get_machine exists to make simple shell scripts that need
  9. to know that hardware architecture it is assuming or what
  10. host operating system is being used.
  11. .br
  12. At its core is figure out the general hardware architecture
  13. and return it as quickly as possible. Although it is sometimes
  14. useful to return something different; which is why --override
  15. exits and thus what ever is supplied by with it is returned.
  16. Scripts that wish to expose that can leverage the environment
  17. variable GET_MACHINE_FLAGS to allow efficient overriding in
  18. their scripts.
  19. .br
  20. If one wishes for something more exact than x86 or amd64, the
  21. option --exact will return more specific values like i686-pae.
  22. .br
  23. Should one desire to know the host operating system: --OS
  24. .br
  25. A word of warning; --override always will take top precedence
  26. and can return anything you desire.
  27. .SH EXAMPLES
  28. Typically, get_machine will be in scripts used in bootstrapping
  29. .br
  30. # get_machine
  31. .br
  32. # get_machine --override "I am the very model of a modern major general"
  33. .br
  34. # get_machine ${GET_MACHINE_FLAGS}
  35. .br
  36. .SH COMPATIBILITY
  37. get_machine is compatible with all Turing complete machines;
  38. even the ones that try to be Turing complete -1
  39. .SH AUTHORS
  40. Jeremiah Orians <Jeremiah@pdp10.guru>
  41. .SH COPYRIGHT
  42. Copyright 2016-2019 Jeremiah Orians <Jeremiah@pdp10.guru>
  43. .br
  44. License GPLv3+.
  45. .SH "SEE ALSO"
  46. M1(1), hex2(1), blood-elf(1), kaem(1), syscalls(2)