WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: artificial intelligence; automatic HW identification and driver download  (Read 979 times)

Offline xor

  • Hero Member
  • *****
  • Posts: 728
Re: artificial intelligence; automatic HW identification and driver download
« Reply #30 on: October 02, 2020, 11:16:35 PM »
I wrote the previous comment a little hurriedly.
Google Translate ; again misinterpreted long sentences! but the main idea is clear!
hardware can be variable.
however, each of them has a fixed and unchangeable id id.
No driver is required to read hardware IDs.
if you fully understand what I am trying to explain here.
Without adding garbage files that will never be used in the system,
a smaller, more minimalist linux distribution might emerge.
also, the end user will not need to search for drivers.
especially new users.
« Last Edit: October 02, 2020, 11:25:36 PM by xor »

Offline ladnar

  • Newbie
  • *
  • Posts: 45
Re: artificial intelligence; automatic HW identification and driver download
« Reply #31 on: October 03, 2020, 10:52:26 PM »
Quote
Seeing "chmod 777" raises alarm bells to me!!

Oh yeah. Don't do that. ( I knew this, but not how fatal it is).

https://superuser.com/questions/300743/sudo-chmod-r-777

I think I am OK because I didn't use the -r , recursive, function (I read something once about sticky bits "bricking" a raspeberyy pi; I hope I didn't do that?). But I will change my code. Why did I do it in the first place? I think the piCore wouldn't let me mkdir in root? Maybe I'll just change the U to 7 and leave the G and O alone?

(People out there, reading this; listen to Greg and others. Not me. Unless I said something smart about biology or philosophy or the history of science. Then listen to me.)

*Edit* Maybe,  $ chmod 7GO , and then, at the end of the script, $ chmod UGO ; where UGO are the original settings for root on a picore OS. Yeah, that's much better.
« Last Edit: October 03, 2020, 11:03:52 PM by ladnar »