Re: [lfs-support] Using wpa_supplicant [Was: ifup--a really uninformed question]
Dan McGhee wrote:
On 11/02/2013 02:50 PM, Bruce Dubbs wrote:
Dan McGhee wrote:
(Received complaints about /run/var/bootlog all through the process.
They were right, it doesn't exist yet.)
Do you have /run/var?
I just discovered. No I don't. Nor do I have /run/lock. I looked in the
book Sections 6.5 and 6.6 to see where and how I missed these. I didn't
see their creation in either section. Would you please tell me where in
the book they get created? I've got to see if I missed anything else.
/etc/init.d/mountvirtfs
When I create them, just to double check, make sure the permissions are
0755?
Only /run/shm needs the permissions changed.
/run is mounted form fstab
tmpfs/run tmpfs defaults 0 0
in the very first boot boot script (mountvirtfs):
# Make sure /run/var is available before logging any messages
if ! mountpoint /run /dev/null; then
mount /run || failed=1
fi
mkdir -p /run/var /run/lock /run/shm
...
The scripts all use so the only reason that you would get this error
is iv /run is not mounted. Actually, even then the writing would be to
a standard directory so the issue would be permissions. These scripts
need to be run as root.
That's great info. Thanks. Referencing the paragraph above, the
directories /run/{var,lock} get created the first time the system boots?
I do have /run/shm. It got created in Section 6.2.
Since I'm operating in chroot, I need to mount /run. Again, to double
check, is the following command the one to use?
mount -v -t tmpfs tmpfs /run
That would probably work.
If the bootscripts are exiting, then it's no wonder that my efforts are
failing. I consider this one of the simple things that I miss. My
knowledge of the bootscripts is slowly coming back. I knew them well six
years ago. :)
The bootscripts were completely rewritten for LFS 7.0. That's why we
are at 7.x and not 6.x.
Before I forget. Once I get the directory thing straightened out, should
I, as root, touch /run/var/bootlog?
That wouldn't be needed if /ver/run has been created, but I don't
understand running the bootscripts in chroot. Why are you trying to do
that?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Using wpa_supplicant [Was: ifup--a really uninformed question]
On 11/03/2013 11:14 AM, Bruce Dubbs wrote: If the bootscripts are exiting, then it's no wonder that my efforts are failing. I consider this one of the simple things that I miss. My knowledge of the bootscripts is slowly coming back. I knew them well six years ago. :) The bootscripts were completely rewritten for LFS 7.0. That's why we are at 7.x and not 6.x. I had noticed some big differences from what I was used to. My last complete LFS build was 6.7. I was going to ask later, but you just let me know. Thanks. Before I forget. Once I get the directory thing straightened out, should I, as root, touch /run/var/bootlog? That wouldn't be needed if /ver/run has been created, but I don't understand running the bootscripts in chroot. Why are you trying to do that? -- Bruce The original situation got lost in the responses to a passing comment I made when I originally posted. The comment was that 'ifup' complained that /run/var/bootlog didn't exist. I want to build up through Xorg in chroot. I've done it before, but I used the host system to down load packages and patches and read the book. I thought that if I could get my wifi working in chroot then I could do what I wanted to and could download packages directly to the LFS tree without having to go through the host system to do that. Just an idea to make it easier for me. I posted in LFS because I didn't know if this was possible in chroot and knew that someone would tell me if it weren't. The problem I'm having is a BLFS one in that I've not configured either dhcpcd or wpa_supplicant correctly. I'm learning that it might be an Ubuntu phenomenon. Short version with no more info is that my card wlan0 authenticates and, then, immediately de-authenticates. I'm still trying to troubleshoot and learn. But.with the info about the bootscripts, I got rid of the error messages in chroot. Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
