Date: Tue, 11 Jan 2000 23:08:06 +1000 From: Stephen McKay <syssgm@detir.qld.gov.au> To: naddy@mips.rhein-neckar.de (Christian Weisgerber) Cc: freebsd-security@freebsd.org, syssgm@detir.qld.gov.au Subject: Re: dump over ssh Message-ID: <200001111308.XAA31980@nymph.detir.qld.gov.au> In-Reply-To: <858p5j$mu3$1@bigeye.rhein-neckar.de> from Christian Weisgerber at "09 Jan 2000 02:44:19 %2B0100" References: <854v9q$1gf9$1@bigeye.rhein-neckar.de> <858p5j$mu3$1@bigeye.rhein-neckar.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 9th January 2000, Christian Weisgerber wrote: >Christian Weisgerber <naddy@mips.rhein-neckar.de> wrote: > >> # dump -0aP ssh -f host:/dev/nrsa0 / > >BTW, I just noticed that the Linux port of dump contains equivalent >functionality. No additional flag there, but the environment variable >RSH is checked. Opinions on which approach is preferable? I use dump over ssh all the time. I just use a pipe as suggested by others here. I don't think your change is necessary. But if you absolutely *must* change dump to tightly integrate ssh, I really hope you use an explicit command line argument, not an environment variable. There are too many hidden magic environment variables already. Stephen. PS Once upon a time I used a command that took an input stream and wrote it to a set of tapes or floppies or whatever. If I still had that program you could use "ssh host dump ... | multivol /dev/nrsa0" and keep changing tapes to make it happy. That's more Unix-like, if that counts for anything. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001111308.XAA31980>