Re: ssh support for notebooks :) --> screen?
On Mon, Jun 28, 2004 at 01:07:21AM +0100, Colin Watson wrote:
> On Mon, Jun 28, 2004 at 01:25:21AM +0200, Osamu Aoki wrote:
> > On Sun, Jun 27, 2004 at 08:21:18PM +0100, Colin Watson wrote:
> > > openssh-client-udeb. I didn't package scp because it's straightforward
> > > to do the same thing with ssh and tar, but I suppose I could add it.
> > openssh-client-udeb is sufficient for me. I only meant some SCP like
> > functionality. I really doubt needs to login to another machine from a
> > machine running on initrd. So really stripped down ssh shall be enough
> > (no X forwarding etc.)
> Sure, although some people (e.g. me :-)) do like to be able to log into
> other machines from the middle of a d-i install. You can use that
> facility to ask for help, for instance.
That is a very good point. There is no man nor info on d-i process.
Hmmm... How come I missed it. I guess I was only looking for
ssh-client-udeb. It did not hit me to look under "o". Thanks.
> > Just nit pick. It is ssh+cat == scp. 'scp foo name@host:bar' is like
> > '<foo ssh name@host "cat - >bar"'. "tar" is a sepatete issue although
> > it is an idiom used with ssh to move multiple files. (These files will
> > not be concatenated if moved with ssh+tar in the famous way.)
> I beg to differ. scp preserves file modes, for instance, unlike ssh+cat.
You got me.
I should have said, for my requirements, I can do file transfer simply by
ssh+cat. Use of tar looked overkill to me but tar and cat are already
parts of busybox. No difference in binary size.
> > By the way, speaking of basic functionality of initrd, I do not see
> > "screen" command missing in initrd nor in pool/* as udeb. I wonder how
> > you are handling some operations which kill the remote terminal
> > connection used for the install.
> We don't perform such operations. :-)
I do not have Big IBM here either. But someday when I want to boot
broken LCD old notebook PC, I may need it.