Outil de surveillance et d'alerte des logs

[Olivier]

Bonjour,

Je recherche un logiciel installable sur des serveurs Debian (Buster,
Stretch, Jessie, ...) opérant comme suit:

- lecture en temps réel de fichiers de logs
- déclenchement de scripts personnalisés en cas d'occurrence d'événements
matérialisés par la présence d'expressions dans les fichiers de logs
surveillés.

Que conseillez-vous ?

Slts

Re: Non-free firmware [was: Debian install Question]

[David Wright]

On Tue 02 Mar 2021 at 23:29:15 (+), Brian wrote:
> On Tue 02 Mar 2021 at 16:19:45 -0500, rhkra...@gmail.com wrote:
> > On Tuesday, March 02, 2021 02:55:08 PM Brian wrote:
> > > On Mon 01 Mar 2021 at 08:13:13 -0500, rhkra...@gmail.com wrote:
> > > > On Sunday, February 28, 2021 12:03:31 PM Celejar wrote:
> > > > > "Many wireless network cards (and even some wired ones) require
> > > > > non-free firmware to function properly. This firmware is not included
> > > > > in the standard installation images, due to Debian's free software
> > > > > ideals. If the network hardware your installation will rely upon
> > > > > requires such firmware, you may consider using the alternate non-free
> > > > > installation images available here."
> > > > 
> > > > +1
> > > 
> > > "+1" for what? Advertising each and every non-Debian installer that
> > > comes along and is uploaded to unofficial?

I was under the impression that "The Debian Images Team is a small
team of people working on creating, testing and distributing Debian
images for [us]", whereas you seem to be describing something like
a wiki where any Tom, Dick or Harry dumps their cobbled together
installer.

> > No.  Providing a reasonable explanatory text about why some other installer 
> > may be required and a link to a place where you can find one or more.
> 
> My installer is aimed at users with an adapter that uses the p54usb
> driver. It requires firmware that needs to be extracted from the device
> and there aren't any such files in the non-free archive. I imagine there
> are other similar devices.
> 
> I can easlily provide explanatory text about why my installer is needed
> and why it would benefit users. Would it be ok to have it in unofficial
> as a non-Debian installer?

Extracting firmware from the device itself is something I've never had
to do, and wouldn't know where to get started. That might be the sort
of process to describe in the Firmware wiki, under "Location of
firmware files".

Having extracted it, the "naive" user might then follow the
instructions in the Installation Guide, of course, and then wonder
why the d-i wouldn't find and load it.

Cheers,
David.

Re: Installation problems

[David Wright]

On Tue 02 Mar 2021 at 15:42:27 (-0600), Richard Owlett wrote:
> On 03/02/2021 02:31 PM, Brian wrote:
> > On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:
> > 
> > > I've one fine machine running i386 flavor of Debian 9.13 .
> > > I've wish to install 64 bit flavor on a second machine.
> > > debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.
> > > 
> > > I've a couple of 8GB flash drives which have served as installation media 
> > > in
> > > past. IIRC I could use gparted to wipe them before using dd to copy the 
> > > iso
> > > to the entire device.
> > 
> > You do not need gparted to wipe them. Just write the ISO there with dd
> > or cp.
> 
> DUH!
> I now have a minimal system installed.
> I had forgotten that the installer doesn't recognize the USB device
> T-Mobile provides to connect to the cell network. They sell it as a
> WiFi Hotspot but I use it essentially as an old fashioned modem. I
> usually do installs from DVD1 of the set. After an install everything
> "Just works" ;/
> 
> Any one know exactly what I need to add that would normally just be
> silently installed. I just took it as part of "universal" in USB.

Have you used your other system with that same device? If so, it will
presumably have the necessary firmware installed on it. Just install
the same packages; you might even have copies of them already if you
cache your downloads. (They should be Architecture: all.)

On Wed 03 Mar 2021 at 09:47:02 (+1100), Keith Bainbridge wrote:
> On 3/3/21 07:31, Brian wrote:
> > Just write the ISO there with dd
> 
> +1   I proved my back-up worked one day by dd of=sda
> 
> ignore cp in this scenario, PLEASE.

I don't know about anyone else, but I've got in the habit of typing:

# fdisk -l /dev/sdX

then ↑ to recall the line, overtyping it to read:

# dd bs=512 of=/dev/sdX

before finally adding if=… to the end of the line.
It seems to make mistakes less likely to happen.
(Add sudo to taste.)

Cheers,
David.

Re: Non-free firmware [was: Debian install Question]

[mick crane]

On 2021-03-02 23:29, Brian wrote:

On Tue 02 Mar 2021 at 16:19:45 -0500, rhkra...@gmail.com wrote:


On Tuesday, March 02, 2021 02:55:08 PM Brian wrote:
> On Mon 01 Mar 2021 at 08:13:13 -0500, rhkra...@gmail.com wrote:
> > On Sunday, February 28, 2021 12:03:31 PM Celejar wrote:
> > > "Many wireless network cards (and even some wired ones) require
> > > non-free firmware to function properly. This firmware is not included
> > > in the standard installation images, due to Debian's free software
> > > ideals. If the network hardware your installation will rely upon
> > > requires such firmware, you may consider using the alternate non-free
> > > installation images available here."
> >
> > +1
>
> "+1" for what? Advertising each and every non-Debian installer that
> comes along and is uploaded to unofficial?

No.  Providing a reasonable explanatory text about why some other 
installer

may be required and a link to a place where you can find one or more.


My installer is aimed at users with an adapter that uses the p54usb
driver. It requires firmware that needs to be extracted from the device
and there aren't any such files in the non-free archive. I imagine 
there

are other similar devices.

I can easlily provide explanatory text about why my installer is needed
and why it would benefit users. Would it be ok to have it in unofficial
as a non-Debian installer?

Just a thought!


The suggestion somebody made of having a tethered phone plugged into USB 
in case non-free drivers are required for network after installation 
seemed like a good one.


mick

--
Key ID4BFEBB31

Re: Bullseye - no sound

[David Wright]

On Wed 03 Mar 2021 at 04:57:59 (+0300), IL Ka wrote:
> > $ pacmd list-sinks
> > 2 sink(s) available.
> 
> pulseaudio is aware of both of your soundcards (although one is physically
> muted).
> Which software reports "No output or input devices found"?
> 
> Since both devices are connected via alsa driver, you may try to use "$
> alsamixer", make sure it is not muted on alsa level, and then run "$
> pavucontrol" and move the volume bar to see if it produces any sound.
> 
> But I am not pulseaudio expert, so let's wait for someone who has more
> experience

The OP has two sound cards, and the index 0 (usually the default) card
is the HDMI output, unlikely to be connected to the speakers.

So try   alsamixer -c 1   to use the other card. Then check for
muting (m toggles), and use arrows to navigate and change volume.
Depending on the source, you might need several turned up, eg
Master, Speaker, PCM, Line, CD, etc.

I have little experience with pulseaudio so far.

Cheers,
David.

Re: Bullseye - no sound

[IL Ka]

> $ pacmd list-sinks
> 2 sink(s) available.
>

pulseaudio is aware of both of your soundcards (although one is physically
muted).
Which software reports "No output or input devices found"?

Since both devices are connected via alsa driver, you may try to use "$
alsamixer", make sure it is not muted on alsa level, and then run "$
pavucontrol" and move the volume bar to see if it produces any sound.

But I am not pulseaudio expert, so let's wait for someone who has more
experience

Re: Installation problems

[Richard Owlett]

On 03/02/2021 07:29 PM, Richard Owlett wrote:

On 03/02/2021 04:13 PM, Andrew M.A. Cater wrote:

On Tue, Mar 02, 2021 at 03:42:27PM -0600, Richard Owlett wrote:

On 03/02/2021 02:31 PM, Brian wrote:

On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:


I've one fine machine running i386 flavor of Debian 9.13 .
I've wish to install 64 bit flavor on a second machine.
debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.

I've a couple of 8GB flash drives which have served as installation 
media in
past. IIRC I could use gparted to wipe them before using dd to copy 
the iso

to the entire device.


You do not need gparted to wipe them. Just write the ISO there with dd
or cp.



DUH!
I now have a minimal system installed.
I had forgotten that the installer doesn't recognize the USB device 
T-Mobile
provides to connect to the cell network. They sell it as a WiFi 
Hotspot but
I use it essentially as an old fashioned modem. I usually do installs 
from

DVD1 of the set. After an install everything "Just works" ;/

Any one know exactly what I need to add that would normally just be 
silently

installed. I just took it as part of "universal" in USB.

Thanks


What do lspci and lsusb report respectively? It's quite possible that you
might need non-free firmware.



The winner is
lsusb
Bus 002 Device 008: ID 1bbb:0195 T & A Mobile Phones

Non-free is enabled in sources.list of my working system.
How do I identify the crucial piece of software?


Just checked Synaptic on my running system.
I have *NO* non-free-firmware installed.

Re: Installation problems

[Richard Owlett]

On 03/02/2021 04:13 PM, Andrew M.A. Cater wrote:

On Tue, Mar 02, 2021 at 03:42:27PM -0600, Richard Owlett wrote:

On 03/02/2021 02:31 PM, Brian wrote:

On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:


I've one fine machine running i386 flavor of Debian 9.13 .
I've wish to install 64 bit flavor on a second machine.
debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.

I've a couple of 8GB flash drives which have served as installation media in
past. IIRC I could use gparted to wipe them before using dd to copy the iso
to the entire device.


You do not need gparted to wipe them. Just write the ISO there with dd
or cp.



DUH!
I now have a minimal system installed.
I had forgotten that the installer doesn't recognize the USB device T-Mobile
provides to connect to the cell network. They sell it as a WiFi Hotspot but
I use it essentially as an old fashioned modem. I usually do installs from
DVD1 of the set. After an install everything "Just works" ;/

Any one know exactly what I need to add that would normally just be silently
installed. I just took it as part of "universal" in USB.

Thanks


What do lspci and lsusb report respectively? It's quite possible that you
might need non-free firmware.



The winner is
lsusb
Bus 002 Device 008: ID 1bbb:0195 T & A Mobile Phones

Non-free is enabled in sources.list of my working system.
How do I identify the crucial piece of software?

Re: Bullseye - no sound

[Peter Hillier-Brook]

On 03/03/2021 01:13, IL Ka wrote:
> Hi.
> 
> Running Bullseye on an Acer Aspire 5 I have no sound - "No output or
> input devices found"
> 
> 
> Is it an output of pulseaudio? 
> If you run "$ pavucontrol" (Pulse Audio control), or "$ pacmd
> list-sinks", what do you see?
>  
$ pacmd list-sinks
2 sink(s) available.
index: 0
name: 
driver: 
flags: HARDWARE DECIBEL_VOLUME LATENCY FLAT_VOLUME DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 9030
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536
/ 100% / 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 0
configured latency: 0.00 ms; range is 0.50 .. 1999.82 ms
card: 1 
module: 7
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "HDMI 0"
alsa.id = "HDMI 0"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "3"
alsa.card = "0"
alsa.card_name = "HDA Intel HDMI"
alsa.long_card_name = "HDA Intel HDMI at 0xf7914000 irq 32"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:03.0"
sysfs.path = "/devices/pci:00/:00:03.0/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "0c0c"
device.product.name = "Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller"
device.form_factor = "internal"
device.string = "hdmi:0"
device.buffering.buffer_size = "352768"
device.buffering.fragment_size = "176384"
device.access_mode = "mmap+timer"
device.profile.name = "hdmi-stereo"
device.profile.description = "Digital Stereo (HDMI)"
device.description = "Built-in Audio Digital Stereo (HDMI)"
alsa.mixer_name = "Intel Haswell HDMI"
alsa.components = "HDA:80862807,80860101,0010"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900,
latency offset 0 usec, available: yes)
properties:
device.icon_name = "video-display"
device.product.name = "DELL U2520D"
active port: 
  * index: 1
name: 
driver: 
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME
LATENCY FLAT_VOLUME DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 9039
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536
/ 100% / 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 2
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 0
linked by: 0
configured latency: 0.00 ms; range is 0.50 .. 2000.00 ms
card: 3 
module: 9
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC887-VD Analog"
alsa.id = "ALC887-VD Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "1"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xf791 irq 33"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "8ca0"
device.product.name = "9 Series Chipset Family HD Audio
Controller"
device.form_factor = "internal"
  

Re: Bullseye - no sound

[IL Ka]

Hi.

Running Bullseye on an Acer Aspire 5 I have no sound - "No output or
> input devices found"
>

Is it an output of pulseaudio?
If you run "$ pavucontrol" (Pulse Audio control), or "$ pacmd list-sinks",
what do you see?

Google earth pro only works as root

[Jeremy Ardley]

I've installed google-earth-pro-stable_current_amd64.deb on my debian system

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

lspci -v | grep VGA
09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos PRO [Radeon HD 7450] (prog-if 00 [VGA controller])

The problem is Google Earth Pro will run just fine when started sudo but 
as a normal user it gives a message


"Unknown Graphics Card"

And proceeds to show a broken set of panes that I can't use.

I assume the problem is permissions and has nothing to do with the 
driver installed?


Any suggestions?


--
Jeremy



OpenPGP_signature
Description: OpenPGP digital signature

Bullseye - no sound

[Peter Hillier-Brook]

Running Bullseye on an Acer Aspire 5 I have no sound - "No output or
input devices found"

Available controllers revealed by lspci are as follows:

00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio
Controller

01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio
Controller (rev a1)

Anyone else with this problem, or a solution will be welcomed to my
Christmas card list.

Thanks in advance.

Peter HB

Re: Non-free firmware [was: Debian install Question]

[Brian]

On Tue 02 Mar 2021 at 16:19:45 -0500, rhkra...@gmail.com wrote:

> On Tuesday, March 02, 2021 02:55:08 PM Brian wrote:
> > On Mon 01 Mar 2021 at 08:13:13 -0500, rhkra...@gmail.com wrote:
> > > On Sunday, February 28, 2021 12:03:31 PM Celejar wrote:
> > > > "Many wireless network cards (and even some wired ones) require
> > > > non-free firmware to function properly. This firmware is not included
> > > > in the standard installation images, due to Debian's free software
> > > > ideals. If the network hardware your installation will rely upon
> > > > requires such firmware, you may consider using the alternate non-free
> > > > installation images available here."
> > > 
> > > +1
> > 
> > "+1" for what? Advertising each and every non-Debian installer that
> > comes along and is uploaded to unofficial?
> 
> No.  Providing a reasonable explanatory text about why some other installer 
> may be required and a link to a place where you can find one or more.

My installer is aimed at users with an adapter that uses the p54usb
driver. It requires firmware that needs to be extracted from the device
and there aren't any such files in the non-free archive. I imagine there
are other similar devices.

I can easlily provide explanatory text about why my installer is needed
and why it would benefit users. Would it be ok to have it in unofficial
as a non-Debian installer?

Just a thought!

-- 
Brian.

Re: Installation problems

[Brian]

On Tue 02 Mar 2021 at 22:21:42 +0100, to...@tuxteam.de wrote:

> On Tue, Mar 02, 2021 at 01:16:41PM -0800, Weaver wrote:
> > On 03-03-2021 06:31, Brian wrote:
> > > On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:
> > > 
> > >> I've one fine machine running i386 flavor of Debian 9.13 .
> > >> I've wish to install 64 bit flavor on a second machine.
> > >> debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.
> > >>
> > >> I've a couple of 8GB flash drives which have served as installation 
> > >> media in
> > >> past. IIRC I could use gparted to wipe them before using dd to copy the 
> > >> iso
> > >> to the entire device.
> > 
> >  I use GParted to wipe them.
> > On too many occasions I've had the installation complaining about
> > writing to `dirty' media, and using GParted beforehand always stops
> > that.
> > Cheers!
> 
> Hm. dd won't complain. It will overwrite the partition table and the
> rest. There's nothing magical about the partition table, it just sits
> in the first block(s) of the device.
> 
> Can you remember which program complained and how?

I have never had an occasion (and I've done it often enough) when
'cp ISO /dev/sdX' has failed or issued a warning. It simply gets on
with the job of writing to the medium and obliterating the existing
contents.

-- 
Brian.

Re: Installation problems

[Keith Bainbridge]

On 3/3/21 07:31, Brian wrote:

Just write the ISO there with dd



+1   I proved my back-up worked one day by dd of=/dev/sda   maybe

ignore cp in this scenario, PLEASE.

--
Keith Bainbridge

ke1thozgro...@gmx.com

Re: Installation problems

[Keith Bainbridge]

On 3/3/21 08:42, Richard Owlett wrote:


Any one know exactly what I need to add that would normally just be
silently installed. I just took it as part of "universal" in USB.



I'd suggest using a live non-free ISO and then install any necessary
drivers - downloaded to a device connected to the net.


--
Keith Bainbridge

ke1thozgro...@gmx.com

Re: Installation problems

[Keith Bainbridge]

On 3/3/21 07:31, Brian wrote:

Just write the ISO there with dd



+1   I proved my back-up worked one day by dd of=sda

ignore cp in this scenario, PLEASE.

--
Keith Bainbridge

ke1thozgro...@gmx.com

Re: Installation problems

[Andrew M.A. Cater]

On Tue, Mar 02, 2021 at 03:42:27PM -0600, Richard Owlett wrote:
> On 03/02/2021 02:31 PM, Brian wrote:
> > On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:
> > 
> > > I've one fine machine running i386 flavor of Debian 9.13 .
> > > I've wish to install 64 bit flavor on a second machine.
> > > debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.
> > > 
> > > I've a couple of 8GB flash drives which have served as installation media 
> > > in
> > > past. IIRC I could use gparted to wipe them before using dd to copy the 
> > > iso
> > > to the entire device.
> > 
> > You do not need gparted to wipe them. Just write the ISO there with dd
> > or cp.
> > 
> 
> DUH!
> I now have a minimal system installed.
> I had forgotten that the installer doesn't recognize the USB device T-Mobile
> provides to connect to the cell network. They sell it as a WiFi Hotspot but
> I use it essentially as an old fashioned modem. I usually do installs from
> DVD1 of the set. After an install everything "Just works" ;/
> 
> Any one know exactly what I need to add that would normally just be silently
> installed. I just took it as part of "universal" in USB.
> 
> Thanks
> 
What do lspci and lsusb report respectively? It's quite possible that you 
might need non-free firmware.

All the very best,

Andy C



> 
> 

Re: Installation problems

[Richard Owlett]

On 03/02/2021 02:31 PM, Brian wrote:

On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:


I've one fine machine running i386 flavor of Debian 9.13 .
I've wish to install 64 bit flavor on a second machine.
debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.

I've a couple of 8GB flash drives which have served as installation media in
past. IIRC I could use gparted to wipe them before using dd to copy the iso
to the entire device.


You do not need gparted to wipe them. Just write the ISO there with dd
or cp.



DUH!
I now have a minimal system installed.
I had forgotten that the installer doesn't recognize the USB device 
T-Mobile provides to connect to the cell network. They sell it as a WiFi 
Hotspot but I use it essentially as an old fashioned modem. I usually do 
installs from DVD1 of the set. After an install everything "Just works" ;/


Any one know exactly what I need to add that would normally just be 
silently installed. I just took it as part of "universal" in USB.


Thanks

Re: Installation problems

[tomas]

On Tue, Mar 02, 2021 at 01:16:41PM -0800, Weaver wrote:
> On 03-03-2021 06:31, Brian wrote:
> > On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:
> > 
> >> I've one fine machine running i386 flavor of Debian 9.13 .
> >> I've wish to install 64 bit flavor on a second machine.
> >> debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.
> >>
> >> I've a couple of 8GB flash drives which have served as installation media 
> >> in
> >> past. IIRC I could use gparted to wipe them before using dd to copy the iso
> >> to the entire device.
> 
>  I use GParted to wipe them.
> On too many occasions I've had the installation complaining about
> writing to `dirty' media, and using GParted beforehand always stops
> that.
> Cheers!

Hm. dd won't complain. It will overwrite the partition table and the
rest. There's nothing magical about the partition table, it just sits
in the first block(s) of the device.

Can you remember which program complained and how?

Cheers
 - t


signature.asc
Description: Digital signature

Re: Non-free firmware [was: Debian install Question]

[rhkramer]

On Tuesday, March 02, 2021 02:55:08 PM Brian wrote:
> On Mon 01 Mar 2021 at 08:13:13 -0500, rhkra...@gmail.com wrote:
> > On Sunday, February 28, 2021 12:03:31 PM Celejar wrote:
> > > "Many wireless network cards (and even some wired ones) require
> > > non-free firmware to function properly. This firmware is not included
> > > in the standard installation images, due to Debian's free software
> > > ideals. If the network hardware your installation will rely upon
> > > requires such firmware, you may consider using the alternate non-free
> > > installation images available here."
> > 
> > +1
> 
> "+1" for what? Advertising each and every non-Debian installer that
> comes along and is uploaded to unofficial?

No.  Providing a reasonable explanatory text about why some other installer 
may be required and a link to a place where you can find one or more.

Re: Installation problems

[Weaver]

On 03-03-2021 06:31, Brian wrote:
> On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:
> 
>> I've one fine machine running i386 flavor of Debian 9.13 .
>> I've wish to install 64 bit flavor on a second machine.
>> debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.
>>
>> I've a couple of 8GB flash drives which have served as installation media in
>> past. IIRC I could use gparted to wipe them before using dd to copy the iso
>> to the entire device.

 I use GParted to wipe them.
On too many occasions I've had the installation complaining about
writing to `dirty' media, and using GParted beforehand always stops
that.
Cheers!

Harry
-- 
`The World is not dangerous because of those who do harm but
 because of those who look on without doing anything'.
 -- Albert Einstein

Re: Deb10 installer can't install grub

[Andrew M.A. Cater]

On Tue, Mar 02, 2021 at 05:57:37AM -0600, Dave Sherohman wrote:
> I've got a new server and am currently fighting with the Debian 10
> installer (build 20190702) in my attempts to get it up and running.
> After much wailing and gnashing of teeth, I managed to get it to stop
> complaining about being unble to mount /boot/efi and complete the
> "Partition disks" step successfully, but now I'm completely stuck on the
> "Install GRUB" step.
> 
> The GUI installer shows the error:
> 
> Unable to install GRUB in dummy
> Executing 'grub-install dummy' failed.
> 
> Checking the syslog output on virtual console 4 shows a bunch of
> os-prober activity (as expected), then finally:
> 
> Installing for x64_64-efi platform.
> grub-install: error: failed to get canonical path of `/dev/nvme0n1p1`.
> error: Running 'grub-install  --force "dummy"' failed.

Check the settings for the disk in BIOS equivalent - I had lots of problems
with an HP because I'd inadvertently told the HP software to take over
partitioning of the disks and put them into an array. 

Andy C.

Re: Installation problems

[Brian]

On Tue 02 Mar 2021 at 14:09:18 -0600, Richard Owlett wrote:

> I've one fine machine running i386 flavor of Debian 9.13 .
> I've wish to install 64 bit flavor on a second machine.
> debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.
> 
> I've a couple of 8GB flash drives which have served as installation media in
> past. IIRC I could use gparted to wipe them before using dd to copy the iso
> to the entire device.

You do not need gparted to wipe them. Just write the ISO there with dd
or cp.

-- 
Brian.

Installation problems

[Richard Owlett]

I've one fine machine running i386 flavor of Debian 9.13 .
I've wish to install 64 bit flavor on a second machine.
debian-10.8.0-amd64-netinst.iso was successfully downloaded & saved.

I've a couple of 8GB flash drives which have served as installation 
media in past. IIRC I could use gparted to wipe them before using dd to 
copy the iso to the entire device.


Gparted is not cooperating. [Both what is on this machine and I also 
have a Gparted Live on another machine.]


What might I be forgetting. Haven't done this in a long time and am not 
having a good week :{


Help please.
TIA

Re: Non-free firmware [was: Debian install Question]

[Brian]

On Mon 01 Mar 2021 at 08:13:13 -0500, rhkra...@gmail.com wrote:

> On Sunday, February 28, 2021 12:03:31 PM Celejar wrote:
> > "Many wireless network cards (and even some wired ones) require
> > non-free firmware to function properly. This firmware is not included
> > in the standard installation images, due to Debian's free software
> > ideals. If the network hardware your installation will rely upon
> > requires such firmware, you may consider using the alternate non-free
> > installation images available here."
> 
> +1

"+1" for what? Advertising each and every non-Debian installer that
comes along and is uploaded to unofficial?

-- 
Brian.

Re: Deb10 installer can't install grub

[Felix Miata]

Dan Ritter composed on 2021-03-02 07:54 (UTC-0500):

> Dave Sherohman wrote: 

>> I've got a new server...

> You'll want to create the following partitions on each,
> identically:

> 1 efi - type efi

Not RAID I presume?

> 2 boot (or boot/root) - type MDADM volume

I never have /boot on RAID, but that's just me I suppose.

> 3 root, if using separate boot - type MDADM volume

Agree.

> 4 swap - type MDADM volume

Think about this:

To start with, RAID1 is marginally slower than ordinary filesystems on 
partitions.

Does a server use swap to hibernate?

Does a server /want/ to use swap for anything?

Does anyone want swap on any type of SSD?

If I was to put swap on NVME, I would not use a RAID, just like on my old RAID
systems on HDDs. If I had 32G or more RAM, I'd just let the kernel swap to file
instead of devoting discrete partition space to swap.
-- 
Evolution as taught in public schools, like religion,
is based on faith, not on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Preseed Bug or User Error?

[Brian]

On Tue 02 Mar 2021 at 10:45:54 -0700, Charles Curley wrote:

> On Tue, 2 Mar 2021 10:25:02 +
> Brian  wrote:
> 
> > I wonder if this line is sufficient? Based on what works for me at
> > priority critucal:
> > 
> > d-i netcfg/wireless_show_essids select manual
> > d-i netcfg/wireless_essid string Curleynet2
> > d-i netcfg/wireless_security_type select wpa
> > d-i netcfg/wireless_wpa >redacted<
> 
> Major improvement, thank you! I did have to answer some questions on
> the way through, but did get a good connection.

Good. As I tried to indicate, the priority at which d-i is run affects
which questions are asked. Otherwise you get the default; what you call
the "correct selection" later on. My preseed file starts with

  debconf debconf/priority string critical

> For the record, here's my complete netcfg setup, other than commented
> out lines:
> 
> d-i netcfg/link_wait_timeout string 4
> d-i netcfg/get_domain string unassigned-domain
> # Disable that annoying WEP key dialog.
> d-i netcfg/wireless_wep string
> d-i netcfg/wireless_essid string Curleynet2
> d-i netcfg/wireless_security_type select wpa
> d-i netcfg/wireless_wpa string >redacted<
> 
> Network related prompts I had to answer:
> 
> Primary network interface
> 
> Wireless networks
> 
> Auto-configure networking
> 
> Please enter the hostname

Try

  d-i netcfg/get_hostname string your_hostname

It works for me.
 
> In all multiple choice cases, the correct selection was already
> highlighted; I did not have to select another option.
> 
> I expect with a bit of playing around I can minimize those.

I would expect so.

-- 
Brian.

Re: Preseed Bug or User Error?

[Charles Curley]

On Tue, 2 Mar 2021 10:25:02 +
Brian  wrote:

> I wonder if this line is sufficient? Based on what works for me at
> priority critucal:
> 
> d-i netcfg/wireless_show_essids select manual
> d-i netcfg/wireless_essid string Curleynet2
> d-i netcfg/wireless_security_type select wpa
> d-i netcfg/wireless_wpa >redacted<

Major improvement, thank you! I did have to answer some questions on
the way through, but did get a good connection.

For the record, here's my complete netcfg setup, other than commented
out lines:

d-i netcfg/link_wait_timeout string 4
d-i netcfg/get_domain string unassigned-domain
# Disable that annoying WEP key dialog.
d-i netcfg/wireless_wep string
d-i netcfg/wireless_essid string Curleynet2
d-i netcfg/wireless_security_type select wpa
d-i netcfg/wireless_wpa string >redacted<

Network related prompts I had to answer:

Primary network interface

Wireless networks

Auto-configure networking

Please enter the hostname

In all multiple choice cases, the correct selection was already
highlighted; I did not have to select another option.

I expect with a bit of playing around I can minimize those.



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Looking for Package Name

[David Wright]

On Tue 02 Mar 2021 at 07:48:57 (-0800), Bug Report wrote:
> I would to know the proper way to describe the package name for the
> 10.7.0 and 10.8.0 stable release installer?  I plan on filing a bug
> report, and thought I would check here first.

debian-installer

Cheers,
David.

Nettoyage du spam : février 2021

[Jean-Pierre Giraud]

Bonjour,
Comme nous sommes en mars, il est désormais possible de
traiter les archives du mois de février 2021 des listes francophones.

N'oubliez bien sûr pas d'ajouter votre nom à la liste des relecteurs
pour que nous sachions où nous en sommes.

Détails du processus de nettoyage du spam sur :

https://wiki.debian.org/I18n/FrenchSpamClean

Nettoyage du spam : février 2021

[Jean-Pierre Giraud]

Bonjour,
Comme nous sommes en février, il est désormais possible de
traiter les archives du mois de janvier 2021 des listes francophones.

N'oubliez bien sûr pas d'ajouter votre nom à la liste des relecteurs
pour que nous sachions où nous en sommes.

Détails du processus de nettoyage du spam sur :

https://wiki.debian.org/I18n/FrenchSpamClean

Re: Deb10 installer can't install grub

[Charles Curley]

On Tue, 2 Mar 2021 09:50:22 -0500
Dan Ritter  wrote:

> > I'm not positive that that's the correct approach, however,
> > especially given that I suspect that /boot will need to be visible
> > to GRUB and may thus need to be outside the LVM.  
> 
> grub can find a root in LVM, but needs /boot to be outside.
> /boot in an mdadm RAID1 is a good idea there.

I'm not sure you need a separate /boot partition. I am using Bullseye
weekly builds, so I may have a more recent d-i and grub than you do.
Also this is on i386 on a small (60GB) drive, and a DOS type MBR.

I have one LVM partition, with swap and root in that. The LVM partition
starts at sector 2048, so I expect grub resides on the first 2048
sectors.

I suspect one can get an idea of things grub can do by
listing /boot/grub/i386-pc/.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Looking for Package Name

[Bug Report]

I would to know the proper way to describe the package name for the 
10.7.0 and 10.8.0 stable release installer?  I plan on filing a bug 
report, and thought I would check here first.


RS

Re: lpoptions

[Pierre Frenkiel]

On Tue, 2 Mar 2021, Klaus Singvogel wrote:


Hi,

I think you forgot the printer name (destination).


  Actually, one doesn't need "lpoptions", as a command like

  lpr -o page-left=50 -o page-top=50  tst

  works perfectly

best regards,
--
Pierre Frenkiel

Re: use of $ARGS in systemd unit file by prometheus package

[Greg Wooledge]

Andrew Spiers (and...@andrewspiers.net) wrote:
> I think EnvironmentFile is just used for setting the environment file
> of the running process.
> Setting ARGS in /etc/default/prometheus seems to add the value to the
> command line arguments, as well as to an environment variable called
> ARGS for the prometheus process.
> I can't find any mention of this in the systemd or prometheus docs,
> but it works.

Show us the systemd unit file, or a URL that points to it exactly as it
appears on your system.  (Hint: if it's a Debian package, and if you're
using the unmodified Debian systemd unit file, you might be able to
find it on sources.debian.org.  If this is the case, tell us what version
of the Debian package you're using.  For example, buster's is at
.)

It might also help if you try "systemctl status prometheus" (or whatever
the unit's name is) and show us what it says.  Just in case the systemd
unit is merely a thin wrapper around a sysv-rc script, as is sometimes
the case.

It's worth noting that the Debian /etc/default/prometheus file from
buster's package
()
explicitly sets a variable named ARGS.

Re: Deb10 installer can't install grub

[The Wanderer]

On 2021-03-02 at 09:50, Dan Ritter wrote:

> The Wanderer wrote: 
>
>> On 2021-03-02 at 07:54, Dan Ritter wrote:
>> 
>>> You'll want to create the following partitions on each,
>>> identically:
>>> 
>>> 1 efi - type efi
>>> 2 boot (or boot/root) - type MDADM volume
>>> 3 root, if using separate boot - type MDADM volume
>>> 4 swap - type MDADM volume
>>> 
>>> Then you go to the mdadm setup and create MDADM RAID1 devices
>>> out of each pair of boot, root and swap.
>> 
>> Out of interest, how would you modify this for someone who intends to
>> run LVM on top of the RAID-1 being defined here, and wants to define as
>> many of the partitions as possible (but at least /) at the LVM level
>> rather than the mdadm level?
>> 
>> I'm guessing that the answer would be to define the EFI partition here
>> directly, then define one further partition as an appropriate type, set
>> up LVM inside that, and define the further partitions from there.
>> 
>> I'm not positive that that's the correct approach, however, especially
>> given that I suspect that /boot will need to be visible to GRUB and may
>> thus need to be outside the LVM.
> 
> grub can find a root in LVM, but needs /boot to be outside.
> /boot in an mdadm RAID1 is a good idea there.

So, three partitions, then?

1. efi
2. /boot
3. LVM

And define everything else inside the LVM. (In practice, "everything
else" here will be /, /var, /tmp, and possibly swap. /home will be on a
separate RAID array.)

It'll still probably be interesting figuring out what to specify as the
destination for the GRUB install, but if I'm lucky it might Just Work.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Deb10 installer can't install grub

[Dan Ritter]

The Wanderer wrote: 
> On 2021-03-02 at 07:54, Dan Ritter wrote:
> 
> > You'll want to create the following partitions on each,
> > identically:
> > 
> > 1 efi - type efi
> > 2 boot (or boot/root) - type MDADM volume
> > 3 root, if using separate boot - type MDADM volume
> > 4 swap - type MDADM volume
> > 
> > Then you go to the mdadm setup and create MDADM RAID1 devices
> > out of each pair of boot, root and swap.
> 
> Out of interest, how would you modify this for someone who intends to
> run LVM on top of the RAID-1 being defined here, and wants to define as
> many of the partitions as possible (but at least /) at the LVM level
> rather than the mdadm level?
> 
> I'm guessing that the answer would be to define the EFI partition here
> directly, then define one further partition as an appropriate type, set
> up LVM inside that, and define the further partitions from there.
> 
> I'm not positive that that's the correct approach, however, especially
> given that I suspect that /boot will need to be visible to GRUB and may
> thus need to be outside the LVM.

grub can find a root in LVM, but needs /boot to be outside.
/boot in an mdadm RAID1 is a good idea there.

-dsr-

Re: Deb10 installer can't install grub

[Dave Sherohman]

On Tue, Mar 02, 2021 at 09:26:21AM -0500, The Wanderer wrote:
> I didn't parse what he wrote that way. He said:
> 
>  You'll want to create the following partitions on each,
>  identically:
>  
>  1 efi - type efi
>  2 boot (or boot/root) - type MDADM volume
>  3 root, if using separate boot - type MDADM volume
>  4 swap - type MDADM volume
>  
>  Then you go to the mdadm setup and create MDADM RAID1 devices
>  out of each pair of boot, root and swap.
> 
> Note that he specified to RAID the three listed MDADM partitions, but
> did not mention the same for the EFI partition.

Ah, right.  When he mentioned RAIDing the boot, I took that to mean the
EFI partitions.  Forgot that he as using a separate /boot.



So I took a look at the grub-installer script, and guess what I found as
a comment just before the `ls` that kills it?

---
# XXX cjwatson 2019-03-25: This is all far too complicated and fragile, and
# should be replaced with in-target or similar.

# Ensure proc is mounted in all the $chroot calls;
# needed for RAID+LVM for example
initial_proc_contents="$(ls $ROOT/proc)"
---

"Far too complicated and fragile", indeed!

-- 
Dave Sherohman

Re: Deb10 installer can't install grub

[The Wanderer]

On 2021-03-02 at 09:20, Dave Sherohman wrote:

> On Tue, Mar 02, 2021 at 09:09:52AM -0500, The Wanderer wrote:
> 
>> On 2021-03-02 at 09:01, Dave Sherohman wrote:

>>> RAID Device #1 is 1.9 TB, ext4fs, and set to mount on /
>>> RAID Device #2 is 2.0 GB, ESP, and bootable
>> 
>> So the EFI partitions themselves are also RAIDed? I wouldn't have
>> expected that to work.
> 
> That was my expectation as well, but Dan said it should work, so I went
> with it.

I didn't parse what he wrote that way. He said:

 You'll want to create the following partitions on each,
 identically:
 
 1 efi - type efi
 2 boot (or boot/root) - type MDADM volume
 3 root, if using separate boot - type MDADM volume
 4 swap - type MDADM volume
 
 Then you go to the mdadm setup and create MDADM RAID1 devices
 out of each pair of boot, root and swap.

Note that he specified to RAID the three listed MDADM partitions, but
did not mention the same for the EFI partition.

> Of course, I've also tried it with then not RAIDed and the results
> are identical, aside from the "canonoical path" error message in 
> syslog changing from /dev/md2 to /dev/nvme0n1p1.

Not terribly surprising, but it was worth a check.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Deb10 installer can't install grub

[Dave Sherohman]

On Tue, Mar 02, 2021 at 09:09:52AM -0500, The Wanderer wrote:
> On 2021-03-02 at 09:01, Dave Sherohman wrote:
> 
> > On Tue, Mar 02, 2021 at 07:54:01AM -0500, Dan Ritter wrote:
> 
> >> Then you go to the mdadm setup and create MDADM RAID1 devices
> >> out of each pair of boot, root and swap.
> > 
> > RAID Device #1 is 1.9 TB, ext4fs, and set to mount on /
> > RAID Device #2 is 2.0 GB, ESP, and bootable
> 
> So the EFI partitions themselves are also RAIDed? I wouldn't have
> expected that to work.

That was my expectation as well, but Dan said it should work, so I went
with it.  Of course, I've also tried it with then not RAIDed and the
results are identical, aside from the "canonoical path" error message in
syslog changing from /dev/md2 to /dev/nvme0n1p1.

> Is grub-installer specific to the Debian installer environment? I don't
> find it at a glance in my installed system, or with 'apt-file search'; I
> do find grub-install, which is a binary (where the error you quote seems
> to indicate a script), and is what I seem to recall having used for the
> manual installation of GRUB that finally got my current machine working
> with a RAIDed boot-drive pair all those years ago. (Albeit not with EFI
> boot partitioning, so that may not be directly comparable.)

Yes, it seems to be unique to the installer environment.  I made that
same trip in reverse, first trying to run grub-install, and then having
to go looking when that didn't exist.

> If grub-installer is a script and is the correct thing to use, the first
> thing I'd be inclined to do in your place is to examine that script and
> see what it's trying to do at the point of the error, so that I can
> figure out what it expects as input and how I can potentially try to
> provide that.

Good thought.  It's a shell script, so I'll see if I can make sense of
what it's doing in [filesystem]/proc.

-- 
Dave Sherohman

Re: Deb10 installer can't install grub

[The Wanderer]

On 2021-03-02 at 09:01, Dave Sherohman wrote:

> On Tue, Mar 02, 2021 at 07:54:01AM -0500, Dan Ritter wrote:

>> Then you go to the mdadm setup and create MDADM RAID1 devices
>> out of each pair of boot, root and swap.
> 
> RAID Device #1 is 1.9 TB, ext4fs, and set to mount on /
> RAID Device #2 is 2.0 GB, ESP, and bootable

So the EFI partitions themselves are also RAIDed? I wouldn't have
expected that to work.

>> After install to those RAID1 devices, grub will want to install.
>> Do that to the boot sector of /dev/nvme0n1, and then again to
>> the boot sector of /dev/nvme1n1.
> 
> ...and this is where it dies.  I'm now in the text-mode "expert
> install", and there is no option to manually specify a partition to
> install GRUB on, only a yes/no "Force GRUB installation to the EFI
> removable media path?" prompt.  Regardless of which answer I choose, I
> get "Unable to install GRUB in dummy" and syslog records "failed to get
> canonical path of /dev/md2".
> 
> I also tried dropping to a shell and manually running `grub-installer
> /dev/nvme0n1` and got the error "ls: /dev/nvme0n1/proc: Not a directory"
> Manually running grub-installer for /dev/md2 and /dev/nvme1n1
> (unsurprisingly) produced similar results.

Is grub-installer specific to the Debian installer environment? I don't
find it at a glance in my installed system, or with 'apt-file search'; I
do find grub-install, which is a binary (where the error you quote seems
to indicate a script), and is what I seem to recall having used for the
manual installation of GRUB that finally got my current machine working
with a RAIDed boot-drive pair all those years ago. (Albeit not with EFI
boot partitioning, so that may not be directly comparable.)

If grub-installer is a script and is the correct thing to use, the first
thing I'd be inclined to do in your place is to examine that script and
see what it's trying to do at the point of the error, so that I can
figure out what it expects as input and how I can potentially try to
provide that.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Deb10 installer can't install grub

[Dave Sherohman]

On Tue, Mar 02, 2021 at 07:54:01AM -0500, Dan Ritter wrote:
> In the installer, you want expert mode. Does the disk
> partitioner recognize both nvme0n1 and nvme1n1 ? 

Yes.  The list of disks shown in the partitioner is currently:

RAID device #1
RAID device #2
/dev/nvme0n1
/dev/nvme1n1
SCSI2 (0,0,0) (sda) - the USB stick I booted from
SCSI1 (0,0,0) (sdb) - the first storage drive
... the other seven storage drives ...

> You'll want to create the following partitions on each,
> identically:
> 
> 1 efi - type efi
> 2 boot (or boot/root) - type MDADM volume
> 3 root, if using separate boot - type MDADM volume
> 4 swap - type MDADM volume

Partitioning is identical on both nvme drives, consisting of:

1.0   MB  free space
2.0   GB  ESP (bootable)
8.0   GB  swap
1.9   TB  RAID physical device
331.8 kB  free space

> Then you go to the mdadm setup and create MDADM RAID1 devices
> out of each pair of boot, root and swap.

RAID Device #1 is 1.9 TB, ext4fs, and set to mount on /
RAID Device #2 is 2.0 GB, ESP, and bootable

> After install to those RAID1 devices, grub will want to install.
> Do that to the boot sector of /dev/nvme0n1, and then again to
> the boot sector of /dev/nvme1n1.

...and this is where it dies.  I'm now in the text-mode "expert
install", and there is no option to manually specify a partition to
install GRUB on, only a yes/no "Force GRUB installation to the EFI
removable media path?" prompt.  Regardless of which answer I choose, I
get "Unable to install GRUB in dummy" and syslog records "failed to get
canonical path of /dev/md2".

I also tried dropping to a shell and manually running `grub-installer
/dev/nvme0n1` and got the error "ls: /dev/nvme0n1/proc: Not a directory"
Manually running grub-installer for /dev/md2 and /dev/nvme1n1
(unsurprisingly) produced similar results.

-- 
Dave Sherohman

Re: Deb10 installer can't install grub

[The Wanderer]

On 2021-03-02 at 07:54, Dan Ritter wrote:

> You'll want to create the following partitions on each,
> identically:
> 
> 1 efi - type efi
> 2 boot (or boot/root) - type MDADM volume
> 3 root, if using separate boot - type MDADM volume
> 4 swap - type MDADM volume
> 
> Then you go to the mdadm setup and create MDADM RAID1 devices
> out of each pair of boot, root and swap.

Out of interest, how would you modify this for someone who intends to
run LVM on top of the RAID-1 being defined here, and wants to define as
many of the partitions as possible (but at least /) at the LVM level
rather than the mdadm level?

I'm guessing that the answer would be to define the EFI partition here
directly, then define one further partition as an appropriate type, set
up LVM inside that, and define the further partitions from there.

I'm not positive that that's the correct approach, however, especially
given that I suspect that /boot will need to be visible to GRUB and may
thus need to be outside the LVM.


This isn't purely academic interest; I'm not moving forward right now
because I can't currently afford all the components, but I'm planning a
new computer build as soon as that changes, and one part of the design
I've decided on is a pair of M.2 SSDs in RAID-1.

I remember having had enough trouble getting GRUB installed and booting
with a pair of SATA SSDs in RAID-1 when I built my current machine,
which doesn't use GPT or EFI boot, and I'd prefer to avoid having to
juggle that on the fly again - especially not given that the need to
cater to the partitioning requirements of EFI boot is likely to make
things more complicated.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Deb10 installer can't install grub

[Dan Ritter]

Dave Sherohman wrote: 
> I've got a new server and am currently fighting with the Debian 10
> installer (build 20190702) in my attempts to get it up and running.
> After much wailing and gnashing of teeth, I managed to get it to stop
> complaining about being unble to mount /boot/efi and complete the
> "Partition disks" step successfully, but now I'm completely stuck on the
> "Install GRUB" step.
> 
> The GUI installer shows the error:
> 
> Unable to install GRUB in dummy
> Executing 'grub-install dummy' failed.
> 
> Checking the syslog output on virtual console 4 shows a bunch of
> os-prober activity (as expected), then finally:
> 
> Installing for x64_64-efi platform.
> grub-install: error: failed to get canonical path of `/dev/nvme0n1p1`.
> error: Running 'grub-install  --force "dummy"' failed.
> 
> I assume that the "canonical path" it's looking for is a /dev/sda-type
> device name, but I have no idea how to assign one of those to an nvme
> drive.  (And I thought that kind of name was supposed to have been
> banished in favor of "predictable" names by now anyhow.)
> 
> Several of the old-style names are already in use; the installer is
> showing sda for the USB stick that the installation was booted from and
> sdb-sdi for eight large disks, but the operating system is to boot and
> run from the drives /dev/nvme0n1 and /dev/nvme1n1.
> 
> What do I need to do to get this working?
> 
> Also, would that solution also work for md devices as well as for nvme
> devices?  I had previously tried putting UEFI onto a RAID1 mirror
> between the two nvme drives, but got a similar error from grub about not
> being able to find the canonical path of /dev/md1.

/dev/nvme0n1 is your first NVMe drive; /dev/nvme1n1 is your
second. Add a p1 to each to reference the first partition.

If you want to install to an mdadm RAID, that's do-able with
grub as well. 

In the installer, you want expert mode. Does the disk
partitioner recognize both nvme0n1 and nvme1n1 ? 

You'll want to create the following partitions on each,
identically:

1 efi - type efi
2 boot (or boot/root) - type MDADM volume
3 root, if using separate boot - type MDADM volume
4 swap - type MDADM volume

Then you go to the mdadm setup and create MDADM RAID1 devices
out of each pair of boot, root and swap.

After install to those RAID1 devices, grub will want to install.
Do that to the boot sector of /dev/nvme0n1, and then again to
the boot sector of /dev/nvme1n1.

After a reboot into the new OS, you should set up your storage
disks. 

If this doesn't work, tell us where in the process it stops, and
what the error is there.

-dsr-

Re: lpoptions

[Klaus Singvogel]

Hi,

I think you forgot the printer name (destination).

Best regards,
Klaus.

Pierre Frenkiel wrote:
> hi,
> trying to configure the lpr output, I found that on the linuxquestions site:
> 
>  lpoptions -o page-left=40 -o page-right=20 -o page-top=40 -o page-bottom=10
> 
> but it doesn't work.
> can anybody tell me how to make it to work?
> thanks in advance.
> 
> best regards,
> 
> -- 
> Pierre Frenkiel

-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Deb10 installer can't install grub

[Dave Sherohman]

I've got a new server and am currently fighting with the Debian 10
installer (build 20190702) in my attempts to get it up and running.
After much wailing and gnashing of teeth, I managed to get it to stop
complaining about being unble to mount /boot/efi and complete the
"Partition disks" step successfully, but now I'm completely stuck on the
"Install GRUB" step.

The GUI installer shows the error:

Unable to install GRUB in dummy
Executing 'grub-install dummy' failed.

Checking the syslog output on virtual console 4 shows a bunch of
os-prober activity (as expected), then finally:

Installing for x64_64-efi platform.
grub-install: error: failed to get canonical path of `/dev/nvme0n1p1`.
error: Running 'grub-install  --force "dummy"' failed.

I assume that the "canonical path" it's looking for is a /dev/sda-type
device name, but I have no idea how to assign one of those to an nvme
drive.  (And I thought that kind of name was supposed to have been
banished in favor of "predictable" names by now anyhow.)

Several of the old-style names are already in use; the installer is
showing sda for the USB stick that the installation was booted from and
sdb-sdi for eight large disks, but the operating system is to boot and
run from the drives /dev/nvme0n1 and /dev/nvme1n1.

What do I need to do to get this working?

Also, would that solution also work for md devices as well as for nvme
devices?  I had previously tried putting UEFI onto a RAID1 mirror
between the two nvme drives, but got a similar error from grub about not
being able to find the canonical path of /dev/md1.

-- 
Dave Sherohman

Re: apt pinning: j'y comprends rien !

[didier gaumet]

De ce que je comprends (mais j'ai peut-être pas tout compris, 
apt_preferences m'a déjà surpris par le passé):


- Les priorités négatives impliquent que tu forces l'interdiction 
inconditionnelle d'installation des paquets qui en sont affectés (y 
compris ceux dont l'absence risque de casser le système)
- C'est l'inverse  des priorités supérieures ou égales à 1000 avec 
lesquelles tu forces l'installation inconditionnelle des paquets qui en 
sont affectés, même si cela risque de casser ton système (si tu veux 
faire un downgrade global d'une distro Debian, tu en passes par là 
(c'est risqué))


Donc quand tu déclares une Testing par défaut dans apt.conf (équivalant 
à 990) et que tu déclares une priorité 800 pour le firefox de Unstable, 
ce dernier ne peut être installé (c'est bien ce que tu recherches? 
installer un firefox Unstable dans ta Testing?).
De même, lorsque tu déclares en priorité -10 des paquets o=Debian ça 
doit probablement signifier sur ton système que seuls les paquets 
Marillat sont installables (ils ont une priorité 990 si tu as paramétré 
ton sources.list avec Marillat Testing)


Je pense aussi qu'il est mieux de commencer l'écriture du fichier 
apt_preferences par les cas particuliers pour aller vers le cas général: 
lorsqu'un paquet est testé par rapport à ces préférences, il est 
possible que le test s'arrête dès la première condition remplie

lpoptions

[Pierre Frenkiel]

hi,
trying to configure the lpr output, I found that on the linuxquestions site:

 lpoptions -o page-left=40 -o page-right=20 -o page-top=40 -o page-bottom=10

but it doesn't work.
can anybody tell me how to make it to work?
thanks in advance.

best regards,

--
Pierre Frenkiel

Re: sphinxsearch on debian

[Roberto C . Sánchez]

On Tue, Mar 02, 2021 at 11:52:24AM +0100, basti wrote:
> Hello,
> 
> as I can See Sphinx 3.0.1 released on Dec 18, 2017.
> (http://sphinxsearch.com/blog/2017/12/18/sphinx-3-0-1-released/)
> 
> Why Debian is still use 2.2.11 ?
> (https://metadata.ftp-master.debian.org/changelogs//main/s/sphinxsearch/sphinxsearch_2.2.11-2_changelog)
> 
> Best Regards
> 
It appears to be a license issue: https://bugs.debian.org/911761

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: apt pinning: j'y comprends rien !

[Gaëtan PERRIER]

Le mardi 02 mars 2021 à 10:30 +0100, didier gaumet a écrit :
> En fait j'ai l'impression que tu te trompes sur les priorités, en 
> considérant qu'un nombre faible signifie une priorité élevée, alors que 
> c'est l'inverse ;-)
> 
> C'est ta détermination de priorités -10 pour o=Debian et 800 pour 
> firefox d'unstable avec une distribution Testing à 990 qui me le 
> laissent supposer...
> 
> Extrait de la page man d'apt_preferences:
> [...]
> Méthode d'interprétation des priorités par APT
>     Les priorités (P) indiquées dans le fichier des préférences 
> doivent être des entiers positifs ou négatifs. Ils sont interprétés à 
> peu près
>     comme suit :
> 
>     P >= 1000
>     cette priorité entraîne l'installation du paquet même s'il 
> s'agit d'un retour en arrière.
> 
>     990 <= P < 1000
>     la version sera installée, même si elle n'appartient pas à 
> la distribution par défaut ; mais elle ne sera pas installée si la version
>     installée est plus récente.
> 
>     500 <= P < 990
>     La version sera installée, sauf s'il existe une version 
> appartenant à la distribution par défaut ou si la version installée est plus
>     récente.
> 
>     100 <= P < 500
>     la version sera installée, sauf s'il existe une version 
> appartenant à une autre distribution ou si la version installée est plus
>     récente.
> 
>     0 < P < 100
>     la version sera installée si aucune version du paquet n'est 
> installée.
> 
>     P < 0
>     cette priorité empêche l'installation de la version.
> 
>     P = 0
>     a un comportement indéfini, ne pas l'utiliser.
> [...]
> 

Non j'ai bien compris que plus P est élevé plus c'est prioritaire. C'est pour
ça que pour dmo j'ai mis 10. Je me suis basé sur cette manpage qui d'ailleurs
manque de cohérence car dans la passage que tu indiques ça semble dire que P
doit-être > 0 mais pourtant ensuite dans les exemple il y a des valeurs
négatives ...

Gaëtan


signature.asc
Description: This is a digitally signed message part

Re: apt pinning: j'y comprends rien !

[Gaëtan PERRIER]

Le mardi 02 mars 2021 à 02:57 +0100, Jérémy Prego a écrit :
> > 
> > Package: *
> >  Pin: release o=Unofficial Multimedia Packages,a=testing
> >  Pin: origin *.deb-multimedia.org
> >  Pin-Priority: 10
> je ne suis pas convaincu qu'il est bien d'avoir deux pin pour une même
> règle :) c'est peut être pour ça que ça ne fonctionne pas ...
> 

J'ai essayé avec seulement l'une ou l'autre et ça ne change rien ...

Gaëtan


signature.asc
Description: This is a digitally signed message part

sphinxsearch on debian

[basti]

Hello,

as I can See Sphinx 3.0.1 released on Dec 18, 2017.
(http://sphinxsearch.com/blog/2017/12/18/sphinx-3-0-1-released/)

Why Debian is still use 2.2.11 ?
(https://metadata.ftp-master.debian.org/changelogs//main/s/sphinxsearch/sphinxsearch_2.2.11-2_changelog)

Best Regards

Re: Preseed Bug or User Error?

[Brian]

On Mon 01 Mar 2021 at 16:27:48 -0700, Charles Curley wrote:

[...]

> ### Description: Wireless network type for ${iface}:
> #   Choose WEP/Open if the network is open or secured with WEP.
> #   Choose WPA/WPA2 if the network is protected with WPA/WPA2 PSK
> #   (Pre-Shared Key).
> # d-i netcfg/wireless_security_type select wpa
> d-i netcfg/wireless_security_type select WPA/WPA2 PSK
> # Possible choices: WEP/Open Network, WPA/WPA2 PSK

I wonder if this line is sufficient? Based on what works for me at
priority critucal:

d-i netcfg/wireless_show_essids select manual
d-i netcfg/wireless_essid string Curleynet2
d-i netcfg/wireless_security_type select wpa
d-i netcfg/wireless_wpa >redacted<

-- 
Brian.

Re: apt pinning: j'y comprends rien !

[didier gaumet]

En fait j'ai l'impression que tu te trompes sur les priorités, en 
considérant qu'un nombre faible signifie une priorité élevée, alors que 
c'est l'inverse ;-)


C'est ta détermination de priorités -10 pour o=Debian et 800 pour 
firefox d'unstable avec une distribution Testing à 990 qui me le 
laissent supposer...


Extrait de la page man d'apt_preferences:
[...]
Méthode d'interprétation des priorités par APT
   Les priorités (P) indiquées dans le fichier des préférences 
doivent être des entiers positifs ou négatifs. Ils sont interprétés à 
peu près

   comme suit :

   P >= 1000
   cette priorité entraîne l'installation du paquet même s'il 
s'agit d'un retour en arrière.


   990 <= P < 1000
   la version sera installée, même si elle n'appartient pas à 
la distribution par défaut ; mais elle ne sera pas installée si la version

   installée est plus récente.

   500 <= P < 990
   La version sera installée, sauf s'il existe une version 
appartenant à la distribution par défaut ou si la version installée est plus

   récente.

   100 <= P < 500
   la version sera installée, sauf s'il existe une version 
appartenant à une autre distribution ou si la version installée est plus

   récente.

   0 < P < 100
   la version sera installée si aucune version du paquet n'est 
installée.


   P < 0
   cette priorité empêche l'installation de la version.

   P = 0
   a un comportement indéfini, ne pas l'utiliser.
[...]