Re: Config-/Dotfiles in CVS
On Fri, Dec 29, 2017 at 10:44:44AM +0100, Michael Hekeler wrote: > Hello all, > > in the past I used RCS on all machines for keeping configfiles in /home > or /etc or whatever. > Nearly everytime when I move to another machine I think that it would > be cool to have all of these repoistories centralized on a server. > So I thought I should convert all of these RCS to CVS. > > Most of my non-production machines are on *BSD, Debian or other OS and > when I want to install CVS everyone is screaming: "Don??t use it..." > > When I ask on internet for ideas how to keep configfiles under revision > control also everyone screams: "don??t use CVS..." and instead of > talking about concepts (symlinks, woring dir,...) most people give > ready-made solutions with git or whatever is their preferred > software. > > I can??t understand why I "shouldn??t use cvs". Because it is old? > Hmmm... Latex is old, vi is old, rcs is old... all of them are useful > and I love to use them > > Although I know that my question is not 100% OpenBSD related, I would > ask here for concepts/ideas how to keep configfiles under revision > control, because I know that there are many experienced admins on this > list. I guess the devel/src package is what you are looking for. http://www.catb.org/~esr/src/ Simple Revision Control is RCS/SCCS reloaded with a modern UI, designed to manage single-file solo projects kept more than one to a directory. Use it for FAQs, ~/bin directories, config files, and the like. Features integer sequential revision numbers, a command set that will seem familiar to Subversion/Git/hg users, and no binary blobs anywhere.
Re: obligatory leaving letter
Well said, Ingo -- -=[rpe]=-
Re: late ro remount to permit reorder_kernel on 6.2
On Sun, Oct 29, 2017 at 06:54:29PM +0100, Klemens Nanni wrote: > On Sun, Oct 29, 2017 at 12:32:58PM +0100, Marko Cupa?? wrote: > > I know read-only setups are unsupported, modifying base files as > > well, but if someone has an advice on what would be a better way of > > remounting local file systems read-only after kernel relinking is done, > > I'd be grateful. > You can use rc.local(8). Not really and btw. the OP uses it already. The kernel relinking happens at the end of rc in the background. rc.local is run before. -- -=[rpe]=-
Re: reordering libraries:/etc/rc[443]: ./test-ld.so: Permission denied
On Tue, Oct 10, 2017 at 06:35:49PM +, Kevin Chadwick wrote: > On Wed, 27 Sep 2017 21:43:48 -0500 > > > > Why is this happening, and is there anything that I should do to > > correct > > > > The system has been getting more and more dynamic to make attackers > fumble in the dark. > > > the "Permission denied" error? > > If you prefer then add: > > /sbin/mount -uo noexec /tmp > > to /etc/rc.local > > The new pledge powers that have been mentioned recently potentially make > noexec more useful ;) > > I am moving all potentially problematic fstab changes such as ro > to /etc/rc.local (/sbin/mount -urf /), letting the devs use the system > during boot as they would their own system. See https://marc.info/?l=openbsd-cvs&m=150783205404965 -- -=[rpe]=-
Re: bsd.rd problem: wd0 is not a valid root disk
On Wed, Aug 02, 2017 at 05:15:58PM +0100, Anthony Campbell wrote: > > > In the last 10 days several attempts to upgrade -current have failed > owing to an error with bsd.rd. I get as far as choosing the keyboard; > then I'm asked to mount the root system and am offered wd0. But when I > accept that it says "wd0 is not a valid root disk". I then have to > reboot. (The boot drive is on wd0a.) > > This is a recent developmet. I thought at first it was just a matter of > waiting for a new version of bsd.rd to appear on -current, but I find > I'm now getting the same error with bsd.rd from -release 6.1. But 6.0 > does work correctly. This suggests to me that something is wrong on my > setup locally but I don't know where to look. > > Google shows nothing relevant. I've tried fdisk -u and installboot to > reconfigure the boot process but they make no difference. > > I thought of trying to reinstall but am reluctant to do that in case I'm > left with a broken system. At least I have a working system at present, > even though I can't uprade it. > > Can anyone kindly suggest what may be wrong? > > I attach dmesg from the last time I could upgrade. > see my response to your mail on bugs@
Re: Trivial bug in installer's .profile
On Sat, Jun 03, 2017 at 01:00:37PM +0300, cho...@jtan.com wrote: > Job control is disabled prior to setting up the auto-install timeout. It > is then re-disabled when the timer has been started. > > The second set +m should be set -m or be removed. > > # Stop monitoring background processes to avoid printing > # job completion notices in interactive shell mode. This > # doesn't stop the "[1] " on starting a job though; > # that's why re redirect stdout and stderr temporarily. > set +m > exec 3<&1 4<&2 >/dev/null 2>&1 > (sleep 5; kill $$) & > timer_pid=$! > exec 1<&3 2<&4 3<&- 4<&- > set +m > > Matthew Job control is never on in the installer as it's a script and the shell is not in interactive mode, in which case job control would be on by default. So it's not a bug. One could argue if it's really necessary to turn monitor mode off in the first place. But in the case above, the author wanted to make sure in any case, that it's off at this point. -- -=[rpe]=-
Re: No 008 patch on ftp.eu.openbsd.org yet
On Sun, May 21, 2017 at 10:36:57AM +0200, Robert Peichaer wrote: > On Sun, May 21, 2017 at 10:28:30AM +0200, Andreas Kusalananda K?h?ri wrote: > > Hi, > > > > I had to switch to ftp.openbsd.org to get the 008 patch for -stable > > since my preferred mirror, ftp.eu.openbsd.org, doesn't seem to be > > updating. The timestamp file says last update was run on 1495188001 > > (Fri May 19 12:00:01 CEST 2017). > > > > There is no contact address in > > https://ftp.eu.openbsd.org/pub/OpenBSD/README so I'm hoping that someone > > who know someone who knows how the mirroring is performed will spot this > > and get them to fix it. > > > > I would also be interested in knowing how often this mirror is > > *supposed* to update (usually it's something like every two hours, > > right?). > > > > > > > > Regards, > > Kusalananda > > > > ftp.eu.openbsd.org is located in Vienna, as is ftp2.eu.openbsd.org. > The latter has the patch already. Bah. Ignore this. ftp.eu is in Stockholm. -- -=[rpe]=-
Re: No 008 patch on ftp.eu.openbsd.org yet
On Sun, May 21, 2017 at 10:28:30AM +0200, Andreas Kusalananda K?h?ri wrote: > Hi, > > I had to switch to ftp.openbsd.org to get the 008 patch for -stable > since my preferred mirror, ftp.eu.openbsd.org, doesn't seem to be > updating. The timestamp file says last update was run on 1495188001 > (Fri May 19 12:00:01 CEST 2017). > > There is no contact address in > https://ftp.eu.openbsd.org/pub/OpenBSD/README so I'm hoping that someone > who know someone who knows how the mirroring is performed will spot this > and get them to fix it. > > I would also be interested in knowing how often this mirror is > *supposed* to update (usually it's something like every two hours, > right?). > > > > Regards, > Kusalananda > ftp.eu.openbsd.org is located in Vienna, as is ftp2.eu.openbsd.org. The latter has the patch already. -- -=[rpe]=-
Re: /usr on NFS, id(1) not found by netstart (diskless client)
On Mon, May 01, 2017 at 05:20:45PM +0200, Andreas Kusalananda K?h?ri wrote: > Hi, > > I configured a diskless client which mounts /usr from a file server > (both running OpenBSD 6.1 -release). > > The client say, as it is running /etc/rc, > > pf enabled > starting network > /etc/netstart[189]: id: not found > /etc/netstart[189]: != 0: unexpected `!=' > > The problem, I assume, is that id(1) lives in /usr/bin and since /usr > hasn't yet been mounted, it's not found. > > This doesn't seem to affect the boot in any way since the network > appears to come up and the filesystems are mounted properly. > > The client has the following in its /etc/fstab: > > server:/export/client/root / nfs rw,soft,tcp,intr > server:/export/shared/usr /usrnfs rw,wxallowed,soft,tcp,intr,nodev > server:/export/shared/home /home nfs rw,soft,tcp,intr,nodev,nosuid > > Let me know if I have misunderstood anything regarding this. Would I > need to move /export/shared/usr back into /export/client/root, for > example? What would be a better hiearchy to use if I wanted to add > multiple clients that share /usr (or even better, share as much as > possible)? > > BTW, the mount options for for the root directory (soft,tcp,intr) seems > to be ignored. I'm assuming this is because it's not remounted once the > network has been started (and it may not even be possible to do that). > > I also noticed that if I use -ro for /export/shared/usr in /etc/exports > on the file server, I am still able to mount the share read-write. > > > Cheers, > Kusalananda I fixed the id error - you're right, the id binary is not available at this point in diskless setups. -- -=[rpe]=-
Re: Latest change to netstart (current)
On Tue, Apr 25, 2017 at 03:20:07PM +0200, Christer Solskogen wrote: > ...seems to not bring up carp0, unless I run "sh /etc/netstart carp0" > manually. > > # ls -l /etc/hostname.carp0 > -rw-r- 1 root wheel 80 Apr 25 15:10 /etc/hostname.carp0 > # cat /etc/hostname.carp0 > inet 192.168.0.1 255.255.255.0 NONE advskew 10 vhid 1 carpdev re0 pass > beefcake > # cat /etc/hostname.re0 > inet 192.168.0.3 255.255.255.0 NONE > > # uname -a > OpenBSD tugs.antarctica.no 6.1 GENERIC.MP#18 amd64 > (latest snapshot, april 25th) I just commited a fix for this. Thanks for reporting. -- -=[rpe]=-
Re: Latest change to netstart (current)
I will check that tonight. Am 25. April 2017 15:20:07 MESZ schrieb Christer Solskogen : >...seems to not bring up carp0, unless I run "sh /etc/netstart carp0" >manually. > ># ls -l /etc/hostname.carp0 >-rw-r- 1 root wheel 80 Apr 25 15:10 /etc/hostname.carp0 ># cat /etc/hostname.carp0 >inet 192.168.0.1 255.255.255.0 NONE advskew 10 vhid 1 carpdev re0 pass >beefcake ># cat /etc/hostname.re0 >inet 192.168.0.3 255.255.255.0 NONE > ># uname -a >OpenBSD tugs.antarctica.no 6.1 GENERIC.MP#18 amd64 >(latest snapshot, april 25th) -- -=[rpe]=-
Re: Little bump in the upgrade path
On Tue, Apr 11, 2017 at 11:00:44AM -0400, trondd wrote: > Just FYI: > > I upgraded 6.0 to 6.1 and /etc/installurl was populated with: > https://ftp4.usa.openbsd.org/pub/OpenBSD/6.1 > > (as is my mirror) > > But when running pkg_add -u to upgrade, it searched > http://ftp4.usa.openbsd.org/pub/OpenBSD/6.1/6.1 for packages. > > Chopped the 6.1 out of installurl to fix. > > Tim. > Fixed. Thanks for reporting. -- -=[rpe]=-
Re: Installer disk info improvement (was - Re: querying scsi id/wwn for scsi disk)
On Thu, Mar 30, 2017 at 09:10:01AM -0400, Jiri B wrote:
> > > > diff -u -p -r1.988 install.sub
> > > > --- distrib/miniroot/install.sub13 Mar 2017 17:08:31 -
> > > > 1.988
> > > > +++ distrib/miniroot/install.sub30 Mar 2017 10:44:01 -
> > > > @@ -264,13 +264,7 @@ diskinfo() {
> > > > local _d
> > > >
> > > > for _d; do
> > > > - make_dev $_d
> > > > - echo -n "$_d: "
> > > > - disklabel -dpg $_d 2>/dev/null |
> > > > - sed -e '/^label: /{s,,,;s/ *$//;s/^$/ > > > label>/;h;d;}' \
> > > > - -e '/.*# total bytes: \(.*\)/{s//(\1)/;H;}' \
> > > > - -e '$!d;x;s/\n/ /'
> > > > - rm -f /dev/{r,}$_d?
> > > > + sed -n "/^$_d/p" /var/run/dmesg.boot
> > > > done
> > > > }
> > > >
> > >
> > > Your proposition is good for the installer? I doubt it.
> > >
> > > j.
> >
> > AFAICT the function diskinfo() is only called once in the installer: if
> > you press ? a the prompt for the root disk. So my diff just changes the
> > output in this case, no other functionality is affected.
> >
> > What causes your doubt?
>
> Robert,
>
> could we use something like this? From dmesg we can get current
> vendor, model, size plus serial if it does exist, 'sd0' could be grepped
> before sed or we could put variable inside sed itself:
>
> sed -e '/^sd0 at.*: <[A-Z]*, \([^,]*\).*fixed *\(.*\)/{s//\1 <\2>/;s/<
> *>$//;h;d;}' -e '/sd0: \([^,]*\).*/{s//(\1)/;H;}' -e '$!d;x;s/\n/
> /' /var/run/dmesg.boot
> SAMSUNG MZ7TE256 (244198MB)
>
> If there's no serial it maybe could print this?
>
> cat /var/run/dmesg.boot | sed 's/fixed.*/fixed/;' | sed -e '/^sd0 at.*:
> <[A-Z]*, \([^,]*\).*fixed *\(.*\)/{s//\1 <\2>/;s/< *>$//;h;d;}' -e
> '/sd0: \([^,]*\).*/{s//(\1)/;H;}' -e '$!d;x;s/\n/ /'
> SAMSUNG MZ7TE256 (244198MB)
>
> What do you think?
>
> PS: sed is really hardcore :)
>
> j.
Parsing dmesg output always tends to be fragile, but what about this?
Use whatever is enclosed in <> in the dmesg output for a disk and get
the size from disklabel.
VMware ESXi:
sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct
fixed naa.5000c2994057dedf
QEMU using virtio:
sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed
My notebook:
sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed
naa.500a07511210a1b8
>From an ppc imac:
wd0 at pciide0 channel 0 drive 0:
sd0: VirtIO, Block Device, (10.0G)
sd0: ATA, VMware Virtual S, naa.5000c2994057dedf (51.2G)
sd0: ATA, MTFDDAK512MBF, LN01 naa.500a07511210a1b8 (512.0G)
wd0: Samsung SSD 840 EVO 120GB (120.0G)
Index: install.sub
===
RCS file: /cvs/src/distrib/miniroot/install.sub,v
retrieving revision 1.989
diff -u -p -p -u -r1.989 install.sub
--- install.sub 31 Mar 2017 18:36:49 - 1.989
+++ install.sub 2 Apr 2017 20:13:04 -
@@ -266,10 +266,11 @@ diskinfo() {
for _d; do
make_dev $_d
echo -n "$_d: "
- disklabel -dpg $_d 2>/dev/null |
- sed -e '/^label: /{s,,,;s/ *$//;s/^$//;h;d;}' \
- -e '/.*# total bytes: \(.*\)/{s//(\1)/;H;}' \
- -e '$!d;x;s/\n/ /'
+ set -- $(sed -n "/^$_d at /{s/^.* .* \(naa\..*\)$/
\1/;s/> .*$//;p;}" \
+ /var/run/dmesg.boot 2>/dev/null) \
+ $(disklabel -dpg $_d 2>/dev/null |
+ sed -n '/.*# total bytes: \(.*\)/s//(\1)/p')
+ echo "$*"
rm -f /dev/{r,}$_d?
done
}
===
Stats: --- 4 lines 166 chars
Stats: +++ 5 lines 220 chars
Stats: 1 lines
Stats: 54 chars
--
-=[rpe]=-
Re: i3bar iwn info and battery status
On Thu, Feb 09, 2017 at 10:18:44PM +0300, Asbel Kiprop wrote:
> hi misc.
> i've moved my -current system from hdd to ssd disk. everything work fine
> for me, but got some strange i3bar behavior.
> wireless _first_ {
> format_up = "W: (%signal at %essid) %ip"
> format_down = "W: down"
> }
> battery 0 {
> format = "%status %percentage \% %remaining"
> }
>
> At first start i get what i want - iwn status and battery life time. But
> after 10-20 minutes it turnes to "W:down" and "can't open /dev/apm"
>
> /dev/apm exesist and and seems no problem with it
> ls -la /dev/apm
>
> crw-r--r-- 1 root wheel 83, 0 Feb 9 14:39 /dev/apm
>
> The problem is i dont even know what should i look for to determine the
> root of the problem..
> I already tried to update with bsd.rd.
>
> ANy suggestions?
This has been fixed recently. Update after new packages are on the
mirrors. The current packages were built before this fix.
http://marc.info/?l=openbsd-ports-cvs&m=148649175810877&w=2
Re: autoinstall with local file
On Fri, Jan 13, 2017 at 11:14:16AM -0700, Theo de Raadt wrote: > > On Fri, Jan 13, 2017 at 06:20:25AM -0600, Ed Ahlsen-Girard wrote: > > > The man page seems to indicate that autoinstall will work with an > > > auto_upgrade.conf file on the local machine, but specifying the path as: > > > > > > /auto_upgrade.conf > > > or > > > file://auto_upgrade.conf > > > or > > > file:auto_upgrade.conf > > > > > > do not work. > > > > > > Is this still a "watch this space!" feature? > > > > It does work. However, / is the root of bsd.rd, not the root of the > > system you want to upgrade (this would have to be guessed and the > > upgrade script doesn't do guessing without asking for confirmation). > > It's a bit of a pain to get the file there, and I don't think there's > > any official documentation. semarie@ wrote some instructions a while > > back: > > https://marc.info/?l=openbsd-misc&m=141552533922277&w=2 > > see also: > > https://marc.info/?l=openbsd-misc&m=146890249418788&w=2 > > where he indicates that there are more posts to be found on misc (but I > > don't know where). > > I would be very surprised to hear that people are using > vnconfig+mount+vnconfig+mount, to add such a file. And while doing so > potentially running low on space issues (it isn't just a matter of > the file fitting, there must be some slop left over because the > installer needs a bit of /tmp) > > Should everything work in every way? I'm not so sure. My truck > still doesn't fly. The original idea of this was to allow ... Welcome to the OpenBSD/amd64 6.0 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s # cat <<_EOF >/auto_install.conf > system hostname = hostA > password for root = whateversecurepassword > http server = ftp.hostserver.de > _EOF # exit erase ^?, werase ^W, kill ^U, intr ^C, status ^T Welcome to the OpenBSD/amd64 6.0 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a If the system had internet access during installation, it's even enough to create an empty /auto_upgrade.conf, because the last used mirror will be used automatically. Welcome to the OpenBSD/amd64 6.0 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s # >/auto_upgrade.conf # exit erase ^?, werase ^W, kill ^U, intr ^C, status ^T Welcome to the OpenBSD/amd64 6.0 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a -- -=[rpe]=-
Re: autoinstall with local file
On Fri, Jan 13, 2017 at 06:20:25AM -0600, Ed Ahlsen-Girard wrote: > The man page seems to indicate that autoinstall will work with an > auto_upgrade.conf file on the local machine, but specifying the path as: > > /auto_upgrade.conf > or > file://auto_upgrade.conf > or > file:auto_upgrade.conf > > do not work. > > Is this still a "watch this space!" feature? > > -- > > Edward Ahlsen-Girard > Ft Walton Beach, FL > The installer looks at the filesystem provided by bsd.rd itself, not the filesystem on disk. -- -=[rpe]=-
Re: reorder_libs() from /etc/rc when using NFS root FS
Hi Frank Thanks for reporting this. I just committed a fix. Cheers Robert
Re: can't upgrade using the last snapshot
On Mon, Apr 11, 2016 at 07:22:31PM +0200, arrowscr...@mail.com wrote: > The snapshot can't find the mirror. It prints: "no address associated with > this name". > I have tried many mirrors (inclusing the mother, ftp.openbsd.org), none work > for me. > > I has been a hard time to work with snapshots since last month... many bugs. > I'm using snapshots to help reporting bugs, of course, so I know that this > kind of situation will happen some times. But, I can't crash the system > everytime I do a new upgrade... I think it's time to just use stable. That means at the time when the installer tries to contact the mirror server, you either don't have network connectivity at all or that you don't have a working DNS. If that's reproducable for you, watch closely if there are any error messages related to the network configuration right after the mounting of the root filesystem. You can switch to the shell and check the network config by entering a '! e.g. at the prompt that asks you about force checking clean non-root filesystems. (just 'exit' to continue) The installer seems to work fine, I just upgraded using the latest snap (4th April).
Re: /etc/hosts during install
On Sat, Mar 12, 2016 at 05:49:32PM +0100, hans wrote: > On Mar 12 16:36:37, rob...@peichaer.org wrote: > > On Sat, Mar 12, 2016 at 04:57:04PM +0100, hans wrote: > > > Has the attitude towards /etc/hosts changed again? > > > After a fresh install of current/i386, > > > > > > 127.0.0.1 localhost > > > ::1 localhost > > > 192.168.22.4www.stare.cz www > > > > > > The first two I would expect. > > > The last one was assigned to me via DHCP during install; > > > I am changing the network configuration now (to another, > > > static IP address), and removing it from /etc/hosts; > > > but it's easy to have a stale DHCP address > > > assigned during install left in /etc/hosts. > > > > > > I believe it was discussed on the list before, > > > and the decision was not to do this. > > > Has the rationale changed? > > > > > > Jan > > > > You're probably referring to this commit from 2 years ago and since then > > nothing changed with respect to adding static entries to /etc/hosts. > > > >revision 1.682 > >date: 2013/07/21 22:06:51; author: halex; state: Exp; lines: +1 -6; > >stop adding static entries to /etc/hosts for dynamic ip addresses > > > >"do it NOW" deraadt@ > > Yes, that's what I was referring to; thanks. > > This is a fresh install, and I sure didn't put it there myself. > How could this entry ended up in my /etc/hosts ? > > The file /etc/hosts is in the Attic since Fri Sep 5 07:22:29 2014 > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc/Attic/hosts > The remove message says > > Make the installer create the /etc/hosts template. > While here, re-add a missing 'echo' from install.sh. > > Could it be where it got back? > > Jan No, I don't think so. The corresponding change in install.sh from ajacoutot@ (rev. 1.258) just writes the two localhost entries to the hosts file instead of using a static hosts template file containing these two localhost entries. I just did a test install myself to verify the current installer behaviour. Having one interface and using 'dhcp' to configure it results in the two localhost lines and nothing more. I used the latest snapshot for that.
Re: /etc/hosts during install
On Sat, Mar 12, 2016 at 04:57:04PM +0100, hans wrote: > Has the attitude towards /etc/hosts changed again? > After a fresh install of current/i386, > > 127.0.0.1 localhost > ::1 localhost > 192.168.22.4www.stare.cz www > > The first two I would expect. > The last one was assigned to me via DHCP during install; > I am changing the network configuration now (to another, > static IP address), and removing it from /etc/hosts; > but it's easy to have a stale DHCP address > assigned during install left in /etc/hosts. > > I believe it was discussed on the list before, > and the decision was not to do this. > Has the rationale changed? > > Jan You're probably referring to this commit from 2 years ago and since then nothing changed with respect to adding static entries to /etc/hosts. revision 1.682 date: 2013/07/21 22:06:51; author: halex; state: Exp; lines: +1 -6; stop adding static entries to /etc/hosts for dynamic ip addresses "do it NOW" deraadt@
Re: Autoinstall via netboot over VLAN interface
On Mon, Jan 04, 2016 at 09:35:04AM -0700, Darren S. wrote: > I have a router on the end of a 802.1q trunk port that I'd like to > netboot for install, but this is only possible if I can PXE boot using > the correct VLAN to reach the PXE server. Some PXE boot ROMs support > this (mine does not currently) and I was going to try it from a booted > bsd.rd on the host, but looks like I only have options for physical > interfaces to select from on an Autoinstall: > > Welcome to the OpenBSD/amd64 5.8 installation program. > (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? a > Available network interfaces are: re0 re1 re2 athn0. > Which network interface should be used for the initial DHCP request? > (or 'done') [re0] > DHCPDISCOVER on re0 - interval 3 > DHCPDISCOVER on re0 - interval 5 > DHCPDISCOVER on re0 - interval 13 > DHCPDISCOVER on re0 - interval 19 > DHCPDISCOVER on re0 - interval 13 > DHCPDISCOVER on re0 - interval 8 > No acceptable DHCPOFFERS received. > No working leases in persistent database - sleeping. > Could not determine next-server. > Could not determine auto mode. > Response file location? > > With additional work I may be able to switch around network > configurations to support a native VLAN (and then reconfigure > post-install) but this isn't ideal. Is it feasible for the autoinstall > support to handle the same VLAN features for booting as is available > later in the installation for network configuration? > > Which network interface do you wish to configure = vlan0 > Which interface:tag should vlan0 be on = re0:100 > IPv4 address for vlan0 = 10.0.1.1 > Netmask for vlan0 = 255.255.255.0 > > -- > Darren Spruell > phatbuck...@gmail.com You can put the response file into the bsd.rd as /auto_upgrade.conf or /auto_install.conf. This way you can avoid the fetching of the response file. https://marc.info/?l=openbsd-misc&m=141552533922277&w=2
Re: OpenBSD installer info prohibit-password > without-password ?
On Sun, Nov 01, 2015 at 11:18:41AM -0500, Adam Van Ymeren wrote: > On 1 Nov 2015 7:06 a.m., "ludovic coues" wrote: > > > > 2015-11-01 8:56 GMT+01:00 S : > > > when installing OpenBSD > > > Alow root ssh login? (yes, no, prohibit-password) [no] prohibit-password > > > > > > after install , in /etc/sshd_config > > > PermitRootLogin without-password > > > > > > so, why not using "without-password" at installation procedure for > consistency? > > > > > > > http://www.openbsd.org/errata58.html > > That doesn't really answer the question. Maybe the actual commit message from deraadt@ explains it a bit better? http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/sshd_config?rev=1.97&content-type=text/x-cvsweb-markup
Re: Maintaining CAs not in cert.pem
On Thu, Jul 30, 2015 at 05:16:30PM +, Stuart Henderson wrote: > On 2015-07-30, Ted Unangst wrote: > > Michael McConville wrote: > >> > Another meat could be, why you're using self-signed certificates? > >> > Given the plethora of options for getting free (valid) certificates. > >> > >> He mentioned in his original email that it's a requirement where he > >> works. That's common, from what I hear, although probably not the > >> safest. > > > > I would consider a cert signed by somebody I actually trust (me) safer than > > delegating that trust to 300 strangers. > > I think cert.pem should move to the etc set, so you can remove > CAs from the file (as well as add new ones) without risk of those > changes getting reverted. > > Downside: CA changes will then only take effect after running > sysmerge. Is that a problem? I would like to see cert.pm become a "managed" file. FWIW OK rpe@ -- -=[rpe]=-
Re: Last snapshots won't install on VMWare ESXi or getting ether_output panic
On Wed, Feb 25, 2015 at 05:55:44PM +, Romain FABBRI wrote: > On last snapshots I can't complete the install when installing > as a guest VM in VMWare ESXi 5.5. (snap: 20150217->20150223) Not sure what you really did. Upgrade from snap 20150217 to 20150223, or reinstall with the newer snapshot? What errors did you have during install? A panic like you showed? > The install fails when installing sets from CD. I just installed a system with the i386 20150223 snap on an ESXi 5.5 using the "FreeBSD 32-bit" HW default suggestions without any problem. After that I changed the ethernet "card" from E1000 to VMXNET2. No issues during install, same with VMXNET3. What virtual "hardware" did you use for the VM? > So I tried to convert a Hyper-V install which completes correctly > and then to deploy the image to VMWare ESXi 5.5. > It can boot but when doing a simple ping I get a kernel panic. > > Ddb output : > > panic: smashed stack in ether_output > Stopped at Debugger+0x7:leave > ddb>trace > Debugger(d09e204a,f53adc08,d09bae0c,f53adc08,da0336c4) at Debugger+0x7 > panic(d09bae0c,d09c33de,0,f53adc1c,d0203025) at panic+0x71 > __stack_smash_handler(d09c33de,e,2,da0336ca,f53adc9a) at __stack_smash_handler > 0x19 > ether_output(d4085830,d9ee8b00,da0336c4,da00fb54,0) at ether_output+0x541 > ip_output(d9ee8b00,0,da0336bc,20,0) at ip_output+0xd0b > rip-output(d9ee8b00,d9f1f648,1b2d23e,d9ee8e00,0) at rip_output+0x144 > sosend(d9f1f648,d9ee8e00,f53ade90,d9ee8e00,0) at sosend+0x444 > sendit(d9ef6174,3,f53adef4,0,f53adf80) at sendit+0x1e1 > sys_sendto(d9ef6174,3,f53adf60,f53adf80,d0569f25,d9ef6174) at sys_sendto+0x6c > syscall() at syscall+0x24d > > ddb>ps > PID PPIDPGRPUID S FLAGS WAIT COMMAND > * 5393 20454 53930 7 0x33ping > > > Tested from i386 image on VMWare ESXi 5.5 (I tried with E1000 and > VMX3 network drivers and got same panic). > > Romain > -- -=[rpe]=-
Re: How to log the install console?
On Mon, Sep 15, 2014 at 09:18:08AM +0200, somelooser3...@hushmail.com wrote: > If I do an install from a flash drive, select (S)hell: > > ## > # mount /dev/sd0a /mnt > # cd /mnt/5.5/amd64 > > # tar -xzvf basexx.tgz ./usr/bin/script > # ln -s /mnt/5.5/amd64/usr/bin/script /usr/bin/ > > # tar -xzvf basexx.tgz ./usr/lib/libutil.so* > # mkdir /usr/lib > # ln -s /mnt/5.5/amd64/usr/lib/libutil.so* /usr/lib/ > > # tar -xzvf basexx.tgz ./usr/lib/libc.so* > # ln -s /mnt/5.5/amd64/usr/lib/libc.so* /usr/lib/ > > # tar -xzvf basexx.tgz ./usr/libexec/ld.so > # mkdir /usr/libexec > # ln -s /mnt/5.5/amd64/usr/libexec/ld.so /usr/libexec/ > > # /usr/bin/script > ## > > It sends an error message: > > : openpty: No such file or directory > > My purpose is just to log the install console to a file for > documentation purpose. > > How can I get through this error message? > > p.s.: additionally I found out when I'm continuing the install, the > /mnt will be unmounted, so ln's doesn't work, but ln's are needed, > because there isn't enough place in / > > Many thanks. > Maybe autoinstall(8) solves this for you? It provides the output as email in the root mbox. -- -=[rpe]=-
Re: cvsweb link on site down?
On Sat, Jul 19, 2014 at 07:00:53AM -0500, James Hartley wrote: > I'm getting a "403 Forbidden" error when trying to access > http://www.openbsd.org/cgi-bin/cvsweb. Is this a known problem? > http://marc.info/?l=openbsd-tech&m=140553819232513&w=2
Re: ksh: expr 2147483648 / 2 = -1073741824 expected behavior or bug?
On Mon, Feb 24, 2014 at 11:10:44PM +, Fred wrote: > On 02/24/14 22:32, Richard P??ttler wrote: > >On Mon, Feb 24, 2014 at 10:59 PM, Fabian Raetz > >wrote: > >>while calculating my phys. memory (mb) with the > >>folllowing shellsript i get as a result -424. > >> > >>sysctl -n hw.physmem returns 3849830400 > >> > >> > >>#!/bin/sh > >> > >>phys_mem_bytes=`sysctl -n hw.physmem` > >>phys_mem_mb=`expr $phys_mem_bytes / 1024 / 1024` > >>echo $phys_mem_mb > >>-- > > > >You declared "#!/bin/sh" so you are using the broune shell, not ksh - fyi. > > > > On OpenBSD sh is the same binary as ksh, the notes section of the sh(1) > gives some more detail as does the faq[1]. > > Fred > > [1]http://www.openbsd.org/faq/faq10.html#ksh #!/bin/sh phys_mem_bytes=$(sysctl -n hw.physmem) phys_mem_mb=$(($phys_mem_bytes / 1024 / 1024)) echo $phys_mem_mb -- -=[rpe]=-
Re: two equal filenames in one dir
On Sun, Jan 27, 2013 at 05:20:14AM -0500, Jiri B wrote: > Hello, > > I'm confused, how is it possible I have two files with same > names in one dir? > > $ ls -li > total 1245376 > 3611817 -rw-r--r-- 1 jirib jirib 168392755 Jan 14 23:35 > Crostata_Alla_Fruta.mp4 > 3741698 -rw-r--r-- 1 jirib jirib 165519511 Mar 12 2010 Pizza > Margherita-10115892.mp4 > 3611818 -rw-r--r-- 1 jirib jirib 165519511 Jan 14 23:35 > Pizza_Margherita-10115892.mp4 > 3741699 -rw-r--r-- 1 jirib jirib 68932635 Jul 31 21:02 jablecny > kolac-46705666.mp4 > 3611819 -rw-r--r-- 1 jirib jirib 68932635 Jan 14 23:35 > jablecny_kolac-46705666.mp4 > > $ sysctl kern.version > kern.version=OpenBSD 5.2-current (GENERIC.MP) #20: Mon Jan 21 17:23:23 MST > 2013 > t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Pizza Margherita-10115892.mp4 Pizza_Margherita-10115892.mp4 ^ jablecny kolac-46705666.mp4 jablecny_kolac-46705666.mp4 ^ -- -=[rpe]=-
Re: nfs_server=YES in /etc/rc.conf.local does not work
On Sun, Oct 28, 2012 at 01:15:56AM +0400, Mike Korbakov wrote: > Seems, authors rc.conf forgotten (or did not for some reason) to load portmap > when nfs_server is marked on. > Or nfsd now works without portmap ? > (rc.conf unchanged: $OpenBSD: rc.conf,v 1.167 2012/04/01 18:32:51 deraadt Exp > $) > > # uname -a > OpenBSD obsd52x64.vm.mike-i7.kmv 5.2 GENERIC.MP#5 amd64 > # cat /etc/rc.conf.local > nfs_server=YES > > # grep -rn nfsd /var/log/* > /var/log/daemon:55:Oct 27 18:01:03 obsd52x64 nfsd[11977]: can't register with > udp portmap > /var/log/daemon:107:Oct 28 00:15:07 obsd52x64 nfsd[10408]: can't register > with udp portmap > /var/log/messages:371:Oct 28 00:15:07 obsd52x64 nfsd[10408]: can't register > with udp portmap > # rpcinfo -p 127.0.0.1 > rpcinfo: can't contact portmapper: RPC: Remote system error - Connection > refused > > P.S. searching by google gives strange result for keyword "nfs_server": > http://www.google.com/search?q=%22nfs_server%22&domains=www.openbsd.org&sitesearch=www.openbsd.org&btnG=Search > I'm not guessed to look for the answer in the documentation in Chinese. > Information from openbsd.ru outdated because recommends edit rc.conf Following the steps described in the FAQ results in a working nfs server. http://www.openbsd.org/faq/faq6.html#NFS -- -=[rpe]=-
Re: Sun Fire v440 sparc64 MP support
Michael schrieb: Hi, according to http://www.openbsd.org/sparc64.html#hardware OpenBSD works on this machine, but does anyone know if multiple UltraSPARC IIIi CPUs are also supported? Thanks in advance. Michael from http://www.openbsd.org/sparc64.html#history, last paragraph: OpenBSD 4.0 was the first release to ship with support for the UltraSPARC III based machines; OpenBSD 4.3 first with SMP support, and OpenBSD 4.4 will be the first to support the UltraSPARC-IV, UltraSPARC T1 and SPARC64-V processors. in short: yes -- -=[rpe]=- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
