Re: Administration CUPS impossible

Super, C'est certainement lié a ce bug qui est prochainement corrigé dans debian https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1950484 [image: photo] *Michel Memeteau* Directeur, Ekimia SAS +33 (0)9 72 30 83 34 <+33+9+72+30+83+34> | m...@ekimia.fr | Notre WebBoutique :

Re: Administration CUPS impossible

Le 06/12/2021 à 09:35, Michel Memeteau - EKIMIA a écrit : cat /etc/group |grep $USER Effectivement, je n'étais pas dans le groupe lpadmin. J'ai donc fait un sudo usermod -aG lpadmin moi J'ai retenté de modifier les réglages de CUPS en localhost:631, et ça a marché. J'ai relancé mon

Re: Administration CUPS impossible

Bonjour , Je crois que c'est un bug auquel j'ai fait face récemment que dit cat /etc/group |grep $USER ? [image: photo] *Michel Memeteau* Directeur, Ekimia SAS +33 (0)9 72 30 83 34 <+33+9+72+30+83+34> | m...@ekimia.fr | Notre WebBoutique : https://shop.ekimia.fr |

Re: Administration demande d’aide ?

Bonsoir, Je cherche un étudiant, sinon pour faire faire le travail, je vais voir un ancien collègue de mon père et je lui demande …. Pour le reste je sais que l’on s’occupe de mes affaires … Le vendredi 1 octobre 2021 à 20:20:02 UTC+2, Alexandre Garreau a écrit : > Le vendredi 1 octobre 2021,

Re: Administration demande d’aide ?

Le vendredi 01 octobre 2021 à 20:14 +0200, Alexandre Garreau a écrit : [...] > j’ai rien vu de désagréable jusqu’ici dans ce thread par contre > c’était > incompréhensible :o il y avait bcp d’infos non expliquées [...] Alors là, non, Alexandre, je m'insurge, non seulement tu ne comprends

Re: Administration demande d’aide ?

Le vendredi 1 octobre 2021, 18:00:31 CEST ptilou a écrit : > J’ai tapé une des ligne contenue dans cette page : > http://carlibrary.org/ExifTool.htm Ca donne : > D:\repertoire\nom.jpg,, > Sur moins de 650 K lignes, et il a mit plus de 9 heures. donc pour 650 000 images, c’est ça ? et il a rien

Re: Administration demande d’aide ?

Le vendredi 1 octobre 2021 à 16:40:02 UTC+2, Alexandre Garreau a écrit : > Le vendredi 1 octobre 2021, 16:01:26 CEST ptilou a écrit : > > Bonjour, > > > > Le vendredi 1 octobre 2021 à 12:00:04 UTC+2, Marc Chantreux a écrit : > > > salut ptilou, > > > > > > Le Fri, Oct 01, 2021 at 02:18:15AM

Re: Administration demande d’aide ?

Le vendredi 1 octobre 2021, 16:01:26 CEST ptilou a écrit : > Bonjour, > > Le vendredi 1 octobre 2021 à 12:00:04 UTC+2, Marc Chantreux a écrit : > > salut ptilou, > > > > Le Fri, Oct 01, 2021 at 02:18:15AM -0700, ptilou a écrit : > > > J’ai plusieurs problèmes d’administrations de fichiers, je

Re: Administration demande d’aide ?

Bonjour, Le vendredi 1 octobre 2021 à 12:00:04 UTC+2, Marc Chantreux a écrit : > salut ptilou, > Le Fri, Oct 01, 2021 at 02:18:15AM -0700, ptilou a écrit : > > J’ai plusieurs problèmes d’administrations de fichiers, je cherche > > comment manipuler un fichier cvs, que j’ai géré avec exisf tool,

Re: Administration demande d’aide ?

salut ptilou, Le Fri, Oct 01, 2021 at 02:18:15AM -0700, ptilou a écrit : > J’ai plusieurs problèmes d’administrations de fichiers, je cherche > comment manipuler un fichier cvs, que j’ai géré avec exisf tool, puis > après avoir éliminé les duplicata, je dois renommer l’ensemble des > fichiers,

Re: administration of initscripts

On Mon, Apr 22, 2013 at 07:51:42PM +0100, Jonathan Dowland wrote: On Sun, Apr 21, 2013 at 12:31:25AM +0100, Kevin Chadwick wrote: Jonathan Dowland wrote: If you were a faithful follower of Kernighan UNIX philosophy, you wouldn't touch those nasty BSDs with a bargepole. Rubbish

Re: administration of initscripts

On Sun, Apr 21, 2013 at 12:31:25AM +0100, Kevin Chadwick wrote: On Wed, Apr 17, 2013 at 09:51:02PM +0100, Kevin Chadwick wrote: And that's a Linux problem where some BSDs put lots of effort into compliance only to have the standard changed to suit linux due to pressure. Which

Re: administration of initscripts

Hello Excerpt from Roger Leigh: -- snip -- update-rc.d foo disable|enable is one method. -- snip -- i did played further around with this. First have a look at this: # find /etc/rc[S0-6].d/ -iname '*mountkernfs.sh*' /etc/rcS.d/S01mountkernfs.sh # update-rc.d mountkernfs.sh disable

Re: administration of initscripts

On Wed, Apr 17, 2013 at 09:52:04PM +0100, Kevin Chadwick wrote: And did it boot slower than with init scripts and waste valuable memory. Lookup systemd on the buildroot list and you will see. Debian may run on even a cheap toaster one day but systemd would causes issues when that is possible.

Re: administration of initscripts

On Wed, Apr 17, 2013 at 09:51:02PM +0100, Kevin Chadwick wrote: And that's a Linux problem where some BSDs put lots of effort into compliance only to have the standard changed to suit linux due to pressure. Which standard, POSIX? POSIX is a very good thing. Do you disagree? I could perhaps

Re: administration of initscripts

Hello Roger, Excerpt from myself: -- snip -- insserv clearly complains instead that other services are affected by this change. Generally to a admin insserv seems to be nicer API over update-rc.d to me. Apart from that, by this i found a major bug in rc-update(). Will fix that. i have

Re: administration of initscripts

On Wed, Apr 17, 2013 at 09:51:02PM +0100, Kevin Chadwick wrote: And that's a Linux problem where some BSDs put lots of effort into compliance only to have the standard changed to suit linux due to pressure. Which standard, POSIX?

Re: administration of initscripts

Hello Roger Excerpt from Roger Leigh: -- snip -- Yes, the man page says it swaps the S for a K. e.g. say we have the following link: /etc/rc2.d/K10cups Then afaik - and please correct if i am wrong - init will call the stop part of this initscript when ever runlevel 2 is entered. So

Re: administration of initscripts

On Tue, Apr 16, 2013 at 10:21:02PM +0100, Kevin Chadwick wrote: I believe very strongly that it is. universality with Linux supporting smaller and smaller Arm chips is part of what I was touching on in the paragraph you had a hard time deciphering. This is something BSD is having a hard time

Re: administration of initscripts

On Tue, Apr 16, 2013 at 08:30:45PM -0400, staticsafe wrote: On 4/16/2013 19:33, Chris Bannister wrote: On Tue, Apr 16, 2013 at 10:21:02PM +0100, Kevin Chadwick wrote: I believe very strongly that it is. universality with Linux supporting

Re: administration of initscripts

Roger Leigh wrote: Getting rid of all the /etc/default disable options will be a release goal for jessie. Good. I'd prefer to be rid of /etc/default entirely! For example, I just learned about /etc/default/keyboard. Why not /etc/keyboard or /etc/keyboard.default? Having a central location for

Re: administration of initscripts

On 04/16/2013 11:55 AM, Thilo Six wrote: Hello Michael, Excerpt from Michael Biebl: -- snip -- + dropping human readable textfiles in favour of c binary code, which makes it needless more complex to debug the whole show. That's non-sense. systemd unit files are text-files in ini-like

Re: administration of initscripts

On 04/16/2013 03:02 PM, Kevin Chadwick wrote: Lets not pollute this useful thread with systemd It seems a thread about init systems and administration/tweaking of them is the most appropriate place for systemd to be mentioned. Not least that it can solve the problem the OP had. It should not be

Re: administration of initscripts

Joel Roth wrote: Roger Leigh wrote: Getting rid of all the /etc/default disable options will be a release goal for jessie. Good. I'd prefer to be rid of /etc/default entirely! So you would rather that people edit the /ec/init.d/* scripts themselves and manage them as conffiles at upgrade

Re: administration of initscripts

Bob Proulx wrote: Joel Roth wrote: Roger Leigh wrote: Getting rid of all the /etc/default disable options will be a release goal for jessie. Good. I'd prefer to be rid of /etc/default entirely! So you would rather that people edit the /ec/init.d/* scripts themselves and manage

Re: administration of initscripts

Hello Roger Excerpt from Roger Leigh: update-rc.d foo disable|enable -- snip -- It might be a nuisance but running the stop part of the initscript isn't the same as not touching it all? Sorry, I don't quite understand the question here. update-rc.d never starts or stops anything--all

Re: administration of initscripts

Joel Roth wrote: I suppose the answer is that there is no shortcut to administering a system than learning the details. Nope. No such thing as a free lunch. And in the free(dom) software community we have the additional free market burden of many different sources. There are many different

Re: administration of initscripts

Although, I accept there is no real excuse for my rudeness. No worries, I have a thick actually english skin as I hope those I talk to do too. If you think that's rude, you are probably a gent. -- ___ 'Write programs that do

Re: administration of initscripts

I believe very strongly that it is. universality with Linux supporting smaller and smaller Arm chips is part of what I was touching on in the paragraph you had a hard time deciphering. This is something BSD is having a hard time competing with atleast in my experience of wanting to be

Re: administration of initscripts

On 04/16/2013 03:02 PM, Kevin Chadwick wrote: Lets not pollute this useful thread with systemd It seems a thread about init systems and administration/tweaking of them is the most appropriate place for systemd to be mentioned. Not least that it can solve the problem the OP had. It

Re: administration of initscripts

On Wed, Apr 17, 2013 at 08:55:42PM +0200, Thilo Six wrote: Hello Roger Excerpt from Roger Leigh: update-rc.d foo disable|enable -- snip -- It might be a nuisance but running the stop part of the initscript isn't the same as not touching it all? Sorry, I don't quite

Re: administration of initscripts

+ dropping human readable textfiles in favour of c binary code, which makes it needless more complex to debug the whole show. That's non-sense. systemd unit files are text-files in ini-like format and much more readable then shell scripts with all their boiler plate. I think you miss

Re: administration of initscripts

On Tue, Apr 16, 2013 at 10:33:47AM +0100, Kevin Chadwick wrote: I think you miss the point which is those unit files depend on C code So do classic init scripts: $ file /sbin/init /sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs),

Re: administration of initscripts

On Mon, Apr 15, 2013 at 09:20:03PM +0100, Kevin Chadwick wrote: Lets not pollute this useful thread with systemd It seems a thread about init systems and administration/tweaking of them is the most appropriate place for systemd to be mentioned. Not least that it can solve the problem the OP had.

Re: administration of initscripts

On 04/16/2013 04:33 AM, Kevin Chadwick wrote: + dropping human readable textfiles in favour of c binary code, which makes it needless more complex to debug the whole show. That's non-sense. systemd unit files are text-files in ini-like format and much more readable then shell scripts with all

Re: administration of initscripts

Hello Michael, Excerpt from Michael Biebl: -- snip -- + dropping human readable textfiles in favour of c binary code, which makes it needless more complex to debug the whole show. That's non-sense. systemd unit files are text-files in ini-like format and much more readable then shell

Re: administration of initscripts

Lets not pollute this useful thread with systemd It seems a thread about init systems and administration/tweaking of them is the most appropriate place for systemd to be mentioned. Not least that it can solve the problem the OP had. It should not be ignored or avoided from being

Re: administration of initscripts

On Tue, Apr 16, 2013 at 10:33:47AM +0100, Kevin Chadwick wrote: I think you miss the point which is those unit files depend on C code So do classic init scripts: $ file /sbin/init /sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared

Re: administration of initscripts

On Tue, Apr 16, 2013 at 09:06:31PM +0100, Kevin Chadwick wrote: Yes and do you know it was designed to do just what it does for a good reason in 32 kb of code. Hello world is 8kb Not relevant to choosing an init system. I am saying it is easy for anyone to follow edit and lookup a man page

Re: administration of initscripts

Yes and do you know it was designed to do just what it does for a good reason in 32 kb of code. Hello world is 8kb Not relevant to choosing an init system. I believe very strongly that it is. universality with Linux supporting smaller and smaller Arm chips is part of what I was touching

Re: administration of initscripts

On Mon, Apr 15, 2013 at 11:21:00AM -0500, Yaro Kasear wrote: [systemd] has a concurrent startup, meaning it brings a system up and down *very* quickly by starting independent units at the same time. Standard SysV init generally cannot do this, though it's hard to account for how initscripts

Re: administration of initscripts

On Mon, Apr 15, 2013 at 09:09:15PM +0200, Thilo Six wrote: update-rc.d foo disable|enable is one method. Thank you for sharing this! It might be a nuisance but running the stop part of the initscript isn't the same as not touching it all? Sorry, I don't quite understand the question

Re: administration of initscripts

Rick Thomas wrote: Bob Proulx wrote: I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? For an example of where one will want to manage the init scripts, take a look at the thread

Re: administration of initscripts

On Tue, Apr 16, 2013 at 10:21:02PM +0100, Kevin Chadwick wrote: Yes and do you know it was designed to do just what it does for a good reason in 32 kb of code. Hello world is 8kb Not relevant to choosing an init system. I believe very strongly that it is. universality with Linux

Re: administration of initscripts

On 4/16/2013 19:33, Chris Bannister wrote: On Tue, Apr 16, 2013 at 10:21:02PM +0100, Kevin Chadwick wrote: Yes and do you know it was designed to do just what it does for a good reason in 32 kb of code. Hello world is 8kb Not relevant to choosing an init system. I believe very strongly

Re: administration of initscripts

On Apr 14, 2013, at 10:10 PM, Bob Proulx wrote: I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? Hi Bob, For an example of where one will want to manage the init scripts, take a

Re: administration of initscripts

I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? Hi Bob, For an example of where one will want to manage the init scripts, take a look at the thread in debian-user with

Re: administration of initscripts

On Mon, Apr 15, 2013 at 11:02:19AM +0100, Kevin Chadwick wrote: I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? Hi Bob, For an example of where one will want to

Re: administration of initscripts

I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? What is more complicated than this. If you want it then install it. If you don't want it then remove or purge it. With those two

Re: administration of initscripts

On Mon, Apr 15, 2013 at 08:39:27AM -0400, Stefan Monnier wrote: I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? What is more complicated than this. If you want it then install

Re: administration of initscripts

Le 15/04/2013 14:39, Stefan Monnier a écrit : I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? What is more complicated than this. If you want it then install it. If you don't want it

Re: administration of initscripts

Le 15/04/2013 16:55, Roger Leigh a écrit : On Mon, Apr 15, 2013 at 08:39:27AM -0400, Stefan Monnier wrote: I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? What is more complicated

Re: administration of initscripts

On Mon, Apr 15, 2013 at 05:28:02PM +0200, Erwan David wrote: Le 15/04/2013 16:55, Roger Leigh a écrit : On Mon, Apr 15, 2013 at 08:39:27AM -0400, Stefan Monnier wrote: I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always

Re: administration of initscripts

On 04/15/2013 05:02 AM, Kevin Chadwick wrote: I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? Hi Bob, For an example of where one will want to manage the init scripts, take a look at

Re: administration of initscripts

On Mon, Apr 15, 2013 at 03:55:33PM +0100, Roger Leigh wrote: Getting rid of all the /etc/default disable options will be a release goal for jessie. Very glad to hear that. Services that come shipped with an /etc/default file that disables the daemon 'by default' really irk me. Not least puppet,

Re: administration of initscripts

Am 15.04.2013 17:26, schrieb Erwan David: And disabling them in /etc/default prevent launching them after boot (see my need on the other tread). update-rc.d disable is the proper way to disable a service from starting at boot time. -- Why is it that all of the instruments seeking

Re: administration of initscripts

Thilo Six wrote: gentoo has a rather nice API for an administrator to handle initscripts s.th. i always missed in debian. Isn't sysv-rc-conf what you are looking for? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Re: administration of initscripts

Hello Bob, Excerpt from Bob Proulx: Thilo Six wrote: Subject: administration of initscripts ...in debian has been no pleasure for some time now. Sorry to hear that. Why not? I was looking for the offical way of dealing with initscript for some time now. If you look online mostly

Re: administration of initscripts

Hello Roger, Excerpt from Roger Leigh: -- snip -- update-rc.d foo disable|enable is one method. Thank you for sharing this! It might be a nuisance but running the stop part of the initscript isn't the same as not touching it all? -- snip -- Getting rid of all the /etc/default disable

Re: administration of initscripts

Hello Siard, Excerpt from Siard: Thilo Six wrote: gentoo has a rather nice API for an administrator to handle initscripts s.th. i always missed in debian. Isn't sysv-rc-conf what you are looking for? Thank you for your help. I am aware of the existents of 3rd party managing tools of this

Re: administration of initscripts

file-rc works, but only just. I would not be surprised if it was removed for the next stable release--it's simply incompatible with dependency-based booting. That's a shame, I would take direct editing of runlevel.conf over dependency-based booting myself. When you are using dynamic

Re: administration of initscripts

Hello Yaro, Excerpt from Yaro Kasear: -- snip -- Systemd has assimilated udev, -- snip -- Related to the above two downsides, systemd is not really a crowning example of a developer following the UNIX Philosophy of one simple task and do it well. -- snip -- Administrators might not

Re: administration of initscripts

On Mon, 15 Apr 2013 08:39:27 -0400 Stefan Monnier monn...@iro.umontreal.ca wrote: I have been using Debian for many years now. In all of that time I have never wanted to manage init scripts. I always wonder. What are people trying to do? What is more complicated than this. If you

Re: administration of initscripts

Am 15.04.2013 20:12, schrieb Celejar: What's wrong with sysv-rc-conf (although it won't work for some of the fancier stuff you have in mind, such as running daemons on demand)? It's orphaned and hasn't seen any updates for over 6 years. -- Why is it that all of the instruments seeking

Re: administration of initscripts

Am 15.04.2013 21:35, schrieb Thilo Six: + dropping human readable textfiles in favour of c binary code, which makes it needless more complex to debug the whole show. That's non-sense. systemd unit files are text-files in ini-like format and much more readable then shell scripts with all their

Re: administration of initscripts

On Tue, 16 Apr 2013 02:12:20 +0200 Michael Biebl bi...@debian.org wrote: Am 15.04.2013 20:12, schrieb Celejar: What's wrong with sysv-rc-conf (although it won't work for some of the fancier stuff you have in mind, such as running daemons on demand)? It's orphaned and hasn't seen any

Re: administration of initscripts

On 04/15/2013 07:13 PM, Michael Biebl wrote: Am 15.04.2013 21:35, schrieb Thilo Six: + dropping human readable textfiles in favour of c binary code, which makes it needless more complex to debug the whole show. That's non-sense. systemd unit files are text-files in ini-like format and much

Re: administration of initscripts

Am 16.04.2013 04:26, schrieb Yaro Kasear: UNLESS, does anyone know if journalctl works fine inside a LiveCD/DVD/USB/Ferret/Whatever on another systemd setup? Or, maybe as a better way to put it, use a live media's journalctl to use a non-running systemd's journal? Sure, that works: journalctl

Re: administration of initscripts

Am 16.04.2013 04:26, schrieb Yaro Kasear: On 04/15/2013 07:13 PM, Michael Biebl wrote: Am 15.04.2013 21:35, schrieb Thilo Six: + dropping human readable textfiles in favour of c binary code, which makes it needless more complex to debug the whole show. That's non-sense. systemd unit files

Re: administration of initscripts

Thilo Six wrote: Subject: administration of initscripts ...in debian has been no pleasure for some time now. Sorry to hear that. Why not? Well the reason i write this, is i found a solution that works for me which i would like to share with you. Thank you for sharing. Following goals had

Re: Administration distante

Bonjour, Merci pour toutes vos propositions, je vais tester tout ça pendant les congés (surtout l'apéro ;). Bon week-end ! -- 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

Re: Administration distante

Le 27 juillet 2011 11:09, Nicolas Froidure froidure_nico...@yahoo.fr a écrit : Bref, qu'utilisez-vous pour intervenir à distance sur le Debian de vos proches ? J'utilise SSH ou eventuellement un client NX. Pour l'accès à travers leurs machinbox, soit je leur installes un client openvpn

Re: Administration distante

Le 27 juillet 2011 11:09, Nicolas Froidure froidure_nico...@yahoo.fr a écrit :            Bonjour,    Pour me débarrasser des soucis que mon entourage rencontre avec Windows, je fais mine de ne connaître que Linux (je sais, c'est moche). Seul problème, certains m'ont demandé d'installer Linux

Re: Administration distante

'lut, Bref, qu'utilisez-vous pour intervenir à distance sur le Debian de vos proches ? Teamviewer. Version gratuite pour les particuliers. Ca évite surtout de devoir modifier la box pour ouvrir le le port kivabien. Par rapport à vnc, il me semble que les perfs sont au rendez-vous. Attention

Re: Administration distante

Le 15182ième jour après Epoch, Nicolas Froidure écrivait: Bref, qu'utilisez-vous pour intervenir à distance sur le Debian de vos proches ? Je me fais inviter à l'apéro ;) -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER,

Re: Administration distante

Le Wed, 27 Jul 2011 11:09:11 +0200, Nicolas Froidure froidure_nico...@yahoo.fr a écrit : Bonjour, Pour me débarrasser des soucis que mon entourage rencontre avec Windows, je fais mine de ne connaître que Linux (je sais, c'est moche). Seul problème, certains m'ont demandé

Re: Administration distante

Le 27/07/2011 12:47, François TOURDE a écrit : Le 15182ième jour après Epoch, Nicolas Froidure écrivait: Bref, qu'utilisez-vous pour intervenir à distance sur le Debian de vos proches ? Je me fais inviter à l'apéro ;) +1, mais parfois il y a phénomène de rétorsion, et

Re: Administration distante

On Wed, 27 Jul 2011 18:25:23 +0200, fred f.r...@yahoo.fr wrote: Bref, qu'utilisez-vous pour intervenir à distance sur le Debian de vos proches ? Je me fais inviter à l'apéro ;) +1, mais parfois il y a phénomène de rétorsion, et rien n'est versé avant l'intervention ?

Re: Administration distante

Le 27/07/2011 11:09, Nicolas Froidure a écrit : Bonjour, (...) Bref, qu'utilisez-vous pour intervenir à distance sur le Debian de vos proches ? Bonjour, J'utilise aussi Teamviewer (www.teamviewer.com). L'avantage c'est qu'il n'y a rien a configurer au niveau de la box (ou

Re: Administration distante

Le 15182ième jour après Epoch, fred écrivait: Le 27/07/2011 12:47, François TOURDE a écrit : [...] Je me fais inviter à l'apéro ;) +1, mais parfois il y a phénomène de rétorsion, et rien n'est versé avant l'intervention ? C'est mieux, en général ;) ... Ça évite pas mal d'erreurs de pas

Re: Administration distante

Le 15182ième jour après Epoch, Jean-Yves F. Barbier écrivait: Y'a pire: l'acompte bien salé, suivit par le paiement du capital réévalué (café, pousse-café, rollmops) 'tain... Rollmops après le café/pousse-café? Faut oser, non? Mais je le note pour mes prochaines interventions :) -- Lisez la

Re: Administration à dis tance de systèmes chiffrés

On Fri, Nov 21, 2008 at 02:23:33AM +0100, Goldy wrote: En fin de compte, placer le montage en noauto n'empêche pas le système de demander le mot de passe au démarrage de l'os. Il va falloir chercher ailleurs. C'est curieux; à ce moment là je pense que la première chose à faire, c'est de

Re: Administration à distance de systè mes chiffrés

Yves Rutschle a écrit : On Mon, Sep 15, 2008 at 02:04:32AM +0200, Goldy wrote: Hmm, ça vaut peut-être le coup d'explorer une solution en mettant des niveaux de démarrage différents alors: en niveau 2 tu ne démarres pas le démon et tu ne montes pas /home, tu bootes, tu te loggues, tu

Re: Administration à distance de systè mes chiffrés

Je me répond à moi même. En fin de compte, placer le montage en noauto n'empêche pas le système de demander le mot de passe au démarrage de l'os. Il va falloir chercher ailleurs. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi

Re: Administration à distance de systè mes chiffrés

Goldy a écrit : L'idée de rediriger la console sur une autre machine est intéressante (je n'ai pas spécialement envie de faire de la virtualisation), tu peux utiliser une carte d'acces a distance. ilo chez HP rsa chez IBM, jesaispu chez DELL plein de vendeur en offre. -- Dominix -- Lisez

Re: Administration à distance de systèmes chiffrés

Ma solution serait un peu identique: un switch KVM en reseau. Cela te permet un peu comme VNC de prendre le controle du clavier de l'ecran a distance comme si l'on etait en face de la machine et ce meme pendant qu'elle boot. C'est un peu honéreux mais c tres facil a mettre en place et ne brise

Re: Administration à distance de systèmes chiffrés

Le Tue, 16 Sep 2008 01:17:11 +0200, Goldy wrote : [...] Ce n'est pas plus long si l'on dit à l'installateur de ne pas effacer la swap en écrivant des données aléatoires dessus. De plus, avec une telle configuration, une swap non chiffré est un trou de sécurité (la passphrase pouvant alors se

Re: Administration (+apt-get dist-upgrade) of 100s of machines

Douglas Allan Tutty dtutty-at-porchlight.ca |volatile-lists| wrote: I use aptitude (this is not a troll, please), and I use it interactivly. I have only those pacakges that I specifically _want_ installed marked as manual with everything else being automatic. Aa! What is *THIS*? manual

Re: Administration (+apt-get dist-upgrade) of 100s of machines

Here goes this term package breakage again. Do you know what it is and how it arises? Most of the time, dist-upgrade just decides to install a couple of extra packages. But some other times... I just never figured out what makes the difference and what the possible problems and solutions

Re: Administration (+apt-get dist-upgrade) of 100s of machines

On Sat, 21 Apr 2007 10:31:21 +0200 Peter Valdemar Mørch (vol) [EMAIL PROTECTED] wrote: Douglas Allan Tutty dtutty-at-porchlight.ca |volatile-lists| wrote: I use aptitude (this is not a troll, please), and I use it interactivly. I have only those pacakges that I specifically _want_

Re: Administration (+apt-get dist-upgrade) of 100s of machines

On Sat, Apr 21, 2007 at 10:31:21AM +0200, Peter Valdemar Mørch (vol) wrote: Douglas Allan Tutty dtutty-at-porchlight.ca |volatile-lists| wrote: I use aptitude (this is not a troll, please), and I use it interactivly. I have only those pacakges that I specifically _want_ installed marked as

Re: Administration (+apt-get dist-upgrade) of 100s of machines

On Sat, Apr 21, 2007 at 10:31:21AM +0200, Peter Valdemar M?rch (vol) wrote: Douglas Allan Tutty dtutty-at-porchlight.ca |volatile-lists| wrote: I use aptitude (this is not a troll, please), and I use it interactivly. I have only those pacakges that I specifically _want_ installed marked as

Re: Administration (+apt-get dist-upgrade) of 100s of machines

Peter Valdemar Morch wrote: Hi there, We have 100s of almost identical machines that need to be kept up-to-date with apt-get dist-upgrade . Having to run apt-get dist-upgrade manually on all of them is just not working (taking too much man-power) due to having to answer the same Y/N

Re: Administration (+apt-get dist-upgrade) of 100s of machines

Alex Samad wrote: If you have 100's of machines all in production or atleast all having to be kept to the same package setup. why not setup yor own repo (and extend it to your down release) could correspond to your SOE, when it comes time to update, go through the testing phase, once your

Re: Administration (+apt-get dist-upgrade) of 100s of machines

On Thu, Apr 19, 2007 at 10:37:54AM -, Peter Valdemar Morch wrote: We have 100s of almost identical machines that need to be kept up-to-date with apt-get dist-upgrade . Having to run apt-get dist-upgrade manually on all of them is just not working (taking too much man-power) due to having

Re: Administration (+apt-get dist-upgrade) of 100s of machines

On Thu, Apr 19, 2007 at 03:55:06PM +0200, Peter Valdemar M?rch wrote: Ok, but what is the alternative? I find that without dist-upgrade, I end up with a constantly growing number of packages in the The following packages have been kept back category. My 2 C worth. Preface: I've never

Re: Administration (+apt-get dist-upgrade) of 100s of machines

export aptopt= $ROOTCMD apt-get $aptopt -f -y dist-upgrade /dev/null Sorry for the late reply.. been busy. You know, you could always use apt-get -simulate dist-upgrade on your machines. Check the output and leave a token somewhere that then allows the machines to do the upgrade for

Re: Administration (+apt-get dist-upgrade) of 100s of machines

On Thu, Apr 19, 2007 at 10:37:54AM -, Peter Valdemar Morch wrote: Is there a smarter way? How does one manage many, many debian installations without having to give each one special manual treatment? Ideally I'd like this to be a fully automated operation and only be notified of any

Re: Administration (+apt-get dist-upgrade) of 100s of machines

Peter Valdemar Morch wrote: Hi there, We have 100s of almost identical machines that need to be kept up-to-date with apt-get dist-upgrade . Okay, I'm not an expert but I'll go like this. Having to run apt-get dist-upgrade manually on all of them is just not working (taking too much

Re: Administration (+apt-get dist-upgrade) of 100s of machines

cedric briner wrote: Peter Valdemar Morch wrote: Hi there, We have 100s of almost identical machines that need to be kept up-to-date with apt-get dist-upgrade . Okay, I'm not an expert but I'll go like this. Having to run apt-get dist-upgrade manually on all of them is just not= working

  1   2   >