Re: ssh support for notebooks :) --> screen?
On Mon, Jun 28, 2004 at 11:00:52PM +0200, Osamu Aoki wrote: > 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: > > > 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. The udebs are running in advance of renaming that will eventually happen to the normal packages too. > > > 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. Well, it shouldn't be much of a problem anyway. main-menu saves its state between menu items. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh support for notebooks :) --> screen?
Hi, 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 [EMAIL PROTECTED]:bar' is like > > '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. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh support for notebooks :) --> screen?
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. > Just nit pick. It is ssh+cat == scp. 'scp foo [EMAIL PROTECTED]:bar' is like > '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. > 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. :-) Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh support for notebooks :) --> screen?
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 '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]
Re: ssh support for notebooks :)
On Sun, Jun 27, 2004 at 10:41:36AM -0700, Joshua Kwan wrote: > On Sun, 27 Jun 2004 13:56:24 +0200, Osamu Aoki wrote: > > 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. > > You're right that it's not there, but I think Colin should roll a > putty-tools-udeb because those don't need to link against OpenSSL and are > thus easier to package for the initrd environment. Well, it would be possible, but I needed to do openssh-server-udeb anyway and it seemed logical to do the client at the same time. In order for openssh-server-udeb to work an OpenSSL .udeb needs to be created, which will also fulfil openssh-client-udeb's dependency. If there's consensus that putty-tools-udeb would be better then I can certainly scrap openssh-client-udeb (I don't want to duplicate .udebs needlessly), but given that libcrypto-udeb is necessary anyway I'm not sure I yet buy your argument above. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh support for notebooks :)
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. If we're going to have scp we should also have sftp; scp is badly designed, inextensible, and should eventually die. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh support for notebooks :)
On Sun, 27 Jun 2004 13:56:24 +0200, Osamu Aoki wrote: > 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. You're right that it's not there, but I think Colin should roll a putty-tools-udeb because those don't need to link against OpenSSL and are thus easier to package for the initrd environment. Yeah, and there currently isn't an ftp client inside either. -- Joshua Kwan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ssh support for notebooks :)
Hi, 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. I am wondering where should I file this wishlist. Osamu PS: Did I miss alternatives such as ftp-client? I did not see it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh support
On Tue, Jun 22, 2004 at 12:47:11PM +0200, Bastian Blank wrote: > - debootstrap needs to install ssh or something needs to forcible > install it via apt-install. The key and the installer user password > needs to be copied to the target and ssh should not build another key > which will result in another fingerprint. If we do this (which worries me, although I can see why you need it), the installer user must be deleted immediately upon completing base-config, and the templates in network-console must be changed to stop saying that the installer user will vanish after the first reboot. Still, it's concerning that an arbitrary number of packages might be installed before that point, or indeed that the person doing the installation might forget to finish base-config. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh support
On Sun, Jun 20, 2004 at 10:03:36PM +0200, Bastian Blank wrote: > What needs to be done: > - Installer-Item changes (anna/choose-mirror/net-retriever). Commited, needs uploads (anna pending). > - Testing (rootskel and network-console). - Proper implementation of di-utils-exit-installer (special exit code which asks main-menu to exit?) and support to exit from network logins. - debootstrap needs to install ssh or something needs to forcible install it via apt-install. The key and the installer user password needs to be copied to the target and ssh should not build another key which will result in another fingerprint. - base-config needs to run on the installer login, not on the console. Bastian -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day of the Dove", stardate unknown signature.asc Description: Digital signature
Re: ssh support
Quoting Colin Watson ([EMAIL PROTECTED]): > On Sun, Jun 20, 2004 at 10:03:36PM +0200, Bastian Blank wrote: > > - Templates for network-console. > > Done. I made a few rewrites for style consistency with the rest of d-i (very few needed). You (Bastian or Colin) took care of using the same formulation than shadow which is fine Shadow templates are like ly to change slightly in the future (removal of exclamation marks...or the "try again" formula which seems a bit unprofessional to me) So, I adapted these templates to what I think to be "better".which again, does not mean a lot of changes. The changes will be commited soon. I will announce this new package to translators. Seppy, be ready. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh support
On Sun, Jun 20, 2004 at 09:59:42PM +0100, Colin Watson wrote: > > and support for network logins. > Isn't that what network-console provides? It should be there to exit from the menu if logged in via network. Bastian -- Spock: The odds of surviving another attack are 13562190123 to 1, Captain. signature.asc Description: Digital signature
Re: ssh support
On Sun, Jun 20, 2004 at 10:03:36PM +0200, Bastian Blank wrote: > - Templates for network-console. Done. > and support for network logins. Isn't that what network-console provides? -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ssh support
Hi folks What needs to be done: - Templates for network-console. - Installer-Item changes (anna/choose-mirror/net-retriever). - Testing (rootskel and network-console). - Proper implementation of di-utils-exit-installer (special exit code which asks main-menu to exit?) and support for network logins. Bastian -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day of the Dove", stardate unknown signature.asc Description: Digital signature
ssh support
Some thinkings about ssh support: * Without possibility to go back in case of trouble: - generate config/keys - debconf: "stop" (needs to be implemented) - start sshd - display it's own message * With possibility to go back: - generate config/keys - debconf: close db files and mark db as readonly - start sshd - debconf: display message - if user ask to abort: - kill sshd - debconf: reopen db Bastian -- War isn't a good life, but it's life. -- Kirk, "A Private Little War", stardate 4211.8 signature.asc Description: Digital signature
