|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
Upgrading to new version 3.1.1I am running Bering 3.0 from a CF card on an IDE to CF adapter. It has
run flawlessly but I was interested in moving up to the latest rev. When I decided to update to the latest version I kept my syslinux.cfg file my leaf.cfg file my configdb.lrp file and my moddb.lrp file from my working 3.O system. I loaded a new CF with the new kernel and LRP files as well as the new *.SER files and the config files from my working system. Everything works but I can not log in remotely to the LEAF box using WinSCP. It connects originally but disconnects after the root password is entered. It could be a problem with WinSCP itself but I am able to log in to the router when the original 3.0 system is booted. My questions are. Should I be able use the *db.lrp flies from LEAF Bering 3.0 with the 3.1.1 version? Do I need to update modules? I use tulip and via-rhine nic modules with crc32, mii and the standard modules that come with the distribution package. What are the *.ser files for and how do they fit into the picture? They weren't in the original 3.0 system. Hopefully the answers will help me get my remote login back the router is running in an old electrical cabinet in the basement and is not easily accessible so the remote administration is a great help. Thanks for your help. It works but I use WinSCP to update my addon hosts file and would like to be able to continue to use it so I have reverted to my original 3.0 install. Ken ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@... https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ |
|
|
|
|
|
Re: Upgrading to new version 3.1.1Hi Ken,
> What are the *.ser files for and how do they fit into the picture? They > weren't in the original 3.0 system. They contain the config for setups that use a serial console - they were introduced with Bering uClibc 3.1 RC1 to make life easier for those of us who run Bering uClibc on a box without a video card (in such a case, simply rename syslinux.ser to syslinux.cfg, and configdb.ser to configdb.lrp and the default image will work on a box that has only a serial console). Martin ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@... https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ |
|
|
Re: Upgrading to new version 3.1.1Thank you for your response.
The problem was the protocol that WinSCP used when attempting to connect. The connection was refused when using SFTP but was successful when using SCP. Apparently the LEAF system wasn't set up to use SFTP and couldn't complete the connection. Thanks Ken Luis.F.Correia wrote: > Hi Ken, > >> -----Original Message----- >> From: Ken M [mailto:keno5@...] >> Sent: Wednesday, March 04, 2009 12:35 AM >> To: leaf-user@... >> Subject: [leaf-user] Upgrading to new version 3.1.1 >> >> I am running Bering 3.0 from a CF card on an IDE to CF >> adapter. It has run flawlessly but I was interested in >> moving up to the latest rev. >> >> >> When I decided to update to the latest version I kept my syslinux.cfg >> file my leaf.cfg file my configdb.lrp file and my moddb.lrp >> file from my >> working 3.O system. I loaded a new CF with the new kernel and LRP >> files as well as the new *.SER files and the config files from my >> working system. >> Everything works but I can not log in remotely to the LEAF box using >> WinSCP. It connects originally but disconnects after the root >> password >> is entered. It could be a problem with WinSCP itself but I am able to >> log in to the router when the original 3.0 system is booted. > > The problem is certainly a cached credential for root@your_system. > > With a new installation, a new SSH key is generated. > > Delete that key from where WinSCP keeps it, and you'll ne fine. > > Luis Correia > Bering uClibc team member > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.237 / Virus Database: 270.11.7/1983 - Release Date: 03/04/09 07:41:00 > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@... https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ |
|
|
Re: Upgrading to new version 3.1.1Thanks I assume then that I can safely remove these files from my boot
disk without causing problems. I only connect using the local console or via SSC or SCP from my local network. Thanks Ken Martin Hejl wrote: > Hi Ken, > >> What are the *.ser files for and how do they fit into the picture? They >> weren't in the original 3.0 system. > They contain the config for setups that use a serial console - they were > introduced with Bering uClibc 3.1 RC1 to make life easier for those of > us who run Bering uClibc on a box without a video card (in such a case, > simply rename syslinux.ser to syslinux.cfg, and configdb.ser to > configdb.lrp and the default image will work on a box that has only a > serial console). > > Martin > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > ------------------------------------------------------------------------ > leaf-user mailing list: leaf-user@... > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.237 / Virus Database: 270.11.7/1983 - Release Date: 03/04/09 07:41:00 > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@... https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ |
| Free embeddable forum powered by Nabble | Forum Help |