modprobe problem

2009-01-05 Thread dennisjperkins
I have finished building another LFS system and I have a problem I have never encountered before. I can't load modules. Whenever I try, I get this message: MODTEST_OVERRIDE used but MODTEST_UNAME not set. Does anyone have any idea what is causing this? -- http://linuxfromscratch.org/mailman/l

Re: jhalfs issue with permissions

2009-01-05 Thread Trent Shea
On January 5, 2009 07:38:15 pm Ralph Porter wrote: >  Building target 029-gcc-pass1 >  [+|du: cannot read directory `/mnt/lfs/.Trash-root': Permission denied1 > sec du: cannot read directory `/mnt/lfs/.Trash-rporter': Permission denied > > FROM HERE IT JUST SPINS AT THE PROMPT > > i have to ctrl-c

Re: jhalfs issue with permissions

2009-01-05 Thread Ralph Porter
On Mon, Jan 5, 2009 at 6:50 PM, DJ Lucas wrote: > Ralph Porter wrote: > >> Building target 028-binutils-pass1 >> [/du: cannot read directory `/mnt/lfs/.Trash-root': Permission denied 0 sec >> du: cannot read directory `/mnt/lfs/.Trash-rporter': Permission denied >> >> > > Wait, it actually start

Re: jhalfs issue with permissions

2009-01-05 Thread DJ Lucas
Ralph Porter wrote: > Building target 028-binutils-pass1 > [/du: cannot read directory `/mnt/lfs/.Trash-root': Permission denied 0 sec > du: cannot read directory `/mnt/lfs/.Trash-rporter': Permission denied > > Wait, it actually started the build! I missed that part yesterday. What exactly

jhalfs issue with permissions

2009-01-05 Thread Wolfgang Messingschlager
Ralph Porter wrote: > On Sun, Jan 4, 2009 at 10:02 PM, DJ Lucas wrote: >> Ralph Porter wrote: >> >>> mk_LUSER >>> You are going to log into the user account lfs >>> sudo requires a password >>> Password: >>> Sorry, try again. >> Since you didn't explicitly say it, we'll go for the obvious first.

Re: jhalfs issue with permissions

2009-01-05 Thread Ralph Porter
On Sun, Jan 4, 2009 at 10:02 PM, DJ Lucas wrote: > Ralph Porter wrote: > >> mk_LUSER >> You are going to log into the user account lfs >> sudo requires a password >> Password: >> Sorry, try again. > > Since you didn't explicitly say it, we'll go for the obvious first. Did > you add rporter to /et