Re: date de sortie prévisionnelle de Debian 12 Bookworm: le 10 juin 2023
Le Mon, 01 May 2023 12:34:35 +, benoit a écrit : > J'ai essayé 2x de passer en Bookworm, mais après la mise à jour, X ne > veut plus se lancer, car il n'a pas le droit d'écrire dans > /tmp:LOCKMACHIN BIDULE (G pas noté le message d'erreur) > > Seul root peut lancer x > > Du coup j'ai restauré mon système et j'ai abandonné le projet de > passer en Bookworm Jamais eu ce genre de problème. A noter: - Je suis prudent et lis donc les messages dans la console! - J'utilise Aptitude (vieille habitude qui m'a toujours satisfait) - J'ajoute le sources.list de la testing sans enlever celui de stable - je désinstalle potentiellement les drivers problématiques (Nvidia...) - je lance l'upgrade depuis la console et non depuis un bureau graphique - une fois passé en testing j'enlève stable et ajoute unstable avec un pinning (en tout cas au début du cycle pour éviter les blocages et logiciels manquants de testing) J'ajouterais au vu des messages que je vois parfois passer: Sur les ordinateurs modernes, il ne faut pas accuser Debian ou Grub de ce qui concerne UEFI, et donc configurer UEFI en fonction de son usage, surtout quand on change d'OS ou «double-boot» avec Windows…
Re: Debian Linux 11 erro
Le 03/05/2023 à 16:57, Pat23 a écrit : Estou com erro na instalação do Debian. Dá a informação - Arquivo ou diretório não encontrado e “não foi possível obter trava /var/lib/dpkg/lock-frontend” Em que passo de que instalação exatamente? -- /¯\ +55 (61) 3216 3613 mailto:l...@dutras.org \ / +55 (61) 3546 7191xmpp:leand...@jabber.org X +55 (61) 99302 2691 matrix:user/l...@matrix.org / \ Brazil GMT−3 https://useplaintext.email/#why-plaintext
Re: processing /etc/sysctl.d
Hello, On Wed, May 03, 2023 at 07:50:30PM -0400, Lee wrote: > I'm at a loss for how to figure out why my settings aren't taking effect. > > $ head /etc/sysctl.d/local.conf […] > # accept router advertisements > net/ipv6/conf/enp1s0/accept_ra = 1 Is it possible that enp1s0 didn't yet exist at the time that systemd-sysctl.service ran? To check, you could instead set the key net/ipv6/conf/default/accept_ra = 1 then any new interfaces should get accept_ra=1 as they are created. Though when I look at my net/ipv6/conf/default/accept_ra it is already set to 1, so another possibility is that you have something that is setting net/ipv6/conf/enp1s0/accept_ra back to 0 after systemd-sysctl.service already set it to 1. NetworkManager is known to do this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025073 So, what are you using to manage enp1s0? Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: processing /etc/sysctl.d
On Wed, May 03, 2023 at 07:50:30PM -0400, Lee wrote: > $ head /etc/sysctl.d/local.conf > # my site local preferences > # > # man sysctl.d > # Configure kernel parameters at boot > # /etc/sysctl.d/*.conf > # key/name/under/proc/sys = some value > > # accept router advertisements > net/ipv6/conf/enp1s0/accept_ra = 1 > > > $ cat /proc/sys/net/ipv6/conf/enp1s0/accept_ra > 0 > > > Telling the system to read /etc/sysctl.d/local.conf works: > $ sudo sysctl --load=/etc/sysctl.d/local.conf > <.. snip lots ..> > > $ cat /proc/sys/net/ipv6/conf/enp1s0/accept_ra > 1 > > How do I get the system to read it at boot time? A guess: perhaps this parameter cannot be set during the initial boot, because the enp1s0 interface isn't in a working state yet. If you put another parameter in the same local.conf file, one that's *not* tied to a piece of hardware, does it work?
processing /etc/sysctl.d
How to get /etc/sysctl.d/local.conf directives processed? I don't see any errors or warnings in the logs that look applicable, and grep sysctl doesn't give me anything interesting: $ grep sysctl /var/log/* 2>/dev/null /var/log/auth.log:May 3 19:41:17 spot sudo: lee : TTY=pts/0 ; PWD=/home/lee ; USER=root ; COMMAND=/usr/sbin/sysctl --load=/etc/sysctl.d/local.conf /var/log/kern.log:May 2 17:55:03 spot kernel: [0.070323] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/kern.log:May 2 18:28:15 spot kernel: [0.070201] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/kern.log:May 2 18:34:23 spot kernel: [0.070002] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/kern.log:May 3 18:21:59 spot kernel: [0.069819] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/kern.log:May 3 19:18:01 spot kernel: [0.070156] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/kern.log:May 3 19:29:12 spot kernel: [0.070329] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/messages:May 2 17:55:03 spot kernel: [0.070323] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/messages:May 2 18:28:15 spot kernel: [0.070201] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/messages:May 2 18:34:23 spot kernel: [0.070002] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/messages:May 3 18:21:59 spot kernel: [0.069819] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/messages:May 3 19:18:01 spot kernel: [0.070156] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/messages:May 3 19:29:12 spot kernel: [0.070329] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/syslog:May 2 17:55:03 spot kernel: [0.070323] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/syslog:May 2 18:28:15 spot kernel: [0.070201] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/syslog:May 2 18:34:23 spot kernel: [0.070002] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/syslog:May 3 18:21:59 spot kernel: [0.069819] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/syslog:May 3 19:18:01 spot kernel: [0.070156] Yama: disabled by default; enable with sysctl kernel.yama.* /var/log/syslog:May 3 19:29:12 spot kernel: [0.070329] Yama: disabled by default; enable with sysctl kernel.yama.* I'm at a loss for how to figure out why my settings aren't taking effect. $ head /etc/sysctl.d/local.conf # my site local preferences # # man sysctl.d # Configure kernel parameters at boot # /etc/sysctl.d/*.conf # key/name/under/proc/sys = some value # accept router advertisements net/ipv6/conf/enp1s0/accept_ra = 1 $ cat /proc/sys/net/ipv6/conf/enp1s0/accept_ra 0 Telling the system to read /etc/sysctl.d/local.conf works: $ sudo sysctl --load=/etc/sysctl.d/local.conf <.. snip lots ..> $ cat /proc/sys/net/ipv6/conf/enp1s0/accept_ra 1 How do I get the system to read it at boot time? TIA Lee
Re: Debian Linux 11 erro
Apaga só esse ficheiro (caminho completo) Paulo Oliveira Eng Tec. Informático Enviado do meu Android Tlm: 912887324 03/05/2023 20:15:16 Pat23 : > Estou com erro na instalação do Debian. Dá a informação - Arquivo ou > diretório não encontrado e “não foi possível obter trava > /var/lib/dpkg/lock-frontend” > > * > * signature.asc Description: PGP signature
Re: Problème pour servir à un exécutable sa dépendance à libc.so.6 (debian 11)
je reformule : il y a des problèmes sur aarch64 INEXISTANTS sur x86_64 > Le 3 mai 2023 à 20:09, RogerT a écrit : > > Ça a compilé. > Ça tourne sur architecture aarch64. > > Mais il y a des problèmes avec certaines dépendances à des fonctions du shell > ou à systemd (inexistantes sur x86_64) que je dois régler. > > >> Le 3 mai 2023 à 09:40, didier gaumet a écrit : >> >> Le mercredi 03 mai 2023 à 03:18 +0200, roger.tar...@free.fr a écrit : >> [...] >>> Est-ce aussi simple que ça ou y a-t-il des pièges sournois dans la >>> cross-compilation ? >> >> Je n'y connais rien vu que je ne construis pas/plus d'exécutables et encore >> moins par cross-compilation mais le wiki Debian a un article sur les >> différentes possibilités et bonnes pratiques de cross-compilation en >> environnement Debian: >> https://wiki.debian.org/CrossCompiling >> >>
Debian Linux 11 erro
Estou com erro na instalação do Debian. Dá a informação - Arquivo ou diretório não encontrado e “não foi possível obter trava /var/lib/dpkg/lock-frontend”
Re: Resolved (was: Re: OT: Using my (new) cable based ISP with their modem in bridge mode and my existing router)
rhkra...@gmail.com wrote: ... > ... Sometimes I feel > like an idiot. > > All seems well. :) i've had days like that... glad you figured it out. completely OT from your issue, but today i finally upgraded my stable partition from whatever it was on (last major update was probably a year or more ago). glad to say that with a bit of heavy hammer hitting i got it all to update and than as usual it did the os-prober at the end which was ok, but since my /boot partition on that setup did not have the right efi/EFI/ it was not able to immediately switch into my refind menu like i am used to doing (because i did not install refind on my stable partition). so of course i go off to do that and then at the end it asks about putting stuff on my efi partition and i say yes and then a second later i'm wondering if i just overwrote my refind configuration file. after a bit of nosing around i could breath a bit better because no it did not destroy my config so i was all set. so you are not the only one here who can mess up something. :) songbird
Re: disk usage for /usr/lib on bullseye
On Wed, May 03, 2023 at 04:22:55PM -, Curt wrote: [...] > You really don't have to tread dangerous waters (or rather wade into > them, unless your Jesus) because you can simulate without root privileges. Yes, +1 for -s :-) > curty@einstein:~$ apt -s purge > NOTE: This is only a simulation! > apt needs root privileges for real execution. > Keep also in mind that locking is deactivated, > so don't depend on the relevance to the real current situation! ^ ...but then this sounds like a downright threat, doesn't it? ;-) Cheers Q: "Doctor, the -s option told me it would remove 0 packages" A: "Yes, but we told you to nor depend on it" -- t signature.asc Description: PGP signature
Re: Problème pour servir à un exécutable sa dépendance à libc.so.6 (debian 11)
Ça a compilé. Ça tourne sur architecture aarch64. Mais il y a des problèmes avec certaines dépendances à des fonctions du shell ou à systemd (inexistantes sur x86_64) que je dois régler. > Le 3 mai 2023 à 09:40, didier gaumet a écrit : > > Le mercredi 03 mai 2023 à 03:18 +0200, roger.tar...@free.fr a écrit : > [...] > > Est-ce aussi simple que ça ou y a-t-il des pièges sournois dans la > > cross-compilation ? > > Je n'y connais rien vu que je ne construis pas/plus d'exécutables et encore > moins par cross-compilation mais le wiki Debian a un article sur les > différentes possibilités et bonnes pratiques de cross-compilation en > environnement Debian: > https://wiki.debian.org/CrossCompiling > >
Resolved (was: Re: OT: Using my (new) cable based ISP with their modem in bridge mode and my existing router)
Intentionally top posting: Thanks to all who replied, I got the Arris DG2470A modem (/ router) working in bridge mode with my existing router (Ubiquiti Edge Router X). I made a dumb mistake -- I had my router and another computer plugged into the Arris (I used the other computer to configure the Arris), and then I switched to bridge mode. At least once I noticed that I could ping the Internet from that other computer, which meant that the Arris was in bridge mode, but that computer was using the Arris modem instead of my router. Since then, I've done better -- e.g., configured the Arris to bridge mode, then powered down the Arris, unplugged that other computer, plugged in my Ubiquiti router and configured it to connect to the WAN by DHCP. Aside: In my previous (DSL) installation, the modem was a modem only, and had only one place to connect an Ethernet cable. With the Arris, being a router as well as a modem, it had 4 places to plug in an Ethernet cable, and, without thinking about it, I plugged in two devices (a computer and the Ubiquiti), but, in bridge mode, only one of those was going to work. Sometimes I feel like an idiot. All seems well. On Friday, April 28, 2023 11:08:45 PM David Wright wrote: -- rhk | No entity has permission to use this email to train an AI.
Re: disk usage for /usr/lib on bullseye
Le 3 mai 2023 Curt a écrit : > You really don't have to tread dangerous waters (or rather wade into > them, unless your Jesus) because you can simulate without root privileges. > > curty@einstein:~$ apt -s purge > NOTE: This is only a simulation! Nice parameter, thanks !
Re: disk usage for /usr/lib on bullseye
On 2023-05-02, Greg Wooledge wrote: > > unicorn:~$ apt purge > E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: > Permission denied) > E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), > are you root? > > Rats! No luck here. Either "apt purge" is not an error, or the argument > processing and validation happens only after acquiring the lock. > > Now we have to tread dangerous waters to find out more information. > You really don't have to tread dangerous waters (or rather wade into them, unless your Jesus) because you can simulate without root privileges. curty@einstein:~$ apt -s purge NOTE: This is only a simulation! apt needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Re: Segfaults after upgrade to Debian 11.7 on virtualized systems with AMD Ryzen CPU
On 02 May 2023 00:19, NetValue Operations Centre wrote: Good thinking, trying that. I worked through some of the cpu features, and when removing the line: the test VM on 5.10.0-22-amd64 booted successfully. https://www.kernel.org/doc/Documentation/x86/protection-keys.txt "Memory Protection Keys provides a mechanism for enforcing page-based protections" "The kernel will send a SIGSEGV in both cases, but si_code will be set to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when the plain mprotect() permissions are violated." So, sounds like a memory protection system which can result in seg faults. AFAICT the host system is running just fine with PKU feature on hosts running either 5.10.0-21-amd64 or 5.10.0-22-amd64, and the host kernel doesn't seem to affect the guest's behaviour either, only if the guest is running 5.10.0-22-amd64 with PKU passed through. I don't know the best bug tracker to create a ticket in would be... https://packages.debian.org/bullseye/linux-image-5.10.0-22-amd64 ? Regards, I have a "similar" problem on a Xen dom0, using a Ryzen 1700x. Xen dom0 won't boot with the new "5.10.0-22-amd64" kernel, but using "5.10.0-21-amd64" works. I don't have a serial console to read the full output, the last visible line is "dom0 has 2 vCPUs". So it happens during the creation of dom0. With a working kernel (so "5.10.0-21-amd64"), the next lines read: (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Scrubbing Free RAM in background So, as you said, it seems related to some "memory handling/protection system". But I didn't have any problem updating the Debian domUs to the new kernel, while using the old one in dom0. PS: if I'm not mistaken, the equivalent of Xen CPU attribution for VMs in KVM is "host-passthrough", maybe try that in your VM configs ?
Re: OT - WhatsApp Web y Firefox [SOLUCIONADO]
El 2/5/23 a las 13:04, JavierDebian escribió: El 2/5/23 a las 12:02, Camaleón escribió: El 2023-05-02 a las 11:46 -0300, JavierDebian escribió: El 2/5/23 a las 10:04, Camaleón escribió: El 2023-05-02 a las 09:39 -0300, JavierDebian escribió: Desde hace una semana me sucede algo extraño. En Firefox-esr 102.10.0esr (64-bit) instalado desde los repositorios de "bookworm", me sucede que si intento ingresar a la dirección https://web.whatsapp.com/ (WhatsApp Web), me redirige automáticamente a https://www.whatsapp.com/ (Página de inicio WhatsApp). No sucede lo mismo con Firefox 112.0.1 (64-bit) instalado desde "sid", ni con Chromium, ni con Chrome. Y no, no se "chocan", nunca lo hicieron, manejan carpetas y archivos distintos. He limpiado historiales, cookies, etc, pero Firefox-esr se niega a ingresar a esa dirección. Hasta llegué a eliminar la carpeta de datos /home/usuario/.mozilla Y no hay caso, se niega a ingresar WhatsApp Web. ¿Alguno tuvo problema similar? Sistema basado en Debian "bookworm" 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-2 (2023-04-08) x86_64 GNU/Linux Prueba a desactivar el javascript del Firefox viejito (102.10) y vuelve a cargar la aplicación web, a ver qué hace. Sólo se me ocurre que la página web esté detectando la versión del navegador no compatible y te redirija mediante algún script a la página principal. Saludos, Nop, se sigue negando. Es más, aún picando el enlace a web.whatsapp.com que tiene la página de inicio, me devuelve al principio. Adjunto video (...) Hum... prueba con este truquillo: [FIX] Whatsapp web redirecting to whatsapp.com https://www.reddit.com/r/whatsapp/comments/q25kpp/fix_whatsapp_web_redirecting_to_whatsappcom/ Saludos, Solución "de chiripa" como decimos acá. Se me ocurrió toquetear las extensiones, hasta que empecé a tocar "User Agent Switcher". Si bien estaba desactivada, la activé para modo "Windows-Firefox 112", y funcionó. (Es una función que necesito para que los sitios de Gobierno crean que uso Windows y Edge). Volví al "Predeterminado", o sea desactivar la extensión... ...y funciona Gracias a todos. JAP Ahora sí está verdaderamente solucionado. Por alguna razón que desconozco, mi navegador Firefox-esr se convirtió en un dispositivo Android. Y estaba teniendo problemas con otras páginas por lo horrible que se veían. Viendo este artículo https://support.mozilla.org/en-US/kb/how-reset-default-user-agent-firefox me encontré que estaba configurado como Agente de usuario: Mozilla/5.0 (Android 10; Mobile; rv:91.0) Gecko/91.0 Firefox/91.0 ¿Por qué razón hizo esto? No lo se. Pero siguiendo las indicaciones del artículo, lo corregí. Gracias JAP
Re: Thunderbird and font size used to display plain text e-mails?
On Sun, 30 Apr 2023 14:26:12 -0600, D. R. Evans wrote: > I have TB configured so as to display incoming e-mail as plain text. They > display correctly, BUT the font used to display the contents in the third > pane > is too large on the new monitor. How *exactly* do I control the size of the > font used to display the contents of received plain text e-mails? > In Settings, General under Language & Appearance there is Fonts & Colors. After it there is Advanced... button. There you can select font face and font size and if plain text messages are shown in fixed width. Especially check Latin and "Other Writing Systems". -- Virgo Pärna virgo.pa...@mail.ee
Re: AW: Was it a good idea to buy an Epson printer?
Schwibinger Michael (12023-05-03): > What do I do wrong? Among other things, what you are doing wrong: - Top posting. - Using 0x65 0x57 0x3A 0x20 instead of 0x52 0x65 0x3A 0x20 as a reply marker in the subject. -- Nicolas George
AW: AW: Was it a good idea to buy an Epson printer?
Good Morning Thank You. Print setting is saying: Epson Ecotank. What do I do wrong? Regards Sophie Von: Andrew M.A. Cater Gesendet: Montag, 1. Mai 2023 17:42 An: debian-user@lists.debian.org Betreff: Re: AW: Was it a good idea to buy an Epson printer? On Fri, Apr 28, 2023 at 10:20:59AM +, Schwibinger Michael wrote: > Good afternoon > > > Thank You for help. > > Its Debian 11 LXDE > In English locale: Preferences -> Print Settings from the menus > > I did not find a button: > > Install printer. > > > Regards > Sophie > > > > Von: Andrew M.A. Cater > Gesendet: Montag, 24. April 2023 21:41 > An: debian-user@lists.debian.org > Betreff: Re: Was it a good idea to buy an Epson printer? > > On Mon, Apr 24, 2023 at 01:36:24PM +, Schwibinger Michael wrote: > > > > > > Good afternoon > > > > Thank You > > Was it a good idea to buy EPSON? > > > > Regards > > Sophie > > > > Good evening, Sophie > > Many printers can be supported in Debian: one way or another we should be > able to help you. > > Since we cannot be with you to see exactly what you are doing: could you > please answer some questions for the list to help us to help you? > > Just to check: Exactly which version of Debian are you using? > > You can find this in the file /etc/debian_version > > Which desktop environment are you running? > > GNOME or KDE or one of the others? > > Many desktop environments have Settings or something similar gathering > together tools to set up screens, sound and printers. > > Thank you for your help in helping us :) > > With best wishes > > Andy Cater > or something similar which gathers together tools to set up sound, screens > and so on. > > > > > > > > > Von: The Wanderer > > Gesendet: Freitag, 14. April 2023 23:28 > > Bis: debian-user@lists.debian.org > > Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you are > > using the wrong driver > > > > On 2023-04-14 at 19:17, Brian wrote: > > > > > On Fri 14 Apr 2023 at 19:06:08 -0400, The Wanderer wrote: > > > > > >> On 2023-04-14 at 18:52, Brian wrote: > > > > >>> The EPSON ET M 1120 doesn't exist. Do we have to guess its > > >>> correct name as well as any other relevant information? > > >> > > >> When I searched for > > >> > > >> Epson ET M 1120 > > >> > > >> I got a suggestion that I may have meant "M1120" instead of the > > >> last two search terms, and hits for the "Epson EcoTank ET M1120" > > >> and/or "Epson EcoTank M1120", which look to be different names for > > >> the same model and to be a fairly clear match. > > >> > > >> While, yes, specifying the exact name clearly would be preferable, > > >> this is far from unreasonably difficult to figure out. > > > > > > I decided to take your signature as a template for my original > > > response :). > > > > I can respect that! > > > > >>> I haven't a clue what you are going on about here. Shift-L in > > >>> mutt was used at this end. > > >> > > >> Your replies to the OP have been fine, AFAIK. The OP's message was > > >> itself a reply, as can be seen by looking at its headers > > >> (In-Reply-To: and References:), but was otherwise presented as if > > >> it had been the start of a new thread; that is not fine, because it > > >> hides the "new thread" inside of the existing one, at least for > > >> anyone using a threaded view of the list of messages. > > > > > > That's an issue for the OP, not me. > > > > Certainly. I was meaning that bullet-point item as an addendum to the > > list you provided (which I understand to have been aimed at the OP), not > > as something directed at you. > > > > -- > >The Wanderer > > > > The reasonable man adapts himself to the world; the unreasonable one > > persists in trying to adapt the world to himself. Therefore all > > progress depends on the unreasonable man. -- George Bernard Shaw > > >
Re: Request for guidance to output(print, i.e.) mouse movements, key press, perepherals insert, etc., on a terminal
Le 5/2/23 à 14:40, songbird a écrit : [...] note this from the package description: "evtest is now in maintenance mode and doesn't support all the features of the latest kernels; evemu-record from the evemu-tools package should be used instead." Thanks for the heads-up! Best, -- yassine -- sysadm +213-779 06 06 23 http://about.me/ychaouche Looking for side gigs.
Re: Re : Re: Problème pour servir à un exécutable sa dépendance à libc.so.6 (debian 11)
Le mercredi 03 mai 2023 à 03:18 +0200, roger.tar...@free.fr a écrit : [...] > Est-ce aussi simple que ça ou y a-t-il des pièges sournois dans la > cross-compilation ? Je n'y connais rien vu que je ne construis pas/plus d'exécutables et encore moins par cross-compilation mais le wiki Debian a un article sur les différentes possibilités et bonnes pratiques de cross-compilation en environnement Debian: https://wiki.debian.org/CrossCompiling
Re: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver
On Tue, May 02, 2023 at 09:31:39PM -0700, Charlie Gibbs wrote: [...] > I don't know about your position, but I find myself repeating > Hanlon's Razor a lot: "Never ascribe to malice that which can > adequately be explained by stupidity." But then, in the back > of my mind, a little voice replies: "But Microsoft isn't stupid!" My preferred tool in this case is Clarke's Third Razor: "any sufficiently advanced form of malice is indistinguishable from stupidity" With apologies to Arthur C. Clarke and whoever Hanlon actually is. Cheers -- t signature.asc Description: PGP signature
