I think it's important to point out that what the original document author meant by the third set of instructions was simply "run these commands verbatim in terminal"; admittedly it would have been clearer to have stated this explicitly. This is an explanation of what each command does, one by one:
Code: Select all
sudo b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o
Runs the b43 firmware extractor with root privileges, telling it to put the firm
ware in /lib/firmware, from the wl_apsta-3.130.20.0.o driver in the present working directory.
Code: Select all
tar xfvj broadcom-wl-4.80.53.0.tar.bz2
Runs tar, an archiving utility, telling it to e
xtract from the
file broadcom-wl-4.80.53.0.tar.bz2 in the present working directory,
verbosely listing all the files it extracts, and filtering the archive through bzip2 (another archiving utility with a better compression ratio) (that's the
j switch, btw). Since no target is specified, the archive is extracted, retaining the file hierarchy in the archive, into the present working directory. It doesn't really matter where, and optionally the archive and the extracted files could be trashed after the next job's done.
Code: Select all
sudo b43-fwcutter --unsupported -w /lib/firmware broadcom-wl-4.80.53.0/kmod/wl_apsta_mimo.o
Again, runs the b43-fwcutter program with root privileges, telling it to put the
unsupported (i.e. Windows (?)) firm
ware in /lib/firmware/, extracting from the wl_apsta_mimo.o file found in the kmod directory of the broadcom-wl-4.80.53.0.
Which should get your firmware sorted without need for nautilus. Also, you don't need to be root to
change present working
directory to /lib/firmware, normal users can read that directory, just not write to it.
Your method works fine, since all the b43-fwcutter specify the target path explicitly, so nothing's really changed except the path you were working from.
If you're new to working with terminal stick with it, the shell if fantastically powerful and over time you'll get accustomed to it. I'm pretty sure that someone on these forums put up a (longish) list of commands with short explanations but I can't seem to find it, otherwise there's a bunch of useful links on this
post. You can also hit tab twice in a row in terminal to have it show you all two thousand + possibilities, but I wouldn't necessarily advise that
My approach has always been to check the man page for whatever command it is if I'm not sure about what it does:
would bring up foo's man(ual) page, if foo existed. Some find man pages too dry and condensed but they're good as a reference. See this useful
post.