Article View: comp.sys.next.misc
Article #2734Re: stripping (was Ramdisk coming for NeXT)
From: Louis A. Mamakos
Date: Sun, 23 Aug 1992 05:18
Date: Sun, 23 Aug 1992 05:18
46 lines
2699 bytes
2699 bytes
In article <1992Aug22.220611.7529@nic.umass.edu> a74k110@titan.ucc.umass.edu (Chris Lloyd) writes: >In article <1992Aug22.205249.27205@atlantis.uucp> bugs@atlantis.uucp (Dan Berry) writes: >> "If you want to save some space, try stripping sdmach [hah hah hah]" >> (paraphrased) >> >>Well, I thought he was joking. And yet, amazingly enough... >> >>atlantis> ls -l /sdmach >>-r-xr--r-- 2 root 708219 Aug 14 19:11 /sdmach* >>atlantis> ls -l /tmp/sdmach >>-rwxr--r-- 1 bugs 624388 Aug 22 14:32 /tmp/sdmach* >> >>*** YEESH! ALERT *** >>How can this be? And although I feel that the stripped version might work with >>no problems, _I_ ain't gonna be the one to try it out. It might work in the >>beginning, but I'd hate to have to deal with sporatic mach-kernel errors. > >Stripping /sdmach won't cause kernel errors per se, just errors when >something tries to link with it, such as kernel loaded servers which use >the relocation info (which strip removes) to link into the kernel. > >If you never intend on using, Midi, NeXTDimension, SLIP, PPP, >MallocDebug (either this or AppInspector, I forget which one), the Tablet >driver, ISDN, TTYDSP, and others I haven't mentioned and others >which will come along, then it's probably fine to do :) And you never intend to use any programs that nlist() the kernel to local symbols. Like netstat, or ps or uptime. >Never hurts to try this stuff, worst that will happen is you'll learn >something, Or worse, you hose your system and then post questions about how to recover a hosed UNIX file system. There's a reason that a lot of these files are owned by root (or bin or anything else) and why normal users don't have write permission on them. Experiment all you want, but you ought to be sure to make a backup first and know how to restore from that backup. Is it really worth the 80k-odd bytes you get back? This reminds me of the common user-error: I deleted that /vmunix program that I never use, and now my system won't boot! I suspect that he *was* really joking, like they guy that suggested you compress your swapfile. [No you can't do this.] louie
Technical Details
Message-ID:
<1992Aug23.051823.1291@ni.umd.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louieReferences:
<1992Aug22.205249.27205@atlantis.uucp> <1992Aug22.220611.7529@nic.umass.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.misc Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louie From: louie@sayshell.umd.edu (Louis A. Mamakos) Subject: Re: stripping (was Ramdisk coming for NeXT) Message-ID: <1992Aug23.051823.1291@ni.umd.edu> Sender: usenet@ni.umd.edu (USENET News System) Nntp-Posting-Host: sayshell.umd.edu Organization: University of Maryland College Park References: <1992Aug22.205249.27205@atlantis.uucp> <1992Aug22.220611.7529@nic.umass.edu> Date: Sun, 23 Aug 1992 05:18:23 GMT Lines: 48