On Mon, Mar 15, 2021, 4:44 PM Anssi Saari wrote:
> Kenneth Parker writes:
>
> > That brings up a question: Do Debian and Devuan (Debian fork without
> SystemD) use the same Kernels?
> >
> > (And I may be able to answer my own question when I get home, as I run
> both).
>
> At least the
Victor Sudakov wrote:
>
> btrfs thinks that /dev/nvme1n1 has a btrfs:
>
> # btrfs filesystem show
> Label: none uuid: 3414ae53-f3d4-43ea-bb88-ffefc9bc86f6
> Total devices 1 FS bytes used 1.05TiB
> devid1 size 2.00TiB used 1.33TiB path /dev/nvme0n1
>
> Label: none uuid:
Andrei POPESCU wrote:
> On Lu, 15 mar 21, 17:21:39, Dan Ritter wrote:
> >
> > At last report: normal desktop Ryzens (nothing with a G suffix
> > unless it also has a PRO marking)
>
> Do you have a reliable source for the lack of ECC support in G suffix
> processors?
>
> And why would it work
On Wed, 10 Mar 2021 11:32:20 -0700
Charles Curley wrote:
> However, XFCE expects to find it, and complains when it doesn't. How
> do I convince XFCE not to look for it?
It seems that the XFCE sensors plugin is the culprit. I saw nothing in
the plugin's configuration about it, though.
--
Does
On Tue, Mar 16, 2021 at 12:08:51AM +0200, Andrei POPESCU wrote:
> On Lu, 15 mar 21, 11:19:55, Stefan Monnier wrote:
> >
> > Last I heard Debian works on the M1 already :-), but its Emacs package
> > doesn't :-(
>
> No surprise considering Emacs is itself a full OS :p
>
Yeah, but it could really
On 3/15/21 10:47 PM, Andrei POPESCU wrote:
On Lu, 15 mar 21, 20:24:56, Sven Hartge wrote:
(I still vividly remember using memmaker and manual ordering the drivers
in config.sys and autoexec.bat to shave another 2KB from the lower
memory so the IPX driver would fit so Doom would run.)
For me it
On Lu, 15 mar 21, 11:19:55, Stefan Monnier wrote:
>
> Last I heard Debian works on the M1 already :-), but its Emacs package
> doesn't :-(
No surprise considering Emacs is itself a full OS :p
(sorry, could not resist)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
On Lu, 15 mar 21, 17:21:39, Dan Ritter wrote:
>
> At last report: normal desktop Ryzens (nothing with a G suffix
> unless it also has a PRO marking)
Do you have a reliable source for the lack of ECC support in G suffix
processors?
And why would it work for PRO processors instead?
I think
On Lu, 15 mar 21, 20:24:56, Sven Hartge wrote:
>
> (I still vividly remember using memmaker and manual ordering the drivers
> in config.sys and autoexec.bat to shave another 2KB from the lower
> memory so the IPX driver would fit so Doom would run.)
For me it was Warcraft :)
And for some game
Hola,
Bé, almenys sabem que quan no funciona no s'arriba ni a executar
systemd, de manera que falla molt aviat en el procés.
El següent pas que t'aconsello es augmentar el nivell de log. Per això
hauries de tornar a editar el fitxer /etc/default/grub i posar un
"loglevel=6" a la variable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I don't know what to say. I rebooted the box, yet again, last evening. This
morning, I tried yesterday's last suggestion (a big grep of dmesg), and there
was no mention of wwan0 or eth1. I ran the others too (dmesg (with several
greps),
Anssi Saari wrote:
> Dan Ritter writes:
>
> As for the ECC support in Ryzen CPUs, as I understand it it's a bit of a
> mess. Sure the CPUs support it but if it's not validated by motherboard
> manufacturers, how do you know it actually works reliably?
... by trying it out and reporting the
On Mon, Mar 15, 2021 at 03:50:56PM -0400, Stefan Monnier wrote:
In retrospect maybe DEC and SGI should have merged and then partnered
with AMD (as you note above some of DEC's processor design team indeed
ended up at AMD on the Opteron project), but I think it would have taken
a crapload of
Dan Ritter writes:
> Intel knew that their argument was bull: they owned the market
> and needed ways of subdividing their CPUs to fit every price
> point. Turning off ECC support was one of those ways.
> That strategy started with the 80486, when they brought out a
> cheap version called the
Hi,
I am inquiring about whether you may be interested in linking to our site Tutor
Bot ( https://www.tutorhunt.com/tutor-bot/ ) from your page?
http://wiki.mynooblife.org/index.php?title=Submenu:Divers_autres
Tutor Bot contains completely free online maths games where children can
practice
Kenneth Parker writes:
> That brings up a question: Do Debian and Devuan (Debian fork without
> SystemD) use the same Kernels?
>
> (And I may be able to answer my own question when I get home, as I run both).
At least the versions look similar, 4.19 in stable and 5.10 from
backports.
>>So it was a great move on the part of AMD: cheap to implement but with
>>an enormous marketing impact.
> It had much more than a marketing impact, because x86 was a PITA for more
> than 2GB of RAM and that was getting cheap and becoming a common problem by
> 2003. Switching to opteron for 8G or
Sven Hartge wrote:
> Stefan Monnier wrote:
>
> > From a purely technical perspective, it's hard to understand how Intel
> > managed to pour so much energy into such an obviously bad idea. The
> > only explanations seem all to be linked to market strategies.
>
> This history repeats for Intel
Stefan Monnier wrote:
> From a purely technical perspective, it's hard to understand how Intel
> managed to pour so much energy into such an obviously bad idea. The
> only explanations seem all to be linked to market strategies.
This history repeats for Intel on several fronts:
Look at the
Joe wrote:
> On Mon, 15 Mar 2021 12:34:42 +0100 Sven Hartge wrote:
>> Imagine a PC with 4GB adressable memory space in 1980.
> I can. It would have cost as much as a mainframe to make full use of it.
I don't say to put it in, only to have a flat 32bit address range.
Just like the current
>> No it wouldn't, and we had it by the late '80's with the advent of
>> 68040 abd 68060 accellerator boards for the Amiga's. But that flat
>> memory model and poor production QC doomed it. Any program could make
>> a missfire and write into another programs memory space, crashing the
>> whole
On Mon, Mar 15, 2021 at 01:35:42PM -0400, Celejar wrote:
Apparently POWER is having a bit of a resurgence lately due to its
openness and non-x86ness:
https://www.osnews.com/story/133093/review-blackbird-secure-desktop-a-fully-open-source-modern-power9-workstation-without-any-proprietary-code/
On Monday 15 March 2021 12:40:51 John Hasler wrote:
> Gene writes:
> > No it wouldn't, and we had it by the late '80's with the advent of
> > 68040 abd 68060 accellerator boards for the Amiga's. But that flat
> > memory model and poor production QC doomed it. Any program could
> > make a
I guess I misremembered. After the merger they certainly *acted* as if
Compaq management was in charge.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Mon, 15 Mar 2021 12:39:10 -0400
Michael Stone wrote:
...
> On Mon, Mar 15, 2021 at 09:15:10AM +0100, Sven Hartge wrote:
> >Stefan Monnier wrote:
> >> The IA64 architecture was a resounding success in one area tho: it
> >> killed most of the competition that was coming from "above" (at least
Hello,
I'm writing to you, because I don't know precisely what package is
responsible for bug- connman?, iw?,openresolv?
I've just installed Buster with mini.iso. Due to age of my PC and small
resources I tried to make my install as slim as possible.
So I went with Openbox and decided to use
On Mon, Mar 15, 2021 at 11:55:40AM -0500, John Hasler wrote:
Michael Stone writes:
...HP bought Compaq.
Compaq bought HP and then renamed themselves HP. The name was all they
really wanted, of course.
That's a strange way to position it, since HP gave Compaq shareholders
HP shares
On Mon, Mar 15, 2021, 12:45 PM Anssi Saari wrote:
> Tixy writes:
>
> > That doesn't seem to be the standard method for the last 9 years,
> > see...
> >
> > https://lwn.net/Articles/518942/
> > https://lkml.org/lkml/2013/8/5/175
>
> Thanks.
>
> > Maybe the old ways are still enabled in Debian
Michael Stone writes:
> ...HP bought Compaq.
Compaq bought HP and then renamed themselves HP. The name was all they
really wanted, of course. HP had already spun off their instrumentation
division (the real HP) as Agilent.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
Tixy writes:
> That doesn't seem to be the standard method for the last 9 years,
> see...
>
> https://lwn.net/Articles/518942/
> https://lkml.org/lkml/2013/8/5/175
Thanks.
> Maybe the old ways are still enabled in Debian and used in some cases?
> My bullseye kernel does have the kernel config
On Mon, Mar 15, 2021 at 11:03:59AM -0400, Stefan Monnier wrote:
From a purely technical perspective, it's hard to understand how Intel
managed to pour so much energy into such an obviously bad idea.
The only explanations seem all to be linked to market strategies.
They just had too much easy
Gene writes:
> No it wouldn't, and we had it by the late '80's with the advent of
> 68040 abd 68060 accellerator boards for the Amiga's. But that flat
> memory model and poor production QC doomed it. Any program could make
> a missfire and write into another programs memory space, crashing the
>
On Sun, Mar 14, 2021 at 10:44:00AM -0500, John Hasler wrote:
The Wanderer wrote:
It caught on, and became so successful that Intel abandoned its ia64
approach and started making amd64 CPUs itself.
Which was unfortunate as the x86 architecture needed to die.
Moving to ia64 would have been
Stefan Monnier wrote:
> > There's already work in progress to port Linux mainline (and
> > consequently Debian) to the Apple M1 :)
>
> Since the M1 implements the ARM instruction set, I don't think there's
> much work to do here, indeed (most likely the hardest part is to fight
> Apple's
On Sun, Mar 14, 2021, 1:50 PM Stefan Monnier
wrote:
> > Well, nearly. Itanium Merced was 2001 [1] (althoug you wouldn't buy
> > /that/ as a private person), DEC Alpha was even 1992 [2];
>
> FWIW And MIPS was there even a bit earlier with their R4000 (tho the
> software support for it only
>> The original plan/claims was that the support for legacy i386
>> application would be "just as fast". This never materialized
>> (unsurprisingly: it's easy to make a CPU that can run efficiency several
>> slightly different instruction sets (ISA), like your average amd64 CPU which
>> can run
>> Indeed. Also, they wanted to move away from the i386 instruction set
>> so as not to be bothered by pre-existing licensing agreements with
>> AMD, and thus making sure there'd be no competing implementation. The
>> IA64 architecture was quite complex, and there are reasons to believe
>> that
In my family's shared music collection, we have a file named
'yay_for_debian-highquality.ogg'. It consists of intermixed, sped-up or
slowed-down or normal-speed clips of various people saying things like
"Debian distributions", "yay for Debian", "we all love Debian here",
"Debian is God", "Debian
On Mon, Mar 15, 2021 at 12:53:46PM +, Joe wrote:
On Mon, 15 Mar 2021 12:34:42 +0100 Sven Hartge wrote:
Imagine a PC with 4GB adressable memory space in 1980.
I can. It would have cost as much as a mainframe to make full use of it.
More. Memory was often the largest line item back then,
On Mon, Mar 15, 2021 at 10:45:15AM -0400, Stefan Monnier wrote:
> >> Another rumor I read was that IBM, when developing the first IBM PC in
> >> 1980, opted to use the 8086/8088 CPU instead of the also availble M68k
> >> CPU because the Intel one was less powerful so it would not be in
> >>
>> Another rumor I read was that IBM, when developing the first IBM PC in
>> 1980, opted to use the 8086/8088 CPU instead of the also availble M68k
>> CPU because the Intel one was less powerful so it would not be in
>> competition with the mainframes the PC was supposed to interface with
>>
Gene writes:
> That, IIRC was a new, super shiny, thing from zilog. No experience
> with it, but if it was as unreliable as the z-80, was, I'm not sorry
> it failed. The Z-80 had an instruction that swapped the
> foregrund/background register sets. But it only worked on odd hours
> of the day.
On Mon, Mar 15, 2021 at 10:02:12AM -0400, Gene Heskett wrote:
[...]
> Snerk. We all did that back in the day, Tomas. that and similar magazines
> were this 8th grade graduates electronics education. Do they still exist
> today? Retired now, so the subs expired.
Some of them:
On Monday 15 March 2021 09:53:40 to...@tuxteam.de wrote:
> On Mon, Mar 15, 2021 at 09:31:05AM -0400, Gene Heskett wrote:
> > On Monday 15 March 2021 07:05:02 to...@tuxteam.de wrote:
> > > On Mon, Mar 15, 2021 at 11:09:35AM +0100, Sven Hartge wrote:
> > >
> > > [...]
> > >
> > > > Another rumor I
On Mon, Mar 15, 2021 at 09:31:05AM -0400, Gene Heskett wrote:
> On Monday 15 March 2021 07:05:02 to...@tuxteam.de wrote:
>
> > On Mon, Mar 15, 2021 at 11:09:35AM +0100, Sven Hartge wrote:
> >
> > [...]
> >
> > > Another rumor I read was that IBM, when developing the first IBM PC
> > > in 1980,
On Monday 15 March 2021 08:53:46 Joe wrote:
> On Mon, 15 Mar 2021 12:34:42 +0100
>
> Sven Hartge wrote:
> > to...@tuxteam.de wrote:
> > > On Mon, Mar 15, 2021 at 11:09:35AM +0100, Sven Hartge wrote:
> > >> Another rumor I read was that IBM, when developing the first IBM
> > >> PC in 1980, opted
On Sun, 14 Mar 2021 21:20:39 -0400
Jude DaShiell wrote:
> Why is frobtads missing from debian repositories? The frobtads package
> makes it possible for those living outside of g.u.i. land to play tads
> games on the console.
frobtads is in Debian non-free, in Sid and Jessie:
On Lu, 15 mar 21, 09:22:26, Susmita/Rajib wrote:
>
> Thank you very, very much for all your inputs. Please put this thread
> to rest and focus instead of helping seekers who need your support. I
> have had enough information already from the post of The Wanderer.
Lengthy, more or less offtopic
On Monday 15 March 2021 07:05:02 to...@tuxteam.de wrote:
> On Mon, Mar 15, 2021 at 11:09:35AM +0100, Sven Hartge wrote:
>
> [...]
>
> > Another rumor I read was that IBM, when developing the first IBM PC
> > in 1980, opted to use the 8086/8088 CPU instead of the also availble
> > M68k CPU because
On Mon, 15 Mar 2021 12:34:42 +0100
Sven Hartge wrote:
> to...@tuxteam.de wrote:
> > On Mon, Mar 15, 2021 at 11:09:35AM +0100, Sven Hartge wrote:
>
> >> Another rumor I read was that IBM, when developing the first IBM PC
> >> in 1980, opted to use the 8086/8088 CPU instead of the also
> >>
>
>
> No stupid memory segmentation,
>
IMHO segmentation was a good idea originally.
You could have separate segments for code and data and since 286 it is
possible to protect them (AFAIK segments were also used to separate
user-space and kernel-space)
But with the advent of virtual memory (386),
On Mon, Mar 15, 2021 at 12:34:42PM +0100, Sven Hartge wrote:
[...]
> Having had a 68k would have been awesome. No stupid memory segmentation,
So were Z8000, NS32K and many others. The horrible segmentation thing on
the '86 were the tribute to backward compatibility, which is the price
you pay
to...@tuxteam.de wrote:
> On Mon, Mar 15, 2021 at 11:09:35AM +0100, Sven Hartge wrote:
>> Another rumor I read was that IBM, when developing the first IBM PC
>> in 1980, opted to use the 8086/8088 CPU instead of the also availble
>> M68k CPU because the Intel one was less powerful so it would not
On Mon, Mar 15, 2021 at 11:09:35AM +0100, Sven Hartge wrote:
[...]
> Another rumor I read was that IBM, when developing the first IBM PC in
> 1980, opted to use the 8086/8088 CPU instead of the also availble M68k
> CPU because the Intel one was less powerful so it would not be in
> competition
Hola Jordi,
De nou, moltes gràcies pel teu temps.
> Entenc que això és la sortida de dmesg d'una arrencada que ha funcionat
> correctament.
Efectivament, és la sortida d'una arrencada que ha funcionat
correctament.
> Amb el canvi aquest del grub el proper cop que l'ordinador no s'engegui
>
Susmita/Rajib wrote:
> May be, Debian should make a summary of all the information collected
> from here and post an article on its page for a pre-emptive
> clarification on the flavours that Debian is available in, and not let
> the information accumulated here go waste.
Wikipedia has quite a
to...@tuxteam.de wrote:
> On Mon, Mar 15, 2021 at 09:15:10AM +0100, Sven Hartge wrote:
>> For the others: they where either on board from the start (like HP),
>> where already dead (like DEC/Compaq) or slipping into the embedded
>> market (like MIPS).
> MIPS had its chance to become the unified
On Mon, Mar 15, 2021 at 10:54:26AM +0200, Andrei POPESCU wrote:
[...]
> I'm better at asynchronous as well, but still find instant messaging to
> have it's uses [...]
> And then there's group chats. There's a reason IRC still exists ;)
Agreed. Tools, jobs and all that :)
Cheers
- t
On Mon, Mar 15, 2021 at 09:15:10AM +0100, Sven Hartge wrote:
[...]
> For the others: they where either on board from the start (like HP),
> where already dead (like DEC/Compaq) or slipping into the embedded
> market (like MIPS).
MIPS had its chance to become the unified architecture for
On Du, 14 mar 21, 14:49:03, Joe wrote:
> On Sun, 14 Mar 2021 13:23:17 +0100
> wrote:
>
> > On Sun, Mar 14, 2021 at 02:08:34PM +0200, Andrei POPESCU wrote:
> > > On Du, 14 mar 21, 12:19:34, to...@tuxteam.de wrote:
> >
> > [...]
> > > > in the first place, I'm not the target audience for
On Du, 14 mar 21, 15:17:39, Stefan Monnier wrote:
>
> The original plan/claims was that the support for legacy i386
> application would be "just as fast". This never materialized
> (unsurprisingly: it's easy to make a CPU that can run efficiency several
> slightly different instruction sets
On Du, 14 mar 21, 16:09:59, jacky cheung wrote:
> Hi
>
> Im using the Debian live version non free
> How can I change my user@debian on terminal to myname@debian. Im using for
> my education purpose.
Do you want to change your user name for the live system or do you
simply want change the
Stefan Monnier wrote:
>> Note: when IA64 was designed (starting in 1994 at HP) we where nowhere
>> near the limits of the 32bit i386 architecture with RAM and frequency,
>> so it made sense, somewhat.
> Indeed. Also, they wanted to move away from the i386 instruction set
> so as not to be
Hola Jordi,
> Pot ser que tinguis el GRUB configurat amb "quiet" i/o "splash" ?? Si
> és així ho podries modificar per poder veure el que s'imprimeix a la
> pantalla quan l'ordinador es congela.
>
> Bàsicament hauries de editar el fitxer /etc/default/grub i modificar
> una línea que dirá algo
TL-DR.
On 3/14/2021 4:54 PM, pe...@easthope.ca wrote:
From: "Alexander V. Makartsev"
Date: Sun, 14 Mar 2021 11:41:47 +0500
But it wasn't creating a device with chosen name anywhere under "/dev" or
"/dev/net/".
I believe, "/dev/net/tun" device is created when "tun" kernel module is
inserted.
65 matches
Mail list logo
