From: vincele <vincele@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Fix utempter
Date: Thu, 15 Dec 2022 09:52:31 +0100 [thread overview]
Message-ID: <20221215085231.YRFWkF_e6ha5-ul_-nw93QmbyVN1gCUDMOZ_EDM_a7w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40988@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
New comment by vincele on void-packages repository
https://github.com/void-linux/void-packages/pull/40988#issuecomment-1352364036
Comment:
I think I have this problem:
<pre>
$ screen /dev/ttyUSB0 1500000
/dev/null/utmp: Not a directory
[screen is terminating]
$ screen -ln /dev/ttyUSB0 1500000
/dev/null/utmp: Not a directory
[screen is terminating]
$ screen -l /dev/ttyUSB0 1500000
/dev/null/utmp: Not a directory
[screen is terminating]
</pre>
But nor `-l` nor `-ln` seem to have any effect on that. I may have misunderstood their intent, though.
<pre>
-l and -ln
turns login mode on or off (for /etc/utmp updating). This can
also be defined through the deflogin .screenrc command.
</pre>
My screen version is still at 4.9.0_1
<pre>
$ xbps-query screen
architecture: x86_64-musl
build-options: ~multiuser
conf_files:
/etc/screenrc
/etc/skel/.screenrc
filename-sha256: 2434acac0bbcc05aa899b470d8e34b23b9c5a9f51d5d59b1562f5628708ef778
filename-size: 557KB
homepage: http://www.gnu.org/s/screen/
install-date: 2022-12-12 22:34 CET
install-script: 688B
installed_size: 898KB
license: GPL-3.0-or-later
maintainer: Frank Steinborn <steinex@nognu.de>
metafile-sha256: c9352d316e60e03d78309afcc84e3704c4e8fdcb6aaeb0f90e49409a5ba5bdde
pkgname: screen
pkgver: screen-4.9.0_1
repository: https://repo-default.voidlinux.org/current/musl
run_depends:
ncurses-libs>=5.8_1
pam-libs>=1.1.6_3
musl>=1.1.24_7
shlib-requires:
libncursesw.so.6
libpam.so.0
libc.so
short_desc: GNU screen manager with VT100/ANSI terminal emulation
source-revisions: screen:217a65562c
state: installed
</pre>
My naive question is: wouldn't it make sense to compile screen without utmp support ?
EDIT:
That may not be as easy as I thought:
<pre>
$ ./xbps-src show-options screen
=> screen-4.9.0_1: the following build options are set:
multiuser: (OFF)
</pre>
next prev parent reply other threads:[~2022-12-15 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 18:37 [PR PATCH] " leahneukirchen
2022-12-14 22:43 ` sbromberger
2022-12-14 23:39 ` vincele
2022-12-14 23:47 ` vincele
2022-12-15 8:52 ` vincele [this message]
2022-12-15 22:59 ` [PR PATCH] [Merged]: " leahneukirchen
2022-12-15 23:18 ` vincele
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221215085231.YRFWkF_e6ha5-ul_-nw93QmbyVN1gCUDMOZ_EDM_a7w@z \
--to=vincele@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).