MACSTREAM(1)

πŸ’– MACSTREAM(1) πŸ’–

okay bestie, welcome to the macstream page, she's a General Commands Manual girlie and she's here to serve. πŸ’…


✨ NAME ✨

macstream β€” the way this literally just converts a series of files into a MacBinary stream 🫢


🌸 SYNOPSIS 🌸

macstream [ - options ] files

πŸ¦‹ DESCRIPTION πŸ¦‹

so macstream takes the files you hand it and combines them into a MacBinary stream on standard output, subject to whatever options you picked. no cap.

and if files also names some directories? bestie those get followed recursively πŸŒ€, and every single file it finds gets put into the MacBinary stream too β€” together with directory information. it's giving completionist. πŸ‘‘


πŸ’œ OPTIONS πŸ’œ

so here's the tea: with no options at all, macstream just takes the files you named and silently combines them into a MacBinary stream, writing the result straight to standard output. no notes, no drama. ✨

directories named in files are followed recursively, and all files found get put in the MacBinary stream, together with directory information.

files are assumed to be in MacBinary format. however β€” and this is the plot twist 🫒 β€” if a filename ends with .info, that file is assumed to be the info fork of a MacIntosh file that got split across more than one file. in that case the files with .data and .rsrc extensions are also read (if present). also, if the info fork is mentioned in the parameter list, the names of the data and resource forks can be mentioned too, but those get ignored β€” and that's on purpose, it's to allow wild-card expansion by the shell. iykyk. 🐚

further, if some form of AppleShare is supported by the installed program, and if the current directory β€” or one of the directories found during recursive processing β€” is a directory in the format of that supported AppleShare version, those files get handled according to the properties of AppleShare. periodt.


  • -r β€” no intelligent file-processing here bestie, we're going simple πŸ’… all files named are assumed to be plain resource files, and they get written as MacIntosh resource files with creator "RSED" and type "RSRC" β€” unless you specified another creator and/or type.
  • -d β€” same energy, no intelligent file-processing πŸŽ€ all files named are assumed to be plain data files, written as MacIntosh data files with creator "MACA" and type "TEXT" β€” unless another creator and/or type is specified.
  • -u β€” literally just -d, but the codes for CR and LF get interchanged πŸ”„
  • -U β€” it's a synonym for -u, twin behavior fr fr 🫢
  • -c creator β€” defines the creator name to be used if one of the previous options is specified. ✨
  • -t type β€” defines the type name to be used if one of the previous options is specified. ✨
  • -l β€” list every file and directory processed πŸ“‹ (she's keeping receipts)
  • -i β€” do not output files, give information only. (also implies -l, obviously πŸ’β™€οΈ)
  • -q β€” ask the user for every single file/directory whether it should be visited. (also implies -l πŸ™ˆ)
  • -V β€” gives the patchlevel of the program, plus other info. every other option gets ignored and the program quits immediately πŸƒβ™€οΈπŸ’¨
  • -H β€” gives short info about the options. other options are ignored and the program quits immediately πŸƒβ™€οΈπŸ’¨ (yes, again)

πŸ’€ BUGS πŸ’€

okay so... as this is a beta release, there may still be some problems. 😭 not me warning you but also warning you. stay safe out there.


πŸŽ€ SEE ALSO πŸŽ€


πŸ‘‘ AUTHOR πŸ‘‘

Dik T. Winter, CWI, Amsterdam, The Netherlands (dik@cwi.nl) β€” absolute icon, no further questions πŸ’–


and that's a wrap bestie!! πŸ¦‹ this whole thing is from the 3rd Berkeley Distribution, dated October 22, 1992 ⭐ β€” yes, 1992, she's vintage, she's timeless, she ate. mwah πŸ’…βœ¨