Re: Definition of service, daemon, script, program and process

--a18wQZUiUjV3U2wr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Steve Litt schrob:
> I've heard the term "script" used many different ways. [...]
> although these days with Just In Time compilation,
> "interpreted language" is a fuzzy term. On a personal level, I view
> this as a distinction lacking a difference: One can perform almost any
> task (perhaps very badly) from either bash or C. I personally call all
> of them "programs".

My definition is:

If I can read the output of "cat `which foo`", then foo is a script,
else it's a binary program.

And the meaningful-to-me difference is that I can simply rsync a script
to any other machine. For binaries, that won't be useful unless the
machines involved share their architecture (and libc).

Hence I have a few C scripts. They start with #!/usr/bin/tcc -run

cheers,
    Jan

--a18wQZUiUjV3U2wr
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEFzbVDxcLcKaSI7wVKV5wPm0dL88FAmoMpNcACgkQKV5wPm0d
L89RsQ/+MwYvEmWMpEL+OfJ4BjZtxym6oT7C7PIFDsVEu+YKsJC6tU61mUitptla
dQTZPMUZMO61HfVTz3TobqlZQmvZirQDT5fe+UwU6P9vR8sgxs3oy0OJgzD/v1RW
treoidfOem2RUZWRFW3FQ4ZJ1KwyjhFW65+pW09NcAiUUhrCUKdPWqSk70HEB5K2
XsavXiVtjvhs+Nz11aksM4iMmBQmGnJPqEc2DtGoOhfL8jkEBIOcSls1ZKEkmW0o
4WjLU2WXLvxmRn03p55ktyBZj+FPoAnL2z+G3HKZbBBXgUF6h2GHifdkeS75M1Er
4IvjUUcqiwv8H7AFaoAeI9bmk88/TE07tJg8mBxEHc+XRHSROGa3+aCqN0OEAWBa
401vmVWv056WwLA99ZFb+rJvvn1x+4cvwuriBJwnszJPIHl4NxvlgRtFqmhDoLap
juK4u73ffNUx4OEt07WT5yH4i175HL1milODSpZCsH+mBlyPuD3zfHJxthbsyEwA
cg40tIp1m5finSequAVhw7waOCnup4ssOmW+yXRRHgUelh7p8EB/F2Rwpb+2/JD6
saZOI7S7PkYofsrXVMO7EmnERbYDfFvhOfRYWD/6QFQxSXXI+H/dveOKykavWv06
wXuFEAsE5Up1N84bBDENQtppcxurD0mgNHMwxBbI2AsPu0xayuk=
=4c//
-----END PGP SIGNATURE-----

--a18wQZUiUjV3U2wr--