Re: Netgen installation problem

2022-05-24 Thread tomas
On Tue, May 24, 2022 at 02:40:09PM -0700, Gary L. Roach wrote:
> Hi all,
> 
> Operating System: Debian GNU/Linux 11
> KDE Plasma Version: 5.20.5
> KDE Frameworks Version: 5.78.0
> Qt Version: 5.15.2
> Kernel Version: 5.10.0-13-amd64
> OS Type: 64-bit
> Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
> Memory: 15.6 GiB of RAM
> Graphics Processor: AMD CAICOS
> 
> I have installed netgen from the Debian Bullseye package library. When I run
> the program I get the following error message:
> 
> /gary@debian:~/Netgen/build$ netgen//
> //NETGEN-6.2-dev//
> //Developed by Joachim Schoeberl at//
> //2010- Vienna University of Technology//
> //2006-2010 RWTH Aachen University//
> //1996-2006 Johannes Kepler University Linz//
> //Including OpenCascade geometry kernel//
> //Including MPI version 3.1//
> //Error in Tcl-Script://
> //result = couldn't load file "libgui.so": libgui.so: cannot open shared
> object file: No such file or directory//
> //
> //Make sure to set environment variable NETGENDIR to directory containing
> ng.tcl/
> 
> /
> /
> 
> /There is not ng.tcl or libgui.so on my system so it is hard to set
> NETGENDIR when I can't find the files. I used locate to try to find the file
> but no luck. Any suggestions?/

  tomas@trotzki:~$ apt-file search libgui.so
  libnglib-6.2: /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2
  libnglib-6.2: /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2.1905
  libnglib-dev: /usr/lib/x86_64-linux-gnu/netgen/libgui.so
  libsight: /usr/lib/x86_64-linux-gnu/sight/gui-0.1/libgui.so.0
  libsight: /usr/lib/x86_64-linux-gnu/sight/gui-0.1/libgui.so.0.1

Next stop seems to be to check whether libnglib-6.2 is installed in
your system and whether /usr/lib/x86_64-linux-gnu/netgen/libgui.so.6.2
is there and points to something existent, too.

Cheers
-- 
t


signature.asc
Description: PGP signature


Re: Firmware III grub

2022-05-24 Thread tomas
On Tue, May 24, 2022 at 03:16:46PM -0400, Greg Wooledge wrote:
> On Tue, May 24, 2022 at 09:07:46PM +0200, Siard wrote:
> > I accomplished the same by creating /usr/local/bin/su containing these 
> > lines:
> > 
> > #! /bin/sh
> > PATH=$PATH:/sbin:/usr/sbin
> > /bin/su
> > 
> > and making it executable.
> 
> Clever.  But the final line should be:
> 
> exec /bin/su "$@"

Good points, as ever :)

> I still prefer the /etc/default/su solution from the wiki, though.

Me too. What's more, when doing command wrappers like above, I tend
to use a new name (say, `zu') and leave the original alone. Scripts
and that (not every script says `/bin/su'). Plus a reminder to myself
that I'm using a wrapper (age and other people's systems and that).

Cheers
-- 
t


signature.asc
Description: PGP signature


Re: any good books about the (art?, economics and) science of optimizing IO performance? ...

2022-05-24 Thread Albretch Mueller
On 5/23/22, John Conover  wrote:
> . . . the problem is to write, NOT to the disk, but to the on disk cache 
> memory . . .

 and I could imagine depending on the kinds of data loads one expects
there are best practices about how to optimally make RAM, SSDs and
RAID configurations of mechanically spinning disks play together.
 That is what I am looking for, which I thought should be cultured in
these "big data" times
 thank you,
 lbrtchx



Netgen installation problem

2022-05-24 Thread Gary L. Roach

Hi all,

Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-13-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD CAICOS

I have installed netgen from the Debian Bullseye package library. When I 
run the program I get the following error message:


/gary@debian:~/Netgen/build$ netgen//
//NETGEN-6.2-dev//
//Developed by Joachim Schoeberl at//
//2010- Vienna University of Technology//
//2006-2010 RWTH Aachen University//
//1996-2006 Johannes Kepler University Linz//
//Including OpenCascade geometry kernel//
//Including MPI version 3.1//
//Error in Tcl-Script://
//result = couldn't load file "libgui.so": libgui.so: cannot open shared 
object file: No such file or directory//

//
//Make sure to set environment variable NETGENDIR to directory 
containing ng.tcl/


/
/

/There is not ng.tcl or libgui.so on my system so it is hard to set 
NETGENDIR when I can't find the files. I used locate to try to find the 
file but no luck. Any suggestions?/


/Gary R/



Re: Apache2 404

2022-05-24 Thread IL Ka
On Tue, May 24, 2022 at 10:27 PM ldmko...@yahoo.com 
wrote:

> I am still confused.  I have quadruple checked the .conf files, rechecked
> to step to create a virtual domain and still I get 404 when trying to
> access the second page of html.
>

1. Which URL do you see in your browser bar exactly?
2. What messages do you see in access.log and error.log in
/var/log/apache2/ ?



The instructions I had said allow web ports through the firewall.  It
> specifically said ufw which my system does not have.  Is there another
> firewall that might be running on my Debian 11 / Apache2 system?
>

Firewall has nothing to do with 404 in most cases: it either blocks traffic
or permits it and it doesn't change error codes.
You either do not have a firewall at all or have nftables or iptables (you
can check its state with ``iptables -L -v -n``). But again: this is not a
firewall problem.


Re: Apache2 404

2022-05-24 Thread Dan Ritter
ldmko...@yahoo.com wrote: 
>  I am still confused.  I have quadruple checked the .conf files, rechecked to 
> step to create a virtual domain and still I get 404 when trying to access the 
> second page of html.  


Please give the complete URL to both the first and second page.


> The instructions I had said allow web ports through the firewall.  It 
> specifically said ufw which my system does not have.  Is there another 
> firewall that might be running on my Debian 11 / Apache2 system?

You only need to allow web ports through your firewall if you
have a firewall between your web server and your browser.

If there is a firewall installed on your machine, this command:

sudo nft list tables

will either not be installed or come back with a blank, and this
command:

sudo iptables -L -n

will show
Chain INPUT (policy ACCEPT)
target prot opt source   destination

Chain FORWARD (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination

Let us know if you get anything else.


> The name you keep telling us is www.ldmdomain.info
> 
> That name does not exist.
> 
> If you want to use this inside your home network and nowhere
> else, you should not use ldmdomain.info. You should use the name
> of your machine, which can be found with
> 
> hostname
> 
> And make sure that other machines on your network can find that
> host; that could involve any of several different approaches.



Re: Debian desktop environment

2022-05-24 Thread Patrick Bartek
On Tue, 24 May 2022 13:27:29 +0200
Antonino Saetta  wrote:

> Hi,
> 
> After my surrender to Jessie I've thought of moving on with Stretch.
> 
> Currently I've installed it through the net, no problems at all.
> 
> So I was wondering, why am I asked to choose (or not) a GNOME desktop
> environment, other than *Debian desktop environment*?

To give you a choice of which desktop or desktops to install, or no GUI
at all. With Linux you can install and run multiple desktops, if you
want to.

> I thought that Debian is GNOME by default...

It is, but you don't have to use/install it if you don't want to.

> Also, what's the lightest desktop? Default, XFCE or LXDE...?

XFCE, LXDE, LXQt are all considered "light" desktops. Running only a
window manager (I use Openbox. There are many others.) is even lighter.

B



Re: Firmware III grub

2022-05-24 Thread Greg Wooledge
On Tue, May 24, 2022 at 09:07:46PM +0200, Siard wrote:
> I accomplished the same by creating /usr/local/bin/su containing these lines:
> 
> #! /bin/sh
> PATH=$PATH:/sbin:/usr/sbin
> /bin/su
> 
> and making it executable.

Clever.  But the final line should be:

exec /bin/su "$@"

I still prefer the /etc/default/su solution from the wiki, though.



Re: Firmware III grub

2022-05-24 Thread Siard
Hans wrote:
> There is also "su -p", which stands for "preserve". You need this, if you
> want use graphical applications as a normal user, which need root rights
> (for example wireshark or editing config files with kwrite, with owner
> "root").

I accomplished the same by creating /usr/local/bin/su containing these lines:

#! /bin/sh
PATH=$PATH:/sbin:/usr/sbin
/bin/su

and making it executable.
/usr/local/bin takes precedence over /bin/su in $PATH.
In fact, su now has its old behaviour back.



AW: Firmaware II

2022-05-24 Thread Schwibinger Michael
We do use the root terminal.

Thank You





Von: to...@tuxteam.de
Gesendet: Sonntag, 01. Mai 2022 11:24
Bis: debian-user@lists.debian.org
Betreff: Re: Firmaware II

On Sun, May 01, 2022 at 10:53:14AM +, Schwibinger Michael wrote:
> Good morning
> Thank You for help.
>
> Do we need this?
>
> We dont use WIFI
> we do connect the PC and the router with cable.

That depends on your hardware. Most Ethernet hardware
works without firmware.

> ***
>
> Short question.
>
> update-grub
> command not found
> What did we do wrong?

Are you running as root?

Cheers
--
t


Re: Firmware III grub

2022-05-24 Thread Hans
There is also "su -p", which stands for "preserve". You need this, if you want 
use graphical applications as a normal user, which need root rights (for 
example wireshark or editing config files with kwrite, with owner "root").

I remember, there was "sux" in earlier times (dunno if it was a SuSE thingi or 
in debian, too), and as far as I remember, it was a wrapper for su in X (same 
as "su -p" now). However, I strongly belive, sux is no more used any more and 
dead.

Best regards

Hans


> "su-" doesn't exist. You have to put at least one
> space between "su" and "-" for it to work.
> 
> Replying to your question: no, it is not better.
> Nor it is worse. Just another tool.
> 
> Cheers






Re: Firmware III grub

2022-05-24 Thread to...@tuxteam.de
On Tue, May 24, 2022 at 04:50:35PM +, Schwibinger Michael wrote:

[turning around the quoting order: top quoting drives
me bonkers]

> tomas wrote

> > I see. You can also do it from a normal terminal
> > by typing "sudo" before the command. You are then
> > asked for your password, then the command is executed
> > as root. In your case:
> > 
> >   sudo update-grub
> >   [asks for password]
> > 
> > But root terminal is fine too.
> 
> Isnt su- better?

"su-" doesn't exist. You have to put at least one
space between "su" and "-" for it to work.

Replying to your question: no, it is not better.
Nor it is worse. Just another tool.

Cheers
-- 
tomás


signature.asc
Description: PGP signature


AW: Firmware III grub

2022-05-24 Thread Schwibinger Michael

Isnt su- better?

Regards





Von: to...@tuxteam.de
Gesendet: Sonntag, 01. Mai 2022 13:33
Bis: Schwibinger Michael
Cc: debian-user@lists.debian.org
Betreff: Re: Firmware III grub

On Sun, May 01, 2022 at 11:49:30AM +, Schwibinger Michael wrote:
>
> Good afternoon
> Thank You
>
> I did start the root terminal.
>
> LXDE has a root terminal.

I see. You can also do it from a normal terminal
by typing "sudo" before the command. You are then
asked for your password, then the command is executed
as root. In your case:

  sudo update-grub
  [asks for password]

But root terminal is fine too.

Cheers
--
t


Re: Debian desktop environment

2022-05-24 Thread Greg Wooledge
On Tue, May 24, 2022 at 02:23:46PM +0100, Brian wrote:
>   apt install task-xfce-desktop
>   apt unstall take-gnome-desktop
>   apt unstall xfce4
>   etc

Freudian typos.



Re: Debian desktop environment

2022-05-24 Thread Brian
On Tue 24 May 2022 at 13:27:29 +0200, Antonino Saetta wrote:

> Hi,
> 
> After my surrender to Jessie I've thought of moving on with Stretch.

Careful! If you go on like this you will end up installing bullseye :).
 
> Currently I've installed it through the net, no problems at all.
> 
> So I was wondering, why am I asked to choose (or not) a GNOME desktop
> environment, other than *Debian desktop environment*?
> 
> I thought that Debian is GNOME by default...

It needn't be GNOME, but it has been for quite some time.
 
> Also, what's the lightest desktop? Default, XFCE or LXDE...?

Lightest? In terms of disk space used?

  apt install task-xfce-desktop
  apt unstall take-gnome-desktop
  apt unstall xfce4
  etc

Lool at the additional disk space to be used.

-- 
Brian.




Re: Debian desktop environment

2022-05-24 Thread Peter Ehlert



On 5/24/22 05:20, Greg Wooledge wrote:

On Tue, May 24, 2022 at 01:27:29PM +0200, Antonino Saetta wrote:

So I was wondering, why am I asked to choose (or not) a GNOME desktop
environment, other than *Debian desktop environment*?

uncheck that box, select any other Desktop you want, or None.

by trial and error I believe it is actually Gnome, the new super 
dumbed-down version.


I much prefer Mate



I thought that Debian is GNOME by default...

*sigh* It's complicated.

See, there's more than one Debian installer program, and there's more
than one IMAGE which uses the Debian installer as its core.

The "Debian desktop environment" setting is designed to choose whichever
desktop the DESIGNER OF YOUR INSTALLATION IMAGE decided should be the
default.

If you're using the official Debian netinst or DVD-1 installer image,
the default choice is GNOME.

If you're using a Debian "Live" image, the default choice is potentially
something other than GNOME.  It'll usually say in the image's filename.

If you're using something other than pure Debian, the default could be
anything at all.


Also, what's the lightest desktop? Default, XFCE or LXDE...?

I really liked tomas's answer to this.  The way you're asking this
question means you've already fallen into the trap of thinking that
it's normal and expected to install a full-blown Desktop Environment
and that you're supposed to choose one of them.

A lot of us (myself included) don't use ANY of those.  We just use a
traditional window manager, of which there are a few dozen.

If you UNSELECT all of the desktop options (including the stupid
"Debian desktop environment" choice that picks one for you)

I agree, the Stupid default is super annoying.

I believe that the "Debian desktop environment"is actually Gnome 
(Gnome3) and it really sucks.

===

BTW: The Debian Installer is the best I have ever found, with only Two 
exceptions... That default crap selection, and auto selecting all swap 
partitions on the entire system for Formatting.


end of rant



, you get
an installation which has only the Standard packages, and no graphical
environment yet.

At that point, if you know which window manager you want to use, you
can do this:

1) Check for missing firmware and video drivers.  You're already booting
to a text console, so you've bypassed the "I can't boot because
the Display Manager locks up because of missing firmware" trap.
Now you get to resolve that peacefully, without a DM trying to take
over the display at boot time.

2) sudo apt-get install xorg your-favorite-wm your-favorite-terminal 

3) startx

If startx works, then you can continue booting to a text console and using
startx to launch the GUI each time.  Or you can select a Display Manager
package and install that, if you want a GUI login.  It's up to you.

Or, of course, you're free to use a Desktop Environment if that's what
you prefer.  That's the thing about Debian: it lets you choose.






Re: Debian desktop environment

2022-05-24 Thread Peter Ehlert



On 5/24/22 04:53, Jeremy Ardley wrote:


On 24/5/22 7:27 pm, Antonino Saetta wrote:


Also, what's the lightest desktop? Default, XFCE or LXDE...?



I use Mate.  It's closest to the old gnome so no fancy crap


I am with you on that.


BTW: the mate-desktop-environment-extras is a Great enhancement
MATE Desktop Environment (extra components, metapackage)


Jeremy





Re: Initialisatie van draadloze netwerkkaarten is onstabiel

2022-05-24 Thread Bruninksbeek

Hallo Martijn,


Hartelijk dank voor je antwoord!

Ik heb ook een antwoord gekregen van Geert Stappers, maar ik heb 
besloten de verkregen antwoorden op volgorde van ontvangst te bestuderen 
én te beantwoorden, alvorens verdere stappen in de richting van een 
oplossing te zetten.


Je vermoedde dat de systeemkern geen vrije adresruimte kan vinden voor 
de draadloze netwerkkaart. Die zienswijze vond ik interessant en zo 
slecht nog niet.


Als ik echter de foutmeldingen nog eens aandachtig lees, dan lees ik in: 
'pcim_iomap_regions_request_all failed' dat de integrale IO-map niet 
verkregen werd.


Je vroeg voor welke architectuur ik Linux gebruik. Ik gebruik Linux voor 
de amd64-architectuur, dat was op te maken uit de systeemkern die ik 
vermeldde. Ach, dat kan gebeuren als je om 07:19 uur al antwoordt.


Je vroeg of ik een andere kaart gebruik die heel veel geheugenruimte 
heeft, bijvoorbeeld een grafische kaart. Nee. Ik gebruik de XFX Radeon 
HD6450 grafische kaart met 1 GB DDR3 geheugen. Op de doos staat dat de 
kaart PCI Express 2.1 gebruikt. De grafische kaart is in PCIEX16_1 
gestoken.


Je vroeg of ik heel veel RAM heb. Ik heb 16 GB aan DDR4 werkgeheugen, 
dat was ook vermeld. 16 GB is tegenwoordig niet heel veel meer. Het 
moederbord ondersteunt maximaal 128 GB.


Je stelde mij daarna twee pittige vragen. Je vroeg eerst of in het BIOS 
64-bits adressering van PCI(e)-apparaten ingeschakeld is. Daarover heb 
ik niets in het BIOS kunnen vinden.


In Advanced\PCI Subsystem Settings staat 'Above 4G Decoding' op 
Disabled. De informatie daarbij luidt: 'Enables or disables 64 bit 
capable devices to be decoded in above 4G address space (only if system 
supports 64 bit PCI decoding).'. Dit is misschien relevant, maar 
Disabled behoort tot de 'fail-safe defaults' van het moederbord. Dit was 
de enige instelling waarvan ik vond dat het in de buurt kwam van 
waarnaar je vroeg.


Je vroeg daarna of 'PCIe Resizeable BAR' aanstaat. Dat was een 
interessante vraag omdat het woord BAR ook in sommige foutmeldingen 
voorkomt en ik die foutmeldingen niet begrijp. Ik heb echter niets over 
een 'resizeable BAR' kunnen vinden in het BIOS.


Wat ik wel heb kunnen vinden is 'PCIEX16_2 4x 1x Switch' die op Auto 
staat. De functie daarvan is dat als een kaart in PCIEX1_1, PCIEX1_2 of 
PCIEX1_3 is gestoken dan krijgt PCIEX16_2 automatisch nog maar 1 lane en 
anders automatisch 4 lanes voor het overdragen van data. In plaats van 
Auto is te kiezen voor 1x of 4x. Ik zou deze instelling op 1x kunnen 
zetten.


Je schreef dat de uitvoer van lspci -vvv voor de netwerkkaart en van 
lsmem voor mij interessant zou kunnen zijn. Ik heb de uitvoer van lspci 
-vvv en van lsmem bekeken. Zie de bijlagen. Ik werd er niet veel wijzer 
van. Uit lspci -vvv bleek wel dat er een kernelmodule iwlwifi actief is 
voor de netwerkkaart.


Ik dacht dat iwlwifi firmware was. Het pakket firmware-iwlwifi geeft 
echter de volgende informatie: 'This package contains the binary 
firmware for Intel Wireless cards supported by the iwl3945, iwl4965, and 
iwlwifi drivers.'. Die zin had ik niet goed gelezen.


Je vroeg of er op 11 mei iets veranderd is, bijvoorbeeld een 
BIOS-update, wat ik zou kunnen terugdraaien. De BIOS-update vond plaats 
op 8 april 2022. Dat was het eerste wat ik deed omdat ik mij tevoren 
behoorlijk had verdiept in het moederbord en de processor. De AMD Ryzen 
5 5600X is een nieuwe processor en het BIOS had daarvoor een update 
nodig. Het moederbord is daarvoor zelfs zo gemaakt dat het BIOS 
vernieuwd kan worden zonder dat er een processor aanwezig is. Ik heb die 
functionaliteit gelukkig niet hoeven te gebruiken. Ik kon in Setup komen 
en de update met 'Asus EZ Flash 3' uitvoeren. Op 11 mei 2022 is niets 
veranderd.


Je vroeg of er misschien een probleem is met het PCIe slot zelf.  Ik 
vond dat de draadloze netwerkkaarten wel heel gemakkelijk in het 
PCIEX1_1 slot schoven. Daarom heb ik later ook het PCIEX1_3 slot 
geprobeerd. Dat maakte echter niet uit; de kaarten gingen net zo 
gemakkelijk in PCIEX1_3. Wacht eens even ... door temperatuurstijging 
kunnen materialen uitzetten ... en dan zouden slechte contacten beter 
contact kunnen maken. Goed punt, Martijn!


Je vroeg als laatste of mijn voeding nog in orde is, of er misschien 
spanningsval is tijdens een koude start. Dat is theoretisch niet uit te 
sluiten. Je vraag was voor mij aanleiding om Scott Mueller's 'Upgrading 
and Repairing PC's', 22e editie, daarop eens na te slaan. Dat boek heb 
ik namelijk. De te leveren spanningen mogen niet meer dan 5% afwijken.


Op 15 mei 2022 heb ik naar de voedingsspanningen gekeken die het BIOS 
monitort. De grootste afwijking naar beneden was toen 0,4%. Op 11 april 
2022 heb ik met s-tui alle processor-threads maximaal belast. De 
processor bleef toen stabiel. Daarom heb ik heel weinig reden om aan 
mijn voeding te twijfelen.


Het boek bleek echter ook problemen met adapterkaarten te behandelen. 
Het schoonmaken van de contacten kan helpen, 

Re: Debian desktop environment

2022-05-24 Thread Greg Wooledge
On Tue, May 24, 2022 at 01:27:29PM +0200, Antonino Saetta wrote:
> So I was wondering, why am I asked to choose (or not) a GNOME desktop
> environment, other than *Debian desktop environment*?
> 
> I thought that Debian is GNOME by default...

*sigh* It's complicated.

See, there's more than one Debian installer program, and there's more
than one IMAGE which uses the Debian installer as its core.

The "Debian desktop environment" setting is designed to choose whichever
desktop the DESIGNER OF YOUR INSTALLATION IMAGE decided should be the
default.

If you're using the official Debian netinst or DVD-1 installer image,
the default choice is GNOME.

If you're using a Debian "Live" image, the default choice is potentially
something other than GNOME.  It'll usually say in the image's filename.

If you're using something other than pure Debian, the default could be
anything at all.

> Also, what's the lightest desktop? Default, XFCE or LXDE...?

I really liked tomas's answer to this.  The way you're asking this
question means you've already fallen into the trap of thinking that
it's normal and expected to install a full-blown Desktop Environment
and that you're supposed to choose one of them.

A lot of us (myself included) don't use ANY of those.  We just use a
traditional window manager, of which there are a few dozen.

If you UNSELECT all of the desktop options (including the stupid
"Debian desktop environment" choice that picks one for you), you get
an installation which has only the Standard packages, and no graphical
environment yet.

At that point, if you know which window manager you want to use, you
can do this:

1) Check for missing firmware and video drivers.  You're already booting
   to a text console, so you've bypassed the "I can't boot because
   the Display Manager locks up because of missing firmware" trap.
   Now you get to resolve that peacefully, without a DM trying to take
   over the display at boot time.

2) sudo apt-get install xorg your-favorite-wm your-favorite-terminal 

3) startx

If startx works, then you can continue booting to a text console and using
startx to launch the GUI each time.  Or you can select a Display Manager
package and install that, if you want a GUI login.  It's up to you.

Or, of course, you're free to use a Desktop Environment if that's what
you prefer.  That's the thing about Debian: it lets you choose.



Re: Debian desktop environment

2022-05-24 Thread Jeremy Ardley


On 24/5/22 7:27 pm, Antonino Saetta wrote:


Also, what's the lightest desktop? Default, XFCE or LXDE...?



I use Mate.  It's closest to the old gnome so no fancy crap

Jeremy



OpenPGP_signature
Description: OpenPGP digital signature


Re: Debian desktop environment

2022-05-24 Thread tomas
On Tue, May 24, 2022 at 01:27:29PM +0200, Antonino Saetta wrote:
> Hi,
> 
> After my surrender to Jessie I've thought of moving on with Stretch.
> 
> Currently I've installed it through the net, no problems at all.
> 
> So I was wondering, why am I asked to choose (or not) a GNOME desktop
> environment, other than *Debian desktop environment*?
> 
> I thought that Debian is GNOME by default...
> 
> Also, what's the lightest desktop? Default, XFCE or LXDE...?

The lightest desktop is no desktop :-)

Cheers
-- 
t


signature.asc
Description: PGP signature


Debian desktop environment

2022-05-24 Thread Antonino Saetta
Hi,

After my surrender to Jessie I've thought of moving on with Stretch.

Currently I've installed it through the net, no problems at all.

So I was wondering, why am I asked to choose (or not) a GNOME desktop
environment, other than *Debian desktop environment*?

I thought that Debian is GNOME by default...

Also, what's the lightest desktop? Default, XFCE or LXDE...?

Thank you :)

PS. Here's a picture of what I mean:
https://unix.stackexchange.com/questions/444531/how-to-install-debian-without-games-office-etc


Re: [HS] MySQL: valeur par défaut [RESOLU]

2022-05-24 Thread Olivier
Merci à tous pour vos réponses !

La réponse de Dethegeek fonctionne parfaitement.
Au passage, j'ignorais que MySQL était si susceptible sur l'absence de
parenthèses.

Le lun. 23 mai 2022 à 22:57, Jean-Michel OLTRA
 a écrit :
>
>
> Bonjour,
>
>
> Le lundi 23 mai 2022, Olivier a écrit...
>
>
> > Exemple:
> > SELECT IFNULL("ABC", macolonne2) AS foo WHERE macolonne1=123
>
> Peut-être :
> select coalesce((select macolonne2 from matable where macolonne1=123),
> 'ABC');
>
> --
> jm
>



Re: Installing Jessie on VirtualBox

2022-05-24 Thread Tim Woodall

On Tue, 24 May 2022, IL Ka wrote:




RAM, disk space... and so on :/



What makes you think so? One person on this thread said he runs Bullseye on
a laptop from 2003.
Linux itself is not resource hungry, only certain applications may have
special requirements.

What is your hardware, and which apps are you going to run there?



This isn't a perfect metric but it's what I have to hand:

-rw-r--r-- 1 apt-mirror apt-mirror 34249604 May  8 16:36 
tarfiles/bullseye.i386.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 33512108 May  8 16:50 
tarfiles/bullseye.amd64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 32866580 May  8 14:56 
tarfiles/sid.i386.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 32144452 May  8 15:10 
tarfiles/sid.amd64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 31777976 May  8 17:31 
tarfiles/bullseye.arm64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 30701772 May  8 17:10 
tarfiles/bullseye.armel.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 30497140 May  8 15:52 
tarfiles/sid.arm64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 29630360 May  8 15:30 
tarfiles/sid.armel.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 29612380 May  8 18:02 
tarfiles/buster.i386.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 28989832 May 10 16:40 
tarfiles/buster.amd64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 27553280 May  8 18:51 
tarfiles/buster.arm64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 26672068 May  8 18:32 
tarfiles/buster.armel.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 26216548 May  8 19:17 
tarfiles/stretch.i386.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 25744928 May  8 19:28 
tarfiles/stretch.amd64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 24276996 May  8 20:23 
tarfiles/jessie.i386.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 24256308 May  8 20:48 
tarfiles/jessie.amd64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 24014860 May  8 19:43 
tarfiles/stretch.armel.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 23905992 May  8 20:00 
tarfiles/stretch.arm64.chroot.tar.xz
-rw-r--r-- 1 apt-mirror apt-mirror 22621460 May  8 21:03 
tarfiles/jessie.armel.chroot.tar.xz

These are the minimal systems that are truely Debian - they have all
the essential and required packages installed along with their
dependencies and nothing else at all.

Jessie is significantly smaller

Tim.



Re: Installing Jessie on VirtualBox

2022-05-24 Thread Tim Woodall

On Mon, 23 May 2022, Antonino Saetta wrote:


Hi, guys

As requested I'm breaking down which files I've used:

- For the DVD installation, I
used https://cdimage.debian.org/cdimage/archive/8.11.1/amd64/iso-dvd/


- For the CD,
https://cdimage.debian.org/cdimage/archive/8.11.1/amd64/iso-cd/

- For the NET, simply that from the first line here:
https://www.debian.org/releases/jessie/debian-installer/

I've also tried through some Live images (
https://cdimage.debian.org/mirror/cdimage/archive/8.11.0-live/amd64/iso-hybrid/,
standard and GNOME), but still the same issues as mentioned in the initial
post...

Finally I've texted VirtualBox but they claim they can't help because the
version I'm using is out of date (but it's the most recent I can use).

If I can't solve this by tomorrow, I'll look at Debian Stretch (as that's
still lighter than Bullseye) and see if I can at least  manage to work with
that...

Thanks for all the help!



Have you tried debootstrap? I have my own system for installing and I
can still install a minimal Jessie system.

I have the following in my scripts:

jessie_sources()
{
  cat 

Re: Lecteur mp3 en ligne de commande

2022-05-24 Thread Sébastien NOBILI

Bonjour,

Le 2022-05-23 16:12, Danilo Uccelli a écrit :
Je dois lire simultanément 3 pistes audio et les diffuser sur 3 cartes 
son différentes, de façon à pouvoir envoyer ces audios sur 3 canaux, du 
genre "silent party", les auditeurs ont un casque et peuvent choisir la 
langue qu'ils souhaitent. La partie diffusion vers les casques existe 
et fonctionne.


VLC, en mode graphique, peut le faire mais je n'arrive pas à trouver 
comment sélectionner la carte son en ligne de commande.
La ligne de commande est absolument nécessaire, car le démarrage doit 
se faire sans intervention humaine, on est dans un musée et les 
gardiens ne doivent pas faire autre chose que démarrer l'installation.


`mpv` devrait répondre à ton besoin.

Sébastien