Date: Fri, 05 Jan 2024 07:56:16 -0800 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Peter <pmc@citylink.dinoex.sub.org> Cc: freebsd-stable@freebsd.org, bapt@freebsd.org, alfix86@gmail.com, asiciliano@freebsd.org Subject: Re: ports-mgmt/portconfig surprize Message-ID: <20240105155617.03436679@slippy.cwsent.com> In-Reply-To: <ZZdAz2EM2htYzfX9@disp.intra.daemon.contact> References: <ZZdAz2EM2htYzfX9@disp.intra.daemon.contact>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <ZZdAz2EM2htYzfX9@disp.intra.daemon.contact>, Peter writes: > Folks, > > somebody got the idea to replace the dialog4ports options > configuring interface by something named 'ports-mgmt/portconfig'. > (And they did not even find it worth mentioning this in the > UPGRADING file.) > > Now this one looks terrible, the screen is garbled, and it is > quite unintellegible which line is currently entered. > See pictures here (old and new): > https://forums.freebsd.org/threads/2024q1-portbuild-trouble.91770/post-636816 > > What is happening: > I am starting a shell script. That fires up a bhyve. In the bhyve 'make' > is run with stdio connected to the second COM. > In the script on the host, bhyve is put in background, 'cu' is started > and connected to that second COM. There the dialog appears. > Since the script on the host is run from remote, it is run within > tmux. > Point is: it did work before. > > disappointed, > PMc > This should have been posted to freebsd-ports@. Next time use the correct ML. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org NTP: <cy@nwtime.org> Web: https://nwtime.org e^(i*pi)+1=0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240105155617.03436679>