• úvod
  • témata
  • události
  • tržiště
  • diskuze
  • nástěnka
  • přihlásit
    registrace
    ztracené heslo?
    DELVITLinux pro zacatecniky a obycejne uzivatele (NO FLAMES!)
    Každý kdo chce poradit ohledně linuxu je na spravném místě. Přímý následovník audítka stejného názvu. Pravidla jsou stejná jako predchozí, hlavně žádné FLAME!
    Na Hompage klubiku najdete alternativy k aplikacim. Snazim se drzet ten list v aktualizovane a hlavne zajimave alternativy, kdyby ste chteli neco pridat do listu dejte vedet.

    Jak se správně ptát:

    1) Popište příznaky problému nebo chyby co možná nejjasněji a nejpečlivěji.
    2) Popište prostředí, ve kterém chyba nastává, tj. architekturu, operační systém, aplikaci, verzi, atd. Jmenujte distribuci a verzi systému (např. Red Hat 8.0, Slackware 5.1, atd.).
    3) Popište, jak jste se k chybě dostali, a jak jste se ji pokusili odhalit, isolovat a pochopit ještě předtím, než jste se zeptali.
    4) Popište relevantní změny v konfiguraci, které jste v poslední době provedli.
    5) Pokuste se už předem zodpovědět případné doplňující otázky.
    6) Na dlouhé výpisy použijte služby na to určené - pastebin - http://pastebin.com/
    rozbalit záhlaví
    YARRDESH
    YARRDESH --- ---
    YARRDESH: resp musim u toho skriptu dodrzet LSB header atd, a dumat, proc ma bezet furt jako service, kdyz ho potrebuju spustit jenom jednou?
    YARRDESH
    YARRDESH --- ---
    SATAI: hele a teda v tom init.d muzou bejt jenom demoni, nebo i skripty k jednomu spusteni?
    YARRDESH
    YARRDESH --- ---
    RATTKIN: me to s crontabem a bootem nefungovalo, a nevim jestli tim, ze se crontab vykonaval pred nahozenim networkingu, a nebo tim, ze prikazy v tom skriptu potrebujou roota, coz kdyz se pusti mimo zalogovanou session, tak nevim, jak se udela. nasel jsem akorat nabadani, ze v init.d a runlevelech to jde jako SU, tak jsem po nefunkcnim crontabu zvolil tuhle cestu. me by teda jako stacilo, kdyby se k ty wifi automaticky pripojilo dle zapisu v /etc/network/interfaces, ale to nepochopitelne nedela. coz mi pripomina dalsi dotaz: kdyz se potrebuju pripojit k wpa wifine, tak v interfaces zadavam do radku wpa-psk ten (zrejme) hashklic z wpa_supplicant.conf , co mi z hesla udela wpa_passphrase , nebo tam zadavam heslo v normalni podobe? a pokud klic, mam ho davat do uvozovek? ja furt nevim, proc se mi wifi sama nenahodi. muzu sem hodit obsah interfaces a pripadne obsah toho skriptu, kterej mi ji pritom nahodi?
    SATAI
    SATAI --- ---
    YARRDESH: je to novější init

    asi napsat systemd unitu a enable. Slušný návod býval tradičně na Arch Linux wiki ;)
    YARRDESH
    YARRDESH --- ---
    SATAI: sice nevim, co to je, ale bezi to tam
    RATTKIN
    RATTKIN --- ---
    YARRDESH: já dávám crontab @boot, funguje mi to. nevím, jestli je to správné nebo špatné
    SATAI
    SATAI --- ---
    YARRDESH: se systemd?
    YARRDESH
    YARRDESH --- ---
    SATAI: kali pro arm (na raspberry). takze naka mutace debianu
    SATAI
    SATAI --- ---
    YARRDESH: jake distro?
    YARRDESH
    YARRDESH --- ---
    pic, kdyz chci, aby se mi spustil nejakej skript pri startu, a usoudil jsem, ze ho nacpu do /etc/init.d a v /etc/rc3.d na nej dam symlinkovej odkaz, tak je to spravne? nebo v init.d muzou bejt jenom demonu a v runlevelovejch adresarich mam symlinkovat na skript nekde jinde, kdyz je to jenom par prikazu pro rucni nahozeni wifi? jsem si totiz v dobry vire udelal skript na nahozeni wifi a dal ho do init.d a v runlevelu 3 s SXX cislem dostatecne pozde udelal symlink, a ac dost prapodivne, nak se mi ta wifi nakonec nahodi. akorat jsem si ted chtel presmerovat provoz z wifiny na eth0 a fungovat jako router, postupoval jsem ted podle nejakyho navodu a dostal jsem se prave do bodu, kdy jsem musel udelat 'update-rc.d setuprouty defaults' (setuprouty je nejakej skript z navodu na prohozeni routovani) a ponekud se to zblaznilo, ze ten muj skript na wifinu nedodrzuje LSB standarty pro demony. vubec nevim, kde to k tomu scriptu prislo :

    (tohle jsou setuprouty)
    #!/bin/sh
    #/etc/init.d/setuproutes
    #
    ### BEGIN INIT INFO
    # Provides: default routes for wlan0
    # Required-Start: $syslog $network
    # Required-Stop: $syslog
    # Should-Start:
    # Should-Stop:
    # X-Start-Before:
    # X-Stop-After:
    # Default-Start: 2 3 4 5
    # Default-Stop: 0 1 6
    # X-Interactive: false
    # Short-Description: adjust default routes
    # Description: removes default route 192.168.2.1 adds default route 192.168.1.1
    ### END INIT INFO
    sudo route del default gw 192.168.9.1 eth0
    sudo route add default gw 192.168.8.1 wlan0


    no a takhle se to na me vydesilo po zadani commandu. kam mam teda davat spousteci skripty, pro ktery potrebuju roota a nahozeny nektery veci, takze nemuzu pouzit crone ?

    update-rc.d setuprouty defaults
    insserv: warning: script 'S06wf_nahod_sklivec' missing LSB tags and overrides
    insserv: warning: script 'wf_nahod_nusru' missing LSB tags and overrides
    insserv: warning: script 'wf_nahod_sklivec' missing LSB tags and overrides
    insserv: There is a loop between service rmnologin and mountnfs if started
    insserv: loop involving service mountnfs at depth 8
    insserv: loop involving service networking at depth 7
    insserv: There is a loop between service rmnologin and mountnfs if started
    insserv: There is a loop between service rmnologin and mountnfs-bootclean if started
    insserv: loop involving service mountnfs-bootclean at depth 11
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Starting wf_nahod_sklivec depends on rmnologin and therefore on system facility `$all' which can not be true!
    insserv: Max recursions depth 99 reached
    insserv: loop involving service saned at depth 2
    insserv: There is a loop between service rmnologin and mountkernfs if started
    insserv: loop involving service mountkernfs at depth 1
    insserv: exiting now without changing boot order!
    update-rc.d: error: insserv rejected the script header
    root@kali:/etc/init.d# ^C
    root@kali:/etc/init.d# ^C
    root@kali:/etc/init.d# missing LSB tags and overrides


    wf_nahod_sklivec a wf_nahod_nusru jsou moje skripty, nusra ani nema symlink, tu mam do zasoby na jinou wifi sit, a rmnlogin je v runlevelu 3 s cislem S04, wf_nahod_sklivec je tamtez s cislem S06. S04rmnlogin vubec netusim k cemu je a proc by na nem mel zaviset muj sklivec. jo a jaktoze maji nektery symlinky stejny poradovy S cislo? pod S04 je jich tam par, pod S03 asi pet atd ..?
    dekuji predem za rady lame, po letech utecivsi z widli
    ERGOSUM
    ERGOSUM --- ---
    SUK: v prohlížeči nízká hlasitost(téměř nic), po stažení GnomeMPlayer, ani Audacious nejsou úspěšnější a když to pro vyloučení chyby u mě pošlu na
    YouTube to mp3 Converter
    http://www.youtube-mp3.org/#v_id=hM9V14hiSZ0
    výsledek stejný.
    Hned druhé video z té série na YT bylo v pořádku.
    [ ERGOSUM @ Linux pro zacatecniky a obycejne uzivatele (NO FLAMES!) ]
    Mě z toho vychází, že to video na YT stojí za nic.
    Tak abys na něm zbytečně nemarnil čas.
    SUK
    SUK --- ---
    ERGOSUM: Spatny soubor na YT? Co to konkretne znamena? Dela mi to asi tak u 80% videi :(
    ERGOSUM
    ERGOSUM --- ---
    SUK: špatný soubor na YT. skus s

    Pink Floyd - The Dark Side of the Moon - Breathe (FLAC)
    https://www.youtube.com/watch?v=fZ_YAK0NSX0&list=PLjw9pdSQ4sqsBHfKZH2gT3SgzBANZ0ltP&index=2
    SUK
    SUK --- ---
    Zdar, strasne zacatecnicky problem :D

    mpd&mpc, youtube-dl - a chci si poustet zvuk z videi na YT. Pouziju napriklad toto: youtube-dl -f251 -g --prefer-insecure 'https://www.youtube.com/watch?v=hM9V14hiSZ0&list=PLjw9pdSQ4sqsBHfKZH2gT3SgzBANZ0ltP' | xargs -n1 mpc add

    Ale je problem, ze mpd to nedokaze prehrat, ozve se jenom bordel :( Zkousel jsem na formaty 251, 171. Funguje to nekomu? Donedavna mi to frcelo dobre (171 urcite). Lze do MPD pridat i nejaky "kodek" (hlavne ten "de")? Konkretne tento format(vypsatelne pomoci youtube-dl -F $URL_VIDEA)?
    251 webm audio only DASH audio 135k , opus @160k, 1.00MiB

    Diky za pripadny tip (i kdyz mam tuseni, ze jsem spis dal radu ostatnim a mi nikdo nepomuze, jak je zvykem u mych nezvyklych dotazu :D )
    SATAI
    SATAI --- ---
    Ono taky neni od veci si uvedomit, ze trebas v Ubutnu cele Universe oficialne neni podporovane.
    DANYSEK
    DANYSEK --- ---
    KECAM: hlavne se podivej na topic (Linux pro zacatecniky)... o tom to je ;) Zacatecnikovi nebudu doporucovat, aby si kompiloval rucne kernel, zacatecnikovi zasadne doporucim, aby se spolehnul na distribuci...
    KECAM
    KECAM --- ---
    DANYSEK: asi si blbe rozumime co povazujeme za update. ja chapu i fix( v tvem pripade aktualizace?) jako update.
    DANYSEK
    DANYSEK --- ---
    KECAM: nechapu, co presne tim chces rict. V ramci distribuci se dnes bezne pouzivaji long-term support kernely - ktere bezpecnostni aktualizave dostavaji, a i v pripade "zdanlive starych" verzi kernelu (a nejen jeho, tyka se to prakticky vsech balicku v distribucich) je reseno backportovani bezpecnostnich oprav - a to casto i v pripade, kdy uz to upstream ani neresi...
    Ve skutecnosti novy kod (nove featury) naopak teoreticky oteviraji nove potencialni vektory utoku. Jestli si myslis, ze kazda novinka v kernelu (a nejen v nem) je z pohledu bezpecnosti a moznych zranitelnosti proverena, tak se seredne mylis ;-)
    DANYSEK
    DANYSEK --- ---
    PISKVOR: zacatecnik to fakt nepotrebuje - maximalne, ma-li nejaky hodne novy a specificky hardware. Na drtivou vetsinu beznych use-case staci distribucni kernely....
    PISKVOR
    PISKVOR --- ---
    CHOROBA: Jak často já updatuju kernel? ... Nevím, a přesto to funguje.
    Kliknutím sem můžete změnit nastavení reklam