Re: Russian in NetbSD 7.0

[Mike]

On Mon, Sep 12, 2016 at 04:47:04PM +, Michael van Elst wrote:
> saa...@gmx.com (Capitan Nemo) writes:
> 
> >So I feel there is time to move on UTF-8 on NetBSD too, and it seems
> >NetBSD 6 has ru_RU.UTF-8 support, however it is still is not complete.
> 
> Yes, neither is the locale complete nor does the console support UTF-8.
> But you should be able to use UTF-8 filenames in an X environment.
That's true - it's working very well for me.

> >LANG="ru_RU.UTF-8"
> >LC_CTYPE="ru_RU.UTF-8"
> >LC_COLLATE="C"
> >LC_TIME="C"
> >LC_NUMERIC="C"
> >LC_MONETARY="C"
> >LC_MESSAGES="ru_RU.UTF-8
> 
> >This cause cyrillic filenamse being shown good, but I cannot access it,
> >because shell print hex code (f.e. \:\262\321\320) instead of letters.
> >Bash is 4.3.0(1) out of the box. (By the way https://wiki.netbsd.org/unicode/
> >says it will work out of the box)
> 
> Dunno about 'bash', but the NetBSD shell should support an UTF-8 locale.
>
Absolutely sure that NetBSD shell should support it). 
Nevertheless I don't know what's the reason can lead to such troubles...
Because all netbsd-shells(bash is among them) that I tested are working 
correctly with utf-8 encoded russian filenames!
(In console these files are still stay accesible - I'm just not able to
see it's names)

Re: Phoronix 8-way-BSD-install - NetBSD bombed

[David Brownlee]

On 11 September 2016 at 23:13, Michael van Elst  wrote:
> lingvofact...@gmail.com ("Andrei M.") writes:
>
>>> That's why it might be interesting to find out why ahcisata fails for you.
>
>>Are there any kernel debug facilities on the installation distro?
>
> Not much. You can boot the kernel with the -x parameter, but capturing
> the dmesg output without a serial console is difficult.

If the system can probe the USB devices OK then another option might
be to boot a USB image, either an install or a full live image. You
should be able to exit the installer and then run dmesg into a file,
and copy (ftp?) it somewhere.

(you could also boot the CD with ahcisata switched to compat and
install onto a USB device then switch it back and boot the USB device
if you want to get a full install, but probably booting one of the
existing USB images would be fine).

Re: Russian in NetbSD 7.0

[Michael van Elst]

saa...@gmx.com (Capitan Nemo) writes:

>So I feel there is time to move on UTF-8 on NetBSD too, and it seems
>NetBSD 6 has ru_RU.UTF-8 support, however it is still is not complete.

Yes, neither is the locale complete nor does the console support UTF-8.
But you should be able to use UTF-8 filenames in an X environment.

>LANG="ru_RU.UTF-8"
>LC_CTYPE="ru_RU.UTF-8"
>LC_COLLATE="C"
>LC_TIME="C"
>LC_NUMERIC="C"
>LC_MONETARY="C"
>LC_MESSAGES="ru_RU.UTF-8

>This cause cyrillic filenamse being shown good, but I cannot access it,
>because shell print hex code (f.e. \:\262\321\320) instead of letters.
>Bash is 4.3.0(1) out of the box. (By the way https://wiki.netbsd.org/unicode/
>says it will work out of the box)

Dunno about 'bash', but the NetBSD shell should support an UTF-8 locale.

-- 
-- 
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."

kernel load failure

[Patrick Welche]

I have 2 laptops with identical cases if not identical internals. One is
my everyday -current/amd64 laptop. I have been trying to netboot the
other one which keeps failing to load the kernel over nfs, at the stage
where the twiddle is still printing the first number. (I think there are
normally 3.)

pxeboot_bin and the kernels are all a few day old -current/amd64.
I tried GENERIC, GENERIC with DEBUG (no extra printing), a compressed
GENERIC, and the kernel from the working laptop. Repeating the
netboot, the load would always stop at the same place for that
kernel. (Different places for different kernels, so not "network
transferred given number of bytes".) Compressed and corresponding
uncompressed kernels stop at the same place. I also tried a
GENERIC/i386 kernel (in case of "can't cope with instruction XXX"),
and the same happened.

On a whim, I tried

  FreeBSD-11.0-CURRENT-amd64-20150716-r285616-bootonly.iso.xz

which successfully netbooted.

Any suggestions on what might be going on?

Cheers,

Patrick

How to enable squid-pf

[Rodolfo Edgar]

Hi guys,

I want to use mode transparent with squid and pf, the default install
squid3 with pkgsrc and pkgin does not enable squid-pf, I am going to
see via pkgsrc make show-options that, help me please how enable
--enable-pf-transparent to squid3, thanks a lot.

I am using NetBSD 6.1.5

Russian in NetbSD 7.0

[Capitan Nemo]

Hello!

My servers keep many files in cyrillic naming. Serving big user loads
it is hard to keep files in old encodings with outside world is already
living in UTF-8. Storing files not in UTF-8 cause some problems with Samba
and fatal problems with Linux & NFS, which don't have conversions at all.

So I feel there is time to move on UTF-8 on NetBSD too, and it seems
NetBSD 6 has ru_RU.UTF-8 support, however it is still is not complete.

Fresh installed 6.1.4 can store files in UTF-8. It also can share these
via SMB or NFS, but I can't make it work in shell.

As I see it has support only for LC_CTYPE and LC_MESSAGES via locale.alias
having no native ru_RU.UTF-8 support.

My linux rxvt-unicode terminal (working locally as expected) with ssh to
NetBSD box show:

[***@gloria ~]$ locale
LANG="ru_RU.UTF-8"
LC_CTYPE="ru_RU.UTF-8"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="ru_RU.UTF-8

This cause cyrillic filenamse being shown good, but I cannot access it,
because shell print hex code (f.e. \:\262\321\320) instead of letters.
Bash is 4.3.0(1) out of the box. (By the way https://wiki.netbsd.org/unicode/
says it will work out of the box)

Two questions on that:

Am I right and aliasing ru_RU.UTF-8 to en_US.UTF-8 make this that bad?

If I am right - what I shall do to complete ru_RU.UTF-8 locale and have
no problems in writing cyrillic filenames?

Intel Iris Pro 580 under NetBSD

[Benny Siegert]

Hi!

I admit that I don’t know much about Intel graphics these days. My machine has 
an Intel Iris Pro 580 graphics adapter. Running X crashes the machine: I get an 
empty screen with text mode cursor, then it becomes unresponsive.

I tried setting the driver to „vesa“, but the result is the same.

When the kernel boots, it does not change to a framebuffer console, as it did 
on my old machine with a Radeon. Does this mean that KMS is not working (which 
is needed for the Intel drivers, right?)?

What is the correct incantation to get X on this card? Even un-accelerated 
graphics would be preferable to a crash.

—Benny.