ils. There isn't a
guarantee of this as quite a lot of enclosures provide their more
serious control operations through vendor specific requests and channels.
Mike
--
Mike Pumford, Senior Software Engineer
MPC Data Limited
e-mail: mpumf...@mpcdata.comweb: www.mpcdata.com
tel: +44
queries.
Mike
--
Mike Pumford, Senior Software Engineer
MPC Data Limited
e-mail: mpumf...@mpcdata.comweb: www.mpcdata.com
tel: +44 (0) 1225 710600fax: +44 (0) 1225 710601
ddi: +44 (0) 1225 710635
___
freebsd-stable@freebsd.org mailing
jb wrote:
From the point of view of an attacker it does not matter whether kernel module
is loaded and linked once only. That's enough to create a window of opportunity
for interfering with relocation process and modifying text (code).
Well yes but said attacker has to be able to modify KERNEL
Ronald Klop wrote:
Do you have a problem yourself or did you just found some messages on
google?
I presume you are running 6.3 yourself. Why don't you upgrade the OS to
6.4 or 7+, but you do upgrade the ports on an unsupported OS?
It is a little mind boggling. Unless required I wouldn't even re
n I was using. This was fixed when I did the
mergemaster on /etc (which I did on a snapshot later). At this point in
time the machine was still running ports compiled in the 5.x timeframe.
I then created a chroot environment to do the ports update in.
Mike
--
Mike Pumford, Senior Software Engineer
Ian Lepore wrote:
On Wed, 2013-05-29 at 16:21 +0200, Oliver Fromme wrote:
Steven Hartland wrote:
> Have you checked your sata cables and psu outputs?
>
> Both of these could be the underlying cause of poor signalling.
I can't easily check that because it is a cheap rented
server in a remo
Abdullah Ibn Hamad Al-Marri wrote:
Previously I didn't mention that there are some functions missing from
the FreeBSD's NDIS api. These are:
With the help of NDIS reference and Linux ndiswrapper I have been able
to implement all but KeBugCheckEx (they are all rather simple but I
Can help y
On 19/01/2018 12:28, Andrea Brancatelli wrote:
Hello guys.
I have a couple of ancient FreeBSD install that I have to bring into
this century (read either 10.4 or 11.1) :-)
I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
9.3-RELEASE-p53.
I've just done a 9.3 to 10.3 upgrade w
s accurate time.
Mike
--
Mike Pumford | Senior Software Engineer
T: +44 (0) 1225 710635
BSQUARE - The business of IoT
www.bsquare.com <http://www.bsquare.com/>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listi
s sold as
2400 but thats actually an overclock profile. If I actually enabled it
(despite both board and RAM being qualified for that) the system ends up
locking up or crashing as soon as you stress it. Go back to the standard
DDR profile advertised by the RAM and it is totally stable.
Mike
es.
From what I read at the time 2133 is the official upper limit of the
DDR4 standard. Any speed faster than that is an overclock profile.
Mike
--
Mike Pumford | Senior Software Engineer
T: +44 (0) 1225 710635
BSQUARE - The business of IoT
www.bsquare.com <http://ww
rofiles on both and it
introduced instability that went away when I went back to the standard
profile. I've done BIOS updates since then so its worth me checking that
again anyway.
Mike
--
Mike Pumford | Senior Software Engineer
T: +44 (0) 1225 710635
BSQUARE - The business of IoT
www.bs
> | I did a CVSUP to 4.3-RC at the weekend and my 250mb parallel zip was
> | still probed just fine when the system booted. I'll play around with it
> | this evening and get back to you.
>
> If you have PS2 mode, please enable it, and let me know if it connects in
> PS2 mode rather than nibble.
13 matches
Mail list logo
