When you enter the realm of hardware errors, anything can happen. If
you are lucky you will see the same hard and soft errors every time you
cross a bad sector, but I have seen many cases wildly varying block
numbers on really sick disks. And yes, bad cables and USB interfaces
can be a proble
Hi,
I'm running fsck on an external USB hard drive, using OpenBSD 6.2
inside VirtualBox on MacOS.
On each run it gives a handful of "CANNOT READ: BLK ..." messages, but
the block numbers reported are different (!) each time.
If the disk is damaged, shouldn't the problematic blocks be
consistent?
Hi, All
I am useing openbsd 6.2 release, as an server production. My network is
split with vlan into int_ and ext_ . However, I'm not sure which way to
run the VPN in a virtual machine or configure it on the int_ or ext_ so
that all the traffic from the int_ side is encrypted tun when it hit HTTP
> Ted Unangst wrote:
> > Otto Moerbeek wrote:
> > > Sparc64 and powerpc also have speculative execution, branch
> > > prediction and extensive caches. It is much wiser to assume they are
> > > also affected by (similar) bugs/explots or whatever you call it.
> >
> > A lot of the commonly available
Ted Unangst wrote:
> Otto Moerbeek wrote:
> > Sparc64 and powerpc also have speculative execution, branch
> > prediction and extensive caches. It is much wiser to assume they are
> > also affected by (similar) bugs/explots or whatever you call it.
>
> A lot of the commonly available sparc64 gear,
> From: Philip Guenther
> Date: Fri, 5 Jan 2018 20:52:20 -0800
>
> Unless something unexpected happens, we'll be applying the workaround to
> amd64 first and then working out what to do for i386 and arm* (if still
> though to be necessary for arm) after that.
FWIW, Meltdown is a non-issue for Op
Otto Moerbeek wrote:
> Sparc64 and powerpc also have speculative execution, branch
> prediction and extensive caches. It is much wiser to assume they are
> also affected by (similar) bugs/explots or whatever you call it.
A lot of the commonly available sparc64 gear, T2 and USIII, are in order.
thanks, I had come to a similar conclusion, though I think they are
JIS screws.
diana
On Sat, 6 Jan 2018, Mihai Popescu wrote:
the PH00 screws don't want to turn with my jeweler's screwdriver.
They may be PZ00. Take care not to mix different types of screws and
bits! PH and PZ look very much
>>So I will be most interested to see the OpenBSD take on this after the
>> embargo period is over.
>How long is embargo period?
apparently Intel were aware of one of issues as early as Late June
Last year... and
late july for another issue ...
it will be interesting how quickly a handful of V
Fair enough, any idea if this could effect MIPS {32 64}? That's my next
most commonly deployed arch. I do assume that there will likely be some
issues on other arches, but from what I see, folks are still doing
pensive beard stroking trying to determine if AMD chips are susceptible.
SPARC is ti
On Sat, Jan 06, 2018 at 10:22:25AM -0800, Jordan Geoghegan wrote:
> All my web-facing servers are running SPARC and/or for a couple smaller
> projects, PowerPC. People thought I was a loon when I vehemently insisted on
> SPARC over the years, and called me crazy when I hosted my personal web
> pro
All my web-facing servers are running SPARC and/or for a couple smaller
projects, PowerPC. People thought I was a loon when I vehemently
insisted on SPARC over the years, and called me crazy when I hosted my
personal web projects on PowerPC. x86 is a disease.
A little bit extra in electricity
Thus said Ed Ashlen-girard on Fri, 5 Jan 2018 07:17:23 -0600
After upgrading to the Jan 4 amd64 snapshot, I do not see a login box. I
can ssh to the machine, and run X applications in an X server, but no
graphical login at the console. dmesg below.
I had no problems, and I think I was on that
On 01/02/18 14:03, Stuart Henderson wrote:
> Hosting a large git repository is not trivial, it uses far more server
> resources (memory and cpu time) than an anoncvs/cvsync/rsync mirror, and
> OpenBSD src/ (or even just ports/) is *huge* for a git repo. It works
> better on Linux where things are m
On Sat, Jan 06, 2018 at 02:40:00PM +, Mik J wrote:
> Hello Edgar,
> I just found that the path is related to the home directory of the virtual
> user that is specified in /etc/passwd
> If you have a configuration that uses virtual users and that relies on a unix
> user _vmail then this unix u
Hello Edgar,
I just found that the path is related to the home directory of the virtual user
that is specified in /etc/passwd
If you have a configuration that uses virtual users and that relies on a unix
user _vmail then this unix user has an entry in /etc/passwd
So the smtpd deamon uses the home
Yes! They are also working on risc-v.
Sent from ProtonMail Mobile
On Fri, Jan 5, 2018 at 19:50, ropers wrote:
> On 4 January 2018 at 09:13, Rupert Gallagher wrote:
>
>> The Chinese have an interesting project on RISC, who is taking ages to hit
>> the market.
>
> Is that https://www.openbsd.or
http://www.mcst.ru/
On Sat, Jan 6, 2018 at 08:05, Jordan Geoghegan wrote:
> They make their own via the /Moscow Center of SPARC Technologies./ Check out
> the Elbrus architecture, its pretty clever. It can run native SPARC binaries
> and also has a fairly efficient x86 compatibility layer buil
- Original message -
On 05/01/18 08:51, Eric Furman wrote:
> I always love threads like this. :)
> Doesn't it tell anybody anything that none of the developers have commented?
My point was that this thread was just pointless speculation
by a bunch of people who have no idea of what they w
Sorry for the typo.
Hi.
I need to access bikecad.ca's Java applet.
I installed icedtea-web and restarted firefox-esr but the applet won't
show up in my browser.
Any advices?
> So I will be most interested to see the OpenBSD take on this after the
> embargo period is over.
How long is embargo period?
So, yes, we the OpenBSD developers are not totally asleep and a handful of
us are working out how to deal with Intel's fuck-up aka the Meltdown
attack. While we have the advantage of less complexity in this area (e.g.,
no 32bit-on-64bit compat), there's still a pile of details to work through
abou
On 05/01/18 08:51, Eric Furman wrote:
> I always love threads like this. :)
> Doesn't it tell anybody anything that none of the developers have commented?
>
Ignorant speculation: has pledge as revealed the severity of these bugs ?
24 matches
Mail list logo
