ping Slack dev team
in [Slackware]
|
Prev: LewPitcher.ca tops Google Search!
Next: Xorg and Intel Integrated Graphics Chipset: low resolution
From: Lew Pitcher on 27 Nov 2009 10:26 On November 27, 2009 10:17, in alt.os.linux.slackware, Aaron W. Hsu (arcfide(a)local) wrote: > Roger Maynard <lewpitcher(a)lewpitcher.ca> writes: > >>But ed requires libraries. There are several tiny editors around >>that do not require a library - there is one called "q" if I recall >>correctly, and these are more ideal for a rescue disk. > > I only see ed linked against libc. Anyway, Roger is wrong. While ed, as delivered in the Slackware package, requires libraries, there is no reason that ed /must be/ compiled to require libraries; it is easy enough to static link all the required libraries directly into the binary, and have a "stand alone" ed. You can use this technique on most utilities; the only tradeoff is that the size of the resulting binary is larger than the dynamic linked version. Many Unix and Unix-like systems provide (or provided) static linked binaries in the /sbin and /bin directories, just to cover the case where a sysadmin needed to fix a system that had lost some of it's libraries. -- Lew Pitcher Master Codewright & JOAT-in-training | Registered Linux User #112576 Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/ ---------- Slackware - Because I know what I'm doing. ------
From: Aaron W. Hsu on 27 Nov 2009 10:29 Mike Jones <Not(a)Arizona.Bay> writes: >You're missing the point by a mile here. >Ok, so assume the role of "not a sysadmin" (ie: end-user with few clues) >and imagine you have a glitched system and need to do a spot of text >hacking, say, to remove the root password from /etc/shadow (as in "I >forgot my root password! Help!"). [...] >For this purpose, Vi not only fails dismally, but actually places the >wannabe repair guy in a no-win situation. If this is the situation you suggested, then they won't know about the /etc/passwd file. This means that they will be following some guide. This also means that they should be chrooting into their system as soon as they can. It's a simple command, and it gets you all your old software, including nano. If you are able to mount and get into the system, and all you have to do is change a few files, then there's nothing hard here, and in fact, single-user mode is probably more useful than a recovery disk for this. Either way, you get nano, and the recovery disk does not have to change. Aaron W. Hsu
From: Theodore Heise on 27 Nov 2009 11:20 On Fri, 27 Nov 2009 20:04:27 +1100, Grant <g_r_a_n_t_(a)bugsplatter.id.au> wrote: > > On a new system first things copied from the file server (once I > get nfs access) are custom .vimrc and .bash* files, the > ~/.ssh/authorized_keys for root and user, and my kernel build > scripts. > > Then I have vim tamed, and only meet vi in its other roles as > 'crontab -e' and visudo -- what do the nano, pica people do > here? I admin my own server, but it's essentially single user and I don't do much that's sophisticated. I've been using Pine for probably 15 years, so I generally favor pico for most editing. When faced with the vi interface that follows 'crontab -e', I reach for the O'Reilly "Unix in a Nutshell" book, in which I've put a tab at the chapter on vi. -- Theodore (Ted) Heise <theo(a)heise.nu> Bloomington, IN, USA
From: Sylvain Robitaille on 27 Nov 2009 11:24 On Fri, 27 Nov 2009 08:21:21 +0100, Henrik Carlqvist wrote: >> Then I saw colleagues doing some things with vim that I'd been wishing >> I could figure out how to do with Emacs > > Even though this thread has since long left its initial purpose I get > curios. Do you have any quick example of some of those things vi can > do? vim in this particular case, not (ordinary) vi. They're not the same. Things like reformatting lines quoted from a netnews article, without first removing the preceding quote (">") characters, then adding them back after formatting (highlight the lines in question, then "gq"). Things like being able to edit a vertical block of text. Things like sending selected text to an external command and receiving the output back into the edit buffer. (that last one I'm sure is possible in Emacs, and I likely even once knew how to do it, but it's something I do quite regularly in vi/vim, without even thinking about it, and I now don't know how to do in Emacs ...) There are probably many more, and many might be possible in Emacs, but I hadn't learned how, or have long ago forgotten how. The power and simplicity of vi(m), ironically given this thread, is what ultimately caused me to move away from Emacs. I don't knock Emacs or get into flame wars about it, as I do think it's an excellent text editor, but for how I work, vim is much better suited, and basic vi is at least close enough in a pinch. -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: Keith Keller on 27 Nov 2009 11:26
On 2009-11-27, Mike Jones <Not(a)Arizona.Bay> wrote: > > BTW, As you missed this one several times now, I'd suggest that you hold > back on making jibes about credibility here. You're drifting into a "My > fav app" flame-war position. This is like the black hole calling the kettle black. --keith -- kkeller-usenet(a)wombat.san-francisco.ca.us (try just my userid to email me) AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt see X- headers for PGP signature information |