Patch to puc(4) to support Advantech PCI-1602B boards

[Jan Mikkelsen]

Hi,

I have raised a PR (with a patch) to support Advantech PCI-1602B and PCI-1603 
boards.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205359

Is it worth forwarding it to anyone in particular, or should I just be patient?

Thanks,

Jan Mikkelsen

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dev/random warning on 10-STABLE after r292122 up till r292855

[Adam Vande More]

On Mon, Jan 4, 2016 at 3:44 PM, Mark Saad  wrote:

> All
>  At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
> starting at or about r292122  and still up till r292855.
>
> On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
>
> random device not loaded; using insecure entropy
>
> The full dmesg can be seen here
> http://dmesgd.nycbug.org/index.cgi?action=dmesgd=view=2871
>
> I checked in svn and there are no recent changes to sys/dev/random .
>
> Does anyone have any insight into this ?
>

It's more of an informational message about seeding the random number
generator.  Probably man 4 random is the best explanation.



-- 
Adam
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dev/random warning on 10-STABLE after r292122 up till r292855

[Mark Saad]

On Tue, Jan 5, 2016 at 8:45 AM, Adam Vande More 
wrote:

> On Mon, Jan 4, 2016 at 3:44 PM, Mark Saad  wrote:
>
>> All
>>  At NYC*BUG we are looking into a warning seen on FreeBSD 10-STABLE amd64
>> starting at or about r292122  and still up till r292855.
>>
>> On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
>>
>> random device not loaded; using insecure entropy
>>
>> The full dmesg can be seen here
>> http://dmesgd.nycbug.org/index.cgi?action=dmesgd=view=2871
>>
>> I checked in svn and there are no recent changes to sys/dev/random .
>>
>> Does anyone have any insight into this ?
>>
>
> It's more of an informational message about seeding the random number
> generator.  Probably man 4 random is the best explanation.
>
>
>
> --
> Adam
>

Adam
  Not sure why I didn't think of that, thanks for the pointer;  I didn't
see any change in the relevant default sysctls .

On a 10-RELEASE box no warning

[msaad@ny4-c108-nocbox ~]$ uname -a
FreeBSD ny4-c108-nocbox 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon
Nov  2 14:19:39 UTC 2015
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
[msaad@ny4-c108-nocbox ~]$ sysctl kern.random
kern.random.sys.harvest.swi: 1
kern.random.sys.harvest.interrupt: 1
kern.random.sys.harvest.point_to_point: 1
kern.random.sys.harvest.ethernet: 1
kern.random.sys.seeded: 1
kern.random.yarrow.slowoverthresh: 2
kern.random.yarrow.slowthresh: 128
kern.random.yarrow.fastthresh: 96
kern.random.yarrow.bins: 10
kern.random.yarrow.gengateinterval: 10
kern.random.live_entropy_sources:
kern.random.active_adaptor: yarrow
kern.random.adaptors: yarrow,dummy


-
On 10-STABLE with warning

msaad@smokeping:~ % uname -a
FreeBSD smokeping 10.2-STABLE FreeBSD 10.2-STABLE #0 r292855: Tue Dec 29
06:17:50 UTC 2015
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC
amd64
msaad@smokeping:~ % sysctl kern.random
kern.random.sys.harvest.swi: 1
kern.random.sys.harvest.interrupt: 1
kern.random.sys.harvest.point_to_point: 1
kern.random.sys.harvest.ethernet: 1
kern.random.sys.seeded: 1
kern.random.yarrow.slowoverthresh: 2
kern.random.yarrow.slowthresh: 128
kern.random.yarrow.fastthresh: 96
kern.random.yarrow.bins: 10
kern.random.yarrow.gengateinterval: 10
kern.random.live_entropy_sources:
kern.random.active_adaptor: yarrow
kern.random.adaptors: yarrow,dummy



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dev/random warning on 10-STABLE after r292122 up till r292855

[Peter Jeremy]

On 2016-Jan-04 16:44:49 -0500, Mark Saad  wrote:
>On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
>
>random device not loaded; using insecure entropy

When I first noticed this, I investigated and worked out that it's
related to how the random device initialises itself and its data and
entropy sources.  In particular, it reflects the state of the random
device at that point in time, not at any later point when random data
is actually requested.

I agree that the wording of this message could unnecessarily alarm a
sysadmin and think it could be done better.  IMHO, this sort of
alamist message should only be output if there is no decent entropy
source available when the random device is unblocked.

-- 
Peter Jeremy


signature.asc
Description: PGP signature

Re: dev/random warning on 10-STABLE after r292122 up till r292855

[Mark Saad]

On Tue, Jan 5, 2016 at 2:00 PM, Peter Jeremy  wrote:

> On 2016-Jan-04 16:44:49 -0500, Mark Saad  wrote:
> >On boot dmesg logs the following warning not seen on 10.2-RELEASE amd64.
> >
> >random device not loaded; using insecure entropy
>
> When I first noticed this, I investigated and worked out that it's
> related to how the random device initialises itself and its data and
> entropy sources.  In particular, it reflects the state of the random
> device at that point in time, not at any later point when random data
> is actually requested.
>
> I agree that the wording of this message could unnecessarily alarm a
> sysadmin and think it could be done better.  IMHO, this sort of
> alamist message should only be output if there is no decent entropy
> source available when the random device is unblocked.
>
> --
> Peter Jeremy
>

Peter
 I agree it looks like its not really a big deal; what I cant find is what
changed to make this even print out. The commits for this warning are from
a long time ago. Off hand they are from 2014 or 2012. There were no changes
to sys/dev/random in as much time; so I cant figure out what changed to
make this even print out.


-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Can I get an ISO-8859-1 system back

[Lars Eighner]

I upgraded from 9.? to 10.2. I used a custom kernel to avoid vt and raster 
fonts in sc. I updated as many ports as would build.


Now I cannot find an editor that will display my files with accent 
characters correctly. I know the files are still iso-8859-1 because they 
are the same size they were and when I cat them, they have the right 
characters in them. This also shows that my term (cons25l1) can display 
the characters correctly. But joe, joe2, ee, and pico-alpine seem to 
convert them to some kind of UTF mess, with two bytes which display as grey 
blocks.


I have tried using LC_ALL and LANG as en_US.iso-8859-1 in .login_conf, and 
unsetting them, I have tried several screen maps.



How far back do I have to downgrade to eliminate UTF from my system 
entirely? I don't care if I can't run a gui. I just want an editor that 
will open iso-8859-1 as iso-8859-1 and not any 2-byte whatever, and will 
display accented characters correctly, as cat does.


I will never want to use sanskrit or Chinese characters. I just want 
Western European characters and I do not want to waste two bytes on them.
I want to use the VGA characters, which the experiment with cat 
demonstrates are on my video card and do work. I do not want unreadable

raster fonts.


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Can I get an ISO-8859-1 system back

[sthaug]

> I upgraded from 9.? to 10.2. I used a custom kernel to avoid vt and raster 
> fonts in sc. I updated as many ports as would build.
> 
> Now I cannot find an editor that will display my files with accent 
> characters correctly. I know the files are still iso-8859-1 because they 
> are the same size they were and when I cat them, they have the right 
> characters in them. This also shows that my term (cons25l1) can display 
> the characters correctly. But joe, joe2, ee, and pico-alpine seem to 
> convert them to some kind of UTF mess, with two bytes which display as grey 
> blocks.
> 
> I have tried using LC_ALL and LANG as en_US.iso-8859-1 in .login_conf, and 
> unsetting them, I have tried several screen maps.

I use "setenv LC_CTYPE no_NO.ISO8859-1" in my .cshrc (yes, I still use
tcsh), and don't set LANG at all, on my 10.2 systems. This works like a
charm - I can display my Norwegian characters (æøå) both on the command
line and for instance in vi etc. No UTF here.

Not at all sure this works with VGA characters though - I mainly use
remote login via ssh.

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"