Re: Mailinglist
On 07-05-15 12:49, Matijs van Zuijlen wrote: On 07/05/15 11:26, lnx wrote: Debian, On 07-05-15 10:40, Matijs van Zuijlen wrote: On 07/05/15 09:40, Paul van der Vlis wrote: Op 07-05-15 om 09:15 schreef Geert Stappers: De term 'onderposten' is mijn inziens ontstaan in een tijd dat men het te veel moeite vond om mensen te leren waar ze de cursor neer moeten zetten. Dat onlogische gedrag noemde men 'bovenposten'. De mensheid zal er nog wel even last van hebben. Misschien zou ik wat minder laten leven moeten hanteren en tegen bovenposters wel moeten zeggen dat ze hun cursus e-mail moeten afmaken. Weet je zo'n cursus? Ik wil mensen het regelmatig uitleggen, maar weet geen URL met uitleg. Het gaat in mijn geval dan meestal om gewone private-mail waarin je op elkaar reageert. Ik vrees dat 'bovenposten' gewoon de norm is geworden, zeker voor private email. Waarom dit niet accepteren en er mee (leren) leven? Beide mogelijkheden staan tenslotte toe dat de voorgaande conversatie in het bericht zelf kan worden nagelezen. .of maak een onderscheidt tussen private e-mails en een technische (lees: debian-user-dutch) mailinglist. Daarom zei ik ook: 'zeker voor private email'. Tegen je niet-technische vrienden (en klanten) zeggen dat ze hun cursus e-mail moeten afmaken is niet echt bevorderlijk voor de goede verstandhouding. Denk dat de Poster van die opmerking specifiek de debian-user-dutch mailinglist bedoelde en niet de niet-technische vrienden (en klanten). Bij een technische mailinglist worden zaken, om tot de kern van het probleem te kunnen komen, afgestreep en worden evt. nieuwe suggesties aangedragen. Door dit IN de email zelf te doen blijft het overzicht behouden en blijft de kern van het probleem centraal staan. Deze twee punten vergen helaas op een mailing list wel enige additionele discipline, maar bottomposten helpt inderdaad, vooral ook om op individuele onderdelen te reageren. Bij techneuten is die additionele discpiline standaard wel aanwezig en bij niet-techneuten zal die additionele discipline gewoon minder aanwezig is. Volgens mij zit hier dan ook het pijnpunt. Dit lijken me uitstekende punten om op de hypothetische pagina met huisregels die ik hieronder noem te noemen. knip Meestal pas ik me aan aan de bestaande conversatie, zoals ook hier :-). Misschien wel de beste oplossing met als vertrekpunt dat het rolmodel techneut is wanneer er gepost gaat worden op een technische mailinglist. Voor mailing lists kan het natuurlijk onderdeel van de huisregels zijn, en dan is een URL met uitleg van die regels inderdaad beter. -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554c5408.8060...@kpnmail.nl
Re: Debian 8 no network...
* Gábor Hársfalvi hgab...@gmail.com [2015-05-07 21:15 +0200]: Hello, I've got the problem yet - and I don't know why. Everything uses my Internet connection - browsers, online games etc. - but the system update manager always gives me an error about no network connection. So you have to check your system update manager's network settings. This is the same when I wish to install a .deb package from the PC. But when I use Terminal commands - for example apt-get install .deb it always work with the same network connection for downloading packages. You can't install Debian binaries via apt-get. You can only install packages like: apt-get install packagename I'm using PPPOE connection with dsl-provider - and I wish to use that for the future too. Should be no problem. Elimar -- Experience is something you don't get until just after you need it! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508062513.gc9...@baumbart.home.lxtec.de
Re: nfs problems
On Fri, 8 May 2015 00:50:24 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote: On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Next is the box on my cnc lathe, #3. But now, not even root can make a third directory on this /net subdir, No Permissions. And the name of the dir could be LanceRumpleStiltSkin root still can't make the directory. i just finished wrestling with NFS set-up problems myself. However I don't understand your description of the problem. why don't you provide the following: /etc/exports from the machine hosting the shares ==from lathe.coyote.den / coyote.coyote.den(rw,sync,fsid=0,no_subtree_check) Gene, Add no_root_squash here, and root will be able to write on the clients. That _is_ what you want, isn't it? Petter -- I'm ionized Are you sure? I'm positive. pgpsc_bIZWLtb.pgp Description: OpenPGP digital signature
Re: Mailinglist
Op 07-05-15 om 10:40 schreef Matijs van Zuijlen: Ik vrees dat 'bovenposten' gewoon de norm is geworden, zeker voor private email. Waarom dit niet accepteren en er mee (leren) leven? Beide mogelijkheden staan tenslotte toe dat de voorgaande conversatie in het bericht zelf kan worden nagelezen. Het nadeel is, dat je gemakkelijk onderdelen uit het bericht vergeet te beantwoorden. Verder moet je niet alleen de antwoorden opschrijven, maar ook duidelijk maken waarop het een antwoord is. Meestal pas ik me aan aan de bestaande conversatie, zoals ook hier :-). Ik pas me natuurlijk ook wel aan, sommige mensen snappen echt niets van quoten. Daarom zou ik ze graag een link willen geven die het wat uitlegt. Er zijn wel wat sites, maar die gaan vaak nogal specifiek over usenet of mailinglijsten. Terwijl ik quoten ook veel voor gewone e-mail gebruik. Bijvoorbeeld hier: http://www.leerquoten.nl/quote.html Voor mailing lists kan het natuurlijk onderdeel van de huisregels zijn, en dan is een URL met uitleg van die regels inderdaad beter. Ik heb het hier niet zozeer over regels, maar wil de kennis van mensen vergroten. Zodat ze begrijpen waarom ik iets doe. Groet, Paul. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554c7913.4090...@vandervlis.nl
Re: Upgrade to Jessie freezes when Grub configuration file is being generated
On Thu, May 07, 2015 at 10:26:33AM -0400, Pierre Chausse wrote: Hi all, I am trying to do an apt-get upgrade which I hadn't done for a while so it was a major update. Everything went well except that the installation cannot complete when it reaches the stage of configuring Grub. I tried to reboot and rerun apt-get install for the installation to complete and it always freezes with the following: Setting up grub-pc (2.02~beta2-22) ... Installing for i386-pc platform. Installation finished. No error reported. OK, so grub (believes it) is installed correctly. Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.2.0-3-amd64 Found initrd image: /boot/initrd.img-3.2.0-3-amd64 No volume groups found So grub-update hung while generating the config file. Let's assume the worst-case scenario that the config file is partially written and so is unusable. I tried to wait long time but it stays there. When I try to reboot it takes forever. We can see the following message multiple times before it reboots: ...: Unexpected close, not stopping watchdog! Oh, this is during the shutdown phase? This isn't (necessarily) a problem. This implies to me that you're using watchdog software (possibly from the watchdog package). When the watchdog service stops, it closes the watchdog device. The message above is just a warning saying I've noticed that you've closed the watchdog device, but the countdown timer is still running. Now, if you're restarting the watchdog service that's not a problem, as you'll write to the device before the timeout; during normal shutdown it should also not be a problem as the watchdog should stop close enough to the actual shutdown/reboot that the watchdog won't fire. So, in other words, something else is causing you problems. Check your logs. Watch the console (if you can), for any services which are holding back the shutdown. One thing that has struck me as a possible issue. How old was the system before the update? Is it possible that you've upgraded a stable Wheezy system to a stable Jessie system? If so, please read the Release Notes for Jessie for any gotchas. Any idea how to fix that. Thanks Pierre -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/c3b394240fc821d9eaa72ff2b56cae96.squir...@mailservices.uwaterloo.ca -- For more information, please reread. signature.asc Description: Digital signature
Re: avatar session lxde
Salut, nono a écrit le 08/05/2015 07:10 : Je cherche à mettre un avatar à l'ouverture de session de mon utilisateur, sous lxde debian 8. Apparemment, il suffit d'avoir une image ou un lien logique : $HOME/.FACE Et avoir gnome-control-center installé (???). Cf : https://wiki.archlinux.org/index.php/LXDM#Adding_face_icons Je n'ai pas testé, je n'ai pas utilisé lxde depuis un moment. -- Stéphane -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/mihqre$npf$2...@usenet.pasdenom.info
Welke desktop
- Forwarded message from Paul van der Vlis - Date: Fri, 08 May 2015 11:53:47 +0200 From: Paul van der Vlis To: debian-user-dutch@lists.debian.org Subject: Re: Vertaling Debian Jessie User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 Op 07-05-15 om 18:38 schreef Patrick Ruytings: On Wed, 06 May 2015 19:28:02 +0200, Jan-Rens Reitsma: Welke desktop? Gnome, KDE, Xfce, Openbox, LXDE, ... ? Ik dacht MATE. Hoe zou je kunnen bepalen welke desktop iemand heeft, als deze dat zelf niet weet? - Gnome3 standaard is te herkennen aan het feit dat er linksboven Activiteiten staat, of in het Engels Activities https://en.wikipedia.org/wiki/Debian#/media/File:Debian.png - Gnome3 classic en Gnome3 flashback hebben linksboven de menu-items Toepassingen en Locaties. Of Applications en Places in het Engels. Hoe deze twee nu precies uit elkaar te houden zijn weet ik nog niet zo goed. Gnome3 classic komt meer voor. Screenshot van Gnome Classic: http://i.stack.imgur.com/VQk6I.png Screenshot van Gnome Flashback, maar dit is geen Debian volgens mij: https://wiki.gnome.org/Projects/GnomeFlashback?action=AttachFiledo=gettarget=gnome-flashback.png - KDE heeft linksonder een startmenu-item icoontje met een K. https://upload.wikimedia.org/wikipedia/commons/4/46/Debian-kde.png - XFCE heeft onder standaard een gecentreerde balk. http://3.bp.blogspot.com/-ybp4wC7OBc4/UOyb1eZ6LZI/BIo/syNF_MIJKr4/s1600/Screenshot+-+01082013+-+04:13:22+PM.png - Cinnamon heeft linksonder een tandwieltje staan, met daarnaast het woord Menu. http://i1-news.softpedia-static.com/images/news2/Debian-8-Jessie-Cinnamon-Live-CD-Screenshot-Tour-479389-2.jpg - MATE is te herkennen omdat er linksboven drie menu items staan, namelijk in het Nederlands Applicaties, Locaties en Systeem. https://screenshots.debian.net/screenshots/m/mate-desktop/10990_large.png - LXDE is volgens mij te herkennen aan een soort vliegtuig linksonder, en een aan/uit knop rechtsonder: http://upload.wikimedia.org/wikipedia/commons/4/4c/LXDE_desktop_full.png - IceWM heeft linksonder een icoontje met Debian, en rechtsonder de tijd staan. https://screenshots.debian.net/screenshots/i/icewm/88_large.png Ik ben er vast nog een aantal vergeten. Groet, Paul. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554c87ab.3080...@vandervlis.nl - End forwarded message - -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508101751.ga23...@gpm.stappers.nl
Re: nfs problems
On Fri, 8 May 2015 06:51:43 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 02:55:53 Petter Adsen wrote: That _is_ what you want, isn't it? root does not need write perms, but I do. If it takes root to do something, that is what the ssh -Y session as me, using sudo is for. If you want to read/write file as your normal user, just make sure that the UID is the same on both systems. You might want to edit /etc/passwd on one of the boxes for that, and then you can use find to chown any files that are owned by the old UID. You shouldn't need to do anything other than that. There are other ways to do this, but that is the way I do it at home so I don't need to mess with UID mapping. Or _is_ the UID on both client and server already identical? Petter -- I'm ionized Are you sure? I'm positive. pgpp8XwvX2fot.pgp Description: OpenPGP digital signature
Re: nfs problems
On Friday 08 May 2015 02:55:53 Petter Adsen wrote: On Fri, 8 May 2015 00:50:24 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote: On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: Greetings all; Next is the box on my cnc lathe, #3. But now, not even root can make a third directory on this /net subdir, No Permissions. And the name of the dir could be LanceRumpleStiltSkin root still can't make the directory. i just finished wrestling with NFS set-up problems myself. However I don't understand your description of the problem. why don't you provide the following: /etc/exports from the machine hosting the shares ==from lathe.coyote.den / coyote.coyote.den(rw,sync,fsid=0,no_subtree_check) Gene, Add no_root_squash here, and root will be able to write on the clients. That might be handy, but 99% of what I would need to do would be done by the user, me. Something like finding some interesting code on the net, downloading it here then moving it to one of those machines, going from say coyote:/home/gene/Downloads, to lathe:/home/gene/linuxcnc/nc_files to put it in the normal data directory for linuxcnc. All as me, gene. If, for instance I dl a firmware zip, the unpacked version of which goes into lathe:/lib/firmware/hm2, I'd copy it to my home tree there, then goto that machine in person or with an ssh -Y session, and use a sudo mc session to unpack move the firmware modules. In that event, I'd be just as well to change the / above to /home/gene. So that part isn't exactly painted on the barn for posterity. And since I'd like to be able to reverse the procedure, an /etc/init.d script that restarts the shebang in one swell foop would be handier than bottled beer. One of these machines has an nfs-common script that does idmapd and statd, and another for the nfs-kernel-server, and I don't see any real reason I can't merge them both into a single /etc/init.d/nfs command so that if I change something in the exports or fstab, all the refreshing to see the effect of the change is done with one command on each of the two machines effected. A full, 2 way share that works from all machines is the target. Limiting the share to /home/gene, isn't that much of a hardship. That _is_ what you want, isn't it? root does not need write perms, but I do. If it takes root to do something, that is what the ssh -Y session as me, using sudo is for. Thanks Petter Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505080651.43856.ghesk...@wdtv.com
Re: Uso de memória no Debian 8.0.0
Instalei em um note com 2GB e o consumo ficou próximo de 1GB... teve um momento que abri 6 abas no chrome + o terminal, observei que o note estava usando swap e dali a pouco travou. Alguém indica usar o Mate para resolver estes problemas de desempenho? Em 7 de maio de 2015 23:58, Nilton Vasques nilton.vasq...@gmail.com escreveu: Bem eu instalei o Jessie, em um netbook acer aspire one bem antigo, com apenas 1 GB de ram e processador atom. Sendo que o consumo de memória fica em torno de 500 mb com apenas o terminal aberto, talvez o gnome tenha alguma feature de otimização para computadores com pouca ram. On 07/05/15 21:07, Luiz Carlos da Silveira Júnior wrote: Estou achando o gnome pesado também, ainda mais usando com o chrome... Em 07/05/2015 20:57, real bas realba...@gmail.com escreveu: Olá pessoal, Sei que é um pouco cedo pra falar disso, mas estou tendo um problema com a versão recém-estável do Debian (Jessie). Meu problema é o seguinte: *uso excessivo de memória*. Mesmo somente com um terminal aberto sem rodar nada, o uso de memória fica em torno de 3.5 GB, chegando até a usar a memória de Swap (isso mesmo). Gostaria de saber se alguém está tendo o mesmo problema e saber se já existe uma solução, procurei no fórum global e não encontrei nada relacionado. Minhas configurações de HW: Processador i5, 4 GB de RAM, placa nvidia e 640 GB de HD. -- Att., Nilton Vasques Carvalho Jr. Mobiloucos Team Graduando em Ciência da Computação Universidade Federal da Bahia telefone: +55 71 9278-0148 (Tim) Github: https://github.com/niltonvasques linkedin: http://goo.gl/hUOs7W -- *att,* *Luiz Carlos*
Re: ACPI y smsc47m1
. Pues si todo funciona correctamente, el módulo se carga y los sensores funcionan, quizá no tengas de qué preocuparte. Lo digo porque encontré un bug de Debian con un asunto similar y esa fue la respuesta de uno de los mantenedores del kernel: ACPI Conflict (Hardware in risk) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602128 P.S. No te olvides de eliminar la línea que añadiste en la configuración de GRUB (acpi_enforce_resources=lax). Saludos, -- Camaleón Hola de nuevo. Leí el enlace sobre el bug ACPI Conflict. Eliminé la línea acpi_enforce_resources=lax del archivo /etc/default/grub, dejándolo como al principio. Actualice el grub, y al reiniciar, en la información sobre la carga del sistema, volvió a aparecer el mensaje de Error, por no poder cargar el módulo smsc47m1, como estábamos al principio. Será que deberé dejar el grub modificado (con la línea acpi_enforce_resources=lax)? También probaré instalando el kernel 3.16 como lo sugirieron antes! Cualquier idea es bienvenida. Saludos fdm -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cabzkbcfb0kymnnex51ms0r1fts1qzf_vlbbg+_lmwn6zyow...@mail.gmail.com
Enc: Re: Enc: Re: Uso de memória no Debian 8.0.0
quanto ao xfce, já tentei usar como default, quando instalei wheezy em meu note, mas controle de volume não funcionou, pausar, play, anterior e próxima também não, no kde e gnome nunca deu problema. Ricardo Libanio Em Sex, 08 Mai 2015 11:47:18 -0300 P. J.lt;pjotam...@gmail.comgt; escreveu Gosto do xfce, a interface padrão é tosca, mas é altamente customizável via prórpia interface gráfica(xfce panel), inclusive para quem gostava do antigo gnome2, dá para botar bem parecido... Para os fãs do nautilius é só remover o thunar e instalar o nautilus, no mais não tenho do que reclamar... meu foco produtividade sem muita perfumaria (nada pessoal). que é um custo benefício que não vale a pena, na minha opinião pessoal. Abs Em 08/05/15, Tiago Rochalt;tiago.ro...@openmailbox.orggt; escreveu: gt; On 08-05-2015 09:56, riesdra wrote: gt;gt; ja que entramos no mérito chrome. também não sou fã dele, mas eu tenho gt;gt; netflix, e não consegui fazer rodar em nenhum outro browser a não ser gt;gt; nele, sem falar em flash, o chrome roda sem nenhum problema, já tive gt;gt; problemas ao rodar vídeos em alguns sites com outros browsers. gt; gt; Eu particularmente prefiro abrir mão do conteúdo do que ter que instalar gt; o Google Chrome/Flash. Embora seja obrigado a concordar (em parte) com gt; quem pensa que instalar o plugin do flash é menos pior. gt; gt;gt; gt;gt; quanto a questão de peso, ainda não verifiquei o consumo de memória, mas gt;gt; logo quando fiz a primeira atualização depois de virar stable, tive gt;gt; problemas de lentidão ao abrir diversas abas no iceweasel, pois venho gt;gt; usando ele desde quando ainda era testing, mas não tive mais este gt;gt; problema, depois que reiniciei. gt;gt; gt; gt; Acho que seria melhor definir a diferença entre consumo de memória e gt; leveza, como bem lembrado pelo DUTRA. O chrome (só para exemplificar) gt; tem o pior dos dois mundos, ele consome muita memória e ainda é meio gt; lento para abrir a maioria das páginas web. gt; gt; Afinal de contas é o Gnome do Debian 8 que está consumindo muita memória gt; e levando o sistema a usar swap, ou é algum beberão como chrome, gt; firefox ou etc?! gt; gt;gt; gt;gt; gt;gt; gt;gt; */Ricardo Libanio gt;gt; gt;gt; /* gt;gt; gt;gt; gt;gt; Em Sex, 08 Mai 2015 08:59:32 -0300 *Tiago Rocha gt;gt; lt;tiago.ro...@openmailbox.orggt;* escreveu gt;gt; gt;gt; On 08-05-2015 08:37, Guimarães Faria Corcete DUTRA, Leandro wrote: gt;gt; gt; Em 8 de maio de 2015 08:26, Tiago Rocha gt;gt; lt;tiago.ro...@openmailbox.org lt;mailto:tiago.ro...@openmailbox.orggt;gt; gt;gt; escreveu: gt;gt; gt;gt; Eu indico não usar o google chrome;) gt;gt; gt; gt;gt; gt; Eu mesmo uso mais o Conkeror e o Epiphany segundo a necessidade, gt;gt; mas gt;gt; gt; quando preciso de um navegador mais popular para os sítios mais gt;gt; gt; chatos, uso o Chromium. Não sei se é mais leve que o Google gt;gt; Chrome, gt;gt; gt;gt; Quando tento lembrar de um navegador mais pesado Google Chrome só me gt;gt; lembro do Internet Explorer É tenso! :-/ gt;gt; gt;gt; gt; mas pelo menos não é uma caixa preta. gt;gt; gt;gt; Mais pura verdade!!! gt;gt; gt;gt; gt;gt; gt;gt; -- gt;gt; Tiago Rocha gt;gt; gt;gt; É bom tudo aquilo que faço que diminui o meu poder sobre outra gt;gt; pessoa; gt;gt; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela. gt;gt; Antônio Joaquim Severino gt;gt; gt;gt; gt;gt; -- gt;gt; To UNSUBSCRIBE, email to gt;gt; debian-user-portuguese-requ...@lists.debian.org gt;gt; lt;mailto:debian-user-portuguese-requ...@lists.debian.orggt; gt;gt; with a subject of unsubscribe. Trouble? Contact gt;gt; listmas...@lists.debian.org lt;mailto:listmas...@lists.debian.orggt; gt;gt; Archive: https://lists.debian.org/554ca524.9060...@openmailbox.org gt;gt; gt;gt; gt;gt; gt; gt; gt; -- gt; Tiago Rocha gt; gt; É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; gt; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela. gt; Antônio Joaquim Severino gt; gt; gt; -- gt; To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org gt; with a subject of unsubscribe. Trouble? Contact gt; listmas...@lists.debian.org gt; Archive: https://lists.debian.org/554cc18a.80...@openmailbox.org gt; gt; -- | .''`. A fé não dá respostas. Só impede perguntas. | : :' : | `. `'` | `- Je vois tout -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cacnf0ph2x6n0kyzullmdn9ojb7w7xsogad+g3pvukfqdvja...@mail.gmail.com
Re: Verificando portas abertas
O lsof tb pode usar com o numero na porta como filtro, mostra processos e arquivos 2015-05-08 1:13 GMT-03:00, Thiago Zoroastro thiago.zoroas...@bol.com.br: Olá a todos, estive verificando as portas do Debian. Me deparei com 1 unknown na porta 58080 depois de testar vários comandos que fui encontrando na internet. # nmap -sN IP.000.000.000 Starting Nmap 5.00 ( http://nmap.org ) at 2015-05-08 01:07 BRT All 1000 scanned ports on (IP.000.000.000) are open|filtered Nmap done: 1 IP address (1 host up) scanned in 21.44 seconds # nmap -sS IP.000.000.000 Starting Nmap 5.00 ( http://nmap.org ) at 2015-05-08 01:08 BRT Interesting ports on (IP.000.000.000): Not shown: 999 filtered ports PORT STATE SERVICE 58080/tcp open unknown Nmap done: 1 IP address (1 host up) scanned in 7.85 seconds Troquei o IP para IP.000.000.000 na mensagem. Estaria a porta 58080 sendo utilizada de forma invasiva por outra pessoa ou isto é normal? Tentei encontrar e não achei a utilidade da porta 58080, na verdade encontrei mas não compreendi. -- | .''`. A fé não dá respostas. Só impede perguntas. | : :' : | `. `'` | `- Je vois tout -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cacnf0pjfwrvbhmcamsdsys+dmq0s1uy0ape5jeumr2g-56f...@mail.gmail.com
Re: nfs problems
* Petter Adsen pet...@synth.no [2015-05-08 13:03 +0200]: On Fri, 8 May 2015 06:51:43 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 02:55:53 Petter Adsen wrote: That _is_ what you want, isn't it? root does not need write perms, but I do. If it takes root to do something, that is what the ssh -Y session as me, using sudo is for. If you want to read/write file as your normal user, just make sure that the UID is the same on both systems. You might want to edit /etc/passwd Or even run nis within your LAN... Elimar -- Do you smell something burning or is it me? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508132454.ga...@baumbart.home.lxtec.de
Re: Enc: Re: Uso de memória no Debian 8.0.0
On 08-05-2015 09:56, riesdra wrote: ja que entramos no mérito chrome. também não sou fã dele, mas eu tenho netflix, e não consegui fazer rodar em nenhum outro browser a não ser nele, sem falar em flash, o chrome roda sem nenhum problema, já tive problemas ao rodar vídeos em alguns sites com outros browsers. Eu particularmente prefiro abrir mão do conteúdo do que ter que instalar o Google Chrome/Flash. Embora seja obrigado a concordar (em parte) com quem pensa que instalar o plugin do flash é menos pior. quanto a questão de peso, ainda não verifiquei o consumo de memória, mas logo quando fiz a primeira atualização depois de virar stable, tive problemas de lentidão ao abrir diversas abas no iceweasel, pois venho usando ele desde quando ainda era testing, mas não tive mais este problema, depois que reiniciei. Acho que seria melhor definir a diferença entre consumo de memória e leveza, como bem lembrado pelo DUTRA. O chrome (só para exemplificar) tem o pior dos dois mundos, ele consome muita memória e ainda é meio lento para abrir a maioria das páginas web. Afinal de contas é o Gnome do Debian 8 que está consumindo muita memória e levando o sistema a usar swap, ou é algum beberão como chrome, firefox ou etc?! */Ricardo Libanio /* Em Sex, 08 Mai 2015 08:59:32 -0300 *Tiago Rocha tiago.ro...@openmailbox.org* escreveu On 08-05-2015 08:37, Guimarães Faria Corcete DUTRA, Leandro wrote: Em 8 de maio de 2015 08:26, Tiago Rocha tiago.ro...@openmailbox.org mailto:tiago.ro...@openmailbox.org escreveu: Eu indico não usar o google chrome;) Eu mesmo uso mais o Conkeror e o Epiphany segundo a necessidade, mas quando preciso de um navegador mais popular para os sítios mais chatos, uso o Chromium. Não sei se é mais leve que o Google Chrome, Quando tento lembrar de um navegador mais pesado Google Chrome só me lembro do Internet Explorer É tenso! :-/ mas pelo menos não é uma caixa preta. Mais pura verdade!!! -- Tiago Rocha É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela.” Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org mailto:debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org mailto:listmas...@lists.debian.org Archive: https://lists.debian.org/554ca524.9060...@openmailbox.org -- Tiago Rocha É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela.” Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554cc18a.80...@openmailbox.org
Re: Verificando portas abertas
Olá, Experimente o seguinte comando: netstat -tnpl | grep \:58080 Na última coluna você vai ver o número do processo/serviço que é responsável pela porta, com isso você pode saber porque esta porta está aberta. Um exemplo: root@ecelepar16661:~# netstat -tnpl | grep \:139 tcp0 0 0.0.0.0:139 0.0.0.0:* OUÇA 1007/smbd Então eu tenho a porta 139 aberta, e o responsável é o serviço smbd com processo número 1007. Usando o ps e filtrando pelo número do processo: root@ecelepar16661:~# ps aux | grep 1007 root 1007 0.0 0.3 286680 12288 ?Ss 07:30 0:00 /usr/sbin/smbd -D Espero ter ajudado. Att. Fabio Tobich 2015-05-08 1:13 GMT-03:00 Thiago Zoroastro thiago.zoroas...@bol.com.br: Olá a todos, estive verificando as portas do Debian. Me deparei com 1 unknown na porta 58080 depois de testar vários comandos que fui encontrando na internet. # nmap -sN IP.000.000.000 Starting Nmap 5.00 ( http://nmap.org ) at 2015-05-08 01:07 BRT All 1000 scanned ports on (IP.000.000.000) are open|filtered Nmap done: 1 IP address (1 host up) scanned in 21.44 seconds # nmap -sS IP.000.000.000 Starting Nmap 5.00 ( http://nmap.org ) at 2015-05-08 01:08 BRT Interesting ports on (IP.000.000.000): Not shown: 999 filtered ports PORT STATE SERVICE 58080/tcp open unknown Nmap done: 1 IP address (1 host up) scanned in 7.85 seconds Troquei o IP para IP.000.000.000 na mensagem. Estaria a porta 58080 sendo utilizada de forma invasiva por outra pessoa ou isto é normal? Tentei encontrar e não achei a utilidade da porta 58080, na verdade encontrei mas não compreendi.
Re: Debian 8 no network...
On Fri, May 08, 2015 at 03:08:34PM +0200, Petter Adsen wrote: On Fri, 8 May 2015 14:38:53 +0200 Gábor Hársfalvi hgab...@gmail.com wrote: So you have to check your system update manager's network settings. - Where to do it? And where to setup how often do it the update? Well, what _is_ this update manager? Is it some Gnome thing? I know that Ubuntu has something called update-manager, but on my Jessie box with Xfce nothing like that exists. apt-cache search update manager Doesn't find anything that sounds right, either. What are you running? Perhaps he meant 'update-notifier' that's in Jessie? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508142856.GA14286@localhost.localdomain
Re: Jessie 8 per haters de systemd
Hola, 2015-05- 8, 15:14 (+0200); Pedro escriu: quan acabi la instal·lació, estareu arrencant amb sysvinit. Perfecte! Sí, però que arrenqui amb el sysvinit no vol dir que t'hagis desempallegat del systemd! Hi ha el paquet systemd que si l'instal·les crea tot de processos com systemd-logind, systemd-hostnamed i probablement altres. Problema: si desinstal·les systemd aleshores necessites el consolekit, que actualment és un projecte abandonat. -- To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508140729.GA10283@doriath.local
Help with ddrescue
Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508103253.78ce0...@asterius.asterius.net
Re: problema de audio en debian 8 Jessi [solucionado]
El Fri, 08 May 2015 13:35:20 +0200, Ala de Dragón escribió: El 7/5/15, Camaleón noela...@gmail.com escribió: (...) Otros link interesantes para el lector son: http://alsa.opensrc.org/C-Media_CMI8738 http://alsa.opensrc.org/Cmipci http://alsa.opensrc.org/Alsactl Prueba lo que dicen en el primer enlace de desactivar las dos salidas a ver qué sucede. También puedes seguir probando con el comando vlc --aout alsa $HOME/ Escritorio/test.mp4 pero seleccionando el resto de opciones de salida en lugar de alsa, por si vieras algún error, además de las típicas pruebas tontunas como verificar que todos los controles de volumen de salida del applet de sonido de XFCE estén a buen nivel, crear un nuevo usuario y ejecutar VideoLAN desde ahí o si tienes la opción de conectar una salida analógica (conector jack), probar con eso. No tengo chismes HDMI pero si unos cascos para el conector jack, y no suena nada. Jugando con la consola en modo verboso: $vlc -v VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42) [00dc9d78] pulse audio output error: PulseAudio server connection failure: Connection refused [00cfb118] core libvlc: Ejecutar vlc con la interfaz predeterminada. Use «cvlc» para usar vlc sin interfaz. Pues si, resulta que intenta salir por pulseaudio, a pesar de no estar instalado por defecto. Vaya :-? $ vlc -v --aout alsa /home/linux/Escritorio/test.mp4 VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42) ^^^ No me había fijado en eso. Homenaje merecido :-) [00e2d118] core libvlc: Ejecutar vlc con la interfaz predeterminada. Use «cvlc» para usar vlc sin interfaz [7f559cc015b8] mp4 stream warning: unknown box type btrt (incompletely loaded) (...) [7f559cc01808] mp4 demux warning: elst box found [7f559cc01808] mp4 demux warning: STTS table of 1 entries [7f559cc01808] mp4 demux warning: STTS table of 1 entries [7f559cd2c5c8] faad decoder warning: decoded zero sample [02044e58] alsa audio output warning: device cannot be paused (...) Ahora si que suena, analogico por defecto y marcando una opcion de usar la salida spdif si esta disponible suena el audio digital. Pues si, es esto parece un bug de la instalacion. De momento solucionado. Hum... si tienes curiosidad, elimina ese paquetico que tenías instalado vlc-plugin-pulse a ver qué sucede. Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2015.05.08.13.38...@gmail.com
Re: ACPI y smsc47m1
El Fri, 08 May 2015 09:55:23 -0430, Frederit Mogollon escribió: . Pues si todo funciona correctamente, el módulo se carga y los sensores funcionan, quizá no tengas de qué preocuparte. Lo digo porque encontré un bug de Debian con un asunto similar y esa fue la respuesta de uno de los mantenedores del kernel: ACPI Conflict (Hardware in risk) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602128 P.S. No te olvides de eliminar la línea que añadiste en la configuración de GRUB (acpi_enforce_resources=lax). Hola de nuevo. Leí el enlace sobre el bug ACPI Conflict. Eliminé la línea acpi_enforce_resources=lax del archivo /etc/default/grub, dejándolo como al principio. Actualice el grub, y al reiniciar, en la información sobre la carga del sistema, volvió a aparecer el mensaje de Error, por no poder cargar el módulo smsc47m1, como estábamos al principio. ¿A qué mensaje de error te refieres exactamente? ¿Funciona lm-sensors? Será que deberé dejar el grub modificado (con la línea acpi_enforce_resources=lax)? Según la documentación de lm-sensors (ver más abajo) podría ser peligroso. Piensas si no te convendría mejor usar otro monitor de sensores o intentar cargar otro módulo en lm-sensors genérico. También probaré instalando el kernel 3.16 como lo sugirieron antes! Cualquier idea es bienvenida. En el bug de Debian apuntaban aquí: http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2015.05.08.14.52...@gmail.com
Re: Enc: Re: Uso de memória no Debian 8.0.0
Gosto do xfce, a interface padrão é tosca, mas é altamente customizável via prórpia interface gráfica(xfce panel), inclusive para quem gostava do antigo gnome2, dá para botar bem parecido... Para os fãs do nautilius é só remover o thunar e instalar o nautilus, no mais não tenho do que reclamar... meu foco produtividade sem muita perfumaria (nada pessoal). que é um custo benefício que não vale a pena, na minha opinião pessoal. Abs Em 08/05/15, Tiago Rochatiago.ro...@openmailbox.org escreveu: On 08-05-2015 09:56, riesdra wrote: ja que entramos no mérito chrome. também não sou fã dele, mas eu tenho netflix, e não consegui fazer rodar em nenhum outro browser a não ser nele, sem falar em flash, o chrome roda sem nenhum problema, já tive problemas ao rodar vídeos em alguns sites com outros browsers. Eu particularmente prefiro abrir mão do conteúdo do que ter que instalar o Google Chrome/Flash. Embora seja obrigado a concordar (em parte) com quem pensa que instalar o plugin do flash é menos pior. quanto a questão de peso, ainda não verifiquei o consumo de memória, mas logo quando fiz a primeira atualização depois de virar stable, tive problemas de lentidão ao abrir diversas abas no iceweasel, pois venho usando ele desde quando ainda era testing, mas não tive mais este problema, depois que reiniciei. Acho que seria melhor definir a diferença entre consumo de memória e leveza, como bem lembrado pelo DUTRA. O chrome (só para exemplificar) tem o pior dos dois mundos, ele consome muita memória e ainda é meio lento para abrir a maioria das páginas web. Afinal de contas é o Gnome do Debian 8 que está consumindo muita memória e levando o sistema a usar swap, ou é algum beberão como chrome, firefox ou etc?! */Ricardo Libanio /* Em Sex, 08 Mai 2015 08:59:32 -0300 *Tiago Rocha tiago.ro...@openmailbox.org* escreveu On 08-05-2015 08:37, Guimarães Faria Corcete DUTRA, Leandro wrote: Em 8 de maio de 2015 08:26, Tiago Rocha tiago.ro...@openmailbox.org mailto:tiago.ro...@openmailbox.org escreveu: Eu indico não usar o google chrome;) Eu mesmo uso mais o Conkeror e o Epiphany segundo a necessidade, mas quando preciso de um navegador mais popular para os sítios mais chatos, uso o Chromium. Não sei se é mais leve que o Google Chrome, Quando tento lembrar de um navegador mais pesado Google Chrome só me lembro do Internet Explorer É tenso! :-/ mas pelo menos não é uma caixa preta. Mais pura verdade!!! -- Tiago Rocha É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela. Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org mailto:debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org mailto:listmas...@lists.debian.org Archive: https://lists.debian.org/554ca524.9060...@openmailbox.org -- Tiago Rocha É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela. Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554cc18a.80...@openmailbox.org -- | .''`. A fé não dá respostas. Só impede perguntas. | : :' : | `. `'` | `- Je vois tout -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cacnf0ph2x6n0kyzullmdn9ojb7w7xsogad+g3pvukfqdvja...@mail.gmail.com
Re: Vertaling Debian Jessie
On Fri, 08 May 2015 00:37:06 +0200, bert frohn b.fr...@home.nl wrote: Patrick Ruytings schreef op do 07-05-2015 om 18:38 [+0200]: Ik heb vastgesteld dat er ergens in Debian Jessie een probleem is met de vertaling naar het Nederlands. Ik heb minstens 1 menu gezien (rechts klikken op het bureaublad) waar de onderdelen voor een deel in het Nederlands staan en voor een deel in het Engels (en dat vloekt. :-). Welke desktop? Gnome, KDE, Xfce, Openbox, LXDE, ... ? Ik dacht MATE. Mate is o.k. (zie bijlage) Raar...ik zal nog eens testen (zie ook andere reply). -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1krpka1lfls1mpl419kfnrg7jp3o365...@4ax.com
Debian et station d'accueil
Bonsoir à tous, La station d'accueil d'un ordinateur portable peut-elle selon vous perturber le fonctionnement d'une distribution LINUX (DEBIAN). En terme de matériel, je pense à un ancien portable DELL D430 et sa station d'accueil https://www.youtube.com/watch?v=5Zd9r7KYOvY. Merci pour vos réponse. Alex PADOLY
Re: nfs problems
Hi, On 05/08/2015 09:00 AM, Petter Adsen wrote: On Fri, 8 May 2015 00:50:24 -0400 Gene Heskett ghesk...@wdtv.com wrote: On Friday 08 May 2015 00:36:51 bri...@aracnet.com wrote: On Fri, 8 May 2015 00:03:22 -0400 Gene Heskett ghesk...@wdtv.com wrote: i just finished wrestling with NFS set-up problems myself. Add no_root_squash here, and root will be able to write on the clients. But isn't there a potential security risk in using that option? AFAIK, with that option enabled, a remote root user (on the nfs client) could gain root privileges the nfs server. Cheers, Simon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/miis8s$15h$1...@news.albasani.net
Re: Enc: Re: Uso de memória no Debian 8.0.0
Para mim é o contrário... O que existe de pior em gerenciador de arquivos é o Nautilus. Dolphin, PCManFM, Thunar... Todos acho muito melhores Acho que a único coisa que o Gnome 3 não estragou foi a calculadora. Jack Pogorelsky Junior Engº Mecânico Tel: +55 (51) 9348-0140 Site: sulmail.com/pogorelsky E-mail: j...@sulmail.com On 08/05/2015 11:47, P. J. wrote: Gosto do xfce, a interface padrão é tosca, mas é altamente customizável via prórpia interface gráfica(xfce panel), inclusive para quem gostava do antigo gnome2, dá para botar bem parecido... Para os fãs do nautilius é só remover o thunar e instalar o nautilus, no mais não tenho do que reclamar... meu foco produtividade sem muita perfumaria (nada pessoal). que é um custo benefício que não vale a pena, na minha opinião pessoal. Abs Em 08/05/15, Tiago Rochatiago.ro...@openmailbox.org escreveu: On 08-05-2015 09:56, riesdra wrote: ja que entramos no mérito chrome. também não sou fã dele, mas eu tenho netflix, e não consegui fazer rodar em nenhum outro browser a não ser nele, sem falar em flash, o chrome roda sem nenhum problema, já tive problemas ao rodar vídeos em alguns sites com outros browsers. Eu particularmente prefiro abrir mão do conteúdo do que ter que instalar o Google Chrome/Flash. Embora seja obrigado a concordar (em parte) com quem pensa que instalar o plugin do flash é "menos pior". quanto a questão de peso, ainda não verifiquei o consumo de memória, mas logo quando fiz a primeira atualização depois de virar stable, tive problemas de lentidão ao abrir diversas abas no iceweasel, pois venho usando ele desde quando ainda era testing, mas não tive mais este problema, depois que reiniciei. Acho que seria melhor definir a diferença entre consumo de memória e "leveza", como bem lembrado pelo DUTRA. O chrome (só para exemplificar) tem o pior dos dois mundos, ele consome muita memória e ainda é meio lento para abrir a maioria das páginas web. Afinal de contas é o Gnome do Debian 8 que está consumindo muita memória e levando o sistema a usar swap, ou é algum "beberão" como chrome, firefox ou etc?! */Ricardo Libanio /* Em Sex, 08 Mai 2015 08:59:32 -0300 *Tiago Rocha tiago.ro...@openmailbox.org* escreveu On 08-05-2015 08:37, Guimarães Faria Corcete DUTRA, Leandro wrote: Em 8 de maio de 2015 08:26, Tiago Rocha tiago.ro...@openmailbox.org mailto:tiago.ro...@openmailbox.org escreveu: Eu indico não usar o google chrome;) Eu mesmo uso mais o Conkeror e o Epiphany segundo a necessidade, mas quando preciso de um navegador mais popular para os sítios mais chatos, uso o Chromium. Não sei se é mais leve que o Google Chrome, Quando tento lembrar de um navegador mais pesado Google Chrome só me lembro do Internet Explorer É tenso! :-/ mas pelo menos não é uma caixa preta. Mais pura verdade!!! -- Tiago Rocha "É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela." Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org mailto:debian-user-portuguese-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org mailto:listmas...@lists.debian.org Archive: https://lists.debian.org/554ca524.9060...@openmailbox.org -- Tiago Rocha "É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela." Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554cc18a.80...@openmailbox.org -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554ceda1.2040...@gmail.com
Re: Help with ddrescue
On Fri, 08 May 2015 12:10:38 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 10:32 AM, German wrote: Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 would be the partition that you want to recover. Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. So, if failed drive is for instance /dev/sdb and spare drive is for isntance /dev/sdc, the right command will be ddrescue if=/dev/sdb of=/dev/sdc/failed.img ? And also, you didn't answer this, what file system the a spare drive ahs to be formated? Thanks. If you have space, make a copy of failed.img as well (cp failed.img failed2.img) so you don't have to go back to the actual failed drive, which is likely getting worse each time you access it. Next you can run whatever rescue software you like on the failed.img file to see if you can recover anything. I usually start off with something simple like fsck before trying testdisk. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508132034.58b6d...@asterius.asterius.net
Re: Debian et station d'accueil
Le 08/05/2015 19:18, apado...@padoly.besaba.com a écrit : Bonsoir à tous, La station d'accueil d'un ordinateur portable peut-elle selon vous perturber le fonctionnement d'une distribution LINUX (DEBIAN). En terme de matériel, je pense à un ancien portable DELL D430 et sa station d'accueil https://www.youtube.com/watch?v=5Zd9r7KYOvY. Merci pour vos réponse. Alex PADOLY Ça va surement dépendre. Personnellement aucun problème sur Lenovo T530 -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/554cf03a.1000...@rail.eu.org
Re: Help with ddrescue
On 05/08/2015 at 01:20 PM, German wrote: On Fri, 08 May 2015 12:10:38 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 10:32 AM, German wrote: Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 would be the partition that you want to recover. Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. So, if failed drive is for instance /dev/sdb and spare drive is for isntance /dev/sdc, the right command will be ddrescue if=/dev/sdb of=/dev/sdc/failed.img ? No. With ddrescue, you do not (want to) create a new filesystem directly on the new device. What you want to do is create a filesystem _image_, in a file which is stored on the new device. Step-by-step, what you do is: * Create a filesystem on your good drive (/dev/sdc). You can use any filesystem you want. * Mount the newly created filesystem somewhere. For example, if you want to mount it to the empty directory '/mnt/new_disk', you could run the command: mount /dev/sdc1 /mnt/new_disk * Run the command ddrescue /dev/sdb /mnt/new_disk/sdb_failed.img /tmp/sdb_failed.ddrescuelog Note that this will create _two_ files: the rescued filesystem image, and a log file which ddrescue uses to keep track of what it has already successfully rescued and where it has encountered errors. This second file will take up additional space. * If you have enough free space, copy the resulting sdb_failed.img to a separate location, so you have a backup copy if something goes wrong. * Run recovery tools (starting with fsck, as Gary Dale suggested) on sdb_failed.img, and see how much you can recover. * Mount sdb_failed.img, using a loopback mount, and copy out whatever files you can to a new location. Recovering data from a failed drive using ddrescue, dd_rescue, or myrescue is entirely possible; I've done it myself. However, it is not trivial, and in my experience the process requires considerably more space than the size of whatever drive is being rescued. Personally, I would probably recommend the use of myrescue rather than of ddrescue or dd_rescue, but any of them can work if you use them right. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On 08/05/15 10:32 AM, German wrote: Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 would be the partition that you want to recover. If you have space, make a copy of failed.img as well (cp failed.img failed2.img) so you don't have to go back to the actual failed drive, which is likely getting worse each time you access it. Next you can run whatever rescue software you like on the failed.img file to see if you can recover anything. I usually start off with something simple like fsck before trying testdisk. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554cdffe.3090...@torfree.net
Re: Debian 8 no network...
On 2015-05-08, Stephen Allen marathon.duran...@gmail.com wrote: apt-cache search update manager Doesn't find anything that sounds right, either. What are you running? Perhaps he meant 'update-notifier' that's in Jessie? curty@einstein:~$ apt-cache search update | grep manager | grep gnome update-manager-gnome - GNOME application that manages software updates -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmkprjg.320.cu...@einstein.electron.org
Re: Vertaling Debian Jessie
On Fri, 08 May 2015 11:53:47 +0200, Paul van der Vlis p...@vandervlis.nl wrote: Welke desktop? Gnome, KDE, Xfce, Openbox, LXDE, ... ? Ik dacht MATE. Hoe zou je kunnen bepalen welke desktop iemand heeft, als deze dat zelf niet weet? Het verhaal zit zo in elkaar: ik heb een netinstall CD afgehaald en van daaruit enkele desktops geïnstalleerd. Ik heb er verschillende geprobeerd tot ik de (voor mij) beste gevonden heb. Waar ik nu mee werk is Xfce. Dat is dan ook de reden waarom ik schreef: 'Ik dacht MATE'. Ik zal binnenkort een nieuwe VM als test installeren met MATE er op en zien of het die versie inderdaad was. -- To UNSUBSCRIBE, email to debian-user-dutch-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8arpkaha22ph0u4i4arkbtg5rdjm59q...@4ax.com
Re: Verificando portas abertas
Olá. Eu faço isso há um tempo e dá diferentes portas abertas a cada rodada de teste. Pensei ser um falso positivo do nmap, tipo ele mesmo escaneando as portas que ele mesmo abre prá enviar pacotes de teste pro endereço de rede da interface eth0 ou da interface de loopback lo. Ou é isso ou paranoia.mode=on. netstat não acusa essas portas abertas. Mais alguma possibilidade sem ser problema de segurança? Em Fri, 08 May 2015 01:13:39 -0300 Thiago Zoroastro thiago.zoroas...@bol.com.br escreveu: Olá a todos, estive verificando as portas do Debian. Me deparei com 1 unknown na porta 58080 depois de testar vários comandos que fui encontrando na internet. # nmap -sN IP.000.000.000 Starting Nmap 5.00 ( http://nmap.org ) at 2015-05-08 01:07 BRT All 1000 scanned ports on (IP.000.000.000) are open|filtered Nmap done: 1 IP address (1 host up) scanned in 21.44 seconds # nmap -sS IP.000.000.000 Starting Nmap 5.00 ( http://nmap.org ) at 2015-05-08 01:08 BRT Interesting ports on (IP.000.000.000): Not shown: 999 filtered ports PORT STATE SERVICE 58080/tcp open unknown Nmap done: 1 IP address (1 host up) scanned in 7.85 seconds Troquei o IP para IP.000.000.000 na mensagem. Estaria a porta 58080 sendo utilizada de forma invasiva por outra pessoa ou isto é normal? Tentei encontrar e não achei a utilidade da porta 58080, na verdade encontrei mas não compreendi. -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/404907.44724...@smtp209.mail.gq1.yahoo.com
Re: Help with ddrescue
On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave complete; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
problema de acceso a disco USB
Hola gente: Luego de actualizar a Jessie, cuando conecto el disco externo USB aparece el aviso y cuando selecciono abrir con el navegador de archivos (es en KDE) da un error: No se puede ejecutar la orden indicada. El archivo o carpeta file:///media/wodari/Samsung1Tb no existe. En Wheezy no tenía este problema. Si hago un ls -l en /media/wodari me muestra: root@debi5:/media/wodari# ls -l ls: no se puede acceder a Samsung1Tb: Error de entrada/salida total 0 d? ? ? ? ?? Samsung1Tb Un dmesg: [154435.129561] usb 2-2: new high-speed USB device number 11 using xhci_hcd [154435.199553] usb 2-2: New USB device found, idVendor=04e8, idProduct=61b6 [154435.199558] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [154435.199561] usb 2-2: Product: Samsung M3 Portable [154435.199564] usb 2-2: Manufacturer: Samsung M3 Portable [154435.199566] usb 2-2: SerialNumber: 5F7E7DE60C00012A [154435.200841] scsi13 : usb-storage 2-2:1.0 [154436.195666] scsi 13:0:0:0: Direct-Access Samsung M3 Portable 1301 PQ: 0 ANSI: 6 [154436.197051] sd 13:0:0:0: Attached scsi generic sg4 type 0 [154436.198103] sd 13:0:0:0: [sdd] Spinning up diskready [154437.200587] sd 13:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [154437.200909] sd 13:0:0:0: [sdd] Write Protect is off [154437.200914] sd 13:0:0:0: [sdd] Mode Sense: 33 00 00 08 [154437.201244] sd 13:0:0:0: [sdd] No Caching mode page found [154437.201248] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.202511] sd 13:0:0:0: [sdd] No Caching mode page found [154437.202516] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.228143] sdd: sdd1 [154437.229430] sd 13:0:0:0: [sdd] No Caching mode page found [154437.229434] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.229438] sd 13:0:0:0: [sdd] Attached SCSI disk El disco tiene una única partición NTFS. No está referenciado en /etc/fstab Si ejecuto cfdisk /dev/sdd me muestra la partición NTFS. Cuál podrá ser el problema ? Saludos y gracias, -- Walter O. Dari http://swcomputacion.com/ https://facebook.com/swcomputacion/ skype: waomda -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d00f6.1010...@swcomputacion.com
Re: Help with ddrescue
On 08/05/15 02:32 PM, German wrote: On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave complete; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. Hopefully the file system is repairable which will make this possible. If the file system isn't, you need a third drive to hold recovered files. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d050f.9050...@torfree.net
Re: Help with ddrescue
On 05/08/2015 at 02:48 PM, Gary Dale wrote: On 08/05/15 02:32 PM, German wrote: On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wande...@fastmail.fm wrote: Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. In my experience, single-pass recovery like this does not work very reliably or very well; it also doesn't let you make the backup copy you originally suggested, which is a good idea if you have the space (though I never have had). It's technically possible, yes, but I wouldn't want to trust or rely on it in any case where the source device is potentially prone to failure - and in any scenario where it isn't, you're unlikely to want to use one of the *rescue tools in the first place. (There's also the consideration of finding space for the ddrescue log file if you're restoring directly to the identical-size device; that file that may not be as important in some scenarios, but I wouldn't want to try to do such a rescue without one.) Hopefully the file system is repairable which will make this possible. If the file system isn't, you need a third drive to hold recovered files. That's another point, yes; if the filesystem isn't directly repairable, you may have to use forensic tools to dig in and recover data, and at that point it's just easier to work with a separate file IMO. I certainly wouldn't say there are never times when direct device-to-device recovery like that is appropriate, but I haven't encountered one and I would not recommend it as a base-practices procedure. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Jessie o no Jessie
Hola: Estic dubtant entre actualitzar el wheezy que tinc o esborrar-lo i instal·lar el jessie de nou en nou. Tinc el directori home en un disc diferent del de sistema, que el puc deixar inactiu perquè no es perdi res a l'hora d'instal·lar (ja ho he fet en altres ocasions), i un cop feta la instal·lació recarregar les quatre aplicacions que tinc i santes pàsqües. Dubte: He començat a fer la declaració de renda d'aquest any i oh miracle! m'ha funcionat amb Debian. Per allò que diuen si funciona no lo toques potser que esperi a presentar la declaració per fer la migració a Jessie, no? En fi, gràcies per la vostra ajuda. -- Daniel Elias Usuari de Linux nº 461584 -- To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d09d9.8070...@familiaeliasgavernet.cat
Re: Default virtualhost on Debian Jessie with Apache 2.4.10
Marco Stoecker wrote: Bob Proulx wrote: I am unable to recreate your problem on wheezy. I just now installed ... Go back and double check everything. But what happens to the mailman site, if I disable listening on port 80? Will the mailman site still be available? (Me rattles my head and goes, What?) Daniel Bareiro submitted the problem that he could not disable the default web server on port 80. That has been the topic of this thread. Later you posted that you had the same issue. I see now that you did say you wanted to have the mailman site enabled. I didn't see that before since we were focused on Daniel's problem of trying to disable the port 80 web site. Obviously that is impossible. One cannot both disable the port 80 web site and keep it enabled for Mailman. It is one or the other. It cannot be both. And this is a completely different topic than the we one were discussing. That is why there was confusion. In the future if you want to avoid confusion about such things then start a new discussion thread with new topic. Something like, How do I make Mailman the default and only web site? or some such. That would get much better results. On the topic of making the Mailman web interface the default and/or only web site seen: If you want to keep the Mailman web site as the default then do not disable port 80. You will be needing it. Instead make the Mailman web site the default web site. If you are using Apache there are two main ways to do this. One is to ensure that the default site is the first or only VirtualHost listed. Either way then it will be the default site. That is rationale behind the 000-default naming in that the zeros will cause that to be loaded first and therefore will be the default by default. My preference is to remove the 000-default link and keep the original 000-default.conf and default-ssl.conf files pristine. (Previously those were default and default-ssl in Wheezy 7. They have been renamed in Jessie 8.) By keeping those files pristine they will not be prompted for merging upon upgrades. This makes upgrades easier. Then create a new site local file for the local web site configurations. Being a different file it will not be in the package and will not need to be merged when applying security upgrades. The other way from having the 000 naming to force the first configuration to be the default is to use the _default_ tag on one site to explicitly say which is the default. Then the ordering does not matter. This will explicitly tell Apache that it should be the default for all unspecified sites. This is documented here: https://httpd.apache.org/docs/2.4/vhosts/examples.html#default Bob signature.asc Description: Digital signature
Re: Jessie o no Jessie
2015-05-08 21:09 GMT+02:00 Daniel dan...@familiaeliasgavernet.cat: Hola: Estic dubtant entre actualitzar el wheezy que tinc o esborrar-lo i instal·lar el jessie de nou en nou. Tinc el directori home en un disc diferent del de sistema, que el puc deixar inactiu perquè no es perdi res a l'hora d'instal·lar (ja ho he fet en altres ocasions), i un cop feta la instal·lació recarregar les quatre aplicacions que tinc i santes pàsqües. Dubte: He començat a fer la declaració de renda d'aquest any i oh miracle! m'ha funcionat amb Debian. Per allò que diuen si funciona no lo toques potser que esperi a presentar la declaració per fer la migració a Jessie, no? Jo també ho faria, no tocar fins presentar-la. L'he poguda presentar, usant certificats, i des de Jessie! En el meu cas, també m'ha funcionat (el programa s'executa). Ara bé, la funcionalitat que volia (importar dos esborranys en una mateixa declaració, la segona importació no la deixava fer. Hisenda em va dir que en la següent versió funcionaria, i ni així. Val a dir que la màquina on estava ja era jessie de fa temps. Pel que fa a el pas a jessie,m'he trobat dues incidències: - a una màquina feia servir gdm + xfce i l'actualització no iniciava bé xfce des del gdm. Canviat de gdm a lightdm i perfecte. - a una altra, ntop no s'actualitzava bé per mal lligam amb un paquet relacionat. Un cop desinstal·lat, la configuració dels paquets pendents del dist-upgrade van funcionar perfectament. En fi, gràcies per la vostra ajuda. -- Daniel Elias Usuari de Linux nº 461584 -- To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d09d9.8070...@familiaeliasgavernet.cat -- -- Salutacions...Josep -- -- To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/capbo7tavbs2pfjbb6xrcqqgba2z8vkbrxb2p06fgd1rt7gc...@mail.gmail.com
need help with approx-gc
I run approx on one of my local jessie machines. The approx installation is strictly by using the approx deb, which includes a weekly run of approx-gc , which should just clean out the local repository of debs that are no longer useful. But approx-gc has started reporting I/O errors. I suppose I could just delete the repository and let my future use of aptitude refil it, but I'd like to start learning how to deal with this with a little more finesse. I suppose that I might be able to run approx-gc in some sort of debug mode, and discover what file or directory is giving it trouble. So far I have run manually which gives: root@cmn:~# approx-gc -s -v [ security/dists/jessie/updates/non-free/source/Sources.bz2 ] [ security/dists/jessie/updates/non-free/binary-i386/Packages.bz2 ] [ security/dists/jessie/updates/contrib/source/Sources.bz2 ] [ security/dists/jessie/updates/contrib/binary-i386/Packages.bz2 ] [ security/dists/jessie/updates/main/source/Sources.bz2 ] [ security/dists/jessie/updates/main/binary-i386/Packages.bz2 ] Input/output error root@cmn:~# I am running with a single large (160GB) root partition that is 7% in use. Is there a standard sysadmin procedure for diagnosing this? Best Regards, -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508174703.ga1...@big.lan.gnu
Re: Help with ddrescue
On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 01:20 PM, German wrote: On Fri, 08 May 2015 12:10:38 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 10:32 AM, German wrote: Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 would be the partition that you want to recover. Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Once again, thanks for such a complete instructions. So, if failed drive is for instance /dev/sdb and spare drive is for isntance /dev/sdc, the right command will be ddrescue if=/dev/sdb of=/dev/sdc/failed.img ? No. With ddrescue, you do not (want to) create a new filesystem directly on the new device. What you want to do is create a filesystem _image_, in a file which is stored on the new device. Step-by-step, what you do is: * Create a filesystem on your good drive (/dev/sdc). You can use any filesystem you want. * Mount the newly created filesystem somewhere. For example, if you want to mount it to the empty directory '/mnt/new_disk', you could run the command: mount /dev/sdc1 /mnt/new_disk * Run the command ddrescue /dev/sdb /mnt/new_disk/sdb_failed.img /tmp/sdb_failed.ddrescuelog Note that this will create _two_ files: the rescued filesystem image, and a log file which ddrescue uses to keep track of what it has already successfully rescued and where it has encountered errors. This second file will take up additional space. * If you have enough free space, copy the resulting sdb_failed.img to a separate location, so you have a backup copy if something goes wrong. * Run recovery tools (starting with fsck, as Gary Dale suggested) on sdb_failed.img, and see how much you can recover. * Mount sdb_failed.img, using a loopback mount, and copy out whatever files you can to a new location. Recovering data from a failed drive using ddrescue, dd_rescue, or myrescue is entirely possible; I've done it myself. However, it is not trivial, and in my experience the process requires considerably more space than the size of whatever drive is being rescued. Personally, I would probably recommend the use of myrescue rather than of ddrescue or dd_rescue, but any of them can work if you use them right. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508141619.37003...@asterius.asterius.net
Re: Help with ddrescue
On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave complete; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508143219.07338...@asterius.asterius.net
Re: Help with ddrescue
No. With ddrescue, you do not (want to) create a new filesystem directly on the new device. What you want to do is create a filesystem _image_, in a file which is stored on the new device. Step-by-step, what you do is: * Create a filesystem on your good drive (/dev/sdc). You can use any filesystem you want. * Mount the newly created filesystem somewhere. For example, if you want to mount it to the empty directory '/mnt/new_disk', you could run the command: mount /dev/sdc1 /mnt/new_disk * Run the command ddrescue /dev/sdb /mnt/new_disk/sdb_failed.img /tmp/sdb_failed.ddrescuelog Note that this will create _two_ files: the rescued filesystem image, and a log file which ddrescue uses to keep track of what it has already successfully rescued and where it has encountered errors. This second file will take up additional space. As someone just reading this list for my own info, I found the above explanation quite helpful. It is a combination of a detailed example and a tutorial. It provides clarity instead of what often might just be considered helpful(???) hints as to what is required. Thank you!! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d0110.1030...@aim.com
Re: Help with ddrescue
On Fri, 08 May 2015 14:48:47 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:32 PM, German wrote: On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave complete; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? Hopefully the file system is repairable which will make this possible. If the file system isn't, you need a third drive to hold recovered files. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508145623.35846...@asterius.asterius.net
Re: Live Build - Panneau de controle cinnamon sans paramètres régionaux
Bonjour à tous les utilisateurs et développeurs de Debian : Le mardi 5 mai 2015 à 21:20, kayl kayl.k...@laposte.net a écrit : j'ai créé une Debian Live avec le bureau cinnamon. Le problème c'est que lorsque je vais dans le panneau de contrôle,je trouve tout sauf l'icône des Paramètres régionaux. Je n'ai pas de solution à te proposer mais peux-tu exposer ton problème à la liste de discussion dédiée au Debian Live : debian-l...@lists.debian.org ? Cette liste est - apparemment - entièrement en anglais mais, pour peu que tu maîtrises cette langue, je pense que tu as plus de chance de se voir proposer des solutions à ton problème. :-) Je te donne le lien te permettant de souscrire à cette liste : https://lists.debian.org/debian-live/ Cordialement et à bientôt, Stéphane. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/201505082014.56739.stephane.garg...@gmail.com
Re: Help with ddrescue
On Fri, 8 May 2015 21:35:56 +0100 Lisi Reisz lisi.re...@gmail.com wrote: On Friday 08 May 2015 21:09:42 German wrote: What will happen when I duplicate drive? Why is that failed drive is failed and duplicated drive might be repairable? If it's duplicated, it will be exactly the same, no? Yes, that is the point. If there is something wrong with the disk then every time you read it you may be making it worse. Every time you read it it may be the last time you can. And it has your precious data on. So TAKE A COPY WHILE YOU CAN. If the data are really precious take two copies. Then work on a copy. If you are working on it, you may destroy it or anyhow damage it. If you are doing it to the one and only original that would matter. Do it to a copy. Make all the attempts you want on the copy. You still have the original if something goes wrong. Confused. And bad drive is physically ok I think, it is just something wrong with file system. You could still lose or damage the files in the process of recovery. Besides, how sure are you that it is not the drive? How precious are the data? MTF? ? Mean time to failure?? Lisi Well, data is pretty much precious to me. Studios flacs of rare and hard to get music. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508164002.718c5...@asterius.asterius.net
Re: Help with ddrescue
On Fri, 08 May 2015 16:51:20 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 04:34 PM, German wrote: On Fri, 08 May 2015 16:27:22 -0400 The Wanderer wande...@fastmail.fm wrote: What leads you to conclude that the drive is OK and the filesystem is what is bad? What errors are you seeing, in what situations? Error mounting /dev/sdc1 at /media/spore/FreeAgent GoFlex Drive: Command-line `mount -t ntfs -o uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177 /dev/sdc1 /media/spore/FreeAgent GoFlex Drive' exited with non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read of MFT, mft=17625 count=1 br=-1: Input/output error Inode is corrupt (5): Input/output error Index root attribute missing in directory inode 5: Input/output error Failed to mount '/dev/sdc1': Input/output error Input/output error in this sort of context usually means that the drive itself is failing, not the filesystem. (Or that something else in the connection between the system and the drive is faulty; I've seen it happen with bad SATA/IDE cables, and for that matter with cables which were just loose.) Just to confirm, this happens on any mount attempt, correct? Yes, this happens on mount attempt. I still don't think that drive is failing and I think cables are ok too. It's happened when I was installing Lubuntu. During the install, install program obviously probed all available drives, and did something nasty to the drive. NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. If you have a suitable Windows system with which to try the suggested 'chkdsk /f' and double reboot-into-Windows approach, you could do that, but I wouldn't bet on it helping - and if the drive really is failing, then trying to access the drive that way might make things worse. I think it looks as if the drive really is failing, and the separate, larger drive ddrescue/dd_rescue/myrescue approach is the right way to go after all. (Also note that since the filesystem is on /dev/sdc1, you'll almost certainly want to apply your ddrescue command to source that node, not the higher-level /dev/sdc node. You _can_ recover the data from a copy of /dev/sdc, but it's significantly less trivial.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508165812.723cb...@asterius.asterius.net
jessie selinux reference policy package missing
I installed the new Jessie version of debian on a VirtualBox system, and had no problems with the installation. Because I wanted to do work with the SELinux policy I wanted to first make sure that the system would run with SE Linux to provide a platform on which to experiment with the policy. I obtained most of the SELinux packages that I think I needed and/or wanted, selling-utils, selinux-basics etc. Then, per existing documentation on setting up SELinux on a Debian system I attempted to get the selinux-policy-default via 'apt-get install selinux-policy-default' and was told E: Package 'selinux-policy-default' has no installation candidate'. Looking around I find one for Wheezy and for SID but not for Jessie. Given the fact that jessie was just released a few weeks ago, I'm guessing that the jessie policy package simply was not completed yet. But since I really want to have the source so I can experiment with building the policy and generally gain more knowledge of that process, I went looking around looking for a GIT repository that might have the current state of the Debian default and/or reference policy work in it. I found one that I obtained form 'git://anonscm.debian.org/selinux/refpolicy.' This looked promising until I attempted to build it with the command 'debian/rules build-default-policy'. The command makes significant progress but dies with 'make[1]: *** No rule to make target system.if, needed by 'tmp/all_interfaces.conf' I find that the systemd module files are indeed not in the repository that I have, while working on the debian branch. I do however find reference to the systemd module's policy files located in a debian/patches/0050-systemd. But the files identified in this patch file do not exist in the git source repository but because debian/build.conf.default file contains information saying that the systemd module is to be contained in the base module, the build fails. The git repository logs shows commits that modified the file policy/modules/system/systemd.if, and policy/modules/system/systemd.te, yet as content within the patches/0050-systemd file. So there must be some steps that I don't know about and have not found that would tell the attempted build to apply the various patches to the repository before it proceeds with the build. I would appreciate any information that you could provide on the status of the Jessie policy package, both binary and source. I would also really like to know how to utilize the git repository that I have to actually build a jessie compatible policy, and perhaps my own jessie package policy package as I suspect what I will end up doing is having one system for policy experimentation and the other for a policy development system that I'd like to run with the initial state, (hopefully a stable state), that I can build form the initial state of the repository that I have. Spence
Re: Help with ddrescue
On 08/05/15 02:56 PM, German wrote: On Fri, 08 May 2015 14:48:47 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:32 PM, German wrote: On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave complete; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? With the drive duplicated, run fsck on the new drive. Hopefully the file system will be repairable. If it isn't, you can run testdisk or whatever to try to rescue files to another device (not the original, bad drive). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d15c5.3000...@torfree.net
Re: no root file system after encryption
David Christensen wrote: Juha Heinanen wrote: On Partition settings screen, I choose Use as Ext2, Mount point /boot, and Bootable flag on. Then I choose Done setting up the partition. Why ext2? I use ext4. I always use and recommend ext2 for /boot. It avoids wasting space in the ext3/ext4 journal that isn't needed on such a small and seldom modified partition. Also fsck speed for a small 512M ext2 is very fast without needing a journal to speed it up. For /boot ext2 is a good choice. It is fully supported everywhere for rescue boot media. Of course now that we have large disks and can easily allocate 512M to /boot without significantly reducing the remainder of the disk this hardly matters. Basically we are overflowing with disk space and therefore need not be as efficient with it these days. Wasting some space with ext3/ext4 has become a very small matter. Bob signature.asc Description: Digital signature
Re: no root file system after encryption
Juha Heinanen wrote: Bob Proulx writes: Why no LVM? Using LVM is the way I always do it because that allows I didn't have any particular reason to avoid LVM. I just tried if encrypted installation succeeds without it. Now that I tried with LVM, installation was simple and worked without issues. Yes. I was thinking that might improve the experience. :-) Good. One thing that I noticed was that LVM option uses by default ext2 for /boot, whereas some people on the list suggested ext4. So I manually changed that. Oh well. As you saw I had the opposite recommendation. I always use and recommend a ext2 /boot. However also note that I wrote that these days with a moderately sized 512M /boot that the difference is hardly worth discussing. I wouldn't change it after having done it. (Although since it is a separate partition it is trivial to do so.) Glad to hear you have things going for you. Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 16:00:05 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:56 PM, German wrote: On Fri, 08 May 2015 14:48:47 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:32 PM, German wrote: On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave complete; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? With the drive duplicated, run fsck on the new drive. Hopefully the file system will be repairable. If it isn't, you can run testdisk or whatever to try to rescue files to another device (not the original, bad drive). What will happen when I duplicate drive? Why is that failed drive is failed and duplicated drive might be repairable? If it's duplicated, it will be exactly the same, no? Confused. And bad drive is physically ok I think, it is just something wrong with file system. MTF? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508160942.50070...@asterius.asterius.net
Re: bad ABI version?
Sven Hartge wrote: If you know, how to pull yourself out of the mud, are able to file bug reports, read bug reports und know how to use apt-listchanges and apt-listbugs, _then_ you can use Sid. (Been doing that for over 15 years myself.) (Chuckle.) I'm good to go. Specifically the reason I am using Sid Unstable is so that I get the early preview of what is happening in Testing. Then I can avoid the bugs there and Stable and can file bugs and work to get things fixed before they enter Stable. Unfortunately one person's bug is another person's feature and therefore we are not completely in agreement over what ends up in Stable. But participating in the process is much better than being only a passenger on it. If one wants to use Sid, he/she should know about the following things: - how to boot your system from a rescue medium (and have one ready) - how to unpack a DEB without using the Debian tools and only with ar - how to identify a broken library and revert to a working one - be able to interpret linker error messages - know where to find the relevant system log files and how to read them - how to pin pacakges to a specific version - know about snapshot.debian.org - tracker.debian.org - https://release.debian.org/transitions/ - how to rebuild a package using pbuilder/cowbuilder/sbuild - debug packages and basic GDB usage - reportbug - generally understand how a Linux boot works If one needs an always working system, she/he better stick with Stable or Testing (as soon as it has cooled down enough). Agreed to most! Generally in concept anyway. Some of the details vary. :-) I am not a fan of pinning. Generally people try to use it to keep a mixed system. My opinion is that way leads to madness. Building packages does not *require* pbuilder/cowbuilder/sbuild but being able to build your own packages by some method is a very useful and needed skill. I would probably add other skills to the list such as being able to use either apt-get or aptitude (my preference is apt-get and friends) at a deep level to upgrade and downgrade when the system needs manual attention for it. Other things too. Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On Friday 08 May 2015 21:40:02 German wrote: Well, data is pretty much precious to me. Studios flacs of rare and hard to get music. Then I would take at least one copy, preferably two, and work on a copy. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082155.43457.lisi.re...@gmail.com
Re: Help with ddrescue
On Friday 08 May 2015 21:51:17 German wrote: Problem I have now is the lack of money. I simply don't have money now to buy yet another drive. Well, you can use what you have got and risk it. Or you can wait a bit. Assuming that the financial situation might ease. But I would think carefully before doing anything that just might, however unlikely it be, but just might, destroy or damage your music files, if they are precious to you. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082202.38563.lisi.re...@gmail.com
Re: problema de audio en debian 8 Jessi [solucionado]
El 8/5/15, Camaleón noela...@gmail.com escribió: El Fri, 08 May 2015 13:35:20 +0200, Ala de Dragón escribió: El 7/5/15, Camaleón noela...@gmail.com escribió: (...) $ vlc -v --aout alsa /home/linux/Escritorio/test.mp4 VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42) ^^^ No me había fijado en eso. Homenaje merecido :-) Supongo que haran referencia a http://es.wikipedia.org/wiki/Terry_Pratchett La de novelas novelas suyas que han pasado por mis manos ^_^ Y tan bien merecido. Hum... si tienes curiosidad, elimina ese paquetico que tenías instalado vlc-plugin-pulse a ver qué sucede. Saludos, Mañana con mas tiempo le pego un vistazo, tendré que romper las decencias y demás parafernalia. De todos modos por lo que he leído en upstream viene integrado de fabrica en VLC. Tiene mas que ver con opciones de empaquetamiento de las fuentes y compilación de binarios, que ese paquete. -- Camaleón Salu2 y buen finde a todos :D -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2015.05.08.13.38...@gmail.com -- El cielo es para los dragones lo que el agua es para las ninfas -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ca+924hr_jdoappfnjwvhpmbt4zre8804wf8-+csm0kggo...@mail.gmail.com
Re: Help with ddrescue
On 05/08/2015 at 04:09 PM, German wrote: On Fri, 08 May 2015 16:00:05 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:56 PM, German wrote: What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? With the drive duplicated, run fsck on the new drive. Hopefully the file system will be repairable. If it isn't, you can run testdisk or whatever to try to rescue files to another device (not the original, bad drive). What will happen when I duplicate drive? Why is that failed drive is failed and duplicated drive might be repairable? If it's duplicated, it will be exactly the same, no? Confused. And bad drive is physically ok I think, it is just something wrong with file system. MTF? If the bad drive is physically OK, then ddrescue is probably not needed. ddrescue, and the similar *rescue tools, are only for recovering as much data as possible data when you can't use plain dd because the drive itself is producing errors in some sectors. (You still can't recover data from those sectors, but you can generally get the rest.) If the drive is OK but the filesystem is bad, then you need to use other tools for data recovery. Exactly what those tools would be will probably depend on what filesystem is involved; if fsck doesn't work, then it will probably involve advanced manual techniques which we (or, at least, I) could not talk you through via E-mail. If you want to copy the bad filesystem for analysis and/or dissecting, then as long as the drive is OK, you should be able to do it using plain dd - no need for ddrescue or any such thing. What leads you to conclude that the drive is OK and the filesystem is what is bad? What errors are you seeing, in what situations? -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Friday 08 May 2015 21:09:42 German wrote: What will happen when I duplicate drive? Why is that failed drive is failed and duplicated drive might be repairable? If it's duplicated, it will be exactly the same, no? Yes, that is the point. If there is something wrong with the disk then every time you read it you may be making it worse. Every time you read it it may be the last time you can. And it has your precious data on. So TAKE A COPY WHILE YOU CAN. If the data are really precious take two copies. Then work on a copy. If you are working on it, you may destroy it or anyhow damage it. If you are doing it to the one and only original that would matter. Do it to a copy. Make all the attempts you want on the copy. You still have the original if something goes wrong. Confused. And bad drive is physically ok I think, it is just something wrong with file system. You could still lose or damage the files in the process of recovery. Besides, how sure are you that it is not the drive? How precious are the data? MTF? ? Mean time to failure?? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082135.56101.lisi.re...@gmail.com
Re: construction d'un .deb pour un noyau avec une config locale [1/2 RÉSOLU]
Bonjour à toutes et à tous et plus précisément à Erwan et Maderios, De: Erwan David Ça fait longtemps que je n'ai pas compilé de noyau, mais as-tu regardé make-kpkg ? http://www.parinux.org/content/debian-compiler-son-kernel-sous-debian-avec-make-kpkg Merci pour le pointeur Erwan, je vais y jeter un œil. De: Maderios Je compile tous mes noyaux de la façon suivante sur Jessie et Sid. Raison principale: désactiver tout ce qui est inutile et obtenir un vrai noyau patché 'real-time' (l'outil 'ketchup' pour télécharger et patcher est d'ailleurs génial) Décompression du paquet source dans /usr/src Configuration avec make menuconfig Puis par exemple dans /usr/src/linux-3.14.38-rt36/ je lance: make-kpkg --jobs 9 kernel_image --initrd C'est tout, et le paquet .deb est disponible à la fin dans /usr/src Merci pour les infos. Comme dit plus haut, je vais aller jeter un oeil sur la compilation noyau à l'aide de make-kpkg. J'ai donc utilisé cette méthode avec la les règles kernel_image et kernel_headers, ce qui me fourni bien les 2 paquets .deb comme avec la méthode make deb-pkg que j'utilisais auparavant, ceci dit, cette précédente méthode me fournissait également un paquet linux-libc-dev. Je ne suis pas certain de ce que représente exactement ce paquet et du coup, je ne suis pas certain qu'il me faille en fabriquer une et si oui, de comment faire ça. De ce que je pense en avoir compris, le paquet linux-libc-dev fourni la bibliothèque de fonctions les plus basses d'un système linux et j'aurai donc tendance à penser qu'il est de bonne augure d'avoir cette bibliothèque de fonction qui corresponde exactement au noyau installé. J'ai lu pas mal de documentation à propos de cette libc dessus depuis mon précédent message, et soit mes lectures étaient de trop au niveau pour mes connaissances (cad: je n'y ai pas compris grand chose), soit ce que je lisais ne semblait pas correspondre à ma question plus haut. Si quelqu'un peut éclairer ma lanterne, ça sera très apprécié. Cordialement, Olivier -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: https://lists.debian.org/1877915621.1054928823.1431118657161.javamail.r...@zimbra61-e11.priv.proxad.net
Re: Help with ddrescue
On Friday 08 May 2015 21:58:12 German wrote: It's happened when I was installing Lubuntu. Post hoc doesn't necessarily imply propter hoc. http://en.wikipedia.org/wiki/Post_hoc_ergo_propter_hoc Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082205.40946.lisi.re...@gmail.com
Re: Help with ddrescue
On Fri, 8 May 2015 15:00:13 -0600 Bob Proulx b...@proulx.com wrote: German wrote: Bob Proulx wrote: There is an idea that I didn't see proposed as I read through this thread. If one had three same sized drives then there is another possibility. Problem I have now is the lack of money. I simply don't have money now to buy yet another drive. I took out one drive from my another system, bought usb external enclosure and thought I'll succeed. Hmm.. everything is just not as easy as it seems. I think I read that you have one identically sized drive, yes? I am not sure where you are sitting with regards to the other suggestions. But at the least I would make one good backup as soon as possible. And it seems that possibly you have the capability at this time? Yes, I do have two identical 2TB drives. So, you are advising to make a back up. Something like ddrescue if=/dev/sdX of=/dev/sdY ? On the backup it might be possible (not sure how advised it would be) but possible to mount it read-only and then read files from it. The copy would have had errors and therefore the file system would probably be somewhat damaged. But mounted read-only I presume there would be no more changes to it. Might be possible to copy the files that could be recovered from the read-only media off elsewhere over the network or to other places. That might get you a lot of what you need within the limits that you have. Good luck! Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508171020.8...@asterius.asterius.net
Re: ACPI y smsc47m1
Eliminé la línea acpi_enforce_resources=lax del archivo /etc/default/grub, dejándolo como al principio. Actualice el grub, y al reiniciar, en la información sobre la carga del sistema, volvió a aparecer el mensaje de Error, por no poder cargar el módulo smsc47m1, como estábamos al principio. ¿A qué mensaje de error te refieres exactamente? ¿Funciona lm-sensors? Tal vez no utilicé los términos correctos... a ver si me explico mejor... Al reiniciar, y antes de que se inicie el ambiente gráfico, se cargan los módulos de kernel y drivers necesarios para hacer funcionar los dispositivos conectados. Es aquí, donde es posible leer rápidamente en una línea, algo referente a: Error inserting smsc47m1... Device or resource busy A esto es lo que me refiero. lm-sensors si funciona, puesto que tengo conky-all instalado y corriendo monitoreanso cada 5 s, y al llamar en terminal la salida de sensors, obtengo: tesistas@Tesistas:~$ sensors adm1025-i2c-0-2d Adapter: SMBus I801 adapter at efa0 in0: +2.49 V (min = +0.00 V, max = +3.32 V) Vcore:+1.71 V (min = +0.00 V, max = +2.99 V) +3.3V:+3.25 V (min = +2.97 V, max = +3.63 V) +5V: +5.16 V (min = +4.50 V, max = +5.50 V) VCC: +3.32 V (min = +2.97 V, max = +3.63 V) CPU Temp: +42.0°C (low = +0.0°C, high = +127.0°C) M/B Temp: +37.0°C (low = +0.0°C, high = +127.0°C) cpu0_vid:+1.750 V adm1031-i2c-0-2c Adapter: SMBus I801 adapter at efa0 fan1: 0 RPM (min = 330 RPM, div = 8) fan2:4218 RPM (min = 330 RPM, div = 8) M/B Temp: +37.5°C (low = +0.0°C, high = +80.0°C) (crit = +81.0°C) temp2:+35.1°C (low = +0.0°C, high = +80.0°C) (crit = +81.0°C) temp3:+41.2°C (low = +0.0°C, high = +80.0°C) (crit = +81.0°C) --- Para verificar: root@Tesistas:/home/tesistas# /etc/init.d/kmod stop Volví a hacer root@Tesistas:/home/tesistas# sensors-detect y root@Tesistas:/home/tesistas# /etc/init.d/kmod start [info] Loading kernel module loop. [info] Loading kernel module sg. [info] Loading kernel module adm1025. [info] Loading kernel module adm1031. [info] Loading kernel module smsc47m1. ERROR: could not insert 'smsc47m1': Device or resource busy [info] Loading kernel module adm1025. [info] Loading kernel module adm1031. [info] Loading kernel module smsc47m1. ERROR: could not insert 'smsc47m1': Device or resource busy --- Será que deberé dejar el grub modificado (con la línea acpi_enforce_resources=lax)? Según la documentación de lm-sensors (ver más abajo) podría ser peligroso. En el enlace anterior que sugeriste, estaba indicada esa documentación y la leí, pero en ella se refiere a cuando se detiene sensors... y este no es el caso. - Piensas si no te convendría mejor usar otro monitor de sensores o intentar cargar otro módulo en lm-sensors genérico. Sobre usar otro módulo genérico, la verdad no sé nada de ello. Tendría que investigar más. 1) Atendiendo a una sugerencia anterior sobre usar el kernel 3.16 desde los backports para probar si se resolvía este fulano conflicto de ACPI, y 2) aprovechando que estoy instalando playonlinux-wine, y anteriormente este último no se podía usar por falta de instalar dlls, y esto por problemas de dependencias en Debian con el paquete p11-kit-modules:i386, decidí actualizar todo a wheezy-backports. Hice esto: $ sudo aptitude update $ sudo aptitude upgrade $ sudo aptitude -t wheezy-backports safe-upgrade $ sudo aptitude upgrade $ sudo aptitude safe-upgrade $ sudo aptitude full-upgrade Reinicié el sistema. Luego: $ sudo aptitude purge $(deborphan --gues-all) $ sudo aptitude autoremove $ sudo aptitude autoclean Arrancando ya con el kernel 3.16.0-0.bpo.4-686-pae, pude leer la misma línea al cargar módulos: Error inserting smsc47m1... Device or resource busy Al hacer: $ dmesg | tail [ 17.879580] FS-Cache: Loaded [ 17.951326] FS-Cache: Netfs 'nfs' registered for caching [ 18.091008] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 24.489728] lp0: using parport0 (interrupt-driven). [ 53.137423] fuse init (API version 7.23) [ 1508.874684] perf interrupt took too long (2514 2500), lowering kernel.perf_event_max_sample_rate to 5 [ 3488.201220] perf interrupt took too long (5027 5000), lowering kernel.perf_event_max_sample_rate to 25000 [ 3814.805633] smsc47m1: Found SMSC LPC47M10x/LPC47M112/LPC47M13x [ 3814.805661] ACPI Warning: SystemIO range 0x0804-0x0804 conflicts with
Re: Broken package can't be configured, can't be uninstalled
Mark Allums wrote: I have some packages that did not install correctly. One in particular is giving me fits. It can't be upgraded. It can't be removed. It can't be reinstalled. It can't be reconfigured. The error message states that it is in an inconsistent state and needs to be reinstalled before it is removed. But Debian has removed that version from the repository and I can't find it to download, even for a manual install. I need to either remove it by hand or install the new version (by hand if necessary), or something else, if the collective mind of the list knows a better solution. How do I locate the correct version? Until this is resolved, I can't update my system. Help! Help us to help you. Please cut and paste verbatim the entire text of the exchange. That way we can see both the packages involved and the error messages produced. If you are using a graphical tool then please get the verbatim messages from a text window. We need the text and not a screenshot image. (Never send screenshot images.) Open a text window, become root, and run the command there. One of these probably: # apt-get upgrade # apt-get dist-upgrade # apt-get remove FOO Where FOO is the name of the trouble package. It will probably spew error messages. Cut and past the entire command plus the error messages into the email message. Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 16:27:22 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 04:09 PM, German wrote: On Fri, 08 May 2015 16:00:05 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:56 PM, German wrote: What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? With the drive duplicated, run fsck on the new drive. Hopefully the file system will be repairable. If it isn't, you can run testdisk or whatever to try to rescue files to another device (not the original, bad drive). What will happen when I duplicate drive? Why is that failed drive is failed and duplicated drive might be repairable? If it's duplicated, it will be exactly the same, no? Confused. And bad drive is physically ok I think, it is just something wrong with file system. MTF? If the bad drive is physically OK, then ddrescue is probably not needed. ddrescue, and the similar *rescue tools, are only for recovering as much data as possible data when you can't use plain dd because the drive itself is producing errors in some sectors. (You still can't recover data from those sectors, but you can generally get the rest.) If the drive is OK but the filesystem is bad, then you need to use other tools for data recovery. Exactly what those tools would be will probably depend on what filesystem is involved; if fsck doesn't work, then it will probably involve advanced manual techniques which we (or, at least, I) could not talk you through via E-mail. If you want to copy the bad filesystem for analysis and/or dissecting, then as long as the drive is OK, you should be able to do it using plain dd - no need for ddrescue or any such thing. What leads you to conclude that the drive is OK and the filesystem is what is bad? What errors are you seeing, in what situations? Error mounting /dev/sdc1 at /media/spore/FreeAgent GoFlex Drive: Command-line `mount -t ntfs -o uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177 /dev/sdc1 /media/spore/FreeAgent GoFlex Drive' exited with non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read of MFT, mft=17625 count=1 br=-1: Input/output error Inode is corrupt (5): Input/output error Index root attribute missing in directory inode 5: Input/output error Failed to mount '/dev/sdc1': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508163434.45a77...@asterius.asterius.net
Re: Help with ddrescue
The Wanderer wrote: Gary Dale wrote: I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. In my experience, single-pass recovery like this does not work very reliably or very well; it also doesn't let you make the backup copy you originally suggested, which is a good idea if you have the space (though I never have had). I have never had *enough* disk space. Because I always need more! There is an idea that I didn't see proposed as I read through this thread. If one had three same sized drives then there is another possibility. It isn't that unusual to have three drives of the same size. One could then make two copies of the data. Copy the data from the failing drive to a good same-sized drive. It would then be an identical copy. Then take the failing drive and put it on the shelf so as not to damage it further while trying to recover. Then make another identical copy onto the third drive. At that point one of the copies can be used for recovery experimentation and there would still be a copy available for backup on the other drive. Also when making the first backup copy using ddrescue use a third location for the ddrescue log file. I am assuming that a system has been booted up for the rescue and has the failing disk and the target disk attached. That means the host system has its own space available for the copy. Use it for the log file. ddrescue /dev/sdX /dev/sdY /var/tmp/rescuelogfile Where /dev/sdX is the failing source drive, /dev/sdY is the spare target drive, and /var/tmp/rescuelogfile is on the system hosting the recovery effort with its own drives. If I had a spare drive of the same size this would be what I would do to copy it. Then could do the same for the backup onto the working copy spare for recovery. Or just use a normal dd there since presumably both of the spares are good and error free. It's technically possible, yes, but I wouldn't want to trust or rely on it in any case where the source device is potentially prone to failure - and in any scenario where it isn't, you're unlikely to want to use one of the *rescue tools in the first place. My experience has been that once a drive starts to produce hard failures that it tends to become worse rather quickly. I would perform the backup of it. There is no way to avoid it. But I would try to avoid working the failing drive as much as possible until there is as much recovered as possible. After having recovered as much as is possible only then would I try any other work on the failing drive. Because Murphy's Law usually means that it becomes worse quickly. But after I had a good backup then trying other things such as other disk recovery software and so forth is reasonable. Why not if the drive has already failed otherwise? But again I would want a good backup first. And do any recovery work on a different working copy of it. (There's also the consideration of finding space for the ddrescue log file if you're restoring directly to the identical-size device; that file that may not be as important in some scenarios, but I wouldn't want to try to do such a rescue without one.) Agreed. The ddrescue log is critical. But a hosting system with both drives mounted could use /var/tmp/rescuelog for space not on either of the same-sized drives. I certainly wouldn't say there are never times when direct device-to-device recovery like that is appropriate, but I haven't encountered one and I would not recommend it as a base-practices procedure. Storage recovery is definitely a problem that takes skill to produce good results. It's a problem. There is no easy solution because the decisions we make along the way all depend upon the knowledge and the information available at that moment. It is really hard to document a canonical procedure. Sometimes it just helps to be lucky. Bob signature.asc Description: Digital signature
Re: need help with approx-gc
Paul E Condon wrote: I run approx on one of my local jessie machines. The approx installation is strictly by using the approx deb, which includes a weekly run of approx-gc , which should just clean out the local repository of debs that are no longer useful. But approx-gc has started reporting I/O errors. It is reporting I/O errors as in the disk drive is failing types of errors? As in hardware errors outside of the software? What is reported? Are the errors in the /var/log/syslog or /var/log/kern.log files? What types of errors? less /var/log/kern.log Are you running SMART? What do the SMART error logs say? smartctl -l error /dev/sda smartctl -l selftest /dev/sda Are you running selftests? If not try running a SMART selftest and seeing what is the result of it. smartctl -t short /dev/sda sleep 120 # or whatever is predicted above smartctl -l selftest /dev/sda If short is okay then try a 'long' test. If you are seeing I/O errors then I would be worried the disk is failing. In which case the SMART would confirm it. (SMART isn't a good predictor. But it can confirm a diagnosis.) Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On 05/08/2015 at 04:34 PM, German wrote: On Fri, 08 May 2015 16:27:22 -0400 The Wanderer wande...@fastmail.fm wrote: What leads you to conclude that the drive is OK and the filesystem is what is bad? What errors are you seeing, in what situations? Error mounting /dev/sdc1 at /media/spore/FreeAgent GoFlex Drive: Command-line `mount -t ntfs -o uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177 /dev/sdc1 /media/spore/FreeAgent GoFlex Drive' exited with non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read of MFT, mft=17625 count=1 br=-1: Input/output error Inode is corrupt (5): Input/output error Index root attribute missing in directory inode 5: Input/output error Failed to mount '/dev/sdc1': Input/output error Input/output error in this sort of context usually means that the drive itself is failing, not the filesystem. (Or that something else in the connection between the system and the drive is faulty; I've seen it happen with bad SATA/IDE cables, and for that matter with cables which were just loose.) Just to confirm, this happens on any mount attempt, correct? NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. If you have a suitable Windows system with which to try the suggested 'chkdsk /f' and double reboot-into-Windows approach, you could do that, but I wouldn't bet on it helping - and if the drive really is failing, then trying to access the drive that way might make things worse. I think it looks as if the drive really is failing, and the separate, larger drive ddrescue/dd_rescue/myrescue approach is the right way to go after all. (Also note that since the filesystem is on /dev/sdc1, you'll almost certainly want to apply your ddrescue command to source that node, not the higher-level /dev/sdc node. You _can_ recover the data from a copy of /dev/sdc, but it's significantly less trivial.) -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On Fri, 8 May 2015 14:41:24 -0600 Bob Proulx b...@proulx.com wrote: The Wanderer wrote: Gary Dale wrote: I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. In my experience, single-pass recovery like this does not work very reliably or very well; it also doesn't let you make the backup copy you originally suggested, which is a good idea if you have the space (though I never have had). I have never had *enough* disk space. Because I always need more! There is an idea that I didn't see proposed as I read through this thread. If one had three same sized drives then there is another possibility. Problem I have now is the lack of money. I simply don't have money now to buy yet another drive. I took out one drive from my another system, bought usb external enclosure and thought I'll succeed. Hmm.. everything is just not as easy as it seems. It isn't that unusual to have three drives of the same size. One could then make two copies of the data. Copy the data from the failing drive to a good same-sized drive. It would then be an identical copy. Then take the failing drive and put it on the shelf so as not to damage it further while trying to recover. Then make another identical copy onto the third drive. At that point one of the copies can be used for recovery experimentation and there would still be a copy available for backup on the other drive. Also when making the first backup copy using ddrescue use a third location for the ddrescue log file. I am assuming that a system has been booted up for the rescue and has the failing disk and the target disk attached. That means the host system has its own space available for the copy. Use it for the log file. ddrescue /dev/sdX /dev/sdY /var/tmp/rescuelogfile Where /dev/sdX is the failing source drive, /dev/sdY is the spare target drive, and /var/tmp/rescuelogfile is on the system hosting the recovery effort with its own drives. If I had a spare drive of the same size this would be what I would do to copy it. Then could do the same for the backup onto the working copy spare for recovery. Or just use a normal dd there since presumably both of the spares are good and error free. It's technically possible, yes, but I wouldn't want to trust or rely on it in any case where the source device is potentially prone to failure - and in any scenario where it isn't, you're unlikely to want to use one of the *rescue tools in the first place. My experience has been that once a drive starts to produce hard failures that it tends to become worse rather quickly. I would perform the backup of it. There is no way to avoid it. But I would try to avoid working the failing drive as much as possible until there is as much recovered as possible. After having recovered as much as is possible only then would I try any other work on the failing drive. Because Murphy's Law usually means that it becomes worse quickly. But after I had a good backup then trying other things such as other disk recovery software and so forth is reasonable. Why not if the drive has already failed otherwise? But again I would want a good backup first. And do any recovery work on a different working copy of it. (There's also the consideration of finding space for the ddrescue log file if you're restoring directly to the identical-size device; that file that may not be as important in some scenarios, but I wouldn't want to try to do such a rescue without one.) Agreed. The ddrescue log is critical. But a hosting system with both drives mounted could use /var/tmp/rescuelog for space not on either of the same-sized drives. I certainly wouldn't say there are never times when direct device-to-device recovery like that is appropriate, but I haven't encountered one and I would not recommend it as a base-practices procedure. Storage recovery is definitely a problem that takes skill to produce good results. It's a problem. There is no easy solution because the decisions we make along the way all depend upon the knowledge and the information available at that moment. It is really hard to document a canonical procedure. Sometimes it just helps to be lucky. Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508165117.1b7eb...@asterius.asterius.net
Re: Help with ddrescue
On Fri, 8 May 2015 22:05:40 +0100 Lisi Reisz lisi.re...@gmail.com wrote: On Friday 08 May 2015 21:58:12 German wrote: It's happened when I was installing Lubuntu. Post hoc doesn't necessarily imply propter hoc. http://en.wikipedia.org/wiki/Post_hoc_ergo_propter_hoc Lisi You are philosopher. In meanwhile I think that that what caused the problem. I also have internal drive which couldn't be mounted after install of Lubuntu. Interesting enough, after installing Debian on the same system, my internal drive became fully operational. :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508171551.2aa30...@asterius.asterius.net
Re: Uso de memória no Debian 8.0.0
Em 8 de maio de 2015 08:59, Tiago Rocha tiago.ro...@openmailbox.org escreveu: Quando tento lembrar de um navegador mais pesado Google Chrome só me lembro do Internet Explorer É tenso! :-/ Ah, sim, mas minha questão é mais se o Chromium chega a ser mais leve que o Google Chrome ou não. Tem também a questão de estabilidade. O Conkeror é levíssimo, mas com muitas abas na sessão gravada demora bastante para carregar; e depois ele vaza um bocado de memória, creio que por usar o XUL runner (mesmo motor do Iceweasel e do Firefox). -- skype:leandro.gfc.dutra?chat Yahoo!: ymsgr:sendIM?lgcdutra +55 (61) 3546 7191 gTalk: xmpp:leand...@jabber.org +55 (61) 9302 2691ICQ/AIM: aim:GoIM?screenname=61287803 BRAZIL GMT−3 MSN: msnim:chat?contact=lean...@dutra.fastmail.fm -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAFqwwS7Mr8jV_=4gcpsckatsx6v_7cqy2rzxlsl_tfvnh04...@mail.gmail.com
Enc: Re: Uso de memória no Debian 8.0.0
ja que entramos no mérito chrome. também não sou fã dele, mas eu tenho netflix, e não consegui fazer rodar em nenhum outro browser a não ser nele, sem falar em flash, o chrome roda sem nenhum problema, já tive problemas ao rodar vídeos em alguns sites com outros browsers. quanto a questão de peso, ainda não verifiquei o consumo de memória, mas logo quando fiz a primeira atualização depois de virar stable, tive problemas de lentidão ao abrir diversas abas no iceweasel, pois venho usando ele desde quando ainda era testing, mas não tive mais este problema, depois que reiniciei. Ricardo Libanio Em Sex, 08 Mai 2015 08:59:32 -0300 Tiago Rocha lt;tiago.ro...@openmailbox.orggt; escreveu On 08-05-2015 08:37, Guimarães Faria Corcete DUTRA, Leandro wrote: gt; Em 8 de maio de 2015 08:26, Tiago Rocha lt;tiago.ro...@openmailbox.orggt; escreveu: gt;gt; Eu indico não usar o google chrome;) gt; gt; Eu mesmo uso mais o Conkeror e o Epiphany segundo a necessidade, mas gt; quando preciso de um navegador mais popular para os sítios mais gt; chatos, uso o Chromium. Não sei se é mais leve que o Google Chrome, Quando tento lembrar de um navegador mais pesado Google Chrome só me lembro do Internet Explorer É tenso! :-/ gt; mas pelo menos não é uma caixa preta. Mais pura verdade!!! -- Tiago Rocha É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela.” Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554ca524.9060...@openmailbox.org
Re: Debian 8 no network...
On Fri, 8 May 2015 14:38:53 +0200 Gábor Hársfalvi hgab...@gmail.com wrote: So you have to check your system update manager's network settings. - Where to do it? And where to setup how often do it the update? Well, what _is_ this update manager? Is it some Gnome thing? I know that Ubuntu has something called update-manager, but on my Jessie box with Xfce nothing like that exists. apt-cache search update manager Doesn't find anything that sounds right, either. What are you running? Petter -- I'm ionized Are you sure? I'm positive. pgpcLYElZQGA8.pgp Description: OpenPGP digital signature
Re: Help with ddrescue
On 05/08/2015 at 07:08 PM, German wrote: On Fri, 8 May 2015 23:54:46 +0100 Lisi Reisz lisi.re...@gmail.com wrote: On Friday 08 May 2015 23:07:34 German wrote: Can I try to run fsck on the failed drive? They are *your* files. But given that you have actually got a suitable disk, i would at least dd them first onto that. That's what I got: spore@asterius:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 119.2G 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 111.3G 0 part / └─sda3 8:30 7.4G 0 part [SWAP] sdb 8:16 0 465.8G 0 disk sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 sdd 8:48 0 1.8T 0 disk └─sdd1 8:49 0 1.8T 0 part Where sdd is my failed drive. sdc is my spare drive. The correct procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? No. That might potentially work (except that, if I'm reading the ddrescue man page correctly, the syntax is wrong), but it wouldn't be correct. First, unmount /dev/sdc. Then do one of two things: 1) Create /dev/sdc1 (as an unformatted partition, using fdisk or parted or whatever partitioning tool you choose), and then run ddrescue /dev/sdd1 /dev/sdc1 /any/path/you/want/ddrescue.log 2) run ddrescue /dev/sdd /dev/sdc /any/path/you/want/ddrescue.log (Don't do both, of course.) Note that I did NOT specify the 'if=' and 'of=' syntax. That is correct syntax for dd, but the ddrescue man page does not mention it, and I believe that it is incorrect syntax for ddrescue. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: problema de acceso a disco USB
Hola Gerardo... El 08/05/15 a las 22:02, Gerardo Diez García escribió: El 08/05/15 20:31, Walter O. Dari escribió: Hola gente: Luego de actualizar a Jessie, cuando conecto el disco externo USB aparece el aviso y cuando selecciono abrir con el navegador de archivos (es en KDE) da un error: No se puede ejecutar la orden indicada. El archivo o carpeta file:///media/wodari/Samsung1Tb no existe. En Wheezy no tenÃa este problema. Si hago un ls -l en /media/wodari me muestra: root@debi5:/media/wodari# ls -l ls: no se puede acceder a Samsung1Tb: Error de entrada/salida total 0 d? ? ? ? ?? Samsung1Tb Un dmesg: [154435.129561] usb 2-2: new high-speed USB device number 11 using xhci_hcd [154435.199553] usb 2-2: New USB device found, idVendor=04e8, idProduct=61b6 [154435.199558] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [154435.199561] usb 2-2: Product: Samsung M3 Portable [154435.199564] usb 2-2: Manufacturer: Samsung M3 Portable [154435.199566] usb 2-2: SerialNumber: 5F7E7DE60C00012A [154435.200841] scsi13 : usb-storage 2-2:1.0 [154436.195666] scsi 13:0:0:0: Direct-Access Samsung M3 Portable 1301 PQ: 0 ANSI: 6 [154436.197051] sd 13:0:0:0: Attached scsi generic sg4 type 0 [154436.198103] sd 13:0:0:0: [sdd] Spinning up diskready [154437.200587] sd 13:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [154437.200909] sd 13:0:0:0: [sdd] Write Protect is off [154437.200914] sd 13:0:0:0: [sdd] Mode Sense: 33 00 00 08 [154437.201244] sd 13:0:0:0: [sdd] No Caching mode page found [154437.201248] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.202511] sd 13:0:0:0: [sdd] No Caching mode page found [154437.202516] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.228143] sdd: sdd1 [154437.229430] sd 13:0:0:0: [sdd] No Caching mode page found [154437.229434] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.229438] sd 13:0:0:0: [sdd] Attached SCSI disk El disco tiene una única partición NTFS. No está referenciado en /etc/fstab Si ejecuto cfdisk /dev/sdd me muestra la partición NTFS. Cuál podrá ser el problema ? Saludos y gracias, ¿Has probado a montarlo manualmente a ver si muestra algún mensaje (más)? Si, al montarlo nuevamente pasa lo mismo, no me deja acceder. Me pasa con los 3 discos externos que uso para hacer copias de seguridad, si los conecto a otro equipo, con Debian Wheezy, no tengo problemas. Recién acabo de eliminarle la partición NTFS a uno de ellos y crearle una con ext4, ahora lo conecto y no da errores. Así que haré lo mismo con los otros 2, no tengo mucho tiempo para ver de que se trata este problema. Estuve leyendo un poco sobre las cosas a tener en cuenta para la actualización de Wheezy a Jessie pero no vi nada relacionado a este tema. Bueno, de cualquier forma me gustaría saber a que se debe si alguien tiene idea. Saludos ! -- Walter O. Dari http://swcomputacion.com/ https://facebook.com/swcomputacion/ skype: waomda -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d67b0.6000...@gmail.com
Re: problema de acceso a disco USB
El 09/05/15 03:49, Walter O. Dari escribió: Hola Gerardo... El 08/05/15 a las 22:02, Gerardo Diez García escribió: El 08/05/15 20:31, Walter O. Dari escribió: Hola gente: Luego de actualizar a Jessie, cuando conecto el disco externo USB aparece el aviso y cuando selecciono abrir con el navegador de archivos (es en KDE) da un error: No se puede ejecutar la orden indicada. El archivo o carpeta file:///media/wodari/Samsung1Tb no existe. En Wheezy no tenÃa este problema. Si hago un ls -l en /media/wodari me muestra: root@debi5:/media/wodari# ls -l ls: no se puede acceder a Samsung1Tb: Error de entrada/salida total 0 d? ? ? ? ?? Samsung1Tb Un dmesg: [154435.129561] usb 2-2: new high-speed USB device number 11 using xhci_hcd [154435.199553] usb 2-2: New USB device found, idVendor=04e8, idProduct=61b6 [154435.199558] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [154435.199561] usb 2-2: Product: Samsung M3 Portable [154435.199564] usb 2-2: Manufacturer: Samsung M3 Portable [154435.199566] usb 2-2: SerialNumber: 5F7E7DE60C00012A [154435.200841] scsi13 : usb-storage 2-2:1.0 [154436.195666] scsi 13:0:0:0: Direct-Access Samsung M3 Portable 1301 PQ: 0 ANSI: 6 [154436.197051] sd 13:0:0:0: Attached scsi generic sg4 type 0 [154436.198103] sd 13:0:0:0: [sdd] Spinning up diskready [154437.200587] sd 13:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [154437.200909] sd 13:0:0:0: [sdd] Write Protect is off [154437.200914] sd 13:0:0:0: [sdd] Mode Sense: 33 00 00 08 [154437.201244] sd 13:0:0:0: [sdd] No Caching mode page found [154437.201248] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.202511] sd 13:0:0:0: [sdd] No Caching mode page found [154437.202516] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.228143] sdd: sdd1 [154437.229430] sd 13:0:0:0: [sdd] No Caching mode page found [154437.229434] sd 13:0:0:0: [sdd] Assuming drive cache: write through [154437.229438] sd 13:0:0:0: [sdd] Attached SCSI disk El disco tiene una única partición NTFS. No está referenciado en /etc/fstab Si ejecuto cfdisk /dev/sdd me muestra la partición NTFS. Cuál podrá ser el problema ? Saludos y gracias, ¿Has probado a montarlo manualmente a ver si muestra algún mensaje (más)? Si, al montarlo nuevamente pasa lo mismo, no me deja acceder. Me pasa con los 3 discos externos que uso para hacer copias de seguridad, si los conecto a otro equipo, con Debian Wheezy, no tengo problemas. Recién acabo de eliminarle la partición NTFS a uno de ellos y crearle una con ext4, ahora lo conecto y no da errores. Así que haré lo mismo con los otros 2, no tengo mucho tiempo para ver de que se trata este problema. Estuve leyendo un poco sobre las cosas a tener en cuenta para la actualización de Wheezy a Jessie pero no vi nada relacionado a este tema. Bueno, de cualquier forma me gustaría saber a que se debe si alguien tiene idea. Saludos ! Hola Walter, si te pedía más información era porque en su día me pelee en Wheezy con un pendrive con NTFS. De hecho en la lista tiene que haber alguna pregunta al respecto. Si la memoria no me falla, todo se solucionó con un: chown root $(which ntfs-3g) chmod 4755 $(which ntfs-3g) que es lo que indica en la página de ntfs-3g-faq[1] [1]http://www.tuxera.com/community/ntfs-3g-faq/#unprivileged -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d6a04.1020...@gmail.com
Re: Mysar no genera los reportes
El 07/05/15 16:30, Informático Leandro escribió: El Jue, 7 de Mayo de 2015, 10:00 am, Informático Leandro escribió: El Jue, 7 de Mayo de 2015, 9:51 am, Camaleón escribió: El Wed, 06 May 2015 14:35:54 -0400, Informático Leandro escribió: hola listeros hace un tiempo que uso zarg como herramienta de auditoria a los LOGS de squid, pero ultimamente me he visto en la necesidad de pararlo pués como genera muchos figheros me llena el server y estoy un tanto carente de espacio. En esencia lo que quiero es implementar MYSAR 2.1.2 como alternativa, ya lo he instalado he seguido al pie de la letra todos los pasos de instlación del archivo README pero nada de reportes, ya cree la regla en el cron lo reinicie y nada de reportes. Una ves dentro de la pagina de conf le indico todos los parametros correctos pero nada de nada AYUDA POR FAVOR Por aquà tienes una guÃa de instalación y configuración para Debian y en español: Instalar MySAR en Debian - [ EstadÃsticas de navegación ] http://adminnetworks.blogspot.com.es/2011/05/instalar-mysar-en-debian.html Saludos, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/pan.2015.05.07.13.51...@gmail.com gracias hermano vere y te digo -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8d7bbeacf6202f50726209c9be637297.squir...@mail.ipurr.sc.sc.rimed.cu Camaleon ya implemente lo de el link que me diste te dire que no habia diferencia en lo que habia hecho con respecto a esto y una ves ejecuto las dependencias 1 php /var/www/mysar/bin/mysar-binary-importer 2 php /var/www/mysar/bin/mysar-maintenance.php 3 php /var/www/mysar/bin/mysar-resolver.php la primera OK la segunda me genera estos errores root@zeus:~# php /usr/local/mysar/bin/mysar-maintenance.php PHP Strict Standards: mktime(): You should be using the time() function instead in /usr/local/mysar/bin/mysar-maintenance.php on line 61 Optimizing config... Optimization finished.PHP Strict Standards: mktime(): You should be using the time() function instead in /usr/local/mysar/bin/mysar-maintenance.php on line 61 Optimizing hostnames... Optimization finished.PHP Strict Standards: mktime(): You should be using the time() function instead in /usr/local/mysar/bin/mysar-maintenance.php on line 61 Optimizing sites... Optimization finished.PHP Strict Standards: mktime(): You should be using the time() function instead in /usr/local/mysar/bin/mysar-maintenance.php on line 61 Optimizing traffic... Optimization finished.PHP Strict Standards: mktime(): You should be using the time() function instead in /usr/local/mysar/bin/mysar-maintenance.php on line 61 Optimizing trafficSummaries... Optimization finished.PHP Strict Standards: mktime(): You should be using the time() function instead in /usr/local/mysar/bin/mysar-maintenance.php on line 61 Optimizing users... Optimization finished. root@zeus:~# La Tercera root@zeus:~# php /usr/local/mysar/bin/mysar-resolver.php PHP Strict Standards: mktime(): You should be using the time() function instead in /usr/local/mysar/bin/mysar-resolver.php on line 86 root@zeus:~# lo que no entiendo es el tema de la funcion MKTIME() este es el problemita que no me deaja que mysar genere los reportes Propuesta. ¿Y si abres el archivo /usr/local/mysar/bin/mysar-resolver.php, vas a la línea 61 y le borras esa mk? Por probar a ver qué pasa. Según la documentación de php desde la versión 5.1 saltará ese aviso. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d6c65.8070...@gmail.com
Re: Help with ddrescue
On Fri, 08 May 2015 16:00:05 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:56 PM, German wrote: On Fri, 08 May 2015 14:48:47 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:32 PM, German wrote: On Fri, 08 May 2015 14:23:39 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 02:16 PM, German wrote: On Fri, 08 May 2015 13:40:01 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 01:20 PM, German wrote: Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. That's bad. If the drive has only one partition, it probably has a single filesystem taking up all of its space. When you create a ddrescue image from that partition, the new image will take up _at least as much_ space as the original filesystem. That's not the 1.6TB of used space; it's the full 2TB of total space. (Plus however much space is taken up by the index file used by ddrescue while doing its work.) That means that if your two 2TB drives are actually the same size, the good one will not have enough space to store the image you need to rescue from the bad one. Thanks Wanderer. So, I have no chances with two drives the same capacity? Would you advise to wait when I can get more capacity drive and only then to proceed as to save some head ache? Yes, that's what I'd do in your situation. A 2.5TB drive should be more than enough; that would also let you store the sdb_failed.ddrescuelog file on the same drive, if you need to, so you don't have to worry about finding space for it elsewhere. Once again, thanks for such a complete instructions. I wouldn't call the directions I gave complete; there's a lot of details you'll still have to work out on your own, because they will depend on the exact details of your failure and the recovery process. Still, they should at least provide you a good starting point. Again, I would recommend that you install (and read the documentation for) myrescue, and consider using that instead of ddrescue. I've used both (as well as dd_rescue), but if memory serves I've had better results with myrescue. Thanks so much. I wait when I can get a bigger drive. Have a greatest day! I think Wanderer may be overstating the problem a little. If the two drives are exactly the same size, you can use ddrescue to duplicate the failed drive onto the new drive (ddrescue if=/dev/sdb of=/dev/sdc). However this will limit you to recovering in place on new drive. What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? With the drive duplicated, run fsck on the new drive. Can I try to run fsck on the failed drive? Hopefully the file system will be repairable. If it isn't, you can run testdisk or whatever to try to rescue files to another device (not the original, bad drive). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508180734.04bea...@asterius.asterius.net
Re: Help with ddrescue
On 05/08/2015 at 06:07 PM, German wrote: On Fri, 08 May 2015 16:00:05 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:56 PM, German wrote: What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? With the drive duplicated, run fsck on the new drive. Can I try to run fsck on the failed drive? You can (or, rather, on the filesystem which is on that drive), but if the drive really is physically failing, you will probably just make the problems worse - and reduce the likelihood of successfully recovering data off of it later. If the drive _isn't_ physically failing, however, then running fsck on the filesystem is probably the first thing you should do. If you're sure the drive itself is OK and the problem is with the filesystem, I'm kind of surprised you didn't do that before you even contacted the list in the first place. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
Bob Proulx wrote: ddrescue if=/dev/sdX of=/dev/sdY /media/usb1 Where /media/usb1 is an example of a mounted usb storage device. Replace that string with the mount point of the usb device mounted on your host system. Obviously I made a mistake there. Not to the mount directory but to a file upon it. ddrescue if=/dev/sdX of=/dev/sdY /media/usb1/rescuelogfile Bob signature.asc Description: Digital signature
Re: Help with ddrescue
On Fri, 08 May 2015 18:11:03 -0400 The Wanderer wande...@fastmail.fm wrote: On 05/08/2015 at 06:07 PM, German wrote: On Fri, 08 May 2015 16:00:05 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 02:56 PM, German wrote: What will this duplication accomplish? What advantages if I am duplicate? After I duplicate the drive, what are my next steps? With the drive duplicated, run fsck on the new drive. Can I try to run fsck on the failed drive? You can (or, rather, on the filesystem which is on that drive), but if the drive really is physically failing, you will probably just make the problems worse - and reduce the likelihood of successfully recovering data off of it later. If the drive _isn't_ physically failing, however, then running fsck on the filesystem is probably the first thing you should do. If you're sure the drive itself is OK and the problem is with the filesystem, I'm kind of surprised you didn't do that before you even contacted the list in the first place. I am not sure about anything. I just gather some information on how to recover my files. As I said, with R-studio ( linux commercial data recovery app) I could see all files and directory on failed drive. Ok. Could you please tell me how to do fsck on NTFS drive? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508182025.213a9...@asterius.asterius.net
Re: Help with ddrescue
On Fri, 8 May 2015 23:54:46 +0100 Lisi Reisz lisi.re...@gmail.com wrote: On Friday 08 May 2015 23:07:34 German wrote: Can I try to run fsck on the failed drive? They are *your* files. But given that you have actually got a suitable disk, i would at least dd them first onto that. Lisi That's what I got: spore@asterius:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 119.2G 0 disk ├─sda1 8:10 512M 0 part /boot/efi ├─sda2 8:20 111.3G 0 part / └─sda3 8:30 7.4G 0 part [SWAP] sdb 8:16 0 465.8G 0 disk sdc 8:32 0 1.8T 0 disk /media/spore/9F86-0131 sdd 8:48 0 1.8T 0 disk └─sdd1 8:49 0 1.8T 0 part Where sdd is my failed drive. sdc is my spare drive. The correct procedure will be ddrescue if=/dev/sdd1 of=/dev/sdc ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508190847.76259...@asterius.asterius.net
Re: Help with ddrescue
German wrote: Bob Proulx wrote: I think I read that you have one identically sized drive, yes? I am not sure where you are sitting with regards to the other suggestions. But at the least I would make one good backup as soon as possible. And it seems that possibly you have the capability at this time? Yes, I do have two identical 2TB drives. So, you are advising to make a back up. Something like ddrescue if=/dev/sdX of=/dev/sdY ? Again I am not sure of the status of things with you since there have been many good suggestions in this discussion thread. You may be halfway down a different path. But yes if I were having hardware problems I would make a backup as soon as possible. (Actually I already have backups all of the time. Backups are important.) Always use a log file with ddrescue. If I have both of those disks mounted on a second system with its own disks then put the logfile on the host system. That would be on the host system and not either the source or target. ddrescue if=/dev/sdX of=/dev/sdY /var/tmp/rescuelogfile If you had booted a livecd and wanted that logfile to be persistent then mount up a USB storage device and store it there. ddrescue if=/dev/sdX of=/dev/sdY /media/usb1 Where /media/usb1 is an example of a mounted usb storage device. Replace that string with the mount point of the usb device mounted on your host system. I now read that perhaps it wasn't hardware problems. If the disk is okay then the first thing I would do is to fsck it. But if the disk is having hardware problems then I would copy a backup first. Bob signature.asc Description: Digital signature
Re: jessie selinux reference policy package missing
On Fri, May 08, 2015 at 04:18:30PM -0500, Spencer Minear wrote: I installed the new Jessie version of debian on a VirtualBox system, and had no problems with the installation. Because I wanted to do work with the SELinux policy I wanted to first make sure that the system would run with SE Linux to provide a platform on which to experiment with the policy. I obtained most of the SELinux packages that I think I needed and/or wanted, selling-utils, selinux-basics etc. Then, per existing documentation on setting up SELinux on a Debian system I attempted to get the selinux-policy-default via 'apt-get install selinux-policy-default' and was told E: Package 'selinux-policy-default' has no installation candidate'. Looking around I find one for Wheezy and for SID but not for Jessie. Given the fact that jessie was just released a few weeks ago, I'm guessing that the jessie policy package simply was not completed yet. https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=selinux-policy-default;dist=unstable See the bugs marked Grave, Serious, and indeed most of the Important and some of the Unclassified bugs. It may be that someone will someday get a default selinux policy set up for Jessie, but I wouldn't bet on that being soon. You can blame systemd, if you'd like. You might even get a mostly-working system if you change back to sysvinit and try again. -dsr- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508233221.gf23...@randomstring.org
Re: Help with ddrescue
On Friday 08 May 2015 23:07:34 German wrote: Can I try to run fsck on the failed drive? They are *your* files. But given that you have actually got a suitable disk, i would at least dd them first onto that. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201505082354.46323.lisi.re...@gmail.com
Re: Verificando portas abertas
On 08-05-2015 01:13, Thiago Zoroastro wrote: Olá a todos, estive verificando as portas do Debian. Me deparei com 1 unknown na porta 58080 depois de testar vários comandos que fui encontrando na internet. [...] Estaria a porta 58080 sendo utilizada de forma invasiva por outra pessoa ou isto é normal? Tentei encontrar e não achei a utilidade da porta 58080, na verdade encontrei mas não compreendi. Olá! Geralmente essa porta é usada como um proxy http local, isto é, um proxy que serviria somente você e não a rede toda, melhorando de certa forma a performance e consumo de internet, além de proporcionar um controle dos pais. Quanto ao número, é uma variação da 8080 que é usada para proxy http da rede, que por sua vez é uma varição da porta 80, padrão http. Essa porta não deveria ser vista de fora da sua máquina, se está verificando ela na mesma máquina, então está beleza. Verifique se outra máquina tem acesso à essa porta. -- []'s Junior Polegato
Re: Debian 8 no network...
So you have to check your system update manager's network settings. - Where to do it? And where to setup how often do it the update? You can't install Debian binaries via apt-get. You can only install packages like: apt-get install packagename - Sorry - Yes - I mean that too, but not wrote correctly - of course. Thanks 2015-05-08 8:25 GMT+02:00 Elimar Riesebieter riese...@lxtec.de: * Gábor Hársfalvi hgab...@gmail.com [2015-05-07 21:15 +0200]: Hello, I've got the problem yet - and I don't know why. Everything uses my Internet connection - browsers, online games etc. - but the system update manager always gives me an error about no network connection. So you have to check your system update manager's network settings. This is the same when I wish to install a .deb package from the PC. But when I use Terminal commands - for example apt-get install .deb it always work with the same network connection for downloading packages. You can't install Debian binaries via apt-get. You can only install packages like: apt-get install packagename I'm using PPPOE connection with dsl-provider - and I wish to use that for the future too. Should be no problem. Elimar -- Experience is something you don't get until just after you need it! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508062513.gc9...@baumbart.home.lxtec.de
Re: avatar session lxde
Salut Le 08/05/2015 10:07, yamo' a écrit : Salut, nono a écrit le 08/05/2015 07:10 : Je cherche à mettre un avatar à l'ouverture de session de mon utilisateur, sous lxde debian 8. Apparemment, il suffit d'avoir une image ou un lien logique : $HOME/.FACE Et avoir gnome-control-center installé (???). Cf : https://wiki.archlinux.org/index.php/LXDM#Adding_face_icons aïe, cela ne m'enchante pas trop d'installer gnome-control-center, le nombre de dépendance semble trop important. À l'occasion je vais tenter sur une VM avant ;-) merci Je n'ai pas testé, je n'ai pas utilisé lxde depuis un moment. nono -- Trois choses insupportables : le café brûlant, le champagne tiède, et les femmes froides. -+- Orson Welles (1915-1985) -+- signature.asc Description: OpenPGP digital signature
Re: Help with ddrescue
On 5/8/2015 10:20 AM, German wrote: On Fri, 08 May 2015 12:10:38 -0400 Gary Dale garyd...@torfree.net wrote: On 08/05/15 10:32 AM, German wrote: Hi list. Ok, now I have a spare 2TB USB drive where I can save .img file. Is that the right procedure? Do I have make a snapshot of failed drive and transfer it as a .img file to a spare drive, correct? R-studio for linux can display files of failed drive ( TestDisk coudn't do it ). So now I think I'll proceed. What is exact command to do it with ddrescue and what file system the spare drive has to be formated? Thank you very much! You can try ddrescue if=/dev/sdb1 of=failed.img where /dev/sdb1 would be the partition that you want to recover. Using 'dd' would be 'dd if=something of=something' ddrescue is 'ddrescue [options] [source] [destination] [logfile]' Thanks, but some clarification is needed. Now I have two drives, failed and a spare. Both are 2TB in size. Failed drive probably has 1.6 TB data I'd like to recover. It has only one partition I suppose. So, if failed drive is for instance /dev/sdb and spare drive is for isntance /dev/sdc, the right command will be ddrescue if=/dev/sdb of=/dev/sdc/failed.img ? And also, you didn't answer this, what file system the a spare drive ahs to be formated? Thanks. First I would use fdisk to see the size of the drives, not all 2 terabyte drives will be identical in size fdisk -l -l tells fdisk to list the drives. If the destination is larger, no issues, if it is smaller, might still work but may lead to issues later on. Going directly from one device to another, you have to use the force option to overwrite the destination. ddrescue --force /dev/sdb /dev/sdc /home/someusername/ddrescue.log If you go to an image, then you would have to mount the location ahead of time and specify a filename. ddrescue /dev/sdb /mnt/sdc1/rescued.img /home/someusername/ddrescue.log Here is a link to a guide... https://www.technibble.com/guide-using-ddrescue-recover-data/ There is a possibility that going device to device ddrescue might get enough to make a working clone, but I would go into it with the assumption that either way you will need to run recovery software and have yet another drive to recover to. The disadvantage of running recovery software on a failing disk, is the more you do to the disk the higher the risk it will get worse. The advantage of creating an image or clone is that once you have a copy on a good drive can keep trying different recovery options without having to worry about the drive getting worse. The disadvantage is that you need space that is equal to the size of the old drive plus room for all the files you want to recover. Later, Seeker -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d8d5b.40...@comcast.net
Re: Help with ddrescue
On 5/8/2015 5:28 PM, German wrote: On Fri, 08 May 2015 19:52:04 -0400 The Wanderer wande...@fastmail.fm wrote: Not quite. /dev/sda2/ is not a directory; it's a device node. Since /dev/sda2 is mounted to / (the root filesystem), the correct equivalent to this command would be: ddrescue /dev/sdd /dev/sdc /ddrescue.log and although I wouldn't advise storing a log file in the root directory, the command should work. The log file itself can be placed in any writable location which has enough space. Thank you I started ddrescue and it is going somewhere. Probably will take 10 hours or more to complete. I'll let you know how it's all went. Thank you once more. It refused to work as we wanted and asked for --force option ( -f) Looks like I am late to the party and this part got sorted already. For future reference, for people helping, there was a previous thread... https://lists.debian.org/debian-user/2015/04/msg01639.html The problem disk is a Seagate GoFlex. Testdisk deep scan only listed the smaller FAT partition not the NTFS partition. Later, Seeker -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d9a8d.6040...@comcast.net
Re: ¿Hay un wine para Jessie?
El 08/05/15 a las 17:59, Carlos Manuel Escalona Villeda escribió: Hay wine, el problema es que hay una librería que requiere el kernel 3.6 y jessie trae 3.16, por tanto wine ha quedado inusable. no lo creo que kede inusuable , en caso de no haver borrado el kernel anterior, puedes buscarlo en las OBCIONES AVANZADAS de GRUB, al inicio cuando prende la PC. en caso de haver borrado el kernel 3.6 mueve tus repos apuntando a wheezy , actualizas apt e instalas kernel 3.6 nuevamente, depues de instalarlo, pones los repos como estaban (jessie) y reinicias y entras en modo avanzado de GRUB y ahi estara :-) esta es la gran bentaja de GNU sobre Window$, *casi todo tiene solucion* -- ** software libre no significa gratis: richard m. stallman http://wiki.debian.org/es/NormasLista#resumen http://wiki.debian.org/es/NormasLista/Gmail http://es.wikipedia.org/wiki/Top-posting -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554d880c.1050...@gmail.com
Temporarily hold a package............
From my keyboard: I have been looking through the man pages for: apt-get, apt-get upgrade, but I'm certain I don't understand how I might hold a package for a while? Anyone who can and is inclined to help, might assist me for the whole testing cycle in this case with their advice. I get this when I attempt an upgrade of stretch: Retrieving bug reports... Done Parsing Found/Fixed information... Done serious bugs of openssl (1.0.1k-3 → 1.0.2a-1) Outstanding b1 - #770605 - openssl: Removes symbol without SONAME bump Merged with: 768476 768522 769023 770278 771169 771993 781094 781929 Summary: openssl(1 bug) Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n ** ** Exiting with an error in order to stop the installation. ** ** : Thanks in advance. Charlie East Gippsland Wildlife Rehabilitators Inc.. http://www.egwildlife.com.au/ -- Registered Linux User:- 329524 *** They would often change who would be constant in happiness and wisdom. ..Confucius *** Debian GNU/Linux - Magic indeed. - -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150509132040.44543...@egwildlife.com.au
Re: Uso de memória no Debian 8.0.0
On 08-05-2015 08:37, Guimarães Faria Corcete DUTRA, Leandro wrote: Em 8 de maio de 2015 08:26, Tiago Rocha tiago.ro...@openmailbox.org escreveu: Eu indico não usar o google chrome;) Eu mesmo uso mais o Conkeror e o Epiphany segundo a necessidade, mas quando preciso de um navegador mais popular para os sítios mais chatos, uso o Chromium. Não sei se é mais leve que o Google Chrome, Quando tento lembrar de um navegador mais pesado Google Chrome só me lembro do Internet Explorer É tenso! :-/ mas pelo menos não é uma caixa preta. Mais pura verdade!!! -- Tiago Rocha É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela.” Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554ca524.9060...@openmailbox.org
Re: Verificando portas abertas
On Fri, May 08, 2015 at 01:13:39AM -0300, Thiago Zoroastro wrote: Olá a todos, estive verificando as portas do Debian. Me deparei com 1 unknown na porta 58080 depois de testar vários comandos que fui encontrando na internet. # nmap -sN IP.000.000.000 Starting Nmap 5.00 ( http://nmap.org ) at 2015-05-08 01:07 BRT All 1000 scanned ports on (IP.000.000.000) are open|filtered Nmap done: 1 IP address (1 host up) scanned in 21.44 seconds # nmap -sS IP.000.000.000 Starting Nmap 5.00 ( http://nmap.org ) at 2015-05-08 01:08 BRT Interesting ports on (IP.000.000.000): Not shown: 999 filtered ports PORT STATE SERVICE 58080/tcp open unknown Nmap done: 1 IP address (1 host up) scanned in 7.85 seconds Troquei o IP para IP.000.000.000 na mensagem. Estaria a porta 58080 sendo utilizada de forma invasiva por outra pessoa ou isto é normal? Tentei encontrar e não achei a utilidade da porta 58080, na verdade encontrei mas não compreendi. Primeira coisa que você precisar saber é qual processo está escutando nessa porta. Olhe a saída de `netstat -plant`. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Re: problema de audio en debian 8 Jessi [solucionado]
El 7/5/15, Camaleón noela...@gmail.com escribió: El Thu, 07 May 2015 18:02:45 +0200, Ala de Dragón escribió: El 7/5/15, Camaleón noela...@gmail.com escribió: Como te dice el mensaje, VDPAU está relacionado con la gráfica nvidia, no creo que tenga relación con tu problema del sonido. Estuve investigando al respecto, instalando los drivers NVIDIA se soluciona ese error, parece ser que nouveau y VDPAU no terminar de encajar sin intervención humana. Te lo iba a decir pero tampoco veía necesario que instalaras el driver propietario de nvidia sólo por ese mensaje ya que no pensaba que te fuera a solucionar el problema con el sonido. Por otra parte, VLC no saca ningún error, quizá no escuches nada por otro motivo (p. ej., un problema con el módulo de sonido que usa tu tarjeta). ¿Funciona correctamente VideoLAN cuando seleccionas la segunda tarjeta de sonido (la que usa el módulo de intel)? Si es así, quizá tengas que afinar un poco más la configuración de la cmi8738... Por aquí hablan de ese chipset: Lo divertido es que no tengo otra tarjeta, como sea la salida HDMI de la tarjeta grafica. mplayer y audacious de los repos de multimedia funcionan a las mil maravillas. Bueno, tienes una nvidia con driver de intel, eso decían los datos que ponías en el primer correo. ¿No tienes ningún aparatejo con qué probarla? Investigando he visto que tengo instalado este paquete: vlc-plugin-pulse, parece un paquete dummy sin efecto. Sí, eso parece. Por el momento la instalacion por defecto de xfce4 no configura bien vlc, lo cual si diera con fallo real podria notificarlo como un bug. Al menos es mi impresion http://www.sabi.co.uk/Notes/linuxSoundALSA.html#chipsCMI8738 Ya anduve mirando esa pagina, resulta que tengo errores en el modulo MPU-401, que se carga como depencia de snd-cmipci. Mi tarjeta es la trusth y hace tiempo que se que no funciona el midi/game port. There is a Trust card with this chipset which is cheap and has a IEC958/SPDIF bracket with both optical and coaxial input and output. It also has a MIDI/gameport socket. The gameport has a know electrical problem and basically does not work. Other than that the card is pretty decent. The major limitation of the CMI8738 does not support hardware sharing Yo no utilizo la tarjeta para mezclar musica, no necesito esta opción. Es decir solo una aplicación puede acceder al sonido. Sí, eso me pareció entender, lo cual no deja de ser una molestia pero salvo que seas un DJ o te guste hacer mezclas de tipo chumba-chumba no veo mayor problema :-P IEC958/SPDIF output can be simple or somewhat complicated to enable and configure Por eso tengo un listado de comprobaciones que ejecuto cada vez que hago una instalacion, los coloque al principio del correo. Sí, parece que es compleja de configurar pero si sólo te da problemas con VideoLAN y algún otro reproductor pues habrá que centrarse es eso. Also, someone has done a nice utility to control its detailed features Ese link esta muerto y ademas en chino ^_^ Otros link interesantes para el lector son: http://alsa.opensrc.org/C-Media_CMI8738 http://alsa.opensrc.org/Cmipci http://alsa.opensrc.org/Alsactl Prueba lo que dicen en el primer enlace de desactivar las dos salidas a ver qué sucede. También puedes seguir probando con el comando vlc --aout alsa $HOME/ Escritorio/test.mp4 pero seleccionando el resto de opciones de salida en lugar de alsa, por si vieras algún error, además de las típicas pruebas tontunas como verificar que todos los controles de volumen de salida del applet de sonido de XFCE estén a buen nivel, crear un nuevo usuario y ejecutar VideoLAN desde ahí o si tienes la opción de conectar una salida analógica (conector jack), probar con eso. Saludos, No tengo chismes HDMI pero si unos cascos para el conector jack, y no suena nada. Jugando con la consola en modo verboso: $vlc -v VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42) [00dc9d78] pulse audio output error: PulseAudio server connection failure: Connection refused [00cfb118] core libvlc: Ejecutar vlc con la interfaz predeterminada. Use «cvlc» para usar vlc sin interfaz. Pues si, resulta que intenta salir por pulseaudio, a pesar de no estar instalado por defecto. $ vlc -v --aout alsa /home/linux/Escritorio/test.mp4 VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 2.2.1-0-ga425c42) [00e2d118] core libvlc: Ejecutar vlc con la interfaz predeterminada. Use «cvlc» para usar vlc sin interfaz [7f559cc015b8] mp4 stream warning: unknown box type btrt (incompletely loaded) [7f559cc015b8] mp4 stream warning: unknown box type gsst (incompletely loaded) [7f559cc015b8] mp4 stream warning: unknown box type gstd (incompletely loaded) [7f559cc015b8] mp4 stream warning: unknown box type gssd (incompletely loaded) [7f559cc015b8] mp4 stream warning: unknown box type gspu (incompletely loaded)
Motorola Bluetooth adaptor not working on jessie
Hi all. I have an HP pavillion dv6 6131tx laptop late 2011 laptop with Motorola Bluetooth 3.0 hs adaptor. It works fine on Windows but not on Debian Jessie (64 bit gnome) (I have both windows and debian installed as dual boot). Bluetooth menu shows on the panel. It also tries to search for devices but is not able to do so nor does my laptop's bluetooth shows up on any bluetooth device although I have set it visisble. Another fact: I can't turn it off from the panel. I then googled it to get some idea and came to know running lspci command tells information about pci buses and devices and I ran it and found that bluetooth device doesn't show up there too. I am new to Linux and Debian. Any help is highly appreciated. P.S. It used to work on Wheezy 7.8. Thanks folks!
Re: Uso de memória no Debian 8.0.0
Eu indico não usar o google chrome;) On 08-05-2015 07:37, Luiz Carlos da Silveira Júnior wrote: Instalei em um note com 2GB e o consumo ficou próximo de 1GB... teve um momento que abri 6 abas no chrome + o terminal, observei que o note estava usando swap e dali a pouco travou. Alguém indica usar o Mate para resolver estes problemas de desempenho? Em 7 de maio de 2015 23:58, Nilton Vasques nilton.vasq...@gmail.com mailto:nilton.vasq...@gmail.com escreveu: Bem eu instalei o Jessie, em um netbook acer aspire one bem antigo, com apenas 1 GB de ram e processador atom. Sendo que o consumo de memória fica em torno de 500 mb com apenas o terminal aberto, talvez o gnome tenha alguma feature de otimização para computadores com pouca ram. On 07/05/15 21:07, Luiz Carlos da Silveira Júnior wrote: Estou achando o gnome pesado também, ainda mais usando com o chrome... Em 07/05/2015 20:57, real bas realba...@gmail.com mailto:realba...@gmail.com escreveu: Olá pessoal, Sei que é um pouco cedo pra falar disso, mas estou tendo um problema com a versão recém-estável do Debian (Jessie). Meu problema é o seguinte: *uso excessivo de memória*. Mesmo somente com um terminal aberto sem rodar nada, o uso de memória fica em torno de 3.5 GB, chegando até a usar a memória de Swap (isso mesmo). Gostaria de saber se alguém está tendo o mesmo problema e saber se já existe uma solução, procurei no fórum global e não encontrei nada relacionado. Minhas configurações de HW: Processador i5, 4 GB de RAM, placa nvidia e 640 GB de HD. -- Att., Nilton Vasques Carvalho Jr. Mobiloucos Team Graduando em Ciência da Computação Universidade Federal da Bahia telefone: +55 71 9278-0148 tel:%2B55%2071%209278-0148 (Tim) Github: https://github.com/niltonvasques linkedin: http://goo.gl/hUOs7W -- /att,/ /Luiz Carlos/ -- Tiago Rocha É bom tudo aquilo que faço que diminui o meu poder sobre outra pessoa; é ruim tudo aquilo que faço que aumenta o meu poder sobre ela.” Antônio Joaquim Severino -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/554c9d52.3030...@openmailbox.org
Re: An error occurred | GStreamer encountered a general stream error.
yeah I have also found this problem when I installed using Debian live usb but when I installed via Debian DVD on USB the problem was gone. I suppose problem is with the live usb installer. Also when I installed Debian on a virtual machine in windows through Debian live, the videos played fine. Don't know what this means. On Friday, 8 May 2015 10:51 AM, Muntasim Ul Haque tranjees...@inventati.org wrote: Hi, while playing most of the video files using Videos (Totem), a get an error message, saying An error occurred | GStreamer encountered a general stream error.. Videos (Totem) plays *.avi files without any error. But the problem occurs for *.mp4, *.mkv, etc. How to solve the problem? N.B. VLC player works just fine ll these file formats in my case.
Re: Uso de memória no Debian 8.0.0
Em 8 de maio de 2015 08:26, Tiago Rocha tiago.ro...@openmailbox.org escreveu: Eu indico não usar o google chrome;) Eu mesmo uso mais o Conkeror e o Epiphany segundo a necessidade, mas quando preciso de um navegador mais popular para os sítios mais chatos, uso o Chromium. Não sei se é mais leve que o Google Chrome, mas pelo menos não é uma caixa preta. -- skype:leandro.gfc.dutra?chat Yahoo!: ymsgr:sendIM?lgcdutra +55 (61) 3546 7191 gTalk: xmpp:leand...@jabber.org +55 (61) 9302 2691ICQ/AIM: aim:GoIM?screenname=61287803 BRAZIL GMT−3 MSN: msnim:chat?contact=lean...@dutra.fastmail.fm -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAFqwwS74N7XH8zGMPxUs4ocWLrCww=yuymzluvp05t8yxq2...@mail.gmail.com
Hace un twitch desde debian con OBS
Saludos a la lista. Aprovecho para escribir sobre esto: no sé si han oído o leído sobre la amplia popularidad que tienen los servicios de streaming, en concreto, twitch. Existe una forma de mostrar la pantalla del computador/ordenador a través de este servicio, pero proponen usar software externo. El más popular que recomiendan es OBS (obs-studio); sin embargo, sólo hay una opción fácil-de-usar para Ubuntu y ArchLinux: agregar la ppa, instalar las dependencias y el software y listo. Pero para otras distros no hay muchas alternativas al clásico compila-y-usa. Y yo no domino tanto el tema. ¿habrá alguna pista sobre una instalación más simple?. P.D.: Que sea una opción fácil-de-usar no da garantías de que funcione. Cuando estuve en Ubuntu, este software jamás me funcionó, y todo el tiempo tenía que enviar un informe de fallos, y no me era rentable. -- Ayuda para hacer preguntas inteligentes: http://is.gd/NJIwRz -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CALEvJmSYXDztm7U9njAWzT19`4cqpnz1xhkeotzmap6_x...@mail.gmail.com
