A cikin Rasberi, idan baku yi amfani da zane-zane ba, zai zama abin damuwa don hawa ƙwaƙwalwar USB ɗinmu akai-akai. Hakanan, yayin aiwatar da aikin wannan aiki na atomatik (wanda shine abin da na nuna a ƙasa) zaku iya koya ɗan kaɗan game da yadda Linux ke sarrafa na'urori.
Shigar da motoci da kuma udev
Abu na farko da zamuyi shine girka autos y udev
sudo dace-samun shigar autofs udev
udev kayan kernel ne na Linux wanda ke lura da sarrafa kundin adireshin / dev wanda anan ne dukkan na'urorin suke. Kuma motocin suna ba mu damar, da zarar mun daidaita su, duk hawa da cire su kai tsaye da zarar an haɗa keɓaɓɓiyar ko an cire haɗin.
Abu na farko da zamuyi shine haɗa ƙwaƙwalwar ajiyar mu (zan yi amfani da alamar Kingston) a cikin kwamfutar mu / Raspberry Pi. Sannan muna aiwatarwa:
sudo fdisk -l
zai sami fitarwa kwatankwacin wannan:
Disk / dev / mmcblk0: 15.7 GB ... Boot Na'urar Fara Kashe Katange Id System / dev / mmcblk0p1 2048 1607421 802687 e W95 FAT16 (LBA) / dev / mmcblk0p2 1613824 30613503 14499840 85 Linux tsawaita / dev / mmcblk0p3 30613504 Dis .. Disk / dev / sda: 30679039 GB ... Boot Na'ura Fara Karshen Tubalan Id System / dev / sda32768 83 30.9 1 c W2048 FAT60436479 (LBA)
Memory usb na waje yana da 30.9 GB (watau shi ne / dev / sda1) yayin da memarin SD ɗin da nake inda Linux ya girka yana da 15.7 GB.
Dokokin al'ada a cikin udev
Sanin cewa sda1 na'urar mu ce, zamuyi amfani da udev don cire bayanai daga ƙwaƙwalwar ajiya, don haka muke aiwatar da wannan umarnin:
udevadm info -a -p $ (udevadm info -q hanyar -n / dev / sda1)
za a sami bulolin da aka raba ta kalmar "kallon na'urar mahaifa '/ na'urorin / ... .."
don sauƙaƙa binciken zamu iya amfani da man shafawa, don haka zanyi haka:
udevadm info -a -p $ (udevadm info -q hanya -n / dev / sda1) | man shafawa
A cikin akwati na kamar yadda ƙwaƙwalwata ta kasance Kingston fitarwa ita ce:
ATTRS {manufacturer} == "Kingston" # 1 ATTRS {manufacturer} == "Linux 3.12.28+ dwc_otg_hcd"
ko kuma za mu iya bincika:
udevadm info -a -p $ (udevadm info -q hanya -n / dev / sda1) | samfurin grep udevadm info -a -p $ (udevadm info -q hanyar -n / dev / sdd1) | mai siyarwa
Ina sha'awar:
ATTRS {mai sana'a} == "Kingston"
Kamar yadda farkon haɗuwa ta kasance. A cikin fitowar umarnin udevadm Ina neman toshe inda ya fara bayyana "ATTRS {manufacturer}"
Na ɗauki wasu bayanai waɗanda na ɗauka na musamman ne daga na'urar toshe, a halin da nake ciki:
ATTRS {samfurin} == "xxx" ATTRS {serial} == "xxxx" Direbobi == "kebul"
kawai kuna buƙatar ƙirƙirar dokoki. Muna yin fayil ɗin da ya ƙare a cikin .rules a cikin udev:
sudo nano /etc/udev/rules.d/personal.rules
a cikin fayil din da muka sa
ATTRS {product} == "xxx", ATTRS {serial} == "xxx", Direbobi == "usb", SYMLINK + = "miusb"
Yanzu idan na haɗa kebul na za a sami fayil / dev / miusb. Wannan shi ne mafi wuya.
Kafa abubuwan hawa
Muna aiwatarwa:
sudo nano / sauransu / tsoho / autofs
inda aka rubuta "TIMEOUT =" sun saka "TIMEOUT = 1"
Bari mu je zuwa /etc/auto.master
nano /etc/auto.master
kuma a cikin fayil ɗin da muka saka a layin ƙarshe:
/ kafofin watsa labarai /etc/auto.misc
yanzu zamu je /etc/auto.misc
nano /etc/auto.master
kuma a layin karshe zamu rubuta:
myememory -fstype = vfat, masu amfani, rw, umask = 000: / dev / miusb
a ƙarshe mun sanya shi ya ɗora jigon abubuwan motoci a farkon:
sudo nano / sauransu / kayayyaki
kuma a layin karshe zamu rubuta:
autos4
kuma voila, zamu sake kunna Rasberi. Ka tuna cewa babban fayil baya wanzu a cikin / kafofin watsa labarai amma lokacin da muke yin a
cd / kafofin watsa labarai / ƙwaƙwalwar ajiya
mun riga mun shiga ciki. Kuma idan muka daina amfani da shi, babban fayil ɗin ya ɓace kuma za mu iya cire na'urar ba tare da cire shi da hannu ba.
godiya ga posting dinta 🙂
Ina tsammanin akwai kuskure, a matakin gyara auto.misc, auto.master an rubuta a cikin lambar, idan wani rashin hankali yayi hakan kuma bai farga ba 🙂
Na gode, Ina kawai yin shi a kan Raspbian, na yi amfani da Arch a da kuma ya fi sauƙi.
Yayi kyau sosai, cewa nayi lokacin dana sanya Pi a matsayin babban abokin ciniki tare da kundin adireshin da samba ya raba.
Littafin fstab ya ce wani abu da ya fi ƙarfin gaske shi ne bincika lakabin naúrar tare da # blkid, a halin da nake ciki ina da takunkumin windows masu daidaituwa a kowane farawa kamar haka:
/ dev / sda2
UUID = 24A0729FA07276E0 / gida / azureus / Windows ntfs auto, tsoffin abubuwa 0 2
akan rasberi Ina da LVM mai ɗorawa, Ban tuna saitin sosai ba.
Dangane da littafin, zaku iya amfani da # fdisk -l don samun lambar tuki da harafi da # blkid don sanin wane tambari ne yayi daidai da motar.
Na gode.
[Sabuntawa]
Wannan lakabin ya samo asali ne daga gaskiyar cewa akwai mutane (kamar ni) waɗanda suke jin kasala don katse ƙara a duk lokacin da aka kashe kwamfutar, matsalar ita ce lokacin da kuke da kundin da yawa tunda ba koyaushe ake ɗora shi a cikin tsari iri ɗaya ba bayan sake kunnawa da yawa . Af, wannan yana da matsala, lokacin da aka cire na'urar da ta dace da lambar da aka sanya don atomatik, tana jefa kuskure kuma baya ƙyale a shigar da / gida idan an ɗora bangare a gida. Ana iya warware wannan ta hanyar yin tsokaci game da na'urar da ke haifar da rikice-rikice a fstab ko ta sake haɗa na'urar