Date: Mon, 30 Oct 2017 18:37:05 +1100 From: Rami <freebsd@posteo.co> To: freebsd-questions@freebsd.org Subject: Re: Update Jail base binaries Message-ID: <868a4dc2d629f410cd2531d07ce725b5@posteo.net> In-Reply-To: <7da8f9db-94c3-6f76-9345-1a44a40418ca@posteo.net> References: <3b5d8677-e6da-845a-b208-5d7f9d93381c@posteo.net> <7da8f9db-94c3-6f76-9345-1a44a40418ca@posteo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi everyone, I have an issue which I got aware of by accident couple of days ago while I was upgrading a port in the jail. I have a jail created using ezjail and running Gitea port in it. The host system was back then 11.0. Recently Gitea got updated so after upgrading the installed port in the jail, the service started complaining as below ~ # service gitea start daemon: illegal option -- S usage: daemon [-cfr] [-p child_pidfile] [-P supervisor_pidfile] [-t title] [-u user] command arguments ... After a bit of investigating we figured out that the binaries in the jail are behind the host (and the jail kernel release). please check below (note I updated the host using freebsd-update and the jail using ezjail-admin update -u) The jail where the gitea is running # freebsd-version 11.1-RELEASE-p2# uname -a #uname -a FreeBSD git.jail 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug 9 11:55:48 UTC 2017 _ROOT@AMD64-BUILDER.DAEMONOLOGY.NET_:/usr/obj/usr/src/sys/GENERIC amd64 # sha256 /usr/sbin/daemon SHA256 (/usr/sbin/daemon) = 2f1d9b434cae89c67aefa9798b87fd97bcde2f70b2ba0140b7052ae6536aaf8a # /usr/sbin/daemon _USAGE: DAEMON [-CFR] [-P CHILD_PIDFILE] [-P SUPERVISOR_PIDFILE]_ [-T TITLE] [-U USER] COMMAND ARGUMENTS ... The host ~ % freebsd-version 11.1-RELEASE-p2~ % #uname -a _FREEBSD SERVER-LINODE-1-GIT 11.1-RELEASE-P1 FREEBSD 11.1-RELEASE-P1 #0: WED AUG 9 11:55:48 UTC 2017 __ROOT@AMD64-BUILDER.DAEMONOLOGY.NET__:/USR/OBJ/USR/SRC/SYS/GENERIC AMD64_~ % sha256 /usr/sbin/daemon SHA256 (/usr/sbin/daemon) = 2b029a5c274c6292870caf35470041c2553b768346bb001c97d447877bc9caf5~ % /usr/sbin/daemon _USAGE: DAEMON [-CFRS] [-P CHILD_PIDFILE] [-P SUPERVISOR_PIDFILE]__ [-U USER] [-O OUTPUT_FILE] [-T TITLE]__ [-L SYSLOG_FACILITY] [-S SYSLOG_PRIORITY]_ [-T SYSLOG_TAG] [-M OUTPUT_MASK] _COMMAND ARGUMENTS ..._ I will always update the jails using # ezjail-admin update -u and the ports _# ezjail-admin update -P So it seems the kernel been updated yet not the binaries.... can anyone please advise me to what is the best way to keep the whole system kernel, base, and ports up to date in the jail (and keep the base binaries and kernel match the same release) Thanks so much Rami From owner-freebsd-questions@freebsd.org Mon Oct 30 13:20:27 2017 Return-Path: <owner-freebsd-questions@freebsd.org> Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 118CDE5CD6F for <freebsd-questions@mailman.ysv.freebsd.org>; Mon, 30 Oct 2017 13:20:27 +0000 (UTC) (envelope-from olivares14031@gmail.com) Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD0B82A22 for <freebsd-questions@freebsd.org>; Mon, 30 Oct 2017 13:20:26 +0000 (UTC) (envelope-from olivares14031@gmail.com) Received: by mail-vk0-x233.google.com with SMTP id t184so8055684vka.6 for <freebsd-questions@freebsd.org>; Mon, 30 Oct 2017 06:20:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Z/W2Oqk29Jbx2hFfJhZhHIyL2+2aO7qLDFsG5v+btcg=; b=TJRw6bzrH/5vEJAmZjlREeIk/g4TjwbPa0PAZu7ZNsPEVFBYW4MqMdTOXxbADLaffk BbQmuI0xTIJEbOXmQ5OUM5nKlUiBGkxYd3SnCknrISUA370KgnqBjkbAF1uIb2xY7+z0 a1gHkgTp00r4ohRDV7jMdnszBvd4eOKqJyOqpSDYx5HAEBgaC3P5eY+A8bCzok7KsQXE Yy25FVXJFtdi1+wL0f/QsqLkwtwu/5qMoUtlMbusts97ox8DZgArB5ld8ljZOlFuOyKu 3l1jRCAi2kLkz6J9zXagmy/eWpNis2KwIv2u5TlakT+/f41+bu1jhK02aoa0MvBXgpnd 1Qog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Z/W2Oqk29Jbx2hFfJhZhHIyL2+2aO7qLDFsG5v+btcg=; b=Udb3pUiqc9iUhSJb/IBIqK6DcgrFukG7aSJ96aeETLRUpsaF1pGrXQrH65Dhba7RuT Pe8irnrEA+3q0LxiY8Sd+w8lz7lOzrkhO7XzmeL9FgdCIseeY5xn1AyuYwznfC95lE0Q 6OCWoyc2ccAg8DmS3YwZrxWtHMxJwg2iX8XjFU8e9vLAUxGOdmWO0oAmZlvOhOg3/bKu bkRLDX5/gN2YZEBZP75varUKohzB3C2KSmb/jbRnepab6e+Usz6YoFw0CevGVvJhzTsW UrPx+Bx6UeN42/+bB50Ihevlynv3JwPkt11jiGeeg6ifclIjfMdyER4Y6+yz8132qYTb Tm5g== X-Gm-Message-State: AMCzsaWkqwFXoCzZ7KreFzQhSOUHVaQnCXAJ1jgsvNGPsNw0W3DJ9K+W XgvK6z6Vip/dIYqz0q868m8BBvG41xAQ5g1t99/8YA== X-Google-Smtp-Source: ABhQp+QUBOBVUV8gPAaKs36I7uGe5i90h7fSBkDKN9yyMMRPtgRf2LR6dsUv99VigNASx4Da4emyMS+/XGSLxcIZEfU= X-Received: by 10.31.33.3 with SMTP id h3mr6967233vkh.125.1509369625577; Mon, 30 Oct 2017 06:20:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.1.243 with HTTP; Mon, 30 Oct 2017 06:20:25 -0700 (PDT) In-Reply-To: <20171027035803.14dca7c9.freebsd@edvax.de> References: <CAJ5UdcOzd-4g=9ZcL5drTdzBd864=8qb5FjvtMmru2Sm0-PMfg@mail.gmail.com> <20171026215855.67642f40.freebsd@edvax.de> <CAJ5UdcNKLOM7bN1Ztzn0QSjy7oHXF6mupqhy3RO2T9GjPvPMwg@mail.gmail.com> <20171027035803.14dca7c9.freebsd@edvax.de> From: Antonio Olivares <olivares14031@gmail.com> Date: Mon, 30 Oct 2017 08:20:25 -0500 Message-ID: <CAJ5UdcPgSV3QmH1kLMoGtsGf0OO-npUVbfUmeEmB-gtYu-sU5A@mail.gmail.com> Subject: Re: autologin from console not working on FreeBSD-11.1p2 To: Polytropon <freebsd@edvax.de> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 30 Oct 2017 13:20:27 -0000 On Thu, Oct 26, 2017 at 8:58 PM, Polytropon <freebsd@edvax.de> wrote: > On Thu, 26 Oct 2017 20:35:55 -0500, Antonio Olivares wrote: >> On /etc/ttys I have in ttyv0 and changed Pc to Al. And the entry in >> /etc/gettytab is the placed at the very end of the file. >ttyv0 "/usr/libexec/getty Al" xterm on secure > That is correct. > > >ttyv0 "/usr/libexec/getty Al" xterm on secure >> In one machine it >> has xterm , while the older 9.2* machine has cons25 as I just copied over. >> Maybe something changed? > > Yes. The default "text mode" (basically gone with the sc -> vt move) > now is xterm. > > > >> I will add the tc part over and see if it works on >> Monday. > > As you can see from "man gettytab", tc is "table continuation", > and from a working example I think this should be included. > > > >> I will have workshop tomorrow and may not get a chance to check if >> adding the tc part makes it work. I am using shell $ sh and have >> ~/.xinitrc and ~/.profile are correct with the test if console then startx >> and that works. > > According to "man sh", using ~/.profile is the correct approach. > > As you're probably not going to interact with /bin/sh much (as > it is the default scripting shell, not the default dialog shell), > it probably doesn't matter as all you need is something to bring > up X with a desktop environment. > > > >> Just that I am getting password prompt. I login to shell >> then startx, using lumina desktop. > > The problem probably is with the gettytab entries. Check them > when you can, and compare with the solution mentioned. It is > of course possible that during the course of FreeBSD development, > things have changed in a way that it doesn't work anymore... :-/ > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... now adding the "tc=pc' part after al=olivares:tc=Pc did the job. It automatically logins as the other machines. As always thank you for your help. in /etc/ttys I changed Pc to Al as follows: ttyv0 "/usr/libexec/getty Al" xterm on secure in /etc/gettytab: # log me in automatically A|Al|Autologin console:\ ht:np:sp#115200:al=olivares:tc=Pc: and it now works. Best Regards, Antonio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?868a4dc2d629f410cd2531d07ce725b5>