GPT autopartion during install

[Sivan !]

In new desktop computer with a new ssd, the 6.8 amd installer during
auto partition without any user choices, created the numerous device
(partition)s, which is strange:

For eg  rsd0a-rsd0p  ... rsd9a-rsd9p, ie 16x10=160 device partitions ?
starting with rsd* ;  Similarly numerous entries seen for every other
type of 'dev'. Attaching a text file of ls/dev output.

[Sivan !]

On Fri, 19 Feb 2021 at 13:14, Sivan ! <[hidden email]> wrote:
>
> In new desktop computer with a new ssd, the 6.8 amd installer during
> auto partition without any user choices, created the numerous device
> (partition)s, which is strange:
>
> For eg  rsd0a-rsd0p  ... rsd9a-rsd9p, ie 16x10=160 device partitions ?
> starting with rsd* ;  Similarly numerous entries seen for every other
> type of 'dev'. Attaching a text file of ls/dev output.

text file attached now.

[Peter N. M. Hansteen-3]

On Fri, Feb 19, 2021 at 01:14:07PM +0530, Sivan ! wrote:
> In new desktop computer with a new ssd, the 6.8 amd installer during
> auto partition without any user choices, created the numerous device
> (partition)s, which is strange:
>
> For eg  rsd0a-rsd0p  ... rsd9a-rsd9p, ie 16x10=160 device partitions ?
> starting with rsd* ;  Similarly numerous entries seen for every other
> type of 'dev'. Attaching a text file of ls/dev output.
 
Your second mail here seems to contain the output of 'ls /dev'.

Sure, the device nodes exist. That does not mean that the partitions
are created. Check the output of something like

$ doas disklabel sd0

(replace sd0 with whatever your actual storage device is recognized as)
and you'll see what partitions you have and their sizes.

The install guide part of the FAQ (and actually all of the FAQ) is well
worth your time reading.

All the best,
Peter


--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

[Sivan !]

I am sorry, usually replyall is the default in my mail settings.
Didn't realize that it was a reply to you.  Man pages are thorough and
good for
those who grew up in the unix/linux environment, but I am sorry, I
have trouble deciphering the instructions for syntax. There aren't
enough
examples in man pages that illustrate the use of the commands for
someone with copy and paste level of system admin skills.

I sent another message a moment ago, that must also have been sent to
you as a "reply" instead of as a "replyall" to the list.

Copying that message below:

doas is supposed to have been installed by default in openbsd 6.8, but
> I get the error doas is not enabled, /etc/doas.conf: No such file or
> directory, the posts related to doas online assume that /etc/doas.conf
> already exists in the user's computer, it is not
> there.  I tried locating doas in ports, I tried pkg_add doas, it does not work.
>
> -bash-5.0$ sudo pkg_add doas
> quirks-3.441 signed on 2021-02-17T11:25:54Z
> Can't find doas
>
I tried this also:

>=5.73:devel/kf5/kcoreaddons STEM->=5.73:devel/kf5/ki18n STEM->=5.73:devel/kf5/kpty STEM->=5.73:devel/kf5/kservice x11/qt5/qtbase,-main
B-deps: STEM->=1.5.1:devel/ninja
STEM->=5.73:devel/kf5/extra-cmake-modules archivers/xz devel/cmake
devel/gettext,-tools lang/python/3.8 x11/qt5/qttools,-main
R-deps:
Archs: aarch64 amd64 arm i386 mips64 powerpc powerpc64 aarch64 alpha
amd64 arm hppa i386 mips64 mips64el powerpc sparc64

-bash-5.0$ cd /usr/ports/devel/kf5/kdesu
-bash-5.0$ ls
CVS      Makefile distinfo patches  pkg
-bash-5.0$ cd /usr/ports/devel/kf5/kdesu/pkg
-bash-5.0$ ls
CVS   DESCR PLIST
-bash-5.0$ cd /usr/ports/devel/kf5/kdesu
-bash-5.0$ cd /usr/ports/devel/kf5/kdesu/distinfo
-bash: cd: /usr/ports/devel/kf5/kdesu/distinfo: Not a directory
-bash-5.0$ cd /usr/ports/devel/kf5/kdesu/CVS
-bash-5.0$ ls
Entries    Repository Root       Tag
-bash-5.0$ cd /usr/ports/devel/kf5/kdesu/CVS/Entries
-bash: cd: /usr/ports/devel/kf5/kdesu/CVS/Entries: Not a directory
-bash-5.0$ cat Entries
D/patches////
D/pkg////
/Makefile/1.13/Mon Sep  7 14:48:46 2020//TOPENBSD_6_8
/distinfo/1.12/Mon Sep  7 14:48:46 2020//TOPENBSD_6_8
-bash-5.0$ cat Repository
ports/devel/kf5/kdesu
-bash-5.0$ make
make: no target to make.
-bash-5.0$ make doas
make: don't know how to make doas
Stop in /usr/ports/devel/kf5/kdesu/CVS
-bash-5.0$ make install doas
make: don't know how to make install
Stop in /usr/ports/devel/kf5/kdesu/CVS
-bash-5.0$ make-install doas
-bash: make-install: command not found
-bash-5.0$

Don't know how to move forward. Please help

Thank you.

ReplyForward

Compose:
Doas

Peter N. M. Hansteen, [hidden email]
I am sorry, usually replyall is the default in my mail settings.
Didn't realize that it was a reply to you.  Man pages are thorough and
good for
those who grew up in the unix/linux environment, but I am sorry, I
have trouble deciphering the instructions for syntax. There aren't
enough
examples in man pages that illustrate the use of the commands for
someone with copy and paste level of system admin skills.

I sent another message a moment ago, that must also have been sent to
you as a "reply" instead of as a "replyall" to the list.

Copying that message below:

> > Thank you for confirming that this is not unusual. I checked the
> > output of sudo disklabel sd0, it shows 16 partitions, looks alright.
> > doas is supposed to have been installed by default in openbsd 6.8, but
> > I get the error doas is not enabled, /etc/doas.conf: No such file or
> > directory, the posts related to doas online assume that /etc/doas.conf
> > already exists in the user's computer, it is not
> > there.  I tried locating doas in ports, I tried pkg_add doas, it does not work.
>
> doas is part of the base install. You need to create the config file to enable it.
> Check man doas.conf for guidance and a suggested config.
>
> Also, please keep the discussion on the list (to or cc).
>
> Cheers,
>
> --
> Peter N. M. Hansteen, member of the first RFC 1149 implementation team
> http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
> "Remember to set the evil bit on all malicious network traffic"
> delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds

Sivan

[Peter N. M. Hansteen-3]

On Fri, Feb 19, 2021 at 03:53:38PM +0530, Sivan ! wrote:
> Didn't realize that it was a reply to you.  Man pages are thorough and
> good for
> those who grew up in the unix/linux environment, but I am sorry, I
> have trouble deciphering the instructions for syntax. There aren't
> enough
> examples in man pages that illustrate the use of the commands for
> someone with copy and paste level of system admin skills.

If your regular user on the box is the one you created during install,
it's in the wheel group. My doas.conf is for some reason more cluttered
but I think a simple

permit :wheel

(one line!) would work to have any user in the wheel group perform
privileged commands subject to entering their password correctly.

Then again, if you break things really badly, you can always reinstall ;P

- P

--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

[Jean-Pierre de Villiers]

You'll find plenty of examples in the directory "/etc/examples".  It
also helps that many (all?) programs written for the OpenBSD project are
able to check the syntax of their own configuration files while printing
any errors to standard output, including doas.

Regards,
Jean-Pierre de Villiers

[harold felton]

i noticed the newbie-q earlier and am not sure the full-thread,
but the comment below is the "correct" answer for most cases:
ie - look in /etc/examples if the config-file-you-need isnt there yet...

the reason i am chiming in is because i wrote a "crude" script
that i will enclose below - because i found myself often having
the problem that i would make-a-change to /etc/doas.conf and
the lock-myself-out because of user-error...  so...

enclosed is a videos.sh script - like you would use for vipw...

hth, h.

> You'll find plenty of examples in the directory "/etc/examples".  It
> also helps that many (all?) programs written for the OpenBSD project are
> able to check the syntax of their own configuration files while printing
> any errors to standard output, including doas.

#!/bin/sh
#
# hjf latest mod: 2020-04-04 @ 09:30 PDT
#
## vidoas.sh
#
## this is a basic copy/update from eradman at
## http://eradman.com/posts/ut-shell-scripts.html
## PATTERN singleton try/assert()
##
## GOAL try to create a vidoas pgm like visudo...
## ASSUMPTIONS interactive edits, allowing re-edits post-run, ...
export DOASFILE="/etc/doas.conf"
export TTY=`tty`
export USR=`whoami`
export VIDOAS=`basename $0`
export END_STRING="$VIDOAS: succeeded."
export TEST01=" doas-pw for initial copy..."
export TEST02=" edit of doas-file..."
export TEST03=" permissions of valid doas-file..."
export TEST04=" doas-pw for final replacement... "
export DEBUG_STRING=" \
1. incorrect $TEST01 \n \
2. incorrect $TEST02 \n \
3. incorrect $TEST03 \n \
4. incorrect $TEST04 \n"
export TESTING_STRING="Currently 4 possible tests: \n$DEBUG_STRING "
export DODEBUG=1
export DONORMAL=1
export DOHELPFUL=
export START_STRING="$VIDOAS: MUST supply password before AND after edits...
"
export XPLAINING_STRING="Password is normally required twice... \n \
due to checks at Steps 1. and 4. from .... \n$DEBUG_STRING"
function setup {
export LAUNCH_CMDS=`mktemp`
export PERMIT_FILE=`mktemp`
echo "permit $USR" > $PERMIT_FILE
export VI_FILE=`mktemp`
} ; setup ; # call self-setup...`
function teardown {
rm -f $LAUNCH_CMDS
rm -f $VI_FILE
}
# SINGLETON-setup
typeset -i test_runs=0
function try { this="$1"; }
trap 'printf "$0: exit code $? on line $LINENO\nFAIL: $this\n"; exit 1' ERR
function assert {
let tests_run+=1
[ "$1" = "$2" ] && { echo -n "."; return; }
printf "\nFAIL: $this\n'$1' != '$2'\n"; teardown; exit 1
}
# MAIN-STARTS-HERE (assuming setup;)
#
try "0. TESTING..."
[ "$DODEBUG" ] && { echo $TESTING_STRING; }
[ "$DOHELPFUL" ] && { echo $XPLAINING_STRING; }
[ "$DONORMAL" ] && { echo $START_STRING; }
let tests_run-=20
[ "$DODEBUG" ] && { echo "permit file"; }
assert "`doas -C $PERMIT_FILE echo`" "permit"
[ "$DODEBUG" ] && { echo "vi file"; }
assert "`doas -C $VI_FILE echo`" "deny"
typeset -i test_runs=0
# let tests_run=0
[ "$DODEBUG" ] && { echo "vi file"; }
assert "`doas -C $VI_FILE echo`" "deny"
#TEST00m1=`doas -C $PERMIT_FILE echo`
#TEST00m2=`doas -L`
# I need some way to check ownership of tty a/o make a nwe one
# in case i have su'ed into this program somehow... sigh...
#if [ $? ]; then
#if [ "$TEST00m2" != "permit" ]; then
# echo "cannot do ANY doas-stuff, maybe login as hfeltonadmin ?"
#fi
[ "$DODEBUG" ] && { echo "crossing zero"; }
assert "`echo 't'`" "t"
#assert "`doas -C $PERMIT_FILE echo`" "permit"
#try "1. create an edit-able copy..."
try "1. $TEST01"
cat > $LAUNCH_CMDS <<-'LAUNCHER'
doas -L
doas cp $DOASFILE $VI_FILE
doas -L
LAUNCHER
# fd/syserr catches bad passwords here...
assert "`. $LAUNCH_CMDS 2>&1`" ""
#try "2. go ahead and vi-edit ..."
try "2. $TEST02"
cat > $LAUNCH_CMDS <<-'LAUNCHER'
# dont let kshrc-stuff run...
export ENV=''
( sh -i -c "vi $VI_FILE <$TTY >$TTY" )
doas -C $VI_FILE
LAUNCHER
# check for syntax errors from editting...
assert "`. $LAUNCH_CMDS 2>&1`" ""
#try "3. post-edit-check for replacement permissions..."
try "3. $TEST03"
assert "`doas -C $VI_FILE -u $USR cp | cut -c 1-6 `" "permit"
#try "4. install the latest-greatest back..."
try "4. $TEST04"
assert "`doas cp $VI_FILE $DOASFILE 2>&1`" ""
# MAIN-ENDS-HERE....
#
#try "999. Testing ENDS..."
[ "$DODEBUG" ] && { echo; echo "PASS: $tests_run tests run"; }
[ "$DOHELPFUL" ] && { echo; echo "All $tests_run steps ok, so..."; echo
$END_STRING; }
[ "$DONORMAL" ] && { echo $END_STRING; }
#assert "`echo 't'`" "t"
##echo "vidoas.sh succeeded."
teardown; exit 0