Re: document the actual meaning of ssh's "command" argument

On Thu, Jun 02, 2016 at 08:53:49AM +1000, Darren Tucker wrote: > > i'm inclined to disagree with this diff, for the following reasons: > > - other than the concatenation with spaces, it's not a behaviour of ssh(1) > but of the server at the other end of the connection, which might use sh -c > or

Re: document the actual meaning of ssh's "command" argument

On Wed, Jun 01, 2016 at 06:53:10PM +0100, Jason McIntyre wrote: > On Wed, Jun 01, 2016 at 10:04:20AM +0300, pizdel...@gmail.com wrote: > > After reading just the ssh(1) man page and the usage abstract, some poor > > soul may think that the "command" argument to ssh may be either a simple > >

document the actual meaning of ssh's "command" argument

After reading just the ssh(1) man page and the usage abstract, some poor soul may think that the "command" argument to ssh may be either a simple command or executable path that will be directly passed to execvp(). Even if he doesn't depend on any extra arguments being either used or ignored, he

Re: panic during boot of 5.7 in de(4) running in Hyper-V

On Tue, Jun 23, 2015 at 09:08:25PM -0600, Theo de Raadt wrote: -bcopy(sc-tulip_setupdata, sc-tulip_setupbuf, - sizeof(sc-tulip_setupbuf)); +bcopy(sc-tulip_setupdata, sc-tulip_setupbuf, TULIP_SETUP); +sc-tulip_setupbuf = dma_alloc(TULIP_SETUP, PR_WAITOK); +

Re: ffs and utf8

On Sat, Nov 29, 2014 at 09:48:53PM +0100, Dmitrij D. Czarkoff wrote: That said, the standard provides just enough facilities to make filesystem-related aspects of Unicode work nicely, particularily in case of utf-8. Eg. ability to enforce NFD for all operations on file names could actually

Re: OpenBSD 4.3 running in VirtualBox? Anyone have it working properly?

On Thu, Aug 07, 2008 at 05:43:23AM +0100, Tomas Bodzar wrote: 4.3 runs fine on many PCs in Qemu as I tested (Kubuntu,Mandriva,OpenSUSE,Windows).4.4 is Beta,so there may be problems. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jordi Beltran