Cant cd to /usr/obj/usr/src/sys/ error code 2

cant cd to /usr/obj/usr/src/sys/ error code 2

bugs.freebsd.org › bugzilla › show_bug. portsnap fetch extract # cd /usr/ports/www/node # make install touch S" --no-native-code-counters # # Fatal error in, line 0 # Check. I created a duplicate kernel file and edited that to add device sg at the end. Code: cd /usr/src/sys/amd64/conf cp GENERIC MYKERNEL cd /usr/src. cant cd to /usr/obj/usr/src/sys/ error code 2

Cant cd to /usr/obj/usr/src/sys/ error code 2 - phrase

sort -u
did you mess with /etc/make.conf (show it)
also you could compleatly wipe sources and run csup again...
here's my csup file, i used few days ago, everything went file

Code:

*default host=cvsup3.lv.freebsd.org *default tag=RELENG_7_0 *default prefix=/usr *default base=/var/db *default release=cvs delete use-rel-suffix compress src-all
using this supfile you will get FreeBSD 7-p4 sources....
you may want to change host server

btw, what arch are you compiling, i386, right?
and for now (if you try to recompile kernel, try only GENERIC while we find solution)


EDIT... weird that you can't compile kernel.... your supfile seams OK
To speed up compiling you can use -j4

Code:

make -j4 buildworld
don't forget to do that in single user mode


EDIT2:
RENELNG_7 means: The line of development for FreeBSD-7.X, also known as FreeBSD 7-STABLE
So the problem might actually be source files....
try my supfile


Last edited by graudeejs; 9th September 2008 at 01:43 PM.

make installkernel fails in FreeBSD 4.5

From make world section of the handbook:

quote:
21.4.15.4. Can interrupted builds be resumed?

This depends on how far through the process you got before you found a problem.

In general (and this is not a hard and fast rule) the ``make world'' process builds new copies of essential tools (such as gcc(1), and make(1)) and the system libraries. These tools and libraries are then installed. The new tools and libraries are then used to rebuild themselves, and are installed again. The entire system (now including regular user programs, such as ls(1) or grep(1)) is then rebuilt with the new system files.

If you are at the last stage, and you know it (because you have looked through the output that you were storing) then you can (fairly safely) do

... fix the problem ...
# cd /usr/src
# make -DNOCLEAN all

This will not undo the work of the previous ``make world''.

If you see the message

--------------------------------------------------------------
Building everything..
--------------------------------------------------------------

in the ``make world'' output then it is probably fairly safe to do so.

If you do not see that message, or you are not sure, then it is always better to be safe than sorry, and restart the build from scratch.



In other words, it's possible, but you've got to know what you're doing.

virtualbox-ose-nox11 compile fails on newly upgraded 11.2

Dale Scott's profile photo

Dale Scott

unread,
Aug 1, 2018, 7:02:46 PM8/1/18

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to [email protected], [email protected]

virtualbox-ose-nox11 fails to compile from ports on newly upgraded 11.2. I'm
attempting to install from the ports collection because installing the
binary pkg (or possibly the kmod only) is causing the system to crash during
boot (I assume the same issue that is described in the 11.2 errata, causing
me to uninstall virtualbox before upgrading from 11.1).



The errata, and PR228535[1] which it references, indicate building from
source (ports) will avoid the issue (somehow). I think someone responded to
the PR saying installing the pkg after upgrading worked, but not in my case
- which is why I'm now attempting to install from ports.



The host server is a re-purposed media PC with Intel E6600 Core 2 CPU and 6
GB RAM (DDR2 PC2-5300) running 64-bit FreeBSD 11.2. I seem to come across
mention of ZFS when searching this issue. I've always trusted that the
FreeBSD installer/upgrader knows what it's doing without my involvement in
this regard, although I saw a boot message that something ZFS wants to be
given more memory (but not seen now that I've upgraded to 11.2).



Suggestions are greatly appreciated. :-) My goal is to host two pre-built
Linux vm's on what is otherwise a PHP web app server. One vm is ERPNext
(from the project) and the other is Gitlab (from Bitnami). Should I cut my
losses and figure out how to switch my *.ova's to bhyve?



Thanks all,

Dale



# uname -a

FreeBSD whizzer.dalescott.net 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510:
Fri Jun 22 04:32:14 UTC 2018
[email protected]:/usr/obj/usr/src/sys/GENERIC amd64



# portsnap fetch

# portsnap extract

# cd /usr/ports/emulators/virtualbox-ose-nox11

# make install

.

kBuild: Installing
/usr/ports/emulators/virtualbox-ose-nox11/work/VirtualBox-5.2.16/out/freebsd
.amd64/release/bin/sdk/bindings/glue/java/TestVBox.java

kBuild: Installing
/usr/ports/emulators/virtualbox-ose-nox11/work/VirtualBox-5.2.16/out/freebsd
.amd64/release/bin/sdk/bindings/glue/java/Makefile

kmk: *** No rule to make target `/usr/src/sys/kern/bus_if.m', needed by
`/usr/ports/emulators/virtualbox-ose-nox11/work/VirtualBox-5.2.16/out/freebs
d.amd64/release/obj/FreeBSDGeneratedKernelHeaders/bus_if.h'. Stop.

kmk: *** Waiting for unfinished jobs....

kmk: *** Exiting with status 2

*** Error code 2



Stop.

make[1]: stopped in /usr/ports/emulators/virtualbox-ose-nox11

*** Error code 1



Stop.

make: stopped in /usr/ports/emulators/virtualbox-ose-nox11

[email protected]:/usr/ports/emulators/virtualbox-ose-nox11 #







_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[email protected]"

Gary Palmer's profile photo

Gary Palmer

unread,
Aug 1, 2018, 8:16:55 PM8/1/18

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to Dale Scott, [email protected], [email protected]

On Wed, Aug 01, 2018 at 09:01:13AM -0600, Dale Scott wrote:
> virtualbox-ose-nox11 fails to compile from ports on newly upgraded 11.2. I'm
> attempting to install from the ports collection because installing the
> binary pkg (or possibly the kmod only) is causing the system to crash during
> boot (I assume the same issue that is described in the 11.2 errata, causing
> me to uninstall virtualbox before upgrading from 11.1).
>
> The errata, and PR228535[1] which it references, indicate building from
> source (ports) will avoid the issue (somehow). I think someone responded to
> the PR saying installing the pkg after upgrading worked, but not in my case
> - which is why I'm now attempting to install from ports.

[ snip ]


> # uname -a
>
> FreeBSD whizzer.dalescott.net 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510:
> Fri Jun 22 04:32:14 UTC 2018
> [email protected]:/usr/obj/usr/src/sys/GENERIC amd64
>
>
>
> # portsnap fetch
>
> # portsnap extract
>
> # cd /usr/ports/emulators/virtualbox-ose-nox11
>
> # make install
>
> .
>
> kBuild: Installing
> /usr/ports/emulators/virtualbox-ose-nox11/work/VirtualBox-5.2.16/out/freebsd
> .amd64/release/bin/sdk/bindings/glue/java/TestVBox.java
>
> kBuild: Installing
> /usr/ports/emulators/virtualbox-ose-nox11/work/VirtualBox-5.2.16/out/freebsd
> .amd64/release/bin/sdk/bindings/glue/java/Makefile
>
> kmk: *** No rule to make target `/usr/src/sys/kern/bus_if.m', needed by
> `/usr/ports/emulators/virtualbox-ose-nox11/work/VirtualBox-5.2.16/out/freebs
> d.amd64/release/obj/FreeBSDGeneratedKernelHeaders/bus_if.h'. Stop.


Do you have FreeBSD kernel sources installed?

Regards,

Gary
Kevin Oberman's profile photo

Kevin Oberman

unread,
Aug 2, 2018, 3:11:28 AM8/2/18

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to Dale Scott, [email protected], Mailinglists FreeBSD

On Wed, Aug 1, 2018 at 8:01 AM, Dale Scott <[email protected]> wrote:

> virtualbox-ose-nox11 fails to compile from ports on newly upgraded 11.2.
> I'm
> attempting to install from the ports collection because installing the
> binary pkg (or possibly the kmod only) is causing the system to crash
> during
> boot (I assume the same issue that is described in the 11.2 errata, causing
> me to uninstall virtualbox before upgrading from 11.1).
>
>
>
> The errata, and PR228535[1] which it references, indicate building from
> source (ports) will avoid the issue (somehow). I think someone responded to
> the PR saying installing the pkg after upgrading worked, but not in my case
> - which is why I'm now attempting to install from ports.
>
>
>
> The host server is a re-purposed media PC with Intel E6600 Core 2 CPU and 6
> GB RAM (DDR2 PC2-5300) running 64-bit FreeBSD 11.2. I seem to come across
> mention of ZFS when searching this issue. I've always trusted that the
> FreeBSD installer/upgrader knows what it's doing without my involvement in
> this regard, although I saw a boot message that something ZFS wants to be
> given more memory (but not seen now that I've upgraded to 11.2).
>
>
>
> Suggestions are greatly appreciated. :-) My goal is to host two pre-built
> Linux vm's on what is otherwise a PHP web app server. One vm is ERPNext
> (from the project) and the other is Gitlab (from Bitnami). Should I cut my
> losses and figure out how to switch my *.ova's to bhyve?
>
>
>
> Thanks all,
>
> Dale
>

There is no need to build or install virtualbox-ose. Installing the package
version is fine.

You do need to rebuild virtualbox-ose-kmod to prevent a crash at boot time.
To do this you will need the current port.

Be sure that version matches virtualbox-ose. If the versions do not match,
install the virtualbox-ose package from head instead of quarterly and usr
the port from HEAD. The current version is 5.2.16, but older versions (e.g.
5.2.14) should work. Ignore the portrevision, the digit after the '_', if
present.

You must have a full set of kernel sources in /usr/src. The kernel module
must have the kernel sources to build correctly.

Use "kldload vboxdrv vboxnetflt vboxnetadp" and re-enable loading of the
driver at boot.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: [email protected]
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Dale Scott's profile photo

Dale Scott

unread,
Aug 2, 2018, 9:02:26 AM8/2/18

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to Gary Palmer, [email protected], [email protected]

Hi Gary, I don’t have sources installed. I started this server with an 11.0-RELEASE DVD ISO and did not install FreeBSD sources the or ports tree it has been upgraded successively to 11.1 and 11.2 using freebsd-update.

Dale Scott's profile photo

Dale Scott

unread,
Aug 2, 2018, 9:11:13 AM8/2/18

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

You do not have permission to delete messages in this group

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message

to Kevin Oberman, [email protected], Mailinglists FreeBSD


> On Aug 1, 2018, at 5:10 PM, Kevin Oberman <[email protected]> wrote:
>
>> On Wed, Aug 1, 2018 at 8:01 AM, Dale Scott <[email protected]> wrote:
>> virtualbox-ose-nox11 fails to compile from ports on newly upgraded 11.2. I'm
>> attempting to install from the ports collection because installing the
>> binary pkg (or possibly the kmod only) is causing the system to crash during
>> boot (I assume the same issue that is described in the 11.2 errata, causing
>> me to uninstall virtualbox before upgrading from 11.1).

<snip>


> There is no need to build or install virtualbox-ose. Installing the package version is fine.
>
> You do need to rebuild virtualbox-ose-kmod to prevent a crash at boot time. To do this you will need the current port.
>
> Be sure that version matches virtualbox-ose. If the versions do not match, install the virtualbox-ose package from head instead of quarterly and usr the port from HEAD. The current version is 5.2.16, but older versions (e.g. 5.2.14) should work. Ignore the portrevision, the digit after the '_', if present.
>
> You must have a full set of kernel sources in /usr/src. The kernel module must have the kernel sources to build correctly.
>
> Use "kldload vboxdrv vboxnetflt vboxnetadp" and re-enable loading of the driver at boot.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: [email protected]
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>

Thanks Kevin. Very clear.

Share: Cant cd to /usr/obj/usr/src/sys/ error code 2

SEND PACKET ERROR WSAGETLASTERROR = WSAEWOULDBLOCK
Cant cd to /usr/obj/usr/src/sys/ error code 2
Abi 7900 block mismatch error
Cant cd to /usr/obj/usr/src/sys/ error code 2

Similar video

FreeBSD 13 To 13.1 PKG Kernel Mismatch Oh My! What to do? If You are Lazy Like Me Just Wait.

Any tips to connect my php to my oracle DB? (FreeBSD 12.1 AMD)

I'm using FreeBSD 12.1 with amd, php73 and I'm trying to connect my oracle database. and I made a few attempts but to no avail, apparently a missing drive is missing for FreeBSD + AMD.

Well, my first try was connect with PDO:

And i had this error:

my second try was connect via odbc_connect

And, guess what:

Well, after understanding that Drive was missing, I started the quest to try to install either the PDO or the PECL responsible for oracle db.

First thing I did was look for oracle in the freebsd packages

Okay, if you don't have it in pkg, it could be that it exists in ports. let's look there?

Without losing hope, I tried to think simpler and install via PECL, but before downloading, I saw a suggestion on the internet, to download the SDK and put it in a specific folder and put it in a specific folder and at the time of installation pass the path to that folder with the SDK.

But, i had this error now:

I tried to install these missing LIBDs, but I couldn't find any packages that install it.

:( at that moment I lost my hopes and I come to ask the community for help

ignore] changed behaviour of bgpd. Until now evaluate was the implicit default but now the default is ignore. Route age evaluation is not specified in RFC 1771 and results in non deterministic decisions in preference for more stable links.

2004/11/24 - New user and group: _ftp

The FTP daemon is being reworked to use privilege separation. Thus a new user and group "_ftp" are required. Add the user and group by running as root.

2004/12/30 - Switch to gcc3 (i386)

OpenBSD/i386 has converted to gcc3. To upgrade, Now, build gcc3, (using the gcc3 directory) then build the kernel and system as usual.

2005/01/18 - New user and group: _ospfd

The upcoming ospf daemon needs its own user and group _ospfd. Add them by running as root, cant cd to /usr/obj/usr/src/sys/ error code 2.

2005/01/24 - pfsync takes syncdev instead of syncif

When configuring the pfsync device, use 'syncdev' instead of the deprecated keyword 'syncif'.

2005/02/02 - POSIX hex and octal constants in (k)sh

Both sh(1) and ksh(1) now interpret c-like hex (0x.) and octal (0.) constants in arithmetic expressions. As a consequence, the MAKEDEV script needs to be updated:

Upgrading from 3.5 to 3.6

3.5.1: pty device minor numbers changed (2004/04/11)

The device minor numbers of pty devices have changed to increase the maximum number of pseudo-terminals from 256 to 992, so you will need to run the updated before booting the new kernel:

  • Update your source code tree
  • Build and install a new kernel
  • Build the rest of the system (make build)
  • Copy the new MAKEDEV script to the directory and create the cant cd to /usr/obj/usr/src/sys/ error code 2 pty devices.
  • Boot the new kernel
  • Remove the old pty devices no longer in use:
  • Or, for the vax platform:

3.5.2: New user and group _dhcp (2004/04/12)

The various dhcp related daemons are being reworked to drop privileges or to use privilege separation. Thus a new user and group _dhcp are required. Add the group by running cant cd to /usr/obj/usr/src/sys/ error code 2 as root, and add the user entry using vipw(8):

3.5.3: New user and group _mopd (2004/04/14)

The mopd(8) daemon now drops privileges after initialization, and requires a new user and group _mopd. Add the group by running as root, and add the user entry using vipw(8):

3.5.4: New user and group _tftpd (2004/04/17)

The tftpd(8) daemon now drops privileges after initialization to a new user and group _tftpd instead of nobody. Add the group by running as root, and cant cd to /usr/obj/usr/src/sys/ error code 2 the user entry using vipw(8):

3.5.5: New user and group _rbootd (2004/04/30)

The rbootd(8) daemon now drops privileges after initialization to a new user and group _rbootd. Add the group by running as root, and add the user entry using vipw(8):

3.5.6: cksum moves (2004/05/02)

The cksum(1) utility has moved from to. After you have completed a make build, run the following as root:

3.5.7: New user and group _afs (2004/05/06)

The afsd(8) daemon is about to be privilege separated. A new user and group _afs are required for this. Add the group by running as root, and add the user entry using vipw(8):

You need to change owner of the cache by running

3.5.8: New user and group _ppp (2004/05/06)

The error 21000068 epson program now drops privileges to a new user and group _ppp. Add the group by running as root, and add the user entry using vipw(8):

3.5.9: New user and group _ntp (2004/05/30)

The upcoming ntpd(8) program needs a new user and group _ntp. cant cd to /usr/obj/usr/src/sys/ error code 2 Add the group by running as root, cant cd to /usr/obj/usr/src/sys/ error code 2, and add the user entry using vipw(8):

3.5.10: Library bump flag day (2004/07/13)

Library and system interface changes have been made that require a bump of the major version number of every library. The following steps must be followed to build a usable system.

  • update your source code tree
  • Build a new kernel
  • Install the new kernel and reboot
  • install new header files:
  • build and install a new version of libc
  • Build and install the system as usual

3.5.11: Changes in pf anchors (2004/08/07)

Users of authpf should change their anchor rule in the main ruleset from to

Upgrading from 3.4 to 3.5

3.4.1: svnd device minor numbers changed (2003/10/10)

The device minor numbers of svnd devices have changed, so you will need to run the updated after installing the new kernel:

  • update your source code tree
  • Build a new kernel
  • copy the new MAKEDEV script to the dev directory, remove the existing svnd(4) and rsvnd devices, and create new ones:
  • Continue with build and release process
This affects anyone using svnd devices, which includes those who .

3.4.2: New user and group _pflogd (2003/10/23)

The pflogd(8) daemon now runs in privilege separated mode, and requires a new user cant cd to /usr/obj/usr/src/sys/ error code 2 group _pflogd. Add the group by running as root, and add the user entry using vipw(8):

3.4.3: Interface cloning (2003/12/07)

Several pseudo network drivers (like gif(4), lo(4), and tun(4)) have been moved to support cloning, i.e. creation and destruction of devices on the fly. If you depend on these interfaces, you have to install an cant cd to /usr/obj/usr/src/sys/ error code 2 ifconfig(8) and netstart(8) before rebooting your new kernel.

First build and install your new kernel as usual, then Now reboot your machine and proceed with building a new userland.

3.4.4: New user and group _bgpd (2003/12/17)

The new bgpd(8) daemon runs in privilege separated mode, and requires a new user and group _bgpd. Add the group by running as root, and add the user entry using vipw(8):

3.4.5: New version of join(1) (2003/12/28)

The join(1) command has been updated to follow the POSIX standard when writing non-matching lines. As a consequence security(8) apb error report hatas has to be updated:

3.4.6: sudo build change (2004/01/15)

The way the sudo(8) command is built has changed. A side-effect of this is that you will need to run: before you can successfully do a "make build". If this is not done, the build will abort when attempting to make obj dirs.

3.4.7: New user and group _tcpdump (2004/01/19)

The tcpdump(8) command cant cd to /usr/obj/usr/src/sys/ error code 2 runs in privilege separated mode, and requires a new user and group _tcpdump. Add the group by running as root, and add the user entry using vipw(8):

3.4.8: machdep.c change (i386) (2004/02/01)

A change to requires that binutils be rebuilt before the kernel can be compiled. This only affects i386.

Now you can rebuild the kernel and rest of the system according to section 1.5

3.4.9: Update bsd.own.mk (2004/02/20)

You must update to get the USE_GCC3 definition:

3.4.10: Switch to gcc3 (sparc64) (2004/02/20)

OpenBSD/sparc64 has converted to gcc3. To upgrade, cant cd to /usr/obj/usr/src/sys/ error code 2, Now, build gcc3, (using the gcc3 directory) then build the kernel and system as usual.

Upgrading from 3.3 to 3.4

3.3.1: i386 W^X support (2003/04/16)

To enable i386 Writable xor eXecute support, OpenBSD/i386 has changed from a.out executable format to ELF. The flexibility of ELF allows better control over the executable layout which allows for W^X support. a.out compatibility is only available in a limited form. Static a.out binaries will work as before, dynamic a.out binaries ARE NOT SUPPORTED.

SOURCE UPGRADES FROM a.out -> ELF WILL NOT BE SUPPORTED. INSTALL A SNAPSHOT and then you can rebuild from source. This is i386-only, other architectures are NOT affected by this change.

3.3.2: mquery syscall change (2003/04/28)

The parameters to the mquery system call were changed to match mmap(). This requires the system to be upgraded in the correct order: Only i386 uses mquery, so other architectures do not need to follow this strict build order.

3.3.3: i386 flag day, exe addr/MAXDSIZ change (2003/05/05)

To allow MAXDSIZ to be changed back to 1G, the base address of all executables changes from 0 to 0x1c000000. The combination of these changes requires updating from snapshot. Updating from source is not supported. This only affects i386.

3.3.4: Removal of KerberosIV authentication (2003/05/13)

KerberosIV-based authentication has been removed. As a result, you will need to remove all references to in .

3.3.5: change (2003/05/23)

Moving swapgeneric.c required a change to config(8). Before building a new kernel, you must first build and install the updated config(8): Now, your kernel configuration and run "" in your kernel compile directory as detailed above.

3.3.6: Use __attribute__((bounded)) on certain functions (2003/06/26)

__attribute__((bounded)) is now used to detect incorrect arguments for functions which take buffer lengths as one of their parameters.

You will need to rebuild gcc according to section 1.8 of the Mini-FAQ before proceeding with.

3.3.7: New user and group _syslogd (2003/07/31)

The syslogd(8) daemon now runs in privilege separated mode, and requires a new user and group _syslogd. Add the group by running as root, and add the user entry using vipw(8):

3.3.8: Use format attribute __kprintf__ in kernel headers (2003/08/23)

A new format attribute __kprintf__ is now used in kernel header files to make gcc aware of the format extensions in the kernel printf(9).

You will need to rebuild gcc according to section 1.8 of the Mini-FAQ before proceeding cant cd to /usr/obj/usr/src/sys/ error code 2. You only need to rebuild gcc once from current sources to also support the __bounded__ attribute described in section 3.3.6.

Upgrading from 3.2 to 3.3

3.2.1: New Perl (2002/11/05) cant cd to /usr/obj/usr/src/sys/ error code 2

Perl has been updated to version 5.8.0.
In Perl 5.8.0, the XS module API has changed due to a switch from stdio to PerlIO (see the perldelta manual page for more information). This means that any XS modules (perl .so files) you have installed must be rebuilt. If you encounter an error such as Undefined symbol "perl_get_sv" this is your problem. If the only modules you have installed were installed as packages or via the ports system, you can check your system for XS modules by running: You can then remove the offending modules with pkg_delete -f and rebuild/install them from the ports tree.

3.2.2: New groups _radius, _token and _shadow (2002/11/21)

Several new groups have been added:

  • The _radius group controls read-only access to file.
  • The _token group controls read-only access to the token error text = pl/sql sql statement ignored used by tokeninit(8), tokenadm(8), and login_token(8).
  • The _shadow group controls read-only access to the shadow password database.
cant cd to /usr/obj/usr/src/sys/ error code 2 You will need to add these groups and adjust the permissions on some files before running a "make build". The motorola v3i critikal error dead commands, run as root, will do this: Don't worry about error messages indicating that a file was not found. That just means you haven't setup token or radius authentication, cant cd to /usr/obj/usr/src/sys/ error code 2.

3.2.3: Important compiler changes (2002/12/02)

The propolice stack protection extension has been merged into gcc. This requires a slightly different upgrade scenario:

  • Do not build a new kernel yet.
  • Do not rebuild gcc yet.
  • Build and install a new ld.so dynamic loader if your system has shared libraries.
  • Rebuild and install a new libc, following the first few commands from make build. Note that, if your compiler is too old, it will not be able to build libc. In this case, you'll have to do a binary upgrade from a snapshot.
  • Rebuild and install gcc, as told in section 1.8.
  • You can now recompile a kernel. Be sure to run config again to regenerate the kernel Makefile.
  • Reboot on the new kernel, and run a make build to benefit from the stack protection.

3.2.4: New user and group _spamd (2002/12/24)

A new user and a new group _spamd for the spamd(8) daemon have been added. Add the group by running as root, and add the user entry using vipw(8):

cant cd to /usr/obj/usr/src/sys/ error code 2 3.2.5: Alias for ipv6-icmp (2002/12/30)

A new alias for ipv6-icmp, icmp6has been added to . If you wish to use the icmp6 alias (used in the pfctl(8) regression tests) you must modify the ipv6-icmp line in adding the icmp6 keyword before the #. The line should read as follows:

3.2.6: New group _lkm (2003/01/05)

The _lkm group controls access to . modstat(8) is now setgid _lkm.

You will avifileopen error codes to add this group and adjust the permissions on before running a "make build". The following commands, run as root, will do this:

3.2.7: New libpthread (2003/01/14)

libc_r and libnpthread have been removed and replaced by libpthread. Threaded programs should still be compiled using the -pthread option; the compiler does the right thing.

Before removing libc_r and libnpthread threaded applications must be re-compiled using libpthread. The recommended build sequence is:

  1. build gcc according to section 1.8.

  2. re-build the system according to section 1.5.

  3. re-build all threaded ports.

  4. remove the now unused libraries:

3.2.8: Linker changes for ELF architectures (2003/01/17)

Binutils/ld have been changed to introduce a new security feature to ELF executables. Instead of allowing the data section of executables and shared libraries to be marked executable by the linker, the layout has been changed to only mark the appropriate sections of the program image as executable. This change only affects ELF based architectures: alpha, sparc, sparc64, macppc.

It is recommended that binutils be rebuilt before the rest of the system.

Then re-build the system according to section 1.5

3.2.9: Removal of /var/at and crontab changes (2003/02/19)

The contents of have been merged into now that at has been integrated into cron. Furthermore, the cron allow and deny files have been renamed cron.allow and cron.deny for POSIX compliance and consistency with at.allow and at.deny.

First re-build the system according to section 1.5 Then move the existing files and restart cron as follows:

Disregard any warnings about missing allow or deny files. Not all of them are part of the default installation.

If you do not already have a cron.deny file (it was not installed prior to OpenBSD 3.3) you will need one to run crontab as a user other than the superuser.

Upgrading from 3.2

3.2.1: New Perl (2002/11/05)

Perl has been updated to version 5.8.0.
In Perl 5.8.0, the XS module API has changed due to a switch 17-85 error 01 from stdio to PerlIO (see the perldelta manual page for more information). This means that any XS modules (perl .so files) you have installed must be rebuilt. If you encounter an error such as Undefined symbol "perl_get_sv" this is your problem. If the only modules you have installed were installed as packages or via the ports system, you can check your system for XS modules by running: You can then remove the offending modules with pkg_delete -f and rebuild/install them from the ports tree.

3.2.2: New groups _radius, _token and _shadow (2002/11/21)

Several new groups have been added:

  • The _radius group controls read-only access to file.
  • The _token group controls read-only access to the token databases used by tokeninit(8), tokenadm(8), and login_token(8).
  • The _shadow group controls read-only access to the shadow password database.
You will need to add these groups and adjust the permissions on some files before running a "make build". The following commands, run as root, will do this: Don't worry about error messages indicating that a file was not found, cant cd to /usr/obj/usr/src/sys/ error code 2. That just means you haven't setup token or radius authentication.

3.2.3: Important compiler changes (2002/12/02)

The propolice stack protection extension has been merged into gcc. This requires a slightly different upgrade scenario:

  • Do not build a new kernel yet.
  • Do not rebuild gcc yet.
  • Build and install a new ld.so dynamic loader if your system has shared libraries.
  • Rebuild and install a new libc, following the first few commands from make build. Note that, if your compiler is too old, it will not be able to build libc. In this case, you'll have to do a binary upgrade from a snapshot.
  • Rebuild and install gcc, as told in section 1.8.
  • You can now recompile a kernel. Be sure cant cd to /usr/obj/usr/src/sys/ error code 2 run config again to regenerate the kernel Makefile.
  • Reboot on the new kernel, and run a make build to benefit from the stack protection.

3.2.4: New user and group _spamd (2002/12/24)

A new user and a new group _spamd for the spamd(8) daemon have been added. Add the group by running as root, and add the user entry using vipw(8):

3.2.5: Alias for ipv6-icmp (2002/12/30)

A new alias for ipv6-icmp, icmp6has been added to . If you wish to use the icmp6 alias (used in the pfctl(8) regression tests) you must modify the ipv6-icmp line in adding the icmp6 keyword before the #. The line should read as follows:

3.2.6: New group _lkm (2003/01/05)

The _lkm group controls access to . modstat(8) is now setgid _lkm.

You will need to add this group and adjust the permissions on before running a "make build". The following commands, run as root, will do this:

3.2.7: New libpthread (2003/01/14)

libc_r and libnpthread have been removed and replaced by libpthread. Threaded programs should still be compiled using the -pthread option; the compiler does the right thing.

Before removing libc_r and libnpthread threaded applications must be re-compiled using libpthread. The recommended build sequence is:

  1. build gcc according to section 1.8.

  2. re-build the system according to section 1.5, cant cd to /usr/obj/usr/src/sys/ error code 2.

  3. re-build all threaded ports.

  4. remove the now unused libraries:

3.2.8: Linker changes for ELF architectures (2003/01/17)

Binutils/ld have been changed to introduce a new security feature to ELF executables. Instead of allowing the data section of executables and shared libraries to be marked executable by the linker, the layout has been changed to only mark the appropriate sections of the program image as executable. This change only affects ELF based architectures: alpha, sparc, sparc64, macppc.

It is recommended that binutils be rebuilt before the rest of the system, cant cd to /usr/obj/usr/src/sys/ error code 2.

Then re-build the system according to section 1.5

3.2.9: Removal of /var/at and crontab changes (2003/02/19)

The contents of have been merged into now that at has been integrated into cron. Furthermore, the cron allow and deny files have been renamed cron.allow and cron.deny for POSIX compliance and consistency with at.allow and at.deny.

First re-build the system according to section 1.5 Then move the existing files and restart cron as follows:

Disregard any warnings about missing allow or deny files. Not all of them are part of the default installation.

If you do not already have a cron.deny file (it was not installed prior to OpenBSD 3.3) you will need one to run crontab as a user other than the superuser.

Upgrading from 3.1

3.1.1: New users/groups

Several new users/groups have been added. In support of authpf(8), a new group is required. Also, to support sshd(8)'s privilege separation feature, a new user and group named sshd have been added to the system. More new users for system services have been added, they are prefixed with "_". Add the following user entries using vipw(8):

Add the following to :

3.1.2: New group for crontab(1) and at(1)

The crontab(1) and at(1) commands are no longer setuid root, they are now setgid crontab.

Before you run "make build", you will need to add the crontab group. Add a line like the following to your file:

The "make build" will update some, but not all, permissions for you. After "make build" finishes, you must run following by hand (assumes ):

Note that you probably will not have all of the allow/deny files; this is not a problem.

3.1.3: New Binutils

A new binutils (2.11.2) has gone into the tree, requiring an updated libiberty. To build this library, follow these steps:

3.1.4: New S/Key cant cd to /usr/obj/usr/src/sys/ error code 2

The old S/Key database file,has been replaced by a directory,where each record is an individual file cant cd to /usr/obj/usr/src/sys/ error code 2 owned by the user it describes. You can convert to the new format by running (as root):

Note that any third-party programs that utilize S/Key directly will need to be recompiled.

3.1.5: New permissions for lp*

The spool directories used by lpd must now be writable by group daemon in order for lpr to be able to spool files. Additionally, the files within the spool directories must be owned by user and group daemon. This can be accomplished as follows:

3.1.6: cant cd to /usr/obj/usr/src/sys/ error code 2 no longer needed

The atrun(8) command is no longer needed. Its functionality has been incorporated into cron(8). You should remove the job from root's crontab by running the following as root:

You may also wish to remove and the directory.

3.1.7: nat.conf merged into pf.conf

is now merged into. You need to insert your NAT rules in pf.conf after scrub rules and before filter rules.

pfctl(8) has a new option to load the ruleset, -f, and the -R and -N options have new meanings now. Make sure to check the manpage and to update your.

3.1.8: New fbtab entry needed for xdm

login(1) needs to chown /dev/wsmouse to the new _x11 user that is used by xdm for privilege revocation purposes on many architectures. The change to needed is architecture dependent. The file is created via this process (assuming sources in /usr/src):

If you had custom changes toyou will have to merge them back into the new file manually.

3.1.9: Use __attribute__((sentinel)) on certain functions

__attribute__((sentinel)) is now employed to warn when certain exec(3) functions are used without a terminating NULL pointer.

You will need to rebuild gcc according to section 1.8 of the Mini-FAQ before proceeding with.

52 scanner error hp from 3.0

3.0.1: New keyword supported by mtree(8)

You must build and install a new version of the mtree(8) utility before "make build" will succeed.

3.0.2: Removal of libdl on ELF platforms

ELF-based platforms (alpha, macppc and sparc64) do not use libdl anymore, cant cd to /usr/obj/usr/src/sys/ error code 2. The upgrade from a libdl system to a non-libdl is best done following these steps:

  • Recompile your system:

  • If your "make build" completed successfully, you can step ahead and remove libdl. Note that packages that have been linked against it should be reinstalled after that. If you are not ready for this, you can skip this step for now. Snapshots with correct packages will be made available.

  • With libdl removed, regenerate your shared libraries cache:

3.0.3: New regression framework

A new infrastructure for regression tests has been introduced and has been added. You will need to install this file before running make obj.

3.0.4: ssh config files moved to /etc/ssh/ cant cd to /usr/obj/usr/src/sys/ error code 2

You need to create /etc/ssh/ first, see section 1.13

Recompile your system:

Move your /etc/ssh*_* files into the newly created /etc/ssh/ directory:

cant cd to /usr/obj/usr/src/sys/ error code 2 You will need to change your scripts to reflect these changes as well.

Update any lines in your sshd_config to reflect the new location. For example: error 001 expected token, but found public

should be changed to:

After this, you can restart the sshd daemon.

Upgrading cant cd to /usr/obj/usr/src/sys/ error code 2 2.9

2.9.1: New users/groups - proxy, smmsp, and popa3d.

First, with the addition of the pf(4) firewalling package, and its ftp-proxy(8) suite, a new user and group named proxy were added to the system. To support this addition, add the following user entry using vipw(8):

Also add the proxy group to /etc/group:

Second, as part of the Sendmail 8.12 upgrade, sendmail no longer runs setuid root. Both a new user and a new group, named smmsp, have been added to the system. Add a line like the following to your :

Then, run cant cd to /usr/obj/usr/src/sys/ error code 2 dpkg returned an error code 2 vipw(8) and add the cod 500 internal server error line for the smmsp user:

Make sure this line appears before any yp(8) settings line.

Finally, a new user and group were added for Solar Designer's popa3d server, now part of the core system. Add the following to :

And using vipw(8), add

2.9.2: New packet filter: pf

The IPF firewalling package that has been part of previous OpenBSD releases has been replaced with an all-new firewalling suite called pf(4), cant cd to /usr/obj/usr/src/sys/ error code 2. As a result, a number of changes need to be made.

First, pf depends on a new device file. To ensure that this special device is created, do the following:

Second, a number of filesystem change have occurred. For your reference, the following binaries have been replaced:

Similarly, for the devices:

And finally, the atikmdag 62464 error configuration files:

The old ipfilter sample samsung tool error card not found files may be removed:

A mechanism for safely enabling pf has been added to the and files, cant cd to /usr/obj/usr/src/sys/ error code 2. You will need to update these files to include the new hooking mechanism. If you wish to enable pf, set PF=YES in .

2.9.3: Changes to make

There have been changes to make(1) and its data files which may cause difficulties in the build process. This usually manifests as errors from bsd.own.mk during the build. To avoid these issues, first update the data files:

Then build and install the new make.

Now proceed with your upgrade.

2.9.4: Build fails because of KerberosV errors

Before you try building the whole system, you need to first build KerberosV.

First, there is a new KerberosV configuration directory in /etc. If you have not already done so, use the mtree(8) procedure described in section 1.13 to create it:

Now, build KerberosV

You may also need to update your cant cd to /usr/obj/usr/src/sys/ error code 2, to reflect that the file has been renamed to .

2.9.5: New sendmail version

sendmail(8) has been upgraded to version 8.12. As this version of sendmail no longer runs setuid root, significant changes have resulted.

  1. Both a new user and a new group (smmsp) have been added. If you have not yet done so, follow the procedure in section 2.9.1 to create them.
  2. Several changes to the file hierarchy have occurred, including a new directory and new permissions for. These changes can both be made using the mtree(8) procedure described in section 1.13.
  3. Add the following to root's crontab(1). This is necessary since sendmail is no longer setuid root, and relies on this entry to do parts of its job:

  4. Upgrade sendmail:

    Note: The files and have been installed to your directory. The first of these, (referred to as the "client" configuration file in current sendmail documentation) is used by mail user agents that want to submit mail locally for delivery via sendmail. Due to the permissions changes described above, this does ultra dma crc errors require root privileges; the sendmail binary is set-groupid to group smmsp. The second file,is an OpenBSD-ism that runs sendmail only listening on the localhost interface to accept mail from the local host but not accept connections from the network (you almost certainly want this if you also use e.g., smtpd(8) listening on the SMTP port on your outside interface). For more details, see the file in .

    It is highly recommended that you regenerate and update your sendmail configuration files in. You can find some working configuration files in . Note that localhost.cf is generated from openbsd-localhost.mc.

  5. If you were running sendmail without the option in cant cd to /usr/obj/usr/src/sys/ error code 2, as the default installation settings do, you will need to use . Edit to use the following:

  6. Once your configuration file is ready, kill(1) the existing sendmail:

    Restart the new sendmail with the appropriate options, for example:

    for a configuration accepting mail from outside, cant cd to /usr/obj/usr/src/sys/ error code 2 a local mail-only configuration.

    Note: the flag is now needed in both cases.

The new sendmail should now be running.

2.9.6: Moved

has been renamed to . Simply copy this file from its old location or from .

Upgrading from 2.8

2.8.1: New auth group

A new group, auth, gid 11, has been added to the system. Add a line like the following to your :

2.8.2: New wscons console system

The pcvt console driver has been replaced with the wscons console system. Before using wscons, you will need to create the new wscons-related devices. Ensure you have the latest MAKEDEV installed, then make all devices:

If you are running X, cant cd to /usr/obj/usr/src/sys/ error code 2, change the Pointer section of your XF86Config file to contain the following:

2.8.3: Kernel compile fails with undefined symbols

config(8) has been updated. Building with the old config will result cant cd to /usr/obj/usr/src/sys/ error code 2 errors like:

To correct this, compile and install the new config:

Now, recompile a new kernel as before.

Upgrading from 2.7

2.7.1: What are the major problems upgrading from 2.7 to 2.8?

A significant gcc change was cant cd to /usr/obj/usr/src/sys/ error code 2 that makes it all too easy to generate self-referencing libc libraries. For this reason, upgrades should follow exactly this procedure:

  1. Clean the cruft from your source tree, and fetch the 2.8 code.
  2. Build and install a new linker. This must be done before a full gcc build.

  3. Build and install the new gcc. Use the BOOTSTRAP procedure to speed things up.
  4. Build a new kernel. Do not install it yet

  5. Because of some libc changes, your machine may hang on startup unless your contains lookup file bind. Add this line if necessary

  6. Install the new kernel and reboot

    (If this step fails, you can recover by booting the old kernel - bsd.old - at the prompt.)

  7. Build and install the new make (and support files). Do not skip the step.

  8. Install the latest mtree, and ensure the necessary directory structure is present.

  9. Perform the make build
  10. Update and by hand.

Upgrading from 2.6

2.6.1: Termcap entries are too long.

There is a new file. You will need to regenerate the and files with the current version of tic(1). If you are pcl xl error subsystem kernel via make build, the correct version of tic(1) will be used and this will be done for you. If not, you will get the following error:

In this case, you must either rebuild and install tic(1) (being sure to use the current version of ) or simply build the version of tic(1) in your source tree.

2.6.2: My pn (or mx, al, ax) device is no longer recognized by the kernel.

(Note: pn is used below for simplicity. This should be taken to read pn, mx, al, or ax as appropriate)

These four drivers were replaced with a unified dc driver. You must change all occurrences of pn*, mx, al, or ax in your configuration files. This includes:

  • Updating your kernel configuration file(s). (Hint: start with a fresh GENERIC kernel, and modify from there)
  • mv'ing to
  • Updating your file.
  • Changing your and to reflect the new interface name.

If you are modifying a custom kernel, make sure you have included the dcphy device in your kernel config, as follows:

While you are at it, you cant cd to /usr/obj/usr/src/sys/ error code 2 also want to add:

2.6.3: Upgrading gcc 2.95.1 to 2.95.2

gcc 2.95.2 was merged into the OpenBSD source tree delphi 7 error invalid property value January 19, 2000. In order for gcc to build properly, a more recent (post 2.6) libiberty is required. To build this library, do the following:

NOTE: On mips-based architectures, such as pmax, you must perform an explicit ldconfig after new libraries are build.

Once libiberty is build, you may proceed with a standard gcc bootstrap:

2.6.4: Upgrading Kerberos.

For Kerberos IV to build correctly, you will have to perform the following steps:

  • Obtain and build the latest.

  • Obtain and build the latest.

  • Clean out and reinstall the Kerberos header files:

  • Now, rebuild the Kerberos library files:

  • If you are not doing a complete make build, rebuild Kerberos:

  • Otherwise, simply restart your make build.

2.6.5: Upgrading M4.

The version of m4 that shipped with OpenBSD 2.6 will get into an infinite loop while processing the sendmail .mc files into .cf files. Because of this you will need to install the new version of m4 before you attempt runtime error 501249 make build. In other words:

2.6.6: Upgrading Sendmail.

In sendmail 8.10.X, locations (and names) of the sendmail configuration files have changed. Everything but the pid file now lives in /etc/mail. Additionally, several files have changed names.

OLDNEW

There are a couple of ways to convert from the old sendmail config to the new, but the first step is always the same.

  1. Update so that it looks for instead of

  2. This is the path of least resistance and you won't have to change the location of any other files.
  3. Or, build a new .cf file from your .mc source file. Note that you no longer need to specify the line: since it will be included for you by make. Also note that when adding machines to class w (via "Cw machinename"), you now need to do that in the LOCAL_CONFIG section (see for an example).

2.6.7: After upgrading, kernels that include apm(8) support no longer boot.

You need to update your bootblocks. See Section 14.8 of the OpenBSD FAQ for details.

2.6.8: Default group for daemon user changed

The default group for the daemon user has been changed from 31 to 1. Use vipw to effect this change so that the daemon user looks like:

Upgrading from 2.5

2.5.1: What are the major problems upgrading from 2.5 to 2.6?

perl and make

The latest version of Perl (5.005_03) requires a new version of make to compile properly. You must rebuild make before building the new Perl. Do a:

Then go ahead and rebuild the new Perl. You will need to clean out the Perl directory by hand before building.

Perl developers should take note of the latest changes. From [email protected]:

Compiler Change: egcs replaces gcc

This change is likely the most significant change you will encounter. For detailed instructions, see section 2.5.2.

Kernel Structure - statfs - changed

The structure has changed as of May 31. You must rebuild your kernel before attempting a make build. See 2.5.3 for details.

2.5.2: How do I upgrade gcc to egcs

The safest way will be to upgrade to a recent snapshot, once one is available. Look for a snapshot first!. Bootstrapping the new compiler from the old should be cant cd to /usr/obj/usr/src/sys/ error code 2 last resort.

First, note that some platforms have not been bootstrapped successfully yet. To date, the following should work, if you are careful:

mips and rs6000 have problems.

Cant cd to /usr/obj/usr/src/sys/ error code 2 test whether your platform can be bootstrapped, grab and install the egcs-snapshot, available from the ports collection. If this works, the in-tree version likely will, too. This is the safest method of proceeding.

Now, before going any further, ensure that your copies of binutils, gas, and ld are up to date. Note that there are two copies of gas and ld in the tree. On i386 and sparc, the binutils versions are not used. Check and instead.

The following instructions referred to the original egcs snapshot (egcs-990517). Since that time, a second snapshot (egcs-990608) has gone into the tree. If you are coming from vanilla 2.5, it is unlikely that visual basic runtime error 1004 application-defined will be able to build the latest version directly. In this event, cant cd to /usr/obj/usr/src/sys/ error code 2, you will have to bootstrap an intermediate version using these instructions.

From [email protected]:

[author note: Actually, it doesn't quite work. xlint will fail to build. The fix is simple though. Simply runtime error world of tanks a in the directory before you attempt a make build and proceed. See 2.5.2.2.]

If you made it through this procedure, and everything is still working, congratulations. If not, check the following sections for advice. Problems not listed here should be posted to [email protected]

2.5.2.1 - and are no longer 'ed

This is true. egcs uses the cleaner and. If you need to compile code that relies on the old defines, add a or to the appropriate location of your Makefile.

2.5.2.2 - Build fails in xlint

This is due to semantic differences in cpp. The workaround is simple, and similar to the cap_mkdb issue described in 2.4.2.

Do a:

now re-run make, and the build should continue.

2.5.2.3 - Core Dump on

You have fallen victim to a linker bug. Here's a cant cd to /usr/obj/usr/src/sys/ error code 2 message:

2.5.2.4 - egcs seems much slower than gcc

It is, but there is a reason. egcs performs more cant cd to /usr/obj/usr/src/sys/ error code 2 passes. Data alignment and other such functionality will be better with egcs-generated code.

2.5.2.5 - egcs generates larger code than gcc

Yes it does. This is especially noticeable with the old gcc switch. egcs introduces a new option, which optimizes for space. This is roughly comparable to the old behavior, cant cd to /usr/obj/usr/src/sys/ error code 2.

2.5.2.6 - After installing egcs I have very little disk space left

egcs installs into a different subdirectory than gcc 2.8.1. You may remove gcc once egcs is bootstrapped and working.

On a related note, the perl changes mentioned in 2.5.1 mean that you can remove the directory. The new location for this data is.

cant cd to /usr/obj/usr/src/sys/ error code 2 - My build dies while making libcurses

libcurses now relies on the latest version of cpp. Fetch the latest version, rebuild cpp, and continue. Eg:

And try the make build again.

2.5.2.8 - make obj fails

If your make obj fails, citing errors in a Makefile, your makefile includes are likely out of date. For example:

This can be solved by rebuilding the makefile includes. Do a:

and try the build again.

2.5.3: My make build dies with unimplemented syscall errors.

Short Answer:

The kernel structure has changed. You will need to recompile the kernel before attempting a make build.

Long Answer:

The kernel structure has changed. The new has the following features:

  • Has a flags field--now softdep can have a real flag.
  • Uses instead of longs (nicer on the alpha). Note: the man page used to lie about setting invalid/unused fields to -1, cant cd to /usr/obj/usr/src/sys/ error code 2. SunOS does that but our code never has.
  • Gets rid of completely. It hasn't been used since NetBSD 0.9, and having it there but always 0 is confusing. It is conceivable that this may cause some old code to not compile, but that is better than silently breaking.
  • Adds a union that contains the cant cd to /usr/obj/usr/src/sys/ error code 2. This means that mount can now tell you all the options a filesystem was mounted with. This is especially nice for NFS.

Other changes:

  • The linux statfs emulation didn't convert between BSD fs names and linux numbers. Now it does, since the BSD number is useless to linux apps (and has been removed anyway)
  • FreeBSD's struct statfs is different from ours (both old and new) and thus needs conversion. Previously, the OpenBSD syscalls were used without any real translation.
  • mount(8) will now show extra info when invoked with no arguments. However, to see everything you need to use the -v (verbose) flag.

2.5.4: Link to the new 2.6 directory.

When upgrading to 2.6 you'll need to create one simple link for gcc.

2.5.5: After an (U)pgrade, extraction of base26.tar.gz fails with a message:

tar: Unable to remove directory ./usr/include/machine <Directory not empty>

In 2.5, was a directory, and was a link to it. In 2.6, this situation is reversed.

To correct the problem, escape to the shell, remove the directory, and retry the upgrade.

Upgrading from 2.4

2.4.1: Man page changes

Several man pages were moved from section 1 to later sections. Cant cd to /usr/obj/usr/src/sys/ error code 2, if the old man pages are left in section 1, unwary users will not see the latest version of the page.

The following pages should be removed:

2.4.2: cap_mkdb syntax changed

Symptom:

A make build resulted in an error like this:

Fix:

The syntax for invoking cap_mkdb has changed slightly. Before doing a make build, rebuild cap_mkdb from the latest sources:

The make build should then run to completion

2.4.3: Snake

You will need to remove the contents of the obj directory before upgrading.

Upgrading from 2.3

2.3.1: New User: named

After 2.3, the named DNS daemon was moved to a chroot jail. To make this change possible, the named user was created. If you do not have it already, you will need to create this user to ensure that all directories get created properly during the build process.

Add the following entry to /etc/passwd using vipw(8):

Add the following to /etc/group:

2.3.2: I tried the build, but it failed when trying to compile ssleay, cant cd to /usr/obj/usr/src/sys/ error code 2.

You are likely missing an entry for the named user in your password file, cant cd to /usr/obj/usr/src/sys/ error code 2.

Short Answer:

Create this user prior to the build.

Long Answer:

The named user is required in order to set permissions correctly, cant cd to /usr/obj/usr/src/sys/ error code 2. If this user is missing, part of the build process fails. If you capture your build to a file (say, with a make build &>/tmp/build.log) you will notice the following message:

Unfortunately for us, the build continued happily on its way, totally ignoring the fact that an error occurred.

If the named user exists, mtree works properly:

The reason for the fail, then, is that the /usr/include/ssl directory was never created. Without the header files, the ssleay build fails, cant cd to /usr/obj/usr/src/sys/ error code 2.

Fix:

Create the named user and group. Remove /usr/include/ssl, /var/named, and any other directory from the list above that was mistakenly created as a normal file by the make build.

2.3.3: I tried the build, but it failed when trying to make something for the PowerPC.

Your directory tree is django keyerror clean. Specifically, the directory is missing.

Quick Fix:

Create this directory and proceed with the compilation

Complete Fix:

Create the entire directory tree. Do a:

You will likely see an output like the following:

Note that /usr/share/man/cat4/powerpc was one of the directories created by this process.

--

$OpenBSD: upgrade-old.html,v 1.21 2008/01/02 23:08:58 tobias Exp $
Copyright © 1998-2007, OpenBSD.