Re: squeeze: modifier image et couleur de grub2
Le lundi 02 mai 2011 09:31:08 giggzounet, vous avez écrit : Bonjour à tous, je fais mes premiers pas avec grub2...je lutte...Je voudrais modifier un peu le thème par défaut de debian (qui est pour squeeze assez horrible...). J'ai donc mon image png. Quelle est la méthode officielle debian pour l'utiliser dans grub2: Pour l'instant j'ai modifié /etc/default/grub et ajouté la variable GRUB_BACKGROUND. Ensuite j'ai lancé update-grub et j'ai bien mon image au reboot...Je ne sais pas si cette méthode est la mieux mais elle marche. Par contre comment modifier les couleurs du menu ??? Je trouve que modifier le /etc/grub.d/05_debian_theme est un peu barbare. Créer un nouveau fichier dans /etc/grub.d est une possibilité mais je ne trouve pas ça très user-friendly. N'y a t il pas une variable à mettre dans /etc/default/grub ? Merci d'avance Guillaume salut, je réponds tardivement. il existe des programmes pour configurer GRUB2 ici : http://kde-apps.org/content/show.php/GRUB2+Bootloader+Editor?content=139643 http://kde-apps.org/content/show.php/Grub2+Kcm?content=137886 -- 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: http://lists.debian.org/201105070845.21370.tu...@laposte.net
Re: Clef wifi USB reconnue ne détecte pas de réseau
Bonjour Bernard,
Merci pour les idées et pour les commandes à copier-coller !
(Prélude: j'ai lancé une Ubuntu en mode Live CD. Quand j'atterris dans
Gnome, je clique sur l'icône des arcs de cercle concentriques. L'interface
me propose tout de suite une liste de réseaux disponibles; je choisis le
mien, j'entre le mot de passe; ça marche du premier coup. Donc la clef
fonctionne sous Linux. Il manque juste de comprendre quelle magie opère
dans les coulisses de l'icône du wifi sous Gnome.)
| en premier et pour l'ensemble des lecteurs, serait il possible de
| donner :
| -a) la version du noyau installé
| uname -ar |awk '{print $1 $3 $5}'
~ uname -ar |awk '{print $1 $3 $5}'
Linux 2.6.32-5-686 SMP
| -b) la liste des paquets usb installés :
| dpkg -l |grep usb |awk '{print $2 $3}'
~ dpkg -l |grep usb |awk '{print $2 $3}'
libusb-0.1-4 2:0.1.12-17
libusb-1.0-0 2:1.0.8-2
libusbmuxd1 1.0.4-1
multisystem 1.0059
usb-modeswitch 1.1.4-2
usb-modeswitch-data 20100826-1+squeeze0
usbmount 0.0.21
usbmuxd 1.0.4-1
usbutils 0.87-5
xserver-xorg-video-sisusb 1:0.9.3-2
| pour mémoire :
|gestionnaire de bureau : fvwm
|dpkg -l firmware-ralink|awk '{print $2 $3}'
~dpkg -l firmware-ralink|awk '{print $2 $3}'
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
Err?=(none)/Reinst-required (Status,Err:
Name Version
firmware-ralink 0.28
| listes des paquets conseillés
| hostapd - user space IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP
| python-wicd
| wicd
| wicd-cli
| wicd-curses
| wicd-daemon
| wicd-gtk
Certains packages n'étaient pas encore installés. Je les ai ajoutés par:
apt-get install hostapd wicd-cli wicd-curses
Quand je branche la clef usb wifi, elle apparaît maintenant comme wlan1
dans ifconfig.
| apt-cache show networkconf
~# apt-cache show networkconf
N: Unable to locate package networkconf
E: No packages found
~# apt-cache search networkconf
knetworkconf - network configuration tool
~# apt-cache search network | grep network | grep conf | grep ^net | cut -d ' '
-f 1
netenv
netscript-2.4-upstart
netscript-2.4
network-config
Aucun (y compris knetworkconf) ne correspond à la description suivante:
| Network/Wifi configuration tool Simple tool for quickly
| configuring eth and wlan devices for Debian-based
| distributions using /etc/network/interfaces.
| Initially for the Morphix project, this tool also provides
| WEP options for wireless network cards.
| je n'ai pas de solution directe à donner, mais simplement pour
| aporter une piste de réflexion
C'est déjà utile, merci.
Nouvel essai, après avoir décommenté les lignes concernant wlan1 dans
/etc/network/interfaces (où j'ai également changé wlan0 en wlan1):
~# ifdown wlan1 ifup wlan1
ifdown: interface wlan1 not configured
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlan1/34:08:04:94:0f:a9
Sending on LPF/wlan1/34:08:04:94:0f:a9
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 9
^C
~# iwlist wlan1 scan
wlan1 No scan results
Bouh.
Je manque d'idée pour faire le pas suivant... Merci d'avance pour votre
aide !
Seb.
--
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:
http://lists.debian.org/Pine.LNX.4.58.1105071309070.29754@ybpnyubfg.ybpnyqbznva
Cherche expert mdadm ...
Bonjour, Je suis un peu en crise car mon raid vient de me planter très méchamment sur ma Debian Squeeze. Sur un poste, j'avais mis un raid miroir entre deux disques. L'un d'eux a décidé de m’embêter il a une dizaine de jours : il avait des secteurs abimé (ou autres) et les tests smart s'arrêtait à 90%. Je l'ai donc sorti physiquement du raid (bien sûr en oubliant de faire set-faulty et removed ...). Je l'ai mis sur un autre poste où je l'ai testé avec l'utilitaire du constructeur (DxDiag de Western Digital) avant de le renvoyer. Et Là miracle l'utilitaire a trouvé un moyen de me le réparer ! J'étais bien aise, plus d'erreur plus de bug sous smart. Je l'ai donc remis dans mon poste et ai fait un mdadm --add (blablabla..) pour le remettre dans le raid. Il a tourné quelques heures en rebuild et à la fin je n'avais plus le raid comme avant : Le premier disque est resté en active sync et le second en spare... Je crois qu'il ne manquait plus qu'a faire mdadm --assemble... mais sans certitude. Pas eu le temps de vérifier, aujourd'hui, je ne sais pas ce qui est arrivé au premier disque mais il s'est lui complètement planté : disque HS, même plus reconnu par le bios. D'un coup sans avertissement et sans même une alerte smart. J'avoue que je suis un peu vert là. Bref je me dis que le second disque est quand même encore bon. Mais non mdadm ne me le reconnait pas du tout et je ne sais pas quoi faire :s Quelques résultats de commandes mdadm : # mdadm-startall W: mdadm: using ARRAYs defined in existing mdadm.conf. Generating udev events for MD arrays...done. # cat /proc/mdstat Personalities : [raid1] unused devices: none # mdadm --examine --scan ARRAY /dev/md1 UUID=e6d41a96:ca63711a:333fb2a5:6fcb4886 spares=1 # mdadm --assemble /dev/md0 /dev/dm-5 mdadm: No suitable drives found for /dev/md0 Et pourtant si je fais un examen du disque, il est ok mais son state est a spare. # mdadm --examine /dev/dm-5 /dev/dm-5: Magic : a92b4efc Version : 0.90.00 UUID : e6d41a96:ca63711a:333fb2a5:6fcb4886 (local to host loki) Creation Time : Thu Feb 11 22:39:46 2010 Raid Level : raid1 Used Dev Size : 976759360 (931.51 GiB 1000.20 GB) Array Size : 976759360 (931.51 GiB 1000.20 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Update Time : Sat May 7 12:04:57 2011 State : clean Active Devices : 1 Working Devices : 2 Failed Devices : 1 Spare Devices : 1 Checksum : d102c881 - correct Events : 1153340 Number Major Minor RaidDevice State this 2 253 5 2 spare /dev/dm-5 0 0 253 4 0 active sync 1 1 0 0 1 faulty removed 2 2 253 5 2 spare /dev/dm-5 La configuration qui marchait jusque là : # cat /etc/mdadm/mdadm.conf DEVICE partitions CREATE owner=root group=disk mode=0660 auto=yes HOMEHOST system MAILADDR hina...@gmail.com # This file was auto-generated on Wed, 31 Mar 2010 22:14:09 +0200 # by mkconf 3.0.3-2 ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 spares=0 UUID=e6d41a96:ca63711a:333fb2a5:6fcb4886 devices=/dev/dm-4,/dev/dm-5 L'UUID de mon disque semble bon aussi : # blkid /dev/dm-5 /dev/dm-5: UUID=e6d41a96-ca63-711a-333f-b2a56fcb4886 TYPE=linux_raid_member Je ne sais plus quoi faire donc si quelqu'un a des pistes à me proposer ce sera avec une grande joie !!! -- 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: http://lists.debian.org/banlktiksljkg9pafmrx8vhgtj3arw37...@mail.gmail.com
Re: Clef wifi USB reconnue ne détecte pas de réseau
Le vendredi 6 mai 2011, Seb a écrit : | Cette clé USB marche très bien, juste un peu capricieuse et parfois | lente pour accrocher le n° IP depuis le serveur DHCP. Lente comment ? Pourrais-tu copier-coller un exemple de transaction qui s'affiche par /etc/init.d/networking restart ? Merci pour ton aide et pour ces pistes ! Seb. Avec plaisir ... ! Il n'y a pas de message d'erreur, le PC, via la clé USB, tente 5 à 6 fois d'accrocher le n° IP, puis abandonne. Il suffit de relancer : # ifdown wlan0 # ifup wlan0 et la seconde fois, ça accroche. Parfois, je dois retirer la clé puis la remettre. Sous Windows XP et Seven, ça accroche tout de suite ... En espérant que ta connexion va marcher pour toi. -- 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: http://lists.debian.org/201105071613.25052.cor...@free.fr
Re: Cherche expert mdadm ...
Le 07/05/2011 15:43, Hinault a écrit : Bonjour, Bonjour Pas trop d'idée, mais le mdadm --examine donne /dev/md1 et par la suite le fichier de conf donne /dev/md0 Il n'y aurait une inversion ? A+ -- 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: http://lists.debian.org/4dc57888.9060...@shom.fr
Re: Cherche expert mdadm ...
Le 7 mai 2011 18:51, Le Bris Pascal pascal.le.b...@shom.fr a écrit : Il n'y aurait une inversion ? Ben j'y ais pensé aussi, j'ai modifié le fichier en mettant md1 mais ca n'a rien changé. Je ne sais pas où examine va chercher le md1, j'en ai jamais eu. Merci de l'idée -- 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: http://lists.debian.org/banlktim_yw2chvvktqg53ezx6b7lj7y...@mail.gmail.com
Re: Cherche expert mdadm ...
Le 07/05/2011 19:56, Hinault a écrit : Le 7 mai 2011 18:51, Le Bris Pascalpascal.le.b...@shom.fr a écrit : Il n'y aurait une inversion ? Ben j'y ais pensé aussi, j'ai modifié le fichier en mettant md1 mais ca n'a rien changé. Je ne sais pas où examine va chercher le md1, j'en ai jamais eu. Merci de l'idée Et que 'voit' le système ? ls -l /dev/md* Chez moi j'ai (j'avais donné des label a mes partitions) : root@dom0:~# ls -l /dev/md* brw-rw 1 root disk 9, 125 30 avril 16:33 /dev/md125 brw-rw 1 root disk 9, 126 30 avril 16:33 /dev/md126 brw-rw 1 root disk 9, 127 30 avril 16:33 /dev/md127 /dev/md: total 0 lrwxrwxrwx 1 root root 8 30 avril 16:33 dom0 - ../md127 lrwxrwxrwx 1 root root 8 30 avril 16:33 swap - ../md126 lrwxrwxrwx 1 root root 8 30 avril 16:33 xen - ../md125 -- 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: http://lists.debian.org/4dc58bcf.9030...@shom.fr
problème « find -execdir mv » sous Sid
Bonjour à tous,
J'ai le problème suivant sous Sid :
___
$ tree -F --noreport
.
|__ test/
|__ TEST01
$ find . -regex .*TEST01 -execdir mv '{}' test \;
$ tree -F --noreport
.
|__ test/
|__ test
Y'aurait-il un aimable collègue sidien dans la salle pour me dire si
c'est reproductible ?... ou pour m'expliquer la raison de ce
comportement irritant ? :)
J'ai également essayé avec un compte utilisateur « vierge » mais sans
succès. Par contre, le problème n'existe ni sous Squeeze ni sous
Slackware (13.37), qui donnent le résultat attendu.
Dans tous les cas, l'interpréteur était « bash » et la version des
findutils sous Sid est la 4.4.2-1+b1
Merci d'avance,
Alexandre
--
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: http://lists.debian.org/20110507203445.GB2301@localhost
problème « find -execdir mv » sous Sid
Bonjour à tous,
J'ai le problème suivant sous Sid :
___
$ tree -F --noreport
.
|__ test/
|__ TEST01
$ find . -regex .*TEST01 -execdir mv '{}' test \;
$ tree -F --noreport
.
|__ test/
|__ test
Y'aurait-il un aimable collègue sidien dans la salle pour me dire si
c'est reproductible ?... ou pour m'expliquer la raison de ce
comportement irritant ? :)
J'ai également essayé avec un compte utilisateur « vierge » mais sans
succès. Par contre, le problème n'existe ni sous Squeeze ni sous
Slackware (13.37), qui donnent le résultat attendu.
Dans tous les cas, l'interpréteur était « bash » et la version des
findutils sous Sid est la 4.4.2-1+b1
Merci d'avance,
Alexandre
--
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: http://lists.debian.org/20110507204249.GA2891@localhost
Re: problème « find -execdir mv » sous Sid
Le Sat, 7 May 2011 22:40:29 +0200,
debiancbien debiancb...@gmail.com a écrit :
Bonjour à tous,
J'ai le problème suivant sous Sid :
___
$ tree -F --noreport
.
|__ test/
|__ TEST01
$ find . -regex .*TEST01 -execdir mv '{}' test \;
$ tree -F --noreport
.
|__ test/
|__ test
Y'aurait-il un aimable collègue sidien dans la salle pour me dire si
c'est reproductible ?... ou pour m'expliquer la raison de ce
comportement irritant ? :)
J'ai également essayé avec un compte utilisateur « vierge » mais sans
succès. Par contre, le problème n'existe ni sous Squeeze ni sous
Slackware (13.37), qui donnent le résultat attendu.
Dans tous les cas, l'interpréteur était « bash » et la version des
findutils sous Sid est la 4.4.2-1+b1
Merci d'avance,
Alexandre
bonjour,
serait il possible de donner la version du shell Bash employé
sui vant la distribution ?
ensuite, essaye de vérifier avec un shell différent :
pdksh ( très ancien )
zsh ( plus récent )
slt
bernard
--
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:
http://lists.debian.org/20110507232545.4da92cca.bernard.schoenacker_free.fr@hamtaro
Re: problème « find -execdir mv » sous Sid
On Sat, May 07, 2011 at 11:25:45PM +0200, Bernard Schoenacker wrote:
Le Sat, 7 May 2011 22:40:29 +0200,
debiancbien debiancb...@gmail.com a écrit :
J'ai le problème suivant sous Sid :
___
$ tree -F --noreport
.
|__ test/
|__ TEST01
$ find . -regex .*TEST01 -execdir mv '{}' test \;
$ tree -F --noreport
.
|__ test/
|__ test
Y'aurait-il un aimable collègue sidien dans la salle pour me dire si
c'est reproductible ?... ou pour m'expliquer la raison de ce
comportement irritant ? :)
J'ai également essayé avec un compte utilisateur « vierge » mais sans
succès. Par contre, le problème n'existe ni sous Squeeze ni sous
Slackware (13.37), qui donnent le résultat attendu.
Dans tous les cas, l'interpréteur était « bash » et la version des
findutils sous Sid est la 4.4.2-1+b1
bonjour,
serait il possible de donner la version du shell Bash employé
sui vant la distribution ?
ensuite, essaye de vérifier avec un shell différent :
pdksh ( très ancien )
zsh ( plus récent )
slt
bernard
Bonjour Bernard, oui c'est possible :
Slackware (13.37)
- bash version 4.1.10(2)
- findutils 4.4.2
Squeeze
- bash version 4.1.5(1) (même que Sid)
- findutils 4.4.2-1+b1 (même que Sid)
Sid
- bash version 4.1.5(1)
- findutils 4.4.2-1+b1
Et le test suggéré avec zsh produit le même résultat erroné (sous Sid
donc).
J'ai oublié de préciser que les « locale » sont les même pour Sid et
Squeeze (en particulier LANG=fr_CH.UTF-8), mais en_US pour Slack. J'ai
également essayé de précéder ma commande $find avec LANG=en et le
problème est le même.
--
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: http://lists.debian.org/20110507221905.GA3363@localhost
Re: Cherche expert mdadm ...
Le 07/05/2011 15:43, Hinault a écrit : Bonjour, Je suis un peu en crise car mon raid vient de me planter très méchamment sur ma Debian Squeeze. Sur un poste, j'avais mis un raid miroir entre deux disques. L'un d'eux a décidé de m’embêter il a une dizaine de jours : il avait des secteurs abimé (ou autres) et les tests smart s'arrêtait à 90%. Je l'ai donc sorti physiquement du raid (bien sûr en oubliant de faire set-faulty et removed ...). Je l'ai mis sur un autre poste où je l'ai testé avec l'utilitaire du constructeur (DxDiag de Western Digital) avant de le renvoyer. Et Là miracle l'utilitaire a trouvé un moyen de me le réparer ! J'étais bien aise, plus d'erreur plus de bug sous smart.[ [...] Je ne sais plus quoi faire donc si quelqu'un a des pistes à me proposer ce sera avec une grande joie !!! Je n'ai pas de solution à ton problème, mais pour les erreurs de secteurs il faut tester le disque avant de l'utiliser pour le RAID logiciel ou après qu'il est été viré de la grappe et avant de le ré-insérer : while (1); do /sbin/mkfs.ext2 -ccv /dev/ton_disque done Les options -cc demandent de faire un test en lecture / écriture sur le disque, test destructeur qui va écrire et vérifier différents motifs. Tu laisses tourner le formatage un à deux jours, selon la taille du disque et la vitesse d'écriture pour réaliser plus d'une dizaine de formatage. Le but est que le firmware du disque note tous les secteurs défectueux. La roadmap du développeur de mdadm prévoit enfin l'ajout d'un journal des secteurs défectueux pour éviter qu'un disque soit éjecter de la grappe au moindre secteur défectueux : http://lwn.net/Articles/428206 http://neil.brown.name/blog/20110216044002 -- 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: http://lists.debian.org/4dc5c6c4.40...@juliana-multimedia.com
Re: problème « find -execdir mv » sous Sid
Le Sun, 8 May 2011 00:19:05 +0200,
alexandre ac...@bluewin.ch a écrit :
On Sat, May 07, 2011 at 11:25:45PM +0200, Bernard Schoenacker wrote:
Le Sat, 7 May 2011 22:40:29 +0200,
debiancbien debiancb...@gmail.com a écrit :
J'ai le problème suivant sous Sid :
___
$ tree -F --noreport
.
|__ test/
|__ TEST01
$ find . -regex .*TEST01 -execdir mv '{}' test \;
$ tree -F --noreport
.
|__ test/
|__ test
Y'aurait-il un aimable collègue sidien dans la salle pour me dire
si c'est reproductible ?... ou pour m'expliquer la raison de ce
comportement irritant ? :)
J'ai également essayé avec un compte utilisateur « vierge » mais
sans succès. Par contre, le problème n'existe ni sous Squeeze ni
sous Slackware (13.37), qui donnent le résultat attendu.
Dans tous les cas, l'interpréteur était « bash » et la version des
findutils sous Sid est la 4.4.2-1+b1
bonjour,
serait il possible de donner la version du shell Bash
employé sui vant la distribution ?
ensuite, essaye de vérifier avec un shell différent :
pdksh ( très ancien )
zsh ( plus récent )
slt
bernard
Bonjour Bernard, oui c'est possible :
Slackware (13.37)
- bash version 4.1.10(2)
- findutils 4.4.2
Squeeze
- bash version 4.1.5(1) (même que Sid)
- findutils 4.4.2-1+b1 (même que Sid)
Sid
- bash version 4.1.5(1)
- findutils 4.4.2-1+b1
Et le test suggéré avec zsh produit le même résultat erroné (sous Sid
donc).
J'ai oublié de préciser que les « locale » sont les même pour Sid et
Squeeze (en particulier LANG=fr_CH.UTF-8), mais en_US pour Slack. J'ai
également essayé de précéder ma commande $find avec LANG=en et le
problème est le même.
bonjour,
va faloir faire tout un chni pour y arriver
que donne :
grep '=' /etc/default/localization-config
(réponse ) RUNATBOOT=false
grep '=' /etc/default/locale
( réponse chez moi ) LANG=fr_FR.UTF-8
( réponse chez toi ) LANG=fr_CH.UTF-8
en version ( debian ) apt-cache policy tree
tree:
Installé : 1.5.3-2
Candidat : 1.5.3-2
Table de version :
*** 1.5.3-2 0
500 http://ftp2.fr.debian.org/debian/ sid/main i386 Packages
500 http://ftp.de.debian.org/debian/ sid/main i386 Packages
500 http://ftp.uni-stuttgart.de/debian/ testing/main i386 Packages
500 http://ftp.at.debian.org/debian/ testing/main i386 Packages
100 /var/lib/dpkg/status
question :
serait il possible de savoir si sur la version en service Sid
le paquet à été employé :
apt-cache search utf8 migration
utf8-migration-tool - Debian UTF-8 migration wizard
j'espère que c'est reproductible et que grâce à ce genre de
comportement il soit possible de déclarer un incident ...
slt
bernard
--
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:
http://lists.debian.org/20110508063858.5db05097.bernard.schoenacker_free.fr@hamtaro
Re: Guardar reglas iptables en debian squeeze
El Fri, 06 May 2011 16:05:53 -0500, Edgar Vargas escribió: El día 6 de mayo de 2011 14:46, Camaleón noela...@gmail.com escribió: Tal como esta en la wiki Sí, todo parece correcto. Prueba a cargar las reglas una vez iniciado el equipo: iptables-restore /etc/iptables.test.rules Y ejecuta después iptables -L para ver qué te dice. Gracias amiga camaleon por responder, eso sería en forma manual y como comprenderás yo deseo que sea automático, pero lo probaré cuando regrese a retomar el servidor; Sí, eso ya lo sé :-) Lo que estoy intentando comprobar es dónde está el error: a) En la carga del script, que falla b) En las propias reglas, que tienen algún problema Si cargas las reglas de forma manual y todo funciona correctamente, entonces el problema es que al iniciar el equipo no se cargan bien (de ahí el error que te aparece al iniciar y que tendrías que revisar con más calma). Si cargas las reglas de forma manual y tienes algún problema (no te permite hacer ping al exterior), entonces es que tienes las reglas mal y tendrías que revisarlas. lo extraño es que al parecer si aplica las reglas porque si hace nat y reenvia, y todas las reglas que le puse a squid, nada mas que es un poco diferente a cuando lo hago manualmente, solo que no hace ping a ips publicas, supongo que todo lo que salga trata de pasarlo al proxy, pero si solo le dije que reenvie peticiones al puerto 80, i don't know :O, No adivines, haz las pruebas y extrae conclusiones con los datos en la mano ;-) amiga camaleon como te decia cuando esta iniciando el sistema me sale en los mensajes de inicio en la ruta donde esta el restore, such file or directory como que no lo encuentra... Activa el registro del inicio para ver qué es eso... Vete a/etc/default/ bootlogd y pon: BOOTLOGD_ENABLE=Yes Amiga camaleon como guardas las reglas iptables cuando usas ello? Eso es lo que estamos intentando averiguar, pero primero hay que saber qué es lo que está fallando en este caso. 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: http://lists.debian.org/pan.2011.05.07.09.08...@gmail.com
Re: conexion internet perdida tras aptitude safe-upgrade
El Fri, 06 May 2011 22:05:13 -0500, Laura Pamela escribió: El problema es justamente el que describe el subject. Es la segunda vez que lo leo. En la lista inglesa hay un usuario con un problema similar :-? OS: wheezy ## contenido de interfaces # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp ### Realmente la puedo levantar con # ifup eth0 Y es lo que acabo de usar para conectarme y escribir este correo, pero como hacer esto permanente, tal como estaba antes, sin tener que ejecutar este comando cada vez que se reinicie el sistema. Yo también estoy con wheezy y tengo exactamente lo mismo que tú en el archivo /etc/network/interfaces pero la red levanta sin problemas, al menos de momento... Curioso. Mira en el registro, a ver: grep -i eth0 /var/log/syslog* 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: http://lists.debian.org/pan.2011.05.07.09.22...@gmail.com
Re: Instalación de flash plugin en firefox 4
El día 4 de mayo de 2011 08:54, Julio César García Vizcaíno juliocesar.garciavizca...@garviz.mx escribió: El 3 de mayo de 2011 20:22, Nicolás Bevilacqua nicobevilac...@gmail.com escribió: Yo instalé el iceweasel 4 y, si mal no recuerdo, instalando el plugin normalmente era reconocido por el browser. Lo hice agregando el siguiente repositorio: # Iceweasel 4 experimental repository deb http://mozilla.debian.net/ squeeze-backports iceweasel-4.0 Aunque tiene un bug, que cada tanto se cierra solo y el error que tira en la consola es segmentation fault. Fijate si te sirve instalarlo así. Saludos, Nicolás. -- In a world without Fences and Walls, who needs Windows and Gates? Muchas gracias el repositorio me funcionó perfecto. -- Cordiales saludos, Best regards M.Sc. Julio Cesar Garcia Vizcaino Ph.D High Performance Computing (Attending), 2014 (UAB) http://www.safe.mx/ Linkedin profile: http://mx.linkedin.com/in/garviz Por lo menos cuando tuve que instalar Flash para icewasel en debian, baje el de 64 bit que estaba disponible en la web de adobe, baje el source y lo cargue a mano y no tengo problemas con los flashes, puedo ver videos en youtube sin problema, sin cortes y no se me cierra el navegador, lo unico si es que cuando la maquina esta con muchas cosas abiertas U!!! :P y pongo un youtube este se pega un segundo cuando el video va en proceso. pero nada que no me deje verlo igual en el momento. Saludos Cordiales -- Roberto Quiñones Owner - Service Manager and System ACShell.NET – Internet Services robe...@acshell.net - www.acshell.net San Martin #311 Santiago – CL (Chile) +560981361713 -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTikoEPo_FÎwfa-cyjqmqybmik...@mail.gmail.com
Re: Lentitud acceso internet.
El 6 de mayo de 2011 17:16, Odair Augusto Trujillo Orozco hald...@gmail.com escribió: El 6 de mayo de 2011 13:59, Esteban Torres Rodríguez mortenol.tor...@gmail.com escribió: or vpn para probar ahora que no hay carga ninguna en la red y un dvd de debian de un Hola, me gustaría que probaras cambiar tus DNS, por algún motivo hay algunos routers que con un cliente Linux van mal en resolución de DNS, con uno de los míos me toca poner los DNS del ISP directamente, sino tamibén podés probar poner los dns de google o los open-dns. Cuenta que te pasa haaa y no borren el mensaje anterior, respondan debajo. Y por favor no usen html. Gracias. -- usuario linux #274354 normas de la lista: http://wiki.debian.org/NormasLista como hacer preguntas inteligentes: http://www.sindominio.net/ayuda/preguntas-inteligentes.html -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTikè_bj0+j=dhcayj0q5evu-v...@mail.gmail.com
Re: OT. Sobre celular que pueda utilizar cliente de ssh via WiFi o red celular
El mié, 06-04-2011 a las 11:37 -0300, Nicolás Bevilacqua escribió: El 06/04/2011 03:17 a.m., Marc Olive escribió: On Tuesday 05 April 2011 22:48:52 tq wrote: Marc, gracias por la respuesta. Tu que me recomendarías? Yo estoy muy contento con el N900, lo uso mucho mas de lo que creia. He dejado de considerarlo como celular, para mi y el uso que le doy (administrar sistemas, scripting, correo, chat/msn) a estas alturas lo considero un computador de bolsillo. Pero como decia el anuncio: busque, compare y si encuentra algo mejor, comprelo!. Muchas Gracias. Saludos. Saludos, Yo tenía muchas ganas de comprarme un n900 a pesar de su precio. Lastima que Nokia le da cada vez menos atención a Maemo/Meego . Sobre todo ahora con las últimas noticias :-( . Saludos, Nicolás. Hola que tal? estoy viendo que existen clientes ssh(putty) para el symbian s60. Yo tengo un nokia c3 que viene con symbian S40...tienen conocimiento si puede llegar a funcionar esa version de putty en el C3?? Muchas gracias -- Saludos Juan Pablo Alesandri GNU/Linux Registered User:#333844 GnuPG Public Key ID: 8A2B7F96 --- signature.asc Description: Esto es una parte de mensaje firmado digitalmente
[solucionado] Re: conexion internet perdida tras aptitude safe-upgrade
Hola On Sat, May 7, 2011 at 12:04 AM, BasaBuru basab...@basatu.org wrote: # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp El allow-hotplug si no tienes un portatil lo puedes cambiar por auto. Sirve para que cuando pinchas el cable se levante sola. Funciona con tu el cambio que sugieres: ### auto lo iface lo inet loopback # The primary network interface #allow-hotplug eth0 auto eth0 iface eth0 inet dhcp ### Pero me queda una pregunta: por que antes funcionaba sin el auto? De hecho en el directorio hay unos backup del archivo interfaces que seguramente ha hecho el sistema y están igualitos al interfaces Realmente la puedo levantar con # ifup eth0 despues de un ifdown eth0 si tenías levantada el eth0 Creo que no entendi lo que dices aca. Me funciona con ifup eth0 sin hace previamente un ifdown eth0 BasaBuru, Gracias por tu solución. Igual me gustaría encontrar respuesta a mi pregunta para no me quedarme con la duda. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktikwdh_skjih2wfod+kggcjrcdm...@mail.gmail.com
Re: [solucionado] Re: conexion internet perdida tras aptitude safe-upgrade
On Sábado 07 Mayo 2011 20:29:48 Laura Pamela escribió: hola: Funciona con tu el cambio que sugieres: ### auto lo iface lo inet loopback # The primary network interface #allow-hotplug eth0 auto eth0 iface eth0 inet dhcp ### Pero me queda una pregunta: por que antes funcionaba sin el auto? De hecho en el directorio hay unos backup del archivo interfaces que seguramente ha hecho el sistema y están igualitos al interfaces Pudes tener algun tipo de incidencia con udev que se encarga de levantar servicios en caliente entre otras muchas cosas. Pero desde aquí no se que decirte. Ten en cuenta que has desactivado el que cuando pinchas el cable se levante la interface y que la tumbe cuando lo sacas. Realmente la puedo levantar con # ifup eth0 despues de un ifdown eth0 si tenías levantada el eth0 Creo que no entendi lo que dices aca. Me funciona con ifup eth0 sin hace previamente un ifdown eth0 Eso es por que antes no estaba levantada. si tu tienes levantada la interface, cambias de dchp a static por ejemplo. Necesitas tumbarla para volver a levantarla en caliente. Ahora cuando arrancas la máquina se levanta. Si haces un ifup te dice que ya esta levantada. ifup: interface eth0 already configured Haces cambios en el interfaces y tumbas y levantas en caliente y los cambios se activan. No se si me he explicado muy bien. BasaBuru, Gracias por tu solución. Igual me gustaría encontrar respuesta a mi pregunta para no me quedarme con la duda. Si no te ha resultado adecuada la respuesta hablamos mas. Un saludo BasaBuru -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105072150.30416.basab...@basatu.org
Compartir internet por wi-fi
Saludos amigos de la comunidad. Ya me e googleado y no encuentro la solucion a este problema :(. yo me conecto a internet atraves de un Modem [ZTE mf626] de claro [Guatemala] y quisiera poder conpartir la señal por una coneccion wi-fi [Ad-hoc]. pero no se como hacerlo. ¿podrían ayudarme? gracias a todos . -- Robinson E. Guevara R. https://profiles.google.com/RobinsonGuevara Debian https://picasaweb.google.com/lh/photo/oNccd9BOhrd8hLmkL6JAUA?feat=directlink
Re: Compartir internet por wi-fi
Hola. El 07/05/11 16:08, Robinson Guevara escribió: Saludos amigos de la comunidad. Ya me e googleado y no encuentro la solucion a este problema :(. yo me conecto a internet atraves de un Modem [ZTE mf626] de claro [Guatemala] y quisiera poder conpartir la señal por una coneccion wi-fi [Ad-hoc]. pero no se como hacerlo. ¿podrían ayudarme? gracias a todos . -- Probablemente esto te ayude. http://lmgtfy.com/?q=linux+compartir+conexion+wifi Saludos. Robinson E. Guevara R.https://profiles.google.com/RobinsonGuevara Debian https://picasaweb.google.com/lh/photo/oNccd9BOhrd8hLmkL6JAUA?feat=directlink -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc5ca7f.2040...@gmail.com
Re: Compartir internet por wi-fi
2011/5/7 Robinson Guevara robinsonguev...@gmail.com Saludos amigos de la comunidad. Ya me e googleado y no encuentro la solucion a este problema :(. yo me conecto a internet atraves de un Modem [ZTE mf626] de claro [Guatemala] y quisiera poder conpartir la señal por una coneccion wi-fi [Ad-hoc]. pero no se como hacerlo. ¿podrían ayudarme? gracias a todos . Usas network-manager? click derecho en su icono en el área de notificación y creas una nueva red inalámbrica. -- Linux Registered User # 386081 A menudo unas pocas horas de Prueba y error podrán ahorrarte minutos de leer manuales. -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimq56l13meqenp0-+nvsjkvjjq...@mail.gmail.com
Re: Compartir internet por wi-fi
On Domingo 08 Mayo 2011 04:18:20 Carlos Zuniga escribió: 2011/5/7 Robinson Guevara robinsonguev...@gmail.com Saludos amigos de la comunidad. Ya me e googleado y no encuentro la solucion a este problema :(. yo me conecto a internet atraves de un Modem [ZTE mf626] de claro [Guatemala] y quisiera poder conpartir la señal por una coneccion wi-fi [Ad-hoc]. pero no se como hacerlo. ¿podrían ayudarme? gracias a todos . Usas network-manager? click derecho en su icono en el área de notificación y creas una nueva red inalámbrica. Eso suponiendo que el equipo tiene wireless. Si no tendrá que usar una tarjeta wireless. Un saludo BasaBuru -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105080658.35042.basab...@basatu.org
Firefox/iceweacel y 4shared.com
Hola a todos Resulta que intento bajar algunos libros de www.4shared.com usando tanto iceweacel y/o firefox y siempre me retorna con un: 400 Bad request Your browser sent an invalid request. Que puede estar pasando ? Firefox en guindos lo hace bien. Saludos -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110508020348.58b88275.c...@adinet.com.uy
Re: Compartir internet por wi-fi
El 08/05/11 00:28, BasaBuru escribió: On Domingo 08 Mayo 2011 04:18:20 Carlos Zuniga escribió: 2011/5/7 Robinson Guevararobinsonguev...@gmail.com Saludos amigos de la comunidad. Ya me e googleado y no encuentro la solucion a este problema :(. yo me conecto a internet atraves de un Modem [ZTE mf626] de claro [Guatemala] y_*quisiera poder conpartir la señal por una coneccion wi-fi*_ [Ad-hoc]. pero no se como hacerlo. ¿podrían ayudarme? gracias a todos . Usas network-manager? click derecho en su icono en el área de notificación y creas una nueva red inalámbrica. Eso suponiendo que el equipo tiene wireless. Si no tendrá que usar una tarjeta wireless. ¿Qué me perdí? Un saludo Saludos BasaBuru -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc62689.5080...@gmail.com
Re: Compartir internet por wi-fi
On Domingo 08 Mayo 2011 07:13:45 Juan Lavieri escribió: El 08/05/11 00:28, BasaBuru escribió: On Domingo 08 Mayo 2011 04:18:20 Carlos Zuniga escribió: 2011/5/7 Robinson Guevararobinsonguev...@gmail.com Saludos amigos de la comunidad. Ya me e googleado y no encuentro la solucion a este problema :(. yo me conecto a internet atraves de un Modem [ZTE mf626] de claro [Guatemala] y_*quisiera poder conpartir la señal por una coneccion wi-fi*_ [Ad-hoc]. pero no se como hacerlo. ¿podrían ayudarme? gracias a todos . Usas network-manager? click derecho en su icono en el área de notificación y creas una nueva red inalámbrica. Eso suponiendo que el equipo tiene wireless. Si no tendrá que usar una tarjeta wireless. ¿Qué me perdí? Pues que no ha dicho que equipamiento tiene. Si tiene tarjeta wifi en el equipo, si es un portatil, el modelo de la tarjeta (algunas no se pueden poner en ad-hoc), etc. Lo lamento he sido demasiado escueto. sorry :-( Un saludo BasaBuru -- To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105080743.53615.basab...@basatu.org
Saliec rokas uz vidukļa puskailai meičai
Apliec rokas uz pleciem puskailai meičai, nolūko izcilu dzērienu bārā un noskaties erotisko šovu.. Tikko atvērts un klientiem pretīmnākošs klubs gaida tevi un tavus draugus - mēs nesortējam viesus, mums katrs ir svarīgs: vai no Rīgas, vai ārvalstīm. Pieejamas cenas, vāciešu menedžeri - detaļas uzzini t.e: http://cc.st/0ed1c6 -- To UNSUBSCRIBE, email to debian-user-danish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507211946.b552f1cc...@jazz.rusoft.ru
Re: Re: problema com mouse e teclado usb
Olha, Eu tive problemas desse tipo (após atualizacao o mouse e nem o teclado funcionavam no X) e resolvi fazendo downgrade. As versoes que funcionam estão neste post [1]. Mas, nao lembro as versoes que nao funcionaram. 1. http://lists.debian.org/debian-user-portuguese/2011/04/msg00199.html -- O__ --- Marcelo Luiz de Laia -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktikqfoxrjafokndehsyfvi+wwxc...@mail.gmail.com
Re: Problema com som
Saudações. Eden, eu estava tendo esse mesmo problema em minha instalação Debian, como relatei em outra thread, e instalei esse pacote e o problema se resolveu como mágica rsrsrs Vc poderia explicar o que é esse pacote??? Obrigado. On 05-05-2011 14:57, Eden Caldas wrote: Você disse um problema com som, que problema é esse? Instale esse pacote pra ver se resolve firmware-linux-nonfree Eden Caldas Consultor de TI e...@linuxfacil.srv.br (81) 9653 7220 LINUX FÁCIL Consultoria e Serviços em TI Em 5 de maio de 2011 14:48, Ronaldo Reis Junior chrys...@gmail.com escreveu: Pessoal, estou tendo problema com o meu som nesta nova instalação testing amd64, coloquei no /etc/modules para carregar o modulo snd_hda_intel, no root no kde funciona normal, mas como os usuarios normais aparece só um dispositivo fictício. Já tentei setar um monte de permissões e nada foi alterado. Veja os grupos que coloquei lucas@fasterix:/root$ groups lucas daemon sys disk uucp dialout voice cdrom floppy tape audio dip list utmp video sasl plugdev staff games users libuuid mlocate utempter messagebus avahi netdev lpadmin fuse haldaemon powerdev scanner pulse pulse-access veja os dispositivos: lucas@fasterix:/root$ ls -l /dev/snd total 0 drwxr-xr-x 2 root root 80 Mai 5 15:44 by-path crw-rw 1 root audio 116, 6 Mai 5 15:44 controlC0 crw-rw 1 root audio 116, 15 Mai 5 15:44 controlC1 crw-rw 1 root audio 116, 5 Mai 5 15:44 hwC0D0 crw-rw 1 root audio 116, 14 Mai 5 15:44 hwC1D0 crw-rw 1 root audio 116, 13 Mai 5 15:44 hwC1D1 crw-rw 1 root audio 116, 12 Mai 5 15:44 hwC1D2 crw-rw 1 root audio 116, 11 Mai 5 15:44 hwC1D3 crw-rw 1 root audio 116, 4 Mai 5 15:44 pcmC0D0c crw-rw 1 root audio 116, 3 Mai 5 15:44 pcmC0D0p crw-rw 1 root audio 116, 2 Mai 5 15:44 pcmC0D1p crw-rw 1 root audio 116, 10 Mai 5 15:44 pcmC1D3p crw-rw 1 root audio 116, 9 Mai 5 15:44 pcmC1D7p crw-rw 1 root audio 116, 8 Mai 5 15:44 pcmC1D8p crw-rw 1 root audio 116, 7 Mai 5 15:44 pcmC1D9p crw-rw 1 root audio 116, 1 Mai 5 15:44 seq crw-rw 1 root audio 116, 33 Mai 5 15:44 timer Não sei o que mais pode ser. Alguma dica Obrigado Ronaldo -- 18ª lei - Seu orientador quer escrever a melhor carta de recomendação possível para você. --Herman, I. P. 2007. Following the law. NATURE, Vol 445, p. 228. Prof. Ronaldo Reis Júnior | .''`. UNIMONTES/DBG/Lab. Ecologia Comportamental e Computacional | : :' : Campus Universitário Prof. Darcy Ribeiro, Vila Mauricéia | `. `'` CP: 126, CEP: 39401-089, Montes Claros - MG - Brasil | `- Fone: (38) 3229-8192 | ronaldo.r...@unimontes.br | http://www.ppgcb.unimontes.br/lecc | LinuxUser#: 205366 -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc2e2fc.8010...@gmail.com -- Cleber Ianes Ger. de Tecnologias Livre Freenet tecnologias - Dracena/SP cleberianes.blogspot.com -- Linux User #507338 -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc554f8.6060...@yahoo.com.br
Re: Problema com som
se for pacote no packages tem texto explicando. http://packages.debian.org/squeeze/firmware-linux-nonfree -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc56862.7080...@gmail.com
Re: Problema com som
Tem drivers não livres para vários dispositivos. Eden Caldas Consultor de TI e...@linuxfacil.srv.br (81) 9653 7220 LINUX FÁCIL – Consultoria e Serviços em TI 2011/5/7 Sorocaos soroc...@gmail.com se for pacote no packages tem texto explicando. http://packages.debian.org/squeeze/firmware-linux-nonfree -- To UNSUBSCRIBE, email to debian-user-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc56862.7080...@gmail.com
Re: Idioma português brasil no BrOffice
Obrigado! não precisei nem estalar os pacotes foi so desistalar e ele pedio para atualizar uns pacotes la ai ja instalou o libre com tudo em pt-br -- Marcos Egito GNU/Linux User #491326 Fotos www.flickr.com/photos/maregito 081-8762 - 4378 celular OI, 081-3456 - 9739 casa mareg...@gmail.com Skype maregito, MSN mareg...@oi.com.br, Gtalk mareg...@gmail.com “somos um grande quebra-cabeças formado de pedacinhos de outras pessoas que nos completam. (eu mesmo!).
Apliec rokas ap apaļumiem puspilkai dejotājai
Apliec rokas uz pleciem puspilkai meičai, nolūko izcilu dzērienu bārā un noskaties erekciju izraisošu šovu.. Tikko atvērts un spožs klubs gaida tevi - mēs nešķirojam savus viesus, mums katrs ir sevišķs: vai no Latvijas, vai Hamburgas. Pieņemams cenas, vāciešu menedžments - sīkāk skaties t.e: http://goo.gl/K2Bx3 -- To UNSUBSCRIBE, email to debian-user-turkish-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507212452.dcc4e13a6...@liszt.debian.org
Re: URL shortening (was Re: Need /etc/apt/sources.list)
On Sb, 07 mai 11, 00:33:59, Arno Schuring wrote: In other words, please do not use (unnecessary) URL mangling. It needlessly makes your message useless for posterity. +1 Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Loss of connectivity on recent testing updates
On Sat 07 May 2011 at 03:21:39 +0100, AG wrote: After trying #dhclient eth0 there was no output, but I can now access the Internet. When I rebooted the machine to double check, the Net was inaccessible. There is an implication here you are using a wired connection. Is that correct? Is there someway that I can set this up so that this is automatically configured at boot time? There should be. As an aside, this is a recent re-install and the network was configured manually during that process, not through Network Manager. This implies you are using ifupdown to manage the interfaces. Thanks for any advice on getting this set up to access the Net upon boot up. As root, edit /etc/network/interfaces to have auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet dhcp Save and do ifdown -v eth0 and then ifup -v eth0. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507090416.GN13057@desktop
Re: OT: Safe to access SSH server from work?
On Jo, 05 mai 11, 23:09:02, Brian wrote: You can be confident that the default Debian install of openssh-server has a configuration which is very safe. There is nothing for you to do. While I wouldn't say that the Debian (actually upstream?) configuration is unsafe, there are ways to improve it, depending on your specific use case. Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Need /etc/apt/sources.list
On Fri, 06 May 2011 23:07:15 +0300, Dotan Cohen wrote: I just tried tinyurl with wget and got the same IP address (and 200 response) as you. I didn't check the links, though. Then? Are you still getting trouble to reach the tinyurl web site? If yes, there could be a filter/proxy in between of you and the website, that is, your ISP. That's a different issue. There is nothing that needs to be teached here because we are talking about preferences. You don't like tinyurl and that's okay, no one can blame you for that, but in the same way you can't also blame others for use it... even less when that person was willing to help you. No, this is not a matter of preference. Sure it is. Nobody can force a user to use one or other method to post into this list. You can follow the link or not, that's up to you, but blaming someone -that is trying to help you- for using tinyurl (or any other of those URL shortening services) is like an overreaction. There is no reason to pipe the links through some third party service that is unreliable and may, either through malice stupidity or hacking, compromise either the user's ability to connect to the site or perform undesirable actions (tracking, advertising, drive-by malware). Could TinyURL never be hacked? Sold? Forget to pay their hosting bill? Hardware failure? Network failure? Oh, come on! That argument is very flawed. Should we stop of using Gmail e-mail service because of the same? :-) Tinyurl, bit.ly and such have its use (mostly for twitter and sending SMS messages that enforce you a policy of limited characters) but using them in a mailing list is something is only up to the poster, not me, nor you... there is no one point in Debian mailing list netiquette stating the opposite. What advantage exists at all to use tinyURL? It does not have to exist any. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.09.41...@gmail.com
Re: Some way to restrict what apt-get/aptitude installs
On Jo, 05 mai 11, 19:55:11, Chris Brennan wrote: I've a headless server running Debian 6 and I am curious if there is a way to restrict what gets pulled in Not exactly what you are looking for, but look at apt pinning. The apt_preferences(5) man page would be a good start. Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Loss of connectivity on recent testing updates [SOLVED]
On 07/05/11 10:04, Brian wrote: On Sat 07 May 2011 at 03:21:39 +0100, AG wrote: After trying #dhclient eth0 there was no output, but I can now access the Internet. When I rebooted the machine to double check, the Net was inaccessible. There is an implication here you are using a wired connection. Is that correct? Yes, that's right. Is there someway that I can set this up so that this is automatically configured at boot time? There should be. As an aside, this is a recent re-install and the network was configured manually during that process, not through Network Manager. This implies you are using ifupdown to manage the interfaces. I'll have to take your word for that, but as below, the message is that eth0 is not configured (!?) Thanks for any advice on getting this set up to access the Net upon boot up. As root, edit /etc/network/interfaces to have auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet dhcp The file originally read: iface eth0 inet *static* (no quotes/ emphases, of course) Save and do ifdown -v eth0 The response I get to doing this is: $ sudo ifdown -v eth0 ifdown: interface eth0 not configured and then ifup -v eth0. To which, the response is: ~$ sudo ifup -v eth0 Configuring interface eth0=eth0 (inet) run-parts --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/vlan run-parts: executing /etc/network/if-pre-up.d/wpasupplicant dhclient -v -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/00:90:47:05:a3:07 Sending on LPF/eth0/00:90:47:05:a3:07 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPOFFER from 192.168.1.254 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.254 bound to 192.168.1.64 -- renewal in 40816 seconds. run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/50firestarter Stopping the Firestarter firewall Starting the Firestarter firewall run-parts: executing /etc/network/if-up.d/avahi-daemon run-parts: executing /etc/network/if-up.d/ip run-parts: executing /etc/network/if-up.d/mountnfs run-parts: executing /etc/network/if-up.d/wpasupplicant However, following your advice, I am pleased to report back that upon rebooting, at least I now have connectivity by default which is a major advance and has resolved this issue then. Thank you very much, Brian. Much appreciated! Just as an aside: as all of this happened when I rebooted after an uptime of 9 days, how could I determine which package change in updating my system during this time borked the settings? This was a very nasty surprise, but scouring the web I seem to have been the only one affected. Cheers AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc514db.4020...@gmail.com
Re: Nautilus scripts using $1
On Fri, 06 May 2011 19:23:54 -0400, Perry Thompson wrote:
Hi there. I made a nautilus script so that I can right-click on a file,
use it in a program, and then move the produced file back to the working
directory.
I made a test script to try it out.
#!/bin/bash
echo $1 $HOME/Desktop/test.txt
Shouldn't that be? :-?
echo $1 $HOME/Desktop/test.txt
When I am in any Nautilus folder and I right-click on a file and run the
script, in the contents of test.txt I have filename.
(...)
How can I fix it so I can use any file in any environment? Maybe somehow
set nautilus to use full pathnames? Any ideas?
(...)
Yep, try with:
filename=${1##*/}
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.05.07.10.13...@gmail.com
Re: Problems setting up USB printer with CUPS
On Sat, 07 May 2011 03:30:17 +0100, AG wrote: In addition to connectivity problems, I've been having problems setting up my USB Epson printer with CUPS. For one thing, the CUPS admin interface has changed since I last did this, and CUPS doesn't detect the printer as a local printer only giving me 3 options - scsi printer, HP printer HP fax (yes, I've checked - it is plugged in and turned on, etc.). (...) USB printers should be auto-magically detected by CUPS so I would first check if the printer has been detected/configured by the system (dmesg | grep usb). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.10.35...@gmail.com
Re: Loss of connectivity on recent testing updates [SOLVED]
On Sat 07 May 2011 at 10:46:03 +0100, AG wrote: The file originally read: iface eth0 inet *static* (no quotes/ emphases, of course) In which case the complete stanza should have read: iface eth0 inet static address 192.168.1.x netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.254 with x specified by you. Just as an aside: as all of this happened when I rebooted after an uptime of 9 days, how could I determine which package change in updating my system during this time borked the settings? This was a very nasty surprise, but scouring the web I seem to have been the only one affected. There may have been a configuration missetting rather thana package failure. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507102450.GO13057@desktop
Re: grub-probe: error: cannot stat `/dev/root'
On Fri, 06 May 2011 10:44:21 -0700, CACook wrote: This just started after my most recent (very painful) dist-upgrade. It seems that BTRFS is not compatible with grub and Debian. I very nearly lost my whole system because of this catastrophe. Does anyone know the nature of the error and how to fix? You're asking for so much :-) First, the btrfs filesystem is still very experimental so only use it if you really (I mean *really*) know what you are doing and also know how to deal when things go wrong. I would even expect data loss (directly or indirectly related to the usage of this filesystem) so make daily backups if needed. Second, write a bug report at Debian BTS. Every distribution applies different patches/quirks for GRUB and that can make a difference (meaning that the issue can be only visible in Debian based distros while it does not present in others). And third, where are you getting the above error (at booting, when running grub-something...?). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.10.57...@gmail.com
Re: Problems setting up USB printer with CUPS
AG (computing.acco...@googlemail.com on 2011-05-07 03:30 +0100): In addition to connectivity problems, I've been having problems setting up my USB Epson printer with CUPS. For one thing, the CUPS admin interface has changed since I last did this, and CUPS doesn't detect the printer as a local printer only giving me 3 options - scsi printer, HP printer HP fax (yes, I've checked - it is plugged in and turned on, etc.). Do you have any of the packages openprinting-ppds or cups-driver-gutenprint installed? What is the correct way of addressing the printer? For a USB do I select, under Other Network Printers (why is it an other network printer when it is connected directly to my machine?) the LPD/LPR option? None of these options really seem appropriate, and is the address given like this: lpp://localhost/epson or lpp://localhost:631/epson or ... ? port 631 is ipp, not lpp :) You should not need any of these options, once the correct printer driver (ppd) is installed, it should work immediately. If you can't get it to work, you might want to check here: http://www.openprinting.org/printers/manufacturer/Epson and select your correct model. It should give you the name (and a download link) for the recommended driver, which you can then search for in the Debian archive. I can't really say that the on-line help has been very useful and I guess my Google-fu is not what it should be because I cannot find any recent postings on this that answer this query. I always start my search with open printing database. Hope this helps, Arno -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507125851.79775...@neminis.loos.site
Re: Problems setting up USB printer with CUPS [SOLVED]
On 07/05/11 11:35, Camaleón wrote: On Sat, 07 May 2011 03:30:17 +0100, AG wrote: In addition to connectivity problems, I've been having problems setting up my USB Epson printer with CUPS. For one thing, the CUPS admin interface has changed since I last did this, and CUPS doesn't detect the printer as a local printer only giving me 3 options - scsi printer, HP printer HP fax (yes, I've checked - it is plugged in and turned on, etc.). (...) Hi Camaleón USB printers should be auto-magically detected by CUPS That's what was puzzling the heck out of me too! so I would first check if the printer has been detected/configured by the system (dmesg | grep usb). Good pointer - thanks. No it hadn't been picked up. So I replugged it into another USB port and hey presto! Why that port stopped working for the printer but now (still) works fine for a USB data storage hub, I don't know. Given the issue with connectivity (sorted out with the help of Brian others), this printer issue (now sorted thanks to you) and why the desktop appearance settings for Gnome were so borked after I rebooted is a complete mystery to me and don't seem to have anything in common on the face of it. Anyway - issue sorted, and thanks again. All the best AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc5262e.5080...@gmail.com
OT: Are you from Berlin?
Hi all, I don't know how many people read d-community-offtopic so if you are from Berlin please read this http://lists.alioth.debian.org/pipermail/d-community-offtopic/2011-May/000102.html Thanks -- Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Registered Linux User #503414 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc5326f.5080...@dobosevic.com
Now cannot ping print server from second machine
Hello (again) I don't know if this is related to the connectivity issues reported earlier, but now when trying to print from a second machine, I am unable to. The set up is my machine runs the CUPS print server and is directly connected to a USB printer. I used to be able to print from the second (client?) machine, but since this issue following a problem-riddled reboot this is no longer possible. I have tried to ping the server machine (192.168.1.40) from the client machine (192.168.1.29) but cannot. I have stopped all the firewalls (firestarter) on the *.*.*.40 machine and still no dice. The machines are still connected via a hub and that hasn't changed since before I rebooted. The client machine (*.*.*.29) can access the Internet via the same hub, but packets are being dropped when that machine tries to ping the server. The server machine can now access the Net, and can ping the client machine. Any thoughts on what I should check out for? TIA AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc52ea7.3020...@gmail.com
the package can generate xpm
Hi, are there any debian package can generate xpm file? actually I have several .xpm image, but I am trapped in how to change its color from dull grey to something about gorgeous. Thanks for any advice, -- Best Regards, lina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktim2zn1nmncuorx2lywhtwlfcp5...@mail.gmail.com
hidden folder
When I try to backup my home directory I get an error message regarding a folder called '.mozilla'. Looking at it as root there does not appear to be anything inside -- can I get rid of it or is it an essential part of iceweasel/mozilla? It doesn't stop my backup from completing -- it's just a minor annoyance. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc5361e.1040...@sentex.net
Re: the package can generate xpm
On 2011-05-07 14:04, lina wrote: Hi, are there any debian package can generate xpm file? actually I have several .xpm image, but I am trapped in how to change its color from dull grey to something about gorgeous. Thanks for any advice, Hi, GIMP can do it. -- Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Registered Linux User #503414 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc5373c.4070...@dobosevic.com
Re: the package can generate xpm
Thanks, but I still feel the gimp is not, how to say, flexible, in re-color the grey one. lina On Sat, May 7, 2011 at 8:12 PM, godo go...@dobosevic.com wrote: On 2011-05-07 14:04, lina wrote: Hi, are there any debian package can generate xpm file? actually I have several .xpm image, but I am trapped in how to change its color from dull grey to something about gorgeous. Thanks for any advice, Hi, GIMP can do it. -- Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Registered Linux User #503414 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc5373c.4070...@dobosevic.com -- Best Regards, lina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktik28kcmd7wnbvx-glahok0s8e1...@mail.gmail.com
Re: Now cannot ping print server from second machine
Dne, 07. 05. 2011 13:36:07 je AG napisal(a): Hello (again) I don't know if this is related to the connectivity issues reported earlier, but now when trying to print from a second machine, I am unable to. The set up is my machine runs the CUPS print server and is directly connected to a USB printer. I used to be able to print from the second (client?) machine, but since this issue following a problem-riddled reboot this is no longer possible. I have tried to ping the server machine (192.168.1.40) from the client machine (192.168.1.29) but cannot. I have stopped all the firewalls (firestarter) on the *.*.*.40 machine and still no dice. The machines are still connected via a hub and that hasn't changed since before I rebooted. The client machine (*.*.*.29) can access the Internet via the same hub, but packets are being dropped when that machine tries to ping the server. The server machine can now access the Net, and can ping the client machine. Any thoughts on what I should check out for? The IP of your server. On the server, issue 'ifconfig' to see if it still has the former IP (192.168.1.40). TIA AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc52ea7.3020...@gmail.com -- Cheerio, Klistvud http://bufferoverflow.tiddlyspot.com Certifiable Loonix User #481801 Please reply to the list, not to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304771175.28162.0@compax
Re: hidden folder
Dne, 07. 05. 2011 14:07:58 je John Lindsay napisal(a): When I try to backup my home directory I get an error message regarding a folder called '.mozilla'. Looking at it as root there does not appear to be anything inside -- can I get rid of it or is it an essential part of iceweasel/mozilla? It doesn't stop my backup from completing -- it's just a minor annoyance. It contains ALL your firefox/iceweasel settings, cookies, browser hisory, browser cache and what not. You absolutely sure it's empty? Don't use iceweasel/firefox? John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc5361e.1040...@sentex.net -- Cheerio, Klistvud http://bufferoverflow.tiddlyspot.com Certifiable Loonix User #481801 Please reply to the list, not to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304771339.28162.1@compax
Re: hidden folder
On 2011-05-07 14:07, John Lindsay wrote: When I try to backup my home directory I get an error message regarding a folder called '.mozilla'. Looking at it as root there does not appear to be anything inside -- can I get rid of it or is it an essential part of iceweasel/mozilla? It doesn't stop my backup from completing -- it's just a minor annoyance. John Hi, what is error message? .mozilla directory is for some Iceweasel/Firefox, IceApe/SeaMonkey and I guess IceDove/Thunderbird stuff (extenzions, bookmarks etc.). If you use any of this app I think it should be something in .mozilla Try to close all this app and backup again. If it is in your /home/ you should be the owner, is it maybe wrong owner permission? -- Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Registered Linux User #503414 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc53a77.1070...@dobosevic.com
Re: Now cannot ping print server from second machine
On Sat 07 May 2011 at 12:36:07 +0100, AG wrote: The set up is my machine runs the CUPS print server and is directly connected to a USB printer. I used to be able to print from the second (client?) machine, but since this issue following a problem-riddled reboot this is no longer possible. CUPS has to set to accept print jobs from the LAN. But I expect you know that. I have tried to ping the server machine (192.168.1.40) from the client machine (192.168.1.29) but cannot. I have stopped all the firewalls (firestarter) on the *.*.*.40 machine and still no dice. The machines are still connected via a hub and that hasn't changed since before I rebooted. Firestarter configures the firewall. It is not the firewall itself so stopping it would still leave firewall rules in place. I'm not very familiar with iptables but iptables -L lists the current rules, and iptables -F flushes the rules. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507121858.GP13057@desktop
update from squeeze to wheezy
Hi, when I just simply change the deb http://http.us.debian.org/debian stable main contrib non-free to deb http://http.us.debian.org/debian testing main contrib non-free it popped up something like gstreamer0.10-ffmpeg depends on libavcodec52 ( 5:0) or libavcodec-extra-52 ( libavcodec-extra-52 does not appear to be available xserver-xorg-video-nv depends on xorg-video-abi-6.0 xorg-video-abi-6.0 does not appear to be available Thanks for any advice, -- Best Regards, lina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTikXe1SbhYmhUM4b54DfB2YAL=f...@mail.gmail.com
Re: Now cannot ping print server from second machine
On 07/05/11 13:26, Klistvud wrote: Dne, 07. 05. 2011 13:36:07 je AG napisal(a): Hello (again) I don't know if this is related to the connectivity issues reported earlier, but now when trying to print from a second machine, I am unable to. The set up is my machine runs the CUPS print server and is directly connected to a USB printer. I used to be able to print from the second (client?) machine, but since this issue following a problem-riddled reboot this is no longer possible. I have tried to ping the server machine (192.168.1.40) from the client machine (192.168.1.29) but cannot. I have stopped all the firewalls (firestarter) on the *.*.*.40 machine and still no dice. The machines are still connected via a hub and that hasn't changed since before I rebooted. The client machine (*.*.*.29) can access the Internet via the same hub, but packets are being dropped when that machine tries to ping the server. The server machine can now access the Net, and can ping the client machine. Any thoughts on what I should check out for? The IP of your server. On the server, issue 'ifconfig' to see if it still has the former IP (192.168.1.40). You're right! Now my IP has been changed to 192.168.1.64 !!! I'm way confused now - this has always been set at 192.168.1.40 so how has this been changed to *.*.*.64 and how do I ensure that the client machine can keep track of any further changes to this IP? Is this IP change due to having changed the stanza in /etc/network/interfaces from what was iface eth0 inet *static* to iface eth0 inet *dhcp* ? Thanks AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc53c68.5040...@gmail.com
Re: update from squeeze to wheezy
On Sat 07 May 2011 at 20:37:09 +0800, lina wrote: xserver-xorg-video-nv depends on xorg-video-abi-6.0 xorg-video-abi-6.0 does not appear to be available It's probably time for you to move to the nouveau driver as nv has been removed fron Debian. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507124925.GQ13057@desktop
CRITICAL: Wireless connection destroyed on some Netbooks
Could not find the package, but here goes the historial in 2 Netbooks: - Was first noticed on Ubuntu 11.04RC after installation over previous working 10.10 - It was introduced in Ubuntu Netbook Edition 10.10 by April,28 updates. - And confirmed to be in action in the latest Mint Debian XFCE. - Not kernel related (previous kernels were tested, under the unknown updated package) Behavior: - Not a driver problem. Though a previous initialization of the wireless board would allow a correct connection on Linux, as long as hot reboot was made (no power-off). - Handshake fails. When Wicd was tried, sequence was: None, Local, None = Password failure Notes: - There's a chance the board may be misidentified (driver is R8169) but only hanshake fails. - Notice that if windows was called previous to linux, the handshake would go fine. - This is affecting all ACER AspireOne Netbooks using the same wireless board. This is all I got. I'm available for testings if needed. Best regards, Dutra de Lacerda.
Re: Now cannot ping print server from second machine
Dne, 07. 05. 2011 14:34:48 je AG napisal(a): On 07/05/11 13:26, Klistvud wrote: Dne, 07. 05. 2011 13:36:07 je AG napisal(a): Hello (again) I don't know if this is related to the connectivity issues reported earlier, but now when trying to print from a second machine, I am unable to. The set up is my machine runs the CUPS print server and is directly connected to a USB printer. I used to be able to print from the second (client?) machine, but since this issue following a problem-riddled reboot this is no longer possible. I have tried to ping the server machine (192.168.1.40) from the client machine (192.168.1.29) but cannot. I have stopped all the firewalls (firestarter) on the *.*.*.40 machine and still no dice. The machines are still connected via a hub and that hasn't changed since before I rebooted. The client machine (*.*.*.29) can access the Internet via the same hub, but packets are being dropped when that machine tries to ping the server. The server machine can now access the Net, and can ping the client machine. Any thoughts on what I should check out for? The IP of your server. On the server, issue 'ifconfig' to see if it still has the former IP (192.168.1.40). You're right! Now my IP has been changed to 192.168.1.64 !!! I'm way confused now - this has always been set at 192.168.1.40 so how has this been changed to *.*.*.64 and how do I ensure that the client machine can keep track of any further changes to this IP? Is this IP change due to having changed the stanza in /etc/network/interfaces from what was iface eth0 inet *static* to iface eth0 inet *dhcp* ? Absolutely yes. The new IP gets issued from the dhcp server on your LAN now, it's not fixed (static) anymore. It's also not guaranteed to be the same after every reboot, it will be as the dhcp server sees fit. Thanks AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc53c68.5040...@gmail.com -- Cheerio, Klistvud http://bufferoverflow.tiddlyspot.com Certifiable Loonix User #481801 Please reply to the list, not to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304774689.28162.2@compax
Re: update from squeeze to wheezy
00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1) so in wheezy there will be no support for the graphic card of above one? sorry I am not so clearly about those things. On Sat, May 7, 2011 at 8:49 PM, Brian a...@cityscape.co.uk wrote: On Sat 07 May 2011 at 20:37:09 +0800, lina wrote: xserver-xorg-video-nv depends on xorg-video-abi-6.0 xorg-video-abi-6.0 does not appear to be available It's probably time for you to move to the nouveau driver as nv has been removed fron Debian. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507124925.GQ13057@desktop -- Best Regards, lina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimk+gmfsawphw23610b4ygp2h4...@mail.gmail.com
Re: Now cannot ping print server from second machine
Dne, 07. 05. 2011 14:34:48 je AG napisal(a): On 07/05/11 13:26, Klistvud wrote: Dne, 07. 05. 2011 13:36:07 je AG napisal(a): Hello (again) I don't know if this is related to the connectivity issues reported earlier, but now when trying to print from a second machine, I am unable to. The set up is my machine runs the CUPS print server and is directly connected to a USB printer. I used to be able to print from the second (client?) machine, but since this issue following a problem-riddled reboot this is no longer possible. I have tried to ping the server machine (192.168.1.40) from the client machine (192.168.1.29) but cannot. I have stopped all the firewalls (firestarter) on the *.*.*.40 machine and still no dice. The machines are still connected via a hub and that hasn't changed since before I rebooted. The client machine (*.*.*.29) can access the Internet via the same hub, but packets are being dropped when that machine tries to ping the server. The server machine can now access the Net, and can ping the client machine. Any thoughts on what I should check out for? The IP of your server. On the server, issue 'ifconfig' to see if it still has the former IP (192.168.1.40). You're right! Now my IP has been changed to 192.168.1.64 !!! I'm way confused now - this has always been set at 192.168.1.40 so how has this been changed to *.*.*.64 and how do I ensure that the client machine can keep track of any further changes to this IP? That'll be hard to do. DHCP is a dynamic protocol, changing IPs as it sees fit. One way would be to revert to *static* instead of *dhcp* (with all the related issues you had before); the other way would be to use a IP-reservation-capable router as your dhcp server. If you use a router to issue dhcp services, you may want to check out if there is a way to configure IP reservation on the router configuration page. IP reservation is a way to lock a given IP to a given MAC address (MAC is a unique hardware network card identifier), ensuring your client will get the same IP after every reboot. Not all routers have that capability, however. Is this IP change due to having changed the stanza in /etc/network/interfaces from what was iface eth0 inet *static* to iface eth0 inet *dhcp* ? Thanks AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc53c68.5040...@gmail.com -- Cheerio, Klistvud http://bufferoverflow.tiddlyspot.com Certifiable Loonix User #481801 Please reply to the list, not to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304775099.28162.3@compax
cannot resolve hostname
Hello In what seems to be a string of related issues having to do with networking, I now find that not only has my IP address been changed from 192.168.1.40 to 192.168.1.64 but also that my machine's name (valhalla) cannot be resolved. This is the output of ifconfig: $ sudo ifconfig sudo: unable to resolve host valhalla eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07 inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:47117 errors:0 dropped:0 overruns:0 frame:0 TX packets:46335 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:38194090 (36.4 MiB) TX bytes:6237238 (5.9 MiB) Interrupt:18 Base address:0xec00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:7309 errors:0 dropped:0 overruns:0 frame:0 TX packets:7309 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2964856 (2.8 MiB) TX bytes:2964856 (2.8 MiB) Any help would be appreciated in sorting this out, specifically: (1) How do I fix my IP address so that it remains as I originally configured it (i.e. 192.168.1.40) which will make it easier and more predictable for the print client to find the server machine? (2) How do I do so in such a way that I can access the Net once I reboot - which I was unable to do and hence - on good advice - changed the /etc/network/interfaces so that the stanza changed from iface eth0 inet *static* to *dhcp* . This was the only thing that enabled this machine to access the Net after a reboot and I am loathe to change this back to something that didn't work. (3) Helping me to understand how/ why all of these changes have taken place? What happened? I had a perfectly running system - everything worked, and then yesterday I rebooted and I find this dog's breakfast of an arrangement. Thanks in anticipation, list. AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc545bf.4070...@gmail.com
Re: update from squeeze to wheezy
On Sat, May 7, 2011 at 3:21 PM, lina lina.lastn...@gmail.com wrote: 00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1) so in wheezy there will be no support for the graphic card of above one? That is a audio device, not a graphic card For nvidia graphics cards you have xserver-xorg-video-nouveau in wheezy (and nvidia in non-free) gstreamer0.10-ffmpeg is installable in sid, I don't know what happens in wheezy (possible transition?) Regards,
Re: Now cannot ping print server from second machine
On Sat 07 May 2011 at 13:34:48 +0100, AG wrote: Is this IP change due to having changed the stanza in /etc/network/interfaces from what was iface eth0 inet *static* to iface eth0 inet *dhcp* ? Please see your other thread on connectivity. Have x as 40 and use ifdown followed by ifup. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507131810.GR13057@desktop
Re: Now cannot ping print server from second machine
On 07/05/11 14:24, Klistvud wrote: Dne, 07. 05. 2011 14:34:48 je AG napisal(a): On 07/05/11 13:26, Klistvud wrote: Dne, 07. 05. 2011 13:36:07 je AG napisal(a): Hello (again) I don't know if this is related to the connectivity issues reported earlier, but now when trying to print from a second machine, I am unable to. The set up is my machine runs the CUPS print server and is directly connected to a USB printer. I used to be able to print from the second (client?) machine, but since this issue following a problem-riddled reboot this is no longer possible. I have tried to ping the server machine (192.168.1.40) from the client machine (192.168.1.29) but cannot. I have stopped all the firewalls (firestarter) on the *.*.*.40 machine and still no dice. The machines are still connected via a hub and that hasn't changed since before I rebooted. The client machine (*.*.*.29) can access the Internet via the same hub, but packets are being dropped when that machine tries to ping the server. The server machine can now access the Net, and can ping the client machine. Any thoughts on what I should check out for? The IP of your server. On the server, issue 'ifconfig' to see if it still has the former IP (192.168.1.40). You're right! Now my IP has been changed to 192.168.1.64 !!! I'm way confused now - this has always been set at 192.168.1.40 so how has this been changed to *.*.*.64 and how do I ensure that the client machine can keep track of any further changes to this IP? Is this IP change due to having changed the stanza in /etc/network/interfaces from what was iface eth0 inet *static* to iface eth0 inet *dhcp* ? Absolutely yes. The new IP gets issued from the dhcp server on your LAN now, it's not fixed (static) anymore. It's also not guaranteed to be the same after every reboot, it will be as the dhcp server sees fit. Great! So how then can I stop dhcp from randomly assigning a new IP address to my machine so that the client machine can see the server AND enable my (server) machine to access the Net after a reboot? This used to work fine - now it's borked and I don't know why or how, nor more importantly how to put it back to how it was before the package update that kicked in. Cheers AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc54a03.5090...@gmail.com
Re: cannot resolve hostname
On Sat, 07 May 2011 14:14:39 +0100, AG wrote: In what seems to be a string of related issues having to do with networking, I now find that not only has my IP address been changed from 192.168.1.40 to 192.168.1.64 but also that my machine's name (valhalla) cannot be resolved. This is the output of ifconfig: $ sudo ifconfig sudo: unable to resolve host valhalla (...) :-) First, resolve your network layout by either using a dynamic setup (your IP address could change on every reboot) or by using a static configuration. http://wiki.debian.org/NetworkConfiguration Then, review your /etc/hosts file. Do you see the same error if you run /sbin/ifconfig, that is, using not sudo at all? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.13.50...@gmail.com
Re: update from squeeze to wheezy
On Sat, May 7, 2011 at 9:32 PM, Javier Barroso javibarr...@gmail.com wrote: On Sat, May 7, 2011 at 3:21 PM, lina lina.lastn...@gmail.com wrote: 00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1) so in wheezy there will be no support for the graphic card of above one? That is a audio device, not a graphic card what's a mistake. sorry 02:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce 9100M G] (rev b1) For nvidia graphics cards you have xserver-xorg-video-nouveau in wheezy (and nvidia in non-free) gstreamer0.10-ffmpeg is installable in sid, I don't know what happens in wheezy (possible transition?) Regards, -- Best Regards, lina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimfjxckvam3bcgee6saa4fs2-y...@mail.gmail.com
Re: Now cannot ping print server from second machine
On 07/05/11 14:18, Brian wrote: On Sat 07 May 2011 at 13:34:48 +0100, AG wrote: Is this IP change due to having changed the stanza in /etc/network/interfaces from what was iface eth0 inet *static* to iface eth0 inet *dhcp* ? Please see your other thread on connectivity. Have x as 40 and use ifdown followed by ifup. Thanks Brian I had already changed that and I am back to the original problem of loosing connectivity after a reboot. The /etc/network/interfaces file reads (in its entirety): auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static #iface eth0 inet dhcp ## This reflects the earlier suggestion about changing static to dhcp address 192.168.1.40 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 158.43.240.4 dns-search org However, as noted - this returns full circle to the original issues. Thanks AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc54c38.4040...@gmail.com
Re: the package can generate xpm
On 2011-05-07 14:22, lina wrote: Thanks, but I still feel the gimp is not, how to say, flexible, in re-color the grey one. lina Well that's depend what (and how) you wont to do with your pic. I don't think that full automatization is possible with any app. What is problem with GIMP: selecting part of image or make exactly the same gradient but in different color, something else? Maybe full automatization isn't possible but you can do it manually. It is hard for me to tell you anything without seeing .xpm Can you send me .xpm? -- Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Registered Linux User #503414 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc54f29.6080...@dobosevic.com
Re: CRITICAL: Wireless connection destroyed on some Netbooks
On Sat, 07 May 2011 13:54:54 +0100, DuLac Dutra wrote: Could not find the package, but here goes the historial in 2 Netbooks: - Was first noticed on Ubuntu 11.04RC after installation over previous working 10.10 - It was introduced in Ubuntu Netbook Edition 10.10 by April,28 updates. - And confirmed to be in action in the latest Mint Debian XFCE. - Not kernel related (previous kernels were tested, under the unknown updated package) (...) Thanks for the heads-up but better if you provide additional data, for instance: - Is the wifi card detected at all? → lspci - Is it available under your network settings? → /sbin/ifconfig - What do logs say? → review your /var/log/syslog and /var/log/ wpa_supplicant files Behavior: - Not a driver problem. Though a previous initialization of the wireless board would allow a correct connection on Linux, as long as hot reboot was made (no power-off). - Handshake fails. When Wicd was tried, sequence was: None, Local, None = Password failure - Have you tried to setup the card manually or by using another tool (NetworkManager)? Notes: - There's a chance the board may be misidentified (driver is R8169) but only hanshake fails. - Notice that if windows was called previous to linux, the handshake would go fine. - This is affecting all ACER AspireOne Netbooks using the same wireless board. You meant that if you first boot into windows and then start linux the card is working okay? That sounds to me like a power saving issue, I remember something similar happened with some models of realtek wired ethernet adapters some years ago... :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.14.02...@gmail.com
Re: grub-probe: error: cannot stat `/dev/root'
In pan.2011.05.07.10.57...@gmail.com, Camaleón wrote: On Fri, 06 May 2011 10:44:21 -0700, CACook wrote: This just started after my most recent (very painful) dist-upgrade. It seems that BTRFS is not compatible with grub and Debian. I very nearly lost my whole system because of this catastrophe. Does anyone know the nature of the error and how to fix? You're asking for so much :-) First, the btrfs filesystem is still very experimental so only use it if you really (I mean *really*) know what you are doing and also know how to deal when things go wrong. I would even expect data loss (directly or indirectly related to the usage of this filesystem) so make daily backups if needed. As a current btrfs user, I don't recommend you run it on the Squeeze kernel (2.6.32-5) because there are certain circumstances where it doesn't gracefully handle out-of-space issues and that df reports for it lie. I recently filed a bug against the Debian kernel due to this; two BUG() calls within a second leading to a broken btrfs module and needing a reboot and some manual file system recovery. I don't recommend you use the Wheezy kernel (2.6.38-2 in the package name; 2.6.38-3 in the package version) either. There's a least one outstanding bug that I filed involving the in-kernel NULL pointer dereference while mounting a btrfs file system. Again, this leads to a broken btrfs module and needs a reboot to fix. However, it happens easy enough and consistently enough during the Debian boot process that it effectively makes that kernel unusable. I've not tested the Sid kernel; I may do that today. I thought 2.6.39-rc4 from experimental would work, but they haven't put the 2.6.39 kbuild infrastructure in experimental and I have an out-of-tree kernel module that I need for daily operations. This is a close second just because I don't have any experience with it, yet. Right now, my data losses due to btrfs, if any, are still unnoticed. However, I am more worried than ever before that I won't find a file system that meets my unique needs before I start losing data. My unique needs are: on-line growing, on- or off-line shrinking, good performance on 4+ TiB file systems with less than 4 GiB free space. For the few file systems I haven't converted to btrfs, I am still using reiserfs. FWIW, I don't think GRUB2 has BtrFS support, yet. So, you'd have to store your kernel and initrd on a different file system. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: CRITICAL: Wireless connection destroyed on some Netbooks
In banlktim5bvdxyubmi8vcewade4gu_c5...@mail.gmail.com, DuLac Dutra wrote: Could not find the package, but here goes the historial in 2 Netbooks: - Was first noticed on Ubuntu 11.04RC after installation over previous working 10.10 - It was introduced in Ubuntu Netbook Edition 10.10 by April,28 updates. - And confirmed to be in action in the latest Mint Debian XFCE. Both Mint and Ubuntu have their own mailing lists. As far and I can tell, you didn't even test on Debian, rendering your posting off-topic for this mailing list. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: the package can generate xpm
On Sat, 07 May 2011 20:22:21 +0800, lina wrote: On Sat, May 7, 2011 at 8:12 PM, godo go...@dobosevic.com wrote: On 2011-05-07 14:04, lina wrote: are there any debian package can generate xpm file? actually I have several .xpm image, but I am trapped in how to change its color from dull grey to something about gorgeous. Thanks for any advice, GIMP can do it. Thanks, but I still feel the gimp is not, how to say, flexible, in re-color the grey one. If you can't get it with GIMP hardly you'll find a more complete image editor :-) Maybe you only need some tutorials on the matter: How to Digitally Color a Black White Photograph in GIMP http://emptyeasel.com/2008/10/24/how-to-digitally-color-a-black-white-photograph-in-gimp/ Google for gimp black and white colorizer and you'll find more samples. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.14.13...@gmail.com
Re: update from squeeze to wheezy
On Sat 07 May 2011 at 21:21:38 +0800, lina wrote: 00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1) This is your audio card. Regarding your other problem gstreamer0.10-ffmpeg depends on libavcodec52 ( 5:0) or libavcodec-extra-52 ( This is not the dependency I have on my Wheezy install. Does your /etc/apt/sources.list contain an entry for the Debian Multimedia archive? so in wheezy there will be no support for the graphic card of above one? Correct. A way forward is apt-get install xserver-xorg-video-nouveau. If you have an /etc/X11/xorg.conf it might be a good thing to do mv /etc/X11/xorg.conf /etc/X11/xorg.conf-orig before starting X. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507135748.GS13057@desktop
Re: update from squeeze to wheezy
After I removed the xserver-xorg-video-all xserver-xorg-video-nv, it still showed another problem during updating: gstreamer0.10-ffmpeg depends on libavcodec52 ( 5:0) or libavcodec-extra-52 ( libavcodec-extra-52 does not appear to be available Thanks, On Sat, May 7, 2011 at 9:58 PM, lina lina.lastn...@gmail.com wrote: On Sat, May 7, 2011 at 9:32 PM, Javier Barroso javibarr...@gmail.com wrote: On Sat, May 7, 2011 at 3:21 PM, lina lina.lastn...@gmail.com wrote: 00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1) so in wheezy there will be no support for the graphic card of above one? That is a audio device, not a graphic card what's a mistake. sorry 02:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce 9100M G] (rev b1) For nvidia graphics cards you have xserver-xorg-video-nouveau in wheezy (and nvidia in non-free) gstreamer0.10-ffmpeg is installable in sid, I don't know what happens in wheezy (possible transition?) Regards, -- Best Regards, lina -- Best Regards, lina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTinrYqhzrFfg3f7C6pe=6mqdtxb...@mail.gmail.com
Re: update from squeeze to wheezy
On Sat, May 7, 2011 at 9:57 PM, Brian a...@cityscape.co.uk wrote: On Sat 07 May 2011 at 21:21:38 +0800, lina wrote: 00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1) This is your audio card. Regarding your other problem gstreamer0.10-ffmpeg depends on libavcodec52 ( 5:0) or libavcodec-extra-52 ( This is not the dependency I have on my Wheezy install. Does your /etc/apt/sources.list contain an entry for the Debian Multimedia archive? I did not. you are right. Now on its way to the wheezy version. Thanks again, so in wheezy there will be no support for the graphic card of above one? Correct. A way forward is apt-get install xserver-xorg-video-nouveau. If you have an /etc/X11/xorg.conf it might be a good thing to do mv /etc/X11/xorg.conf /etc/X11/xorg.conf-orig before starting X. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507135748.GS13057@desktop -- Best Regards, lina -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTikV9YAdf3n8q6JYP9tjNQ=nsip...@mail.gmail.com
Re: cannot resolve hostname
On 07/05/11 14:50, Camaleón wrote: On Sat, 07 May 2011 14:14:39 +0100, AG wrote: In what seems to be a string of related issues having to do with networking, I now find that not only has my IP address been changed from 192.168.1.40 to 192.168.1.64 but also that my machine's name (valhalla) cannot be resolved. This is the output of ifconfig: $ sudo ifconfig sudo: unable to resolve host valhalla (...) :-) First, resolve your network layout by either using a dynamic setup (your IP address could change on every reboot) or by using a static configuration. http://wiki.debian.org/NetworkConfiguration Then, review your /etc/hosts file. Do you see the same error if you run /sbin/ifconfig, that is, using not sudo at all? Greetings, Hiya OK - I want to use a static IP address (easier for a simpleton like me to configure the printer client machine to see it). The IP address I have customarily used is 192.168.1.40 and that is what is in my /etc/hosts file: 127.0.0.1 localhost 192.168.1.40 valhalla.org # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters (I don't know what all the IPv6 references are, but I assume that I can safely ignore those). When I run /sbin/ifconfig then I don't get the error message about unable to resolve hostname, but I do get that my IP address is now 192.168.1.64 Personally I don't care if the IP address is *.40 or *.64, but I do want it to stay static and I do want to be able to access the Net when I reboot. So, I have just done the following: (1) I altered the /etc/hosts IP address to *.64 (2) ensured that the /etc/network/interface file read static rather than dhcp (3) rebooted When the machine came back on, I was (yet again) unable to access the Net and the only way that I was able to do so was to use Brian's fix #dhclient eth0 which, when checking the /sbin/ifconfig output again shows that the IP address has been made *.64 The hostname is still unresolvable and it seems that I am destined to have to use dhcp when I really don't want to do so ... and yet if I don't I am stuck not being connected. This is rapidly spiralling into a farce and I am still no further ahead than I was, except that I have a partial fix to implement everytime I reboot and hope that the client can find the printer server IP address okay. Perhaps I am being really thick about all of this, but I am very confused about why - in all of the times I have used and installed Debian - this has just started to occur. I am really grateful of any clear ideas or strategies about how to fix this. Thanks AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc553f6.8040...@gmail.com
Re: OT: Are you from Berlin?
On Sat, 07 May 2011 13:52:15 +0200, godo wrote: I don't know how many people read d-community-offtopic so if you are from Berlin please read this http://lists.alioth.debian.org/pipermail/d-community-offtopic/2011-May/000102.html Not from Berlin (I'm at 2,500 Km to the south :-P) but your friend could find useful the information provided by Google: http://maps.google.com/maps?q=Berlin+computer+repairhl=esclient=iceweasel-arls=org.debian:es-ES:unofficialbiw=1280bih=838prmd=ivnscmfdresnum=1bav=on.2,or.r_gc.r_pw.um=1ie=UTF-8sa=Ntab=wl (shorted URI) http://goo.gl/xHPr1 Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.14.38...@gmail.com
Network problem (was: cannot resolve hostname)
On Sat, 07 May 2011 15:15:18 +0100, AG wrote: On 07/05/11 14:50, Camaleón wrote: (...) First, resolve your network layout by either using a dynamic setup (your IP address could change on every reboot) or by using a static configuration. http://wiki.debian.org/NetworkConfiguration Then, review your /etc/hosts file. Do you see the same error if you run /sbin/ifconfig, that is, using not sudo at all? OK - I want to use a static IP address (easier for a simpleton like me to configure the printer client machine to see it). The IP address I have customarily used is 192.168.1.40 and that is what is in my /etc/hosts file: (...) Okay, let's forget momentary the hosts file and go on with the network issue which I think is more important here. So, I have just done the following: (1) I altered the /etc/hosts IP address to *.64 (2) ensured that the /etc/network/interface file read static rather than dhcp (3) rebooted (...) Copy/paste what does your /etc/network/interfaces look like and also post the results of /sbin/ifconfig, cat /etc/resolv.conf, ping -c 3 192.168.0.1 (or whatever the IP of your router is) and just in case ip ro and dmesg | grep -i eth. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.14.49...@gmail.com
Re: cannot resolve hostname
On Saturday 07 May 2011 14:14:39 AG wrote: Hello In what seems to be a string of related issues having to do with networking, I now find that not only has my IP address been changed from 192.168.1.40 to 192.168.1.64 but also that my machine's name (valhalla) cannot be resolved. (1) How do I fix my IP address so that it remains as I originally configured it (i.e. 192.168.1.40) which will make it easier and more predictable for the print client to find the server machine? (2) How do I do so in such a way that I can access the Net once I reboot - which I was unable to do and hence - on good advice - changed the /etc/network/interfaces so that the stanza changed from iface eth0 inet *static* to *dhcp* . This was the only thing that enabled this machine to access the Net after a reboot and I am loathe to change this back to something that didn't work. Have you tried leaving your localhost on dhcp and setting a reserved IP in the router for your localhost's mac address? That might achieve a fixed IP address, while allowing you to keep your dhcp configuration in your /etc/network/interfaces. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105071551.07420.lisi.re...@gmail.com
Re: grub-probe: error: cannot stat `/dev/root'
In 201105070904.26205@iguanasuicide.net, Boyd Stephen Smith Jr. wrote: In pan.2011.05.07.10.57...@gmail.com, Camaleón wrote: On Fri, 06 May 2011 10:44:21 -0700, CACook wrote: This just started after my most recent (very painful) dist-upgrade. It seems that BTRFS is not compatible with grub and Debian. I very nearly lost my whole system because of this catastrophe. Does anyone know the nature of the error and how to fix? You're asking for so much :-) First, the btrfs filesystem is still very experimental so only use it if you really (I mean *really*) know what you are doing and also know how to deal when things go wrong. I would even expect data loss (directly or indirectly related to the usage of this filesystem) so make daily backups if needed. As a current btrfs user, I don't recommend you run it on the Squeeze kernel (2.6.32-5) because Bug 625899 I don't recommend you use the Wheezy kernel (2.6.38-2 in the package name; 2.6.38-3 in the package version) either. There's a least one outstanding bug Bug 622218 I've not tested the Sid kernel; I may do that today. Just tested. Also affected by bug 622218. I thought 2.6.39-rc5 from experimental would work, but they haven't put the 2.6.39 kbuild infrastructure in experimental and I have an out-of-tree kernel module that I need for daily operations. This is a close second just because I don't have any experience with it, yet. You could try this one, if you aren't using any out-of-tree modules. For me it is the NVidia module. I really should find the money for a cheap ATI card so I can use FLOSS modules. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Network problem
On 07/05/11 15:49, Camaleón wrote: snip (...) Okay, let's forget momentary the hosts file and go on with the network issue which I think is more important here. So, I have just done the following: (1) I altered the /etc/hosts IP address to *.64 (2) ensured that the /etc/network/interface file read static rather than dhcp (3) rebooted (...) Hi Camaleón See below. Thanks. Copy/paste what does your /etc/network/interfaces look like # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static #iface eth0 inet dhcp address 192.168.1.40# I have manually specified this netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 158.43.240.4 dns-search org and also post the results of /sbin/ifconfig, $ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07 inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1936 errors:0 dropped:0 overruns:0 frame:0 TX packets:1864 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1018372 (994.5 KiB) TX bytes:237018 (231.4 KiB) Interrupt:18 Base address:0xec00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:644 errors:0 dropped:0 overruns:0 frame:0 TX packets:644 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:54042 (52.7 KiB) TX bytes:54042 (52.7 KiB) cat /etc/resolv.conf, $ cat /etc/resolv.conf domain lan search lan nameserver 192.168.1.254 ping -c 3 192.168.0.1 (or whatever the IP of your router is) $ ping -c 3 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. 64 bytes from 192.168.1.254: icmp_req=1 ttl=64 time=1.74 ms 64 bytes from 192.168.1.254: icmp_req=2 ttl=64 time=0.683 ms 64 bytes from 192.168.1.254: icmp_req=3 ttl=64 time=0.705 ms and just in case ip ro $ ip ro 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.64 default via 192.168.1.254 dev eth0 and dmesg | grep -i eth. $ dmesg | grep eth [0.178866] ACPI Error: Method parse/execution failed [\_SB_.MEM_._CRS] (Node f4c370c0), AE_AML_BUFFER_LIMIT (20110112/psparse-536) [0.178875] ACPI Error: Method execution failed [\_SB_.MEM_._CRS] (Node f4c370c0), AE_AML_BUFFER_LIMIT (20110112/uteval-103) [1.014972] 8139too :01:0a.0: eth0: RealTek RTL8139 at 0xec00, 00:90:47:05:a3:07, IRQ 18 [ 10.733628] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 [ 20.752026] eth0: no IPv6 routers present Greetings, Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc55ff6.4090...@gmail.com
Re: cannot resolve hostname
AG wrote: (I don't know what all the IPv6 references are, but I assume that I can safely ignore those). That is not a safe assumption. If you do not have an IPv6 capable router and DNS server, many applications will timeout before the IPv6 DNS request does. You need to disable IPv6 completely. It may actually be causing your current problem. Bob McConnell N2SPP -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc56429.30...@lightlink.com
Re: Now cannot ping print server from second machine
Dne, 07. 05. 2011 15:42:16 je AG napisal(a): On 07/05/11 14:18, Brian wrote: On Sat 07 May 2011 at 13:34:48 +0100, AG wrote: Is this IP change due to having changed the stanza in /etc/network/interfaces from what was iface eth0 inet *static* to iface eth0 inet *dhcp* ? Please see your other thread on connectivity. Have x as 40 and use ifdown followed by ifup. Thanks Brian I had already changed that and I am back to the original problem of loosing connectivity after a reboot. The /etc/network/interfaces file reads (in its entirety): auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static #iface eth0 inet dhcp ## This reflects the earlier suggestion about changing static to dhcp address 192.168.1.40 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 158.43.240.4 dns-search org However, as noted - this returns full circle to the original issues. Things to check: IS your gateway/router REALLY at 192.168.1.254 ? An error here will lead you to a basically unconnected machine, probably you won't be able even to ping the hosts on your LAN or anything. IS there really a dns server at 158.43.240.4 ? An error here will only affect dns names, so you will not be able to reach, say, www.google.com; you will still be able to reach any hosts by specifying their IP numbers directly. -- Cheerio, Klistvud http://bufferoverflow.tiddlyspot.com Certifiable Loonix User #481801 Please reply to the list, not to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304782346.28162.4@compax
Re: cannot resolve hostname
On Sat, May 7, 2011 at 9:14 AM, AG computing.acco...@googlemail.com wrote: In what seems to be a string of related issues having to do with networking, I now find that not only has my IP address been changed from 192.168.1.40 to 192.168.1.64 but also that my machine's name (valhalla) cannot be resolved. This is the output of ifconfig: $ sudo ifconfig sudo: unable to resolve host valhalla eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07 inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:47117 errors:0 dropped:0 overruns:0 frame:0 TX packets:46335 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:38194090 (36.4 MiB) TX bytes:6237238 (5.9 MiB) Interrupt:18 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:7309 errors:0 dropped:0 overruns:0 frame:0 TX packets:7309 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2964856 (2.8 MiB) TX bytes:2964856 (2.8 MiB) Any help would be appreciated in sorting this out, specifically: (1) How do I fix my IP address so that it remains as I originally configured it (i.e. 192.168.1.40) which will make it easier and more predictable for the print client to find the server machine? (2) How do I do so in such a way that I can access the Net once I reboot - which I was unable to do and hence - on good advice - changed the /etc/network/interfaces so that the stanza changed from iface eth0 inet *static* to *dhcp* . This was the only thing that enabled this machine to access the Net after a reboot and I am loathe to change this back to something that didn't work. (3) Helping me to understand how/ why all of these changes have taken place? What happened? I had a perfectly running system - everything worked, and then yesterday I rebooted and I find this dog's breakfast of an arrangement. sudo: What's the output of cat /etc/hostname and cat /etc/hosts? static/dhcp: Do you have a dhcp server on which you can set reservations and other options? If, yes, you can either specify that the dhcp server hands out a specific address to valhalla or set valhalla up with a static ip address and specify that the dhcp server not hand out that address. (If you use a static ip address you also have to set a default route for it to be able to access the internet.) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktiml5sb0qapd47_rsh2awnbkjri...@mail.gmail.com
Re: Network problem
Dne, 07. 05. 2011 17:06:30 je AG napisal(a): # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 158.43.240.4 Can the above line from your /etc/network/interfaces be conflicting with the: nameserver 192.168.1.254 in your /etc/resolv.conf ? Unfortunately, I'm not network-savvy enough to say anything about that. Perhaps others can comment? -- Cheerio, Klistvud http://bufferoverflow.tiddlyspot.com Certifiable Loonix User #481801 Please reply to the list, not to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304782842.28162.5@compax
Re: cannot resolve hostname
On Sat, May 7, 2011 at 11:24 AM, Bob McConnell rmcco...@lightlink.com wrote: (I don't know what all the IPv6 references are, but I assume that I can safely ignore those). That is not a safe assumption. If you do not have an IPv6 capable router and DNS server, many applications will timeout before the IPv6 DNS request does. You need to disable IPv6 completely. It may actually be causing your current problem. Disabling ipv6 won't prevent ipv6 being made. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTi=6lp0jmz172+8ddsqh3ytvvcx...@mail.gmail.com
Re: Network problem
On Sat, 07 May 2011 16:06:30 +0100, AG wrote: On 07/05/11 15:49, Camaleón wrote: (...) Copy/paste what does your /etc/network/interfaces look like # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static #iface eth0 inet dhcp address 192.168.1.40# I have manually specified this netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 158.43.240.4 dns-search org The above looks okay. and also post the results of /sbin/ifconfig, $ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07 inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1936 errors:0 dropped:0 overruns:0 frame:0 TX packets:1864 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1018372 (994.5 KiB) TX bytes:237018 (231.4 KiB) Interrupt:18 Base address:0xec00 (...) Here there's a problem. Your IP address does not match with the one you defined in the interfaces file. Let's see... on a running system, once you edit the /etc/network/ interfaces file you also have to: 1/ Restart the network service: /etc/init.d/networking restart 2/ Up the network interface: ifup eth0 3/ Check that all is fine: /sbin/ifconfig (this is not needed after you restart the machine) Try it and send the results. The rest of the files look normal so let's focus on this. Also, after running the above 3 commands, review the syslog (grep -i eth0 /var/log/syslog) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.15.39...@gmail.com
Re: Now cannot ping print server from second machine
On 07/05/11 16:32, Klistvud wrote: Dne, 07. 05. 2011 15:42:16 je AG napisal(a): On 07/05/11 14:18, Brian wrote: On Sat 07 May 2011 at 13:34:48 +0100, AG wrote: Is this IP change due to having changed the stanza in /etc/network/interfaces from what was iface eth0 inet *static* to iface eth0 inet *dhcp* ? Please see your other thread on connectivity. Have x as 40 and use ifdown followed by ifup. Thanks Brian I had already changed that and I am back to the original problem of loosing connectivity after a reboot. The /etc/network/interfaces file reads (in its entirety): auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static #iface eth0 inet dhcp ## This reflects the earlier suggestion about changing static to dhcp address 192.168.1.40 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 158.43.240.4 dns-search org However, as noted - this returns full circle to the original issues. Things to check: IS your gateway/router REALLY at 192.168.1.254 ? An error here will lead you to a basically unconnected machine, probably you won't be able even to ping the hosts on your LAN or anything. IS there really a dns server at 158.43.240.4 ? An error here will only affect dns names, so you will not be able to reach, say, www.google.com; you will still be able to reach any hosts by specifying their IP numbers directly. Hi Klistvud Yes, that is the gateway/ router IP address - I just checked with the provider. Yes, the DNS address given is accurate - domain names resolve fine (once I can get connected). This seems to be emanating from something to do with the dhcp vs. static settings which is an issue I have never run into before and has only occurred since one of the last updates. The reason I know this is because yesterday I reinstalled my system using a testing netinstall CD from February 2011 that I had. All was fine - could connect, could print, etc. However, when I ran dist-upgrade and rebooted, this is when all of the problems started again ... just as they had after I rebooted prior to the reinstall after a 9 day uptime. This is what leads me to think that some or other configuration has been changed by a package upgrade over the last week or so. But I don't know which one. Thanks AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc56725.9090...@gmail.com
Re: cannot resolve hostname
On 07/05/11 16:31, Tom H wrote: On Sat, May 7, 2011 at 9:14 AM, AGcomputing.acco...@googlemail.com wrote: In what seems to be a string of related issues having to do with networking, I now find that not only has my IP address been changed from 192.168.1.40 to 192.168.1.64 but also that my machine's name (valhalla) cannot be resolved. This is the output of ifconfig: $ sudo ifconfig sudo: unable to resolve host valhalla eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07 inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:47117 errors:0 dropped:0 overruns:0 frame:0 TX packets:46335 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:38194090 (36.4 MiB) TX bytes:6237238 (5.9 MiB) Interrupt:18 Base address:0xec00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:7309 errors:0 dropped:0 overruns:0 frame:0 TX packets:7309 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2964856 (2.8 MiB) TX bytes:2964856 (2.8 MiB) Any help would be appreciated in sorting this out, specifically: (1) How do I fix my IP address so that it remains as I originally configured it (i.e. 192.168.1.40) which will make it easier and more predictable for the print client to find the server machine? (2) How do I do so in such a way that I can access the Net once I reboot - which I was unable to do and hence - on good advice - changed the /etc/network/interfaces so that the stanza changed from iface eth0 inet *static* to *dhcp* . This was the only thing that enabled this machine to access the Net after a reboot and I am loathe to change this back to something that didn't work. (3) Helping me to understand how/ why all of these changes have taken place? What happened? I had a perfectly running system - everything worked, and then yesterday I rebooted and I find this dog's breakfast of an arrangement. sudo: What's the output of cat /etc/hostname and cat /etc/hosts? Tom $ cat /etc/hostname valhalla $ cat /etc/hosts 127.0.0.1 localhost #192.168.1.64 valhalla.org 192.168.1.40 valhalla.org # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters static/dhcp: Do you have a dhcp server on which you can set reservations and other options? If, yes, you can either specify that the dhcp server hands out a specific address to valhalla or set valhalla up with a static ip address and specify that the dhcp server not hand out that address. (If you use a static ip address you also have to set a default route for it to be able to access the internet.) This is what Lisi suggested, but considering the mess I am currently wading through with the help of this list, I fear that I will be waltzing directly into the lion's den with that approach. Moreover, it doesn't address the whole issue of why/ how this has just occurred over the last week when I've never had this problem before in the 5 years I've been running Debian (or several with Slackware, before that). AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc5680a.3090...@gmail.com
Re: Network problem
On 07/05/11 16:39, Camaleón wrote: On Sat, 07 May 2011 16:06:30 +0100, AG wrote: On 07/05/11 15:49, Camaleón wrote: (...) Copy/paste what does your /etc/network/interfaces look like # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static #iface eth0 inet dhcp address 192.168.1.40# I have manually specified this netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 158.43.240.4 dns-search org The above looks okay. and also post the results of /sbin/ifconfig, $ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07 inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1936 errors:0 dropped:0 overruns:0 frame:0 TX packets:1864 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1018372 (994.5 KiB) TX bytes:237018 (231.4 KiB) Interrupt:18 Base address:0xec00 (...) Here there's a problem. Your IP address does not match with the one you defined in the interfaces file. Let's see... on a running system, once you edit the /etc/network/ interfaces file you also have to: 1/ Restart the network service: /etc/init.d/networking restart 2/ Up the network interface: ifup eth0 3/ Check that all is fine: /sbin/ifconfig (this is not needed after you restart the machine) Try it and send the results. The rest of the files look normal so let's focus on this. Here are the results of those three commands: $ sudo /etc/init.d/networking restart sudo: unable to resolve host valhalla Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces ... (warning). Reconfiguring network interfaces...Stopping the Firestarter firewall Starting the Firestarter firewall done. $ sudo ifup eth0 sudo: unable to resolve host valhalla Stopping the Firestarter firewall Starting the Firestarter firewall $ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07 inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10700 errors:0 dropped:0 overruns:0 frame:0 TX packets:10113 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8424815 (8.0 MiB) TX bytes:1223781 (1.1 MiB) Interrupt:18 Base address:0xec00 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:983 errors:0 dropped:0 overruns:0 frame:0 TX packets:983 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:79512 (77.6 KiB) TX bytes:79512 (77.6 KiB) The IP address is now consistent. Now is this likely to hold when I reboot so that I can access the Net? Also, after running the above 3 commands, review the syslog (grep -i eth0 /var/log/syslog) I did, and here is the output (I trimmed it to the last lines consistent with the current time): May 7 16:43:13 valhalla NetworkManager[1550]: info (eth0): carrier now OFF (device state 1) May 7 16:43:13 valhalla dhclient: receive_packet failed on eth0: Network is down May 7 16:43:29 valhalla NetworkManager[1550]: info (eth0): carrier now ON (device state 1) May 7 16:43:29 valhalla kernel: [ 5878.118829] eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 May 7 16:43:40 valhalla kernel: [ 5888.800028] eth0: no IPv6 routers present Thanks (as always!) AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc569f3.4010...@gmail.com
Re: Now cannot ping print server from second machine
Dne, 07. 05. 2011 17:37:09 je AG napisal(a): Hi Klistvud Yes, that is the gateway/ router IP address - I just checked with the provider. Unfortunately, it's not as simple as that. Providers have been wrong in the past. The ultimate check would be: can you reach your router's configuration page by specifying 192.168.1.254 in your browser? Yes, the DNS address given is accurate - domain names resolve fine (once I can get connected). Well, AFAIK the domain names may be resolving fine because dhcp finds a working DNS server for you. The specified DNS servers (as per your static configuration) may still be wrong. You have to understand that dhcp and static are quite separate: once you enable *dhcp*, all other entries in your /etc/network/interfaces get disregarded, and any errors therein will not be picked up (and may thus pass completely unnoticed). The reverse is also true: as soon as you enable *static* no auto-configuration is taking place anymore -- you'll have to get your address, network, gateway, broadcast and other stanzas exactly right to make it work. In this configuration, potential errors in your /etc/network/interfaces will *not* pass unnoticed at all. I apologize if you already know that, didn't want to sound paternalizing ;) -- Cheerio, Klistvud http://bufferoverflow.tiddlyspot.com Certifiable Loonix User #481801 Please reply to the list, not to me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1304785196.28162.6@compax
Does apt-get dist-upgrade upgrade the kernel?
Hello, I'm running wheezy and it's since weeks that I started wondering when a new kernel will come to testing :-) root@debian:~# cat /etc/issue Debian GNU/Linux wheezy/sid \n \l test@debian:~$ uname -r 2.6.32-5-686 Now (by purely chance) I realized that there is indeed a new kernel available in the repositories so that this means it was me making some kind of mistake. root@debian:~# apt-cache search linux-image linux-headers-2.6.38-2-486 - Header files for Linux 2.6.38-2-486 linux-headers-2.6.38-2-686 - Header files for Linux 2.6.38-2-686 linux-headers-2.6.38-2-686-bigmem - Header files for Linux 2.6.38-2-686-bigmem linux-headers-2.6.38-2-amd64 - Header files for Linux 2.6.38-2-amd64 linux-image-2.6.38-2-486 - Linux 2.6.38 for old PCs linux-image-2.6.38-2-686 - Linux 2.6.38 for modern PCs linux-image-2.6.38-2-686-bigmem - Linux 2.6.38 for PCs with 4GB+ RAM linux-image-2.6.38-2-686-bigmem-dbg - Debugging infos for Linux 2.6.38-2-686-bigmem linux-image-2.6.38-2-amd64 - Linux 2.6.38 for 64-bit PCs linux-image-2.6-486 - Linux 2.6 for old PCs (meta-package) linux-image-2.6-686 - Linux 2.6 for modern PCs (meta-package) linux-image-2.6-686-bigmem - Linux 2.6 for PCs with 4GB+ RAM (meta-package) linux-image-2.6-amd64 - Linux 2.6 for 64-bit PCs (meta-package) linux-image-486 - Linux for old PCs (meta-package) linux-image-686 - Linux for modern PCs (meta-package) linux-image-686-bigmem - Linux for PCs with 4GB+ RAM (meta-package) linux-image-amd64 - Linux for 64-bit PCs (meta-package) alsa-base - Archivos de configuración del controlador de ALSA linux-image-2.6.32-5-686 - Linux 2.6.32 for modern PCs linux-headers-2.6.32-5-686 - Header files for Linux 2.6.32-5-686 I use to upgrade the machine with this command: apt-get update apt-get -V dist-upgrade Should I have been using another one that automatically triggered the new kernel? Or is that kernel needs to be manually pulled? :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.16.18...@gmail.com
Re: Does apt-get dist-upgrade upgrade the kernel?
On 07/05/11 17:18, Camaleón wrote: Hello, I'm running wheezy and it's since weeks that I started wondering when a new kernel will come to testing :-) snip I use to upgrade the machine with this command: apt-get update apt-get -V dist-upgrade Should I have been using another one that automatically triggered the new kernel? Or is that kernel needs to be manually pulled? :-? Camaleón FWIW, I only ever use either the Update Manager or aptitude safe-upgrade and it pulls in the kernel and headers as well as far as I can ascertain. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc57241.5070...@gmail.com
Re: Network problem
On Sat, 07 May 2011 16:49:07 +0100, AG wrote: On 07/05/11 16:39, Camaleón wrote: (...) Let's see... on a running system, once you edit the /etc/network/ interfaces file you also have to: 1/ Restart the network service: /etc/init.d/networking restart 2/ Up the network interface: ifup eth0 3/ Check that all is fine: /sbin/ifconfig (this is not needed after you restart the machine) Try it and send the results. The rest of the files look normal so let's focus on this. Here are the results of those three commands: $ sudo /etc/init.d/networking restart sudo: unable to resolve host (...) Once you resolve the networking problem, you should look from where is coming that sudo error... Is it happening for any sudo command you type? :-? $ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:90:47:05:a3:07 inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::290:47ff:fe05:a307/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10700 errors:0 dropped:0 overruns:0 frame:0 TX packets:10113 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8424815 (8.0 MiB) TX bytes:1223781 (1.1 MiB) Interrupt:18 Base address:0xec00 (...) Hey, that seems to be the right one :-) The IP address is now consistent. Now is this likely to hold when I reboot so that I can access the Net? (...) Sure, and if not something is very badly broken. Restart the machine to be sure and if the IP address changes again, review your syslog. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.05.07.16.26...@gmail.com
Re: Now cannot ping print server from second machine
On 07/05/11 17:19, Klistvud wrote: Dne, 07. 05. 2011 17:37:09 je AG napisal(a): Hi Klistvud Yes, that is the gateway/ router IP address - I just checked with the provider. Unfortunately, it's not as simple as that. Providers have been wrong in the past. The ultimate check would be: can you reach your router's configuration page by specifying 192.168.1.254 in your browser? Yes. Yes, the DNS address given is accurate - domain names resolve fine (once I can get connected). Well, AFAIK the domain names may be resolving fine because dhcp finds a working DNS server for you. The specified DNS servers (as per your static configuration) may still be wrong. You have to understand that dhcp and static are quite separate: once you enable *dhcp*, all other entries in your /etc/network/interfaces get disregarded, and any errors therein will not be picked up (and may thus pass completely unnoticed). The reverse is also true: as soon as you enable *static* no auto-configuration is taking place anymore -- you'll have to get your address, network, gateway, broadcast and other stanzas exactly right to make it work. In this configuration, potential errors in your /etc/network/interfaces will *not* pass unnoticed at all. I apologize if you already know that, didn't want to sound paternalizing ;) No apologies necessary, thanks. Networking always confused me, and neither it nor computing are my areas of specialisation, so I'm trying to get my head around material that is quite alien to me, so all info gratefully received. Thanks AG -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc57180.6040...@gmail.com
Re: Does apt-get dist-upgrade upgrade the kernel?
On 2011-05-07 18:18, Camaleón wrote: Hello, I'm running wheezy and it's since weeks that I started wondering when a new kernel will come to testing :-) root@debian:~# cat /etc/issue Debian GNU/Linux wheezy/sid \n \l test@debian:~$ uname -r 2.6.32-5-686 Now (by purely chance) I realized that there is indeed a new kernel available in the repositories so that this means it was me making some kind of mistake. root@debian:~# apt-cache search linux-image linux-headers-2.6.38-2-486 - Header files for Linux 2.6.38-2-486 linux-headers-2.6.38-2-686 - Header files for Linux 2.6.38-2-686 linux-headers-2.6.38-2-686-bigmem - Header files for Linux 2.6.38-2-686-bigmem linux-headers-2.6.38-2-amd64 - Header files for Linux 2.6.38-2-amd64 linux-image-2.6.38-2-486 - Linux 2.6.38 for old PCs linux-image-2.6.38-2-686 - Linux 2.6.38 for modern PCs linux-image-2.6.38-2-686-bigmem - Linux 2.6.38 for PCs with 4GB+ RAM linux-image-2.6.38-2-686-bigmem-dbg - Debugging infos for Linux 2.6.38-2-686-bigmem linux-image-2.6.38-2-amd64 - Linux 2.6.38 for 64-bit PCs linux-image-2.6-486 - Linux 2.6 for old PCs (meta-package) linux-image-2.6-686 - Linux 2.6 for modern PCs (meta-package) linux-image-2.6-686-bigmem - Linux 2.6 for PCs with 4GB+ RAM (meta-package) linux-image-2.6-amd64 - Linux 2.6 for 64-bit PCs (meta-package) linux-image-486 - Linux for old PCs (meta-package) linux-image-686 - Linux for modern PCs (meta-package) linux-image-686-bigmem - Linux for PCs with 4GB+ RAM (meta-package) linux-image-amd64 - Linux for 64-bit PCs (meta-package) alsa-base - Archivos de configuración del controlador de ALSA linux-image-2.6.32-5-686 - Linux 2.6.32 for modern PCs linux-headers-2.6.32-5-686 - Header files for Linux 2.6.32-5-686 I use to upgrade the machine with this command: apt-get update apt-get -V dist-upgrade Should I have been using another one that automatically triggered the new kernel? Or is that kernel needs to be manually pulled? :-? Greetings, Hi, whenever I power on my boxes firs I go in single user mod and apt-get update apt-get dist-upgrade like you. On my Wheezy box: $ uname -r 2.6.38-2-686 I really doubt that I got it just because I was in single-user. Maybe your box was just tired and made a small mistake? :-) -- Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Registered Linux User #503414 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc578ac.9000...@dobosevic.com
Re: cannot resolve hostname
On Sat 07 May 2011 at 15:15:18 +0100, AG wrote: OK - I want to use a static IP address (easier for a simpleton like me to configure the printer client machine to see it). The IP address I have customarily used is 192.168.1.40 and that is what is in my /etc/hosts file: 127.0.0.1 localhost 192.168.1.40 valhalla.org valhalla.org does not have an IP address of 192.168.1.40. This may or may not be a cause of your problem. Commenting it out would do no harm. You can fix it later. Similarily for the dns-servers and dns-search lines in the interfaces file. Commenting them out loses you nothing. Just ensure/etc/resolv.conf has an entry for a nameserver. When the machine came back on, I was (yet again) unable to access the Net and the only way that I was able to do so was to use Brian's fix #dhclient eth0 which, when checking the /sbin/ifconfig output again shows that the IP address has been made *.64 What I gave you wasn't a fix but a simple way to get you going :). Changing to a static stanza should still have kept you online but it seems there are other things in your setup preventing that. Pinging your router and nameserver by IP and www.debian,org would establish the extent of your connectivity. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110507164128.GW13057@desktop
