On Thu, Jul 16, 2020 at 09:54:06PM -0700, Andy Ruhl wrote:
> What about booting from install media and dropping /rescue/sh into
> whatever the defined shell path is? Isn't that a statically linked
> binary that should work pretty much anywhere? Isn't that kinda what
> it's for?
Yes, that works
On Thu, 16 Jul 2020, Greg Troxel wrote:
What I would do is
export EDITOR=ed
export VISUAL=ed
Perhaps also "export TERM=cons25" would help.
I think that last one was the one that got me past having to
learn a bit of ed for the first time in probably thirty years.
vipw worked fine once
On Thu, Jul 16, 2020 at 9:28 PM Martin Husemann wrote:
> Either set TERM and export it, or instead of chsh do some simple hack
> like:
>
> cp /bin/csh /usr/pkg/bin/tcsh
I'm not claiming this will work, just looking for feedback.
What about booting from install media and dropping
On Thu, Jul 16, 2020 at 06:21:57PM -0400, Bob Bernstein wrote:
> On Thu, 16 Jul 2020, Greg Troxel wrote:
>
> > 2) boot single user, by hitting space during the countdown and "boot
> > -s". hit return for sh. Once there, type "fsck -p" to fix any issues.
> > Then "mount -a". Then put back the
If you actually bricked your root account: boot single user and chsh to
/bin/sh or /bin/csh.
I always keep /bin/sh as my root shell and do
if [ -x /usr/pkg/bin/tcsh ]; then
exec /usr/pkg/bin/tcsh
fi
in /root/.profile. I know why, and now you do too...
On Thu, Jul 16, 2020 at 10:16 PM
Bob Bernstein writes:
> On Thu, 16 Jul 2020, Greg Troxel wrote:
>
>> 2) boot single user, by hitting space during the countdown and "boot
>> -s". hit return for sh. Once there, type "fsck -p" to fix any
>> issues. Then "mount -a". Then put back the shell with pkg_add, or
>> use vipw to change
On Thu, 16 Jul 2020, Greg Troxel wrote:
2) boot single user, by hitting space during the countdown and
"boot -s". hit return for sh. Once there, type "fsck -p" to
fix any issues. Then "mount -a". Then put back the shell with
pkg_add, or use vipw to change your shell back to /bin/sh.
vipw
On Thu, 16 Jul 2020 at 21:16, Bob Bernstein wrote:
>
> There's a long back-story to this event, but it's not important.
>
> Suffice to say that I removed all the packages from my system,
> including the shell I like at /usr/pkg/bin/tcsh, and now all my
> attempts to login are rejected because the
On Wed, 15 Jul 2020 at 14:25, Chavdar Ivanov wrote:
>
> Checking once more, it would appear I haven't tried qemu-nvmm on the
> kernel from 12-th of July; the last successful execution was on the
> 11th with a kernel and system from the 9th of July, so the window is a
> bit wider than initially
Bob Bernstein writes:
> There's a long back-story to this event, but it's not important.
>
> Suffice to say that I removed all the packages from my system,
> including the shell I like at /usr/pkg/bin/tcsh, and now all my
> attempts to login are rejected because the shell cannot be found.
>
> Is
There's a long back-story to this event, but it's not important.
Suffice to say that I removed all the packages from my system,
including the shell I like at /usr/pkg/bin/tcsh, and now all my
attempts to login are rejected because the shell cannot be
found.
Is there a work-around?
Thank
I thought that setting up a bridge was as trivial as the following, but
apparently not as the ping fails. bridge0 doesn't even learn box2's
ethernet address. What am I missing?
Cheers,
Patrick
# ++
# ||
# box1
On Wed, 15 Jul 2020, Greg A. Woods wrote:
These are my relevant hacks which I make directly to
pkgsrc/mk/defaults/mk.conf:
PKGMAKECONF = /etc/mk.conf
PKGSRC_MAKE_ENV += USER=${USER:Q}
WRKOBJDIR ?=/var/package-obj/${USER}
DISTDIR ?= /var/package-distfiles
PACKAGES ?=
13 matches
Mail list logo
