On Thu, Oct 29, 2009 at 01:08, Theo de Raadt dera...@cvs.openbsd.org wrote:
I am going to revisit this.
I do believe i386/amd64 RAMDISKs are destined to more or
less mainstream hardware and ISA CGA, MDA, EGA, HGA
stuff isn't there anymore.
So on i386 RAMDISK (like amd64 one), I suggest to
On Thu, Oct 29, 2009 at 01:08, Theo de Raadt dera...@cvs.openbsd.org wrote:
I am going to revisit this.
I do believe i386/amd64 RAMDISKs are destined to more or
less mainstream hardware and ISA CGA, MDA, EGA, HGA
stuff isn't there anymore.
So on i386 RAMDISK (like amd64 one), I
On Thu, Oct 29, 2009 at 09:58, Theo de Raadt dera...@cvs.openbsd.org wrote:
i386 arch supports hardware starting from 80486. I recall
these old good days and all my machines (386SX and up)
was v...@isa (Trident and Currus Logic). 10+ years ago.
I understand dmesgs are somewhat private, but
[IMAGE]
LEGGI LA VERSIONE ITALIANA | READ ENGLISH VERSION
ENGLISH
[IMAGE]Huge success and interest around the newly-born, totally custom
JYI64RS, created by Jacaroni Yacht International. Also at the Genoa's
49th International Boat Show â after her September presentation at
Cannes' Festival de
On Thu, 29 Oct 2009, Theo de Raadt wrote:
I can't control when people submit dmesg's to dm...@openbsd.org
How often should one re-send dmesglog? After new, perhaps exotic hardware
has been added (not configured ones)? Upgraded to a new release? What
about if I update frequently using
I can't control when people submit dmesg's to dm...@openbsd.org
How often should one re-send dmesglog? After new, perhaps exotic hardware
has been added (not configured ones)? Upgraded to a new release? What
about if I update frequently using -current snaps, is there any harm in
sending
If you're updating frequently using current - there's no harm in
sending one every time you upgrade.
2009/10/29 Antti Harri i...@openbsd.fi:
On Thu, 29 Oct 2009, Theo de Raadt wrote:
I can't control when people submit dmesg's to dm...@openbsd.org
How often should one re-send dmesglog? After
