Thanks Elly.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
On 9/1/2012 4:01 PM, Mikie wrote:
>> This might sound really odd or insulting or completely unrelated, but you
>> could try remastering an already existing distro to learn about Linux in
>> addition to building LFS. For example, you can strip about 3/4 of the
>> packages from Ubuntu and it still
>This might sound really odd or insulting or completely unrelated, but you
>could try remastering an already existing distro to learn about Linux in
>addition to building LFS. For example, you can strip about 3/4 of the packages
>from Ubuntu and it still works, you simply have less functionality
On 9/1/2012 3:34 PM, Mikie wrote:
>
> I have said this before on this list and I'll say it again.
> LFS is a wonderful site for Linux experts who already know a lot of this
> stuff.
> Not so much for the rest of us.
> You say "Know the build system" ... how I say?
>
> LFS does not effectively teac
>I've noticed a flood of messages cause of your script. People build scripts
>when they know what is going on with their project. And they know how to
>troubleshoot it. It's hard to trouble shoot user scripts as there are many
>ways to build and have the same outcome. For instance, we have never
On Fri, Aug 31, 2012 at 07:43:22PM +, Mikie wrote:
> >A last thought : if you didn't build the correct disk drivers
> >into* the kernel (NOT as modules), that can also cause this sort of problem.
> > This is where the a Live CD can be useful: they build everything as
> >modules, using an init
On Aug 31, 2012, at 16:17 PM, Bruce Dubbs wrote:
> Mikie wrote:
>> I will redo once more (4th attemp ... only the 1st booted succesfuly)
>> and pay particular attention to kernel config ... devtmpfs.
>>
>> ... but I am using the same script I made with few changes:
>>
>> http://www.mikienet.com/l
Mikie wrote:
> I will redo once more (4th attemp ... only the 1st booted succesfuly)
> and pay particular attention to kernel config ... devtmpfs.
>
> ... but I am using the same script I made with few changes:
>
> http://www.mikienet.com/linux/lfs.htm
>
> So I don't know why this has started to ha
I will redo once more (4th attemp ... only the 1st booted succesfuly) and pay
particular attention to kernel config ... devtmpfs.
... but I am using the same script I made with few changes:
http://www.mikienet.com/linux/lfs.htm
So I don't know why this has started to happen.
Thanks.
--
http
On 8/31/2012 3:32 PM, Mikie wrote:
> Tried and Tried but could not stop the display during boot so ...
>
>
> I took a vid:
>
> http://www.mikienet.com/linux/VID_20120831_150531.3gp
>
> at 14 seconds it says:
>
> mount: unknown filesystem type 'devtmpfs'
> ln: failed to create symbolic link '/dev/sh
Mikie wrote:
> Tried and Tried but could not stop the display during boot so ...
> mount: unknown filesystem type 'devtmpfs'
Kernel configuration:
#
# Generic Driver Options
#
...
CONFIG_DEVTMPFS=y
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfro
Tried and Tried but could not stop the display during boot so ...
I took a vid:
http://www.mikienet.com/linux/VID_20120831_150531.3gp
at 14 seconds it says:
mount: unknown filesystem type 'devtmpfs'
ln: failed to create symbolic link '/dev/shm': Read Only file system
cp: cannot remove '/dev/nu
>A last thought : if you didn't build the correct disk drivers
>into* the kernel (NOT as modules), that can also cause this sort of problem.
>This is where the a Live CD can be useful: they build everything as modules,
>using an initrd, so 'lsmod' will tell you which modules were actually
>inst
On Fri, Aug 31, 2012 at 03:19:16PM +, Mikie wrote:
>
> CTRL s did not work but scroll lock did (go figure).
>
Thanks - _I've_ learned something ;)
> I see lots of " Read only file systems ... no such file or directory" for
> everything it trys to access.
>
>
> I see this on /dev/sro
>
On 08/31/2012 11:53 AM, Mikie wrote:
> Another thing I see is that when I boot to a live CD and run fdisk I tried to
> delete the 2nd partition (host system) to see if it was the issue.
> Last build of LFS I was able to boot no problem and I had deleted /dev/sda2
> at the end of chapter 9 ... but
Another thing I see is that when I boot to a live CD and run fdisk I tried to
delete the 2nd partition (host system) to see if it was the issue.
Last build of LFS I was able to boot no problem and I had deleted /dev/sda2 at
the end of chapter 9 ... but this time I didn't.
But back to what I was
>3. Try booting, and watch to see if you can spot the first error message from
>the bootscripts. When that appears, the old Ctrl-S (to stop the console
>scrolling) might work. If you can read the gist of the message, and what
>script it came from, you will be on the way towards sorting it out.
On Thu, Aug 30, 2012 at 11:30:30PM +, Mikie wrote:
> >It's possible you really do have filesystem errors, but that message might
> >be provoked by other errors. To begin with, you could try running fsck from
> >the host system on the LFS partition(s).
>
> I can boot a live CD and mount /dev
>It's possible you really do have filesystem errors, but that message might be
>provoked by other errors. To begin with, you could try running fsck from the
>host system on the LFS partition(s).
I can boot a live CD and mount /dev/sda1 (where I built LFS) with no problems.
--
http://linuxfroms
>Try editing /etc/sysconfig/rc.site and un-commenting
>#IPROMPT="yes" # Whether to display the interactive boot prompt
The book said rc.site was a optional file.
Anything that was optional I omited so I could stay with the basics.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ
Ken Moffat wrote:
> On Thu, Aug 30, 2012 at 07:05:29PM +, Mikie wrote:
>> Hello all,
>>
>> After completing the 7.1 book thru chapter 9 I reboot but get several fail
>> messages.
>>
>> The last one is fatal and refers to file system errors that must be fixed.
>>
>> The only option is to press
On Thu, Aug 30, 2012 at 07:05:29PM +, Mikie wrote:
> Hello all,
>
> After completing the 7.1 book thru chapter 9 I reboot but get several fail
> messages.
>
> The last one is fatal and refers to file system errors that must be fixed.
>
> The only option is to press enter and reboot.
>
> I
Hello all,
After completing the 7.1 book thru chapter 9 I reboot but get several fail
messages.
The last one is fatal and refers to file system errors that must be fixed.
The only option is to press enter and reboot.
I can't read the boot messages so I need to look thru the log file.
I can't
23 matches
Mail list logo