Re: AMD64 Snapshot Issues
> > This is how it goes with snaps. You should not complain. If team > > managed to build it, it does not mean that it IS stable. I'v been in > > this situation several times. There are no one to blame. You should > > ever stay away from snaps or be prepared to fix problems by yourself. > > No one is complaining, and no one needs a lecture. > > These emails are simply to point out the issue in case devs aren't > aware, and to warn people who were considering updating to wait a day or > two. > > Fixing snapshot problems yourself isn't necessary as long as you are > willing to briefly have an inoperable machine a few times a year. > > Anecdotally, consider wrapping your future emails to 72 characters. It > makes them easier to read for many email clients and archivers: > > http://www.openbsd.org/mail.html > Micheal, let's keep talking this forever.
Re: AMD64 Snapshot Issues
> This is how it goes with snaps. You should not complain. If team > managed to build it, it does not mean that it IS stable. I'v been in > this situation several times. There are no one to blame. You should > ever stay away from snaps or be prepared to fix problems by yourself. No one is complaining, and no one needs a lecture. These emails are simply to point out the issue in case devs aren't aware, and to warn people who were considering updating to wait a day or two. Fixing snapshot problems yourself isn't necessary as long as you are willing to briefly have an inoperable machine a few times a year. Anecdotally, consider wrapping your future emails to 72 characters. It makes them easier to read for many email clients and archivers: http://www.openbsd.org/mail.html
Re: AMD64 Snapshot Issues
> > > I suspect that the devs are already aware of this, but I thought I'd > > > mention it. > > > > He is pointing out the error. There have been several cases of the devs > thanking users for pointing out issues in snapshots. That's kind of > what they are here for.. testing. Generally the first time a person reports it, it is quickly handled. Then a meta discussion starts..
Re: AMD64 Snapshot Issues
> This is how it goes with snaps. You should not complain. If team > managed to build it, it does not mean that it IS stable. I'v been in > this situation several times. There are no one to blame. You should > ever stay away from snaps or be prepared to fix problems by yourself. > > Br > //mxb He said: > > I suspect that the devs are already aware of this, but I thought I'd > > mention it. > He is pointing out the error. There have been several cases of the devs thanking users for pointing out issues in snapshots. That's kind of what they are here for.. testing. I agree that you get to keep all the pieces if snapshots break, though. Shouldn't expect a fix for every problem that arises. Just hope the next one fixes it, or that a downgrade works.
Re: AMD64 Snapshot Issues
This is how it goes with snaps. You should not complain. If team managed to build it, it does not mean that it IS stable. I'v been in this situation several times. There are no one to blame. You should ever stay away from snaps or be prepared to fix problems by yourself. Br //mxb Sent from my iDevice > 17 Jun 2015, в 19:39, Michael McConville написал(а): > > About twelve hours ago, I downloaded and installed the latest AMD64 > snapshot (#1063 in /etc/motd). When booting it hits an infinite loop, > repeatedly printing "Process (pid 1) got signal 4" to the console. > > When I boot to a snapshot ramdisk or bsd.rd now, it hangs at "root on > rd0a swap on rd0b dump on rd0b". This happens on two different USBs, and > whether or not my primary drive is even connected to the machine. > > A half hour ago, I downloaded a newer snapshot ramdisk from > ftp.openbsd.org. When booted to, this one immediately hits an infinite > loop, printing "Using drive 0, partition 3." to the console. > > I'm pretty confident that this is an issue with the snapshots and not my > machine because the 5.7 release images boot fine. > > I suspect that the devs are already aware of this, but I thought I'd > mention it.
Re: AMD64 Snapshot Issues
Using AMD64 snapshot taken 16-Jun-2015 17:07 SHA256 (install57.fs) = b0b72edf6544d98f11dabf14b3c052f8302f5c75332b1747ada95b7a1fe08acf I also could not get installer prompt / shell. The system was stuck at root on rd0a swap on rd0b dump on rd0b I had success with the newest snapshot from ftp.openbsd.org tough: SHA256 (install57.fs) = 32737e8b4ba1833412a762a7a06567b65d369418554a73d9cc6d59c5fd528e10 This latest one has seems not to have been synced across all mirrors yet. On 17 Jun 2015, at 19:39, Michael McConville wrote: > About twelve hours ago, I downloaded and installed the latest AMD64 > snapshot (#1063 in /etc/motd). When booting it hits an infinite loop, > repeatedly printing "Process (pid 1) got signal 4" to the console. > > When I boot to a snapshot ramdisk or bsd.rd now, it hangs at "root on > rd0a swap on rd0b dump on rd0b". This happens on two different USBs, and > whether or not my primary drive is even connected to the machine. > > A half hour ago, I downloaded a newer snapshot ramdisk from > ftp.openbsd.org. When booted to, this one immediately hits an infinite > loop, printing "Using drive 0, partition 3." to the console. > > I'm pretty confident that this is an issue with the snapshots and not my > machine because the 5.7 release images boot fine. > > I suspect that the devs are already aware of this, but I thought I'd > mention it.
AMD64 Snapshot Issues
About twelve hours ago, I downloaded and installed the latest AMD64 snapshot (#1063 in /etc/motd). When booting it hits an infinite loop, repeatedly printing "Process (pid 1) got signal 4" to the console. When I boot to a snapshot ramdisk or bsd.rd now, it hangs at "root on rd0a swap on rd0b dump on rd0b". This happens on two different USBs, and whether or not my primary drive is even connected to the machine. A half hour ago, I downloaded a newer snapshot ramdisk from ftp.openbsd.org. When booted to, this one immediately hits an infinite loop, printing "Using drive 0, partition 3." to the console. I'm pretty confident that this is an issue with the snapshots and not my machine because the 5.7 release images boot fine. I suspect that the devs are already aware of this, but I thought I'd mention it.
