| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2011-03-14 | unify a chunk | Theo de Raadt | |
| 2010-10-18 | Place a smaller spwd.db onto the install media. Be consistant with the naming | Theo de Raadt | |
| of the "additional" list files (for architectures which split the list) Then... cleanup some TZ which it is clear should not have been placed onto certain media which don't have the space for them. | |||
| 2010-04-03 | Use hw.product sysctl to tell whether we are installing on a Gdium Liberty | Miod Vallat | |
| system, or something else. Derive the fdisk instructions in `use the whole disk for OpenBSD' from this knowledge, and set up a 32MB ext2fs partition on Gdium, and the 1MB elsewhere (as was already been done). On Gdium, format this partition in fancy mode (-O 1) and 4KB blocks, so that PMON has a chance to load files larger than 4MB (such as bsd.rd) without failing in a pathetic way, and also copy the kernel image to the ext2fs partition after the installation has completed. Note that, apart from creating a larger ext2fs partition on Gdium, there should be no need for this. Unfortunately, since regular PMON does not have ext2fs code, Lemote wrote its own code to access ext2 filesystems. Saying that this code is full of shortcomings and bugs would be an understatement. What is worse is that this code has been written by people with no knowledge (or even insight) of how error conditions ought to be handled, and their ext2fs code will happily abort a read upon error with no error; if one does not compare the final read size to the file size obtained by stat(), there is no way to figure out that the read has been aborted. Of course since regular (upstream) PMON code is written correctly, it does not expect this, so it is easy to end up with PMON not loading a kernel image completely, yet proceeding happily to transfer control to this broken image. I guess the morale behind this is that system software is too difficult to get done correctly, to be done by hardware people. | |||
| 2010-03-31 | put date(1) onto the media, it fits | Theo de Raadt | |
| 2010-03-08 | now that fsck_ext2fs is repaired wrt small filesystems, remove | Otto Moerbeek | |
| redundant comment | |||
| 2010-02-19 | less verbose in congrats text | Otto Moerbeek | |
| 2010-02-18 | -q for newfs | Otto Moerbeek | |
| 2010-02-18 | loongson install procedure, using a newly created small ext2 partition (or an | Otto Moerbeek | |
| existing one) to install the bootloader on. | |||
| 2010-02-18 | built miniroot | Otto Moerbeek | |
| 2010-02-18 | fsck_ext2fs is not reliable on small filesystems, so remove -f for now | Otto Moerbeek | |
| 2010-02-17 | Put /sbin/kbd on the ramdisk, as Gdium may have non-US keyboards. | Miod Vallat | |
| 2010-02-16 | build an image of an ext2 fs that can be dd'ed to an usb stick | Otto Moerbeek | |
| 2010-02-12 | do not build cd image; lemote pmon's are too braindead to boot from it | Otto Moerbeek | |
| 2010-02-09 | mount_ext2fs and ral firmware on the ramdisk. | Miod Vallat | |
| 2010-02-07 | build iso | Otto Moerbeek | |
| 2010-02-06 | no bsd.bin here as well | Otto Moerbeek | |
| 2010-02-04 | no need for bsd.bin | Otto Moerbeek | |
| 2010-01-31 | initial ramdisk stuff, produces a working bsd.rd | Otto Moerbeek | |
 |
index : src | |
| OpenBSD base system |
| summaryrefslogtreecommitdiff |