Sep 28
    Change language to:

So as people might have noticed; I did some active things in the FreeBSD region again, special emphasis on VuXML. I did some entries again and showed that I am still here :) I am also challenging people to work ‘against’ me in this case, please overtake me in the amount of entries; the FreeBSD-Security will surely improve because of that and that means our users are more aware of security issues, have a better chance at running secure applications [ or at least, fixing known issues, the unknown ones are always upcoming ].So far nobody really could get near except for Martin Wilke, who is doing a lot of entries as well; but not that near yet ;) (come on Martin!).Next week [ and perhaps this weekend ] I will do some more entries and outrank nectar@ and after that ofcourse the biggest committer for this simon@ :)Let the challenge begin, and improve the FreeBSD Security!  Continue reading »

written by Remko

Sep 24
    Change language to:

Recently I posted some news about EuroBSDcon, but the planet aggregator choked on Python 2.5 so the idea behind it was lost :(You can read about it here , and especially dont forget Tom Scholten’s wiki page  where he placed a few mindmaps of talks he visited, they could be very helpful for you!  Continue reading »

written by Remko

Sep 19
    Change language to:

Jikes! I upgraded my fileserver from 6-STABLE to 7-CURRENT. Everything still works fine :-) The only thing that stopped working is my Highpoint controller; which does not yet support 7-CURRENT (hey, highpoint people, please look into this :-)). FreeBSD happily sees this as a raid array though and uses ar0 to get to the data, which means all my data is still accessible etc.Ofcourse to prove this, my dmesg below for my fileserver, and indeed I now have two important machines running on FreeBSD CURRENT, my soekris firewall (5501) and my fileserver. The reason I can do this is because the system is fairly stable already! and has a bulk of superinteresting features like ZFS and better TCP stuff. So please try this at home! :-)

CODE:
  1. Copyright (c) 1992-2007 The FreeBSD Project.
  2. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
  3.         The Regents of the University of California. All rights reserved.
  4. FreeBSD is a registered trademark of The FreeBSD Foundation.
  5. FreeBSD 7.0-CURRENT #6: Sat Oct  6 21:32:48 CEST 2007
  6.     root@guardian.elvandar.org:/usr/obj/usr/src/sys/GUARDIAN
  7. link_elf_obj: symbol msleep undefined
  8. KLD file highpoint.ko - could not finalize loading
  9. Timecounter "i8254" frequency 1193182 Hz quality 0
  10. CPU: AMD Athlon(tm) 64 Processor 3000+ (2002.58-MHz K8-class CPU)
  11.   Origin = "AuthenticAMD"  Id = 0xf48  Stepping = 8
  12.   Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
  13.   AMD Features=0xe0500800<SYSCALL,NX,MMX+,LM,3DNow!+,3DNow!>
  14. usable memory = 2133962752 (2035 MB)
  15. avail memory  = 2059280384 (1963 MB)
  16. ACPI APIC Table: <A M I  OEMAPIC>
  17. ioapic0: Changing APIC ID to 1
  18. MADT: Forcing active-low polarity and level trigger for SCI
  19. ioapic0 <Version 0.3> irqs 0-23 on motherboard
  20. kbd1 at kbdmux0
  21. ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
  22. acpi0: <A M I OEMRSDT> on motherboard
  23. acpi0: [ITHREAD]
  24. acpi0: Power Button (fixed)
  25. acpi0: reservation of 0, a0000 (3) failed
  26. acpi0: reservation of 100000, 7fef0000 (3) failed
  27. Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
  28. acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
  29. cpu0: <ACPI CPU> on acpi0
  30. powernow0: <Cool`n'Quiet K8> on cpu0
  31. device_attach: powernow0 attach returned 6
  32. pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
  33. pci0: <ACPI PCI bus> on pcib0
  34. agp0: <VIA 8385 host to PCI bridge> on hostb0
  35. pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
  36. pci1: <ACPI PCI bus> on pcib1
  37. vgapci0: <VGA-compatible display> port 0x7000-0x70ff mem 0xe8000000-0xefffffff,0xfc400000-0xfc40ffff irq 16 at device 0.0 on pci1
  38. fwohci0: <VIA Fire II (VT6306)> port 0xd800-0xd87f mem 0xfdd00000-0xfdd007ff irq 16 at device 7.0 on pci0
  39. fwohci0: [FILTER]
  40. fwohci0: OHCI version 1.0 (ROM=1)
  41. fwohci0: No. of Isochronous channels is 4.
  42. fwohci0: EUI64 00:e0:18:00:00:5f:8d:72
  43. fwohci0: Phy 1394a available S400, 2 ports.
  44. fwohci0: Link S400, max_rec 2048 bytes.
  45. firewire0: <IEEE1394(FireWire) bus> on fwohci0
  46. dcons_crom0: <dcons configuration ROM> on firewire0
  47. dcons_crom0: bus_addr 0x278c000
  48. fwe0: <Ethernet over FireWire> on firewire0
  49. if_fwe0: Fake Ethernet address: 02:e0:18:5f:8d:72
  50. fwe0: Ethernet address: 02:e0:18:5f:8d:72
  51. fwip0: <IP over FireWire> on firewire0
  52. fwip0: Firewire address: 00:e0:18:00:00:5f:8d:72 @ 0xfffe00000000, S400, maxrec 2048
  53. sbp0: <SBP-2/SCSI over FireWire> on firewire0
  54. fwohci0: Initiate bus reset
  55. fwohci0: BUS reset
  56. fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
  57. atapci0: <Promise PDC20378 SATA150 controller> port 0xe800-0xe83f,0xe400-0xe40f,0xe000-0xe07f mem 0xfdf00000-0xfdf00fff,0xfde00000-0xfde1ffff irq 18 at device 8.0 on pci0
  58. atapci0: [ITHREAD]
  59. atapci0: [ITHREAD]
  60. ata2: <ATA channel 0> on atapci0
  61. ata2: [ITHREAD]
  62. ata3: <ATA channel 1> on atapci0
  63. ata3: [ITHREAD]
  64. ata4: <ATA channel 2> on atapci0
  65. ata4: [ITHREAD]
  66. skc0: <Marvell Gigabit Ethernet> port 0xd400-0xd4ff mem 0xfdc00000-0xfdc03fff irq 17 at device 10.0 on pci0
  67. skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7)
  68. sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
  69. sk0: Ethernet address: 00:0e:a6:70:21:41
  70. miibus0: <MII bus> on sk0
  71. e1000phy0: <Marvell 88E1011 Gigabit PHY> PHY 0 on miibus0
  72. e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
  73. skc0: [ITHREAD]
  74. atapci1: <HighPoint HPT374 (channel 0+1) UDMA133 controller> port 0xb400-0xb407,0xb000-0xb003,0xa800-0xa807,0xa400-0xa403,0xa000-0xa0ff irq 16 at device 11.0 on pci0
  75. atapci1: [ITHREAD]
  76. ata5: <ATA channel 0> on atapci1
  77. ata5: [ITHREAD]
  78. ata6: <ATA channel 1> on atapci1
  79. ata6: [ITHREAD]
  80. atapci2: <HighPoint HPT374 (channel 2+3) UDMA133 controller> port 0xd000-0xd007,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xb800-0xb8ff irq 16 at device 11.1 on pci0
  81. atapci2: [ITHREAD]
  82. ata7: <ATA channel 0> on atapci2
  83. ata7: [ITHREAD]
  84. ata8: <ATA channel 1> on atapci2
  85. ata8: [ITHREAD]
  86. em0: <Intel(R) PRO/1000 Network Connection Version - 6.5.3> port 0x9800-0x983f mem 0xfd900000-0xfd91ffff,0xfd800000-0xfd81ffff irq 18 at device 13.0 on pci0
  87. em0: Ethernet address: 00:0e:0c:2e:41:f6
  88. em0: [FILTER]
  89. em1: <Intel(R) PRO/1000 Network Connection Version - 6.5.3> port 0x9400-0x943f mem 0xfd600000-0xfd61ffff,0xfd400000-0xfd41ffff irq 19 at device 14.0 on pci0
  90. em1: Ethernet address: 00:0e:0c:2e:3f:ce
  91. em1: [FILTER]
  92. atapci3: <VIA 6420 SATA150 controller> port 0x9000-0x9007,0x8800-0x8803,0x8400-0x8407,0x8000-0x8003,0xec00-0xec0f,0xdc00-0xdcff irq 20 at device 15.0 on pci0
  93. atapci3: [ITHREAD]
  94. ata9: <ATA channel 0> on atapci3
  95. ata9: [ITHREAD]
  96. ata10: <ATA channel 1> on atapci3
  97. ata10: [ITHREAD]
  98. atapci4: <VIA 8237 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0
  99. ata0: <ATA channel 0> on atapci4
  100. ata0: [ITHREAD]
  101. ata1: <ATA channel 1> on atapci4
  102. ata1: [ITHREAD]
  103. uhci0: <VIA 83C572 USB controller> port 0x9c00-0x9c1f irq 21 at device 16.0 on pci0
  104. uhci0: [GIANT-LOCKED]
  105. uhci0: [ITHREAD]
  106. usb0: <VIA 83C572 USB controller> on uhci0
  107. usb0: USB revision 1.0
  108. uhub0: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
  109. uhub0: 2 ports with 2 removable, self powered
  110. uhci1: <VIA 83C572 USB controller> port 0xac00-0xac1f irq 21 at device 16.1 on pci0
  111. uhci1: [GIANT-LOCKED]
  112. uhci1: [ITHREAD]
  113. usb1: <VIA 83C572 USB controller> on uhci1
  114. usb1: USB revision 1.0
  115. uhub1: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
  116. uhub1: 2 ports with 2 removable, self powered
  117. uhci2: <VIA 83C572 USB controller> port 0xbc00-0xbc1f irq 21 at device 16.2 on pci0
  118. uhci2: [GIANT-LOCKED]
  119. uhci2: [ITHREAD]
  120. usb2: <VIA 83C572 USB controller> on uhci2
  121. usb2: USB revision 1.0
  122. uhub2: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
  123. uhub2: 2 ports with 2 removable, self powered
  124. uhci3: <VIA 83C572 USB controller> port 0xcc00-0xcc1f irq 21 at device 16.3 on pci0
  125. uhci3: [GIANT-LOCKED]
  126. uhci3: [ITHREAD]
  127. usb3: <VIA 83C572 USB controller> on uhci3
  128. usb3: USB revision 1.0
  129. uhub3: <VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
  130. uhub3: 2 ports with 2 removable, self powered
  131. ehci0: <VIA VT6202 USB 2.0 controller> mem 0xfd200000-0xfd2000ff irq 21 at device 16.4 on pci0
  132. ehci0: [GIANT-LOCKED]
  133. ehci0: [ITHREAD]
  134. usb4: EHCI version 1.0
  135. usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
  136. usb4: <VIA VT6202 USB 2.0 controller> on ehci0
  137. usb4: USB revision 2.0
  138. uhub4: <VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4
  139. uhub4: 8 ports with 8 removable, self powered
  140. isab0: <PCI-ISA bridge> at device 17.0 on pci0
  141. isa0: <ISA bus> on isab0
  142. pci0: <multimedia, audio> at device 17.5 (no driver attached)
  143. acpi_button0: <Power Button> on acpi0
  144. acpi_button1: <Sleep Button> on acpi0
  145. sio0: configured irq 3 not in bitmap of probed irqs 0
  146. sio0: port may not be enabled
  147. sio0: configured irq 3 not in bitmap of probed irqs 0
  148. sio0: port may not be enabled
  149. sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0
  150. sio0: type 16550A
  151. sio0: [FILTER]
  152. sio1: configured irq 4 not in bitmap of probed irqs 0
  153. sio1: port may not be enabled
  154. sio1: configured irq 4 not in bitmap of probed irqs 0
  155. sio1: port may not be enabled
  156. sio1: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0
  157. sio1: type 16550A
  158. sio1: [FILTER]
  159. orm0: <ISA Option ROM> at iomem 0xc0000-0xccfff on isa0
  160. atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
  161. atkbd0: <AT Keyboard> irq 1 on atkbdc0
  162. kbd0 at atkbd0
  163. atkbd0: [GIANT-LOCKED]
  164. atkbd0: [ITHREAD]
  165. ppc0: cannot reserve I/O port range
  166. sc0: <System console> at flags 0x100 on isa0
  167. sc0: VGA <16 virtual consoles, flags=0x300>
  168. vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
  169. Timecounter "TSC" frequency 2002576565 Hz quality 800
  170. Timecounters tick every 1.000 msec
  171. firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
  172. firewire0: bus manager 0 (me)
  173. ad4: 78167MB <Maxtor 6L080M0 BANC1G10> at ata2-master SATA150
  174. ad10: 305245MB <MAXTOR STM3320620A 3.AAD> at ata5-master UDMA100
  175. ad11: 305245MB <MAXTOR STM3320620A 3.AAD> at ata5-slave UDMA100
  176. ad12: 305245MB <MAXTOR STM3320620A 3.AAD> at ata6-master UDMA100
  177. ad13: 305245MB <MAXTOR STM3320620A 3.AAD> at ata6-slave UDMA100
  178. ar0: 915735MB <HighPoint v3 RocketRAID RAID5 (stripe 64 KB)> status: READY
  179. ar0: disk0 READY using ad10 at ata5-master
  180. ar0: disk1 READY using ad13 at ata6-slave
  181. ar0: disk2 READY using ad12 at ata6-master
  182. ar0: disk3 READY using ad11 at ata5-slave
  183. Trying to mount root from ufs:/dev/ad4s1a
  184. WARNING: ZFS is considered to be an experimental feature in FreeBSD.
  185. ZFS filesystem version 6
  186. ZFS storage pool version 6

written by Remko

Sep 19
    Change language to:

Heh, well yeah a lot of new posts in one go. I found some time to actually write them so lets go :-)I am currently doing a new project in between, recently we disconnected our old VCR player at home. We never used it much and old VHS tapes are guaranteed to break at some point. So we decided to cleanup etc. Now we have just a few (50 or so) VHS tapes lying around doing nothing. Amongst them are a few videos of when my brother and I were young, oh those good old days :p

Since I do not want to loose those videos and preserve them on recent modern equipment, I am transporting them to DVD, which is an timeconsuming job, but seems to work very well so far. The first test I did was with a cartoon of Robin Hood, (A fox in the cartoon version), which looks OK enough on TV, ofcourse it copies the video quality so it wont improve much from that, but at least it's digitally stored now. I need to make sure to regulary copy them over again so that the DVD's remain healthy (burned DVD's will ofcourse fade away at some point). When this huge project is over, we can safely store our VHS tapes in a closet or somethign and use the DVD's from now on.

Now only to persuade my parents to buy an DVD / HD recorder to grab TV broadcasts so that we really do not need to VHS tape thingy any longer ;-)

written by Remko

Sep 19
    Change language to:

Recently I had some feedback from Lance Spitzner about the Honeynet mirror check tool; he was very happy that it finally worked well :-), we are currently using this on a day by day basis to check the status of our various mirrors. We already dropped a few hosts and added a few new ones, all because of the mirror check tool (or because of the interest ofcourse). So I can safely assume that it is an success so far.

There are a couple of ideas to improve the tool a bit more, like timeout values for alerting so that you are not covered in alerts day in day out, propagating the output to an db so that you might generate more usefull information from it (mostly reporting) and a few more. Ofcourse I want to update the perl code itself to be more cool (it's just very basic at the moment, effective but basic :-)), if you have good suggestions for this tool, please comment on this item and I Will see what I can do :-)

written by Remko

Sep 19
    Change language to:

As most of you might have noticed I had been slacking again lately for FreeBSD work. Problem for me is that I need to find a serious way to handle my groups, they aren't too many, but I have a problem giving groups Priorities, because I want to be active in all my regions and not in just one :-)

I think I figured out a way how to handle that now, in front of me is  a little note that devides my time each day, for Secteam, Source committer team, bugmeister team, doc team and doc-nl team. These days will be processed and delt with in a work week (monday till friday) so that I have dedicated time available for those regions. Whenever time permits or inactivity occurs in one of the specified days, I can always do something else (perl coding, maintaining one of the other groups, etc.) I think and feel this will work now that I have visited EuroBSDcon again, this inspired me to do a lot as I used to do :-), now bear with me and give me ideas if you think I should do better at some front!

written by Remko