On 27/04/17 05:44, Don Armstrong wrote:
Your newish hardware may require a backported kernel to function reliably.
This. Any recent Dell machine will likely have a Skylake or Kaby Lake
CPU and a bad time on the stock jessie kernel, especially if using the
iGPU. Please install a 4.9.18 kernel
Não é Debian em Cloud, falo dos sistemas FOSS.
Deveria haver uma forma de podermos instalar o sistema do zero.
Os sistemas em Cloud em geral vem com tudo no /, ou separam apenas o /,
/home e /usr.
Não é apenas isso, eles vem com as configurações padrão.
Alterar o fstab não é assim tão fácil,
Qual o problema do Debian em Cloud? Caso o sistema estaja no "/" Basta
alterar o fstab isso não é problema algum. Todos servicos de Cloud permitem
criar outras partições caso necessário.
Ao encaminhar esta mensagem, por favor:
1 - Apague meu endereço eletrônico;
2 - Encaminhe como Cópia Oculta
I'm trying to work on a home-grown kiosk using Jessie.
I've got 90% of it done, but I need it to logout after a certain time of
inactivity, but only after the computer has been used at least once since
the last start of X (otherwise it'll just be in a slow loop of restarting
X).
In other words,
On 04/26/2017 10:02 AM, Lisi Reisz wrote:
On Wednesday 26 April 2017 15:36:36 Richard Owlett wrote:
On 04/26/2017 07:50 AM, Darac Marjal wrote:
On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
For interface
Kent West composed on 2017-04-26 13:35 (UTC-0500):
> Don Armstrong wrote:
>> On Wed, 26 Apr 2017, Kent West wrote:
>> > Two identical newish Dell desktops. Configured for non-legacy, UEFI-only
>> > booting. No Secure-Boot or Fast Boot.
>> > Every other boot results in a hang at "Initializing
On Wed, Apr 26, 2017 at 12:44 PM, Don Armstrong wrote:
> On Wed, 26 Apr 2017, Kent West wrote:
> > Two identical newish Dell desktops. Configured for non-legacy, UEFI-only
> > booting. No Secure-Boot or Fast Boot.
>
> [...]
>
> > Every other boot results in a hang at
Pedro:
> Alex M, Ermengol, si em permeteu que us pregunti directament?
> Sembla que a vosaltres no us afecten aquests problemes de
> privacitat? Sí? No? Com us ho feu?
Jo sóc conscient dels riscos i procuro mantenir-me informat en
termes de seguretat alhora que intento trobar un equilibri prou
On Wed, 26 Apr 2017, Kent West wrote:
> Two identical newish Dell desktops. Configured for non-legacy, UEFI-only
> booting. No Secure-Boot or Fast Boot.
[...]
> Every other boot results in a hang at "Initializing Ramdisk"
This usually is indicative of a video driver (or some other driver)
On 4/25/17, Ric Moore wrote:
> On 04/24/2017 11:19 AM, Cindy-Sue Causey wrote:
>
>> Mine will occasionally do something like this. In my case, it gives
>> the appearance it's switching back and forth between entire cursor
>> themes. Is there a chance that's actually what's
On 4/26/17, Kent West wrote:
> Two identical newish Dell desktops. Configured for non-legacy, UEFI-only
> booting. No Secure-Boot or Fast Boot.
>
> Both fresh minimal installs of Jessie.
>
> Every other boot results in a hang at "Initializing Ramdisk" just after
> grub, requiring
On 2017-04-26, Greg Wooledge wrote:
> On Wed, Apr 26, 2017 at 10:25:10AM -0400, Ric Moore wrote:
>> On 04/26/2017 10:17 AM, Greg Wooledge wrote:
>> >On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
>> >>"ifconfig" has to be run as root.
>
>> >This is not correct, if
Eduardo M KALINOWSKI wrote on 04/26/17 16:46:
> On Qua, 26 Abr 2017, Richard Owlett wrote:
>> I would go further saying iproute2 is non-functional due to being
>> functionally
>> un-documented.
>>
>> https://manpages.debian.org/jessie/iproute2/ip.8.en.html is useless.
>>
>> Functional commands,
Two identical newish Dell desktops. Configured for non-legacy, UEFI-only
booting. No Secure-Boot or Fast Boot.
Both fresh minimal installs of Jessie.
Every other boot results in a hang at "Initializing Ramdisk" just after
grub, requiring holding the power button for 8 seconds to power off. Then
On Qua, 26 Abr 2017, Richard Owlett wrote:
I would go further saying iproute2 is non-functional due to being
functionally un-documented.
https://manpages.debian.org/jessie/iproute2/ip.8.en.html is useless.
Functional commands, for this thread's topic would be
ip -s link
or
ip -s link ls
On Wednesday 26 April 2017 15:36:36 Richard Owlett wrote:
> On 04/26/2017 07:50 AM, Darac Marjal wrote:
> > On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
> >> On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> >>> For interface statistics from ip, try "ip -s link
Lo,
On Wed, Apr 26, 2017 at 04:39:23PM +0200, alex.pad...@laposte.net wrote:
> Je dispose d'une carte nvidia nvs, la seconde sortie n'a pas été
> detectée par Arandr, quel paquet dois-je installé pour que la
> seconde sortie DVI soit active et que mon vidéoprojecteur soit
> détecté.
Essaye
Bonsoir,
Je dispose d'une carte nvidia nvs, la seconde sortie n'a pas été detectée par
Arandr, quel paquet dois-je installé pour que la seconde sortie DVI soit active
et que mon vidéoprojecteur soit détecté.
Merci beaucoup.
Alex
On 04/26/2017 07:50 AM, Darac Marjal wrote:
On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
For interface statistics from ip, try "ip -s link [interface]".
On stretch:
wooledg:~$ ip -s link eth0
Command "eth0" is
On Wed, Apr 26, 2017 at 10:25:10AM -0400, Ric Moore wrote:
> On 04/26/2017 10:17 AM, Greg Wooledge wrote:
> >On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
> >>"ifconfig" has to be run as root.
> >This is not correct, if you are just using it to view an interface rather
> >than to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
> On 04/26/2017 08:36 AM, Brian wrote:
> >On Wed 26 Apr 2017 at 07:17:11 -0500, Richard Owlett wrote:
> >
> >>On 04/25/2017 08:17 AM, Richard Owlett wrote:
> >>>On 04/24/2017 04:12 PM, Ben
On 04/26/2017 10:17 AM, Greg Wooledge wrote:
On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
"ifconfig" has to be run as root.
ric@iam:~$ sudo ifconfig
[sudo] password for ric:
enp8s0: flags=4163 mtu 1500
This is not correct, if you are just using
On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
> "ifconfig" has to be run as root.
> ric@iam:~$ sudo ifconfig
> [sudo] password for ric:
> enp8s0: flags=4163 mtu 1500
This is not correct, if you are just using it to view an interface rather
than to
On 04/26/2017 08:36 AM, Brian wrote:
On Wed 26 Apr 2017 at 07:17:11 -0500, Richard Owlett wrote:
On 04/25/2017 08:17 AM, Richard Owlett wrote:
On 04/24/2017 04:12 PM, Ben Caradoc-Davies wrote:
On 24/04/17 22:58, Richard Owlett wrote:
If there were user accessible registers with a running
On 4/26/17, Ben Finney wrote:
> Felix Dietrich writes:
>
>> What is the etiquette dealing with seemingly forgotten bug reports?
>
> You should start with a message to the bug report email address. That
> will reach both the current owner of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 26, 2017 at 01:50:15PM +0100, Darac Marjal wrote:
> On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
> >On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> >>For interface statistics from ip, try "ip -s link
Buenas
viste esta doc de zimbra?
https://wiki.zimbra.com/wiki/GAL_Sync_Account
--
Matias Mucciolo
Area de Infraestructura.
Piedras 737 C.A.B.A
SUTEBA
On Tuesday 25 April 2017 11:27:56 Lic. Manuel Salgado wrote:
> Saludos a todos:
> Aunque lo que voy a preguntar es para aplicar en Zimbra
On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
For interface statistics from ip, try "ip -s link [interface]".
On stretch:
wooledg:~$ ip -s link eth0
Command "eth0" is unknown, try "ip link help".
wooledg:~$ ip -s
On Wed 26 Apr 2017 at 07:17:11 -0500, Richard Owlett wrote:
> On 04/25/2017 08:17 AM, Richard Owlett wrote:
> >On 04/24/2017 04:12 PM, Ben Caradoc-Davies wrote:
> >>On 24/04/17 22:58, Richard Owlett wrote:
> >>>If there were user accessible registers with a running total of
>
On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> For interface statistics from ip, try "ip -s link [interface]".
On stretch:
wooledg:~$ ip -s link eth0
Command "eth0" is unknown, try "ip link help".
wooledg:~$ ip -s link dev eth0
Command "dev" is unknown, try "ip link help".
Richard Owlett:
>
> I did an install using expert mode, not selecting any GUI.
> At several points during the install I did Alt-F2 to bring up a terminal to
> attempt running ifconfig.
>
> "Command not found" was the uniform response.
> I booted the new install and attempted as root to run
On Wed, Apr 26, 2017 at 07:17:11AM -0500, Richard Owlett wrote:
On 04/25/2017 08:17 AM, Richard Owlett wrote:
On 04/24/2017 04:12 PM, Ben Caradoc-Davies wrote:
On 24/04/17 22:58, Richard Owlett wrote:
If there were user accessible registers with a running total of
uploaded/downloaded data
On 04/25/2017 08:17 AM, Richard Owlett wrote:
On 04/24/2017 04:12 PM, Ben Caradoc-Davies wrote:
On 24/04/17 22:58, Richard Owlett wrote:
If there were user accessible registers with a running total of
uploaded/downloaded data since device power on would be almost ideal
granularity.
Is
Bom dia.
Estou respondendo para a lista, pois pode interessar a mais alguem.
Qualquer pessoa que tiver uma conta na AWS pode usar meu produto
gratuitamente.
Na AWS você paga pelos serviços computacionais deles, no caso de
produtos no Market Place, você paga pela utilização do produto também,
> On Apr 26, 2017, at 3:39 AM, Tony van der Hoff wrote:
>
> Hi,
> Running Jessie, postfix/courier on my VPS. I don't often need to restart,
> which is just as well, as after a reboot, I'm unable to access mail over IMAP.
>
> It turns out, that if I run service
Hi,
Running Jessie, postfix/courier on my VPS. I don't often need to
restart, which is just as well, as after a reboot, I'm unable to access
mail over IMAP.
It turns out, that if I run service courier-imap-ssl restart and/or
service courier-imap restart, mail functionality is restored.
Felix Dietrich writes:
> What is the etiquette dealing with seemingly forgotten bug reports?
You should start with a message to the bug report email address. That
will reach both the current owner of the report, and the package
maintainer address.
> […] to have
37 matches
Mail list logo