Re: What is z3fold and do I need it? (error: /usr/sbin/mkinitramfs: 12: /etc/initramfs-tools/conf.d/local.conf: z3fold: not found)

On Fri, 04 Mar 2022, Ottavio Caruso wrote: > ~$ sudo find /lib/modules/ -iname "*z3fold*" > /lib/modules/4.19.0-17-amd64/kernel/mm/z3fold.ko > /lib/modules/4.19.0-14-amd64/kernel/mm/z3fold.ko > /lib/modules/4.19.0-8-amd64/kernel/mm/z3fold.ko > > > Then why doesn't it load up? update-initramfs

Re: OpenSSH: cause of random kex_exchange_identification errors?

On Wed, 02 Feb 2022, Vincent Lefevre wrote: > When I want to connect with SSH (ssh/scp) to some machine, I sometimes > get errors, either > > kex_exchange_identification: Connection closed by remote host > > or > > kex_exchange_identification: read: Connection reset by peer That's a very early

Re: WARNING: debian11 + bind-9.16.15 + dnssec-policy in options{} = crashes

On Mon, 16 Aug 2021, raf wrote: > If like me, you've been eagerly awaiting debian11 to > get bind-9.16.15, which finally lets you implement > DNSSEC extremely easily on debian stable, I have a > warning. And I have another: make sure your system clock is correct. DNSSEC will fail if system time

Re: missing memory and the mystery of MTRRs

On Mon, 15 Feb 2021, Andrei POPESCU wrote: > On Du, 14 feb 21, 12:22:25, Charlie Gibbs wrote: > > We had a power outage the other day, and when I tried to restart the > > machine it would get past the Grub screen, then sit there forever with > > a screen that was blank except for a blinking

Re: Missing memory and the mystery of MTRRs

On Sat, 13 Feb 2021, Charlie Gibbs wrote: > [This would probably be an FAQ if I knew the proper incantation...] Well, sorta > I realized recently that a box I've been running for a while isn't seeing > all of its installed memory. The BIOS screens indicate that 8GB is > installed, but

Re: [OT] Remote SSH (dynamic IP) without third-party server

On Fri, 31 Jul 2020, riveravaldez wrote: > Hi, to clarify: I would like to connect to a remote home-machine > (dynamic IP) through SSH session but without using a third-party > server (free or paid), just with software running in both machines. I am not sure if you'd consider a DDNS (dynamic DNS)

Re: Dúvida com ITP para novos pacotes

On Wed, 01 Jul 2020, Leandro Guimarães Faria Corcete DUTRA wrote: > 1 de jul de 2020 18:47:38 Leandro Cunha : > > > é para a mesma finalidade que a devel do idioma estrangeiro > > Exato.  Inclusive mentoria. Mentoria básica na debian-devel foi redirecionada para debian-mentors. Em português,

Re: Understanding the ThinkPad W550s keyboard

On Sun, 01 Dec 2019, Celejar wrote: > 1) Most of the function keys don't seem to have scancodes / keycodes > (evtest doesn't react in any way to their press / release). Is this a > hardware thing - they just aren't designed as keyboard keys - or a > failure of the kernel? Some of the ones that

Re: Package selection for bugreport (suspend, BIOS option, Interrupt remapping)

. That said, please make sure you have the latest version of the thinkstation c20 firmware (BIOS, etc). It is a BIOS bug to even offer to enable interrupt remapping on a non-fixed version of the chipset in the first place. -- Henrique de Moraes Holschuh

Re: fix for no ssh

On Mon, 08 Jul 2019, Andrei POPESCU wrote: > In my understanding what sysv-init does (crediting entropy over reboots) > is not secure for various reasons. Writes to /dev/urandom using dd *DOES NOT* and *NEVER HAS* credited any entropy to the pool. Which is what sysvinit (actually, initscripts)

Re: Debian Programming languages

On Sat, 25 May 2019, Kenneth Parker wrote: > As one who has been involved in "low level plumbing", since the 1970's > (including on IBM Mainframe Computers), I'm not afraid of Assembler > Language. I'm surprised, that I didn't know about Rust (package rustc). > Thanks for alerting me! Rust, the

Re: [OT] ext4 corruption (was: Re: Just had to reset/reboot again, total loss of keyboard & mouse)

On Sat, 18 May 2019, Curt wrote: > On 2019-05-18, Reco wrote: > > On Sat, May 18, 2019 at 09:16:34AM -0300, Henrique de Moraes Holschuh wrote: > >> Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4 > >> filesystems. > > > > Can you share

Re: [OT] ext4 corruption (was: Re: Just had to reset/reboot again, total loss of keyboard & mouse)

On Sat, 18 May 2019, Reco wrote: > On Sat, May 18, 2019 at 09:16:34AM -0300, Henrique de Moraes Holschuh wrote: > > Just don't use any kernel 5.1.x where x < 4: it can corrupt ext4 > > filesystems. > > Can you share a bug number please? On LKML. Just look at the ext4 pat

Re: Just had to reset/reboot again, total loss of keyboard & mouse

On Fri, 17 May 2019, Gene Heskett wrote: > The first thing I saw as it rebooted was some msgs about hid-common > This was before recovering the journal on the boot drive. That's a core component of the Linux *kernel* HID (human interface device) subsystem. You need, for a bug report: 1. the

Re: systemd+anacron breaks cron jobs?

On Mon, 03 Dec 2018, Kamil Jońca wrote: > >> Dec 03 00:23:54 alfa systemd[1]: anacron.service: State 'stop-sigterm' > >> timed out. Killing. > > See, someone or some script told systemd to stop anacron (or maybe to > > stop-and-start/restart it). THIS is causing the undesired behavior. > > Dec

Re: systemd+anacron breaks cron jobs?

On Mon, 03 Dec 2018, Kamil Jońca wrote: > 1. as "everybody" knows, in case of anacron presence, system cron jobs > are delegated to anacron. > 2. recently in Debian we have anacron.timer which also runs "cron.daily" >entry. > 3. there is a timeout in systemd services which cause to kill my

Re: SyncTeX?

On Fri, 14 Sep 2018, Glenn English wrote: > Crazy-making; it litters my screen. Anyone have a suggestion/explanation? shell completion scripts? As in the stuff in bash-completion, etc. -- Henrique Holschuh

Re: kernel: device-mapper: table: 254:1: adding target device sda1 caused an alignment inconsistency

On Sat, 28 Jul 2018, David Wright wrote: > On Sat 28 Jul 2018 at 10:57:45 (-0300), Henrique de Moraes Holschuh wrote: > > On Sat, 28 Jul 2018, Rick Thomas wrote: > > > > rbthomas@small:~$ lsblk -t > > > > NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC

Re: kernel: device-mapper: table: 254:1: adding target device sda1 caused an alignment inconsistency

On Sat, 28 Jul 2018, Rick Thomas wrote: > > rbthomas@small:~$ lsblk -t > > NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED > > RQ-SIZE RA WSAME > > sda0 4096 335539204096 5121 mq-deadline > >60 1280B > > `-sda1

Re: An introduction to Debian's topology/structure/???

On Thu, 19 Jul 2018, David Wright wrote: > While there are commands like aptitude search and aptitude why > available for such purposes, these are really designed for routine > maintenance. For your purposes, I think you need to develop a more > intimate relationship with the files in

Re: Warning: Debian/testing full-upgrade removes security packages!

On Sun, 15 Jul 2018, The Wanderer wrote: > >> be warned: Wheh you do apt full-upgrade, > > > > You're in testing: what are you "full-upgrade"-ing to and why? > > To testing, of course. Eh, I believe the meant that as "why are you using full-upgrade instead of safe-upgrade or upgrade" (depending

Re: mdraid on SSD - use scterc?

On Sun, 17 Jun 2018, Richard Hector wrote: > Should I enable it on the SSDs? Or are they not prone to failure in such > a way that it would be useful? Which SSDs? Usually one lets the SSDs try as hard as they can to recover, but they're also *MUCH* faster than HDDs at it... -- Henrique

Re: Distinguishing among [unmount, Safely Remove Drive, Eject]

On Sun, 06 May 2018, Richard Owlett wrote: > On 05/06/2018 06:23 AM, Henrique de Moraes Holschuh wrote: > > Anyway, it looks like it is giving you "unmount" when it thinks it is an > > unremovable device, and the two others when it thinks either the device > >

Re: Distinguishing among [unmount, Safely Remove Drive, Eject]

On Sat, 05 May 2018, Richard Owlett wrote: > What are the distinguishing features of unmount, Safely Remove Drive, and > Eject? Usually it goes like this: unmount: exactly what it says. Likely operates only on a single filesystem (device may have many, if it is partitioned, etc). Will flush

Re: Debian 9 t: Update Gstreamer Base plugins package to resolve a Gstreamer bug

On Sat, 05 May 2018, Liam O'Toole wrote: > On 2018-05-05, Henrique de Moraes Holschuh <h...@debian.org> wrote: > > On Fri, 04 May 2018, Dinesh Iyer wrote: > >> "You'll have to talk to whoever is providing you your older version of > >> GStreamer. They wil

Re: Debian 9 t: Update Gstreamer Base plugins package to resolve a Gstreamer bug

On Fri, 04 May 2018, Dinesh Iyer wrote: > "You'll have to talk to whoever is providing you your older version of > GStreamer. They will have to backport the fix to that old version, but it > should just cleanly apply to the older versions." > > The patch that needs to be applied is: >

Re: ACPI Error on boot

On Thu, 12 Apr 2018, Anil Duggirala wrote: > I am also getting missing firmware notices, namely, > [9.269384] ath10k_pci :03:00.0: firmware: failed to load > ath10k/pre-cal-pci-:03:00.0.bin (-2) > [9.269386] ath10k_pci :03:00.0: Direct firmware load for >

Re: ACPI Error on boot

On Thu, 12 Apr 2018, Anil Duggirala wrote: > On Mon, Apr 9, 2018, at 11:55 AM, Anil Duggirala wrote: > > I am getting an error on boot in my dual boot Win 10-Debian 9 system, > > ACPI Error: Cannot release Mutex [PATM], not acquired (20160831/ > > exmutex-393) > > ACPI Error: Method

Re: Status of Intel-related vulnerabilities and bugs?

On Tue, 10 Apr 2018, Niclas Arndt wrote: > 1. Can the latest microcode updates still in stretch-backports be > trusted to run properly by now? > https://newsroom.intel.com/wp-content/uploads/sites/11/2018/04/microcode-update-guidance.pdf Yes, these microcode updates are stable. The same might or

Re: Invalid UTF-8 byte? (was: Re: utf)

On Wed, 04 Apr 2018, to...@tuxteam.de wrote: > On Wed, Apr 04, 2018 at 08:18:23AM -0300, Henrique de Moraes Holschuh wrote: > > On Tue, 03 Apr 2018, Michael Lange wrote: > > > I believe (please anyone correct me if I am wrong) that "text" files > > > won't con

Re: utf

On Tue, 03 Apr 2018, Darac Marjal wrote: > If these things matter to you, it's better to convert from UTF-8 to Unicode, UTF-8 *is* Unicode :p What you mean is either UCS-4 or UTF-32 (which are just another encoding for Unicode). But all of them are Unicode. UTF-* are only used for Unicode

Re: Invalid UTF-8 byte? (was: Re: utf)

On Tue, 03 Apr 2018, Michael Lange wrote: > I believe (please anyone correct me if I am wrong) that "text" files > won't contain any null byte; many text editors even refuse to open such a Depends on the encoding. For ASCII, ISO-8859-* and UTF-8 (and any other modern encoding AFAIK, other than

Re: Invalid UTF-8 byte? (was: Re: utf)

On Mon, 02 Apr 2018, rhkra...@gmail.com wrote: > The wikipedia article is rather interesting, in a quick skim, I learned some > interesting things about UTF-8, especially the property of self- > synchronization. Yes, UTF-8 is a brilliant design. > I had trouble reading that large table--but if

Re: Invalid UTF-8 byte? (was: Re: utf)

On Mon, 02 Apr 2018, rhkra...@gmail.com wrote: > A few weeks ago, I was looking for a byte that, in UTF-8, would be a totally > invalid byte (not an invalid sequence of bytes). At the time, I tried some > googling, but it looked rather hopeless (maybe it was my googling that was > hopeless).

Re: Stretch kernel vulnerable to meltdown

On Thu, 15 Mar 2018, Peter Steinmetz wrote: > should be fixed wrt meltdown. But I see this > # grep -R . /sys/devices/system/cpu/vulnerabilities/ > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic > retpoline >

Re: Intel-Microcode 20180312 - Meltdown/Spectre

On Wed, 14 Mar 2018, mlnl wrote: > under Debian Stretch i have updated the Microcode from Intel > > according to the readme >

Re: PAE or not PAE?

On Mon, 12 Mar 2018, Neo wrote: > No PAE. > > For 2GB of RAM it makes no sense. You just need this on 32bit machines with > more than 4GB of RAM. You need PAE to get the NX (non-execute) protection, and also KPTI (aka Meltdown defense). Note that KPTI for i686 is a work in progress. So, it

Re: Is Debian Linux protected against the Meltdown and Spectre security flaws?

On Mon, 26 Feb 2018, Curt wrote: > What does that mean 'bugs : cpu_meltdown spectre_v1 spectre_v2 > exactly? It it is supposed to mean your processor has those defects. It does not say anything about the mitigation strategy being employed to avoid those defects. Obviously, that thing

Re: lftp breakage upcoming

On Mon, 12 Feb 2018, Jude DaShiell wrote: > If debian users can download torrents with lftp now, expect as systemd gets > upgraded systemd will break lftp and make it no longer useable. The > archlinux distribution is on the bleeding edge of a rolling release and > that's what's happened over

Re: Causes, cures and prevention of orphaned inodes?

On Mon, 05 Feb 2018, Stephen P. Molnar wrote: > I installed memtest86+ and ran it with all of the defaults. It took > over an hour, but no errors were reported. Memtest86 and memtest86+ are not always that good at finding memory errors for some reason... Try a 24h/48h test over the weekend or

Re: "Stopped (with error) /dev/dm-0"

On Mon, 05 Feb 2018, Curt wrote: > At every shutdown; looks like another oldie but goodie bug affecting > those with encrypted swap (maybe some kind or race condition, if that is > indeed the proper term). Incorrect sequencing, actually. But if this is ephemeral swap (or ephemeral *anything*),

Re: Causes, cures and prevention of orphaned inodes?

On Sun, 04 Feb 2018, Stephen P. Molnar wrote: > I am running Debian Stretch on am eight thread AMD GPU platform. > Lately, it seems if I have been plagued by surfeit of orphaned nodes. That means: 1. "unlinked" files or directories were still open when the filesystem had to be shutdown/made

Re: policy around 'wontfix' bug tag

On Mon, 05 Feb 2018, Richard Hector wrote: > On 05/02/18 00:43, Nicolas George wrote: > > Richard Hector (2018-02-05): > >> #389251 (coreutils: date's -d switch doesn't honour locale) - it's quite > >> an old one. But I found another instance in which the same claim applies: > >> > >>

Re: Frustration over Debian naming (was: Re: Meltdown fix for wheezy-backports)

On Sat, 13 Jan 2018, Jonathan Dowland wrote: > > Some people always seem to remain confused. Perhaps they have > > the same confusion with timezones, for similar reasons. > > Both are confusing. One, Debian has the possibility to improve. Yes, we could "improve". But for many of us that doesn't

Re: Debian Live USB fails; bricks the USB stick

On Wed, 08 Nov 2017, Thomas Schmitt wrote: > > dd: failed to open '/dev/sdd': Read-only file system > > What the hell ... ? > Why does dd talk of filesystems ? I'd understand if it said "Permission > denied". The superuser isn't what he used to be. Because the only error number usable for "this

Re: how to enable trim for an external encrypted SSD?

On Tue, 07 Nov 2017, Alexander V. Makartsev wrote: > TRIM will erase blocks marked as deleted beforehand even if they are not Not on any SSD that is not an utter piece of trash. TRIM marks pages as unused for the garbage collector, and that's it. On SSDs that return all-zeroes for TRIMMed

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

On Sun, 29 Oct 2017, none wrote: > So is there an example ocaml code that can trigger the bug ? Read the first referece (the INRIA ocaml bug report) throughoutly. It has been public since day one. And read all references in the updates I sent to that thread too, for good measure. It is not

Re: [OT] Breaking WPA2 by forcing nonce reuse

ld images or the updated packages with the wpa/hostapd binaries. It obviously protects you only while connected to that AP. You still want/need a device firmware update or to always use a VPN (or ssh or https, etc) when using random APs out there... --   Henrique de Moraes Holschuh <h...@debian.org>

Re: in /etc/network/interfaces: "auto" vs "allow-hotplug"

On Sat, 23 Sep 2017, Rick Thomas wrote: > I have two machines (out of a group of ten) that will not bring up > their ethernet interface at boot time if the interfaces is of type > “allow-hotplug”. When I change that to “auto” the interface comes up > at boot with no problem… ... > Anybody have

Re: Btrs vs ext4. Which one is more reliable?

On Thu, 31 Aug 2017, David Wright wrote: > "RPC portmapper replacement" needs to be shut down cleanly however > long it takes. Likewise the "Color Profiles" manager which, while Because if it didn't exit, it most likely means an NFS partition is still unmounting and you could incur data loss if

Re: No ifconfig

On Sat, 19 Aug 2017, Jonathan de Boyne Pollard wrote: > Henrique de Moraes Holschuh: > > [...] and the only reason we had to keep it around by default [...] was > > broken by GNU upstream when it took ifconfig out of the bit-rot pit hell > > and started maintaining it

Re: debian9.1 ifdown bug

On Fri, 18 Aug 2017, Toad Zhou wrote: > #ifconfig eth3 > eth3: flags=4099 mtu 1500 > inet 172.16.1.20 > > #cat /etc/network/interfaces > auto eth3 > iface eth3 inet static > address 172.16.1.16 > netmask 255.255.255.0 > > #ifdown -v eth3

Re: No ifconfig [Was: no /etc/inittab]

On Tue, 15 Aug 2017, Felix Miata wrote: > >> > Please ellaborate. Why should ifconfig be part of the base system? Indeed. It shouldn't, and it doesn't anymore. Maybe net-tools should be part of the *standard* system, but it certainly does not belong to the *base* system anymore. *base* is

Re: no /etc/inittab

On Mon, 14 Aug 2017, Joe wrote: > On Mon, 14 Aug 2017 11:21:24 -0300 > Henrique de Moraes Holschuh <h...@debian.org> wrote: > > > On Mon, 14 Aug 2017, Joe wrote: > > > up the courage to do the real thing. There was nothing fundamentally > > > wrong, but a

Re: no /etc/inittab

On Mon, 14 Aug 2017, Joe wrote: > up the courage to do the real thing. There was nothing fundamentally > wrong, but a separate /usr really is a show-stopper with systemd, and > it's nice to have a working firewall... The standard Debian initramfs is supposed to handle that, if it is not doing

Re: How to change default umask in Stretch?

On Sat, 12 Aug 2017, Jonathan de Boyne Pollard wrote: > Henrique de Moraes Holschuh: > > Note that the ideal implementation would be to inherit the umask [...] > > Actually, the ideal implementation from the GNOME point of view would be for > these programs to pass the uma

Re: How to change default umask in Stretch?

On Mon, 07 Aug 2017, Garrett R. wrote: > Does anybody know, this gnome/systemd bug of umask, it this something > that I will have to wait for Debian 10 before it is fixed? Or will > Debian 9 implement a fix when/if gnome/systemd issues a fix? It is too early to tell. It depends on how complex

Re: xfig(1) in Debian 8/Jessie

On Sun, 06 Aug 2017, John Conover wrote: > On Debian 8/Jessie, i386, do: > > xfig xxx.fig > > Then, (draw a dash-dot-dash-dot line, anyplace): > > POLYLINE drawing > > Line Style > select dash-dot-dash-dot ... > and then draw a line, anyplace > > And, it

Re: Sudden death of bluetooth headphone connectivity

On Fri, 04 Aug 2017, Mark Fletcher wrote: > suddenly stopped working. I didn't do an apt autoremove last Sunday, but > may have done one the Sunday before -- which would have been reckless The log files are at: /var/log/apt* /var/log/apt/* Failing that: /var/log/dpkg* It will list everything

Re: Fonts readability (was: Arial vs. Helvetica.)

On Thu, 03 Aug 2017, Nicolas George wrote: > Another point where the bitmap fonts beat the vectorial fonts at tiny > sizes: you usually want your vectorial fonts anti-aliased, but at tiny > sizes it hurts readability. Even worse, the anti-aliasing is done wrong: > it is done without taking gamma

Re: Arquitetura i386 para amd64

Olha, trocar um Debian de i386 para amd64 é possível via "Multiarch". Chamamos isso de "cross-grade". Mas é uma dor de cabeça que não é recomendada nem para quem é usuário avançado. Se for simples reinstalar, reinstale. Se não for, e quiser tentar um cross-grade, *FAÇA BACKUP FULL INCLUSIVE DO

Re: Darn 'beep' stoped working after installing Stretch in place of Jessie

On Tue, 01 Aug 2017, Dejan Jocic wrote: > On 01-08-17, RavenLX wrote: > > Having it work out-of-the-box would be nice. After a fresh install, I have a > > bash script I run that installs all the apps I use and configures them. > > Sometimes though, there are things that a user needs to answer.

Re: systemd autocompletion does not work

On Fri, 28 Jul 2017, Michael Biebl wrote: > Am 28.07.2017 um 06:14 schrieb Kamil Jońca: > > /etc/dbus-1/system.d/: > > > > -rw-r--r-- 1 root root 3947 Apr 29 2014 org.freedesktop.systemd-shim.conf > > Purge the

Re: Weird resolver problem in Debian 8

On Tue, 25 Jul 2017, Torbjorn Pettersson wrote: > Same result regardless of how many times I run it. Great, > but telnet, however, chooses one of the a records at "random". DNS sortlist works mostly for apps using outdated APIs. telnet in stretch has long moved to the new APIs that are

Re: video driver - new thread

On Mon, 24 Jul 2017, Greg Wooledge wrote: > On Mon, Jul 24, 2017 at 02:20:08PM +0100, Darac Marjal wrote: > > You'd need some sort of system logging daemon. Something which runs with > > the privileges necessary to write to the log file, and which can accept > > log messages from unprivileged

Intel Skylake/Kaby Lake Hyper-threading bug update

TL;DR: Intel has issued public microcode updates in 2017-07-07, fixing the hyper-threading errata on every affected processor. These updates have been included in the stable and oldstable point releases from 2017-07-22. The microcode updates in the "intel-microcode" packages with the base

Re: Problema configurar wifi Debian 9

On Wed, 19 Jul 2017, Fred Maranhão wrote: > 2017-07-18 20:44 GMT-03:00 Filipe yinyang : > > Boa noite a todos. > > Agradeço a vossa rapida resposta e a vontade em me ajudar. No entanto, mesmo > > seguindo os vossos conselhos não consegui ligar o wifi, provavelmente por > >

Re: Problema configurar wifi Debian 9

On Mon, 17 Jul 2017, Filipe yinyang wrote: > -Montei uma pen usb com debian 9 "live install" amd64 para poder fazer um > teste antes de instalar definitivamente, seguindo este link Quando for instalar definitivamente, *por favor* NÃO use a "live install", porque ela tem causado problemas quando é

Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice

On Mon, 10 Jul 2017, Rene Engelhard wrote: > On Mon, Jul 10, 2017 at 09:47:09AM -0300, Henrique de Moraes Holschuh wrote: > > On seg, 10 jul 2017, Rene Engelhard wrote: > > > On Mon, Jul 10, 2017 at 01:28:54PM +0200, Hans wrote: > > > > only once! After st

Re: WARNING: Libreoffice - Do not remove ~/.config/libreoffice

On seg, 10 jul 2017, Rene Engelhard wrote: > On Mon, Jul 10, 2017 at 01:28:54PM +0200, Hans wrote: > > only once! After stopping and restarting LO again, it will not start again. > > bt? Is that the same Java crash? See > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303 > and >

Re: Problem reserving enough space for Java object heap since stretch upgrade

On Mon, 03 Jul 2017, Adam Rosi-Kessel wrote: > This isn't on purpose and not something I've ever thought about it. It looks > like migrating an existing system from i386 to amd64 is a cumbersome and > potentially glitchy process. Is it still true that there is no foolproof and > easy way to

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

(updated perl script, it now needs the "liblist-moreutils-perl" package) On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > > This warning advisory is relevant for users of systems with the Intel > > proce

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

(updated perl script, it now needs the "liblist-moreutils-perl" package) On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > > This warning advisory is relevant for users of systems with the Intel > > proce

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

(updates, hopefully the last ones...) On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > Fast-forward a few months, and Mark Shinwell noticed the mention of a > possible fix for a microcode defect with unknown hit-ratio in the > intel-microcode package changelog. H

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

for the inconvenience. On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > Once you know your processor model name, you can check the two lists > below: > > * List of Intel processors code-named "Skylake": > http://ark.intel.com/products/codename/37572/Skylake > >

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

For the record: the email with the perl script doesn't contain malware. The "malware" alert came from an extremely badly configured system that violates every best practice in the field: it sends email to every original recipient (and not just to local users), and it FORGES its headers to look

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > This warning advisory is relevant for users of systems with the Intel > processors code-named "Skylake" and "Kaby Lake". These are: the 6th and > 7th generation Intel Core processors (desktop, embedded, mobi

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > This warning advisory is relevant for users of systems with the Intel > processors code-named "Skylake" and "Kaby Lake". These are: the 6th and > 7th generation Intel Core processors (desktop, embedded, mobi

[WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

This warning advisory is relevant for users of systems with the Intel processors code-named "Skylake" and "Kaby Lake". These are: the 6th and 7th generation Intel Core processors (desktop, embedded, mobile and HEDT), their related server processors (such as Xeon v5 and Xeon v6), as well as select

Re: Wheezy to Stretch upgrade failure

On Sat, 24 Jun 2017, Andrew wrote: > Ive tried to update a non GUI system from Wheezy to Stretch and its gone > horribly wrong. ... > Would I have been wise to upgrade it to Jessie first? Yes. The safest procedure is: 1. Update to the latest point-release of the version you have installed.

Re: Where to Report Non-Bug Problems

On Fri, 23 Jun 2017, Greg L wrote: > I wanted to report missing backgrounds (wallpaper) in Debian Stretch > stable. Which individual or email address shall I report this to? I > appreciate your help. Thank you. Since this is unrelated to software defects, and you already contacted the list

Re: quasi-SOLVED: Re: no network after jessie -> stretch

On Fri, 23 Jun 2017, D. R. Evans wrote: > Can anyone provide suggestions as to how to remove this delay? Yes. The fastest way would be to ask your network administrator for a static IP and DNS information, so that you can do static configuration. This is faster than DHCP even when everything is

Re: "no public key" warning on upgrade to stretch

On Thu, 22 Jun 2017, Charles E. Blair wrote: >When I type "apt-get upgrade" I get > this message, and things stop: > > W: There is no public key available for the following key IDs: > EF0F382A1A7B6500 > >I hope there is a simple fix. You can ignore the warning _in this specific

Re: Lançado o Debian 9 "Stretch" - GnuPG

On Wed, 21 Jun 2017, Gilberto F da Silva wrote: > On Sun, Jun 18, 2017 at 06:28:09AM -0300, Marcelo Santana wrote: > O vem a ser "curva elíptica" em se tratando de programa de > criptografia? O que seriam esses padrões melhores?

Re: Stretch

On Tue, 20 Jun 2017, Arles wrote: > Estou usando os repositórios testing e, mesmo depois de atualizar, meu > Debian continua na versão 9 Stretch. Isso é normal nessa fase de transição? Sim. Vai mudar quando alguem atualizar o base-files no unstable. -- Henrique Holschuh

Re: Preparando para atualizar o Debian 8 para o 9

On Tue, 20 Jun 2017, Thiago C. F. wrote: > Então... eu tinha adicionado este repositório através de um tutorial na > internet ensinando o que fazer depois de instalar o Debian. Agora... a > dúvida é: É realmente necessário o repositório deb-multimedia.org? Depende muito. Eu pessoalmente não

Re: Preparando para atualizar o Debian 8 para o 9

On Tue, 20 Jun 2017, Thiago C. F. wrote: > Que nada mais é arquivos do repositório "ftp.deb-mutimedia.org", que achei > visualizando pelo Synaptic. Em geral, esse repositório causa problemas para atualizações. As versões de pacote nem sempre são compatíveis, e não tem garantias que o

Re: where to submit low security vulnerability in .profile?

On Mon, 19 Jun 2017, The Wanderer wrote: > On 2017-06-19 at 11:59, Henrique de Moraes Holschuh wrote: > > On Mon, 19 Jun 2017, Greg Wooledge wrote: > >> You appear to be claiming that putting ~/bin in PATH is somehow > >> inherently unsafe. I don't agree.

Re: where to submit low security vulnerability in .profile?

On Mon, 19 Jun 2017, Greg Wooledge wrote: > You appear to be claiming that putting ~/bin in PATH is somehow inherently > unsafe. I don't agree. Under what conditions would this result in any > kind of privilege escalation? The OP was complaining that ~/bin was being *prepended* to PATH, instead

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

On Mon, 19 Jun 2017, Brian wrote: > The same experience as yours on tty1 to tty6. Except a couple of days > ago when I used nouveau.modeset=0 on GRUB's linux line and got what is > in the subject header. Kernel modeset must be enabled non-root X to work, as you found out... -- Henrique

Re: Can't install Debian 9, missing liblzo2

On Mon, 19 Jun 2017, Wellington Terumi Uemura wrote: > I'm trying to install Debian 9 from a Live version with no success, I'm Plese don't. Please install from an install image. the Live images will get fixed, but it is always safer to use them only for testing things or playing with Debian,

Re: Stretch: FontAwesome not properly installed / not working?

On Mon, 19 Jun 2017, Matthias Herrmann wrote: > When I visit the font-awesome cheat sheet [1] and copy-paste a character ... > (like , or fa-envelope []) into gnome-shell or into another > program, e.g. gedit, or thunderbird, it shows up as another character or > the box with the hexvalues in

Re: Can a US Robotics USB Softmodem be made to work on Linux?

On Thu, 15 Jun 2017, Jason wrote: > I have a U.S. Robotics USR5639 USB modem. I am wondering how hard it > is to get it to work with Linux. Using Mint 18.1. ... > Bus 001 Device 006: ID 047e:2892 Agere Systems, Inc. (Lucent) Systems Soft > Modem Look for ltmodem and linmodem. If you are very

Re: Please help me resize my ext4 file system to size > 16TB

On Tue, 13 Jun 2017, R. Ramesh wrote: > >That would be organizing your videos into N subdirectories and using new > >filesystems for some of those. Each single filesystem will be smaller > >than 16TB. > > > >If that works with your use case, you could do that now. > > Thanks. In that case, is

Re: Please help me resize my ext4 file system to size > 16TB

On Mon, 12 Jun 2017, R. Ramesh wrote: > >You implied you don't even have a backup of that data, which means you > >have exactly one chance of getting it right. This is a non-starter. ... > Let us not worry about backup. The data is just videos and not worth the > effort. They are all

Re: Please help me resize my ext4 file system to size > 16TB

On Mon, 12 Jun 2017, Ramasubramanian Ramesh wrote: > >I think you ran into this problem: > >http://blog.ronnyegner-consulting.de/2011/08/18/ext4-and-the-16-tb-limit-now-solved/ > > > >I know of no way to get resize2fs to work with partitions larger than > >16 TB, however in the blog post it's

Re: https_port

On Thu, 08 Jun 2017, Darac Marjal wrote: > On Thu, Jun 08, 2017 at 08:41:14AM -0700, Adiel Plasencia Herrera wrote: > >How to generate the certificate and the key to make a very > >basic configuration of the https connection. > > NTP doesn't use HTTPS. It uses its own port, it's own protocol and

Re: NTP.conf pool vs server

On Wed, 07 Jun 2017, Greg Wooledge wrote: > On Wed, Jun 07, 2017 at 03:54:26PM +0100, Darac Marjal wrote: > > As I understand it "server" will do name resolution once and pick an IP > > from the result. "pool" will periodically refresh the name and cycle to > > a different member of the pool. > >

Re: Oh no something has gone wrong! after reinstalling Debian and Gnome.

On Wed, 24 May 2017, Felix Miata wrote: > Once upon a time, Intel gfx did not need any firmware that was not part of a > default or minimal installation. :-( Nowadays it may actually requires BIOS/UEFI _and_ processor microcode updates as well. The BIOS/UEFI updates work around issues related to

Re: "libstdc++6:i386" package breaks "libstdc++6"

On Thu, 11 May 2017, Martin T wrote: > I need to install "openjdk-7-jre-headless:i386" package in my amd64 > Debian 8 system. However, it depends on "libstdc++6:i386" package Check the full binary package versions of libstdc++6 for i386 and amd64. They must match. apt-cache policy

  1   2   3   4   5   6   7   8   9   10   >