On 04/12/17 12:49, Jonathan Dowland wrote:
> On Fri, Dec 01, 2017 at 03:30:50PM +0100, solitone wrote:
>> On 01/12/17 15:22, Jonathan Dowland wrote:
>>> AppArmor is not enabled in current
>>> stable, so you should only hit this bug if you are using stable's
>>> thunderbird on a testing/sid system,
On 03/01/18 07:30, Brian wrote:
>> Michael Stone wrote:
There is nothing a user can do to *prevent* himself from destroying his
own files,
>> Greg Wooledge wrote:
>>> Actually, there is. It's called making a backup.
>> This is a very good point.
> What *prevents* a user from destroying
On 1/6/2018 4:06 AM, Jason wrote:
On a RasperryPi with Raspbian, I would like to create a PDF Printer to
print files to. I only know how to do this with the GUI program
system-config-printer but I don't want to install that on this
Pi. What shell command do I need to create a PDF printer on the P
On Friday 05 January 2018 22:06:22 Jason wrote:
> On a RasperryPi with Raspbian, I would like to create a PDF Printer to
> print files to. I only know how to do this with the GUI program
> system-config-printer but I don't want to install that on this
> Pi. What shell command do I need to create a
if you're in a hurry in this situation try:
apt-get remove --purge nano
problem solved?
--
CK
On a RasperryPi with Raspbian, I would like to create a PDF Printer to
print files to. I only know how to do this with the GUI program
system-config-printer but I don't want to install that on this
Pi. What shell command do I need to create a PDF printer on the Pi (or
on any Debian, for that matter
On 1/5/2018 3:25 PM, Roberto C. Sánchez wrote:
On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
When I run
sudo vipw or sudo vigr, it uses nano as the default editor. I've already
used update-alternatives to select vim as my default editor, but this
doesn't seem to work for vipw/vi
On 01/05/18 06:56, Gary Dale wrote:
> On 2018-01-03 01:59 PM, David Christensen wrote:
>> On 01/03/18 06:45, Gary Dale wrote:
>>> ... Encryption is similar in concept to compression.
>>> ... It could even reduce the space requirements.
>>
>> I'm curious -- can you cite a compressing cipher code th
On 05.01.2018 21:46, Roberto C. Sánchez wrote:
> There is essentially no functional difference between allowing only the
> EDITOR variable and any arbitrary environment variable. Allowing EDITOR
> (or PAGER, or any other thing that sets the name of a command to
> execute) through to sudo provides
On Fri 05 Jan 2018 at 21:37:16 +0100, Ulf Volmer wrote:
> On 05.01.2018 21:15, Greg Wooledge wrote:
> > On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
>
> >> sudo EDITOR=vim vipw
>
> > Defaultsenv_reset
> > Defaults:greg !env_reset
>
> That basically keeps the *whole* e
On Fri, Jan 05, 2018 at 09:37:16PM +0100, Ulf Volmer wrote:
>
> That basically keeps the *whole* environment, what is usually a security
> issue. Better solution is to keep only needed and proved environment
> variables using
>
> Defaults env_keep += "EDITOR"
>
Allowing the EDITOR variable thro
On Fri, Jan 05, 2018 at 09:37:16PM +0100, Ulf Volmer wrote:
> On 05.01.2018 21:15, Greg Wooledge wrote:
> > On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
>
> >> sudo EDITOR=vim vipw
>
> > Defaultsenv_reset
> > Defaults:greg !env_reset
>
> That basically keeps the *whole
On 05.01.2018 21:15, Greg Wooledge wrote:
> On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
>> sudo EDITOR=vim vipw
> Defaultsenv_reset
> Defaults:greg !env_reset
That basically keeps the *whole* environment, what is usually a security
issue. Better solution is to keep on
On Fri, Jan 5, 2018 at 12:42 PM, Marc Auslander wrote:
> Nicholas Geovanis writes:
>
>>On Fri, Jan 5, 2018 at 6:55 AM, wrote:
>>> (mainframes of that time had at least VM, possibly
>>> speculative prefetch).
>>
>>Is it correct to call branch prediction the same as speculative execution?
>>If so
On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
> When I run
>
> sudo vipw or sudo vigr, it uses nano as the default editor. I've already
> used update-alternatives to select vim as my default editor, but this
> doesn't seem to work for vipw/vigr.
>
> I have to do
>
> sudo EDITOR=v
On Fri, Jan 05, 2018 at 03:00:43PM -0500, John Ratliff wrote:
> I have to do
>
> sudo EDITOR=vim vipw
>
> How can I make vim the default editor for vipw/vigr. Or how can I set the
> EDITOR variable when I use sudo automatically?
By default, sudo strips all the useful variables out of your enviro
When I run
sudo vipw or sudo vigr, it uses nano as the default editor. I've already
used update-alternatives to select vim as my default editor, but this
doesn't seem to work for vipw/vigr.
I have to do
sudo EDITOR=vim vipw
How can I make vim the default editor for vipw/vigr. Or how can I s
Richard Owlett composed on 2018-01-05 09:44 (UTC-0600):
> I have 3 machines with differing problems physically accessing the
> CD/DVD drive. To install Debian I routinely use a USB connected drive
> WITHOUT any problem by using the BIOS option to select a boot device.
> The SOURCES.LIST(5) man
Nicholas Geovanis writes:
>On Fri, Jan 5, 2018 at 6:55 AM, wrote:
>> (mainframes of that time had at least VM, possibly
>> speculative prefetch).
>
>Is it correct to call branch prediction the same as speculative execution?
>If so, then "yes" they had it, but I don't honestly know if that's cor
> Is it correct to call branch prediction the same as speculative execution?
Not really: they're closely related yet different.
Stefan
>> With TLB cache and all that? Pretty impressive :)
> I am not sure about the 68010 and its separate MMU. But beginning with 68020
> there surely was memory space separation per process and cache memory in the
> CPU.
The 68020 didn't have an MMU on chip (it required a separate chip
(MC68851) if y
Leandro Noferini writes:
> I would like to change the default background of gdm login screen on my
> laptop (to put into my contacts); I looked for a solution but none of my
> findings worked: is there a way to change this background that actually
> works?
Any help?
In the meantime I installed
Hi,
Richard Owlett wrote:
> I had tried "umount /media/richard/Debian 9.1.0 i386 1", but umount objected
> to the spaces in the file name.
Use quotation marks to make the directory path a single "word"
umount "/media/richard/Debian 9.1.0 i386 1"
(It is somewhat astounding that you can mount /
On 01/05/2018 10:28 AM, bw wrote:
On Fri, 5 Jan 2018, Richard Owlett wrote:
Synaptic still returns
E: Type 'file:/home/richard/Desktop/testdvd' is not known on line 2 in source
list /etc/apt/sources.list
"Type" is probably referring to the deb or deb-src entry that is missing.
I've bee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 05, 2018 at 10:33:45AM -0600, Nicholas Geovanis wrote:
> On Fri, Jan 5, 2018 at 6:55 AM, wrote:
> > (mainframes of that time had at least VM, possibly
> > speculative prefetch).
>
> Is it correct to call branch prediction the same as spe
On Fri, Jan 5, 2018 at 6:55 AM, wrote:
> (mainframes of that time had at least VM, possibly
> speculative prefetch).
Is it correct to call branch prediction the same as speculative execution?
If so, then "yes" they had it, but I don't honestly know if that's correct.
Pipeline rewinding was neces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 05, 2018 at 10:15:45AM -0600, Richard Owlett wrote:
> On 01/05/2018 09:55 AM, Thomas Schmitt wrote:
> >Hi,
> >
> >Richard Owlett wrote:
> >>root@stretch17oct2017:/home/richard# mount /dev/sr1
> >>/home/richard/Desktop/testcd
> >>...
> >>>
On 01/05/2018 09:55 AM, Thomas Schmitt wrote:
Hi,
Richard Owlett wrote:
root@stretch17oct2017:/home/richard# mount /dev/sr1
/home/richard/Desktop/testcd
...
E: Type 'file:/home/richard/Desktop/testdvd' is not known on line 2 in
"testcd" is not the same as "testdvd".
(Copy+paste error or th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 05, 2018 at 04:39:41PM +0100, Thomas Schmitt wrote:
> Hi,
>
> to...@tuxteam.de wrote:
(thanks for this walk down the memory (pun? me?) lane.
[...]
> > > Man against hardware. Who will finally win ?
>
> > Hardware.
>
> The more we shou
Hi,
Richard Owlett wrote:
> root@stretch17oct2017:/home/richard# mount /dev/sr1
> /home/richard/Desktop/testcd
> ...
> > E: Type 'file:/home/richard/Desktop/testdvd' is not known on line 2 in
"testcd" is not the same as "testdvd".
(Copy+paste error or the cause of your problem ?)
Have a nice
I have 3 machines with differing problems physically accessing the
CD/DVD drive. To install Debian I routinely use a USB connected drive
WITHOUT any problem by using the BIOS option to select a boot device.
The SOURCES.LIST(5) man page hints that I should be able us something like
file:/me
Hi,
to...@tuxteam.de wrote:
> > > Does any of the processors in the M68K family support VM?
I wrote:
> > http://gunkies.org/wiki/MC68010
> With TLB cache and all that? Pretty impressive :)
I am not sure about the 68010 and its separate MMU. But beginning with 68020
there surely was memory spa
On 2018-01-03 01:59 PM, David Christensen wrote:
On 01/03/18 06:45, Gary Dale wrote:
On 2018-01-02 02:35 PM, Pascal Hambourg wrote:
Encryption does not require extra space (except for header and block
padding). Encrypted data have the same size of cleartext data.
+1
Encryption is similar
On Fri, Jan 05, 2018 at 09:11:53AM -0600, John Hasler wrote:
> sejobud33 writes:
> > are "melton" & "spectre" related at the ime hidden features
>
> No. The management engine is certainly a dangerous feature but this is
> orthogonal to it.
It is nice to know that we have unfixable security vulne
sejobud33 writes:
> are "melton" & "spectre" related at the ime hidden features
No. The management engine is certainly a dangerous feature but this is
orthogonal to it.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
processor_unfixable security flaws
I cannot answer these questions myself:
- are "melton" & "spectre" related at the ime hidden features
(linustorwald said it is not a bug but a function not yet
discovered/exploited | 40 flaws) ?
* Replacing the cpu should solve these 'bugs'.
- does it mean that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 05, 2018 at 02:41:57PM +0100, Thomas Schmitt wrote:
> Hi,
>
> to...@tuxteam.de wrote:
> > Does any of the processors in the M68K family support VM?
>
> They did since the early 1980s when i wondered what the advantage of an
> 68010 would
Hi,
to...@tuxteam.de wrote:
> Does any of the processors in the M68K family support VM?
They did since the early 1980s when i wondered what the advantage of an
68010 would be over an 68000 (with HP BASIC: none).
http://gunkies.org/wiki/MC68010
After all, early Sun, HP and Apollo Unix workstati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 05, 2018 at 07:39:23AM -0500, Jack Dangler wrote:
[...]
> Did this also affect Motorola chipsets? I know they haven't been
> popular in a while, but I believe they are still in use (i.e. 68000)
You can answer this question yourself:
-
On 01/04/2018 12:55 PM, The Wanderer wrote:
On 2018-01-04 at 12:30, Michael Fothergill wrote:
On 4 January 2018 at 17:22, Curt wrote:
https://arstechnica.com/gadgets/2018/01/meltdown-and-spectre-every-modern-
processor-has-unfixable-security-fladdws/U
TL;DR
Windows, Linux, and macOS h
40 matches
Mail list logo
