From owner-freebsd-questions@freebsd.org Sat May 2 10:13:50 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 885582CB005 for ; Sat, 2 May 2020 10:13:50 +0000 (UTC) (envelope-from per@hedeland.org) Received: from mailout.easydns.com (mailout.easydns.com [64.68.202.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49DlMK4By9z41y7 for ; Sat, 2 May 2020 10:13:49 +0000 (UTC) (envelope-from per@hedeland.org) Received: from localhost (localhost [127.0.0.1]) by mailout.easydns.com (Postfix) with ESMTP id 84D84A1AD5; Sat, 2 May 2020 10:13:48 +0000 (UTC) Received: from mailout.easydns.com ([127.0.0.1]) by localhost (emo13-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DkpEJaftHFug; Sat, 2 May 2020 10:13:48 +0000 (UTC) Received: from hedeland.org (81-228-157-209-no289.tbcn.telia.com [81.228.157.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easydns.com (Postfix) with ESMTPSA id DF303A0FE5; Sat, 2 May 2020 10:13:46 +0000 (UTC) Received: from pluto.hedeland.org (pluto.hedeland.org [10.1.1.5]) by tellus.hedeland.org (8.15.2/8.15.2) with ESMTPS id 042ADhm1016684 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Sat, 2 May 2020 12:13:44 +0200 (CEST) (envelope-from per@hedeland.org) Subject: Re: Xdm var/log/xdm.log To: Polytropon Cc: freebsd-questions@freebsd.org References: <20200501051811.2b24d320.freebsd@edvax.de> <20200501053836.76a32eaf.freebsd@edvax.de> <20200501060500.4a89db8b.freebsd@edvax.de> <24235.45694.473965.863585@jerusalem.litteratus.org> <20200501073326.ace7ae66.freebsd@edvax.de> <24236.3691.152243.385927@jerusalem.litteratus.org> <20200501151725.635f7b29.freebsd@edvax.de> <16588249-02ee-b4a1-dbd2-1ec8972ff023@hedeland.org> <20200502095144.787d9d0a.freebsd@edvax.de> From: Per Hedeland Message-ID: <8bdb0453-8c73-0e8a-cf4a-693d95f93eca@hedeland.org> Date: Sat, 2 May 2020 12:13:43 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 MIME-Version: 1.0 In-Reply-To: <20200502095144.787d9d0a.freebsd@edvax.de> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49DlMK4By9z41y7 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of per@hedeland.org has no SPF policy when checking 64.68.202.10) smtp.mailfrom=per@hedeland.org X-Spamd-Result: default: False [0.09 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; RECEIVED_SPAMHAUS_PBL(0.00)[209.157.228.81.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.60)[-0.600,0]; NEURAL_HAM_LONG(-0.35)[-0.352,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[hedeland.org]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[10.202.68.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16686, ipnet:64.68.200.0/22, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.24)[ip: (0.22), ipnet: 64.68.200.0/22(-0.23), asn: 16686(1.28), country: CA(-0.09)]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 May 2020 10:13:50 -0000 On 2020-05-02 09:51, Polytropon wrote: > On Sat, 2 May 2020 09:09:35 +0200, Per Hedeland wrote: >> On 2020-05-01 15:17, Polytropon wrote: >>> On Fri, 1 May 2020 07:56:27 -0400, Robert Huff wrote: >>>> >>>> Polytropon writes: >>>> >>>>> > > > Ok, I will add xsession. >>>>> > > >>>>> > > NB: .xsession (the dot is significant). >>>>> > > >>>>> > > Or you can do the following, as you said you already have >>>>> > > a .xinitrc (which xdm will ignore, as mentioned): >>>>> > > >>>>> > > % cp .xinitrc .xsession >>>>> > >>>>> > From my home directory: >>>>> > >>>>> > lrwxrwxr-x 1 huff huff 8 May 1 01:19 .xsession -> .xinitrc >>>>> > >>>>> > This implies you want the same environment from both. >>>>> >>>>> Will usually work, but doesn't keep C shell initialization >>>>> (environmental variables, aliases, settings), which might >>>>> not be a problem if you're not using the C shell for dialog >>>>> sessions or if you concentrate on GUI entirely. :-) >>>> >>>> Once I start X, I do pretty much everything within it. For the >>>> rest I console-switch. >>>> (And the first line of the file is "#! /bin/sh". :-) ) >>>> What is there that one might wish to do that can't be handled out >>>> of an xterm? >>> >>> If I remember correctly, if you use xdm, and start an X terminal >>> inside the X session, your settings from .cshrc will not be in >>> effect due to the fact that the invoked shell is not a login shell. >> >> I believe you are confusing .cshrc with .login - .cshrc is read by >> *every* instance of [t]csh unless the -f option is used, while .login >> is indeed only read by login shells (and thus pretty much useless). > > Yes, that's what "man csh" says... but decades ago it didn't > work. Well, "it" as in "every instance reads .cshrc" has definitely worked at least since the csh version shipped with 4.1BSD (1981) when I started using it, and continued to do so across the tcsh that was a set of source patches to csh, and the "merged" open-source version in FreeBSD. But you may of course have things *in* your .cshrc that e.g. makes most of it be skipped if it has already been read. > I remember that when using xdm with .xsession to launch > the user components of X, whenever I opened a terminal, my > C shell settings from .cshrc (!) weren't included, that's why > I invented the "cascading approach" for .xsession and .xinitrc. As I already wrote, "shell settings" can't be inherited across an exec, as you reported having in your .xsession: #!/bin/csh source ~/.cshrc exec ~/.xinitrc > That was a long time ago, but it still works. Or, whatever it was that you did that *actually* fixed your problem still works.:-) Sourcing .cshrc in a csh script also works of course, but the csh instance running the script has already sourced it (unless it was started with -f), so it isn't likely to be useful. > I don't know how other display managers handle things. I did > not need that for slim, and I got rid of gdm quite quickly > because it didn't care for _any_ user configuration file (no > .xsession, no .xinitrc, no nothing). I've only ever "actively" used xdm, haven't seen a need for anything else. >> FWIW, while I use tcsh as my interactive shell, both my .xsession and >> .xinitrc have #!/bin/sh (as all scripts should:-), [...] > > I think the #!/bin/sh in .xinitrc is just for the reader, because > the manual of startx says that it will use /bin/sh for execution > if .xinitrc regardless. However, it's not wrong and it doesn't > do any harm. Similarly, there is no mention that this file has > to be executable (+x attribute set), but again, it's probably > not wronger than the #!/bin/sh line... :-) The execute permissions are certainly required (and shebang strongly recommended) if you want to 'exec' .xinitrc from .xsession, though. --Per