Modern automounters and umount

[Thomas Schmitt]

Hi,

during a discussion on linuxquestion.org i got a (Mint) user's report
that an automounted DVD cannot be unmounted manually:

https://www.linuxquestions.org/questions/linux-general-1/compiling-xfburn-source-code-additional-packages-required-4175667265/page7.html#post6092450
> $ mount | fgrep /dev/sr0
> /dev/sr0 on /media/ddval/ISOIMAGE type iso9660 (ro,nosuid,nodev,relatime,
> nojoliet,check=s,map=n, blocksize=2048,uid=1000,gid=1000,dmode=500,
> fmode=400,uhelper=udisks2)
> $ sudo umount /dev/sr0
> umount: /dev/sr0: not mounted

Does anybody here experience similar stubbornness of automounting ?
If so: How to unmount a DVD without ejecting it ?


Have a nice day :)

Thomas

Re: Modern automounters and umount

[Klaus Singvogel]

Thomas Schmitt wrote:
> > $ mount | fgrep /dev/sr0
> > /dev/sr0 on /media/ddval/ISOIMAGE type iso9660 (ro,nosuid,nodev,relatime,
> > nojoliet,check=s,map=n, blocksize=2048,uid=1000,gid=1000,dmode=500,
> > fmode=400,uhelper=udisks2)
> > $ sudo umount /dev/sr0
> > umount: /dev/sr0: not mounted

Try instead: sudo umount /media/ddval/ISOIMAGE

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

I am preparing servers to use with OpenSMTPD and Sympa to provide mail and
mailing list service.

I need to settle on names to define as the "mailname" for each the two
servers I will designate for the DNS MX records for all my mail-enabled
domains. The mailnames should be "fully qualified domain names" (FQDNs) so
they will have names like:

+ mail.example.com
+ smtp.example.com
+ mx.example.com

Does anyone have strong reasons to use one over another, or any other
choice?

Thanks for any help.

Best regards,

-Tom

Re: Choice of "mailname" for mail server: suggestions welcome

[john doe]

On 2/21/2020 12:09 PM, Tom Browder wrote:
> I am preparing servers to use with OpenSMTPD and Sympa to provide mail and
> mailing list service.
>
> I need to settle on names to define as the "mailname" for each the two
> servers I will designate for the DNS MX records for all my mail-enabled
> domains. The mailnames should be "fully qualified domain names" (FQDNs) so
> they will have names like:
>
> + mail.example.com
> + smtp.example.com
> + mx.example.com
>
> Does anyone have strong reasons to use one over another, or any other
> choice?
>

I might be missing something here but the domain name is what you
buy/what you get.

If your planning to use split DNS, 'internal' and 'external' could be
one option.

For the lists, 'lists.example.com' might not be a bad idea.

You can also use cname record to point to the same thing.

--
John Doe

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 05:39 john doe  wrote:
...

> I might be missing something here but the domain name is what you
> buy/what you get.


Note I own (techically it's more of a rental or lease) multiple domains
hosted across multiple servers which I also fully control (no sharing, full
root control).

As I understand it, a mail server has to use smtp to physically transfer
mail between physical hosts and that requires one name that will resolve to
an IP. Even if the server is hosting multiple domains, the mail for each
still has to use the one "mailname" for transport.

Hence my original question.

-Tom

Re: Choice of "mailname" for mail server: suggestions welcome

[Jonas Smedegaard]

Hi tom,

Quoting Tom Browder (2020-02-21 12:09:47)
> I am preparing servers to use with OpenSMTPD and Sympa to provide mail 
> and mailing list service.
> 
> I need to settle on names to define as the "mailname" for each the two 
> servers I will designate for the DNS MX records for all my 
> mail-enabled domains. The mailnames should be "fully qualified domain 
> names" (FQDNs) so they will have names like:
> 
> + mail.example.com
> + smtp.example.com
> + mx.example.com
> 
> Does anyone have strong reasons to use one over another, or any other 
> choice?

Depends on the purpose of the name(s).

If you run everything on a single host, then mail.example.com.

If you need to distinguish mail routing from other tasks (e.g. when 
running a spam filter on a different host and you want to tell other 
smtp servers to deliver to that instead of directly to your main mail 
server), then mx.example.com (or mx1.example.com) for that.

Similar for other names: Use protocol or other special name to emphasize 
that service, otherwise it is more confusing than helping.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: Choice of "mailname" for mail server: suggestions welcome

[Michael Howard]

On 21/02/2020 11:09, Tom Browder wrote:
I am preparing servers to use with OpenSMTPD and Sympa to provide mail 
and mailing list service.


I need to settle on names to define as the "mailname" for each the two 
servers I will designate for the DNS MX records for all my 
mail-enabled domains. The mailnames should be "fully qualified domain 
names" (FQDNs) so they will have names like:


+ mail.example.com 
+ smtp.example.com 
+ mx.example.com 

Does anyone have strong reasons to use one over another, or any other 
choice?


Thanks for any help.

Best regards,

-Tom



I don't know your use case but using 'regular' names like 
smtp.example.com, imap.example.com, pop3.example.com etc, help with the 
auto config processes used on devices, thus making it easier for users 
to setup accounts on their devices.


--
Michael Howard

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 06:00 Jonas Smedegaard  wrote:

> Hi tom,
>
...

> > Does anyone have strong reasons to use one over another, or any other
>
> choice?
>
...

> Depends on the purpose of the name(s).

...

Thanks, Jonas, that makes good sense. Based on that I should use "mail" and
maybe "mail2" for my backup mail server.

One of the reasons I asked was I know Gmail used to use something like "
smtp.gmail.com" for its smtp server and thought that might be popular among
sysadmins with such servers.

-Tom

Re: Choice of "mailname" for mail server: suggestions welcome

[Joe]

On Fri, 21 Feb 2020 06:00:14 -0600
Tom Browder  wrote:

> On Fri, Feb 21, 2020 at 05:39 john doe  wrote:
> ...
> 
> > I might be missing something here but the domain name is what you
> > buy/what you get.  
> 
> 
> Note I own (techically it's more of a rental or lease) multiple
> domains hosted across multiple servers which I also fully control (no
> sharing, full root control).
> 
> As I understand it, a mail server has to use smtp to physically
> transfer mail between physical hosts and that requires one name that
> will resolve to an IP. Even if the server is hosting multiple
> domains, the mail for each still has to use the one "mailname" for
> transport.

Not really, you can have an A record for each domain, with the MX
record for each domain pointing to its 'own' A record. The only common
feature must be the IP address that the A records point to.

You may well have only one PTR record for the address, although
multiple PTRs on one address are valid, but not many ISPs make provision
for that.

> 
> Hence my original question.
> 

I don't really see any reason either way, you can call it
fred.example.com if you wish, as long as the MX records point to it.

You may well have multiple A records for the address, anyway. An
important feature of a mail server is a complementary A-PTR pair, and
not all ISPs allow user setting of the PTR. So you may well have an
A-PTR pair on the IP address, both supplied by the ISP, which bear no
relation to any of your domain names. No problem.

If you have external account users, they will need to set up addresses
for both SMTP and IMAP/POP, and it is slightly more convenient to use
the one name for both, and 'mail' will then be more suitable. It's only
when you get fancy, with separate incoming and outgoing servers, that
you need distinct and meaningful names.

-- 
Joe

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 06:17 Michael Howard 
wrote:
...

> I don't know your use case but using 'regular' names like smtp.example.com,
> imap.example.com, pop3.example.com etc, help with the auto config
> processes used on devices, thus making it easier for users to setup
> accounts on their devices.
>

I'm not planning on anything at the moment but supporting mailing lists,
but you have a good point for any future expansion.

Thanks, Michael.

-Tom

Re: Choice of "mailname" for mail server: suggestions welcome

[Jonas Smedegaard]

Quoting Tom Browder (2020-02-21 13:17:52)
> On Fri, Feb 21, 2020 at 06:00 Jonas Smedegaard  wrote:
> 
> > Hi tom,
> >
> ...
> 
> > > Does anyone have strong reasons to use one over another, or any other
> >
> > choice?
> >
> ...
> 
> > Depends on the purpose of the name(s).
> 
> ...
> 
> Thanks, Jonas, that makes good sense. Based on that I should use 
> "mail" and maybe "mail2" for my backup mail server.

Only if by "backup" you mean mirror of mail services generally - i.e. 
also for your users to connect to for fetching their mail when the 
primary server is down.

Otherwise, if you mean MX backup then I would use "mx2" for the backup 
host (and I would then consider naming the primary host _both_ "mail" 
and "mx1" so that I can use "mx1" and "mx2" for MX records.


> One of the reasons I asked was I know Gmail used to use something like 
> " smtp.gmail.com" for its smtp server and thought that might be 
> popular among sysadmins with such servers.

Lots of names are popular for various reasons.

Google has numerous hosts serving specifc services, likely with failover 
so that one hostname is even used for multiple hosts behind the scenes.

So if your setup is complex, then name each service, and number it too.

...but if you want simplicity, then beware that for each hostname you 
may (now or later) need to fumble with TLS certificates and/or DNSSEC 
signing keys.

...and beware that your users are not helped by hosts named by services 
but will likely find it geeky that they need to use "smpt2" to send and 
"pop3" to receive (unless of course they are all geeks, where they might 
prefer hosts named by characters in Tolkien books or Star Wars).


As Michael also mentioned, some mail clients blindly assume the world 
uses specific names for user-facing incoming and outgoing services, and 
probe those names before asking the user.  Personally I have found it 
least confusing for my users to tell them that "the server is 
mail-dot-our-domain for all user-facing services - both incoming and 
outgoing", and I then setup hints for those mail clients that wants to 
auto-configure.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 06:29 Joe  wrote:

> On Fri, 21 Feb 2020 06:00:14 -0600
> Tom Browder  wrote:

...

> > As I understand it, a mail server has to use smtp to physically
> > transfer mail between physical hosts and that requires one name that
> > will resolve to an IP. Even if the server is hosting multiple
> > domains, the mail for each still has to use the one "mailname" for
> > transport.
>
> Not really, you can have an A record for each domain, with the MX
> record for each domain pointing to its 'own' A record. The only common
> feature must be the IP address that the A records point to.
>
> You may well have only one PTR record for the address, although
> multiple PTRs on one address are valid, but not many ISPs make provision
> for that.
>

Interesting--I would prefer that. So with all mail stuff on one server, I
can have each domain's MX record point to its own mail server. And I do
have control of the PTR record. I just need to ensure everything resolves
to the correct host IP.

So how does all that jibe with the single name required by OpenSMPTD?

Thanks, Joe.

-Tom

Re: Choice of "mailname" for mail server: suggestions welcome

[Joe]

On Fri, 21 Feb 2020 06:46:59 -0600
Tom Browder  wrote:

> On Fri, Feb 21, 2020 at 06:29 Joe  wrote:
> 
> > On Fri, 21 Feb 2020 06:00:14 -0600
> > Tom Browder  wrote:  
> 
> ...
> 
> > > As I understand it, a mail server has to use smtp to physically
> > > transfer mail between physical hosts and that requires one name
> > > that will resolve to an IP. Even if the server is hosting multiple
> > > domains, the mail for each still has to use the one "mailname" for
> > > transport.  
> >
> > Not really, you can have an A record for each domain, with the MX
> > record for each domain pointing to its 'own' A record. The only
> > common feature must be the IP address that the A records point to.
> >
> > You may well have only one PTR record for the address, although
> > multiple PTRs on one address are valid, but not many ISPs make
> > provision for that.
> >  
> 
> Interesting--I would prefer that. So with all mail stuff on one
> server, I can have each domain's MX record point to its own mail
> server. And I do have control of the PTR record. I just need to
> ensure everything resolves to the correct host IP.
> 
> So how does all that jibe with the single name required by OpenSMPTD?
> 

Don't know, I'm not familiar with that. But mail server software
shouldn't need to know anything about the DNS records used to route SMTP
mail to it. If so configured, it will look up DNS records of senders,
but not generally its own.

Exim4 has a default mailname, but to the best of my knowledge, it is
used only in the HELO/EHLO banner, and can be overridden for multiple
domains. HELO/EHLO is used to identify the server in logs, and need not
have any relationship to any email domain handled by the server, and is
often (incorrectly) configured as a bare domain name. It is best
configured to the same FQDN that the domain's primary MX record holds.

It is certainly supposed to be a FQDN, and it does need to be
resolvable in public DNS. My mail server, like most, is configured to
reject email from a sender whose HELO is not resolvable, and
particularly those whose HELO appears to be my own domain or public IP
address (yes, some malware does that). DNS servers aren't really
supposed to resolve bare domain names, but most do, aliasing to the
'www' A record, because many people are too lazy to type 'www' in what
should be a web FQDN.

-- 
Joe

Re: Modern automounters and umount

[Stefan Monnier]

>> > $ mount | fgrep /dev/sr0
>> > /dev/sr0 on /media/ddval/ISOIMAGE type iso9660 (ro,nosuid,nodev,relatime,
>> > nojoliet,check=s,map=n, blocksize=2048,uid=1000,gid=1000,dmode=500,
>> > fmode=400,uhelper=udisks2)
>> > $ sudo umount /dev/sr0
>> > umount: /dev/sr0: not mounted
> Try instead: sudo umount /media/ddval/ISOIMAGE

Indeed.  And FWIW, you should/might be able to avoid the `sudo` by
asking udisks2 to do the unmount (I don't know how that works, tho.
I personally still use `mount` instead, so I'd do `pumount
/media/ddval/ISOIMAGE`).


Stefan

Re: Choice of "mailname" for mail server: suggestions welcome

[Henning Follmann]

On Fri, Feb 21, 2020 at 12:38:45PM +0100, john doe wrote:
> On 2/21/2020 12:09 PM, Tom Browder wrote:
> > I am preparing servers to use with OpenSMTPD and Sympa to provide mail and
> > mailing list service.
> >
> > I need to settle on names to define as the "mailname" for each the two
> > servers I will designate for the DNS MX records for all my mail-enabled
> > domains. The mailnames should be "fully qualified domain names" (FQDNs) so
> > they will have names like:
> >
> > + mail.example.com
> > + smtp.example.com
> > + mx.example.com
> >
> > Does anyone have strong reasons to use one over another, or any other
> > choice?
> >
> 
> I might be missing something here but the domain name is what you
> buy/what you get.
> 
> If your planning to use split DNS, 'internal' and 'external' could be
> one option.
> 
> For the lists, 'lists.example.com' might not be a bad idea.
> 
> You can also use cname record to point to the same thing.
> 
> --
> John Doe
>


Don't do THAT!

RFC2181 section 10.3 says you can't point your MX record to a CNAME

-H


-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 08:37 Henning Follmann 
wrote:

> On Fri, Feb 21, 2020 at 12:38:45PM +0100, john doe wrote:

...

> Don't do THAT!
>
> RFC2181 section 10.3 says you can't point your MX record to a CNAME
>

Maybe that's why Namecheap has the MXE record that points to an IP.

Besides the relevant RFCs, can anyone recommend a good book that covers all
this. I have a couple of the O'Reilly books on "Postfix" and "DNS and Bind"
and I am going back to refresh myself, but any other recs?

Thanks.

-Tom

Re: Modern automounters and umount

[Jonathan Dowland]

On Fri, Feb 21, 2020 at 08:53:50AM -0500, Stefan Monnier wrote:

Indeed.  And FWIW, you should/might be able to avoid the `sudo` by
asking udisks2 to do the unmount


Yep. It requires you to specify the device, rather than the filesystem
mount point:

   $ udisksctl unmount -b /dev/sdb1

But does not require superuser, if udisks2 mounted it on your user's
behalf in the first place.


--
👱🏻  Jonathan Dowland
🔗   https://jmtd.net

Re: Choice of "mailname" for mail server: suggestions welcome

[Brian]

On Fri 21 Feb 2020 at 05:09:47 -0600, Tom Browder wrote:

> I am preparing servers to use with OpenSMTPD and Sympa to provide mail and
> mailing list service.
> 
> I need to settle on names to define as the "mailname" for each the two
> servers I will designate for the DNS MX records for all my mail-enabled
> domains. The mailnames should be "fully qualified domain names" (FQDNs) so
> they will have names like:
> 
> + mail.example.com
> + smtp.example.com
> + mx.example.com
> 
> Does anyone have strong reasons to use one over another, or any other
> choice?

I wouldn't use any of those with Exim because I am aware of the function
of /etc/mailname in its sending of mail. What does /etc/mailname do on
OpenSMTPD?

-- 
Brian.

Re: Choice of "mailname" for mail server: suggestions welcome

[Henning Follmann]

On Fri, Feb 21, 2020 at 08:47:36AM -0600, Tom Browder wrote:
> On Fri, Feb 21, 2020 at 08:37 Henning Follmann 
> wrote:
> 
> > On Fri, Feb 21, 2020 at 12:38:45PM +0100, john doe wrote:
> 
> ...
> 
> > Don't do THAT!
> >
> > RFC2181 section 10.3 says you can't point your MX record to a CNAME
> >
> 
> Maybe that's why Namecheap has the MXE record that points to an IP.
> 
> Besides the relevant RFCs, can anyone recommend a good book that covers all
> this. I have a couple of the O'Reilly books on "Postfix" and "DNS and Bind"
> and I am going back to refresh myself, but any other recs?
>

For years I operated a couple of sendmail installations. That and the
O'Reilly Sendmail book tought me a lot.
Today I prefer postfix. There is a german book from Peer Heinlein.
This is an excellent source if you want to set up a multidomain
mailserver completely driven by a LDAP directory.

-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 09:36 Brian  wrote:

> On Fri 21 Feb 2020 at 05:09:47 -0600, Tom Browder wrote:
>
...
| > I need to settle on names to define as the "mailname" for each the two

> > servers I will designate for the DNS MX records for all my mail-enabled
> > domains. The mailnames should be "fully qualified domain names" (FQDNs)
> so
>
...

> I wouldn't use any of those with Exim because I am aware of the function
> of /etc/mailname in its sending of mail. What does /etc/mailname do on
> OpenSMTPD?


The source of my info is in this link:


https://poolp.org/posts/2019-09-14/setting-up-a-mail-server-with-opensmtpd-dovecot-and-rspamd/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

-Tom

Re: Choice of "mailname" for mail server: suggestions welcome

[Brian]

On Fri 21 Feb 2020 at 11:22:58 -0600, Tom Browder wrote:

> On Fri, Feb 21, 2020 at 09:36 Brian  wrote:
> 
> > On Fri 21 Feb 2020 at 05:09:47 -0600, Tom Browder wrote:
> >
> ...
> | > I need to settle on names to define as the "mailname" for each the two
> 
> > > servers I will designate for the DNS MX records for all my mail-enabled
> > > domains. The mailnames should be "fully qualified domain names" (FQDNs)
> > so
> >
> ...
> 
> > I wouldn't use any of those with Exim because I am aware of the function
> > of /etc/mailname in its sending of mail. What does /etc/mailname do on
> > OpenSMTPD?
> 
> 
> The source of my info is in this link:
> 
> 
> https://poolp.org/posts/2019-09-14/setting-up-a-mail-server-with-opensmtpd-dovecot-and-rspamd/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

Thanks, I will read the page in detail later. Meanwhile, I did a quick
search on the page for "mailname" and didn't get anything. Anyway, what
I really wanted to know was what function *you* thought /etc/mailname
played in OpenSMTPD because it would determine what you chose for it.

On Exim it is used to qualify a local part without a domain name. After
I installed OpenSMTPD it seems to me that this is also what OpenSMTPD
does. In other words, if I had mailname as gmail.com, a mail I send to
tombrowder (no domain name) would go to tombrow...@gmail.com.

Apologies if I have missed the point and this is something you have
factored into your planning.

-- 
Brian.

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 12:05 PM Brian  wrote:
> On Fri 21 Feb 2020 at 11:22:58 -0600, Tom Browder wrote:
>
> > On Fri, Feb 21, 2020 at 09:36 Brian  wrote:
...
> Thanks, I will read the page in detail later. Meanwhile, I did a quick
> search on the page for "mailname" and didn't get anything. Anyway, what
> I really wanted to know was what function *you* thought /etc/mailname
> played in OpenSMTPD because it would determine what you chose for it.
>
> On Exim it is used to qualify a local part without a domain name. After
> I installed OpenSMTPD it seems to me that this is also what OpenSMTPD
> does. In other words, if I had mailname as gmail.com, a mail I send to
> tombrowder (no domain name) would go to tombrow...@gmail.com.

Brian, you may be right. I cannot find anything in the man pages, but
it may have been stated during the installation of the Debian package.
I'll uninstall and reinstall to see if I can capture the
instructions...

-Tom

blank screen after NFS boot

[Ross Boylan]

I have a computer I have been network booting into a buster system without
incident.
A few days ago I powered it off, and later in the day turned it on. It went
through the early phases of the boot OK, but never showed the graphical
login screen.  I tried a couple of times, but it never started.  Any
suggestions about what to do?

I don't think I installed any software--dpkg.log doesn't show anything--in
between, or updated the kernel image used in the netboot.  I may have put
the fob for the wireless keyboard in a different USB port, maybe USB 3 vs 2
before.  But I doubt I even changed that.

The closest thing I have to an indication of  the source of the problem is
this message at the end  of the most recent failed graphical startup:
[11.941] (EE) Failed to open authorization file
"/var/run/sddm/{b7709304-0924-4a8a-b829-372cd2cea583}": No such file or
directory
which suggests either a problem launching sddm or that /var/run isn't being
properly setup.  But the previous failed startup does not show that message.

I processed syslog to minimize noise difference, and compared the results
for the last good boot and the first bad one.
Here are just the things that seemed notable, mostly because they appeared
in only one of the files.

GOOD
=
systemd: Mounted POSIX Message Queue File System.
systemd: Mounted Kernel Debug File System.
systemd: Mounted Huge Pages File System.

kernel: Memory: 7574244K/7824848K available (10252K kernel code, 1241K
rwdata, 3320K rodata, 1592K init, 2276K bss, 250604K reserved, 0K
cma-reserved)

kernel: audit: type=000 audit(000.000:8): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="nvidia_modprobe"
pid=000 comm="apparmor_parser"
kernel: audit: type=000 audit(000.000:9): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod"
pid=000 comm="apparmor_parser"

systemd: Startup finished in 386ms.
sddm: Message received from greeter: Login
sddm: Reading from "/usr/share/xsessions/plasma.desktop"
sddm: Reading from "/usr/share/xsessions/plasma.desktop"
sddm: Session "/usr/share/xsessions/plasma.desktop" selected, command:
"/usr/bin/startkde"
# and many more about kscreen, the greeter, and subsequent activity

BAD
===
kernel: Memory: 7574236K/7824848K available (10252K kernel code, 1241K
rwdata, 3320K rodata, 1592K init, 2276K bss, 250612K reserved, 0K
cma-reserved)
# the first and last numbers differ slightly from those in the GOOD scenario
kernel: audit: type=000 audit(000.000:7): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="man_groff" pid=000
comm="apparmor_parser"
# man_groff not in good
kernel: audit: type=000 audit(000.000:11): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="nvidia_modprobe"
pid=000 comm="apparmor_parser"
# nvidia_modprobe is in good, but bad lacks nvidia_modprove//kmod
# The hardware this is running on has no nvidia card; it uses onboard Intel
graphics.
systemd: Startup finished in 373ms.


Since I attempted several restarts, there isn't a recent Xorg.log from a
successful boot.  Both recent ones show problems, though not the same
problem:
Most recent Xorg.0.log
[10.922] (--) Log file renamed from "/var/log/Xorg.pid-434.log" to
"/var/log/Xorg.0.log"
[10.924]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[10.924] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[10.924] Current Operating System: Linux family2 4.19.0-8-amd64 #1 SMP
Debian 4.19.98-1 (2020-01-26) x86_64
[10.924] Kernel command line:
BOOT_IMAGE=debian/buster/vmlinuz-4.19.0-8-amd64
initrd=debian/buster/initrd.img-4.19.0-8-amd64 root=/dev/nfs
nfsroot=192.168.1.10:/var/local/family2/
[10.924] Build Date: 05 March 2019  08:11:12PM
[10.924] xorg-server 2:1.20.4-1 (https://www.debian.org/support)
[10.924] Current version of pixman: 0.36.0

[10.946] (II) systemd-logind: logind integration requires -keeptty and
-keeptty was not provided, disabling logind integration
[10.947] (II) xfree86: Adding drm device (/dev/dri/card0)
[10.961] (--) PCI:*(0@0:2:0) 8086:0162:8086:2034 rev 9, Mem @
0xf780/4194304, 0xe000/268435456, I/O @ 0xf000/64, BIOS @
0x/131072
...
[11.515] (II) modeset(0): Output HDMI-3 using initial mode 1024x768 +0+0
[11.516] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[11.516] (==) modeset(0): DPI set to (96, 96)
...
[11.615] (II) modeset(0): [DRI2] Setup complete
[11.615] (II) modeset(0): [DRI2]   DRI driver: i965
[11.615] (II) modeset(0): [DRI2]   VDPAU driver: i965

# a series of confusing messages about input devices
# seem to say it is found, and then that it is not?
[11.883] (II) config/udev: Adding input device Logitech K400
(/dev/input/event3)
[11.883] (**) Logitech K400: Applying InputClass "libinput pointer
catchall"
[11.883] (**) Logitech K400: Applying InputClass "libinput keyboard
catchall"
[11.883] (II) Using input driver 'libinput' for '

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 12:36 PM Tom Browder  wrote:
> On Fri, Feb 21, 2020 at 12:05 PM Brian  wrote:
> > Thanks, I will read the page in detail later. Meanwhile, I did a quick
> > search on the page for "mailname" and didn't get anything. Anyway, what
> > I really wanted to know was what function *you* thought /etc/mailname
> > played in OpenSMTPD because it would determine what you chose for it.
> >
> > On Exim it is used to qualify a local part without a domain name. After
> > I installed OpenSMTPD it seems to me that this is also what OpenSMTPD
> > does. In other words, if I had mailname as gmail.com, a mail I send to
> > tombrowder (no domain name) would go to tombrow...@gmail.com.
>
> Brian, you may be right. I cannot find anything in the man pages, but
> it may have been stated during the installation of the Debian package.
> I'll uninstall and reinstall to see if I can capture the
> instructions...

Okay, here are the instructions, just as you said:

The "mail name" is used as the domain name in the email address for
messages that only have a "local part" (such as
  │  or ). It should be a fully qualified domain
name (FQDN) that you are entitled to use.
  │
  │ For instance, to allow the local host to generate mail with
addresses such as , set the
  │ system mail name to "example.org".

So, I guess I can trust opensmtpd to do the right thing if I set up
its configuration properly. And for the DNS just make every domain
have its own mail server (as long as everything eventually maps the
the correct server IP listening on port 25).

Thanks.

-Tom

Re: Choice of "mailname" for mail server: suggestions welcome

[Brian]

On Fri 21 Feb 2020 at 12:36:38 -0600, Tom Browder wrote:

> On Fri, Feb 21, 2020 at 12:05 PM Brian  wrote:
> > On Fri 21 Feb 2020 at 11:22:58 -0600, Tom Browder wrote:
> >
> > > On Fri, Feb 21, 2020 at 09:36 Brian  wrote:
> ...
> > Thanks, I will read the page in detail later. Meanwhile, I did a quick
> > search on the page for "mailname" and didn't get anything. Anyway, what
> > I really wanted to know was what function *you* thought /etc/mailname
> > played in OpenSMTPD because it would determine what you chose for it.
> >
> > On Exim it is used to qualify a local part without a domain name. After
> > I installed OpenSMTPD it seems to me that this is also what OpenSMTPD
> > does. In other words, if I had mailname as gmail.com, a mail I send to
> > tombrowder (no domain name) would go to tombrow...@gmail.com.
> 
> Brian, you may be right. I cannot find anything in the man pages, but
> it may have been stated during the installation of the Debian package.
> I'll uninstall and reinstall to see if I can capture the
> instructions...

Instead, you can do 'dpkg-reconfigure opensmtpd'.

-- 
Brian.

Re: Modern automounters and umount

[songbird]

Thomas Schmitt wrote:
...
> Does anybody here experience similar stubbornness of automounting ?
> If so: How to unmount a DVD without ejecting it ?

  not having done much with DVDs recently i can't say much
about them.  i can say that i really hate having something 
automounted even when i tell the system to not do anything 
with it.

  i've not had a chance to test the recent MATE update to 
see if that is still an issue or not, but it sure did get 
my peeve up.

  my camera was being captured by gio or some other part of 
the desktop and i had ticked all the boxes and options to 
tell the desktop that i didn't want it touched at all when 
i plugged it in.

  in my script i have to do some fiddling around to make 
sure the device is unmounted and then remounted where i want
it (and that it is actually available).  i did get the 
script working and that is where it has to sit for now.  :)

  check to see if some desktop or other system widget has got 
ahold of it (udev, gio, gvfs, udisk2 and no, i don't know all 
other possible names or details about things that might be 
doing this sort of interference).

  good luck!


  songbird

Re: Thunderbird no longer opens links

[Thomas George]

Wait for a new update? It happened before.

In the meantime I am forwarding the emails to thunderbird on a 
raspberrypi desktop. On that thunderbird the links can be opened.


On 2/19/20 6:06 PM, Boas Kirui wrote:

what do I do now,should I re-enable the virtual syscall?

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 11:04 AM Henning Follmann
 wrote:
> On Fri, Feb 21, 2020 at 08:47:36AM -0600, Tom Browder wrote:
> > On Fri, Feb 21, 2020 at 08:37 Henning Follmann 
...
> For years I operated a couple of sendmail installations. That and the
> O'Reilly Sendmail book tought me a lot.
> Today I prefer postfix. There is a german book from Peer Heinlein.
> This is an excellent source if you want to set up a multidomain
> mailserver completely driven by a LDAP directory.

That got some good reviews--sorry my old German-speaking roommate is not nearby.

Thanks, Henning.

-Tom

Re: Choice of "mailname" for mail server: suggestions welcome

[Tom Browder]

On Fri, Feb 21, 2020 at 5:09 AM Tom Browder  wrote:
>
> I am preparing servers to use with OpenSMTPD and Sympa to provide mail
and mailing list service.
...

After considering all the suggestions, I have prepared a plan, using a bit
of pseudo code, to describe what I believe I need to do.

Interested parties can view at this gist:

  https://gist.github.com/tbrowder/0be832c0405d54021fa730b791629643

I appreciate all the help for, IMHO, a very complicated subject.


-Tom

Re: Modern automounters and umount

[Mark Allums]

On 2/21/20 9:23 AM, Jonathan Dowland wrote:

On Fri, Feb 21, 2020 at 08:53:50AM -0500, Stefan Monnier wrote:

Indeed.  And FWIW, you should/might be able to avoid the `sudo` by
asking udisks2 to do the unmount


Yep. It requires you to specify the device, rather than the filesystem
mount point:

    $ udisksctl unmount -b /dev/sdb1

But does not require superuser, if udisks2 mounted it on your user's
behalf in the first place.



Explain this, then:

george@martha:~$ udisksctl unmount -b /dev/sdb1
Unmounted /dev/sdb1.
george@martha:~$ sudo e2fsck -c -c -k -p -f -C 0 /dev/sdb1
/dev/sdb1 is in use.
e2fsck: Cannot continue, aborting.

Thnx,

Mark

Re: Modern automounters and umount

[Gene Heskett]

On Friday 21 February 2020 22:58:10 Mark Allums wrote:

> On 2/21/20 9:23 AM, Jonathan Dowland wrote:
> > On Fri, Feb 21, 2020 at 08:53:50AM -0500, Stefan Monnier wrote:
> >> Indeed.  And FWIW, you should/might be able to avoid the `sudo` by
> >> asking udisks2 to do the unmount
> >
> > Yep. It requires you to specify the device, rather than the
> > filesystem mount point:
> >
> >     $ udisksctl unmount -b /dev/sdb1
> >
> > But does not require superuser, if udisks2 mounted it on your user's
> > behalf in the first place.
>
> Explain this, then:
>
> george@martha:~$ udisksctl unmount -b /dev/sdb1
> Unmounted /dev/sdb1.
> george@martha:~$ sudo e2fsck -c -c -k -p -f -C 0 /dev/sdb1
> /dev/sdb1 is in use.
> e2fsck: Cannot continue, aborting.
>
> Thnx,
>
> Mark
Is there a user cd'd into it?  That locks it up.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Encrypted lvm error messages at boot

[john doe]

Hi all,

I just installed Debian buster with encrypted LVM, when starting Debian
I see the following:

"  Volume group "debian-buster-vg" not found
  Cannot process volume group debian-buster-vg
  Volume group "debian-buster-vg" not found
  Cannot process volume group debian-buster-vg"

It works but I would like to get rid of those error messages.

Any thoughts on how to do that is appriciated?

--
John Doe