Hello.
/etc/network/interfaces - as usual: "allow-hotplug eth0", "iface eth0
inet dhcp"
Systemd upgraded from 215-17+deb8u5 up to 215-17+deb8u6
The system hangs for 1m30s during boot up, network interface is down,
but can be ifup'ed manually.
Reverting ifup@.service back to deb8u5 solves t
On 01/23/17 13:52, Sam Smith wrote:
Ah yes, the docs for this model are actually screwed up. When first
released, the chipset did in fact not support anything over 8GB (it
would simply not be seen). However they updated the motherboard to
support quad core i7. That also came with 16gb support bui
On 01/14/2017 02:26 PM, Jimmy Johnson wrote:
And it still works.
I updated Sid/testing a couple days ago and retested current drivers,
"nouveau" is working with sddm okay but froze with plasma(colorful
lighting bolts). Current nvidia-legacy-304xx is working with XRender
and compositing enabled
On 01/22/2017 06:06 PM, Jimmy Johnson wrote:
I'm getting this on a few of my system while updating apt,
"Failed to fetch
copy:/var/lib/apt/lists/partial/ftp.us.debian.org_debian_dists_sid_non-free_dep11_icons-64x64.tar.gz
Hash Sum mismatch Hashes of expected file: - Filesize:1024 [weak] -
SHA
This is what i have in modules:
# List of modules that you want to include in your initramfs.
# They will be loaded at boot time in the order below.
#
# Syntax: module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
-HP Garcia
On Mon
No, but I will look.
Thanks
-HP Garcia
On Mon, 23 Jan 2017 08:16:26 +0100
deloptes wrote:
> HP Garcia wrote:
>
> > Any suggestions on how to force the kernel modules load
> > during boot? I did a Google search on this subject and I followed
> > the instruction and no luck.
>
> did you have a
Miguel González composed on 2017-01-24 00:45 (UTC+0100):
...
Is there any way to improve the performance of ext4 both in the hosting
proxmox server and the virtual machines?
Who made those SATA cables, when, and are they red? Have you tried other cables?
Subject: Re: SATA cables
https://lists
On Mon, Jan 23, 2017 at 4:04 PM, Joe wrote:
> On Mon, 23 Jan 2017 14:28:33 -0400
> francis picabia wrote:
>
> > On Mon, Jan 23, 2017 at 2:18 PM, Greg Wooledge
> > wrote:
> >
> > > On Mon, Jan 23, 2017 at 02:12:04PM -0400, francis picabia wrote:
> > > > I'm running Debian 8.6, and looking at old
Hi,
I´m running Proxmox 4.2 which is debian jessy with a software RAID of 2
Tb SATA disks of 7200 RPM in a dedicated server.
I have set it up using OVH Proxmox installer with ext4. I have
realized that another server with just one SATA disk has writes of about
140 MB/s while this server with 2
On 01/20/2017 11:35 PM, David Christensen wrote:
Looking at the data sheet for your computer:
http://www.lenovo.com/shop/americas/content/pdf/system_data/t520_tech_specs.pdf
It covers three variants:
1. ThinkPad® T520 4243 (Onsite)
2. ThinkPad® T520 4243 (Optimus) - Onsite
3. ThinkPa
On 24/01/17 09:09, to...@tuxteam.de wrote:
There should be a session file somewhere in ~/.config (sorry I have no
more details). Perhaps XFCE honors ~/.xinitrc, ~/.xsessionrc or some
of their siblings.
I use ~/.config/xfce4/xinitrc to set environment variables before XFCE
starts:
#!/bin/sh
#
On Mon, Jan 23, 2017 at 2:09 PM, wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, Jan 23, 2017 at 07:58:01PM +, der.hans wrote:
> > Am 23. Jan, 2017 schwätzte S. P. Molnar so:
> >
> > moin moin Stephen,
> >
> > >
> > >On 01/23/2017 01:38 PM, der.hans wrote:
> > >>grep PS1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 23, 2017 at 07:58:01PM +, der.hans wrote:
> Am 23. Jan, 2017 schwätzte S. P. Molnar so:
>
> moin moin Stephen,
>
> >
> >On 01/23/2017 01:38 PM, der.hans wrote:
> >>grep PS1 ~/.bashrc ~/.bash_profile ~/.profile
> >
> >Thanks for the an
On Mon, 23 Jan 2017 14:28:33 -0400
francis picabia wrote:
> On Mon, Jan 23, 2017 at 2:18 PM, Greg Wooledge
> wrote:
>
> > On Mon, Jan 23, 2017 at 02:12:04PM -0400, francis picabia wrote:
> > > I'm running Debian 8.6, and looking at old logs. I'd like to
> > > confirm
> > when
> > > the s
Am 23. Jan, 2017 schwätzte S. P. Molnar so:
moin moin Stephen,
On 01/23/2017 01:38 PM, der.hans wrote:
grep PS1 ~/.bashrc ~/.bash_profile ~/.profile
Thanks for the answers.
I thought that i had the solution. Grep showed me that ps1 was only in
.bashrc. After making a copy of .bashrc I r
On Mon, Jan 23, 2017 at 02:43:12PM -0500, S. P. Molnar wrote:
> I added PS1="\u@\h >" to the end of .bashrc and sourced the file - it
> worked, in that terminal. However, if I open a new terminal (I'm using
> xfce4-terminal) the prompt is back to the corrupted one!
Normally when you open a ter
On 01/23/2017 01:38 PM, der.hans wrote:
grep PS1 ~/.bashrc ~/.bash_profile ~/.profile
Thanks for the answers.
I thought that i had the solution. Grep showed me that ps1 was only in
.bashrc. After making a copy of .bashrc I removed the entire if ... fi
section that contained PS1.
I added
On 2017-01-23 14:12 -0400, francis picabia wrote:
> I'm running Debian 8.6, and looking at old logs. I'd like to confirm when
> the system was rebooted to invoke the newer kernel which fixed
> the Dirty COW bug. With systemd, I'm not seeing the old signs
> like the announcement of the kernel ver
Am 23. Jan, 2017 schwätzte S. P. Molnar so:
moin moin Stephen,
check for PS1 in ~/.bashrc, ~/.bash_profile and ~/.profile.
grep PS1 ~/.bashrc ~/.bash_profile ~/.profile
If you don't find it that way, check to see if any of those include
another rc file.
You can set PS1 at the bottom of ~/.bas
On 24/01/17 07:27, S. P. Molnar wrote:
I'm embarrassed to admit it. but I am completely confused.
Somehow, I don't know how I managed to reset my bash user prompt. Rather
than the default user prompt '\u@h >', it has morphed to (p4env).
I have found plenty of Google results about correcting the
On Mon, Jan 23, 2017 at 01:27:05PM -0500, S. P. Molnar wrote:
> I have found plenty of Google results about correcting thei promled,
> and, indeed export PS1='\u@\h > ' restores the prompt - that is, until I
> close that terminal. The next time I open a terminal the prompt is back
> to (p4env).
I'm embarrassed to admit it. but I am completely confused.
Somehow, I don't know how I managed to reset my bash user prompt. Rather
than the default user prompt '\u@h >', it has morphed to (p4env).
I have found plenty of Google results about correcting thei promled,
and, indeed export PS1='\u
On Mon, Jan 23, 2017 at 2:18 PM, Greg Wooledge wrote:
> On Mon, Jan 23, 2017 at 02:12:04PM -0400, francis picabia wrote:
> > I'm running Debian 8.6, and looking at old logs. I'd like to confirm
> when
> > the system was rebooted to invoke the newer kernel which fixed
> > the Dirty COW bug.
>
> l
On Mon, Jan 23, 2017 at 02:12:04PM -0400, francis picabia wrote:
> I'm running Debian 8.6, and looking at old logs. I'd like to confirm when
> the system was rebooted to invoke the newer kernel which fixed
> the Dirty COW bug.
last | grep boot
or, apparently (according to the man page):
last re
I'm running Debian 8.6, and looking at old logs. I'd like to confirm when
the system was rebooted to invoke the newer kernel which fixed
the Dirty COW bug. With systemd, I'm not seeing the old signs
like the announcement of the kernel version. If I have a complete
copy of my /var/log from last O
On Mon, Jan 23, 2017 at 12:33:55PM -0500, Tony Baldwin wrote:
> Perhaps it is these Daemons that are not doing their job(?), because
> I'll set the hostname (as root with "hostname $myhostname", or editing
> /etc/hostname, I've done both), and on reboot, it returns to (none).
Anything you set wi
On 01/23/2017 08:38 AM, Greg Wooledge wrote:
On Sun, Jan 22, 2017 at 12:48:19PM -0500, Tony Baldwin wrote:
I rent a VPS from Contabo, in Germany (as if the location were
relevant), which is still running wheezy.
Lately, when I access it (generally via ssh) the hostname appears to be
changed to
Small bit of background. Wheezy has no problem at all using the proxy.
Nor does Ubuntu, SUSE or Centos. Every Jessie install I have built has
been unable to use the proxy. It basically stops at "Hit
http://security.debian.org jessie/updates/main Translation-en" at
"100% [Waiting for headers]"
Debian unstable w/KDE, all patches applied.
When I boot the machine, I get a console rather than X. I see the
following in ~/.xsession-errors:
klauncher: Exiting on signal 15
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
On Sun, Jan 22, 2017 at 12:48:19PM -0500, Tony Baldwin wrote:
> I rent a VPS from Contabo, in Germany (as if the location were
> relevant), which is still running wheezy.
> Lately, when I access it (generally via ssh) the hostname appears to be
> changed to (none).
Edit (or create) the file /etc
Small bit of background. Wheezy has no problem at all using the proxy.
Nor does Ubuntu, SUSE or Centos. Every Jessie install I have built has
been unable to use the proxy. It basically stops at "Hit
http://security.debian.org jessie/updates/main Translation-en" at "100%
[Waiting for headers]"
Hi,
On Mon, 23 Jan 2017 08:40:32 +0100
Matthias Bodenbinder wrote:
(...)Yes, this is exactly what happens on my PC. But it has no solution.
>
> In the meantime I found a workaround. I moved /etc/cron.daily/apt out
> of the way. It looks like this script is being executed during boot
> before th
> Do you mean to suggest that you know that this bug is confirmed to exist
> in Debian and has already been reported?
Yes, that is. See here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851748
You can test it this way:
1. Move ~/.config/menus* somewhere
2. Start LXDE, no more menus.
3. I
The first thing to establish is does this bug actually exist in Debian.
That doesn't mean knowing that it is present in an upstream version that
Debian carries, it means someone has to verify the bug in person with the
installed package.
On Mon, Jan 23, 2017 at 10:44:50AM +0100, Hans wrote:
> Sear
Am Sonntag, 22. Januar 2017, 23:57:59 CET schrieb kamaraju kusumanchi:
> Update from which version to which version? What version of LXDE shows
> this bug? Can you provide a link to the kali-linux bug report?
See here:
https://bugs.kali.org/view.php?id=3822
>
> > Do the LXDE developers know of th
Si vous ne visualisez pas ce message, cliquez sur ce lien :
(http://news2.infoduchef.com/public/read_message.jsp?tsp=1485161158756&custid=22231&uid=22388015594&sig=MHOKINGANIFFOMCJ&mid=2200650159)
Vous recevez cet email car vous êtes inscrit pour recevoir les offres des
partenaires du Gro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, 2017-01-22 at 17:38 +0100, iqwue Wabv wrote:
> Hello Ulf, hello Debian,
>
> Ulf thanks for the link. It helps me! After some talking in upstream (ticket h
> ttps://github.com/hadess/iio-sensor-proxy/issues/134)
> and giving some info about t
37 matches
Mail list logo
