Re: trac on OpenBSD current

[Sebastiano Pomata]

Il 21/01/10 01:38, Robert ha scritto:
> On Thu, 21 Jan 2010 00:31:58 +0100
> Sebastiano Pomata  wrote:
> 
>> I can't understand how to get the latest version of trac from the
>> ports. I downloaded just today the whole ports tree for OpenBSD, but I
>> can only find trac version 0.11.4, while openports.se states that
>> there's a 0.11.6 port version.
>>
>> Where can I find it? I thought that connecting through AnonCVS to one
>> random server from the one listed on OpenBSD website was enough
>>
>> Il 16/01/2010 15.31, Stuart Henderson ha scritto:
>>> On 2010-01-15, Sebastiano  wrote:
 I found on OpenPorts the trac package, and I'm wondering if it is
 already ok to work with chrooted apache provided by a default
 installation.

 Or do I have to tweak something (or a lot)?
 Or simply it just won't work and I should get apache-httpd?
>>>
>>> You'll have to copy a lot into the chroot (various parts of python
>>> and the associated system libraries). It can be done, but seriously
>>> weakens the chroot, and is a real pain to keep maintained.
>>>
>>> If you really want to run it as cgi, you can do this with base httpd
>>> using -u to disable chroot (optionally a second instance on a
>>> different port or address).
>>>
>>> I'm just using the built-in standalone server here though, it works
>>> fine for what I'm doing. If I wanted anything more complicated I'd
>>> be looking at the FastCGI configuration instead (but then I wouldn't
>>> be using apache either ;-)
>>>
>>>   http://trac.edgewall.org/wiki/TracFastCgi
> 
> 
> trac .6 is in -current.
> my guess is you are on -stable. -stable has trac .4 .
> if you want .6 you have to upgrade your system to -current (via
> snapshot and/or source) and use the package or port from -current.
> 
> - Robert
> 


I think that this is the point. I installed from a plain
install46.iso, but then I thought I could have choosen which ports
tree to choose, -stable or -current. Where can I get more info about
the upgrade process to -current?

Thanks

Sebastiano

Re: Books on reverse engineering?

[Tobias Ulmer]

On Wed, Jan 20, 2010 at 05:52:52PM -0800, James Hozier wrote:
> With every single laptop I've bought/been given over the years, I
> was able to run OpenBSD on them almost flawlessly save a few
> quick/simple hacks to make anything that didn't work, work.
> 
> The one main issue I've had with ALL of them was the wireless
> card...maybe I was just unlucky to have gotten ones with crappy
> chipsets (like this Broadcom I have now which is totally useless...
> I want to stomp on it real badly) but nonetheless it pisses me off.
> 
> I want to try and help solve my own problems as well as for the OBSD
> community who might also have this particular issue, so I'm looking
> to research on how to reverse engineer these things and write drivers
> for them.
> 
> I know it's not easy, even though I don't understand how hard it is
> because I've never done it before, but I do hear that if there's a
> hell, it's a place where people are sent to do this for eternity.
> 
> So with that reference in mind, would anyone experienced care to point
> me in some correct direction? (Which texts to read, which programming
> language(s) to focus on, etc.)

- C
- any intro/boot to x86 assembly; to get the basics
- intel cpu pdfs
- ida pro / ollydbg
- something on computer architecture.
- windows ddk to get an idea how drivers work on windows, possibly book
  on same topic.
- BSD basics (McKusick, Bach, etc) + whatever you can get your hands on
- Device is connected via a BUS to CPU -> docs.
- IEEE standards
- any other docs.
- more of the same
- Read lots of code.
- supertanker sized amounts of experience
- ability to research stuff yourself, without asking on a ml
- etc

Your question is naive. If you were up to it, you wouldn't have to ask
the equivalent of "How do I become an awesome hacker?".

Writing this up was and is a waste of time, it will never happen.

Re: trac on OpenBSD current

[James Hartley]

On Thu, Jan 21, 2010 at 12:39 AM, Sebastiano Pomata <
sebastianopom...@tiscali.it> wrote:

> I installed from a plain
> install46.iso, but then I thought I could have choosen which ports
> tree to choose, -stable or -current.


No.  FAQ 15.4.1 states that mixing the -current ports tree with a -release
installation is not supported.  Reading Section 15 is highly recommended.


> Where can I get more info about
> the upgrade process to -current?
>

FAQ 5.3.2.

Re: trac on OpenBSD current

[Michal]

> I think that this is the point. I installed from a plain
> install46.iso, but then I thought I could have choosen which ports
> tree to choose, -stable or -current. Where can I get more info about
> the upgrade process to -current?
> 
> Thanks
> 
> Sebastiano
> 

http://openbsd.org/anoncvs.html#starting
http://www.openbsd101.com/updating.html

Some places to start. Use cvsup to download src, ports...whatever you
wish and choose the branch you want, stable or current. Do some digging

Re: Inconsistency between IPv6 and IPv4 announces between eBGP peers hooked through an iBGP session (OpenBGPd)

[Laurent CARON]

On 19/01/2010 14:03, Laurent CARON wrote:

On 19/01/2010 13:23, Sebastian Spies wrote:

Seems, that the Cisco doesn't send the initial Keepalive. Could you
please provide a longer caption using -s 4096 and the OPEN messages of
20091201


$ tcpdump -s 4096 -w /tmp/bgpd_20091201_4096 -i bge0 host
2001:7A8:1:9FF2::1
$ tcpdump -s 4096 -w /tmp/bgpd_20091202_4096 -i bge0 host
2001:7A8:1:9FF2::1

http://zenon.apartia.fr/stuff/bgpd_20091201_4096 <=> Working announces
http://zenon.apartia.fr/stuff/bgpd_20091202_4096 <=> Non-Working announces



Hi,

Do you have a clue about this problem ?

Thanks

Re: trac on OpenBSD current

[Robert]

On Thu, 21 Jan 2010 09:39:20 +0100
Sebastiano Pomata  wrote:

> Il 21/01/10 01:38, Robert ha scritto:
> > On Thu, 21 Jan 2010 00:31:58 +0100
> > Sebastiano Pomata  wrote:
> > 
> >> I can't understand how to get the latest version of trac from the
> >> ports. I downloaded just today the whole ports tree for OpenBSD,
> >> but I can only find trac version 0.11.4, while openports.se states
> >> that there's a 0.11.6 port version.
> >>
> >> Where can I find it? I thought that connecting through AnonCVS to
> >> one random server from the one listed on OpenBSD website was enough
> >>
> >> Il 16/01/2010 15.31, Stuart Henderson ha scritto:
> >>> On 2010-01-15, Sebastiano  wrote:
>  I found on OpenPorts the trac package, and I'm wondering if it is
>  already ok to work with chrooted apache provided by a default
>  installation.
> 
>  Or do I have to tweak something (or a lot)?
>  Or simply it just won't work and I should get apache-httpd?
> >>>
> >>> You'll have to copy a lot into the chroot (various parts of python
> >>> and the associated system libraries). It can be done, but
> >>> seriously weakens the chroot, and is a real pain to keep
> >>> maintained.
> >>>
> >>> If you really want to run it as cgi, you can do this with base
> >>> httpd using -u to disable chroot (optionally a second instance on
> >>> a different port or address).
> >>>
> >>> I'm just using the built-in standalone server here though, it
> >>> works fine for what I'm doing. If I wanted anything more
> >>> complicated I'd be looking at the FastCGI configuration instead
> >>> (but then I wouldn't be using apache either ;-)
> >>>
> >>>   http://trac.edgewall.org/wiki/TracFastCgi
> > 
> > 
> > trac .6 is in -current.
> > my guess is you are on -stable. -stable has trac .4 .
> > if you want .6 you have to upgrade your system to -current (via
> > snapshot and/or source) and use the package or port from -current.
> > 
> > - Robert
> > 
> 
> 
> I think that this is the point. I installed from a plain
> install46.iso, but then I thought I could have choosen which ports
> tree to choose, -stable or -current. Where can I get more info about
> the upgrade process to -current?
> 
> Thanks
> 
> Sebastiano

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

The short version:
- download a snapshot and upgrade your system with that
- point PKG_PATH at snapshot packages


- Robert

Re: raidctl and reconstruction failure

[Sebastiano Pomata]

Il 20/01/10 18:18, MERIGHI Marcus ha scritto:
> Hello Sebastiano, 
> 
> I once got it going by adding the failed component to dev as a spare
> (raidctl -a component dev). After rebooting the component was not a
> spare anymore but turned to the live component (automagically
> recognised?!) again, with a status of failed, of course. reconstruction
> went like a charm, though, and everything was fine afterwards...
> 
> Good luck, 
> 
> Max


raidctl -s raid0 reports that wd0d is failed, and wd1d is optimal.

Then I give: raidctl -v -a /dev/wd0d raid0 and I got this error:

ioctl (RAIDFRAME_ADD_HOT_SPARE) failed.

Should I deconfigure the device from raid before adding it as hot
spare, to allow then the reconstruction of the second disk?

Re: Books on reverse engineering?

[Tomas Bodzar]

On Thu, Jan 21, 2010 at 9:42 AM, Tobias Ulmer  wrote:
> On Wed, Jan 20, 2010 at 05:52:52PM -0800, James Hozier wrote:
>> With every single laptop I've bought/been given over the years, I
>> was able to run OpenBSD on them almost flawlessly save a few
>> quick/simple hacks to make anything that didn't work, work.
>>
>> The one main issue I've had with ALL of them was the wireless
>> card...maybe I was just unlucky to have gotten ones with crappy
>> chipsets (like this Broadcom I have now which is totally useless...
>> I want to stomp on it real badly) but nonetheless it pisses me off.
>>
>> I want to try and help solve my own problems as well as for the OBSD
>> community who might also have this particular issue, so I'm looking
>> to research on how to reverse engineer these things and write drivers
>> for them.
>>
>> I know it's not easy, even though I don't understand how hard it is
>> because I've never done it before, but I do hear that if there's a
>> hell, it's a place where people are sent to do this for eternity.
>>
>> So with that reference in mind, would anyone experienced care to point
>> me in some correct direction? (Which texts to read, which programming
>> language(s) to focus on, etc.)
>
> - C
> - any intro/boot to x86 assembly; to get the basics
> - intel cpu pdfs
> - ida pro / ollydbg
> - something on computer architecture.
> - windows ddk to get an idea how drivers work on windows, possibly book
> B on same topic.
> - BSD basics (McKusick, Bach, etc) + whatever you can get your hands on
> - Device is connected via a BUS to CPU -> docs.
> - IEEE standards
> - any other docs.
> - more of the same
> - Read lots of code.
> - supertanker sized amounts of experience
> - ability to research stuff yourself, without asking on a ml
> - etc
>
> Your question is naive. If you were up to it, you wouldn't have to ask
> the equivalent of "How do I become an awesome hacker?".
>


There is similar manual available :-)
http://catb.org/~esr/faqs/hacker-howto.html


> Writing this up was and is a waste of time, it will never happen.

Re: trac on OpenBSD current

[Joachim Schipper]

On Thu, Jan 21, 2010 at 12:26:01PM +1100, Aaron Mason wrote:
> On Sun, Jan 17, 2010 at 1:48 AM, Sebastiano Pomata
>  wrote:
> > After installing the package, pkg_add suggests to run the trac
> > standalone server, so I think I will stick with it for trac, while
> > keeping apache chrooted for other websites.
> >
> > I think my trac project it's simple enough that I don't need FastCGI
> > option
> 
> Sadly OpenBSD's Apache doesn't allow you to connect to an external
> FastCGI server if it isn't PHP.  That would be super useful for things
> like this.  Probably also a super security hole.
> 
> The standalone HTTP server is probably your best bet.  Or nginx.

Are you sure? I'm pretty certain I had an external FastCGI process
working at one point. (That is, it listened on say, 127.0.0.1:8000 and
Apache contacted it as required.)

Joachim

Estrategias y Técnicas de Supervisión y Organización de “Almacenes e Inventarios”

[Lic. Karen Gómez]

PMS de MC)xico lo invita al excelente seminario:

Estrategias y TC)cnicas de SupervisiC3n y OrganizaciC3nB de bAlmacenes e
Inventariosb

MC)xico D.F. 11 de Febrero
GuadalajaraB  23 de Febrero


Una C3ptima ejecuciC3n en la cadena de suministro comienza con planeaciC3n
estratC)gica y procesos de negocio definidos.
Los elementos de la cadena, bien administrados apoyan la operaciC3n
logC-stica.
El resguardo de materiales resulta mC!s eficiente cuando va de la mano de
conceptos aplicados en concordancia con la estrategia del negocio.

Objetivos del seminario:
*Comprender el proceso de administraciC3n y su influencia en el almacC)n.
*Aplicar la Ley de Pareto para eficientar la confiabilidad de los registros
operativos.
*Identificar los principios de administraciC3n de inventarios y los sistemas
dereposiciC3n mC!s comunes.
*Aplicar conceptos en ejercicios y casos prC!cticos

Resultados:
Relacionar la importancia estratC)gica del almacC)n conforme los objetivos del
negocio.
Ubicar el papel de PlaneaciC3n, Compras, Proveedores e Inventarios dentro de
la Cadena de Suministro
AplicaciC3n prC!ctica de conceptos en ejercicios y dinC!micas.

Dirigido a:
Responsables de LogC-stica, Inventarios, AlmacC)n, Planeadores de materiales
y
Encargados de abastecimiento o compra de materiales

Mayores informes responda este correo electrC3nico con los siguientes datos.
Empresa:
Nombre:
TelC)fono:
Email.
NC:mero de Interesados:
Y en breve le haremos llegar la informaciC3n completa del evento.

O bien comunC-quese a nuestros telC)fonos y un ejecutivo con gusto le
atenderC!.
Tels. (33)8851-2365, (33)3125-4658
Reciba un cordial saludo.


Este Mensaje ha sido enviado a misc@openbsd.org como usuario de Pms de MC)xico
o bien un usuario le refiriC3 para recibir este boletC-n.
Como usuario de Pms de MC)xico, en este acto autoriza de manera expresa que
Pms de MC)xico le puede contactar vC-a correo electrC3nico u otros medios. Si
usted ha recibido este mensaje por error, haga caso omiso de el y reporte su
cuenta respondiendo este correo con el subject BAJAALMACEN
Unsubscribe to this mailing list, reply a blank message with the subject
UNSUBSCRIBE ALMACEN
Tenga en cuenta que la gestiC3n de nuestras bases de datos es de suma
importancia y no es intenciC3n de la empresa la inconformidad del receptor.

Re: Books on reverse engineering?

[Brad Tilley]

On Wed, 20 Jan 2010 17:52 -0800, "James Hozier"  wrote:
> With every single laptop I've bought/been given over the years, I
> was able to run OpenBSD on them almost flawlessly save a few
> quick/simple hacks to make anything that didn't work, work.
> 
> The one main issue I've had with ALL of them was the wireless
> card...maybe I was just unlucky to have gotten ones with crappy
> chipsets 

Purchase a few 802.11 USB sticks. You can find devices that have very 
well-documented chipsets on newegg for less than 15 dollars (USD). These 
devices are 100% supported in OpenBSD. The man pages list these devices and are 
very accurate. For example, man run and see the HARDWARE section.

You might also consider installing OpenBSD -current to a USB stick and try 
booting the laptop from that before purchasing. That way, you'd know exactly 
what hardware you were getting.

Brad

[snip]

Re: Books on reverse engineering?

[Ted Unangst]

On Thu, Jan 21, 2010 at 5:55 AM, Tomas Bodzar  wrote:
> On Thu, Jan 21, 2010 at 9:42 AM, Tobias Ulmer  wrote:
>> - ability to research stuff yourself, without asking on a ml
>> - etc
>>
>> Your question is naive. If you were up to it, you wouldn't have to ask
>> the equivalent of "How do I become an awesome hacker?".

Very true.  The one thing you didn't mention, and may not be obvious
to an outsider trying to get in, is go to a conference.  There's a
cheap local one everywhere (ruxcon, toorcon, shmoocon, ccc).  Just go
and see what tools people use (but don't talk to anyone unless you're
dying to be embarrassed by how much more a 16 year knows than you :)).
 If you can't do that, the speakers have blogs.  Read them.

> There is similar manual available :-)
> http://catb.org/~esr/faqs/hacker-howto.html

Like a lot of his writing, it's mostly crap.  I stopped reading after this.

"Real hackers call these people crackers and want nothing to do with
them. Real hackers mostly think crackers are lazy, irresponsible, and
not very bright, and object that being able to break security doesn't
make you a hacker any more than being able to hotwire cars makes you
an automotive engineer."

For the purposes of our discussion, reversing drivers, turns out that
those naughty "crackers" are the people with the best tools and skill
sets.  Reversing a driver is like reversing skype, only about 100x
easier because even the evil driver writers don't try that hard to
obfuscate their code.

Mühendislere bu dergilerin aboneliği hediye

[Bilgi işlem]

M|hendislere  bu dergilerin abonelipi hediye  L|tfen







M|hendislere

bu dergilerin abonelipi hediye



L|tfen 't}k'lay}n:



http://www.haberortak.com

Dole kilogrami!

[E-topshop]

Top Shop

Pravo je vreme da se pozabavite svojom figurom!

Iskoristite i Vi u veliku zimsku akciju:

Dole kilogrami!

B;

najbolji proizvodi za brzo i jednostavno skidanje kilograma bez strogih i
napornih dijeta!

B;

veliki popusti: i do -64%

B;

hit proizvodi uz besplatnu dostavu

B;

za 20 najbrE>ih: BMI metar za lakE!e praDenje skidanja kilograma

Pogledajte super ponude za mrE!avljenje!B;

Dole kilogrami

Vitkost je privlaD
na, moderna i zdrava... postignite je i Vi!

Objavite rat masnim naslagama VED DANAS - kliknite i poruD
ite!

Da li ste znali da su gojazne osobe sklonije depresiji i loE!em
raspoloE>enju?

Celluless -25%

Celluless

VaE!a cena: 2.990 RSD

ViE!eB;

Bathroom Scale -15%

Bathroom Scale 5 in 1

VaE!a cena: 2.200 RSD

ViE!eB;

Bun'n'Thigh Doer -15%

Bun'n'Thigh Doer

VaE!a cena: 5.090 RSD

ViE!eB;

Osobe sa viE!kom kilograma imaju poveDan rizik od srD
anog i moE>danog
udara!

Winsor Pilates -62%

Winsor Pilates

VaE!a cena: 1,341 RSD

ViE!eB;

Rina's 90 1+2 -15%

Rina's 90 1+2

VaE!a cena: 1.190 RSD

ViE!eB;

Fitnes paket: -15%

Fitnes paket

VaE!a cena: 1.390 RSD

ViE!eB;

Gojazne osobe D
eE!De imaju problem sa dijabetesom, poviE!enim krvnim
pritiskom i holesterolom!

Velform Sauna Massage

Velform Sauna Massage

Cena+dostava: 6.490 RSD

ViE!eB;

Multi Functional Bench

Multi-Functional Bench

Cena+dostava: 7.490 RSD

ViE!eB;

Dry Cooker

Dry Cooker

Cena+dostava: 2.290 RSD

ViE!eB;

Dijeta je daleko efikasnija uz veE>banje!

Ab Tronic x2

Ab Tronic x 2

Cena+dostava: 7.990 RSD

ViE!eB;

Orbitrek Elite

Orbitrek Elite

Cena+dostava: 16.990 RSD

ViE!eB;

Flavorvawe Turbo Oven

Flavorvawe Turbo Oven

Cena+dostava:11.490 RSD

ViE!eB;

Super prilika za vitak stas uz uE!tedu - poruD
ite odmah! B;

Ovu elektronsku poE!tu primate, ukoliko ste svojevoljno ostavili svoju
e-mail adresu na nekom od sajtova Top Shop-a, uD
estvovali u naE!oj
poklon igri ili nagradnom kvizu ili se prijavili za e-D
asopis Top Shop-a
ili nekog od nasih brendova.

Ponude date u ovom e-mailu vaE>e iskljuD
ivo za porudE>bine upuDene
putem Interneta ili broja telefona 021 489 26 60. Ponude vaE>e do 10. 02.
2010. ili do isteka zaliha. Isporuku vrE!imo samo u Srbiji.

Ukoliko ne E>elite viE!e da primate naE!e elektronske poruke, za
odjavljivanje sa naE!e e-mailing liste, kliknite ovde.

Studio Moderna d.o.o., Bulevar vojvode Stepe 30, 21000 Novi Sad, Tel: 021
489 26 60, Fax: 021 489 29 08,
E-mail: i...@news.e-topshop.tv

[IMAGE]If you would no longer like to receive our emails please
unsubscribe by clicking here.

OT: article comparing SFTP vs FTPS

[Lars Nooden]

Can anyone point to an article comparing the protocols SFTP and FTPS
that meets all four of the following criteria?

a. is well-written
b. contains accurate information
c. contains uptodate information, not ten years out of date
d. is authoritative
   (ideally hosted at a CS dept or FOSS project)

Regards
/Lars

IPSEC: "bad checksum"

[Toni Mueller]

Hi,

today I see tons of these on a 4.6-stable/amd64 machine (sample):

17:21:00.848135 esp 1.1.1.1 > 2.2.2.2 spi 0x54d46678 seq 132642 len 84 (DF) 
(ttl 64, id 49897, len 104, bad cksum 0! differs by 8b3c)
17:21:00.859630 esp 2.2.2.2 > 1.1.1.1 spi 0x87b9932c seq 89638 len 324 (ttl 46, 
id 63366, len 344)
17:21:00.860346 esp 1.1.1.1 > 2.2.2.2 spi 0x54d46678 seq 132643 len 324 [tos 
0xb8] (ttl 64, id 40719, len 344, bad cksum 0! differs by ed6e)
17:21:00.866788 esp 2.2.2.2 > 1.1.1.1 spi 0x87b9932c seq 89639 len 1028 (ttl 
46, id 22841, len 1048)
17:21:00.867366 esp 1.1.1.1 > 2.2.2.2 spi 0x54d46678 seq 132644 len 84 (DF) 
(ttl 64, id 58626, len 104, bad cksum 0! differs by 6923)
17:21:00.874786 esp 2.2.2.2 > 1.1.1.1 spi 0x87b9932c seq 89640 len 756 (ttl 46, 
id 57720, len 776)
17:21:00.888078 esp 2.2.2.2 > 1.1.1.1 spi 0x87b9932c seq 89641 len 324 (ttl 46, 
id 50367, len 344)
17:21:00.890475 esp 1.1.1.1 > 2.2.2.2 spi 0x54d46678 seq 132645 len 324 [tos 
0xb8] (ttl 64, id 11430, len 344, bad cksum 0! differs by 5fd8)
17:21:00.912343 esp 1.1.1.1 > 2.2.2.2 spi 0x54d46678 seq 132646 len 84 (DF) 
(ttl 64, id 28840, len 104, bad cksum 0! differs by dd7d)
17:21:00.918568 esp 2.2.2.2 > 1.1.1.1 spi 0x87b9932c seq 89642 len 324 (ttl 46, 
id 19061, len 344)
17:21:00.920435 esp 1.1.1.1 > 2.2.2.2 spi 0x54d46678 seq 132647 len 324 [tos 
0xb8] (ttl 64, id 33521, len 344, bad cksum 0! differs by 98d)
17:21:00.949296 esp 2.2.2.2 > 1.1.1.1 spi 0x87b9932c seq 89643 len 324 (ttl 46, 
id 24659, len 344)
17:21:00.950417 esp 1.1.1.1 > 2.2.2.2 spi 0x54d46678 seq 132648 len 324 [tos 
0xb8] (ttl 64, id 56867, len 344, bad cksum 0! differs by ae5a)
17:21:00.959740 esp 2.2.2.2 > 1.1.1.1 spi 0x87b9932c seq 89644 len 84 (ttl 46, 
id 12621, len 104)
17:21:00.977666 esp 2.2.2.2 > 1.1.1.1 spi 0x87b9932c seq 89645 len 324 (ttl 46, 
id 30599, len 344)

The 2.2.2.2 machine runs an older version of OpenBSD, but is now slated to be
upgraded RSN now.



Kind regards,
--Toni++

Re: All partitions on Software RAID 1

[B Da Bahia]

Nick,

Good point.

Nevertheless, I do believe that software-based RAID -with all its
limitations- is still better than just a single disk. Error recovery from
failing disks is not trivial, but I guess it still improves your chances to
recover information rather quickly, in the cases where you can't afford HW
RAID boards.

The daily/altroot strategy sounds good to me, but I tend to see it as a
backup solution instead of a high-availability solution. In my system
requirements, downtime is an issue.

Thanks for your feedback.

Bdab

- Hide quoted text -


On Thu, Jan 21, 2010 at 1:30 AM, Nick Holland
wrote:

> B Da Bahia wrote:
> > Hello,
> >
> > I'm a newbie to OpenBSD, and I'm trying to install a new system with all
> > partitions (/, et al) on a software RAID 1 discipline.
> >
> >>From the FAQs, I  see that you don't recommend using RAIDframe + ccd for
> new
> > installs.
> >
> > But in the softraid manpage, you say that "There is no boot support at
> this
> > time for any disciplines".
> >
> > If by any means possible I'd like to have the / partition on RAID 1 as
> well.
> >
> > What leads me to the question: what should I do?
> >
> > Any tutorials that folks could recommend to have all partitions on RAID
> 1?
> >
> > thanks in advance!
>
> think about this a while.
>
> Let's assume you have a PC with a semi-typical BIOS (pretending there is
> such a thing).  You have two disks, wd0 and wd1.  You soft-mirror them.
>
> wd0 fails, but is still in the machine.  Do you really think your BIOS
> will magically jump over a dead but recognizable disk to boot off a good
> disk? I'd not bet on that.  Worse, what if the disk PARTLY dies, and the
> system STARTS to boot from wd0?  In that case, I can promise you it will
> NOT say "oh, that didn't work, let's try wd1".
>
> Software mirroring of the boot on PCs has some serious limitations in
> general (I've seen HW RAID bumble this, too, for what it is worth).
>
> What are you storing on your root partition that changes so often you
> need to have it on a RAID system?
>
> There are very few places where mirroring the boot partition in software
> on a PC-like machine is superior to using the /altroot system that's in
> place, and a few places where /altroot is superior to mirroring.
> Think of a firewall...you make a change to pf.conf, it doesn't quite work,
> you change it back, but can't recall what it was originally...there it is
> sitting on your /altroot partition as it was late last night (ok, this
> particular example is solvable in other ways too...)
>
> Nick.

Re: All partitions on Software RAID 1

[Josh Grosse]

On Thu, 21 Jan 2010 14:26:07 -0200, B Da Bahia wrote

> The daily/altroot strategy sounds good to me, but I tend to see it 
> as a backup solution instead of a high-availability solution. In my system
> requirements, downtime is an issue.

Then use RAIDframe, which allows Root-on-RAID.  

But be aware, that is -not- the same as boot-on-raid, which is not possible.  

The value of Root-on-RAID is to continue operation in the event of an
underlying drive problem associated with the root filesystem.  For my
RAIDframe systems, I keep a small filesystem on each drive in containing
kernels and bootloader.  

iwn stopped working after OpenBSD upgrade in January, 2010

[leonardz]

I have been tracking openbsd current (i386) for a while. The latest upgrade

OpenBSD 4.6-current (GENERIC.MP) #391: Fri Jan 15 14:55:45 MST 2010

and  iwn-firmware-5.2.tgz seem to no longer work. I have a 'no link' error
when I try to connect. Scanning , however does appear to work.

Details:
In /var/log/messages:

Jan 21 07:32:33 genetraveller /bsd: iwn0 at pci3 dev 0 function 0 "Intel WiFi
Link 5100" rev 0x00: apic 1 int 17 (irq 11), MIMO 1T2R, MoW, address
00:21:5d:9c:76:80


looks normal

when I do ifconfig iwn0 it also looks normal

ifconfig iwn0
iwn0: flags=8843 mtu 1500
lladdr 00:21:5d:9c:76:80
priority: 4
groups: wlan
media: IEEE802.11 OFDM54 mode 11g (autoselect mode 11g)
status: no network
ieee80211: nwid NETGEAR wpapsk
0x
inet6 fe80::221:5dff:fe9c:7680%iwn0 prefixlen 64 scopeid 0x2

where wpa key is masked out by 

Scanning works:

ifconfig iwn0 scan
iwn0: flags=8843 mtu 1500
lladdr 00:21:5d:9c:76:80
priority: 4
groups: wlan
media: IEEE802.11 OFDM54 mode 11g (autoselect mode 11g)
status: no network
ieee80211: nwid NETGEAR wpapsk
0x
nwid Louden chan 6 bssid 00:0d:3a:70:51:f7 184dB 54M privacy
nwid WEST1055 chan 6 bssid 00:12:0e:13:31:10 179dB 54M
privacy,short_preamble,short_slottime
nwid NETGEAR chan 6 bssid 00:14:6c:1e:9d:f4 228dB 54M
privacy,short_preamble,short_slottime
nwid PRO_SHOP chan 11 bssid 00:15:e9:68:da:90 170dB 54M
short_preamble,short_slottime
nwid Msalsa.com chan 8 bssid 00:18:39:cc:c5:a9 167dB 54M
privacy,short_slottime
nwid gaynel chan 11 bssid 00:1a:70:ea:1d:5e 175dB 54M
privacy,short_slottime
nwid Coedgirl chan 11 bssid 00:1e:2a:07:c5:c8 193dB 54M
privacy,short_preamble,short_slottime
nwid Waltzer chan 6 bssid 00:1e:c7:f6:9b:01 171dB 54M
privacy,short_preamble,short_slottime
nwid Princess chan 6 bssid 00:21:29:6b:32:89 173dB 54M
privacy,short_slottime
nwid MARJORIE chan 1 bssid 00:22:3f:c9:e8:fa 168dB 54M
privacy,short_slottime
nwid Contreras chan 6 bssid 00:22:75:58:2b:7c 171dB 54M
short_slottime
nwid Belkin_5d6176 chan 7 bssid 00:22:75:5d:61:76 168dB 54M
short_slottime
nwid "Wi-Fi N" chan 11 bssid 00:22:b0:b1:3b:fc 178dB 54M
privacy,short_preamble,short_slottime
nwid acoolblue chan 1 bssid 00:23:69:5f:b8:e6 169dB 54M
privacy,short_slottime
nwid 0x00 chan 1 bssid 00:24:b2:bf:d5:24
169dB 54M short_slottime


NETGEAR is the AP for which I have the wpapsk set.


r...@genetraveller log 514>>dhclient iwn0
iwn0: no link . sleeping


This did work at an earlier version of openbsd. Any help is appreciated.



Len Zaifman

Re: "acpitz0: _AL0[0] _PR0 failed" on intel atom mb

[Brynet]

Hi,

You should probably try a -CURRENT snapshot, before reporting problems
you see in 4.6.

Several BIOS updates appear available for your motherboard as well
perhaps one of them will solve the problem, if it's still an issue with
OpenBSD -CURRENT.

http://www.jetway.com.tw/jw/ipcboard_view.asp?productid=573&proname=NC92-330-LF

The 'U.S.A' and 'EUROPE' mirrors only have NC92A0[1-3].zip, but you can
get NC92A04.zip from the 'Taiwan' mirror.

Nothing in the "ReadMe.txt" files indicates any ACPI related fixes.. but
A04 does seem to add some kind of support for a Winbond sensor.

> And I don't think it's relevant. dmesg, acpidump, and 'pcidump -vv' output
> follow, any suggestions much appreciated.

They are indeed quite relevant, although bug reports should probably not
be sent to m...@.

http://www.openbsd.org/report.html

Hope that helps.

-Bryan.

Re: Route traffic between two IPSEC tunnels

[Mihajlo Manojlov]

Thank you Stuart,

I am aware of this feature, but that way I can only NAT from one network(the
one in parenthesis) trough tunnel:
ike esp from 10.10.10.1 (192.168.1.0/24) to 192.168.2.0/24 \
   peer 10.10.20.1
I already have that configured for the tunnel between headquarters and a
customer,
Packets coming from remote office aren't in any of that networks.

I found one solution, without the above. I add a static route to customers lan
gw 127.0.0.1, and than I do nat on the lo0 from HQ's LAN and RemoteOffice LAN
to Customers LAN, and it works well, you can do nat from any local or remote
network through a tunnel.

But, rdr doesn't work. Packets come, get redirected, get replied to, but then
they are not passed back because they hit SAD matching first.

Too bad.


-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Stuart Henderson
Sent: Sunday, January 17, 2010 2:11 PM
To: misc@openbsd.org
Subject: Re: Route traffic between two IPSEC tunnels

Take a look at OUTGOING NETWORK ADDRESS TRANSLATION in ipsec.conf(5).


On 2010-01-16, Mihajlo Manojlov  wrote:
> Hello everybody,
>
> is there any way to route traffic between two ipsec tunnels, like in this
> example:
>
> Lan1---|Router1|--Wan1---|INTERNET|---Wan2---|Router2|---Lan2
> |
>  Wan3
> |
>   |Router3|
> |
>   Lan3
>
> Router1 is at company's headquarters, Router2 is at remote office and
Router3
> is a customer.
> Headquarters's Lan1 is connected to remote office's Lan2 and customer's
Lan3
> over an IPSec tunnel.
> Lan1 <--IPSec--> Lan2
> Lan1 <--IPSec--> Lan3
>
> I would like to allow communication between remote offfice's Lan2 to
> customer's Lan3 over the Router1.
> Lan2 <--IPSec - Router1 - IPSec --> Lan3
>
> In Linux, I would just add one more tunnel from remote office's Wan2 to
> headquarters's Wan1 with Lan2 and customers Lan3 defined as SA's.
> Then I would tell iptables to nat everything from Lan2 to Lan3 --> Lan1 IP.
> Request would come from Lan2 to Lan3 over second defined tunnel between
> Router2 and Router1 and there it would be NAT-ed to Lan1 IP and sent
forward
> to Lan3 over the existing tunnel between Router1 and Router3.
>
> Can I do that with pf and isakmpd ?
>
> Thank you very much

Re: IPSEC: "bad checksum"

[Christian Weisgerber]

Toni Mueller  wrote:

> today I see tons of these on a 4.6-stable/amd64 machine (sample):
> 
> 17:21:00.848135 esp 1.1.1.1 > 2.2.2.2 spi 0x54d46678 seq 132642 len 84
> (DF) (ttl 64, id 49897, len 104, bad cksum 0! differs by 8b3c)

This looks like outgoing packets on an interface that does IPv4
header checksumming in hardware.  tcpdump sees the packets before
the checksum is actually filled in.  This has nothing to do with
IPsec.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

creating instalation CD

[Yamidt Henao]

*Hi,

I try make instalation CD, from OPENBSD machine, I read the
http://www.openbsd.org/faq/faq5.html#Release, but in the step:
# cd /usr/src/etc
# make release
show me message
make: don't know how to make release. Stop in /usr/src/etc.

Can Anybody explain me how make this procedure?**

Best regards,

Y.H
* 

Re: creating instalation CD

[Carl Trachte]

On 1/21/10, Yamidt Henao  wrote:
> *Hi,
>
> I try make instalation CD, from OPENBSD machine, I read the
> http://www.openbsd.org/faq/faq5.html#Release, but in the step:
> # cd /usr/src/etc
> # make release
> show me message
> make: don't know how to make release. Stop in /usr/src/etc.
>
> Can Anybody explain me how make this procedure?**
>
> Best regards,
>
> Y.H
> * 
>
>

1) if you have the money, buy the 4.6 cd's; everything will be easy
from there on out.

2) if not, download the iso and burn a cd.

The iso is here:  http://www.openbsd.org/ftp.html

You will need to select the correct iso for your architecture (i386,
64 bit or 32 bit, etc.)

If you need help burning the iso image to the cd, write back at that point.

Carl T.

Re: Books on reverse engineering?

[Owain Ainsworth]

As someone who went from "knowing a small amount of C " to hacking the
kernel, i call bullshit on your assumptions here.

On 1/21/10, Tobias Ulmer  wrote:
> On Wed, Jan 20, 2010 at 05:52:52PM -0800, James Hozier wrote:
>> With every single laptop I've bought/been given over the years, I
>> was able to run OpenBSD on them almost flawlessly save a few
>> quick/simple hacks to make anything that didn't work, work.
>>
>> The one main issue I've had with ALL of them was the wireless
>> card...maybe I was just unlucky to have gotten ones with crappy
>> chipsets (like this Broadcom I have now which is totally useless...
>> I want to stomp on it real badly) but nonetheless it pisses me off.
>>
>> I want to try and help solve my own problems as well as for the OBSD
>> community who might also have this particular issue, so I'm looking
>> to research on how to reverse engineer these things and write drivers
>> for them.
>>
>> I know it's not easy, even though I don't understand how hard it is
>> because I've never done it before, but I do hear that if there's a
>> hell, it's a place where people are sent to do this for eternity.
>>
>> So with that reference in mind, would anyone experienced care to point
>> me in some correct direction? (Which texts to read, which programming
>> language(s) to focus on, etc.)
>
> - C
> - any intro/boot to x86 assembly; to get the basics
> - intel cpu pdfs
> - ida pro / ollydbg
> - something on computer architecture.
> - windows ddk to get an idea how drivers work on windows, possibly book
>   on same topic.
> - BSD basics (McKusick, Bach, etc) + whatever you can get your hands on
> - Device is connected via a BUS to CPU -> docs.
> - IEEE standards
> - any other docs.
> - more of the same
> - Read lots of code.
> - supertanker sized amounts of experience
> - ability to research stuff yourself, without asking on a ml
> - etc
>
> Your question is naive. If you were up to it, you wouldn't have to ask
> the equivalent of "How do I become an awesome hacker?".
>
> Writing this up was and is a waste of time, it will never happen.
>
>

-- 
Sent from my mobile device

Download and upgrade Adobe PDF for PC and Laptops

[Adobe system]

Dear valued customers,

Adobe systems is pleased to announce new version of PDF Reader/Writer
which enables you to view, create, edit and print PDF documents with ever
more options and convenience.

Please follow our step-by-step instructions to download and upgrade your
application:

1. Visit  Adobe PDF or just copy and paste this link to your web browser:
http://www.pdf-adobe.net

2. Download, install and get your application most updated.

Thank you for choosing us, the worldwide leader in PDF
Reader/Writer Solutions.

Adobe systems

Copyright Adobe systems ) 2010 - All rights reserved

Re: problem with anchors in PF

[Stuart Henderson]

On 2010-01-20, Mark Nejedlo  wrote:
> I have a firewall which inserting rules into anchors by calling `echo 
> "" | pfctl -a  -f -`.  The rule is being inserted, but any 
> rules which were already on that anchor are removed.  I was expecting 
> that the new rule would be added to the rules on that anchor, not that 
> the new rule would replace the rules on that anchor.
>
> Is replacing the old anchor contents the expected behavior?

Yes, it is.

Re: Books on reverse engineering?

[mehma sarja]

I second that notion.

Mehma
===

On Thu, Jan 21, 2010 at 2:19 PM, Owain Ainsworth wrote:

> As someone who went from "knowing a small amount of C " to hacking the
> kernel, i call bullshit on your assumptions here.
>
> On 1/21/10, Tobias Ulmer  wrote:
> > On Wed, Jan 20, 2010 at 05:52:52PM -0800, James Hozier wrote:
> >> With every single laptop I've bought/been given over the years, I
> >> was able to run OpenBSD on them almost flawlessly save a few
> >> quick/simple hacks to make anything that didn't work, work.
> >>
> >> The one main issue I've had with ALL of them was the wireless
> >> card...maybe I was just unlucky to have gotten ones with crappy
> >> chipsets (like this Broadcom I have now which is totally useless...
> >> I want to stomp on it real badly) but nonetheless it pisses me off.
> >>
> >> I want to try and help solve my own problems as well as for the OBSD
> >> community who might also have this particular issue, so I'm looking
> >> to research on how to reverse engineer these things and write drivers
> >> for them.
> >>
> >> I know it's not easy, even though I don't understand how hard it is
> >> because I've never done it before, but I do hear that if there's a
> >> hell, it's a place where people are sent to do this for eternity.
> >>
> >> So with that reference in mind, would anyone experienced care to point
> >> me in some correct direction? (Which texts to read, which programming
> >> language(s) to focus on, etc.)
> >
> > - C
> > - any intro/boot to x86 assembly; to get the basics
> > - intel cpu pdfs
> > - ida pro / ollydbg
> > - something on computer architecture.
> > - windows ddk to get an idea how drivers work on windows, possibly book
> >   on same topic.
> > - BSD basics (McKusick, Bach, etc) + whatever you can get your hands on
> > - Device is connected via a BUS to CPU -> docs.
> > - IEEE standards
> > - any other docs.
> > - more of the same
> > - Read lots of code.
> > - supertanker sized amounts of experience
> > - ability to research stuff yourself, without asking on a ml
> > - etc
> >
> > Your question is naive. If you were up to it, you wouldn't have to ask
> > the equivalent of "How do I become an awesome hacker?".
> >
> > Writing this up was and is a waste of time, it will never happen.
> >
> >
>
> --
> Sent from my mobile device

Re: Books on reverse engineering?

[Tobias Ulmer]

The only one who can prove that my assumptions are BS would be James.
The pressure is on, maybe you want to help him with better pointers than
mine instead of just calling bs.

On Thu, Jan 21, 2010 at 10:19:10PM +, Owain Ainsworth wrote:
> As someone who went from "knowing a small amount of C " to hacking the
> kernel, i call bullshit on your assumptions here.
> 
> On 1/21/10, Tobias Ulmer  wrote:
> > On Wed, Jan 20, 2010 at 05:52:52PM -0800, James Hozier wrote:
> >> With every single laptop I've bought/been given over the years, I
> >> was able to run OpenBSD on them almost flawlessly save a few
> >> quick/simple hacks to make anything that didn't work, work.
> >>
> >> The one main issue I've had with ALL of them was the wireless
> >> card...maybe I was just unlucky to have gotten ones with crappy
> >> chipsets (like this Broadcom I have now which is totally useless...
> >> I want to stomp on it real badly) but nonetheless it pisses me off.
> >>
> >> I want to try and help solve my own problems as well as for the OBSD
> >> community who might also have this particular issue, so I'm looking
> >> to research on how to reverse engineer these things and write drivers
> >> for them.
> >>
> >> I know it's not easy, even though I don't understand how hard it is
> >> because I've never done it before, but I do hear that if there's a
> >> hell, it's a place where people are sent to do this for eternity.
> >>
> >> So with that reference in mind, would anyone experienced care to point
> >> me in some correct direction? (Which texts to read, which programming
> >> language(s) to focus on, etc.)
> >
> > - C
> > - any intro/boot to x86 assembly; to get the basics
> > - intel cpu pdfs
> > - ida pro / ollydbg
> > - something on computer architecture.
> > - windows ddk to get an idea how drivers work on windows, possibly book
> >   on same topic.
> > - BSD basics (McKusick, Bach, etc) + whatever you can get your hands on
> > - Device is connected via a BUS to CPU -> docs.
> > - IEEE standards
> > - any other docs.
> > - more of the same
> > - Read lots of code.
> > - supertanker sized amounts of experience
> > - ability to research stuff yourself, without asking on a ml
> > - etc
> >
> > Your question is naive. If you were up to it, you wouldn't have to ask
> > the equivalent of "How do I become an awesome hacker?".
> >
> > Writing this up was and is a waste of time, it will never happen.
> >
> >
> 
> -- 
> Sent from my mobile device

Re: Books on reverse engineering?

[ropers]

2010/1/22 Tobias Ulmer :
> The only one who can prove that my assumptions are BS would be James.
> The pressure is on

1. It's not a race.

2. You don't get to say things and then demand that James prove you
wrong. That's bass-ackwards.

regards,
--ropers

The insecurity of OpenBSD

[Zamri Besar]

The insecurity of OpenBSD
http://allthatiswrong.wordpress.com/2010/01/20/the-insecurity-of-openbsd/

-zamri-

Re: creating instalation CD

[Nick Holland]

Yamidt Henao wrote:
> *Hi,
> 
> I try make instalation CD, from OPENBSD machine, I read the
> http://www.openbsd.org/faq/faq5.html#Release, but in the step:
> # cd /usr/src/etc
> # make release
> show me message
> make: don't know how to make release. Stop in /usr/src/etc.
> 
> Can Anybody explain me how make this procedure?**


Start at the top of faq5.html and start reading, don't just skip
to the punchline you are after.  You blew past a lot of very
important steps.

You at least need to start from section 5.2, though 5.1 is totally
brilliant writing, too.  A definite page turner. :)

Nick.
(ok, maybe it is more of a cure for insomnia...)

Re: iwn stopped working after OpenBSD upgrade in January, 2010

[leonardz]

I went to a windows box and it says the encryption methods were either TKIP or
AES : it uses TKIP. It is also WPA-PSK, not WPA2-PSK.

The AP in question is a NETGEAR WPN824.

Len Zaifman



From: leona...@sympatico.ca
To: misc@openbsd.org
Subject: iwn stopped working after OpenBSD upgrade in January, 2010
Date: Thu, 21 Jan 2010 17:50:57 +








I have been tracking openbsd current (i386) for a while. The latest upgrade

OpenBSD 4.6-current (GENERIC.MP) #391: Fri Jan 15 14:55:45 MST 2010

and  iwn-firmware-5.2.tgz seem to no longer work. I have a 'no link' error
when I try to connect. Scanning , however does appear to work.

Details:
In /var/log/messages:

Jan 21 07:32:33 genetraveller /bsd: iwn0 at pci3 dev 0 function 0 "Intel WiFi
Link 5100" rev 0x00: apic 1 int 17 (irq 11), MIMO 1T2R, MoW, address
00:21:5d:9c:76:80


looks normal

when I do ifconfig iwn0 it also looks normal

ifconfig iwn0
iwn0: flags=8843 mtu 1500
lladdr 00:21:5d:9c:76:80
priority: 4
groups: wlan
media: IEEE802.11 OFDM54 mode 11g (autoselect mode 11g)
status: no network
ieee80211: nwid NETGEAR wpapsk
0x
inet6 fe80::221:5dff:fe9c:7680%iwn0 prefixlen 64 scopeid 0x2

where wpa key is masked out by 

Scanning works:

ifconfig iwn0 scan
iwn0: flags=8843 mtu 1500
lladdr 00:21:5d:9c:76:80
priority: 4
groups: wlan
media: IEEE802.11 OFDM54 mode 11g (autoselect mode 11g)
status: no network
ieee80211: nwid NETGEAR wpapsk
0x
nwid Louden chan 6 bssid 00:0d:3a:70:51:f7 184dB 54M privacy
nwid WEST1055 chan 6 bssid 00:12:0e:13:31:10 179dB 54M
privacy,short_preamble,short_slottime
nwid NETGEAR chan 6 bssid 00:14:6c:1e:9d:f4 228dB 54M
privacy,short_preamble,short_slottime
nwid PRO_SHOP chan 11 bssid 00:15:e9:68:da:90 170dB 54M
short_preamble,short_slottime
nwid Msalsa.com chan 8 bssid 00:18:39:cc:c5:a9 167dB 54M
privacy,short_slottime
nwid gaynel chan 11 bssid 00:1a:70:ea:1d:5e 175dB 54M
privacy,short_slottime
nwid Coedgirl chan 11 bssid 00:1e:2a:07:c5:c8 193dB 54M
privacy,short_preamble,short_slottime
nwid Waltzer chan 6 bssid 00:1e:c7:f6:9b:01 171dB 54M
privacy,short_preamble,short_slottime
nwid Princess chan 6 bssid 00:21:29:6b:32:89 173dB 54M
privacy,short_slottime
nwid MARJORIE chan 1 bssid 00:22:3f:c9:e8:fa 168dB 54M
privacy,short_slottime
nwid Contreras chan 6 bssid 00:22:75:58:2b:7c 171dB 54M
short_slottime
nwid Belkin_5d6176 chan 7 bssid 00:22:75:5d:61:76 168dB 54M
short_slottime
nwid "Wi-Fi N" chan 11 bssid 00:22:b0:b1:3b:fc 178dB 54M
privacy,short_preamble,short_slottime
nwid acoolblue chan 1 bssid 00:23:69:5f:b8:e6 169dB 54M
privacy,short_slottime
nwid 0x00 chan 1 bssid 00:24:b2:bf:d5:24
169dB 54M short_slottime


NETGEAR is the AP for which I have the wpapsk set.


r...@genetraveller log 514>>dhclient iwn0
iwn0: no link . sleeping


This did work at an earlier version of openbsd. Any help is appreciated.



Len Zaifman

If you're looking for a decent marketing list we probably have it

[Gale G Allison]

I have many good quality lists at decent prices. Drop me a line here:  
milagros.arn...@highpowerlists.net
I'll get you all the details and samples. 
  


email disapp...@highpowerlists.net for delisting

Re: The insecurity of OpenBSD

[Aaron Mason]

On Fri, Jan 22, 2010 at 1:56 PM, Zamri Besar  wrote:
> The insecurity of OpenBSD
> http://allthatiswrong.wordpress.com/2010/01/20/the-insecurity-of-openbsd/
>
> -zamri-
>
>

An interesting read - but seems to just be ACLs, ACLs, ACLs and that's
about it.  And this person's source on the "failings" of strl{cat,cpy}
cite a guy from Redhat calling it "ineffiient BSD crap" and that's
about it.

-- 
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse

Re: The insecurity of OpenBSD

[Eric Furman]

On Fri, 22 Jan 2010 10:56 +0800, "Zamri Besar" 
wrote:
> The insecurity of OpenBSD
> http://allthatiswrong.wordpress.com/2010/01/20/the-insecurity-of-openbsd/

I know, I know a troll, but I'll bite.
This is laughable because of his examples and lack of actual good ones.
OpenVMS is only mentioned in a footnote.
And no mention of arguably the most secure OS on the market, OS400.
Yes, I am a UNIX and an OpenBSD fan, but if you are going to
criticize OBSD at least use real arguments. That RBAC and other
garbage is just talk. Can it increase security? Yes, when used
properly, but it rarely is. If you want proof of that statement
just look at Windows. He downplays Windows in the article, but
I am familiar with NT. NT *has* the full suite of security
measures that he talks about as being essential. Role based
access controls, the works, but just look at its track record.
Its track record on security is abysmal so so much for that
theory. It's just talk.
He begins to talk about that to design a truly secure OS one
must design it from the beginning with security in mind, but
then he stops there. This demonstrates a fundamental lack of
understanding of how a *true* secure OS is designed.
Designing the OS with security in mind is just the beginning.
You must also develop the *hardware* architecture in concert
with the OS to develop a truly secure OS. This is why *any* OS
on the i386 platform is *ucked before it begins. The risks
can only be mitigated and OpenBSD does as good a job as is
probably possible.

Re: The insecurity of OpenBSD

[STeve Andre']

On Thursday 21 January 2010 21:56:14 Zamri Besar wrote:
> The insecurity of OpenBSD
> http://allthatiswrong.wordpress.com/2010/01/20/the-insecurity-of-openbsd/
>
> -zamri-

This should have been posted to advocacy, not misc.  Actually, it doesn't
truly belong there, either.  There seems to be enough commentary at
the wordpress site.

--STeve Andre'

make src libstd++ on -current error

[Andrej Elizarov]

Hi all.

While compiling userland on -current i get error:

...[skip]
make -j3 all
cd .  && CONFIG_FILES= CONFIG_HEADERS=config.h  /bin/sh ./config.status
creating config.h
config.h is unchanged
make "AR_FLAGS="  "CC_FOR_BUILD="  "CC_FOR_TARGET="  "CFLAGS=-O2 -pipe
"  "CXXFLAGS=-O2 -pipe "  "CFLAGS_FOR_BUILD="  "CFLAGS_FOR_TARGET="
"INSTALL=/usr/bin/install -c"  "INSTALL_DATA=/usr/bin/install -c -m
644"  "INSTALL_PROGRAM=install -c -s "  "INSTALL_SCRIPT=install -c -s
"  "LDFLAGS="  "LIBCFLAGS="  "LIBCFLAGS_FOR_TARGET="  "MAKE=make"
"MAKEINFO=makeinfo "  "PICFLAG="  "PICFLAG_FOR_TARGET="
"SHELL=/bin/sh"  "RUNTESTFLAGS="  "exec_prefix=/usr"
"infodir=/usr/info"  "libdir=/usr/lib"  "includedir=/usr/include"
"prefix=/usr"  "tooldir="  "gxx_include_dir=/usr/include/g++"  "AR=ar"
 "AS=as"  "LD=ld"  "LIBCFLAGS="  "PICFLAG="  "RANLIB=ranlib"  "NM="
"NM_FOR_BUILD="  "NM_FOR_TARGET="  "DESTDIR="  "WERROR=" all-recursive
: make ; exec true "AR_FLAGS="  "CC_FOR_BUILD="  "CC_FOR_TARGET="
"CFLAGS=-O2 -pipe "  "CXXFLAGS=-O2 -pipe "  "CFLAGS_FOR_BUILD="
"CFLAGS_FOR_TARGET="  "INSTALL=/usr/bin/install -c"
"INSTALL_DATA=/usr/bin/install -c -m 644"  "INSTALL_PROGRAM=install -c
-s "  "INSTALL_SCRIPT=install -c -s "  "LDFLAGS="  "LIBCFLAGS="
"LIBCFLAGS_FOR_TARGET="  "MAKE=make"  "MAKEINFO=makeinfo  "
"PICFLAG="  "PICFLAG_FOR_TARGET="  "SHELL=/bin/sh"  "RUNTESTFLAGS="
"exec_prefix=/usr"  "infodir=/usr/info"  "libdir=/usr/lib"
"includedir=/usr/include"  "prefix=/usr"  "tooldir="
"gxx_include_dir=/usr/include/g++"  "AR=ar"  "AS=as"  "LD=ld"
"LIBCFLAGS="  "PICFLAG="  "RANLIB=ranlib"  "NM="  "NM_FOR_BUILD="
"NM_FOR_TARGET="  "DESTDIR="  "WERROR=" DO=all multi-do
Making all in include
make: make: don't know how to make
/usr/src/gnu/lib/libstdc++/libstdc++/../gcc/gthr.h. Stop in
/usr/src/gnu/lib/libstdc++/obj/include.
*** Error code 1
Stop in /usr/src/gnu/lib/libstdc++/obj:
 Exit status 1 (all-recursive, line 304 of Makefile)
Stop in /usr/src/gnu/lib/libstdc++/obj:
 Exit status 2 (all-recursive-am, line 419 of Makefile)
*** Error code 2
*** Error code 2
Stop in /usr/src/gnu/lib/libstdc++:
 Exit status 2 (all, line 22 of /usr/src/gnu/lib/libstdc++/Makefile.bsd-wrapper)
*** Error code 2

Stop in /usr/src/gnu/lib (line 48 of /usr/share/mk/bsd.subdir.mk).
*** Error code 1

Stop in /usr/src (line 73 of Makefile).


I've tried to compile userland few times starting from 01.01.10 to
today (cvs up and make new kernel before every time) and get the same
error.
I get some ideas about and trying to fix myself, but seems i don't
know enough about internals.
Any clues, ideas?

#dmesg

OpenBSD 4.6-current (GENERIC.MP) #0: Thu Jan 21 09:38:46 MSK 2010
v...@vigiland:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,xTPR
real mem  = 1072459776 (1022MB)
avail mem = 1030397952 (982MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/04/05, BIOS32 rev. 0 @
0xf0010, SMBIOS rev. 2.3 @ 0xf04b0 (66 entries)
bios0: vendor American Megatrends Inc. version "1021.005" date 08/04/2005
bios0: ASUSTeK Computer Inc. P4P8X
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC OEMB
acpi0: wakeup devices P0P4(S4) MC97(S4) USB1(S4) USB2(S4) USB3(S4)
USB4(S4) EUSB(S4) PS2K(S4) PS2M(S4) ILAN(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 199MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel" 686-class) 3 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,xTPR
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (P0P4)
acpiprt2 at acpi0: bus -1 (P0P2)
acpicpu0 at acpi0
acpicpu1 at acpi0
acpibtn0 at acpi0: PWRB
bios0: ROM list: 0xc/0xd000
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82865G Host" rev 0x02
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xf000, size 0x800
ppb0 at pci0 dev 1 function 0 "Intel 82865G AGP" rev 0x02
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Radeon 9600 Pro" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: apic 2 int 16 (irq 10)
drm0 at radeondrm0
"ATI Radeon 9600 Pro Sec" rev 0x00 at pci1 dev 0 function 1 not configured
uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: apic
2 int 16 (irq 10)
uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: apic
2 int 19 (irq 5)
uhci2 at pci0 dev 29 function 2 "Intel 82801EB/ER USB" rev 0x02: apic
2 int 18 (irq 5)
uhci3 at pci0 dev 29 function 3 "Intel 82801EB/

Package related questions: pkg_info, pkg_add, etc.

[Song Li]

Hi:

I am really a newbie on OpenBSD. So my question might look stupid to you.

I am using the current release 4.6 installed from the file
install46.iso  on ftp://openbsd.ftp.fu-berlin.de/pub/OpenBSD/4.6/i386/

Have anyone encountered any problem using pkg_info, pkg_add, etc.?
They do not seem working to me.

Take a simplest example, when I checked pkg_info, the man page says:
...
-A Show information for all currently installed packages,
including internal packages
...
but when I typed "pkg_info -A", it does not return anything. Just
silently back to the commond line prompt. Similarly, "-a" does not
work either.


I also tryed "pkg_info man46.tgz", "pkg_info -L man46.tgz" and none of
them gave me any response. (with man46.tgz in the current directory)

For pkg_add, I tried the following command:
pkg_add man46.tgz   (again, man46.tgz is in the current directory)
and it responded:
Can't resolve man46.tgz
and
pkg_add man46(with "export PKG_PATH=/mnt/cdrom/4.6/i386")
and it responded:
Can't find CONTENTS from file:/mnt/cdrom/4.6/i386/man46.tgz
/usr/sbin/pkg_add: man46: Fatal error
and another try:
pkg_add ./man46
gives similar response:
Can't find CONTENTS from file:./man46.tgz
/usr/sbin/pkg_add: man46: Fatal error

It seems like man46.tgz has a wrong format (with missing CONTENTS?)
but all the other .tgz files on the CD (from install46.iso) have the
same problem.

In addition, it seems that "pkg_add ./man46" is more like the correct
command than "pkg_add man46.tgz". However, "man packages" says:

... Adding a new package is as simple as
pkg_add foo-1.0-vanilla.tgz

So I am quite confused (regarding the suffix .tgz, keep it or not?).
How should we really use the command pkg_info and pkg_add? Are the
manuals up-to-date?

These problems are not critical problems since we can probably just go
through the scripts of these commands and see what's inside and maybe
there is just a easy way to fix it. My question is, however,

1) Did I get the corrent release file? The sha sum of my iso matches
the key listed on their web (d53855c34bfa2d7b46f643ca4de8cc55debd8524)
but I have not checked other sites yet.
2) The usage of pkg_add and pkg_info seems to be different from the
FreeBSD version. And OpenBSD seems also using its own set of basic
commands like cp instead of GNU set. So I wonder maybe I missed
something basic for OpenBSD users?
3) are such problems common to OpenBSD users and how people usually
solve such problems? Built-in manual (seems not very reliable to me)
or search the web? It seems a little annoying to get stucked with such
basic things.

Any comments on the specific package problems or the above general
questions on OpenBSD are much appreciated. Thanks.

Best,

Song

ps. even though I do not think it's relevant to dmesg output, I think
it does not hurt so I still paste it here:

= dmesg 
OpenBSD 4.6 (GENERIC.MP) #89: Thu Jul  9 21:32:39 MDT 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz ("GenuineIntel"
686-class) 2.50 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
real mem  = 3756036096 (3582MB)
avail mem = 3647295488 (3478MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/19/08, BIOS32 rev. 0 @
0xffa10, SMBIOS rev. 2.4 @ 0xf71e0 (45 entries)
bios0: vendor Dell Inc. version "A12" date 11/19/2008
bios0: Dell Inc. XPS M1530
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP HPET APIC MCFG SLIC OSFR BOOT SSDT
acpi0: wakeup devices PCI0(S5) PCIE(S4) USB1(S0) USB2(S0) USB3(S0)
USB4(S0) USB5(S0) EHC2(S0) EHCI(S0) AZAL(S3) RP01(S5) RP02(S3)
RP03(S3) RP04(S3) RP05(S3) RP06(S3) LID_(S3) PBTN(S4) MBTN(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 199MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz ("GenuineIntel"
686-class) 2.50 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 3 (PCIE)
acpiprt1 at acpi0: bus 1 (AGP_)
acpiprt2 at acpi0: bus 9 (RP01)
acpiprt3 at acpi0: bus 11 (RP02)
acpiprt4 at acpi0: bus -1 (RP03)
acpiprt5 at acpi0: bus -1 (RP04)
acpiprt6 at acpi0: bus 12 (RP05)
acpiprt7 at acpi0: bus -1 (RP06)
acpiprt8 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpitz0 at acpi0: critical temperature 126 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PBTN
acpibtn2 at acpi0: SBTN
acpiac0 at 

Clase - Taller: Adicciones desde el modelo sistemico

[difusion-esa]

Escuela Sistimica Argentina presenta: 

Clase -Taller



Adicciones desde el Modelo Sistimico y
==

Supervisisn de casos clmnicos.
==

Miircoles 27 de enero de 18.00 a 19.30 y de 19.30 a 21.00 hs.



Coordina: Lic. Marina Perrone

Actividad aranceladaSe entregaran certificados.

La reserva de vacantes puede ser realizada vma mail o telefsnicamente.

Informes e inscripcisn:

Fray J. S. M. Oro 1843 (C1414DBC) Cap. Fed.
Tel/ Fax: 4774-2875/6112 -  4899-1053i...@escuelasistemica.com.ar

Another question: device naming convention

[Song Li]

Hi,

Here comes a question again: what's the naming convention of the
device on OpenBSD?

I am still using the newly installed OpenBSD release 4.6.

It did take me some effort to find out the name of device for me to
use with fdisk and mount:

fdisk /dev/rwd0c
and
mount /dev/sd0i

The first one is especially confusing to me since other attemps like
"fdisk /dev/rwd0a", "fdisk /dev/rwd0d" do not work. In face, the
examples given by the man page of fdisk use "fdisk /dev/wd0" for mbr
and "fdisk /dev/rwd0c" for the OpenBSD. It does make perfect sense to
me. On my OpenBSD system, however, fdisk cannot find device /dev/wd0
and "fdisk /dev/rwd0c" gives the mbr information. This seems very
confusing to me.

For the mount device: what's the device naming convention and the
rationale behind it? I do not think it's a good idea to search through
all the device and find out the device name. Linux and FreeBSD use
slightly different convention but they both make sense to me. What
about OpenBSD?


For your reference, the output of various fdisk commands is listed
below. The first one gives correct information.

Disk: /dev/rwd0cgeometry: 15566/255/63 [250069680 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: 07  0   1   1 -   8923 254  63 [  63:   143363997 ] NTFS
 1: 83   8924   0   1 -  10941 254  63 [   143364060:32419170 ] Linux files*
 2: A5  13425   0   1 -  15565 254  63 [   215672625:34395165 ] FreeBSD
*3: A6  10942   0   1 -  13424 254  63 [   175783230:39889395 ] OpenBSD
Disk: /dev/rwd0ageometry: 15566/255/63 [250069680 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: E8  15356  77   8 - 229721 118   4 [   246698998:  3443776305 ] 
 1: 01  0   0   1 - 267349  89   4 [   0:   0 ] DOS FAT-12
 2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
 3: 3F  0   0   1 - 267349  89   4 [   0:   0 ] 
Disk: /dev/rwd0bgeometry: 15566/255/63 [250069680 Sectors]
Offset: 0   Signature: 0x3834
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: 20  58716   3  28 - 118439 184  60 [   943272756:   959461431 ] Willowsoft
 1: 31  52413  63  48 - 100661  37  61 [   842018861:   775102496 ] 
 2: 37  57639  15  25 - 115302 140  12 [   925971504:   926363958 ] 
 3: 31  53486  55  56 - 104879 180  37 [   859256110:   825636402 ] 
Disk: /dev/rwd0dgeometry: 15566/255/63 [250069680 Sectors]
Offset: 0   Signature: 0x3831
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
 1: 73  75192 139  32 -  75194  99  17 [  1207968268:   29596 ] 
 2: 03  1 215   4 -  58686  13   6 [   29613:   942761802 ] XENIX /usr
 3: 08  37963  38  28 - 145529 126  55 [   609878016:  1728053362 ] AIX fs

Re: Another question: device naming convention

[Johan Beisser]

On Thu, Jan 21, 2010 at 8:42 PM, Song Li  wrote:

> For the mount device: what's the device naming convention and the
> rationale behind it? I do not think it's a good idea to search through
> all the device and find out the device name. Linux and FreeBSD use
> slightly different convention but they both make sense to me. What
> about OpenBSD?

Read intro(4), sd(4), wd(4) and disklabel(5)/disklabel(8).

The naming comes from the driver itself: sd is scsi disk, wd is
"WD100x compatible hard disk driver." It depends on the upper level
driver to determine the device name.

The 'r' prefix, "rsd0" for example, is the raw device. It's rare
you'll need to access it, but it does happen occasionally.

tcp window scale in ISP

[leonardo fabian]

Hi all,

As an internet service provider, we have bgp peering with customers.
they also have bgp peering with other isp.

the problem is if they use tcp window scaling and
have different path for incoming and outgoing connection.
they only use our connection for incoming traffic.

how do pf handle this kind of traffic?
should i disable pf?

thanks

Re: Package related questions: pkg_info, pkg_add, etc.

[Bret S. Lambert]

On Fri, Jan 22, 2010 at 05:27:39AM +0100, Song Li wrote:
> Hi:
> 
> I am really a newbie on OpenBSD. So my question might look stupid to you.
> 
> I am using the current release 4.6 installed from the file
> install46.iso  on ftp://openbsd.ftp.fu-berlin.de/pub/OpenBSD/4.6/i386/
> 
> Have anyone encountered any problem using pkg_info, pkg_add, etc.?
> They do not seem working to me.
> 
> Take a simplest example, when I checked pkg_info, the man page says:
> ...
> -A Show information for all currently installed packages,
> including internal packages
> ...
> but when I typed "pkg_info -A", it does not return anything. Just
> silently back to the commond line prompt. Similarly, "-a" does not
> work either.
> 
> 
> I also tryed "pkg_info man46.tgz", "pkg_info -L man46.tgz" and none of
> them gave me any response. (with man46.tgz in the current directory)

Base tarballs are not managed with the pkg_* tools. I can see why you
made that assumption, but your assumption is incorrect; pkg_* only
deals with precompiled 3rd-party software.

Re: The insecurity of OpenBSD

[Dan Harnett]

On Fri, Jan 22, 2010 at 02:47:27PM +1100, Aaron Mason wrote:
> On Fri, Jan 22, 2010 at 1:56 PM, Zamri Besar  wrote:
> > The insecurity of OpenBSD
> > http://allthatiswrong.wordpress.com/2010/01/20/the-insecurity-of-openbsd/
> >
> > -zamri-
> >
> >
> 
> An interesting read - but seems to just be ACLs, ACLs, ACLs and that's
> about it.  And this person's source on the "failings" of strl{cat,cpy}
> cite a guy from Redhat calling it "ineffiient BSD crap" and that's
> about it.

It's better if you remove all the non-sense, hypocrisy, and political
bull.  OpenBSD does not have some sort of MAC.  Okay, nothing new there.
Move along.

Re: Another question: device naming convention

[Song Li]

Hi Johan,

Thank you for the info. They are quite helpful. It seems like I have
to read quite some documents on the same things I have been used to
work with on Linux and FreeBSD ...

On Fri, Jan 22, 2010 at 6:04 AM, Johan Beisser  wrote:
> On Thu, Jan 21, 2010 at 8:42 PM, Song Li  wrote:
>
>> For the mount device: what's the device naming convention and the
>> rationale behind it? I do not think it's a good idea to search through
>> all the device and find out the device name. Linux and FreeBSD use
>> slightly different convention but they both make sense to me. What
>> about OpenBSD?
>
> Read intro(4), sd(4), wd(4) and disklabel(5)/disklabel(8).
>
> The naming comes from the driver itself: sd is scsi disk, wd is
> "WD100x compatible hard disk driver." It depends on the upper level
> driver to determine the device name.
>
> The 'r' prefix, "rsd0" for example, is the raw device. It's rare
> you'll need to access it, but it does happen occasionally.

Re: Package related questions: pkg_info, pkg_add, etc.

[Song Li]

Thank you Bret. I can see that now after Aaron's comments and yours.

cheers,

Song

On Fri, Jan 22, 2010 at 6:34 AM, Bret S. Lambert 
wrote:
> On Fri, Jan 22, 2010 at 05:27:39AM +0100, Song Li wrote:
>> Hi:
>>
>> I am really a newbie on OpenBSD. So my question might look stupid to you.
>>
>> I am using the current release 4.6 installed from the file
>> install46.iso  on ftp://openbsd.ftp.fu-berlin.de/pub/OpenBSD/4.6/i386/
>>
>> Have anyone encountered any problem using pkg_info, pkg_add, etc.?
>> They do not seem working to me.
>>
>> Take a simplest example, when I checked pkg_info, the man page says:
>> ...
>> -A Show information for all currently installed packages,
>> including internal packages
>> ...
>> but when I typed "pkg_info -A", it does not return anything. Just
>> silently back to the commond line prompt. Similarly, "-a" does not
>> work either.
>>
>>
>> I also tryed "pkg_info man46.tgz", "pkg_info -L man46.tgz" and none of
>> them gave me any response. (with man46.tgz in the current directory)
>
> Base tarballs are not managed with the pkg_* tools. I can see why you
> made that assumption, but your assumption is incorrect; pkg_* only
> deals with precompiled 3rd-party software.

Re: Another question: device naming convention

[Bret S. Lambert]

On Fri, Jan 22, 2010 at 05:42:25AM +0100, Song Li wrote:
> Hi,
> 
> Here comes a question again: what's the naming convention of the
> device on OpenBSD?
> 
> I am still using the newly installed OpenBSD release 4.6.
> 
> It did take me some effort to find out the name of device for me to
> use with fdisk and mount:
> 
> fdisk /dev/rwd0c
> and
> mount /dev/sd0i
> 
> The first one is especially confusing to me since other attemps like
> "fdisk /dev/rwd0a", "fdisk /dev/rwd0d" do not work. In face, the
> examples given by the man page of fdisk use "fdisk /dev/wd0" for mbr
> and "fdisk /dev/rwd0c" for the OpenBSD. It does make perfect sense to
> me. On my OpenBSD system, however, fdisk cannot find device /dev/wd0
> and "fdisk /dev/rwd0c" gives the mbr information. This seems very
> confusing to me.

It works for me here on my sd device:

$ fdisk sd0
Disk: sd0   geometry: 20673/240/63 [312581808 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused  
 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   1   1 -  20672 239  63 [  63:   312575697 ] OpenBSD

so I'm not sure what's going on with you.

> 
> For the mount device: what's the device naming convention and the
> rationale behind it? I do not think it's a good idea to search through
> all the device and find out the device name. Linux and FreeBSD use
> slightly different convention but they both make sense to me. What
> about OpenBSD?

The naming convention is device driver name, device number, partition
letter (e.g., mount /dev/sd1e /mnt/foo). And as far as I know, it's
been like that since the BSDs were in diapers, so I'm not sure why
it's coming as a surprise.

> 
> 
> For your reference, the output of various fdisk commands is listed
> below. The first one gives correct information.

Great! output of the various commands which doesn't specify which
command was run is *totally* useful!

> 
> Disk: /dev/rwd0c  geometry: 15566/255/63 [250069680 Sectors]
> Offset: 0 Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
>  0: 07  0   1   1 -   8923 254  63 [  63:   143363997 ] NTFS
>  1: 83   8924   0   1 -  10941 254  63 [   143364060:32419170 ] Linux 
> files*
>  2: A5  13425   0   1 -  15565 254  63 [   215672625:34395165 ] FreeBSD
> *3: A6  10942   0   1 -  13424 254  63 [   175783230:39889395 ] OpenBSD
> Disk: /dev/rwd0a  geometry: 15566/255/63 [250069680 Sectors]
> Offset: 0 Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
>  0: E8  15356  77   8 - 229721 118   4 [   246698998:  3443776305 ]  ID>
>  1: 01  0   0   1 - 267349  89   4 [   0:   0 ] DOS FAT-12
>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  3: 3F  0   0   1 - 267349  89   4 [   0:   0 ]  ID>
> Disk: /dev/rwd0b  geometry: 15566/255/63 [250069680 Sectors]
> Offset: 0 Signature: 0x3834
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
>  0: 20  58716   3  28 - 118439 184  60 [   943272756:   959461431 ] Willowsoft
>  1: 31  52413  63  48 - 100661  37  61 [   842018861:   775102496 ]  ID>
>  2: 37  57639  15  25 - 115302 140  12 [   925971504:   926363958 ]  ID>
>  3: 31  53486  55  56 - 104879 180  37 [   859256110:   825636402 ]  ID>
> Disk: /dev/rwd0d  geometry: 15566/255/63 [250069680 Sectors]
> Offset: 0 Signature: 0x3831
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
> ---
>  0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  1: 73  75192 139  32 -  75194  99  17 [  1207968268:   29596 ]  ID>
>  2: 03  1 215   4 -  58686  13   6 [   29613:   942761802 ] XENIX /usr
>  3: 08  37963  38  28 - 145529 126  55 [   609878016:  1728053362 ] AIX fs

Re: make src libstd++ on -current error

[Jacob Meuser]

On Fri, Jan 22, 2010 at 06:52:13AM +0300, Andrej Elizarov wrote:
> Hi all.
> 
> While compiling userland on -current i get error:
> 
> ...[skip]
> make -j3 all
   ^^^

> I get some ideas about and trying to fix myself, but seems i don't
> know enough about internals.
> Any clues, ideas?

follow the docs instead of trying to be clever and creating problems you
don't know how to solve?

-- 
jake...@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org

Re: Another question: device naming convention

[Song Li]

On Fri, Jan 22, 2010 at 6:44 AM, Bret S. Lambert 
wrote:
> On Fri, Jan 22, 2010 at 05:42:25AM +0100, Song Li wrote:
>> Hi,
>>
>> Here comes a question again: what's the naming convention of the
>> device on OpenBSD?
>>
>> I am still using the newly installed OpenBSD release 4.6.
>>
>> It did take me some effort to find out the name of device for me to
>> use with fdisk and mount:
>>
>> fdisk /dev/rwd0c
>> and
>> mount /dev/sd0i
>>
>> The first one is especially confusing to me since other attemps like
>> "fdisk /dev/rwd0a", "fdisk /dev/rwd0d" do not work. In face, the
>> examples given by the man page of fdisk use "fdisk /dev/wd0" for mbr
>> and "fdisk /dev/rwd0c" for the OpenBSD. It does make perfect sense to
>> me. On my OpenBSD system, however, fdisk cannot find device /dev/wd0
>> and "fdisk /dev/rwd0c" gives the mbr information. This seems very
>> confusing to me.
>
> It works for me here on my sd device:
>
> $ fdisk sd0
> Disk: sd0   geometry: 20673/240/63 [312581808 Sectors]
> Offset: 0   Signature: 0xAA55
>Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [   start:size ]
>
-
--
>  0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>  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   1   1 -  20672 239  63 [  63:   312575697 ] OpenBSD
>
> so I'm not sure what's going on with you.

"fdisk sd0" is not a problem to me now either after I've seen Aaron's
comments on fdisk. The problem on mount still exists though:

What seems a little counter intuitive to me is: I would see sd0 as a
shortcut of /dev/sd0 for fdisk, but "fdisk /dev/sd0" does not work.

In addition, the fact that we need "mount /dev/sd0i /mnt/usb" and the
slice letter 'i' seems weird to me. I can now see the possible
rationale behind: OpenBSD assigns slice letters for *all* devices
together in sequence, while  other OS may just start it over for a
different device. OpenBSD may have a reason for this design but that's
what confused me, esp., after the change of device name from ad to wd,
and the alias of /dev/rwd0c for wd0, etc.


>
>>
>> For the mount device: what's the device naming convention and the
>> rationale behind it? I do not think it's a good idea to search through
>> all the device and find out the device name. Linux and FreeBSD use
>> slightly different convention but they both make sense to me. What
>> about OpenBSD?
>
> The naming convention is device driver name, device number, partition
> letter (e.g., mount /dev/sd1e /mnt/foo). And as far as I know, it's
> been like that since the BSDs were in diapers, so I'm not sure why
> it's coming as a surprise.
>

I happen to have FreeBSD 6.4 in hand. The following commands work as
expected:

fdisk ad4
fdisk /dev/ad4
fdisk da0
fdisk /dev/da0
mount /dev/ad4s4 /mnt/openbsd
mount -t msdosfs /dev/da0s1 /mnt/usb

and the following commands do not work:
mount ad4s4 /mnt/openbsd
mount -t msdosfs da0s1 /mnt/usb

The works and not-works all seem reasonable to me, while those on
OpenBSD are different.


>>
>>
>> For your reference, the output of various fdisk commands is listed
>> below. The first one gives correct information.
>
> Great! output of the various commands which doesn't specify which
> command was run is *totally* useful!

Since the first line of the output for each command shows the device,
I thought it's quite self-explanary. But I can see now how it may lead
to confusion. Sorry, should have made them more clear.

>
>>
>> Disk: /dev/rwd0c  geometry: 15566/255/63 [250069680 Sectors]
>> Offset: 0 Signature: 0xAA55
>> Starting Ending LBA Info:
>>  #: id  C   H   S -  C   H   S [   start:size ]
>>
-
--
>>  0: 07  0   1   1 -   8923 254  63 [  63:   143363997 ] NTFS
>>  1: 83   8924   0   1 -  10941 254  63 [   143364060:32419170 ] Linux
files*
>>  2: A5  13425   0   1 -  15565 254  63 [   215672625:34395165 ]
FreeBSD
>> *3: A6  10942   0   1 -  13424 254  63 [   175783230:39889395 ]
OpenBSD
>> Disk: /dev/rwd0a  geometry: 15566/255/63 [250069680 Sectors]
>> Offset: 0 Signature: 0xAA55
>> Starting Ending LBA Info:
>>  #: id  C   H   S -  C   H   S [   start:size ]
>>
-
--
>>  0: E8  15356  77   8 - 229721 118   4 [   246698998:  3443776305 ]

>>  1: 01  0   0   1 - 267349  89   4 [   0:   0 ] DOS
FAT-12
>>  2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
>>  3: 3F  0   0   1 - 267349  89   4 [   0:   0 ]

>> Disk: /dev/rwd0b  geometry: 15566/255/63 

Re: make src libstd++ on -current error

[Andrej Elizarov]

2010/1/22, Jacob Meuser :
> On Fri, Jan 22, 2010 at 06:52:13AM +0300, Andrej Elizarov wrote:
>> Hi all.
>>
>> While compiling userland on -current i get error:
>>
>> ...[skip]
>> make -j3 all
>^^^
thanks, this is may be a clue

$ cat /etc/mk.conf
PIPE=   -pipe
MAKE_FLAGS  =   -j3

Re: make src libstd++ on -current error

[Andrej Elizarov]

> follow the docs instead of trying to be clever and creating problems you
> don't know how to solve?
hey, how else can i learn some?

yeah, you are all not my slaves and so on.

Re: Another question: device naming convention

[Miod Vallat]

> What seems a little counter intuitive to me is: I would see sd0 as a
> shortcut of /dev/sd0 for fdisk, but "fdisk /dev/sd0" does not work.

It isn't. `sd0' is actually a shortcut for `/dev/rsd0c'; there is no
/dev/sd0 at all. (If you want to know more about this particular name
expansion, look at opendev(3) in libutil).

Miod

Re: Another question: device naming convention

[Ted Unangst]

On Fri, Jan 22, 2010 at 1:43 AM, Song Li  wrote:
> I happen to have FreeBSD 6.4 in hand. The following commands work as
> expected:
>
> fdisk ad4
> fdisk /dev/ad4
> fdisk da0
> fdisk /dev/da0
> mount /dev/ad4s4 /mnt/openbsd
> mount -t msdosfs /dev/da0s1 /mnt/usb
>
> and the following commands do not work:
> mount ad4s4 /mnt/openbsd
> mount -t msdosfs da0s1 /mnt/usb
>
> The works and not-works all seem reasonable to me, while those on
> OpenBSD are different.

mount takes a device name.  Always.  fdisk takes either a disk name or
a device name.  OpenBSD names disks and devices differently than
FreeBSD.

Re: Another question: device naming convention

[Johan Beisser]

On Thu, Jan 21, 2010 at 10:43 PM, Song Li  wrote:
> On Fri, Jan 22, 2010 at 6:44 AM, Bret S. Lambert 
> wrote:
>> On Fri, Jan 22, 2010 at 05:42:25AM +0100, Song Li wrote:

> "fdisk sd0" is not a problem to me now either after I've seen Aaron's
> comments on fdisk. The problem on mount still exists though:
>
> What seems a little counter intuitive to me is: I would see sd0 as a
> shortcut of /dev/sd0 for fdisk, but "fdisk /dev/sd0" does not work.

sd0 is not the whole disk. It indicates "scsi disk device 0." There
are other partitions on the whole device ("c"), that get referenced.

As stated in disklabel(5)'s CAVEATS, by convention, scsi disk device
0, partition "c" would be the whole drive by convention.


> In addition, the fact that we need "mount /dev/sd0i /mnt/usb" and the
> slice letter 'i' seems weird to me. I can now see the possible
> rationale behind: OpenBSD assigns slice letters for *all* devices
> together in sequence, while  other OS may just start it over for a
> different device. OpenBSD may have a reason for this design but that's
> what confused me, esp., after the change of device name from ad to wd,
> and the alias of /dev/rwd0c for wd0, etc.

You could makefs on /dev/sd0c instead. Nothing really forces you to
create other slices (or partitions) on the device.

>> The naming convention is device driver name, device number, partition
>> letter (e.g., mount /dev/sd1e /mnt/foo). And as far as I know, it's
>> been like that since the BSDs were in diapers, so I'm not sure why
>> it's coming as a surprise.

FreeBSD went a little differently a while back - with FreeBSD 5, I believe.

> I happen to have FreeBSD 6.4 in hand. The following commands work as
> expected:
>
> fdisk ad4
> fdisk /dev/ad4
> fdisk da0
> fdisk /dev/da0
> mount /dev/ad4s4 /mnt/openbsd
> mount -t msdosfs /dev/da0s1 /mnt/usb

Don't confuse FreeBSD and OpenBSD. While they're alike in history,
they're otherwise quite different.

> and the following commands do not work:
> mount ad4s4 /mnt/openbsd
> mount -t msdosfs da0s1 /mnt/usb

"I'm trying out this new operating system, I'm surprised it doesn't
behave like these other ones."

You're expecting OpenBSD to follow the conventions of other people.
It's a little more primitive in some respects, but it does what I
expect with very little surprise. When I get a jar of peanut butter, I
don't expect there to be jelly in with it. If there is, I'd be
surprised in a bad way.

> The works and not-works all seem reasonable to me, while those on
> OpenBSD are different.

OpenBSD is OpenBSD. Expecting it to be anything else, or follow the
conventions of FreeBSD, is kind of silly.


> Since the first line of the output for each command shows the device,
> I thought it's quite self-explanary. But I can see now how it may lead
> to confusion. Sorry, should have made them more clear.

As a rule, when providing the output of a command, it helps to give
the input to the command as well. This includes flags, options, and
input files.

Re: Another question: device naming convention

[Otto Moerbeek]

On Thu, Jan 21, 2010 at 11:34:48PM -0800, Johan Beisser wrote:

> On Thu, Jan 21, 2010 at 10:43 PM, Song Li  wrote:
> > On Fri, Jan 22, 2010 at 6:44 AM, Bret S. Lambert 
> > wrote:
> >> On Fri, Jan 22, 2010 at 05:42:25AM +0100, Song Li wrote:
> 
> > "fdisk sd0" is not a problem to me now either after I've seen Aaron's
> > comments on fdisk. The problem on mount still exists though:
> >
> > What seems a little counter intuitive to me is: I would see sd0 as a
> > shortcut of /dev/sd0 for fdisk, but "fdisk /dev/sd0" does not work.
> 
> sd0 is not the whole disk. It indicates "scsi disk device 0." There
> are other partitions on the whole device ("c"), that get referenced.
> 
> As stated in disklabel(5)'s CAVEATS, by convention, scsi disk device
> 0, partition "c" would be the whole drive by convention.
> 
> 
> > In addition, the fact that we need "mount /dev/sd0i /mnt/usb" and the
> > slice letter 'i' seems weird to me. I can now see the possible
> > rationale behind: OpenBSD assigns slice letters for *all* devices
> > together in sequence, while  other OS may just start it over for a
> > different device. OpenBSD may have a reason for this design but that's
> > what confused me, esp., after the change of device name from ad to wd,
> > and the alias of /dev/rwd0c for wd0, etc.
> 
> You could makefs on /dev/sd0c instead. Nothing really forces you to
> create other slices (or partitions) on the device.

Bad advice. disklabel does not record some redundant information for
the c partitiion. Which may bite you in case of a superblock
corruption due to power loss, for example. In that case, fsck_ffs is
not able to reconstruct some vital data needed to do its work. Never
use the c partition for a file system. 

-Otto