Help - Search - Members - Calendar
Full Version: Upgrading Your Openbsd Zaurus
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > OpenBSD
mathemajikian
Since 4.0 is right around the corner I want to kind of prepare myself for a successful upgrade. From Andys guide I obtained the following

QUOTE
*Maintenance Step, On subsequent OpenBSD releases updating the initrd.bin*

When a new OpenBSD version is released for the Zaurus (or a snapshot) if you decide to install that release it is probably wise to update zbsdmod.o and zboot located in the flash of the Zaurus.

To achieve this update perform the following steps.

i. Copy zbsdmod.o and zboot to a storage card.

ii. Enter Emergency Linux as described earlier in this document.

iii. Enter the following commands..

mkdir /mnt/flashroot
mount -t jffs2 /dev/mtdblock2 /mnt/flashroot
cd /mnt/flashroot/bsd

iv. Insert the storage card and copy the new versions of zboot and zbsdmod.o to this location as follows (if using a CF card then substitute the path /mnt/cf for /mnt/card).

cp /mnt/card/zbsdmod.o .
cp /mnt/card/zboot .

v. Flag zboot as executable using..

chmod +x zboot

vi. Reboot the device using...

shutdown -r now


If I download the source can the kernel be built normally on the Z? If so how long would this take? I'm assuming x < 5 days! I know that during a normal install that the packges consisting of a base install are just pulled down and unpacked. Is there a similar way of doing this without going through the installation process?

Thanks in Advance!
iamasmith
Actually no, that updates the boot loader for the 'all disk' install that I produced and not the kernel.

Start the install process again and choose upgrade instead of install and the system will upgrade.

An upgrade will skip two important archives that are used in a base install. These archives are base.tgz and xbase.tgz therefore if you are worried about files in /etc just make sure that they are in one of these archives and you should be relatively safe to perform an upgrade and keep your changes.

Strictly speaking you should back up all of this stuff before performing the upgrade of course.

-Andy
mathemajikian
ok, so to upgrade to the current snapshot what procedures must I follow? what files must be replaced? Do I just replace the zboot and zbsdmod.o from emergency linux and then follow the normal installation process except selecting upgrade instead of install? How do I determine if I am running the lastest and greatest snapshot? uname -v ?

Thanks

QUOTE(iamasmith @ Aug 1 2006, 09:05 AM)
Actually no, that updates the boot loader for the 'all disk' install that I produced and not the kernel.

Start the install process again and choose upgrade instead of install and the system will upgrade.

An upgrade will skip two important archives that are used in a base install. These archives are base.tgz and xbase.tgz therefore if you are worried about files in /etc just make sure that they are in one of these archives and you should be relatively safe to perform an upgrade and keep your changes.

Strictly speaking you should back up all of this stuff before performing the upgrade of course.

-Andy
*
Sequethin
QUOTE(mathemajikian @ Aug 1 2006, 07:49 AM)
ok, so to upgrade to the current snapshot what procedures must I follow? what files must be replaced? Do I just replace the  zboot and zbsdmod.o from emergency linux and then follow the normal installation process except selecting upgrade instead of install? How do I determine if I am running the lastest and greatest snapshot? uname -v ?

Thanks


It's the same procedure as upgrading a normal openbsd system, with the addition of the steps required if you followed andy's (great) whole disk doc. When I download snaps I usually keep them in a directory named after the date (JULY27-SNAPSHOT, for example) so that when I hit the ftp site and see a snapshot with a new date I know how old mine is. Keep in mind that it's not always a good idea to be on the bleeding edge - there's bleeding involved wink.gif
iamasmith
actually there was a typo in my earlier response, top marks for anyone that spotted.

etcNN.tgz and xetcNN.tgz are the archives that are skipped during update (where NN = version number).
mathemajikian
***********************************************************************
HOW TO UPGRADE YOUR OPENBSD ZAURUS TO CURRENT SNAPSHOT
***********************************************************************

Warning! upgrades of OpenBSD are currently only supported from the
immediately previous release.

a. Copy the latest and greatest zbsdmod.o and bsd.rd from
ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus to sd/cf card.

b. Unplug Zaurus from AC power.

c. Remove battery cover from the SL-C3200

d. Leaving the Battery Cover OFF, return the battery cover lock to the LOCKED position.

e. Locate reset switch on the left side edge of battery compartment.

f. Open the unit so that the keyboard is accessible with one hand and the base of the unit is accessible with the other.

g. Hold down D+B on the keyboard and whilst these keys are held depress the reset button using the stylus.

h. Release the D+B keys and within a few seconds the unit should start to boot into Emergency Linux.

i. Reconnect AC power.

j. Return battery cover lock to unlocked position, Replace battery cover, Lock cover.

k. Log into Emergency Linux using the username root (no password).

l. Insert the SD or CF storage card.

m. Change directory:
# cd /mnt/card for SD card or
# cd /mnt/cf for a CF card.

n. Load kernel module:
# insmod zbsdmod.o

o. cp bsd.rd to the zboot proc entry:
# cp bsd.rd /proc/zboot

You should now be observing the OpenBSD kernel boot messages.

p. In the text below everything after a ? should be typed as is except for text in ( !@#$%^). Some options are already selected as the [default response] and will only require you to press enter. Alot of this is just commen sense but I have listed it anyway.
-------------------------------------------------------------------------------------------------------------------
Term? vt200
(I)Install (U)Upgrade (S)Shell? U
Disk? wd0
Root partition? wd0a
Use the existing filesystems defined in /etc/fstab? yes
Edit fstab? no
Use network settings on root partition? yes
Manual network configuration? no
Location of sets? ftp
Http/ftp proxy URL? none
Display list of known ftp servers? no
Server? (IP address, hostname or 'done' ) ftp.openbsd.org
Does server support passive mode ftp? yes
Server directory? pub/OpenBSD/snapshots/zaurus
Login? anonymous
Set name? all ( etc.zz and xetc.zz will not be downloaded )
Set name? done
Ready to upgrade sets? yes
Getting bsd...
-------------------------------------------------------------------------------------------------------------------
All BSD Sets should now begin to download... Time to complete download varies depending on the speed of your network connection and server usage at the time.

After all the sets have been downloaded you will be prompted once agian for the

q. locations of sets? done

OpenBSD will the begin making all device nodes and then ask you to Calibrate your touch screen.

After you have calibrated the touch screen you should see a message stating that you have now successfully upgraded your Openbsd zaurus system!

r. Type halt to reboot the system

It is strongly advised that you also download and unpack the corresponding etczz.tgz set found at ftp.openbsd.org/pub/snapshots/zaurus in a temporary directory and merge any changes by hand. Some components of your system may not function correctly until your files in `/etc' are updated. To accomplish this use a tool such as mergemaster. Mergemaster can be found in ports/sysutils/mergemaster

Finally you may want to rebuild some/all of your installed applications if they fail to operate correctly after upgrading. However, you will want to update your ports tree first.

s. Change to your ports directory:
# cd /usr/ports

t. Update your ports tree: ( This can take awhile )
# cvs -d anoncvs@anoncvs.openbsd.org:/cvs up -Pd
# make index

u. Update your ports via packages: (This is optional, you can rebuild your ports one-by-one from the ports directory)
# pkg_add -ui -F update -F updatedepends
mathemajikian
**************************************************
UPGRADING YOUR OPENBSD ZAURUS VIA CVS
**************************************************

If you haven't previously checked out /usr/src or /usr/ports then STOP and do so before continuing.

# cd /usr
# cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs checkout -P src
# cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs checkout -P ports

Use CVS to download the latest source and ports collection

This process updates the sources you have previously checked out! If you just checked them out then you can skip this step!

# cd /usr/src
# cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs up -Pd
# cd /usr/ports
# cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs up -Pd

Required pre-build processes

# make -k cleandir
# rm -rf /usr/obj/*
# make obj
# cd /usr/src/etc/mtree
# install -c -o root -g wheel -m 660 special /etc/mtree
# install -c -o root -g wheel -m 444 4.4BSD.dist /etc/mtree
# mtree -qdef /etc/mtree/4.4BSD.dist -p / -u
# cd /usr/src/etc
# env DESTDIR=/ make distrib-dirs

Build and Install the new Kernel

# cd /usr/src/sys/arch/zaurus/conf/
# config GENERIC
# cd ../compile/GENERIC
# make clean && make depend && make
# make install
# reboot
or
# cp /bsd /bsd.old
# cp bsd /bsd
# chown root:wheel /bsd
# reboot

Build and Install the new System

# cd /usr/src/
# make build
# cd /dev
# cp /usr/src/etc/etc.zaurus/MAKEDEV ./
# ./MAKEDEV all
# cd /usr/src/usr.sbin/httpd
# make -f Makefile.bsd-wrapper distribution

Build and Install mergemaster to merge any changes in the new files with the old

# cd /usr/ports/sysutils/mergemaster
# make install clean
# /usr/local/sbin/mergemaster
# reboot

Most of this information can be found here: http://www.openbsd.org/faq/faq5.html
TronDD
What is needed to run mergemaster for the files in etc and xetc?

Do I need the whole CVS tree?
mathemajikian
I always downloaded the entire cvsup tree and then ran mergemaster from /usr/src after a complete rebuild of the system. Due to limited internet access I cannot find any further information at this time.

QUOTE(TronDD @ Oct 21 2006, 05:39 PM)
What is needed to run mergemaster for the files in etc and xetc?

Do I need the whole CVS tree?
*
jpmatrix
help
i've a little problem with the upgrade process (i already had it with the install process) : when i mount the msdos filesystem where my openbsd install files are located, i see the files in UPPERcase ! so the openbsd install process cannot find them....
i've to copy them to my openbsd partition then rename all then the upgrade process find them....
is there any issue?
TronDD
QUOTE(jpmatrix @ Nov 8 2006, 08:25 PM)
is there any issue?
*


Is there any issue with what? A DOS partition having uppercase file names or with having the BSD packages on the BSD partition?

I've been upgrading by downloading the BSD files right to the BSD partition. Works great. If you have the BSD partition and can access it to get the files on, why use a DOS partition at all?
jpmatrix
well,
i used to download openbsd install files from my desktop pc (adsl powered!) then put the files on a cf card . it is a windows machine so the cf is fat formated.

when i mount the cf under openbsd i see the openbsd files in uppercase....so the install script cannot find them....... that only happens under openbsd. when i mount the card under qtopia or D+B startup mode, the files are in lowercase...that's why i talked about an issue with openbsd.

of course i could download the files from the openbsd onto my openbsd partition, although it would be longer...
zogs
for bsd.rd you can try on openbsd with:

# cd /
# wget ftp://ftp.openbsd.org/pub/OpenBSD/4.0/zaurus/bsd.rd
# reboot

and on the boot:

boot> bsd.rd

QUOTE(mathemajikian @ Aug 18 2006, 01:31 AM)
***********************************************************************
HOW TO UPGRADE YOUR OPENBSD  ZAURUS TO CURRENT SNAPSHOT
***********************************************************************

Warning! upgrades of OpenBSD are currently only supported from the
immediately previous release.

a. Copy the latest and greatest  zbsdmod.o and bsd.rd from
ftp.openbsd.org/pub/snapshots/zaurus to sd/cf card. 

b. Unplug Zaurus from AC power.

c. Remove battery cover from the SL-C3200

d. Leaving the Battery Cover OFF, return the battery cover lock to the LOCKED position.

e. Locate reset switch on the left side edge of battery compartment.

f.  Open the unit so that the keyboard is accessible with one hand and the base of the unit is accessible with the other.

g. Hold down D+B on the keyboard and whilst these keys are held depress the reset button using the stylus.

h. Release the D+B keys and within a few seconds the unit should start to boot into Emergency Linux.

i. Reconnect AC power.

j. Return battery cover lock to unlocked position, Replace battery cover, Lock cover.

k. Log into Emergency Linux using the username root (no password).

l. Insert the SD or CF storage card.

m. Change directory:
# cd /mnt/card for SD card or
# cd /mnt/cf for a CF card.

n. Load kernel module:
# insmod zbsdmod.o

o. cp bsd.rd to the zboot proc entry:
# cp bsd.rd /proc/zboot

You should now be observing the OpenBSD kernel boot messages.

*
mathemajikian
I just upgraded my Z to -current (which is pre-OpenBSD-4.1) and have had to perform the horrifying act of pkg_delete -q /var/db/pkg/* ohmy.gif You've been warned!
mathemajikian
4.1-beta is now available for testing. smile.gif
jpmatrix
QUOTE(mathemajikian @ Feb 13 2007, 02:09 PM)
4.1-beta is now available for testing.  smile.gif
*


where do you find it?
i see only 4.0 under lastest snapshot here
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus/
mathemajikian
QUOTE(jpmatrix @ Feb 13 2007, 05:16 PM)
QUOTE(mathemajikian @ Feb 13 2007, 02:09 PM)
4.1-beta is now available for testing.  smile.gif
*


where do you find it?
i see only 4.0 under lastest snapshot here
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus/
*



You have to update your source via cvs. smile.gif
jpmatrix
QUOTE(mathemajikian @ Feb 14 2007, 12:00 AM)
QUOTE(jpmatrix @ Feb 13 2007, 05:16 PM)
QUOTE(mathemajikian @ Feb 13 2007, 02:09 PM)
4.1-beta is now available for testing.  smile.gif
*


where do you find it?
i see only 4.0 under lastest snapshot here
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus/
*



You have to update your source via cvs. smile.gif
*




well it seems to be there :
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/zaurus

can someone explain us the update news?
mathemajikian
$ dmesg
OpenBSD 4.1-beta (ZAURUS) #5: Sat Feb 17 00:06:50 GMT 2007
zaurus.mersenne:/usr/src/sys/arch/zaurus/compile/ZAURUS
real mem = 67108864 (65536K) 64MB
avail mem = 53161984 (51916K)
using 844 buffers containing 3457024 bytes (3376K) of memory
mainbus0 (root)
cpu0 at mainbus0: PXA27x step C-5 (XScale core)
cpu0: DC enabled IC enabled WB enabled LABT branch prediction enabled
cpu0: 32KB(32b/l,32way) I-cache, 32KB(32b/l,32way) wr-back-lock D-cache
pxaip0 at mainbus0: CPU clock = 416.000 MHz
pxaintc0 at pxaip0 addr 0x40d00000: Interrupt Controller
pxagpio0 at pxaip0 addr 0x40e00000: GPIO Controller
pxadmac0 at pxaip0 addr 0x40000000 intr 25: DMA Controller
pxaost0 at pxaip0 addr 0x40a00000
com0 at pxaip0 addr 0x40100000 intr 22: pxa2x0, 32 byte fifo
com1 at pxaip0 addr 0x40200000 intr 21: pxa2x0, 32 byte fifo
com2 at pxaip0 addr 0x40700000 intr 20: pxa2x0, 32 byte fifo (SIR)
pxaudc0 at pxaip0: USB Device Controller
usbf0 at pxaudc0: USB revision 1.1
cdcef0 at usbf0: OpenBSD.org CDC Ethernet Emulation, rev 1.01/1.00
cdcef0: address 2a:cb:00:00:00:00
ohci0 at pxaip0, version 1.0
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: PXA27x OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
lcd0 at pxaip0
wsdisplay0 at lcd0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1 added (std, vt100 emulation)
zkbd0 at pxaip0
wskbd0 at zkbd0: console keyboard, using wsdisplay0
scoop0 at pxaip0: PCMCIA/GPIO controller
scoop1 at pxaip0: PCMCIA/GPIO controller
pxapcic0 at pxaip0: 2 slots
pcmcia0 at pxapcic0
pcmcia1 at pxapcic0
zssp0 at pxaip0
apm0 at pxaip0
zts0 at pxaip0
wsmouse0 at zts0 mux 0
zaudio0 at pxaip0: I2C, I2S, WM8750 Audio
audio0 at zaudio0
zrc0 at pxaip0: CE-RH2 remote control
wskbd1 at zrc0 mux 1
wskbd1: connecting to wsdisplay0
flash0 at pxaip0: Samsung K9F1G08U0A 128Mx8 3.3V
wdc0 at pcmcia0 function 0 "HITACHI, microdrive" port 0x0/16: irq 138
wd0 at wdc0 channel 0 drive 0: <HMS360606D5CF00>
wd0: 32-sector PIO, LBA, 5859MB, 12000556 sectors
wd0(wdc0:0:0): using BIOS timings
wi0 at pcmcia1 function 0 "BUFFALO, WLI2-CF-S11, " port 0x0/64, irq 137
wi0: PRISM2.5 ISL3873 (0x800c), Firmware 1.1.0 (primary), 1.3.5 (station), address
boot device: wd0.
rootdev=0x1000 rrootdev=0x1000 rawdev=0x1002
mathemajikian
QUOTE
can someone explain us the update news?


From http://www.openbsd.org/41.html

QUOTE
This is a partial list of new features and systems included in OpenBSD 4.1. For a comprehensive list, see the changelog leading to 4.1.

    * New/extended platforms:
          o OpenBSD/landisk.
            Various SH4-based appliances, made by IO-Data and resold by Plextor.
          o OpenBSD/sparc64.
            UltraSPARC III based machines are now supported even better, and run at full speed now!

    * Removed platforms:
          o OpenBSD/cats.
            Because the machines are very hard to find, and the developers hate them.

    * Improved hardware support, including:
          o New USB client controller support:
                + Support for the USB client functionality in the pxaudc(4) driver on the Zaurus.
                + New usbf(4) midlayer for USB Client controllers.
                + New cdcef(4) driver for providing a CDCE function on USB client controllers.
          o New cas(4) driver for Sun Cassini 10/100/Gigabit Ethernet devices.
          o New uow(4) driver for Maxim/Dallas DS2490 USB 1-Wire devices.
          o New owsbm(4) driver for 1-Wire smart battery monitor devices.
          o New zyd(4) driver for ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network devices.
          o New moscom(4) driver for MosChip Semiconductor MCS7703 based USB serial adapters.
          o New glxsb(4) driver for hardware random numbers and AES acceleration on the AMD Geode LX processor.
          o New vic(4) driver for VMware VMXnet Virtual Interface Controllers.
          o New malo(4) driver for Marvell Libertas IEEE 802.11b/g wireless network devices.
          o New pwdog(4) driver for Quancom PWDOG1 watchdog timer devices.
          o New uberry(4) driver for Research In Motion Blackberry devices.
          o New mbg(4) driver for Meinberg Funkuhren radio clocks.
          o New mesh(4) driver for the on-board SCSI controller of old world Apple Power Macintosh systems.
          o New mc(4) driver for the on-board Ethernet of many old world Apple Power Macintosh systems
          o Improved msk(4) driver now supports many more Marvell Yukon-2 variants including dual port cards and fiber cards.
          o The gem(4) driver now supports fiber cards.
          o The OpenBSD/amd64 platform now has more accurate and robust time keeping.
          o The OpenBSD/i386 boot(8) program now works properly on Intel-based Macs.
          o The pciide(4) driver has had support added for newer chipsets, including:
                + AMD CS5536 IDE;
                + Intel i31244;
                + NVIDIA MCP67 PATA, MCP67 SATA.
          o The com(4) driver now supports ST16C654 devices.
          o The adt(4) driver supports some newer chipsets, such as the ADT7475.
          o The OpenBSD/macppc platform now automatically turns the machine back on following an unexpected loss of power.
          o boot.mac an XCOFF formated boot loader for OpenBSD/macppc capable of booting on many old world macs.

    * New tools:
          o BSD-licensed pkg-config(1), a complete rewrite of the GNU tool of the same name, significantly smaller and more maintainable.
          o hoststated(8), a layer 3 and layer 7 server load balancing daemon with host monitoring capacities.
          o new BSD-licensed ripd(8).
          o bgplg(8), a CGI looking glass for OpenBGPD, is now available for use with the system httpd.
          o bgplgsh(8), a looking glass shell for OpenBGPD, is now avalilable for use as a restricted read-only command line interface.

    * New functionality:
          o syslogd(8) can now pipe logs directly to other programs, making real-time log analysis easier.
          o The IP_RECVTTL ip(4) socket option allows programs to receive the incoming ttl on raw and udp sockets.
          o The IP_MINTTL ip(4) socket option allows programs to ask the kernel to discard any packets with a ttl smaller than the given one, for implementing the IP TTL security hack aka the Generalized TTL Security Mechanism specified in RFC 3682.
          o Multiple, independent routing tables, with pf(4) acting as selector. route(8) can be told which table to work with now, and routing daemons have been modified to cope as well.
          o The pflog(4) interface is now clonable. pf(4) can log to multiple pflog interfaces now, each rule can specify which pflog interface to log to. pflogd(8) and spamlogd(8) can now be told which pflog interface to work with.
          o The pfsync(4) interface is now clonable as well, thus only there when actually needed.
          o pfctl(8) can now expire table entries.
          o Allow pf(4) rules inside anchors to have their counters reset, and make counter read & reset an atomic operation.
          o sensorsd(8) dampens status changes now, thus not alerting for a single wrong sensor read, since many sensors lie once in a while.
          o spamd(8) and spamlogd(8) now support synchronisation of the greylist database across multiple hosts. The greytrapping mechanism now allows for whole domain traps, and noticing out of order MX use.
          o spamd(8) database format has changed from DB_BTREE to DB_HASH for much better performance on large installations with big databases.
          o The bridge(4) driver and the brconfig(8) tool now support the Rapid Spanning Tree Protocol (RSTP). The new RSTP mode is now used by default when enabled with the stp option.
          o cd(4) now supports reading from region protected DVDs.
          o Detect MS-DOS filesystems and spoof disklabel partitions for them even when there is no MBR, e.g. on some newer iPods.

    * Assorted improvements and code cleanup:
          o The fsck_ffs(8) command has been improved to be more robust to various forms of inode and superblock corruption.
          o The top(1) command got some new ways of filtering the display.
          o pthreads(3) file descriptor handling has been improved to eliminate several race and deadlock conditions and improve performance.
          o The MS-DOS filesystem has had a potential corruption issue fixed, and is more reliable when given a corrupted filesystem to mount.
          o The MS-DOS filesystem and the fdisk(8) command have been enhanced to work on devices with 2048 byte sectors, e.g. newer iPods.
          o The OpenRCS tools are smarter at handling files, especially when dealing with binary files. GNU RCS compatibility has also been improved.
          o The mg(1) editor now displays column numbers in the status bar. It has also received several improvements which make it more reliable: line numbers, file insertions, and search wrapping all now work as expected.
          o The systat(1) command has a cleaner look, and a display was added for hardware sensors.
          o The OpenBSD/alpha platform now uses gcc3.
          o Improved support for usb attached cd drives and ever more odd umass(4) devices.
          o Don't treat NetBSD or FreeBSD MBR partitions as substitutes for an OpenBSD partition. i.e. don't try to boot from them or use them to store OpenBSD disklabels.

    * Install/Upgrade process changes
          o More reliable detection of disk and cd devices.
          o More reliable installation from MSDOS FAT partitions.
          o New sanity check in case sets for the wrong architecture are selected.
          o No need to specify the filesystem types of source partitions during disk or cd installs.
          o No need to select a source partition during disk or cd installs when there is only one to choose from.

    * OpenBGPD 4.1:
          o Fixes for sessions with tcp md5sig and ipsec. Now sessions can be migrated from and to any form of ipsec and tcpmd5 with just a simple bgpctl reload, and the session migrates the next time it gets established.
          o Include file support in the config parser.
          o Can now use the new IP_MINTTL socket option to implement the ttl security mechanism.

    * OpenOSPFD 4.1:
          o Reload support added. It is no longer needed to restart ospfd after a configuration change.
          o Multiple networks per interface are now supported.
          o It is now possible to specify the route metric and type for each redistribution rule.

    * OpenNTPD 4.1:
          o Greatly improved support for timedelta sensors.
          o ntpd now uses a strictly monotonically increasing time (uptime, basically) for its internal timers, so setting the system clock doesn't influence query rates, trust levels, etc. any more.


I've also noticed better audio/video performance on my SL-C3200 using this release.
mathemajikian
Anyone upgrading their Z to 4.1 should read the upgrading instructions first! I learned the hard way earlier this month when building -current. smile.gif Here's the link to the instructions and a quote:

http://www.openbsd.org/faq/upgrade41.html

QUOTE
Special note for ARM users (armish, zaurus): Changes in the ABI requires a slightly different upgrade process if not using standard install kernel. Do not reboot after installing the kernel and before installing the new userland.

Reboot on the new kernel: (NOT for ARM users) This might be a tempting step to skip, but it should be done now, as usually, the new kernel will run old userland apps (such as the soon to be important reboot!), but often a new userland will NOT work on the old kernel.

Note: ARM users (armish/zaurus) SHOULD skip this step for this upgrade cycle.
jpmatrix
i'm trying a cvs update.
i'd like to say that the first method i tried didn't work :

QUOTE
Use CVS to download the latest source and ports collection
# cd /usr/src
# cvs -d anoncvs@anoncvs.ca.openbsd.org:/cvs up -Pd


give me an error message (something not found).

it seems you first need to do a checkout :

To checkout a -current CVS src tree, you can use the following:
# cd /usr
# export CVSROOT=anoncvs@anoncvs.example.org:/cvs
# cvs -d$CVSROOT checkout -P src
mathemajikian
QUOTE(jpmatrix @ May 13 2007, 08:43 AM)
It seems you first need to do a checkout :
To checkout a -current CVS src tree, you can use the following:
    # cd /usr
    # export CVSROOT=anoncvs@anoncvs.example.org:/cvs
    # cvs -d$CVSROOT checkout -P src

I've corrected the instructions to accommodate those who haven't previously checked out the ports tree or system sources. smile.gif
jpmatrix
hmm
i've just compiled and install a new kernel, following the instructions here and
uname -a gives me :

GENERIC#0

is it normal ???
mathemajikian
QUOTE(jpmatrix @ Jun 22 2007, 06:20 PM)
hmm
i've just compiled and install a new kernel, following the instructions here and
uname -a gives me :

GENERIC#0

is it normal ???
*


Yes. smile.gif
jpmatrix
QUOTE(mathemajikian @ Jun 26 2007, 08:58 PM)
QUOTE(jpmatrix @ Jun 22 2007, 06:20 PM)
hmm
i've just compiled and install a new kernel, following the instructions here and
uname -a gives me :

GENERIC#0

is it normal ???
*


Yes. smile.gif
*



ok ! that seems a little strange indeed smile.gif
anyway i went into trouble following the system build process... it failed with some error messages like error code 1 ...
next time i think i'll just try the upgrade via snapshot smile.gif
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.