On Sun, Jun 27, 2004 at 08:21:18PM +0100, Colin Watson wrote: > On Sun, Jun 27, 2004 at 01:56:24PM +0200, Osamu Aoki wrote: > > I am wondering if ssh can be supported for normal d-i initrd too. > > > > Most importantly, scp. > > > > This is because many new PC comes without floppy to save failed install > > except to USB or HDD. SCP makes it easy to copy the log. This should > > make failed install easier to debug as long as network is alive. > > > > At lease inclusion of some ssh package to the pool/* will be nice for > > netinst CD. > > 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.) Just nit pick. It is ssh+cat == scp. 'scp foo [EMAIL PROTECTED]:bar' is like '<foo ssh [EMAIL PROTECTED] "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.) > If we're going to have scp we should also have sftp; scp is badly > designed, inextensible, and should eventually die. True. Code choice for udeb should be minimalistic. 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. It will interrupt install process unless "screen" like commands are used. Just an innocent question without much thought. So excuse me if I am asking some obvious. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
