OT: integrating git branch output into ksh PS1 shell prompt?
Git fans like to know what branch is current, and bash's implementation of PS1 allows for update each time it is displayed. All of my attempts of adding a call to a ksh function into PS1 appear to be evaluated at the time that PS1 is set, but not upon each new display of the shell prompt. Does anyone have suggestions on how to have ksh execute a function upon each display of PS1? Thanks!
Re: mounting CVS tree read-only?
On Friday, February 21, 2014 11:14 AM, Theo de Raadt dera...@cvs.openbsd.org wrote: After studying FAQ 5.3, I am contemplating mounting /usr/src and /usr/xenocara read-only through NFS so I can maintain a centralized tree for multiple platforms. Is this possible? Are all writes made to /usr/obj and /usr/xobj? That is the intent. From time to time, mistakes sneak in. If you find them, work with us to get them resolved. I think not enough people use this mechanism. Thank you for your prompt reply! In FAQ 5.3.4, config(8) is being used to populate the /usr/src/sys/arch/platform/compile/GENERIC directory. Am I correct in thinking this directory should be mounted read/write? Thanks, again!
Re: using ifstated(8) to monitor wireless connections?
On Monday, October 28, 2013 6:10 AM, Stefan Sperling s...@openbsd.org wrote: On Sun, Oct 27, 2013 at 10:43:05PM -0700, Fred Snurd wrote: $ sudo ifconfig ath0 nwid my-id wpakey my-password $ ifconfig ath0ath0: flags=8822BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST mtu 1500 lladdr a8:54:b2:23:da:80 priority: 4 groups: wlan media: IEEE802.11 autoselect status: no network ieee80211: nwid my-id wpakey not displayed wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip $ ...which still shows that the link has not changed as expected. The interface isn't marked UP in the flags= line. So try 'ifconfig ath0 up' here. dhclient does this automatically before requesting a lease. Thanks Stefan Reyk for replying. Further testing tonight showed that the original /etc/ifstated.conf file did indeed work. I had thought that the link would be re-established quickly, but this was not the case. In fact, re-establishing the link took ~3-4 minutes to complete (but this factors in the time the AP needed to get reinitialized too...). I added logger(1) messages to my ifstated.conf(5) observing that the link state bounces about before stabilizing. I don't know if this peculiarity is associated with the ath(4) driver, WIstron CM9 card, Alix hardware, or the cheap ActionTec AP used. If there is any interest, I can submit a report with more details. I simply would like to take more time determining if there is anything else I can observe. Thanks again for your timely replies.
using ifstated(8) to monitor wireless connections?
On Monday, October 28, 2013 12:38 AM, Fred Snurd fredsn...@yahoo.com wrote:
I found the following article on undeadly which uses ifstated(8) to
automatically acquire a DHCP lease upon link state
changes on an Ethernet interface:
http://undeadly.org/cgi?action=articlesid=20071012140725mode=expanded
... thought that it would be simple to modify this for wireless links. To
prove this to myself, I looked at the output of
ifconfig(8) on an Alix system as it was connecting to an access point. Before
doing any interface configuration:
$ ifconfig ath0
ath0: flags=8822BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST mtu 1500
lladdr a8:54:b2:23:da:80
priority: 4
groups: wlan
media: IEEE802.11 autoselect
status: no network
ieee80211: nwid
$
...where status indicates the link state. Upon connecting to the AP,
$ sudo ifconfig ath0 nwid my-id wpakey my-password
$ ifconfig ath0ath0: flags=8822BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST mtu 1500
lladdr a8:54:b2:23:da:80
priority: 4
groups: wlan
media: IEEE802.11 autoselect
status: no network
ieee80211: nwid my-id
wpakey not displayed wpaprotos wpa1,wpa2 wpaakms psk wpaciphers
tkip,ccmp wpagroupcipher tkip
$
...which still shows that the link has not changed as expected. Upon getting a
DHCP lease,
$ sudo dhclient ath0
DHCPREQUEST on ath0 to 255.255.255.255 on port 67
DHCPACK from 192.168.0.1 (..:..:..:..:..:..)
bound to 192.168.0.4 -- renewal in 43200 seconds.
$ ifconfig ath0
ath0: flags=8863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr a8:54:b2:23:da:80
priority: 4
groups: wlan egress
media: IEEE802.11 autoselect (DS11 mode 11b)
status: active
ieee80211: nwid homestead chan 1 bssid 00:26:b8:d4:1c:49 wpakey not
displayed wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher
tkip
inet6 fe80::aa54:b2ff:fe23:da80%ath0 prefixlen 64 scopeid 0x4
inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255
$
...which now shows that the link is active. After turning off the AP, the link
is seen to go down:
$ ifconfig ath0
ath0: flags=8863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr a8:54:b2:23:da:80
priority: 4
groups: wlan egress
media: IEEE802.11 autoselect (DS11 mode 11b)
status: no network
ieee80211: nwid homestead wpakey not displayed wpaprotos wpa1,wpa2
wpaakms psk wpaciphers
tkip,ccmp wpagroupcipher tkip
inet6 fe80::aa54:b2ff:fe23:da80%ath0 prefixlen 64 scopeid 0x4
$
Upon turning the AP back on, the link is seen again to become active:
$ ifconfig ath0
ath0: flags=8863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr a8:54:b2:23:da:80
priority: 4
groups: wlan egress
media: IEEE802.11 autoselect (DS11 mode 11b)
status: active
ieee80211: nwid homestead wpakey not displayed wpaprotos
wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip
inet6 fe80::aa54:b2ff:fe23:da80%ath0 prefixlen 64 scopeid 0x4
$
...so I assumed that ifstated.conf file shown in the article doesn't require
much modification. Below is the minimal changes made:
$ cat /etc/ifstated.conf
wireless_up = 'ath0.link.up'
wireless_down = '!ath0.link.up'
state auto {
if $wireless_up
set-state main
}
state main {
init {
run 'ifconfig ath0 nwid my-id wpakey my-password'
run 'dhclient ath0'
}
if $wireless_down {
# run 'ifconfig ath0 delete'
set-state auto
}
}
init-state auto
$
ifstated has been enabled in /etc/rc.conf.local, the system has been rebooted:
$ grep ifstated /etc/rc.conf.local
ifstated_flags=''
$
No /etc/hostname.ath0 file has been created. ath0 comes up as expected at
system boot, but cycling the AP
doesn't result in the network connection to be re-established.
Can someone point out what I am missing for I'm not seeing it. Thanks for any
clarification shared.
Re: Mac mini G4
fu...@safe-mail.net fu...@safe-mail.net wrote: I have one question: Is the any way to put the mini in server mode (make it boot automatically after Power Loss)? While asking about server mode, is it also possible to run a PPC mini headless? Thanks.
Re: powering off with shutdown -hp?
Rene wrote: You can try to disable apm inthe kernel config. Christian wrote: Remco wrote: If I remember correctly, the following hack in /etc/sysctl.conf worked for me on a Pentium II machine: machdep.apmhalt=1# 1=powerdown hack, try if halt -p doesn't work It does work for my Pentium III-based Thinkpad A20m. Both methods worked! Either by disabling apm at UKC or by editing sysctl.conf. Theo wrote: There is a sophisticated heuristic in play. Thanks for jogging my memory! Not that the following describes all the gory details, but part of this heuristic is based on the SMBIOS version. Single processor system older than 2.4 (mine's 2.1) gets APM: http://marc.info/?l=openbsd-techm=124545473209570w=2 If anyone cares to indulge me further, is there any preference/advantage of going with ACPI over APM? Thanks again for such a great operating system! I'm always amazed at how OpenBSD helps keep old systems usable!
powering off with shutdown -hp?
I've just resurrected an old Pentium 3 system with the 22 October i386 snapshot of OpenBSD 4.6-current. It works great, however after issuing shutdown -hp now (I'm greeted with the message shutdown: switch -p must be used with -h. when using shutdown -p now), I'm getting the system message syncing disks... done followed by Attempting to power down The system never shuts off. From the dmesg (below), this appears to be an old APM-based motherboard. The shutdown(8) manpage states that not all hardware supports automatic power down. That's fine if this hardware doesn't support it, but given the Attempting to power down... message, I am curious if it might be possible. I'm including the dmesg output below along with pcidump -v and pcidump -x. If you would like more information, please let me know. Thanks!. # dmesg | more OpenBSD 4.6-current (GENERIC) #325: Thu Oct 22 20:38:45 MDT 2009 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class, 512KB L2 cache) 599 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE real mem = 804864000 (767MB) avail mem = 771416064 (735MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/17/00, BIOS32 rev. 0 @ 0xfd7a0, SMBIOS rev. 2.1 @ 0xefbe0 ( 42 entries) bios0: vendor Intel Corp. version 4S4EB2X0.86A.0024.P17 date 08/17/2000 bios0: Intel Corporation SE440BX-2 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xfd7a0/0x860 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries) pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x1000 0xe/0x4000! 0xe4000/0xc000 cpu0 at mainbus0: (uniprocessor) cpu0: disabling processor serial number pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82443BX AGP rev 0x03 intelagp0 at pchb0 agp0 at intelagp0: aperture at 0xf800, size 0x400 ppb0 at pci0 dev 1 function 0 Intel 82443BX AGP rev 0x03 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 Matrox MGA G400/G450 AGP rev 0x05 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) piixpcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x02 pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 wired to compatibility , channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: ST3160815A wd0: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: PLEXTOR, DVDR PX-820A, 1.00 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 7 function 2 Intel 82371AB USB rev 0x01: irq 9 piixpm0 at pci0 dev 7 function 3 Intel 82371AB Power rev 0x02: SMI iic0 at piixpm0 lmenv0 at iic0 addr 0x2d: adm9240 rev 2, starting scan spdmem0 at iic0 addr 0x50: 256MB SDRAM ECC PC133CL2 spdmem1 at iic0 addr 0x51: 256MB SDRAM ECC PC133CL2 spdmem2 at iic0 addr 0x52: 256MB SDRAM ECC PC133CL2 em0 at pci0 dev 13 function 0 Intel PRO/1000GT (82541GI) rev 0x05: irq 11, address 00:1b:21:0f:8b: 43 fxp0 at pci0 dev 14 function 0 Intel 8255x rev 0x08, i82559: irq 10, address 00:90:27:a7:50:80 inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 ohci0 at pci0 dev 15 function 0 NEC USB rev 0x43: irq 5, version 1.0 ohci1 at pci0 dev 15 function 1 NEC USB rev 0x43: irq 9, version 1.0 ehci0 at pci0 dev 15 function 2 NEC USB rev 0x04: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NEC EHCI root hub rev 2.00/1.00 addr 1 isa0 at piixpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at ohci0: USB revision 1.0 uhub2 at usb2 NEC OHCI root hub rev 1.00/1.00 addr 1 usb3 at ohci1: USB revision 1.0 uhub3 at usb3 NEC OHCI root hub rev 1.00/1.00 addr 1 biomask eb65 netmask ef65 ttymask mtrr: Pentium Pro MTRR support vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root root on wd0a swap on wd0b dump on wd0b # pcidump -v Domain /dev/pci0: 0:0:0: Intel 82443BX AGP 0x: Vendor ID: 8086 Product
books on embedded programming?
I've been looking at what books Amazon has on embedded programming, and the number is quite large. I would most certainly appreciate anyone's opinion on books on this subject. Since I'm pretty proficient in C programming and to a lesser degree assembly level programming, I'm looking for titles more meaty than introductory ones. Again, thanks for any recommendations shared.
mini-PCI Wistron CM9 2 antennae?
Scouring the archives didn't answer the following question; neither has poking about the Web. The Wistron CM9 mini-PCI card has 2 miniature SMT coaxial connectors. Is it possible to use just a single antenna, and is this advisable? Thanks for any insight shared.
CARP DHCP?
This may be incredibly simple to answer. Section 6.11.1 states that members of a CARP group need to reside on the same subnet with static IP addresses. So, does this mean that CARP can't be used in typical home environment using IP addresses coming from an ISP's DHCP server? I was wondering whether I could set up a CARP firewall with PF to add some protection to some home servers. Any information would be appreciated. Thanks!
inserting non-printable characters in sed?
I have been looking at sed to insert non-printable characters into text files. The sed(1) manpage states that I should be able to insert octal values by preceding the three character octal value with a backslash. However, my foo apparently isn't strong enough. eg. $ cat file first line second line FF third line fourth line FF $ sed 's!FF$!\f!' file output $ cat output first line second line FF third line fourth line FF $ sed 's!FF!\014!' file output $ cat output first line second line 014 third line fourth line 014 How am I misinterpreting how octal values can be inserted?
OpenNTPD configuration?
I'm a bit confused by what I am seeing in the logfiles when compared to the information found in the manpages and FAQ. I would appreciate if someone could provide some perspective. I've set up OpenNTPD on a 4.3-current server (192.168.0.4), and the time has finally reached synchronization as best I can tell: server $ sudo tail /var/log/daemon May 24 17:38:17 server ntpd[32321]: adjusting clock frequency by 12.518122 to 37.282963ppm May 24 18:06:18 server ntpd[32321]: adjusting clock frequency by -3.055956 to 34.227007ppm May 24 18:34:19 server ntpd[32321]: adjusting clock frequency by 1.532853 to 35.759861ppm May 24 19:02:20 server ntpd[32321]: adjusting clock frequency by -1.548559 to 34.211301ppm May 24 19:30:21 server ntpd[32321]: adjusting clock frequency by 27.436873 to 61.648175ppm May 24 19:58:22 server ntpd[32321]: adjusting clock frequency by -16.620842 to 45.027332ppm May 24 20:26:24 server ntpd[32321]: adjusting clock frequency by -21.159011 to 23.868321ppm May 24 20:54:25 server ntpd[32321]: adjusting clock frequency by -8.922065 to 14.946257ppm May 24 21:22:26 server ntpd[32321]: adjusting clock frequency by 19.461742 to 34.407999ppm May 24 21:50:27 server ntpd[32321]: adjusting clock frequency by -14.422098 to 19.985901ppm server $ I also have a 4.3-current client on the same subnet (192.168.0.6) switch (no firewalls involved), and see Connection refused in /var/log/daemon on the client's side: client $ sudo tail /var/log/daemon May 24 17:12:11 client dhclient[273]: DHCPACK from 192.168.0.1 May 24 17:12:11 client dhclient[273]: bound to 192.168.0.6 -- renewal in 43200 seconds. May 24 21:11:00 client ntpd[16786]: ntp engine ready May 24 21:11:00 client ntpd[16786]: recvfrom 192.168.0.4: Connection refused May 24 21:11:01 client savecore: no core dump May 24 21:29:45 client ntpd[8992]: ntp engine ready May 24 21:29:45 client ntpd[8992]: recvfrom 192.168.0.4: Connection refused May 24 21:29:46 client savecore: no core dump May 24 22:24:27 client ntpd[8992]: 0 out of 1 peers valid May 24 22:24:27 client ntpd[8992]: bad peer 192.168.0.4 (192.168.0.4) client $ The client has the following contents for its configuration files: client $ cat /etc/rc.conf.local ntpd_flags=-v client $ cat /etc/ntpd.conf # $OpenBSD: ntpd.conf,v 1.8 2007/07/13 09:05:52 henning Exp $ # sample ntpd configuration file, see ntpd.conf(5) # Addresses to listen on (ntpd does not listen by default) #listen on * # sync to a single server #server ntp.example.org server 192.168.0.4 # use a random selection of 8 public stratum 2 servers # see http://support.ntp.org/bin/view/Servers/NTPPoolServers #servers pool.ntp.org client $ I saw in the archives someone else having a similar error, but no definitive reply. It appears that the server is sending out traffic correctly on port 123: server $ netstat -f inet -na Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) ip 0 0 *.**.*17 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp0224 192.168.0.6.22 192.168.0.125.43307ESTABLISHED tcp0 0 192.168.0.6.48455 192.168.0.4.22 ESTABLISHED tcp0 0 192.168.0.6.22 192.168.0.125.44198ESTABLISHED tcp0 0 127.0.0.1.587 *.*LISTEN tcp0 0 127.0.0.1.25 *.*LISTEN tcp0 0 *.22 *.*LISTEN tcp0 0 *.37 *.*LISTEN tcp0 0 *.13 *.*LISTEN tcp0 0 *.113 *.*LISTEN Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) udp0 0 127.0.0.1.512 *.* udp0 0 192.168.0.6.32093 192.168.0.4.123 udp0 0 *.514 *.* server $ I know that it can take some time for the client to synchronize with an NTP server, but the Connection refused message has me wondering if I have missed something else in the configuration. Any help would be appreciated. Thanks!
Re: OpenNTPD configuration?
Jordi Espasa Clofent [EMAIL PROTECTED] write: ?Can you attach some log/info from _server_? Sure! I've attached a cheap USB GPS unit. The idea came from a thread back in October: http://marc.info/?l=openbsd-miscw=2r=1s=configuring+ntpd+to+use+GPSq=b server $ cat rc.conf.local nmeaattach_flags='/dev/cuaU0' ntpd_flags='-v' server $ cat ntpd.conf # $OpenBSD: ntpd.conf,v 1.8 2007/07/13 09:05:52 henning Exp $ # sample ntpd configuration file, see ntpd.conf(5) # Addresses to listen on (ntpd does not listen by default) #listen on * # sync to a single server #server ntp.example.org # use a random selection of 8 public stratum 2 servers # see http://support.ntp.org/bin/view/Servers/NTPPoolServers #servers pool.ntp.org sensor * $
configuration tweaks for CF-based systems?
There was mention a few days back that the following still contains useful information when it comes to reducing the amount of writing done to CF-like systems: http://blog.innerewut.de/2005/05/14/openbsd-3-7-on-wrap Yet I'm puzzled by the desire/need to move /dev into mfs. The timestamp on the files within /dev don't change, so what is the reason for moving the device nodes into memory? Are there parameters which are frequently changed residing in this directory? Any information shared would be appreciated. You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com
Re: configuration tweaks for CF-based systems?
On Thu, Apr 3, 2008 at 1:05 PM, Chris Kuethe [EMAIL PROTECTED] wrote: Try this: ls -ltr /dev | tail ; date ; tty This explains a lot. Thanks. The article referenced discusses copying /tmp, /var, and /dev into a memory-based filesystem. Obviously, the contents of /tmp don't need to retained across reboots, and the article covers how to save /var at shutdown. Are the changed contents of /dev not important to retain too? Thanks again! You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com
creating FAT32 partitions?
I apologize for the newbie question, but how is one supposed to add a FAT32 partition? The following shows where I have verified the partitioning of a USB flash drive containing two partitions through fdisk. One for OpenBSD (type A6) the rest FAT32. Yet when entering the disklabel, I am not seeing the FAT32 partition (typically partition 'i'), and disklabel doesn't allow adding it either. What is the trick for making this visible? $ sudo fdisk sd0 Disk: sd0 geometry: 124/255/63 [2002944 Sectors] Offset: 0 Signature: 0xAA55 Starting EndingLBA Info: #: id C H S - C H S [ start:size ] 0: 06 26 0 1 -123 254 63 [ 417690: 1574370 ] DOS 32MB 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused *3: A6 0 0 33 - 25 254 63 [ 32: 417658 ] OpenBSD $ sudo disklabel -E sd0 # Inside MBR partition 3: type A6 start 32 size 417658 Treating sectors 32-417690 as the OpenBSD portion of the disk. You can use the 'b' command to change this. Initial label editor (enter '?' for help at any prompt) p device: /dev/rsd0c type: SCSI disk: SCSI disk label: Flash Voyager bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 124 total sectors: 2002944 free sectors: 0 rpm: 3600 16 partitions: #size offset fstype [fsize bsize cpg] a: 417658 32 4.2BSD 2048 163841 c: 20029440 unused 0 0 a i No space left, you need to shrink a partition q No label changes. $ Special deal for Yahoo! users friends - No Cost. Get a month of Blockbuster Total Access now http://tc.deals.yahoo.com/tc/blockbuster/text3.com
OpenBSD support of EFI?
Please excuse my ignorance. In reading through the recent Intel Mac Mini thread, I'm confused by what appears to OpenBSD's support? OpenBSD now supports EFI? Or is EFI have some compatibility mode with the older BIOS standard? Any information would be greatly appreciated. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
