From russ at quist.ca Tue Jan 1 08:07:49 2008 From: russ at quist.ca (Russell Sutherland) Date: Mon, 31 Dec 2007 14:07:49 -0700 Subject: [flashboot] Kernel Config for Neoware e100 with CV860A motherboard Message-ID: <52e934090712311307l2c5cdf43mb83307b907ba0325@mail.gmail.com> Greetings to all. And a happy new year to one and all. I've been using flashboot on a number of platforms. Recently I installed in on a number of Neoware e100 style thin clients. These machines are interesting in the sense that they are diskless and run without a CPU fan (albeit a bit warm) and best of all are readily available on ebay and the like very cheap. They have one PCI expansion slot. I looked inside and found a CV860A mother board, which seems to be a Lex board from Taiwan. I have attached the kernel config file as well as the output from dmesg. My particular machine has one dual 10/100 intel board installed, hence the prescence of the fxp0 and fxp1 interfaces. Cheers! -- Russell Sutherland russ AT madhaus . cns . utoronto . ca +1.416.978.0470 [ voice ] +1.416.978.6620 [ fax ] -------------- next part -------------- A non-text attachment was scrubbed... Name: CV860A Type: application/octet-stream Size: 4868 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/flashboot/attachments/20071231/909b4e42/attachment.obj -------------- next part -------------- A non-text attachment was scrubbed... Name: dmesg.out Type: application/octet-stream Size: 3345 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/flashboot/attachments/20071231/909b4e42/attachment-0001.obj From massimo at cedoc.mo.it Wed Jan 2 21:13:02 2008 From: massimo at cedoc.mo.it (Massimo Lusetti) Date: Wed, 2 Jan 2008 11:13:02 +0100 Subject: [flashboot] LE565 and pcibios Message-ID: <20080102111302.7198b33e.massimo@cedoc.mo.it> Does anyone have been playing with this boards recently? It's newer then LE564 and features C7 fanless with 4 re(4) gigabit cards. For using that board with openbsd (honestly i try only up to 4.1) i've to disable pcibios, comment out the kernel config line, otherwise as soon as i configure more then one ethernet i got flooded by watchdog timeouts errors. Then i noticed that almost 4 months ago re(4) was added to the LE564 kernel and since that board doens't have i guess if this is of interest for the LE565 board. Thanks you and happy new year! -- Massimo A fool and your money are soon partners. From jbg at masterplan.org Sat Jan 5 19:40:30 2008 From: jbg at masterplan.org (Jason George) Date: Sat, 5 Jan 2008 01:40:30 -0700 (MST) Subject: [flashboot] Problems building with -CURRENT Message-ID: <20080105011333.F15142@ingenuity.resourcechain.com> I am having issues getting kernels built with the flashboot scripts to work with -CURRENT source. Once the kernel boots, I get "panic: init died (signal 0, exit 4)", which I have an unproven suspicion may have to do with MAKEDEV or possibly with the config flag day that occurred over a month ago (also pasted below is a snipped from build-largekernel.sh output). To try to eliminate glitches in my customized scripts, I grabbed the Dec 7 cvs snapshot of flashboot and ran it against a Nov 20 -CURRENT source tree on a separate machine (that whole system is running a Nov 20 snapshot). That image boots fine on my embedded machine. I have problems with the Dec 7 and Jan 3 flashboot cvs snaps (the first and last available on the website at the time) against a Jan 3 OpenBSD -CURRENT tree Is there anyone else who can corroborate my observations by building against a -CURRENT source tree? Any other thoughts or comments? Thanks... --Jason Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.2-current (GENERIC-RD.LARGE) #0: Sat Jan 5 00:53:48 MST 2008 jbg at embedded:/v00/embedded/projects/TS5400/fb-1207/flashboot/obj/GENERIC-RD.LARGE cpu0: AMD Am486DX4 W/B or Am5x86 W/B 150 ("AuthenticAMD" 486-class) cpu0: FPU real mem = 66674688 (63MB) avail mem = 32989184 (31MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 10/25/04, BIOS32 rev. 0 @ 0xe7200 pcibios0 at bios0: rev 2.1 @ 0xe7270/0x1000 pcibios0: PCI BIOS has 4 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 9 10 11 pcibios0: no compatible PCI ICU found pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) elansc0 at pci0 dev 0 function 0 "AMD ElanSC520 PCI" rev 0x00: product 0 stepping 1.1, CPU clock 100MHz, reset 0 gpio0 at elansc0: 32 pins dc0 at pci0 dev 13 function 0 "Davicom DM9102" rev 0x40: irq 11, address 00:d0:69:12:44:09 amphy0 at dc0 phy 1: DM9102 10/100 PHY, rev. 1 dc1 at pci0 dev 14 function 0 "Davicom DM9102" rev 0x40: irq 10, address 00:d0:69:b2:44:09 amphy1 at dc1 phy 1: DM9102 10/100 PHY, rev. 1 isa0 at mainbus0 ast0 at isa0 port 0x1a0/32 irq 5 pccom3 at ast0 slave 0: ns8250, no fifo pccom4 at ast0 slave 1: ns8250, no fifo pccom5 at ast0 slave 2: ns8250, no fifo pccom6 at ast0 slave 3: ns8250, no fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc_cmd: send error pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard kbc: aux echo error 1 kbc: cmd word write error wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: wd0: 1-sector PIO, LBA, 30MB, 62720 sectors wd0(wdc0:0:0): using BIOS timings pcppi0 at isa0 port 0x61 midi0 at pcppi0: spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pccom2: irq 5 already in use pcic: does not support memory and I/O cards, ignored (ident=1) pcic: does not support memory and I/O cards, ignored (ident=41) pcic: does not support memory and I/O cards, ignored (ident=1) pcic: does not support memory and I/O cards, ignored (ident=41) pcic: does not support memory and I/O cards, ignored (ident=1) pcic: does not support memory and I/O cards, ignored (ident=41) pcic: does not support memory and I/O cards, ignored (ident=1) pcic: does not support memory and I/O cards, ignored (ident=41) pcic: does not support memory and I/O cards, ignored (ident=1) pcic: does not support memory and I/O cards, ignored (ident=41) pcic: does not support memory and I/O cards, ignored (ident=1) pcic: does not support memory and I/O cards, ignored (ident=41) biomask f3c5 netmask ffc5 ttymask ffe7 rd0: fixed, 40960 blocks softraid0 at root root on rd0a swap on rd0b dump on rd0b panic: init died (signal 0, exit 4) Stopped at Debugger+0x4: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb> trace Debugger(d4ea9ecc,0,d4ea9f00,d03cdcba,d0885e80) at Debugger+0x4 panic(d0885e80,0,4,d03d35f0,d41f0150) at panic+0x9d exit1(d41eb000,400,1,0) at exit1+0x32 sys_exit(d41eb000,d4ea9f58,d4ea9f50,d059de09) at sys_exit+0x22 syscall() at syscall+0x2d4 --- syscall (number 1) --- 0xe3b9923: ddb> ps PID PPID PGRP UID S FLAGS WAIT COMMAND 11 0 0 0 3 0x100200 bored crypto 10 0 0 0 3 0x100200 aiodoned aiodoned 9 0 0 0 3 0x100200 syncer update 8 0 0 0 3 0x100200 cleaner cleaner 7 0 0 0 3 0x100200 reaper reaper 6 0 0 0 3 0x100200 pgdaemon pagedaemon 5 0 0 0 3 0x100200 pftm pfpurge 4 0 0 0 3 0x100200 bored syswq 3 0 0 0 3 0x100200 idle0 2 0 0 0 3 0x100200 kmalloc kmthread * 1 0 0 0 7 0x4000 init 0 -1 0 0 3 0x80200 scheduler swapper ddb> sudo env TOPDIR=/v00/embedded/projects/TS5400/fb-1207/flashboot CURDIR=/v00/embedded/projects/TS5400/fb-1207/flashboot OBJDIR=/v00/embedded/projects/TS5400/fb-1207/flashboot/obj SRCDIR=/v00/embedded/projects/TS5400/OpenBSD/src TARGDIR=/mnt UTILS=/v00/embedded/projects/TS5400/fb-1207/flashboot/tools DESTDIR=/v00/embedded/projects/TS5400/fb-1207/flashboot/flash-dist TTYSPEED=9600 sh /v00/embedded/projects/TS5400/fb-1207/flashboot/tools/runlist.sh /v00/embedded/projects/TS5400/fb-1207/flashboot/list.temp SCRIPT ${DESTDIR}/dev/MAKEDEV dev/MAKEDEV SPECIAL chmod 700 dev/MAKEDEV SPECIAL cd dev; ./MAKEDEV ramdisk pty systrace tty00 tty01 pci wdt0 sh: [1]: mknod: tty00: File exists sh: [1]: mknod: cua00: File exists sh: [1]: mknod: tty01: File exists sh: [1]: mknod: cua01: File exists sh: [1]: mknod: wd0a: File exists sh: [1]: mknod: rwd0a: File exists sh: [1]: mknod: wd0b: File exists sh: [1]: mknod: rwd0b: File exists sh: [1]: mknod: wd0c: File exists sh: [1]: mknod: rwd0c: File exists sh: [1]: mknod: wd0d: File exists sh: [1]: mknod: rwd0d: File exists sh: [1]: mknod: wd0e: File exists sh: [1]: mknod: rwd0e: File exists sh: [1]: mknod: wd0f: File exists sh: [1]: mknod: rwd0f: File exists sh: [1]: mknod: wd0g: File exists sh: [1]: mknod: rwd0g: File exists sh: [1]: mknod: wd0h: File exists sh: [1]: mknod: rwd0h: File exists sh: [1]: mknod: wd0i: File exists sh: [1]: mknod: rwd0i: File exists sh: [1]: mknod: wd0j: File exists sh: [1]: mknod: rwd0j: File exists sh: [1]: mknod: wd0k: File exists sh: [1]: mknod: rwd0k: File exists sh: [1]: mknod: wd0l: File exists sh: [1]: mknod: rwd0l: File exists sh: [1]: mknod: wd0m: File exists sh: [1]: mknod: rwd0m: File exists sh: [1]: mknod: wd0n: File exists sh: [1]: mknod: rwd0n: File exists sh: [1]: mknod: wd0o: File exists sh: [1]: mknod: rwd0o: File exists sh: [1]: mknod: wd0p: File exists sh: [1]: mknod: rwd0p: File exists SPECIAL cd dev; ./MAKEDEV ttyU0 ttyU1 SPECIAL cd dev; ./MAKEDEV tun0 tun1 tun2 tun3 tun4 tun5 tun6 tun7 SPECIAL cd dev; ./MAKEDEV bpf0 bpf1 bpf2 bpf3 bpf4 bpf5 bpf6 bpf7 SPECIAL cd dev; ./MAKEDEV pf crypto fd wsmux wscons apm local gpio sh: [1]: mknod: wsmouse: File exists sh: [1]: mknod: wskbd: File exists From jbg at masterplan.org Sat Jan 5 19:59:55 2008 From: jbg at masterplan.org (Jason George) Date: Sat, 5 Jan 2008 01:59:55 -0700 (MST) Subject: [flashboot] Problems building with -CURRENT In-Reply-To: <20080105011333.F15142@ingenuity.resourcechain.com> References: <20080105011333.F15142@ingenuity.resourcechain.com> Message-ID: <20080105015740.U15296@ingenuity.resourcechain.com> I hate replying to my own emails... I think the MAKEDEV issue is a red herring in regards to the init panic. It's late and I just recognized that the build with the Dec 7 flashboot on Nov 20 -CURRENT has the same MAKEDEV mknod noise. --J On Sat, 5 Jan 2008, Jason George wrote: > > I am having issues getting kernels built with the flashboot scripts to > work with -CURRENT source. > > Once the kernel boots, I get "panic: init died (signal 0, exit 4)", which > I have an unproven suspicion may have to do with MAKEDEV or possibly with > the config flag day that occurred over a month ago (also pasted below is > a snipped from build-largekernel.sh output). > > To try to eliminate glitches in my customized scripts, I grabbed the Dec 7 > cvs snapshot of flashboot and ran it against a Nov 20 -CURRENT source tree > on a separate machine (that whole system is running a Nov 20 snapshot). > That image boots fine on my embedded machine. > > I have problems with the Dec 7 and Jan 3 flashboot cvs snaps (the first > and last available on the website at the time) against a Jan 3 OpenBSD > -CURRENT tree > > Is there anyone else who can corroborate my observations by building > against a -CURRENT source tree? Any other thoughts or comments? > > Thanks... > > --Jason > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2008 OpenBSD. All rights reserved. > http://www.OpenBSD.org > > OpenBSD 4.2-current (GENERIC-RD.LARGE) #0: Sat Jan 5 00:53:48 MST 2008 > > jbg at embedded:/v00/embedded/projects/TS5400/fb-1207/flashboot/obj/GENERIC-RD.LARGE > cpu0: AMD Am486DX4 W/B or Am5x86 W/B 150 ("AuthenticAMD" 486-class) > cpu0: FPU > real mem = 66674688 (63MB) > avail mem = 32989184 (31MB) > mainbus0 at root > bios0 at mainbus0: AT/286+ BIOS, date 10/25/04, BIOS32 rev. 0 @ 0xe7200 > pcibios0 at bios0: rev 2.1 @ 0xe7270/0x1000 > pcibios0: PCI BIOS has 4 Interrupt Routing table entries > pcibios0: PCI Exclusive IRQs: 9 10 11 > pcibios0: no compatible PCI ICU found > pcibios0: Warning, unable to fix up PCI interrupt routing > pcibios0: PCI bus #0 is the last bus > cpu0 at mainbus0 > pci0 at mainbus0 bus 0: configuration mode 1 (bios) > elansc0 at pci0 dev 0 function 0 "AMD ElanSC520 PCI" rev 0x00: product 0 > stepping 1.1, CPU clock 100MHz, reset 0 > gpio0 at elansc0: 32 pins > dc0 at pci0 dev 13 function 0 "Davicom DM9102" rev 0x40: irq 11, address > 00:d0:69:12:44:09 > amphy0 at dc0 phy 1: DM9102 10/100 PHY, rev. 1 > dc1 at pci0 dev 14 function 0 "Davicom DM9102" rev 0x40: irq 10, address > 00:d0:69:b2:44:09 > amphy1 at dc1 phy 1: DM9102 10/100 PHY, rev. 1 > isa0 at mainbus0 > ast0 at isa0 port 0x1a0/32 irq 5 > pccom3 at ast0 slave 0: ns8250, no fifo > pccom4 at ast0 slave 1: ns8250, no fifo > pccom5 at ast0 slave 2: ns8250, no fifo > pccom6 at ast0 slave 3: ns8250, no fifo > pckbc0 at isa0 port 0x60/5 > pckbd0 at pckbc0 (kbd slot) > pckbc_cmd: send error > pckbc0: using irq 1 for kbd slot > wskbd0 at pckbd0: console keyboard > kbc: aux echo error 1 > kbc: cmd word write error > wdc0 at isa0 port 0x1f0/8 irq 14 > wd0 at wdc0 channel 0 drive 0: > wd0: 1-sector PIO, LBA, 30MB, 62720 sectors > wd0(wdc0:0:0): using BIOS timings > pcppi0 at isa0 port 0x61 > midi0 at pcppi0: > spkr0 at pcppi0 > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 > pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > pccom0: console > pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo > pccom2: irq 5 already in use > pcic: does not support memory and I/O cards, ignored (ident=1) > pcic: does not support memory and I/O cards, ignored (ident=41) > pcic: does not support memory and I/O cards, ignored (ident=1) > pcic: does not support memory and I/O cards, ignored (ident=41) > pcic: does not support memory and I/O cards, ignored (ident=1) > pcic: does not support memory and I/O cards, ignored (ident=41) > pcic: does not support memory and I/O cards, ignored (ident=1) > pcic: does not support memory and I/O cards, ignored (ident=41) > pcic: does not support memory and I/O cards, ignored (ident=1) > pcic: does not support memory and I/O cards, ignored (ident=41) > pcic: does not support memory and I/O cards, ignored (ident=1) > pcic: does not support memory and I/O cards, ignored (ident=41) > biomask f3c5 netmask ffc5 ttymask ffe7 > rd0: fixed, 40960 blocks > softraid0 at root > root on rd0a swap on rd0b dump on rd0b > panic: init died (signal 0, exit 4) > Stopped at Debugger+0x4: leave > RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS > PANIC! > DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! > ddb> trace > Debugger(d4ea9ecc,0,d4ea9f00,d03cdcba,d0885e80) at Debugger+0x4 > panic(d0885e80,0,4,d03d35f0,d41f0150) at panic+0x9d > exit1(d41eb000,400,1,0) at exit1+0x32 > sys_exit(d41eb000,d4ea9f58,d4ea9f50,d059de09) at sys_exit+0x22 > syscall() at syscall+0x2d4 > --- syscall (number 1) --- > 0xe3b9923: > ddb> ps > PID PPID PGRP UID S FLAGS WAIT COMMAND > 11 0 0 0 3 0x100200 bored crypto > 10 0 0 0 3 0x100200 aiodoned aiodoned > 9 0 0 0 3 0x100200 syncer update > 8 0 0 0 3 0x100200 cleaner cleaner > 7 0 0 0 3 0x100200 reaper reaper > 6 0 0 0 3 0x100200 pgdaemon pagedaemon > 5 0 0 0 3 0x100200 pftm pfpurge > 4 0 0 0 3 0x100200 bored syswq > 3 0 0 0 3 0x100200 idle0 > 2 0 0 0 3 0x100200 kmalloc kmthread > * 1 0 0 0 7 0x4000 init > 0 -1 0 0 3 0x80200 scheduler swapper > ddb> > > > > sudo env TOPDIR=/v00/embedded/projects/TS5400/fb-1207/flashboot > CURDIR=/v00/embedded/projects/TS5400/fb-1207/flashboot > OBJDIR=/v00/embedded/projects/TS5400/fb-1207/flashboot/obj > SRCDIR=/v00/embedded/projects/TS5400/OpenBSD/src TARGDIR=/mnt > UTILS=/v00/embedded/projects/TS5400/fb-1207/flashboot/tools > DESTDIR=/v00/embedded/projects/TS5400/fb-1207/flashboot/flash-dist > TTYSPEED=9600 sh > /v00/embedded/projects/TS5400/fb-1207/flashboot/tools/runlist.sh > /v00/embedded/projects/TS5400/fb-1207/flashboot/list.temp > SCRIPT ${DESTDIR}/dev/MAKEDEV dev/MAKEDEV > SPECIAL chmod 700 dev/MAKEDEV > SPECIAL cd dev; ./MAKEDEV ramdisk pty systrace tty00 tty01 pci wdt0 > sh: [1]: mknod: tty00: File exists > sh: [1]: mknod: cua00: File exists > sh: [1]: mknod: tty01: File exists > sh: [1]: mknod: cua01: File exists > sh: [1]: mknod: wd0a: File exists > sh: [1]: mknod: rwd0a: File exists > sh: [1]: mknod: wd0b: File exists > sh: [1]: mknod: rwd0b: File exists > sh: [1]: mknod: wd0c: File exists > sh: [1]: mknod: rwd0c: File exists > sh: [1]: mknod: wd0d: File exists > sh: [1]: mknod: rwd0d: File exists > sh: [1]: mknod: wd0e: File exists > sh: [1]: mknod: rwd0e: File exists > sh: [1]: mknod: wd0f: File exists > sh: [1]: mknod: rwd0f: File exists > sh: [1]: mknod: wd0g: File exists > sh: [1]: mknod: rwd0g: File exists > sh: [1]: mknod: wd0h: File exists > sh: [1]: mknod: rwd0h: File exists > sh: [1]: mknod: wd0i: File exists > sh: [1]: mknod: rwd0i: File exists > sh: [1]: mknod: wd0j: File exists > sh: [1]: mknod: rwd0j: File exists > sh: [1]: mknod: wd0k: File exists > sh: [1]: mknod: rwd0k: File exists > sh: [1]: mknod: wd0l: File exists > sh: [1]: mknod: rwd0l: File exists > sh: [1]: mknod: wd0m: File exists > sh: [1]: mknod: rwd0m: File exists > sh: [1]: mknod: wd0n: File exists > sh: [1]: mknod: rwd0n: File exists > sh: [1]: mknod: wd0o: File exists > sh: [1]: mknod: rwd0o: File exists > sh: [1]: mknod: wd0p: File exists > sh: [1]: mknod: rwd0p: File exists > SPECIAL cd dev; ./MAKEDEV ttyU0 ttyU1 > SPECIAL cd dev; ./MAKEDEV tun0 tun1 tun2 tun3 tun4 tun5 tun6 tun7 > SPECIAL cd dev; ./MAKEDEV bpf0 bpf1 bpf2 bpf3 bpf4 bpf5 bpf6 bpf7 > SPECIAL cd dev; ./MAKEDEV pf crypto fd wsmux wscons apm local gpio > sh: [1]: mknod: wsmouse: File exists > sh: [1]: mknod: wskbd: File exists > > _______________________________________________ > flashboot mailing list > flashboot at mindrot.org > https://lists.mindrot.org/mailman/listinfo/flashboot > From anontrol at gmail.com Fri Jan 11 01:10:13 2008 From: anontrol at gmail.com (anon trol) Date: Thu, 10 Jan 2008 23:10:13 +0900 Subject: [flashboot] flashboot + OpenBSD + Routerboard | Ubiquiti powerstation hardware Message-ID: Is *anyone* is attempting on getting flashboot working with routerboard (rb133/rb532/rb333 in particular) or Ubiquiti powerstation (PS2 in particular)? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20080110/e33dfa5f/attachment.html From ake.xx.nordin at ericsson.com Fri Jan 11 04:25:59 2008 From: ake.xx.nordin at ericsson.com (=?iso-8859-1?Q?=C5ke_Nordin_XX?=) Date: Thu, 10 Jan 2008 18:25:59 +0100 Subject: [flashboot] flashboot + OpenBSD + Routerboard | Ubiquitipowerstation hardware In-Reply-To: References: Message-ID: <9171BA436A79BF46953672FB5A11DA5E01B39B76@esealmw104.eemea.ericsson.se> Anon Trol thusly scribed: > Is *anyone* is attempting on getting flashboot working with > routerboard (rb133/rb532/rb333 in particular) or Ubiquiti > powerstation (PS2 in particular)? I would be very surprised if anyone stepped forth with an affirmative answer. I do however have to admit to having had greater surprises than that from OpenBSD (which forms the core of flashboot). The systems you mention seems to be MIPS 4K, that is 32-bit systems, if I got it right. Support for 4K-like systems in OpenBSD ended by OpenBSD 2.3. The sgi support is 64-bit and I would assume it is portable (in theory) to general mips 5K stuff but out of the question as a base for 4K stuff. -- . /Ake Nordin ake.xx.nordin_ericsson.com [{+46|0}8]4045306 KI/EAB/GTO/NS Unix, Network, Lab support ECN: 850 45306 KI3203355, Ericsson, 164 80 Kista, Sweden From russ at quist.ca Fri Jan 18 01:58:11 2008 From: russ at quist.ca (Russell Sutherland) Date: Thu, 17 Jan 2008 09:58:11 -0500 Subject: [flashboot] Dealing with OpenBSD patches Message-ID: <52e934090801170658t26a3549btd0cac1551375fa86@mail.gmail.com> When a new patch is released, is it necessary to do a "build-release.sh" operation? Or is a patch followed by a "build-kernel.sh" sufficient? -- Russell Sutherland russ AT madhaus . cns . utoronto . ca +1.416.978.0470 [ voice ] +1.416.978.6620 [ fax ] From yg at ygunit.net Sat Jan 19 00:57:15 2008 From: yg at ygunit.net (Yannick Gravel) Date: Fri, 18 Jan 2008 08:57:15 -0500 Subject: [flashboot] Dealing with OpenBSD patches In-Reply-To: <52e934090801170658t26a3549btd0cac1551375fa86@mail.gmail.com> References: <52e934090801170658t26a3549btd0cac1551375fa86@mail.gmail.com> Message-ID: <4790B03B.3060408@ygunit.net> Russel, It depands... For OpenBSD 4.2, errata 004 and 005 are for the kernel, so build-kernel.sh is sufficient there but for the errata 001 and 002 that are in user-space, you need to do the build-release.sh before. So with that in mind, for the next errata, have a look at the patch, you'll figure out what need to be done. Cheers Y. Russell Sutherland wrote: > When a new patch is released, is it necessary to do a > "build-release.sh" operation? > Or is a patch followed by a "build-kernel.sh" sufficient? > > From rd at tilde.se Sat Jan 19 02:33:29 2008 From: rd at tilde.se (Rickard Dahlstrand) Date: Fri, 18 Jan 2008 16:33:29 +0100 Subject: [flashboot] Dealing with OpenBSD patches In-Reply-To: <4790B03B.3060408@ygunit.net> References: <52e934090801170658t26a3549btd0cac1551375fa86@mail.gmail.com> <4790B03B.3060408@ygunit.net> Message-ID: <4790C6C9.5010503@tilde.se> The rule is if the patch is affecting files in the sys/-dir only, a build-kernel.sh will do, if any thing else you will have to do a build-release.sh. However, flashboot only contains a subset of the OpenBSD distribution, so as Yannick said, read up on if you need to apply the patch before you put the effort into upgrading your system. Regards, Rickard. Yannick Gravel wrote: > Russel, > > It depands... > > For OpenBSD 4.2, errata 004 and 005 are for the kernel, so > build-kernel.sh is sufficient there but for the errata 001 and 002 that > are in user-space, you need to do the build-release.sh before. So with > that in mind, for the next errata, have a look at the patch, you'll > figure out what need to be done. > > Cheers > > Y. > > Russell Sutherland wrote: > >> When a new patch is released, is it necessary to do a >> "build-release.sh" operation? >> Or is a patch followed by a "build-kernel.sh" sufficient? >> >> >> > > _______________________________________________ > flashboot mailing list > flashboot at mindrot.org > https://lists.mindrot.org/mailman/listinfo/flashboot > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20080118/520ab993/attachment.html