Re: BusyBox built-in shell (ash)

2017-12-13 Thread Didier Kryn
Le 13/12/2017 à 00:56, Mattias Schlenker a écrit : Am 13.12.2017 um 00:28 schrieb A.W.C.: Hi, yes, I know that Squashfs is read-only filesystem. Tried again, not sure what need be changed here for this specific configuration and filesystems available. # mknod -m 666 /dev/null c 1 3 mknod:

Re: BusyBox built-in shell (ash)

2017-12-12 Thread Michael Conrad
On 12/12/2017 6:28 PM, A.W.C. wrote: yes, I know that Squashfs is read-only filesystem. Tried again, not sure what need be changed here for this specific configuration and filesystems available. # mknod -m 666 /dev/null c 1 3 mknod: /dev/null: Read-only file system You say you understand

Re: BusyBox built-in shell (ash)

2017-12-12 Thread Mattias Schlenker
Am 13.12.2017 um 00:28 schrieb A.W.C.: Hi, yes, I know that Squashfs is read-only filesystem. Tried again, not sure what need be changed here for this specific configuration and filesystems available. # mknod -m 666 /dev/null c 1 3 mknod: /dev/null: Read-only file system # mknod -m 666

Re: BusyBox built-in shell (ash)

2017-12-12 Thread A.W.C.
mnt/ failed: No such file or directory > # mknod -m 644 /dev/mtd10      c 90 20 > mknod: /dev/mtd10: Read-only file system > > One day I sucessfully managed mount mtd9 nvram partition (jffs2), but next > time I can't mount anymore, all time system is 'Read-only file system' for

Re: BusyBox built-in shell (ash)

2017-12-12 Thread Tito
mount mtd9 nvram partition (jffs2), but next time I can't mount anymore, all time system is 'Read-only file system' for any partition. Regards, Aex On Mon, 12/4/17, Mattias Schlenker <m...@mattiasschlenker.de> wrote: Subject: Re: BusyBox bu

Re: BusyBox built-in shell (ash)

2017-12-12 Thread A.W.C.
(jffs2), but next time I can't mount anymore, all time system is 'Read-only file system' for any partition. Regards, Aex On Mon, 12/4/17, Mattias Schlenker <m...@mattiasschlenker.de> wrote: Subject: Re: BusyBox built-in shell (ash) To: busybox

Re: BusyBox built-in shell (ash)

2017-12-03 Thread Mattias Schlenker
Am 04.12.2017 um 00:09 schrieb A.W.C.: Hi Baruch, what I want ismanually mount the root file system from busybox rescue shell. To make some changes, umount and exit from shell.  Linux v 2.6.26.5, rootfstype=squashfs, root filesystem is on mtd4, NAND flash, jffs2. # mount -t proc none

Re: BusyBox built-in shell (ash)

2017-12-03 Thread A.W.C.
Hi Baruch, what I want is manually mount the root file system from busybox rescue shell. To make some changes, umount and exit from shell.  Linux v 2.6.26.5, rootfstype=squashfs, root filesystem is on mtd4, NAND flash, jffs2. BusyBox v1.10.2 (2017-08-02 14:07:25 CST) built-in shell (ash) Enter

Re: BusyBox built-in shell (ash)

2017-12-02 Thread Baruch Siach
Hi Alex, On Fri, Dec 01, 2017 at 03:17:39PM +, A.W.C. wrote: > But I already have directories /dev, /proc, /sys, /tmp > If I'll make these new dir for TinyCross they will replace existing ones? > > mkdir -p /proc > mkdir -p /sys > mkdir -p /tmp > mkdir -p /var/log > > Basically, I want

Re: BusyBox built-in shell (ash)

2017-12-01 Thread Tito
properly? Command 'exit' produces Kernel panic. Regards, Alex On Fri, 12/1/17, Mattias Schlenker <m...@mattiasschlenker.de> wrote: Subject: Re: BusyBox built-in shell (ash) To: busybox@busybox.net Date: Friday, December 1, 2017, 4:21 PM

Re: BusyBox built-in shell (ash)

2017-12-01 Thread A.W.C.
, Mattias Schlenker <m...@mattiasschlenker.de> wrote: Subject: Re: BusyBox built-in shell (ash) To: busybox@busybox.net Date: Friday, December 1, 2017, 4:21 PM Am 01.12.2017 um 10:38 schrieb tiggersWelt.net (Support): >  This should work whenever /dev is mounted. > Matthias [0]

Re: BusyBox built-in shell (ash)

2017-12-01 Thread tiggersWelt.net (Support)
Am 01.12.2017 um 15:21 schrieb Mattias Schlenker: [...] >> >> >> Everything you need is written down there and is not busybox-related, >> but how to build a linux from scratch (maybe the LFS-Project would be a >> good

Re: BusyBox built-in shell (ash)

2017-12-01 Thread Mattias Schlenker
Am 01.12.2017 um 10:38 schrieb tiggersWelt.net (Support):  This should work whenever /dev is mounted. Matthias [0] already gave you the advice to look at other rc-scripts how they are doing this kind of stuff, like his own scripts:

Re: BusyBox built-in shell (ash)

2017-12-01 Thread tiggersWelt.net (Support)
Am 30.11.2017 um 23:40 schrieb A.W.C.: > # mount -t dev dev /dev > mount: mounting dev on /dev failed: No such device The fstype you are looking for is "devtmpfs" not "dev": mount -t devtmpfs devtmpfs /dev fstype-names aren't very plausible at this point, but all of them has gone through some

Re: BusyBox built-in shell (ash)

2017-11-30 Thread tiggersWelt.net (Support)
Am 30.11.2017 um 14:59 schrieb A.W.C.: > But 'mount' command not available too: > > # mount > mount: no /proc/mounts That's not true. Mount is just unable to list current mounts because proc is not available. Just try # mount -t proc proc /proc # mount -- \\\||/// \\ - - // (

Re: BusyBox built-in shell (ash)

2017-11-30 Thread A.W.C.
wrote: Subject: Re: BusyBox built-in shell (ash) To: busybox@busybox.net Date: Thursday, November 30, 2017, 3:33 PM Am 30.11.2017 um 14:13 schrieb A.W.C.: > Hello, > > Linux embedded file system (Linux v. 2.6.26.5) running on raw NAND flash, and use Full Image's RootFS. >

Re: BusyBox built-in shell (ash)

2017-11-30 Thread Mattias Schlenker
Am 30.11.2017 um 14:13 schrieb A.W.C.: Hello, Linux embedded file system (Linux v. 2.6.26.5) running on raw NAND flash, and use Full Image's RootFS. I need to access to linux shell when Linux kernel is fully loaded U-Boot> setenv bootargs console=ttyS1,115200n8 rootfstype=squashfs noalign

BusyBox built-in shell (ash)

2017-11-30 Thread A.W.C.
Hello, Linux embedded file system (Linux v. 2.6.26.5) running on raw NAND flash, and use Full Image's RootFS. I need to access to linux shell when Linux kernel is fully loaded U-Boot> setenv bootargs console=ttyS1,115200n8 rootfstype=squashfs noalign half_image=0 verify=y single init=/bin/sh