Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #244163

Please take this as constructive

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Every time that I search for solutions to my wifi drivers, the solution is
to apt-get install a bunch of drivers. Why does nobody realize that apt'ing
anything is a non-solution: How can I apt-get install <network drivers> if
I don't have network drivers? There are DOZENS of responses to questions
about network drivers that say to apt-get install various packages without
any thought to the fact that nobody can apt without first having network
drivers. It's seriously starting to **** me off. I've got computers with
Broadcom wifi. How the heck am I going to fix that by using networking to
download the gosh darn drivers to fix the networking that I don't have? Of
the dozens of "solutions" that I've read about this, NOBODY ever thinks
about how to fix the network driver without having a network driver.

Do I know how to use sneakernet? Yes. In my young adulthood, email was
dialing into a BBS that would then dial the next closest free telephone
call to another BBS, and so forth until your message from California got to
the East Coast. Days. I remember trucks with huge spools of
punch-cards that were data for the mainframe.

When I try to use sneakernet to overcome the networking issues then I get
errors from dpkg that it can't install debs because ldconfig and
start-stop-daemon aren't available. I haven't bothered searching for the
debs that provide those things because I cannot use a deb to fix dpkg
because dpkg doesn't function.

The catch-22's are endless. In my case, I need Broadcom drivers. I can't
get b43 over the network. I can't use sneakernet for b43 debs because dpkg
doesn't work (let alone finding all the dependencies and dependencies of
dependencies and so forth).

Now what?

-- 

*R. Toby Richards*

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Please take this as constructive "R. Toby  Richards" <tobias.richards@gmail.com> - 2022-01-18 07:50 +0100
  Re: Please take this as constructive john doe <johndoe65534@mail.com> - 2022-01-18 08:00 +0100
  Re: Please take this as constructive The Wanderer <wanderer@fastmail.fm> - 2022-01-18 12:10 +0100
  Re: Please take this as constructive "Andrew M.A. Cater" <amacater@einval.com> - 2022-01-18 14:00 +0100
  Re: Please take this as constructive Loïc Grenié <loic.grenie@gmail.com> - 2022-01-18 14:40 +0100
    Re: Please take this as constructive Brian <ad44@cityscape.co.uk> - 2022-01-18 14:50 +0100
      Re: Please take this as constructive Celejar <celejar@gmail.com> - 2022-01-18 18:00 +0100
        Re: Please take this as constructive Brian <ad44@cityscape.co.uk> - 2022-01-18 19:00 +0100
          Re: Please take this as constructive The Wanderer <wanderer@fastmail.fm> - 2022-01-19 04:10 +0100
            Re: Please take this as constructive Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-21 18:30 +0100
  Re: Please take this as constructive Stefan Monnier <monnier@iro.umontreal.ca> - 2022-01-18 15:00 +0100
    Re: Please take this as constructive Anssi Saari <as@sci.fi> - 2022-01-19 11:10 +0100
      Re: Please take this as constructive Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-01-21 18:50 +0100
  Re: Please take this as constructive Polyna-Maude Racicot-Summerside <debian@polynamaude.com> - 2022-01-18 15:10 +0100

csiph-web