On 2024-06-04, Jan Stary wrote:
>> > I want to upgrade an amd64 system running 6.9.
>
> Backup, reinstall current from scratch,
> restore from backup.
>
>> > wget https://cdn.openbsd.org/pub/OpenBSD/7.{0,1,2}/amd64/bsd.rd
>> > returns 404 for all three qu
> > I want to upgrade an amd64 system running 6.9.
Backup, reinstall current from scratch,
restore from backup.
> > wget https://cdn.openbsd.org/pub/OpenBSD/7.{0,1,2}/amd64/bsd.rd
> > returns 404 for all three queries.
> > Where can I find the bsd.rd images for these vers
upgrades
could fail due to disk space.
You may be better off re-installing.
wget https://cdn.openbsd.org/pub/OpenBSD/7.{0,1,2}/amd64/bsd.rd
returns 404 for all three queries.
Where can I find the bsd.rd images for these versions?
Thanks for your help.
Wish you luck
On Fri, 31 May 2024 10:02:57 +0100,
"Quentin Carbonneaux" wrote:
>
> I want to upgrade an amd64 system running 6.9. Following
> the guide I would like to upgrade to 7.{0,1,2,3,4,5}
> sequentially. However it looks like
>
> wget https://cdn.openbsd.org/pub/Op
Hi,
I want to upgrade an amd64 system running 6.9. Following
the guide I would like to upgrade to 7.{0,1,2,3,4,5}
sequentially. However it looks like
wget https://cdn.openbsd.org/pub/OpenBSD/7.{0,1,2}/amd64/bsd.rd
returns 404 for all three queries.
Where can I find the bsd.rd images for
The keyboard is a Newmen GM610 Gaming Keyboard I shot on amazon.
Regards
Harri
n is there
significant risk that new users would encounter this in the wild, with a
probability large enough that it would be useful to add a note about this to
say https://www.openbsd.org/faq/faq4.html#bsd.rd somewhere?
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http
>
>
> On 12/28/23 12:30, Michael Hekeler wrote:
> >
> > I try to install OpenBSD on netcup ARM, too...
> >
> > > I disabled the pluart driver in the ramdisk kernel (on a other machine
> > > with
> > > config -e -f /bsd.rd and copied the r
On 12/28/23 12:30, Michael Hekeler wrote:
I try to install OpenBSD on netcup ARM, too...
I disabled the pluart driver in the ramdisk kernel (on a other machine with
config -e -f /bsd.rd and copied the ramdisk kernel over to the nectup
server) and got access the the installation script
I try to install OpenBSD on netcup ARM, too...
> I disabled the pluart driver in the ramdisk kernel (on a other machine with
> config -e -f /bsd.rd and copied the ramdisk kernel over to the nectup
> server) and got access the the installation script.
How did you disable pluart driv
On Sun, Dec 17, 2023 at 09:56:04PM +0100, Sven Wolf wrote:
> I only have access to the graphical console
IIRC they have a forum where some support could be provided.
I'd ask about serial over lan access. Hetzner have it, but I'm not
sure about netcup.
Best regards,
Chris Narkiewicz
On Aug 28 06:34:01, Jan Stary wrote:
>On Aug 27 22:56:59, ch...@mailfence.com wrote:
>> I would like be able to transfer files over ethernet from a system
>> that has been booted from bsd.rd
>
>Why do you need that?
>
>(The only case where I want to have file
On Aug 27 22:56:59, ch...@mailfence.com wrote:
> I would like be able to transfer files over ethernet from a system
> that has been booted from bsd.rd
Why do you need that?
(The only case where I want to have files from a bsd.rd boot
is a dmesg of a machine I am looking at, without inst
The interactive mode of the ftp client is not compiled into the
install media.
But, the non-interactive mode is there, so you can use -o
to download files.
However, you seem to want to push files out. That support is also
compiled out.
These things are missing because if they remained, the inst
Hello,
TL;DR:
I would like be able to transfer files over ethernet from a system
that has been booted from bsd.rd, to an installed OpenBSD system.
This does not seem to be possible. If it is somehow possible, because
I am missing something, or perhaps because there is an undocumented
to send a dmesg, but I can't get one as I can't boot anything.
With current
probing: pc0 mem[636K 1878M 12M 5M 76K 172K 700K 6M 5M 30732M]
disk: hd0 hd1* hd2* hd3* hd4*
>> OpenBSD/amd64 BOOTX64 3.64
boot>
cannot open hd0a:/etc/random.seed: No such file or directory
booting hd
On 2023-05-01, Damian McGuckin wrote:
>
> What is required please?
>
> I am trying to boot this bsd.rd (which is a file 4Mb big) on an old
> NET5500 which has 512MBytes of RAM. On a running system,
>
> From the
>
> boot>
>
> prompt, doing
>
>
On Mon, 1 May 2023 at 12:38, Damian McGuckin wrote:
[...]
> it appears to loads bsd.rd, but then drops straight back into the BIOS
> and starts the BIOS boot.
>
> Any suggestions.
Try switching the console to serial instead of relying on the BIOS:
boot> stty com0 19200
boo
Are you sure you're using i386 and not amd64?
Paul 'WEiRD' de Weerd
On Mon, May 01, 2023 at 12:26:41PM +1000, Damian McGuckin wrote:
|
| What is required please?
|
| I am trying to boot this bsd.rd (which is a file 4Mb big) on an old
| NET5500 which has 512MBytes of RAM. On a
How are you getting to the boot> prompt?
On Mon, May 1, 2023 at 12:28 PM Damian McGuckin wrote:
>
>
> What is required please?
>
> I am trying to boot this bsd.rd (which is a file 4Mb big) on an old
> NET5500 which has 512MBytes of RAM. On a running system,
>
>
What is required please?
I am trying to boot this bsd.rd (which is a file 4Mb big) on an old
NET5500 which has 512MBytes of RAM. On a running system,
From the
boot>
prompt, doing
boot> boot bsd.rd
it appears to loads bsd.rd, but then drops straight back into th
I also got other tips outside the email list, and this got me going
down a rabbit hole within the BIOS. After clearing nvram, and
resetting to defaults, somehow this got it to boot up just fine. I'm
part relieved that it works, and part concerned that I have no idea
why, so I've spent the weeken
s equipped with four
> serial ports, so use one. This does not address the bug-if in fact
> there is one-but it should at least allow you to work around it.
>
Thanks for the suggestions. The only way I can boot is through bsd.rd.
Boot -s made no difference as it hangs before this wo
least allow you to work around it.
I very recently ran into a similar issue with a new system I built. I
was able to boot bsd.rd as well as bsd in single-user mode; however
when booting bsd normally, it would hang after fsck(8) ran. This
happened with the most recent snapshot as well. I was ab
Hello,
I am able to boot bsd.rd/install usb just fine. If I drop to shell
and manually mount/chroot into the installed system, everything
_seems_ to work just fine. Whenever I try to boot the fresh install,
the furthest I was able to get by disabling inteldrm, and items
related to either
I went to do a sysupgrade on my Dell R410 server last night and it entered
a boot loop situation. While loading bsd.upgrade, it immediately reboots. I
manually selected "boot /bsd" and then downloaded a fresh OpenBSD 7.2
bsd.rd (saved to /bsd.rd.72) and booted from that with the s
sd/src/blob/636cc85955243f5226db2246a74229481ad6bac2/distrib/miniroot/install.sub#L1838
>
> It seems we do not allow "@" either at the moment...
>
> /Alexander
>
> Thank you,
A pity I did not see your post earlier, In the installer, I had to page
with lousy 'more(1)
ets by prepending a '-', e.g.: '-game*'. Selected sets are labelled
'[X]'.
[X] bsd [X] man71.tgz [X] xfont71.tgz
[X] bsd.rd [X] game71.tgz [X] xserv71.tgz
[X] base71.tgz [X] xbase71.tgz
reya=@192.168.222.242' is not a valid hostname.
>
>The same error occurs when I want to install the custom site* sets
>from my non-local xyz.nl server
>
>HTTP Server? (hostname, list#, 'done' or '?') [192.168.222.242]
>wodan:=ilovefreya=@xyz.nl
>'wo
7;done' or '?') [192.168.222.242]
wodan:=ilovefreya=@xyz.nl
'wodan:=ilovefreya=@xyz.nl' is not a valid hostname.
So using an username and password for .htaccess control is accepted by
bsd.rd for the 'install.conf' and
autopartioning template, while it er
Nicola Dell'Uomo wrote:
> From a couple of weeks I've been noticing these problems when I upgrade from
> bsd.rd:
>
> - after installing all verified .tgz files and making device nodes &
> fw_update my system reports as follows: 'Failed to install bootblock
I'm trying to install OpenBSD current on HP ProBook 450 G8 and booting
bsd.rd is stuck at the very initial stage (last line - entry point 0x).
I've tried disabling various bios features but without success.
Any suggestions on making OpenBSD to work?
dmesg from ubuntu is bellow:
[
On 2022-01-27, S V wrote:
> Hello, I want to build "bigger" bsd.rd image. Does rebuilding it only way
> to increase it? Can I somehow increase its size and just rdsetroot new
> disk.fs?
You'll need to build a release(8) after adjusting at least FSSIZE in the
relevant Mak
Hello, I want to build "bigger" bsd.rd image. Does rebuilding it only way
to increase it? Can I somehow increase its size and just rdsetroot new
disk.fs?
--
Nerfur Dragon
-==(UDIC)==-
Upgrading from current 6.9 GENERIC#108 amd64 to current 6.9 GENERIC#129 amd64
solved the problem.
Thanks.
‐‐‐ Original Message ‐‐‐
Il sabato 10 luglio 2021 10:05 PM, Nicola Dell'Uomo
ha scritto:
> Thank you: I'm used to upgrading to the latest snapshot once at week and this
> is th
Thank you: I'm used to upgrading to the latest snapshot once at week and this
is the first time this kind of error happens.
I don't know what I should look for: moreover as my disk is totally encrypted,
I fear to screw up my boot block and system and not to be able to boot anymore.
Every sugges
Can somebody suggest me what should I look at?
‐‐‐ Original Message ‐‐‐
Il giovedì 8 luglio 2021 11:17 AM, Nicola Dell'Uomo
ha scritto:
> Hi,
>
> upgrading from current 6.9 GENERIC#99 amd64 to current 6.9 GENERIC#108 amd64
> end up with this error:
>
> [snip]
> Making all device nodes.
Hi,
upgrading from current 6.9 GENERIC#99 amd64 to current 6.9 GENERIC#108 amd64
end up with this error:
[snip]
Making all device nodes... done
installboot: write: No space left on device
Failed to install bootblocks.
You will not be able to boot OpenBSD from sd1.
[end]
In this case sd1 is th
> On 4 May 2021, at 21:50, Dave Voutila wrote:
>
> Mischa writes:
>
>> Hi All,
>>
>> I have a couple of machines running on 6.8 still, will upgrade soon. :)
>> For some reason when I am trying to boot a 6.9 bsd.rd nothing is happening.
>
> 6.9 bsd.r
Mischa writes:
> Hi All,
>
> I have a couple of machines running on 6.8 still, will upgrade soon. :)
> For some reason when I am trying to boot a 6.9 bsd.rd nothing is happening.
6.9 bsd.rd's for amd64 are gzip'd. For 6.9, vmd was taught how to boot
compressed kernels/ra
Hi All,
I have a couple of machines running on 6.8 still, will upgrade soon. :)
For some reason when I am trying to boot a 6.9 bsd.rd nothing is happening.
It's only showing:
Connected to /dev/ttypq (speed 115200)
Nothing else appears.
Booting from a 6.8 bsd.rd works normally.
Equally bo
> >
> > I tried to `set db_console 1` and change video mode
> > with machine video before booting, and entering
> > `boot dump` blindly ( video off )
> > but after rebooting in bsd.rd /var/ has no dmesg.anything
> > or some log
> >
> > I think the last
and change video mode
> with machine video before booting, and entering
> `boot dump` blindly ( video off )
> but after rebooting in bsd.rd /var/ has no dmesg.anything
> or some log
>
> I think the last line of boot i see is 'softraid0'
>
> There's probabl
ering
> `boot dump` blindly ( video off )
> but after rebooting in bsd.rd /var/ has no dmesg.anything
> or some log
>
> I think the last line of boot i see is 'softraid0'
>
> There's probably a few tricks I should try to get the actual
> message, I will do my
amd64 installation the video
signal is completely lost and network too ( suspect crash )
I tried to `set db_console 1` and change video mode
with machine video before booting, and entering
`boot dump` blindly ( video off )
but after rebooting in bsd.rd /var/ has no dmesg.anything
or some log
I thin
#x27;d files? I am not sure
> > > about that.
> >
> > Yeah, I don't think so either. gzip(1) can be easily used to
> > uncompress it beforehand.
> >
> > But the result is still that rdsetroot on -current is not able to
> > extract a bsd.rd even when
. gzip(1) can be easily used to uncompress
> it beforehand.
>
> But the result is still that rdsetroot on -current is not able to
> extract a bsd.rd even when given an uncompressed bsd.rd (i.e. a "ELF
> 64-bit LSB executable, x86-64, version 1" bsd.rd).
>
I looked at w
on -current is not able to
extract a bsd.rd even when given an uncompressed bsd.rd (i.e. a "ELF
64-bit LSB executable, x86-64, version 1" bsd.rd).
current amd64, I fetched a -current amd64 bsd.rd, then run
> $ rdsetroot -x bsd.rd ramdisk
> rdsetroot: bsd.rd: not an elf
>
> I didn't expect that, so I run file on it which said
> bsd.rd: gzip compressed data, max compression, from Unix
>
> I naively tried to gunz
Hi,
Running -current amd64, I fetched a -current amd64 bsd.rd, then run
$ rdsetroot -x bsd.rd ramdisk
rdsetroot: bsd.rd: not an elf
I didn't expect that, so I run file on it which said
bsd.rd: gzip compressed data, max compression, from Unix
I naively tried to gunzip it:
$ mv bsd.rd bsd.
On 2021-01-30, Daniel Jakots wrote:
> Hi,
>
> I upgraded my APU2 on 2021-01-16 and I have this in the upgrade log
> email:
>
> Terminal type? [vt220] vt220
> Available disks are: sd0.
> Which disk is the root disk? ('?' for details) [sd0] sd0
> Checking root filesystem (fsck -fp /dev/sd0a)... OK.
normal/expected?
It doesn't cause me any trouble but I would have expected the same
'behavior' from trunk(4) and aggr(4) in this regard. Or is it to keep
bsd.rd on a diet?
Cheers,
Daniel
Status Code Available
DXE Status Code Available
>> OpenBSD/amd64 BOOTX64 3.50
boot>
booting hd0a:/bsd: 12952904+2757640+331808+0+708608
[807661+128+1024872+749630]=0x1272b18
entry point at 0x1001000
[ using 2583320 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
T
On Sun, Jul 19, 2020 at 9:06 AM Alfred Morgan wrote:
>
> OpenBSD upgrade.lan 6.7 GENERIC.MP#182 amd64
>
> If I set tty com0 then bsd.rd boots fine. If I have a monitor plugged in
> bsd.rd boots fine. If I don't have a monitor and I don't direct tty to com0
> then bsd.r
OpenBSD upgrade.lan 6.7 GENERIC.MP#182 amd64
If I set tty com0 then bsd.rd boots fine. If I have a monitor plugged in
bsd.rd boots fine. If I don't have a monitor and I don't direct tty to com0
then bsd.rd reboots my machine after a few seconds.
Any tips on how I can inspect what is goi
I think you are using the old boot method, which boots bsd from
msdos. The new method has a bootblock, which loads bsd from the
filesystem.
Meaning you didn't read the notes, and your setenv's are wrong.
Lars Noodén wrote:
> I've tried downloading bsd.rd for octeon for both
I've tried downloading bsd.rd for octeon for both 6.6 and snapshots. However,
when I actually boot from it, I seem to get 6.5 instead of 6.6 for both the
boot message and the sets it looks for over HTTP. The file verifies with
signify using the SHA256.sig file using the 6.6 key. I
Roderick(hru...@gmail.com) on 2019.12.21 19:50:03 +:
>
> On Thu, 19 Dec 2019, Theo de Raadt wrote:
>
> > for 6.5 onwards, all you had to was type
> >
> > sysmerge
> > sysupgrade
>
> I read somewhere that something like this was coming for 6.6, but
> I remember that I followed the i
On Thu, 19 Dec 2019, Theo de Raadt wrote:
> for 6.5 onwards, all you had to was type
>
> sysmerge
> sysupgrade
I read somewhere that something like this was coming for 6.6, but
I remember that I followed the instructions for upgrading from 6.5
to 6.6, and this was to be done manually
"Theo de Raadt" writes:
> Jonathan Thornburg wrote:
>
>> Being able to copy the new (6.6) bsd.rd to an existing filesystem on the
>> (running) old OpenBSD system, then boot that bsd.rd to install, was
>> really really nice. Thank you!
>
> well you missed
his time I found myself with the
>> combination of a broken built-in cd/dvd drive, and a computer which
>> didn't
>> seem to want to boot from USB even after fiddling with bios settings.
>> Being able to copy the new (6.6) bsd.rd to an existing filesystem on the
>
On 2019-12-20, "Theo de Raadt" wrote:
> well you missed out
>
> for 6.5 onwards, all you had to was type
>
> sysmerge
> sysupgrade
I think that was intended to read
syspatch
sysupgrade
> for 6.6 onwards you'll only need sysupgrade
--
Christian "naddy" Weisgerber
ch didn't
> seem to want to boot from USB even after fiddling with bios settings.
> Being able to copy the new (6.6) bsd.rd to an existing filesystem on the
> (running) old OpenBSD system, then boot that bsd.rd to install, was
> really really nice. Thank you!
well you missed out
for 6
ttings.
Being able to copy the new (6.6) bsd.rd to an existing filesystem on the
(running) old OpenBSD system, then boot that bsd.rd to install, was
really really nice. Thank you!
--
-- "Jonathan Thornburg [remove color- to reply]"
"He wakes me up every morning meowing to death
I'd quite like to debug this problem. I'm looking through the code
now to find out where I can inject some sort of printf-like statement
to glean some information about what it's [not] doing and may eventually
even get somewhere.
I'll continue to do this regardless because I'm bored and I just
spe
As per the subject, bsd.rd boots and the installation proceeded as
usual. Another laptop saved from ever booting the mess it came
preinstalled with. Yay.
Subsequently rebooting results in the following (bsd.sp does the
same with different addresses):
probing: pc0 mem[632K 475M 255M 208M 137M
Hi! I have yeeloong8089d laptop computer, with pmon2000 firmware
(version line: "PMON2000 2.1 (Bonito) #14: Tue May 18 10:33:47 CST
2010"). I write OpenBSD/6.6/loongson/miniroot66.fs to usb drive. In
first partition of miniroot66.fs, rest identical 2 file "bsd" and
&quo
[not subscribed to this list, so please Cc me. thanks.]
An extraordinarly crap machine, certainly compared to the Thinkpad;
don't ask me how megot hold of it, or why me's using it at all.
The USB kbd has been provided by me and is thus not part of the craptop.
--zeurkous.
OpenBSD 6.4
See this post:
https://marc.info/?l=openbsd-tech&m=153713589005530&w=2
Doesn't hurt to search before posting.
trap type 18, code 0, pc=81374ace
gsbase 0x81870ff0 kgsbas 0x0
panic: trap type 18, code 0, pc=81374ace
dmesg below.
--
Edward Ahlsen-Girard
Ft Walton Beach, FL
OpenBSD 6.4-beta (GENERIC.MP) #294: Wed Sep 12 19:50:03 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/
Hi all,
I'm having a similar problem with the snapshot dated 15-Sep-2018. I've
verified the hash and with signify and it seems to be not corrupted,
but I'm unable to boot from it.
Mulder: sorry if I sent only to you the previous mail.
Here's some information, hope they help
On Sun, 16 Sep 2018 17:02:05 +0200
Omar Polo wrote:
> I'm having a similar problem with the snapshot dated 15-Sep-2018. I've
> verified the hash and with signify and it seems to be not corrupted,
> but I'm unable to boot from it.
I'm still seeing the issue with the Sep 15 snapshot also.
Sijmen
Hi all,
I downloaded https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/bsd.rd
dated 14-Sep-2018 23:01 and verified its hash:
SHA256 (/bsd.rd) =
e362a4faff40decf0a1cc336a4cace03dadc4e8e43fa27492439ca9370a73625
When I boot it, the system reboots almost immediately. This is what
dmesg has to
On 2018-04-05 15.29.22 -0600, ch...@ccmach14.org wrote:
> Hello - will someone please tell me where I can find the source for
> bsd.rd?
That's the kernel. Two ways to start reading:
/usr/src/distrib - this is how bsd.rd itself is built.
/usr/src/sys/kern/init_main.c - this is the ma
Same place as the bsd kernel itself - they're both built from the same source.
On Fri, Apr 6, 2018 at 7:29 AM, wrote:
> Hello - will someone please tell me where I can find the source for bsd.rd?
> Thanks
>
--
Aaron Mason - Programmer, open source addict
I've taken my
Hello - will someone please tell me where I can find the source for
bsd.rd? Thanks
No.
bsd.rd is for installation. It is not a diagnostic tool.
There are other ways to do diagnostics.
> does it make sense to add acpidump to bsd.rd ?
> I've tried to install snapshot on Dell R640 and installation went well
> but booting stops with this error:
> http://kosjenk
Hi all,
does it make sense to add acpidump to bsd.rd ?
I've tried to install snapshot on Dell R640 and installation went well
but booting stops with this error:
http://kosjenka.srce.hr/~hrvoje/zaprocvat/r640-01.jpg
i also noticed this ahci2 log while booting
http://kosjenka.srce.hr/~h
It turns out that the snapshot on Aarnet failed to match its checksum
for a blindingly obvious reason. It was corrupt.
I installed a snapshot from another mirror, started X, and crashed the
kernel. I'll try to post the details to bugs@ in a day or two, but
some hand holding would be appreciated.
Thanks Stuart
> Better to test sooner, if it still fails, if you can get a good report
> written up there's still some chance of a fix before release.
The machine is a cheap Dell laptop that's about 10 years old. It's
possible that an innocent change in the software triggered a latent
hardware f
lease you need should be
setting the install path, and using -Dsnap when installing packages.
>> You need to be sure to use the bsd.rd from the snapshot!
>
> I'm pretty sure that's what I booted. Does any other bsd.rd have a
> default path of pub/OpenBSD/6.3/i386?
>
&
wing:
>
> 1. Download bsd.rd and SHA256.sig from
> http://mirror.aarnet.edu.au/pub/OpenBSD/snapshots/
>
> 2. Fail to verify the 6.3 signatures, because I'm running 6.1. (It would
> be nice if the signify man page had instructions to download and verify
> openbsd--base.pub
Thanks for the replies. I suspect this is the answer I needed: don't
try to install a 6.2 snapshot just before version 6.3 is released,
instead wait for the release and install that.
> You need to be sure to use the bsd.rd from the snapshot!
I'm pretty sure that's what I boote
at work? I tried the following:
>
> 1. Download bsd.rd and SHA256.sig from
> http://mirror.aarnet.edu.au/pub/OpenBSD/snapshots/
>
> 2. Fail to verify the 6.3 signatures, because I'm running 6.1. (It would
> be nice if the signify man page had instructions to download and
bsd.rd and SHA256.sig from
http://mirror.aarnet.edu.au/pub/OpenBSD/snapshots/
2. Fail to verify the 6.3 signatures, because I'm running 6.1. (It
would
be nice if the signify man page had instructions to download and
verify
openbsd--base.pub.)
3. Reboot, with boot> boot sd0a:/root/b
Hi
This is my first post here, I appreciate how much work you all do, please
be gentle. :-)
Could someone please tell me how to install the latest snapshot, or point
me at some instructions that work? I tried the following:
1. Download bsd.rd and SHA256.sig from
http://mirror.aarnet.edu.au/pub
Gret, everything is in. Thank you.
For the record, the relevant function is :
uo_addfile() {
local dest=${1}
local src=${2}
local vnd_n=0
[ -r "${WRKDIR}/bsd.rd" ] || uo_err 2 "
l behaves as if the machine is netbooted,
but uses the local response file.
"""
I would like to build a custom bsd.rd to include auto_install.conf
file.
Do you have any advice for this ?
I found some tutorials for 5.7 [1], so quite outdated, and can't go
through
the en
As mentionned in autoinstall(8),
"""
If either /auto_install.conf or /auto_upgrade.conf is found on bsd.rd's
built-in RAM disk, autoinstall behaves as if the machine is netbooted,
but uses the local response file.
"""
I would like to build a custom bsd.rd to
info/?l=openbsd-tech&m=150719094005071&w=2
On Tue, Oct 17, 2017 at 1:56 PM, Mike Larkin wrote:
> On Tue, Oct 17, 2017 at 06:24:42PM +0200, Remco wrote:
>> I am not able to upgrade using bsd.rd on my VIA C3 system.
>>
>> Booting the i386 6.2 bsd.rd progresses to th
On Tue, Oct 17, 2017 at 06:24:42PM +0200, Remco wrote:
> I am not able to upgrade using bsd.rd on my VIA C3 system.
>
> Booting the i386 6.2 bsd.rd progresses to the "npx0 ..." line.
> After a short moment the system reboots and that's the end of the story.
>
I am not able to upgrade using bsd.rd on my VIA C3 system.
Booting the i386 6.2 bsd.rd progresses to the "npx0 ..." line.
After a short moment the system reboots and that's the end of the story.
I did check the bsd.rd using signify and it checked out all right:
$ signify -C
On Wed, Aug 02, 2017 at 05:15:58PM +0100, Anthony Campbell wrote:
>
>
> In the last 10 days several attempts to upgrade -current have failed
> owing to an error with bsd.rd. I get as far as choosing the keyboard;
> then I'm asked to mount the root system and am offered wd0.
In the last 10 days several attempts to upgrade -current have failed
owing to an error with bsd.rd. I get as far as choosing the keyboard;
then I'm asked to mount the root system and am offered wd0. But when I
accept that it says "wd0 is not a valid root disk". I then have to
re
I have everything split apart into two flash drives to get enough
diskspace. I couldn't get bsd.rd to work since not all of the partitions
were mounted. Any reasonable fix good for this problem? I was doing
upgrade to 6.1 from an older 6.1 -current.
Since everything is mounted when syst
My main OpenBSD system is a Shuttle SH81R4 with a 4th Gen i5. I run the latest
snapshot on it and once or twice a week I will boot into bsd.rd and run update.
A week or two ago I put a mini-pcie wifi card in it (athn0) and after getting
some help from this mailing list, I got this system
* Raf Czlonka [170401 00:15]:
Date: Fri, 31 Mar 2017 09:13:57 +0100
From: Raf Czlonka
To: OpenBSD Misc
Subject: Re: Question about bsd.rd
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: owner-m...@openbsd.org
On Fri, Mar 31, 2017 at 02:51:47AM BST
On Fri, Mar 31, 2017 at 02:51:47AM BST, Steven Schneider wrote:
> Hi @misc,
>
> I've noticed that bsd.rd wants to download the install base packages from
> /pub/OpenBSD/6.1/i386. Is this an error or some sort of alias for the path
> to the snapshots of the install base? bsd.
> I've noticed that bsd.rd wants to download the install base packages
> from /pub/OpenBSD/6.1/i386. Is this an error or some sort of alias for
> the path to the snapshots of the install base? bsd.rd seems to find the
> install base packages alright.
That is normal during
Hi @misc,
I've noticed that bsd.rd wants to download the install base packages
from /pub/OpenBSD/6.1/i386. Is this an error or some sort of alias for
the path to the snapshots of the install base? bsd.rd seems to find the
install base packages alright. pkg_add has trouble findin
1 - 100 of 446 matches
Mail list logo
