Em qui., 14 de jan. de 2021 às 03:19, Bruce Dubbs via lfs-dev <lfs-dev@lists.linuxfromscratch.org> escreveu: > > On 1/13/21 11:45 PM, Jamenson Espindula via lfs-dev wrote: > > Em qua., 13 de jan. de 2021 às 12:47, Pierre Labastie via lfs-dev > > <lfs-dev@lists.linuxfromscratch.org> escreveu: > >> > >> On Wed, 2021-01-13 at 10:05 -0300, Jamenson Espindula via lfs-dev > >> wrote: > > >> Looks like you haven't send the whole story. You should have seen > >> something like: > >> Mounting virtual file systems: /run /proc /sys /dev > >> > >> + maybe an error message before "FAILURE ..." > >> > >> The mail subject tells "read-only file system failure", but there is no > >> evidence in the error message you sent us... > > > > > > Thank you for your response. In fact, there are other error messages. > > I am sorry. > > > > = = = = = Begin of transcription = = = = = > > > > chmod: cannot access '/run/lock': No such file or directory > > Lets start here. That is the very 1st boot script. It is doing: > > mount /run > mkdir -p /run/lock /run/shm > chmod 1777 /run/shm /run/lock > > And failing. > ----- > > What we need is to see your file system. What is the output of > 'ls /' (or 'ls /mnt/lfs' from the host). It should be. >
< ls -l /mnt/lfs/ >: total 512112 drwxr-xr-x 2 root root 4096 jan 11 01:47 bin drwxr-xr-x 2 root root 4096 jan 13 13:17 boot drwxr-xr-x 2 root root 4096 jan 8 01:55 dev drwxr-xr-x 13 root root 4096 jan 14 07:54 etc drwxr-xr-x 3 root root 4096 jan 12 01:07 home drwxr-xr-x 6 root root 4096 jan 11 04:11 lib drwxr-xr-x 2 root root 4096 jan 7 01:19 lib64 drwx------ 2 root root 16384 jan 6 23:48 lost+found drwxr-xr-x 6 root root 4096 jan 11 02:51 media drwxr-xr-x 4 root root 4096 jan 11 02:48 mnt drwxr-xr-x 2 root root 4096 jan 8 02:02 opt drwxr-xr-x 2 root root 4096 jan 8 01:55 proc drwxr-x--- 4 root root 4096 jan 14 07:51 root drwxr-xr-x 4 root root 4096 jan 13 13:18 run drwxr-xr-x 2 root root 4096 jan 14 07:04 sbin drwxr-xr-x 3 root root 4096 jan 12 04:48 sources drwxr-xr-x 2 root root 4096 jan 8 02:02 srv -rw------- 1 root root 524288000 jan 11 04:41 swapfile drwxr-xr-x 2 root root 4096 jan 8 01:55 sys drwxrwxrwt 2 root root 20480 jan 14 07:03 tmp drwxr-xr-x 11 root root 4096 jan 11 01:52 usr drwxr-xr-x 10 root root 4096 jan 8 02:03 var > > Second don't just say the /etc/fstab is right. Paste it in. It should < cat /mnt/lfs/etc/fstab >: # Begin /etc/fstab # file system mount-point type options dump fsck order /dev/sda2 / ext4 defaults 1 1 /swapfile none swap sw 0 0 proc /proc proc nosuid,noexec,nodev 0 0 sysfs /sys sysfs nosuid,noexec,nodev 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /run tmpfs defaults 0 0 devtmpfs /dev devtmpfs mode=0755,nosuid 0 0 # End /etc/fstab > > The last five lines should be identical to what you have. If /run is > correctly mounted as a tmpfs, then the next two lines should not fail. > > -- Bruce > > -- > http://lists.linuxfromscratch.org/listinfo/lfs-dev > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page To re-emphasize: I _solved_ the problem. How: creating a configuration file from scratch (make config); answering all the questions accepting the suggested default answers. After that, I have invoked (make menuconfig) and adjusted some hardware configurations. Compiling and installing the kernel just builded. Unfortunately, I accidentally erased the old configuration file. So, I can not tell exactly where the misconfiguration was. But, I have no doubt: the problem was raised by a kernel misconfiguration. I made a mistake. Respectful Jamenson Espindula -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
