Am 22.09.2016 um 04:47 schrieb Philip Guenther:
> Backing up to the beginning...
>
> On Wed, Sep 21, 2016 at 2:39 PM, Peer Janssen wrote:
>> I updated an alix.3c3 box from OpenBSD 4.6 release to 6.0 release
>> recently via bsd.rd install kernel.
>> This went very smooth
Am 29.09.2016 um 14:05 schrieb Stuart Henderson:
> On 2016-09-28, Peer Janssen wrote:
>> # tftpd -d /tftpboot
>>
>> tftpd: 192.168.0.81: read request for 'pxeboot'
>> tftpd: 192.168.0.81: read request for 'pxeboot'
>> tftpd: 192.168.0.81: re
ntributing their
comparative working or failing cases!
Peer
Am 02.10.2016 um 17:54 schrieb Peer Janssen:
> Goal: Upgrade a working soekris net4801 from OpenBSD 4.6 to 6.0.
>
> First I copied the complete 256 MB SiliconDrive CF-Disk to a newer
> SanDisk 8 GB Ultra one and rebootet, which wo
Am 02.10.2016 um 21:24 schrieb Paul Suh:
>> On Oct 2, 2016, at 3:06 PM, Peer Janssen wrote:
>>
>> Now I reinstalled on another CF-Disk (4GB Transcend) with another method
>> (miniboot.fs), this went through and first-rebooted just fine.
>>
>> But now halti
alting directly after
logging in.
Peer
Am 02.10.2016 um 17:54 schrieb Peer Janssen:
> Goal: Upgrade a working soekris net4801 from OpenBSD 4.6 to 6.0.
>
> First I copied the complete 256 MB SiliconDrive CF-Disk to a newer
> SanDisk 8 GB Ultra one and rebootet, which worked smoothly and fi
indeed the unaltered one from the other
i386 OpenBSD 6.0 machine, and these
https://marc.info/?l=openbsd-misc&m=144242763106881&w=2 hints were taken
into account.
Is a system like the soekris net4801 not supported any more? Or is there
something I can do to install the new version on it?
Peer
--
Peer Janssen - p...@pjk.de
Am 28.09.2016 um 13:27 schrieb Solène Rapenne:
> Le 2016-09-28 12:45, Peer Janssen a écrit :
>> TFTP pxeboot requests:
>>
>> 12:15:45.064076 192.168.0.81.2070 > alix.fritz.box.tftp: 24 RRQ
>> "pxeboot"
>> : 4500 0034 0002 1411 24ea c0a8 00
Am 28.09.2016 um 11:33 schrieb Peer Janssen:
> the request seems to be constructed in different ways. This goes
> beyond what tftpd man page says about tftpd's options. Indeed, it
> looks like there aren't any tftpd options for this kind of variation
> at all, so it seems to
Am 28.09.2016 um 11:05 schrieb Peer Janssen:
> Am 28.09.2016 um 10:50 schrieb Solène Rapenne:
>> Le 2016-09-28 10:21, Peer Janssen a écrit :
>>> The target system for an OpenBSD 6.0 install, an alix.2d13, is directly
>>> connected to an alix.3x box serving dhcp an
Am 28.09.2016 um 10:50 schrieb Solène Rapenne:
> Le 2016-09-28 10:21, Peer Janssen a écrit :
>> The target system for an OpenBSD 6.0 install, an alix.2d13, is directly
>> connected to an alix.3x box serving dhcp and tftp.
>> alix.3x (Server):
>>
>> # tftp localhost
to experiment with putting "/pxeboot" in the dhcpd.conf options
instead of "pxeboot" (the docs are not clear which one is necessary for
a file in tftpboot chroot dir), but this kind of change only got me to
this kind of strange tftpd console logs:
tftpd: 192.168.0.81: re
unknown off
tty01 "/usr/libexec/getty std.9600" unknown off
tty02 "/usr/libexec/getty std.9600" unknown off
tty03 "/usr/libexec/getty std.9600" unknown off
tty04 "/usr/libexec/getty std.9600" unknown off
I also tried console:
# cu -d -l console -s 9600
Connected to /dev/console (speed 9600)
Seems configured at least -- but no data arrives. So still something is
missing.
Maybe some BIOS quirk, who knows.
Maybe someone on this list had a similar problem?
This is a very fresh install, I didn't update but reinstall completely.
Peer
--
Peer Janssen - p...@pjk.de
my serial logger software
(instead of getty) directly to tty00 (once I know how to configure it),
so that when the box boots, it automatically starts logging, and if the
process disappears, it restarts it. Right?
Peer
--
Peer Janssen - p...@pjk.de
at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (0e0478eff5b1b08d.a) swap on wd0b dump on wd0b
--
Peer Janssen - p...@pjk.de
(1)
The pkg_add man page sais that digitally signed packages are checked
against authorities in /etc/ssl/pkgca.pem.
I didn't find this pkgca.pem at said place, although pkg_add is indeed
installed.
I suppose checking of digitally signed packages will not be possible
without these certificates.
So
Hi,
I'm writing this
- in order to provide some feedback about my user experience (before it
even started, that is),
- because others might find a modicum of help here if they happen to
stumble on the same issue,
- in order to suggest a check for completeness for building the CD sets,
- and maybe
Is there another way to buy those cool wireframe-puffy stickers, than from
kd85?
I need something to cover my 'new' laptop. :-(
This is something I am curious about as well, new laptops look bare
without Puffy on the lid
I guess Wim would be more than happy to sell his stock of stickers and
Hi!
I subscribed to security-announce a long time ago and thought I would
receive information about security annoucements, but contrary to what is
stated on http://openbsd.org/mail.html:
"security-announce - Security announcements. This low volume list
receives OpenBSD security advisories an
18 matches
Mail list logo