|
osdir.com mailing list archive |
|
Subject: Re: Read-only root-filesystem - msg#00014List: network.ssh.dropbearThis was solved when i added "--disable-openpty" in the configuration. Thanx - Prasad On 3/23/06, DeviPrasad Natesan <ndprasad@xxxxxxxxx> wrote: > Hi all, > Does the dropbear-ssh needs writable root-filesystem to run correctly. > I set my file-system as read-only (which i ultimately wants to) and it > fails giving the following error. > > ==================== > TRACE: continue recv_msg_channel_request: session request > TRACE: enter chansessionrequest > TRACE: type is shell > TRACE: enter sessioncommand > TRACE: enter ptycommand > [147] Mar 23 04:51:57 no pty was allocated, couldn't execute > ======================== > > It works ok when i change the root-filesystem as the read-write. > Apparently due to the /dev/pty* ?. > > I am running the default dropbear found in the uClinux-dist > distribution with my microblaze as the processor. Please let me know > how i can run the dropbear with the read-only root file system. > > Appreciate your reply. > > Thnx > - Prasad > Thread at a glance:
Previous Message by Date: click to view message previewRead-only root-filesystemHi all, Does the dropbear-ssh needs writable root-filesystem to run correctly. I set my file-system as read-only (which i ultimately wants to) and it fails giving the following error. ==================== TRACE: continue recv_msg_channel_request: session request TRACE: enter chansessionrequest TRACE: type is shell TRACE: enter sessioncommand TRACE: enter ptycommand [147] Mar 23 04:51:57 no pty was allocated, couldn't execute ======================== It works ok when i change the root-filesystem as the read-write. Apparently due to the /dev/pty* ?. I am running the default dropbear found in the uClinux-dist distribution with my microblaze as the processor. Please let me know how i can run the dropbear with the read-only root file system. Appreciate your reply. Thnx - Prasad Next Message by Date: click to view message previewRe: Read-only root-filesystemMessage: 3 Date: Thu, 23 Mar 2006 16:14:19 -0800 From: "DeviPrasad Natesan" <ndprasad@xxxxxxxxx> Subject: Re: Read-only root-filesystem To: dropbear@xxxxxxxxxx Message-ID: <3351bfbe0603231614r2ba1d199jb68a286b4f653af1@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 Hi, This was solved when i added "--disable-openpty" in the configuration. ---------------------------------- You can also use devfs (if you have kernel 2.4) or tmpfs to create /dev. Create the necessary devices in your init scripts. --Yan Previous Message by Thread: click to view message previewRead-only root-filesystemHi all, Does the dropbear-ssh needs writable root-filesystem to run correctly. I set my file-system as read-only (which i ultimately wants to) and it fails giving the following error. ==================== TRACE: continue recv_msg_channel_request: session request TRACE: enter chansessionrequest TRACE: type is shell TRACE: enter sessioncommand TRACE: enter ptycommand [147] Mar 23 04:51:57 no pty was allocated, couldn't execute ======================== It works ok when i change the root-filesystem as the read-write. Apparently due to the /dev/pty* ?. I am running the default dropbear found in the uClinux-dist distribution with my microblaze as the processor. Please let me know how i can run the dropbear with the read-only root file system. Appreciate your reply. Thnx - Prasad Next Message by Thread: click to view message previewRe: Read-only root-filesystemMessage: 3 Date: Thu, 23 Mar 2006 16:14:19 -0800 From: "DeviPrasad Natesan" <ndprasad@xxxxxxxxx> Subject: Re: Read-only root-filesystem To: dropbear@xxxxxxxxxx Message-ID: <3351bfbe0603231614r2ba1d199jb68a286b4f653af1@xxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 Hi, This was solved when i added "--disable-openpty" in the configuration. ---------------------------------- You can also use devfs (if you have kernel 2.4) or tmpfs to create /dev. Create the necessary devices in your init scripts. --Yan Loading Comments...
|
|
