Em Mon, 04 Sep 2006 09:46:10 -0300
Otavio Salvador <[EMAIL PROTECTED]> escreveu:
> Gustavo Noronha Silva <[EMAIL PROTECTED]> writes:
>
> >
> > Using an alternative
> >
> >
> > I install two gconf defaults files, one containing this (save the
> > markers):
Gustavo Noronha Silva <[EMAIL PROTECTED]> writes:
>
> Using an alternative
>
>
> I install two gconf defaults files, one containing this (save the
> markers):
Well all good here but then on d-i side we'll need to configure the
default one?
--
O
Gustavo Noronha Silva wrote:
>
> Using an alternative
>
I strongly prefer this one. Anything that makes d-i dump a
non-package-owned file onto the disk is not a good thing.
--
see shy jo
signature.asc
Description: Digital signature
Em Wed, 23 Aug 2006 02:29:27 -0400
Joey Hess <[EMAIL PROTECTED]> escreveu:
> If the schema file is managed by alternatives, I think it would be
> better to let d-i detect this case and switch to the sudo
> alternative. Users can choose to use a sudo-only setup in expert mode
> so a hidden question
Gustavo Noronha Silva wrote:
> Could be done, as well, but I'd prefer the gconf route, since that
> doesn't require patching .desktop files. Something that comes to my mind
> is providing a debconf key in the gksu packge that would never be asked,
> or would be 'low', and that would be used to deci
Em Tue, 22 Aug 2006 17:06:48 -0400
Joey Hess <[EMAIL PROTECTED]> escreveu:
> > Though, maybe that is easier said than done. Thanks.
>
> We really can't make that kind of change at install time in d-i.
Can we provide a default gconf setting at install time, though? The
'gksu' application decides
Joseph Smidt wrote:
> I don't know if this fix works with policy, but all you have to do is in
> every gui admin's .desktop file change:
>
> TryExec=gksu
> Exec=gksu -u root disks-admin
>
> or
>
> TryExec=gksu
> Exec=gksu disks-admin
>
> To:
>
> TryExec=gksudo
> Exec=gksudo disks-admin
>
> Th
I don't know if this fix works with policy, but all you have to do is inevery gui admin's .desktop file change:TryExec=gksuExec=gksu -u root disks-adminorTryExec=gksuExec=gksu disks-admin
To:TryExec=gksudoExec=gksudo disks-adminThough, maybe that is easier said than done. Thanks. Joseph
Andre Luis Lopes wrote:
>Maybe gksu ? Here's what I have in my
> /usr/share/applications/synaptic.desktop (which is a standard file, ie,
> not changed by me) :
>
> Exec=gksu -u root /usr/sbin/synaptic
>
>This way when I click on GNOME's menu shortcut to run Synaptic
> (GNOME's frontend to
On 8/14/06, Andre Luis Lopes <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joey Hess wrote:
> Joseph Smidt wrote:
>> I choose to go the sudo route. Everything works fine on the command
>> line, i.e. I can't login as root and sudo works with the password I gave
>> it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joey Hess wrote:
> Joseph Smidt wrote:
>> I choose to go the sudo route. Everything works fine on the command
>> line, i.e. I can't login as root and sudo works with the password I gave
>> it. But none of the gui admin applications work without roo
Joseph Smidt wrote:
> I choose to go the sudo route. Everything works fine on the command
> line, i.e. I can't login as root and sudo works with the password I gave
> it. But none of the gui admin applications work without root.
> Example, I try to use synaptic my sudo password doesn't work.
Subject: debian-installer: Sudo not properly configuredPackage: debian-installerSeverity: normal*** Please type your report below this line ***Boot method: Sid Businesscard i386Image version: Beta 3
Date: August 12, 2006Machine: Toshiba A105-S4004 LaptopProcessor:i386 Centrino DuoMemory:1 GBPartiti
13 matches
Mail list logo
