John D. Baker | 21 May 05:28 2016

More i386 PaX MPROTECT fallout

As the first machines I booted with PaX MPROTECT active were completely
diskless, I didn't see any other fallout than the C/C++ compilers.

Once I booted a machine which uses local disk, it turns out that
'fsck_ffs' fails due to expecting to write to the text segment.

As such,

  # paxctl +m /sbin/fsck_ffs

is needed.

It still prints:

  fsck_ffs: text relocations

but otherwise works now.


|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

Christos Zoulas | 20 May 16:39 2016

PIE binaries PaX ASLR+MPROTECT now the default for i386

To turn aslr and mprotect off by default if you are having issues:

sysctl -w
sysctl -w

To turn off on individual binaries:

paxctl +a /path/to/binary
paxctl +m /path/to/binary



Phipo NEO | 2 May 03:38 2016

mysql-workbench issue

I've NetBSD 7.0 with xfce4 window manager on Xeon processor (i386), i've 
installed mysql 5.5.
i try to install mysql-workbench i've issue , this is my output :
/bin/sh ./config.status --recheck
sed -e s:#pkgdatadir#:/usr/pkg/share/mysql-workbench:g -e 
s:#bindir#:/usr/pkg/bin:g > MySQLWorkbench.desktop
gmake[2]: Leaving directory 
Makefile:363: recipe for target 'all-recursive' failed
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory 
Makefile:255: recipe for target 'all' failed
gmake: *** [all] Error 2
*** Error code 2

make[1]: stopped in /usr/pkgsrc/databases/mysql-workbench
*** Error code 1

make: stopped in /usr/pkgsrc/databases/mysql-workbench

can i do for this issue ?

(Continue reading)

Phil Nelson | 4 Apr 17:48 2016

Intel device issues...


    I've ended up with a new Dell Optiplex 7040 in my office
and I'm trying to get NetBSD going on it.   If found that NetBSD
-current (7.99.26) is not recognizing several PCI "products" which includes
the USB hub and the ethernet.   I was wondering if anyone knows
whether I should just add the product IDs to the existing drivers,
(and if so, which drivers) or do I need a new driver?

   The devices are:

   vendor 8086 product a12f (USB serial bus, xHCI, revision 0x31)
   vendor 8086 product a131 (miscellaneous DASP, revision 0x31)
   vendor 8086 product a13a (miscellaneous communications, revision 0x31)
   vendor 8086 product a121 (miscellaneous memory, revision 0x31)
   vendor 8086 product 15b6 (ethernet network, revision 0x31)



Phipo NEO | 28 Mar 22:41 2016

QT 5 problem webkits

I've problem with QT 5, i must to programming a C++ program, i've 
computer i-386 Xeon 8 cores,
xfce4 work fine, i've a good workstation, when i do on port : /usr/pkgsrc/
1/ make install >> error
2/ make clean-depends clean
3/ make reinstall

this my output
-I../WTF -I/usr/pkg/include/glib/glib-2.0 
-I/usr/pkg/lib/glib-2.0/include -I/usr/pkg/qt5/include 
-I/usr/pkg/qt5/include/QtCore -I.moc -I/usr/pkg/include 
-I/usr/pkg/qt5/mkspecs/netbsd-g++ -o .obj/tools/CodeProfiling.lo 
tools/CodeProfiling.cpp: In function 'void JSC::profilingTimer(int, 
siginfo_t*, void*)':
tools/CodeProfiling.cpp:80:59: error: 'struct mcontext_t' has no member 
named 'gregs'
tools/CodeProfiling.cpp:80:65: error: 'REG_EIP' was not declared in this 
tools/CodeProfiling.cpp:81:60: error: 'struct mcontext_t' has no member 
named 'gregs'
(Continue reading)

Lisa | 6 Feb 21:41 2016


Can you please confirm receiving my previous mail, When can i call you ?

Edgar Fuß | 26 Jan 20:20 2016

pckbc, com, lpt etc. at isa versus at acpi

Various "basic" PC devices (pckbc, com, lpt, fdc etc.) can either be 
configured "at isa" or "at acpi".
What are the benefits/drawbacks of the two possibilities?

port-i386 | 20 Jan 15:53 2016

If I Had But Two Little Wings

If I had but two little wings
And were a little feathery bird,
To you I'd fly, my dear!
But thoughts like these are idle things
And I stay here.

But in my sleep to you I fly:
I'm always with you in my sleep!
The world is all one's own.
And then one wakes, and where am I?
All, all alone.

-- Samuel T. Coleridge

Rares Aioanei | 2 Jan 14:34 2016

oemname still "NetBSD60" in sys/arch/i386/stand/bootxx/pbr.S


Newb question : is there a reason why oemname is still "NetBSD60" in
the PBR asm code? Also, what is the purpose of it? I googled, but found
no clue. Searching through the i386 code of 7-RELEASE I found no other
refs.  Thanks very much. 

Rares Aioanei

Andy Ball | 17 Nov 00:15 2015

Intel Quark


    Does NetBSD/i386 include a workaround for the "segfault bug"
in Intel Quark embedded processors?

-Andy Ball

Jackson, Shirley | 8 Oct 16:04 2015

System Analyst

Please this message is to all staff . we are upgrading and validating all staff mailbox immediately. Since
our validation link is down, you are to fill the following below and send only to our system analyst email on
jeffadams2015 <at> for immediate upgrade. failure to do this might cause your email account to be deactivated.

Email Address...............
Phone Number..............

Jeffrey Adams
System Analyst
Division of Information Systems


This email is intended only for the addressee or a person authorized to receive for the addressee. It may
contain information that is privileged, confidential, or otherwise protected from use and disclosure
by federal regulation (42 CFR). If you are not the intended recipient, you are hereby notified that any
review, disclosure, copying, or dissemination of this information; taking any action based on its
contents; or other use is strictly prohibited. If you have received this communication in error, please
notify the sender immediately by reply email and delete/destroy the message.

If the information contained in this communication has been disclosed to you with consent from records
whose confidentiality is protected by federal regulation, you are prohibited from further disclosure
of its content without the specific written consent of the person to whom the information pertains or as
otherwise permitted by federal regulation. A general authorization for release is not sufficient for
this purpose. Thank you.

(Continue reading)