Re: Dell Latitude E6540 OpenBSD 6.2 amd64 freezes when adjusting refresh rate using xrandr

[Xianwen Chen]

Dear Mihai,

Although your tone in your email was not pleasant, I would still like to thank 
you for your response, because it contained helpful information, see below.

I have searched around, read, and tried to fix the problem myself for a couple 
of days now. I searched misc's archive on-line and did not find more useful 
email conversations. If you know some messages on misc that contain helpful 
information, could you point me to them?

If you are right that humans are not able to see the difference between 60 Hz 
and 59.95 Hz, then something is wrong with xrandr that the actual refresh rate 
is quite below 60, not as much as 59.95 as reported by xrandr, because I can 
clearly see the flickering. I do not think that this is a minimal thing, 
because the flickering screen makes my head dizzy.

I do not think that there is problem with the connection cable, as there was no 
such problem when the same external monitor is connected to a ThinkPad R52 
using the same VGA cable a couple of days ago. I can check the cable connection 
again tomorrow.

I am sceptical whether there is any other source of distortion. I don't know 
where to start if there should be distortion.

Yours sincerely,
Xianwen

On Tue, Mar 20, 2018 at 6:22 PM, Mihai Popescu 
> wrote:
Hello,

It looks like you have some problems in setting up OpenBSD. The misc@
has some messages with your problems. I think you started on the wrong
foot: using OpenBSD is not like trying to replace Windows or Linux.
Stop making noise of minimal things and try to read more on man pages
and message lists.

 1920x1200 59.95 +

This, compared to 60 Hz is like 0.05 Hz difference. Seriously, can you
grasp that? Can you say the time difference?
Sometimes, the electronics is not able to do a perfect X frequency.

Please, do not say you can see flicker at 60 Hz. No human can do that
until now. If you really see some flickering, it must be from an
imperfect connection cable or other source of distorsion.

Have fun.

Dell Latitude E6540 OpenBSD 6.2 amd64 freezes when adjusting refresh rate using xrandr

[Xianwen Chen]

Dear OpenBSD users,

I run OpenBSD 6.2 amd64 on a Dell Latitude E6540 laptop.

I hook a Dell U2412M monitor to the laptop using VGA port. xrandr recognizes 
the maximum resolution of the external monitor, but the refresh rate is 
slightly below 60:

VGA-1 connected (normal left inverted right x axis y axis)
   1920x1200 59.95 +
   1920x1080 60.00
   1600x1200 60.00
   1680x1050 59.95
   1280x1024 60.02
   1280x960  60.00
   1024x768  60.00
   800x600   60.32
   640x480   60.00
   720x400   70.08

I can visibly see the flickering of the screen on the external monitor. Is this 
because the refresh rate is below 60?

At the back of the monitor, a label states that the monitor supports a 
resolution of 1920x1200 at 60 refresh rate.

I tried to use xrandr to adjust refresh rate. I ran

$ gtf 1920 1200 60

The output is:
  # 1920x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 193.16 MHz
  Modeline "1920x1200_60.00"  193.16  1920 2048 2256 2592  1200 1201 1204 1242  
-HSync +Vsync

$ nice -n 20 xrandr --newmode "1920x1200_60.00" Modeline "1920x1200_60.00"  
193.16  1920 2048 2256 2592  1200 1201 1204 1242  -HSync +Vsync

$ xrandr --addmode VGA-1 1920x1200_60.00

$ xrandr --output VGA-1 --mode 1920x1200_60.00

Then the entire laptop freezes. The keyboard is not responding, nor is the 
mouse or touchpad. The system is somehow running though, as the system 
gracefully shuts down when I press the power button.

Do you have experience with setting up refresh rate on an external monitor?

Yours sincerely,
Xianwen

Re: iwi0: fatal firmware error

[Xianwen Chen]

Dear Stefan and Z Ero,

Thank you.

I do not live in the US and it is very hard to get old parts, because
most of the sellers do to ship to where I live.

I think I can live with the unstable wireless adapter for now. I
probably should have spent less time on-line anyway. If I am too
bothered with it, I will get a USB dongle, I think.

Yours sincerely,
Xianwen

On 3/3/18, Stefan Sperling  wrote:
> On Sat, Mar 03, 2018 at 05:49:33AM -0500, Z Ero wrote:
>> I believe these era Thinkpads will not accept a non-IBM authorized
>> minipci WIFI card without Bios modification.
>>
>> See
>> http://www.thinkwiki.org/wiki/Problem_with_unauthorized_MiniPCI_network_card
>
> The misc/tpwireless port can help work around this on some old Thinkpads.
> Warning: Make sure it's compatible with your model of thinkpad, else it
> could brick the machine. It is known to work fine on the Thinkpad X40.

Re: iwi0: fatal firmware error

[Xianwen Chen]

Dear Stefan,

Thank you. I guess the first step is to find out a way to ask iwi0
driver to output more details of the error, before it could be fixed.
I don't have prior experiences with the iwi0 driver. Do you know how I
can enable a debugger mode, if there is one?

Yours sincerely,
Xianwen

On 3/2/18, Stefan Sperling <s...@stsp.name> wrote:
> On Fri, Mar 02, 2018 at 12:14:14PM +, Xianwen Chen wrote:
>> Dear OpenBSD users,
>>
>> I am running OpenBSD 6.2 i386 on ThinkPad R52. The system has been
>> complaining "iwi0: fatal firmware error" in the past two or three
>> days. I was not aware of the problem before that.
>>
>> The problem can usually be worked around by "ifconfig iwi0 -inet
>> -wpakey -nwkey down" and set it up again. Earlier today, when I was
>> trying to ifconfig iwi0 without setting it down first, the system
>> froze.
>>
>> The strange thing is that I do not see much error message at all,
>> except "iwi0: fatal firmware error". Is there some where I shall look
>> into to find a verbose errror message so that I could post it here to
>> get more help?
>>
>> Yours sincerely,
>> Xianwen
>>
>
> See https://marc.info/?l=openbsd-misc=149894337805012=2

iwi0: fatal firmware error

[Xianwen Chen]

Dear OpenBSD users,

I am running OpenBSD 6.2 i386 on ThinkPad R52. The system has been
complaining "iwi0: fatal firmware error" in the past two or three
days. I was not aware of the problem before that.

The problem can usually be worked around by "ifconfig iwi0 -inet
-wpakey -nwkey down" and set it up again. Earlier today, when I was
trying to ifconfig iwi0 without setting it down first, the system
froze.

The strange thing is that I do not see much error message at all,
except "iwi0: fatal firmware error". Is there some where I shall look
into to find a verbose errror message so that I could post it here to
get more help?

Yours sincerely,
Xianwen

Re: USB SIM-card dongle on OpenBSD

[Xianwen Chen]

Dear Stuart,

Interesting. Thank you for the link! I, however, do not think I have the 
resource to get it to work on OpenBSD currently.

Yours sincerely,
Xianwen

On Fri, Feb 23, 2018 at 8:49 AM, Stuart Henderson 
<s...@spacehopper.org<mailto:s...@spacehopper.org>> wrote:
On 2018-02-22, Marcus MERIGHI 
<mcmer-open...@tor.at<mailto:mcmer-open...@tor.at>> wrote:
> Hello Xianwen,
>
> xianwen.c...@nina.no<mailto:xianwen.c...@nina.no> (Xianwen Chen), 2018.02.22 
> (Thu) 01:49 (CET):
>> I actually do not know. I just have this idea that I would like to use
>> my OpenBSD laptop as a mobile phone as well. I think there are USB
>> dongles that act as GSM network device. I am wondering if I could use
>> such a dongle to operate a SIM card on OpenBSD, to receive/send SMS
>> and to receive/make phone calls.
>
> regarding GSM phone calls: how is the sound going to get from the GSM
> device to your ears? And from your speech output device (aka mouth) to
> the GSM device?
>
> The way I'd try is: network connectivity via GSM modem, run VoIP/SIP
> over that. Have yourself connected to the phone world by some Provider.

You can get voice traffic out of some mobile devices, there is
http://wiki.e1550.mobi/doku.php?id=introduction which is a module for
asterisk (and then you could use a softphone like baresip on the same
machine).

No idea what is required to get it to work on OpenBSD though.

Re: Hard disk controller not recognized

[Xianwen Chen]

Dear Tom,

Booting from a USB dongle works! Thank you!

Yours sincerely,
Xianwen

On Thu, Feb 22, 2018 at 2:37 AM, Tom Smyth 
<tom.sm...@wirelessconnect.eu<mailto:tom.sm...@wirelessconnect.eu>> wrote:
Hi Xianwen,

if you try with the USB Boot device...  you can see if you can load it .

then I suggest you get a compact low profiile USB key  so that it
doenst snag on your bag when putting
the laptop back in the case
Tom

On 22 February 2018 at 02:11, Xianwen Chen 
<xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> wrote:
> Dear Steve,
>
> I agree! Thank you for the advice!
>
> Yours sincerely,
> Xianwen
>
> On Mon, Feb 12, 2018 at 11:27 PM, STeve Andre' 
> <and...@msu.edu<mailto:and...@msu.edu><mailto:and...@msu.edu<mailto:and...@msu.edu>>>
>  wrote:
>
>
> On 02/12/18 12:07, Xianwen Chen wrote:
> Dear OpenBSD users,
>
> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The
> installation was done by taking out the hard drive and hook it through
> a USB reader to another machine.
>
> I boot the hard drive through Legacy Boot menu. The boot process stops with
> root device:
>
> It is possible to boot through bsd.rd. However, the hard drive is not
> recognized there.
>
> Here is the dmesg from bsd.rd:
> [snip]
>
> Xianwen,
>
> Obviously the best thing is for IT to release the BIOS control to you,
> but if they won't, get a USB SATA disk interface, and try to use that.
> Your IT department might have figured out how to interfere with that too, but 
> that might be a solution.  You'd have to keep that external disk and its 
> interface with you, but at least you could use OpenBSD.
>
> --STeve Andre'
>



--
Kindest regards,
Tom Smyth

Mobile: +353 87 6193172<tel:%2B353%2087%206193172>
The information contained in this E-mail is intended only for the
confidential use of the named recipient. If the reader of this message
is not the intended recipient or the person responsible for
delivering it to the recipient, you are hereby notified that you have
received this communication in error and that any review,
dissemination or copying of this communication is strictly prohibited.
If you have received this in error, please notify the sender
immediately by telephone at the number above and erase the message
You are requested to carry out your own virus check before
opening any attachment.

Re: USB SIM-card dongle on OpenBSD

[Xianwen Chen]

Dear Marcus,

Thank you for your suggestion.

I was thinking of using a headset that is connected to the computer to hear and 
speak.

Yours sincerely,
Xianwen

On Thu, Feb 22, 2018 at 9:31 AM, Marcus MERIGHI 
<mcmer-open...@tor.at<mailto:mcmer-open...@tor.at>> wrote:
Hello Xianwen,

xianwen.c...@nina.no<mailto:xianwen.c...@nina.no> (Xianwen Chen), 2018.02.22 
(Thu) 01:49 (CET):
> I actually do not know. I just have this idea that I would like to use
> my OpenBSD laptop as a mobile phone as well. I think there are USB
> dongles that act as GSM network device. I am wondering if I could use
> such a dongle to operate a SIM card on OpenBSD, to receive/send SMS
> and to receive/make phone calls.

regarding GSM phone calls: how is the sound going to get from the GSM
device to your ears? And from your speech output device (aka mouth) to
the GSM device?

The way I'd try is: network connectivity via GSM modem, run VoIP/SIP
over that. Have yourself connected to the phone world by some Provider.

Marcus

> On Wed, Feb 21, 2018 at 1:36 PM, David Anthony 
> <d...@silentsystems.org<mailto:d...@silentsystems.org><mailto:d...@silentsystems.org<mailto:d...@silentsystems.org>>>
>  wrote:
> Xianwen,
>
> Which application would use this SIM-card dongle? Just curious.
>
> Regards,
> dma
>
> > On Feb 21, 2018, at 6:35 AM, Xianwen Chen 
> > <xianwen.c...@nina.no<mailto:xianwen.c...@nina.no><mailto:xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>>>
> >  wrote:
> >
> > Dear OpenBSD users,
> >
> > I am thinking of adding a SIM-card dongle to my laptop so that I can 
> > receive and send SMS, and receive and make phone calls. Do you have prior 
> > experience with that? Which USD dongle do you use?
> >
> > Yours faithfully,
> > Xianwen
>

Re: USB SIM-card dongle on OpenBSD

[Xianwen Chen]

Dear Luis,

That will be fantastic! Thank you!

Yours sincerely,
Xianwen

On Thu, Feb 22, 2018 at 2:05 AM, Luis Coronado 
<lcoron...@ticoit.com<mailto:lcoron...@ticoit.com>> wrote:
I used Huawei and Dlink GSM usb based modems. I don’t recall the models but I 
will look around for the notes I had about that and send it your way.

-luis

On Wed, Feb 21, 2018 at 7:59 PM Xianwen Chen 
<xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> wrote:
Dear Luis,

Thank you. Do you use a USB dongle to drive the SIM card? If yes, which one do 
you use?

Yours sincerely,
Xianwen

On Thu, Feb 22, 2018 at 1:45 AM, Luis Coronado 
<lcoron...@ticoit.com<mailto:lcoron...@ticoit.com><mailto:lcoron...@ticoit.com<mailto:lcoron...@ticoit.com>>>
 wrote:
I used smstools from ports to deliver sms alerts from nagios. There are other 
alternatives as well.

-luis

On Wed, Feb 21, 2018 at 6:59 PM Xianwen Chen 
<xianwen.c...@nina.no<mailto:xianwen.c...@nina.no><mailto:xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>>>
 wrote:
Dear David,

I actually do not know. I just have this idea that I would like to use my 
OpenBSD laptop as a mobile phone as well. I think there are USB dongles that 
act as GSM network device. I am wondering if I could use such a dongle to 
operate a SIM card on OpenBSD, to receive/send SMS and to receive/make phone 
calls.

Yours sincerely,
Xianwen

On Wed, Feb 21, 2018 at 1:36 PM, David Anthony 
<d...@silentsystems.org<mailto:d...@silentsystems.org><mailto:d...@silentsystems.org<mailto:d...@silentsystems.org>><mailto:d...@silentsystems.org<mailto:d...@silentsystems.org><mailto:d...@silentsystems.org<mailto:d...@silentsystems.org>>>>
 wrote:
Xianwen,

Which application would use this SIM-card dongle? Just curious.

Regards,
dma

> On Feb 21, 2018, at 6:35 AM, Xianwen Chen 
> <xianwen.c...@nina.no<mailto:xianwen.c...@nina.no><mailto:xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>><mailto:xianwen.c...@nina.no<mailto:xianwen.c...@nina.no><mailto:xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>>>>
>  wrote:
>
> Dear OpenBSD users,
>
> I am thinking of adding a SIM-card dongle to my laptop so that I can receive 
> and send SMS, and receive and make phone calls. Do you have prior experience 
> with that? Which USD dongle do you use?
>
> Yours faithfully,
> Xianwen

Re: Hard disk controller not recognized

[Xianwen Chen]

Dear Steve,

I agree! Thank you for the advice!

Yours sincerely,
Xianwen

On Mon, Feb 12, 2018 at 11:27 PM, STeve Andre' 
<and...@msu.edu<mailto:and...@msu.edu>> wrote:


On 02/12/18 12:07, Xianwen Chen wrote:
Dear OpenBSD users,

I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The
installation was done by taking out the hard drive and hook it through
a USB reader to another machine.

I boot the hard drive through Legacy Boot menu. The boot process stops with
root device:

It is possible to boot through bsd.rd. However, the hard drive is not
recognized there.

Here is the dmesg from bsd.rd:
[snip]

Xianwen,

Obviously the best thing is for IT to release the BIOS control to you,
but if they won't, get a USB SATA disk interface, and try to use that.
Your IT department might have figured out how to interfere with that too, but 
that might be a solution.  You'd have to keep that external disk and its 
interface with you, but at least you could use OpenBSD.

--STeve Andre'

Re: USB SIM-card dongle on OpenBSD

[Xianwen Chen]

Dear Luis,

Thank you. Do you use a USB dongle to drive the SIM card? If yes, which one do 
you use?

Yours sincerely,
Xianwen

On Thu, Feb 22, 2018 at 1:45 AM, Luis Coronado 
<lcoron...@ticoit.com<mailto:lcoron...@ticoit.com>> wrote:
I used smstools from ports to deliver sms alerts from nagios. There are other 
alternatives as well.

-luis

On Wed, Feb 21, 2018 at 6:59 PM Xianwen Chen 
<xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> wrote:
Dear David,

I actually do not know. I just have this idea that I would like to use my 
OpenBSD laptop as a mobile phone as well. I think there are USB dongles that 
act as GSM network device. I am wondering if I could use such a dongle to 
operate a SIM card on OpenBSD, to receive/send SMS and to receive/make phone 
calls.

Yours sincerely,
Xianwen

On Wed, Feb 21, 2018 at 1:36 PM, David Anthony 
<d...@silentsystems.org<mailto:d...@silentsystems.org><mailto:d...@silentsystems.org<mailto:d...@silentsystems.org>>>
 wrote:
Xianwen,

Which application would use this SIM-card dongle? Just curious.

Regards,
dma

> On Feb 21, 2018, at 6:35 AM, Xianwen Chen 
> <xianwen.c...@nina.no<mailto:xianwen.c...@nina.no><mailto:xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>>>
>  wrote:
>
> Dear OpenBSD users,
>
> I am thinking of adding a SIM-card dongle to my laptop so that I can receive 
> and send SMS, and receive and make phone calls. Do you have prior experience 
> with that? Which USD dongle do you use?
>
> Yours faithfully,
> Xianwen

Re: USB SIM-card dongle on OpenBSD

[Xianwen Chen]

Dear David,

I actually do not know. I just have this idea that I would like to use my 
OpenBSD laptop as a mobile phone as well. I think there are USB dongles that 
act as GSM network device. I am wondering if I could use such a dongle to 
operate a SIM card on OpenBSD, to receive/send SMS and to receive/make phone 
calls.

Yours sincerely,
Xianwen

On Wed, Feb 21, 2018 at 1:36 PM, David Anthony 
<d...@silentsystems.org<mailto:d...@silentsystems.org>> wrote:
Xianwen,

Which application would use this SIM-card dongle? Just curious.

Regards,
dma

> On Feb 21, 2018, at 6:35 AM, Xianwen Chen 
> <xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> wrote:
>
> Dear OpenBSD users,
>
> I am thinking of adding a SIM-card dongle to my laptop so that I can receive 
> and send SMS, and receive and make phone calls. Do you have prior experience 
> with that? Which USD dongle do you use?
>
> Yours faithfully,
> Xianwen

USB SIM-card dongle on OpenBSD

[Xianwen Chen]

Dear OpenBSD users,

I am thinking of adding a SIM-card dongle to my laptop so that I can receive 
and send SMS, and receive and make phone calls. Do you have prior experience 
with that? Which USD dongle do you use?

Yours faithfully,
Xianwen

Re: Segmentation fault when opening a particular PDF file in mupdf

[Xianwen Chen]

Dear Mihai,

Thank you.

I think mupdf supports more file formats than xpdf, which is a benefit for some.

Sincerely,
Xianwen

On Sat, Feb 17, 2018 at 5:13 PM, Mihai Popescu 
> wrote:
> I guess that evince is heavier than mupdf, when I consider its dependent 
> libraries.

Some of that dependencies are already requested by another must have
applications.
mupdf looks like it is written by a company with ties in ghostscript.
Must try it!

Re: Segmentation fault when opening a particular PDF file in mupdf

[Xianwen Chen]

Dear Stuart and Edgar,

Thank you. I am only looking for the most lightweight PDF viewer. I am in the 
process of compiling xpdf now.

Sincerely,
Xianwen

On Sat, Feb 17, 2018 at 5:32 PM, Edgar Pettijohn 
<ed...@pettijohn-web.com<mailto:ed...@pettijohn-web.com>> wrote:


On 02/17/18 07:14, Stuart Henderson wrote:
On 2018-02-17, Xianwen Chen <xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> 
wrote:
Dear Vincent,

Thank you.

I am surprised that mupdf is actually close to 30 MB of size. You are right 
that it is not lightweight in terms of package size.
It has the full PDF renderer in it, unlike evince which just uses poppler for 
that.
Metrics for CJK fonts are compiled in to mupdf too.

I guess that evince is heavier than mupdf, when I consider its dependent 
libraries. I do not know a good way to list evince's dependencies, its 
dependencies' dependencies etc. Do you know how I may check that?
  $ cd /usr/ports/textproc/mupdf
$ make full-run-depends
bzip2-1.0.6p8
freeglut-3.0.0
nghttp2-1.30.0
curl-7.58.0p0
jpeg-1.5.3v0
tiff-4.0.9
lcms2-2.9
graphite2-1.3.10p1
xdg-utils-1.1.2p0
libiconv-1.14p3
gettext-0.19.8.1p1
sqlite3-3.21.0
pcre-8.41
lzo2-2.10
png-1.6.34
jbig2dec-0.11
openjp2-2.3.0
libffi-3.2.1p4
python-2.7.14p0
libelf-0.8.13p4
glib2-2.54.3p0
desktop-file-utils-0.23p0
cairo-1.14.12
harfbuzz-1.7.5

$ cd /usr/ports/graphics/evince
$ make full-run-depends
texlive_texmf-buildset-2017
hicolor-icon-theme-0.17
bzip2-1.0.6p8
lz4-1.8.1.2
libusb1-1.0.21
zziplib-0.13.62p0
cdparanoia-3.a9.8p3
xz-5.2.3p0
detex-2.8.1
dbus-1.12.4v0
dbus-daemon-launch-helper-1.12.4
dbus-1.12.4v0
giflib-5.1.4
jpeg-1.5.3v0
tiff-4.0.9
lcms2-2.9
soundtouch-1.9.2p2
dvi2tty-5.3.1p0
potrace-1.15
iso-codes-3.77
graphite2-1.3.10p1
libdaemon-0.14p1
jasper-2.0.14
t1utils-1.41
libiconv-1.14p3
gettext-0.19.8.1p1
gdbm-1.13
libgpg-error-1.27p1
libassuan-2.5.1p0
libgcrypt-1.8.2p0
libksba-1.3.5p1
aspell-0.60.6.1p5
e2fsprogs-1.42.12p4
libunistring-0.9.7
libidn2-2.0.0p0
libxml-2.9.7
libxslt-1.1.32
libarchive-3.3.2
unzip-6.0p11
fribidi-0.19.7
libass-0.13.7p0
sqlite3-3.21.0
gnome-backgrounds-3.26.2
ghostscript-fonts-8.11p3
libogg-1.3.3
libvorbis-1.3.5
tremor-20120410p1
libtheora-1.1.1p3
flac-1.3.2p1
libsndfile-1.0.27
libbs2b-3.1.0p2
mozilla-dicts-en-GB-1.3p1
hunspell-1.6.1p2
yelp-xsl-3.20.1
libpaper-1.1.24.5
psutils-1.23
ffcall-1.10p3
pcre-8.41
orc-0.4.24p0
libtasn1-4.13p0
ijs-0.35p2
hyphen-2.8.8
gmp-6.1.2p1
libnettle-3.4
opus-1.2.1
libsigsegv-2.12
clisp-2.49p2
unrar-5.50v1
npth-1.5p0
lzo2-2.10
icu4c-58.2p5
png-1.6.34
jbig2dec-0.11
libwebp-0.6.1p0
gd-2.2.5p0
openjp2-2.3.0
libffi-3.2.1p4
python-2.7.14p0
p11-kit-0.23.2p0
gnutls-3.5.18
python-3.6.4
poppler-data-0.4.8
cantarell-fonts-0.100
libelf-0.8.13p4
glib2-2.54.3p0
dconf-0.26.1
gsettings-desktop-schemas-3.24.1
avahi-0.7p1
cups-libs-2.2.6
ghostscript-9.07p7
libspectre-0.2.8p2
ps2eps-1.68p0
desktop-file-utils-0.23p0
shared-mime-info-1.9p0
gdk-pixbuf-2.36.11
gtk-update-icon-cache-3.22.28
djvulibre-3.5.27p2
libnotify-0.7.7
libproxy-0.4.15p0
glib2-networking-2.54.1
libsoup-2.60.3
json-glib-1.4.2
meta-tracker-2.0.3
avahi-0.7p1
geoclue2-2.4.7
cairo-1.14.12
harfbuzz-1.7.5
harfbuzz-icu-1.7.5
texlive_base-2017
harfbuzz-1.7.5
pango-1.40.14
poppler-0.59.0
libgxps-0.2.5p2
libsecret-0.18.5p0
pinentry-1.1.0p0
gnupg-2.2.4
libcroco-0.6.12
librsvg-2.40.20
adwaita-icon-theme-3.26.1
gnome-icon-theme-3.12.0p3
gnome-icon-theme-symbolic-3.12.0p2
atk-2.26.1
gtk+2-2.24.32
gtk-engines2-2.20.2p9
gnome-themes-standard-3.22.3p0
at-spi2-core-2.26.2
at-spi2-atk-2.26.1
gtk+3-3.22.28
gcr-3.20.0p0
gvfs-1.34.2
gnome-desktop-3.26.2
gnome-autoar-0.2.2p0
nautilus-3.26.2
gstreamer1-1.12.4p0
gstreamer1-plugins-base-1.12.4
libmms-0.6.2p4
gstreamer1-plugins-bad-1.12.4
enchant-1.6.1p1
webkitgtk4-2.18.6
yelp-3.26.0p0

I don't know all of your needs but the lightest of the pdf viewers is probably 
xpdf

laptop$ cd /usr/ports/textproc/xpdf
laptop$ make full-run-depends
jpeg-1.5.1p0v0
libiconv-1.14p3
ghostscript-fonts-8.11p3
png-1.6.31
motif-2.3.7

Re: Segmentation fault when opening a particular PDF file in mupdf

[Xianwen Chen]

Dear Stuart,

Thank you! I compiled mupdf and it works like a charm!

I do have one additional question. How do I compile a "flavour" of a package? 
For example, for mupdf, there is mupdf and mupdf-js. I ran "make package" and 
it gave me mupdf. How would I obtain mupdf-js?

Sincerely,
Xianwen

On Fri, Feb 16, 2018 at 11:18 PM, Stuart Henderson 
<s...@spacehopper.org<mailto:s...@spacehopper.org>> wrote:
On 2018-02-16, Xianwen Chen <xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> 
wrote:
> Dear Stuart,
>
> Thank you.
>
> I am interested in trying to build it from ports. I checked OpenBSD's FAQs 
> and did not find information on building packages from ports. Could you point 
> me to a web page or a manual page?
>
> Sincerely,
> Xianwen

First you need to fetch the ports tree from cvs, see
http://www.openbsd.org/anoncvs.html (you want the 6.2-stable ports
tree for this, no need for src or xenocara).

Then cd /usr/ports/textproc/mupdf, "make package" (as a normal user),
then "make install" as root.

Re: Segmentation fault when opening a particular PDF file in mupdf

[Xianwen Chen]

Dear Vincent,

Thank you.

I am surprised that mupdf is actually close to 30 MB of size. You are right 
that it is not lightweight in terms of package size.

I guess that evince is heavier than mupdf, when I consider its dependent 
libraries. I do not know a good way to list evince's dependencies, its 
dependencies' dependencies etc. Do you know how I may check that?

Sincerely,
Xianwen

On Sat, Feb 17, 2018 at 7:42 AM, vincent delft 
<vincent.de...@gmail.com<mailto:vincent.de...@gmail.com>> wrote:
Interesting :-).

By just looking at OpenBSD repositary 
(http://ftp.fr.openbsd.org/pub/OpenBSD/6.2/packages/amd64/)
evince file size is +-10x smaller than mupdf.

Most probably your "lightweight" point of view is not linked to the file size. 
For my own understanding, what are you looking for in term of lightweight ?

regards






On Sat, Feb 17, 2018 at 1:11 AM, Xianwen Chen 
<xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> wrote:
Dear Vincent,

Thank you for the suggestion!

I thought about using evince. I think I can use Firefox to open the document, 
before I obtain an updated mupdf. I use mupdf mainly because it is more 
lightweight than evince.

Sincerely,
Xianwen

On Fri, Feb 16, 2018 at 11:30 PM, vincent delft 
<vincent.de...@gmail.com<mailto:vincent.de...@gmail.com><mailto:vincent.de...@gmail.com<mailto:vincent.de...@gmail.com>>>
 wrote:
Hello,

You could also use evince. (http://openports.se/graphics/evince)
On my machine (openbsd-current) I can open your specific pdf.

regards



On Thu, Feb 15, 2018 at 9:05 PM, Xianwen Chen 
<xianwen.c...@nina.no<mailto:xianwen.c...@nina.no><mailto:xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>>>
 wrote:
Dear Carlin and Erling,
Thank you both!
Yes, I am using 6.2 with mupdf-1.11p1. Then I shall just wait until next 
release and use Firefox to read the document at the moment.
Sincerely,
Xianwen

On Thu, Feb 15, 2018 at 5:13 PM, Erling Westenvik 
<erling.westen...@gmail.com<mailto:erling.westen...@gmail.com><mailto:erling.westen...@gmail.com<mailto:erling.westen...@gmail.com>><mailto:erling.westen...@gmail.com<mailto:erling.westen...@gmail.com><mailto:erling.westen...@gmail.com<mailto:erling.westen...@gmail.com>>>>
 wrote:
On Fri, Feb 16, 2018 at 05:38:11AM +1300, Carlin Bingham wrote:
> On 16/02/2018 4:28 a.m., Xianwen Chen wrote:
> > mupdf crashes and reports segmentation fault when I try to open a
> > particular PDF file:
> > https://brage.bibsys.no/xmlui/bitstream/handle/11250/2440173/SoL-Rapport-2014-06.pdf?sequence=1=y
> >
> > If you use mupdf too, could you try to open the file and see whether
> > mupdf crashes on your computer too? In that way, you can help me
> > understand whether the problem is reproducible.

Opens just fine. See below.

> Are you using 6.2 with mupdf-1.11p1?
> There was a crash that's fixed on -current:
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/textproc/mupdf/patches/patch-source_fitz_load-jpx_c?rev=1.5=text/x-cvsweb-markup

I'm using current as of yesterday, February 14th, here.

Erling

Re: Segmentation fault when opening a particular PDF file in mupdf

[Xianwen Chen]

Dear Vincent,

Thank you for the suggestion!

I thought about using evince. I think I can use Firefox to open the document, 
before I obtain an updated mupdf. I use mupdf mainly because it is more 
lightweight than evince.

Sincerely,
Xianwen

On Fri, Feb 16, 2018 at 11:30 PM, vincent delft 
<vincent.de...@gmail.com<mailto:vincent.de...@gmail.com>> wrote:
Hello,

You could also use evince. (http://openports.se/graphics/evince)
On my machine (openbsd-current) I can open your specific pdf.

regards



On Thu, Feb 15, 2018 at 9:05 PM, Xianwen Chen 
<xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> wrote:
Dear Carlin and Erling,
Thank you both!
Yes, I am using 6.2 with mupdf-1.11p1. Then I shall just wait until next 
release and use Firefox to read the document at the moment.
Sincerely,
Xianwen

On Thu, Feb 15, 2018 at 5:13 PM, Erling Westenvik 
<erling.westen...@gmail.com<mailto:erling.westen...@gmail.com><mailto:erling.westen...@gmail.com<mailto:erling.westen...@gmail.com>>>
 wrote:
On Fri, Feb 16, 2018 at 05:38:11AM +1300, Carlin Bingham wrote:
> On 16/02/2018 4:28 a.m., Xianwen Chen wrote:
> > mupdf crashes and reports segmentation fault when I try to open a
> > particular PDF file:
> > https://brage.bibsys.no/xmlui/bitstream/handle/11250/2440173/SoL-Rapport-2014-06.pdf?sequence=1=y
> >
> > If you use mupdf too, could you try to open the file and see whether
> > mupdf crashes on your computer too? In that way, you can help me
> > understand whether the problem is reproducible.

Opens just fine. See below.

> Are you using 6.2 with mupdf-1.11p1?
> There was a crash that's fixed on -current:
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/textproc/mupdf/patches/patch-source_fitz_load-jpx_c?rev=1.5=text/x-cvsweb-markup

I'm using current as of yesterday, February 14th, here.

Erling

Re: Segmentation fault when opening a particular PDF file in mupdf

[Xianwen Chen]

Dear Stuart,

Thank you.

I am interested in trying to build it from ports. I checked OpenBSD's FAQs and 
did not find information on building packages from ports. Could you point me to 
a web page or a manual page?

Sincerely,
Xianwen

On Thu, Feb 15, 2018 at 11:37 PM, Stuart Henderson 
<s...@spacehopper.org<mailto:s...@spacehopper.org>> wrote:
On 2018-02-15, Xianwen Chen <xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> 
wrote:
> Dear Carlin and Erling,
> Thank you both!
> Yes, I am using 6.2 with mupdf-1.11p1. Then I shall just wait until next 
> release and use Firefox to read the document at the moment.
> Sincerely,
> Xianwen

BTW I've just backported this fix to the 6.2-stable ports tree if you're
happy with building from ports.. (Will need to wait a couple of hours for
anoncvs mirrors to catch up).

Re: Segmentation fault when opening a particular PDF file in mupdf

[Xianwen Chen]

Dear Carlin and Erling,
Thank you both!
Yes, I am using 6.2 with mupdf-1.11p1. Then I shall just wait until next 
release and use Firefox to read the document at the moment.
Sincerely,
Xianwen

On Thu, Feb 15, 2018 at 5:13 PM, Erling Westenvik 
<erling.westen...@gmail.com<mailto:erling.westen...@gmail.com>> wrote:
On Fri, Feb 16, 2018 at 05:38:11AM +1300, Carlin Bingham wrote:
> On 16/02/2018 4:28 a.m., Xianwen Chen wrote:
> > mupdf crashes and reports segmentation fault when I try to open a
> > particular PDF file:
> > https://brage.bibsys.no/xmlui/bitstream/handle/11250/2440173/SoL-Rapport-2014-06.pdf?sequence=1=y
> >
> > If you use mupdf too, could you try to open the file and see whether
> > mupdf crashes on your computer too? In that way, you can help me
> > understand whether the problem is reproducible.

Opens just fine. See below.

> Are you using 6.2 with mupdf-1.11p1?
> There was a crash that's fixed on -current:
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/textproc/mupdf/patches/patch-source_fitz_load-jpx_c?rev=1.5=text/x-cvsweb-markup

I'm using current as of yesterday, February 14th, here.

Erling

Re: Firefox (and SeaMonkey) automatically creates a Desktop folder in $HOME

[Xianwen Chen]

Dear Jim and Tobias,

It worked like charm! Thank you very much for helping me solve the problem!

Sincerely,
Xianwen

On Thu, Feb 15, 2018 at 6:00 PM, Tobias Ulmer 
<tobi...@tmux.org<mailto:tobi...@tmux.org>> wrote:
On Wed, Feb 14, 2018 at 07:42:53AM -0700, James Anderson wrote:
> Xianwen,
>
> If you create ~/.config/user-dirs.dirs with the following lines it will
> prevent Firefox from creating those folders:
>
> XDG_DESKTOP_DIR="$HOME"
> XDG_DOCUMENTS_DIR="$HOME"
> XDG_DOWNLOAD_DIR="$HOME"

Needs to be "$HOME/" exactly:
https://cgit.freedesktop.org/xdg/xdg-user-dirs/tree/xdg-user-dir-lookup.c#n126

>
>
> Jim
>
> On Wed, Feb 14, 2018 at 7:23 AM, Xianwen Chen 
> <xianwen.c...@nina.no<mailto:xianwen.c...@nina.no>> wrote:
>
> > Dear OpenBSD users,
> >
> > I find that Firefox and SeaMonkey automatically create a Desktop folder in
> > $HOME directory. I do not use Desktop folder in fvwm and I do not want it.
> > You probably encountered the same problem. How can this behavior of Firefox
> > be disabled?
> >
> > Sincerely,
> > Xianwen
> >

Segmentation fault when opening a particular PDF file in mupdf

[Xianwen Chen]

Dear OpenBSD users,

mupdf crashes and reports segmentation fault when I try to open a particular 
PDF file: 
https://brage.bibsys.no/xmlui/bitstream/handle/11250/2440173/SoL-Rapport-2014-06.pdf?sequence=1=y

If you use mupdf too, could you try to open the file and see whether mupdf 
crashes on your computer too? In that way, you can help me understand whether 
the problem is reproducible.

Sincerely,
Xianwen

Firefox (and SeaMonkey) automatically creates a Desktop folder in $HOME

[Xianwen Chen]

Dear OpenBSD users,

I find that Firefox and SeaMonkey automatically create a Desktop folder in 
$HOME directory. I do not use Desktop folder in fvwm and I do not want it. You 
probably encountered the same problem. How can this behavior of Firefox be 
disabled?

Sincerely,
Xianwen

Re: Hard disk controller not recognized

[Xianwen Chen]

Dear Mestre,

Thank you. I agree!

Sincerely,
Xianwen

On 2/12/18, Ricardo Mestre <ser...@helheim.mooo.com>
<ser...@helheim.mooo.com> wrote:
> Hi Xianwen,
>
> I guess this is one of "you're-on-your-own" cases, the BIOS being locked by
> IT I'm even surprised you're allowed to install a different OS on the
> machine.
>
> For starters I'd speak directly with them and check what are you allowed or
> not to do with the machine.
>
> /mestre
>
> On Monday, 12 February 2018, Xianwen Chen wrote:
>> Dear Mike,
>>
>> From the output of dmesg, I guess so. The BIOS is locked by IT
>> administrators. Is there some way that I can use OpenBSD while the
>> controller is set to RAID mode?
>>
>> Sincerely,
>> Xianwen
>>
>> On 2/12/18, Mike Larkin <mlar...@azathoth.net> wrote:
>> > On Mon, Feb 12, 2018 at 05:07:15PM +, Xianwen Chen wrote:
>> >> Dear OpenBSD users,
>> >>
>> >> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The
>> >> installation was done by taking out the hard drive and hook it through
>> >> a USB reader to another machine.
>> >>
>> >> I boot the hard drive through Legacy Boot menu. The boot process stops
>> >> with
>> >> root device:
>> >>
>> >> It is possible to boot through bsd.rd. However, the hard drive is not
>> >> recognized there.
>> >>
>> >> Here is the dmesg from bsd.rd:
>> >>
>> >> OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct  3 21:26:51 MDT 2017
>> >>
>> >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
>> >> real mem = 17064423424 (16273MB)
>> >> avail mem = 16543502336 (15777MB)
>> >> mainbus0 at root
>> >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries)
>> >> bios0: vendor Dell Inc. version "A16" date 01/18/2016
>> >> bios0: Dell Inc. Latitude E6330
>> >> acpi0 at bios0: rev 2
>> >> acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR
>> >> ASF! SSDT SLIC BGRT
>> >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>> >> cpu0 at mainbus0: apid 0 (boot processor)
>> >> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz
>> >> cpu0:
>> >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
>> >> cpu0: 256KB 64b/line 8-way L2 cache
>> >> cpu0: TSC frequency 2891029960 Hz
>> >> cpu0: apic clock running at 99MHz
>> >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
>> >> cpu at mainbus0: not configured
>> >> cpu at mainbus0: not configured
>> >> cpu at mainbus0: not configured
>> >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
>> >> acpiprt0 at acpi0: bus 0 (PCI0)
>> >> acpiprt1 at acpi0: bus -1 (P0P1)
>> >> acpiprt2 at acpi0: bus 1 (RP01)
>> >> acpiprt3 at acpi0: bus 2 (RP02)
>> >> acpiprt4 at acpi0: bus -1 (RP05)
>> >> acpiprt5 at acpi0: bus 11 (RP06)
>> >> acpiprt6 at acpi0: bus -1 (RP07)
>> >> acpiprt7 at acpi0: bus -1 (RP08)
>> >> acpiprt8 at acpi0: bus -1 (PEG0)
>> >> acpiprt9 at acpi0: bus -1 (PEG1)
>> >> acpiprt10 at acpi0: bus -1 (PEG2)
>> >> acpiprt11 at acpi0: bus -1 (PEG3)
>> >> acpiprt12 at acpi0: bus 3 (RP03)
>> >> acpiprt13 at acpi0: bus 7 (RP04)
>> >> acpiec0 at acpi0
>> >> acpicpu at acpi0 not configured
>> >> acpitz at acpi0 not configured
>> >> "INT3F0D" at acpi0 not configured
>> >> "DLLK0533" at acpi0 not configured
>> >> "DLL0533" at acpi0 not configured
>> >> "PNP0401" at acpi0 not configured
>> >> "SMO8810" at acpi0 not configured
>> >> "*pnp0c14" at acpi0 not configured
>> >> "PNP0C0D" at acpi0 not configured
>> >> "PNP0C0C" at acpi0 not configured
>> >> "PNP0C0E" at acpi0 not configured
>> >> "ACPI0003" at acpi0 not configured
>> >> "PNP0C0A" at acpi0 not configured
>> >> "PNP0C0A" at acpi0 not configured
>> >> "PNP0C0A"

Re: Hard disk controller not recognized

[Xianwen Chen]

Dear Peter,

Thank you. There is probably such an option in BIOS. Unfortunately I
do not have access to BIOS at the moment, because it is locked by
administrators of my IT department.

Sincerely,
Xianwen

On 2/12/18, Peter N. M. Hansteen <pe...@bsdly.net> wrote:
> On 02/12/18 18:07, Xianwen Chen wrote:
>> Dear OpenBSD users,
>>
>> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The
>> installation was done by taking out the hard drive and hook it through
>> a USB reader to another machine.
>>
>> I boot the hard drive through Legacy Boot menu. The boot process stops
>> with
>> root device:
>>
>> It is possible to boot through bsd.rd. However, the hard drive is not
>> recognized there.
>
> I'm guessing that for some reason or the other the controller is set to
> 'hardware raid' mode (which OpenBSD does not support) instead of a more
> useful SATA mode:
>
>> pciide0 at pci0 dev 31 function 2 "Intel 82801HBM RAID" rev 0x04: DMA,
>> channel 0 wired to native-PCI, channel 1 wired to native-PCI
>> pciide0: using apic 2 int 19 for native-PCI interrupt
>
> See if the BIOS offers a choice of modes for the controller, hopefully
> there is a SATA option.
>
> - Peter
>
> --
> Peter N. M. Hansteen, member of the first RFC 1149 implementation team
> http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
> "Remember to set the evil bit on all malicious network traffic"
> delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
>

Re: Hard disk controller not recognized

[Xianwen Chen]

Thank you Mike!

Sincerely,
Xianwen

On 2/12/18, Mike Larkin <mlar...@azathoth.net> wrote:
> On Mon, Feb 12, 2018 at 05:25:57PM +, Xianwen Chen wrote:
>> Dear Mike,
>>
>> >From the output of dmesg, I guess so. The BIOS is locked by IT
>> administrators. Is there some way that I can use OpenBSD while the
>> controller is set to RAID mode?
>>
>> Sincerely,
>> Xianwen
>>
>
> not that I know of
>
>> On 2/12/18, Mike Larkin <mlar...@azathoth.net> wrote:
>> > On Mon, Feb 12, 2018 at 05:07:15PM +, Xianwen Chen wrote:
>> >> Dear OpenBSD users,
>> >>
>> >> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The
>> >> installation was done by taking out the hard drive and hook it through
>> >> a USB reader to another machine.
>> >>
>> >> I boot the hard drive through Legacy Boot menu. The boot process stops
>> >> with
>> >> root device:
>> >>
>> >> It is possible to boot through bsd.rd. However, the hard drive is not
>> >> recognized there.
>> >>
>> >> Here is the dmesg from bsd.rd:
>> >>
>> >> OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct  3 21:26:51 MDT 2017
>> >>
>> >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
>> >> real mem = 17064423424 (16273MB)
>> >> avail mem = 16543502336 (15777MB)
>> >> mainbus0 at root
>> >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries)
>> >> bios0: vendor Dell Inc. version "A16" date 01/18/2016
>> >> bios0: Dell Inc. Latitude E6330
>> >> acpi0 at bios0: rev 2
>> >> acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR
>> >> ASF! SSDT SLIC BGRT
>> >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>> >> cpu0 at mainbus0: apid 0 (boot processor)
>> >> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz
>> >> cpu0:
>> >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
>> >> cpu0: 256KB 64b/line 8-way L2 cache
>> >> cpu0: TSC frequency 2891029960 Hz
>> >> cpu0: apic clock running at 99MHz
>> >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
>> >> cpu at mainbus0: not configured
>> >> cpu at mainbus0: not configured
>> >> cpu at mainbus0: not configured
>> >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
>> >> acpiprt0 at acpi0: bus 0 (PCI0)
>> >> acpiprt1 at acpi0: bus -1 (P0P1)
>> >> acpiprt2 at acpi0: bus 1 (RP01)
>> >> acpiprt3 at acpi0: bus 2 (RP02)
>> >> acpiprt4 at acpi0: bus -1 (RP05)
>> >> acpiprt5 at acpi0: bus 11 (RP06)
>> >> acpiprt6 at acpi0: bus -1 (RP07)
>> >> acpiprt7 at acpi0: bus -1 (RP08)
>> >> acpiprt8 at acpi0: bus -1 (PEG0)
>> >> acpiprt9 at acpi0: bus -1 (PEG1)
>> >> acpiprt10 at acpi0: bus -1 (PEG2)
>> >> acpiprt11 at acpi0: bus -1 (PEG3)
>> >> acpiprt12 at acpi0: bus 3 (RP03)
>> >> acpiprt13 at acpi0: bus 7 (RP04)
>> >> acpiec0 at acpi0
>> >> acpicpu at acpi0 not configured
>> >> acpitz at acpi0 not configured
>> >> "INT3F0D" at acpi0 not configured
>> >> "DLLK0533" at acpi0 not configured
>> >> "DLL0533" at acpi0 not configured
>> >> "PNP0401" at acpi0 not configured
>> >> "SMO8810" at acpi0 not configured
>> >> "*pnp0c14" at acpi0 not configured
>> >> "PNP0C0D" at acpi0 not configured
>> >> "PNP0C0C" at acpi0 not configured
>> >> "PNP0C0E" at acpi0 not configured
>> >> "ACPI0003" at acpi0 not configured
>> >> "PNP0C0A" at acpi0 not configured
>> >> "PNP0C0A" at acpi0 not configured
>> >> "PNP0C0A" at acpi0 not configured
>> >> "DELLABCE" at acpi0 not configured
>> >> "PNP0C31" at acpi0 not configured
>> >> pci0 at mainbus0 bus 0
>> >> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09
>> >> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 40

Re: Hard disk controller not recognized

[Xianwen Chen]

Dear Mike,

>From the output of dmesg, I guess so. The BIOS is locked by IT
administrators. Is there some way that I can use OpenBSD while the
controller is set to RAID mode?

Sincerely,
Xianwen

On 2/12/18, Mike Larkin <mlar...@azathoth.net> wrote:
> On Mon, Feb 12, 2018 at 05:07:15PM +0000, Xianwen Chen wrote:
>> Dear OpenBSD users,
>>
>> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The
>> installation was done by taking out the hard drive and hook it through
>> a USB reader to another machine.
>>
>> I boot the hard drive through Legacy Boot menu. The boot process stops
>> with
>> root device:
>>
>> It is possible to boot through bsd.rd. However, the hard drive is not
>> recognized there.
>>
>> Here is the dmesg from bsd.rd:
>>
>> OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct  3 21:26:51 MDT 2017
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
>> real mem = 17064423424 (16273MB)
>> avail mem = 16543502336 (15777MB)
>> mainbus0 at root
>> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries)
>> bios0: vendor Dell Inc. version "A16" date 01/18/2016
>> bios0: Dell Inc. Latitude E6330
>> acpi0 at bios0: rev 2
>> acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR
>> ASF! SSDT SLIC BGRT
>> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
>> cpu0 at mainbus0: apid 0 (boot processor)
>> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz
>> cpu0:
>> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
>> cpu0: 256KB 64b/line 8-way L2 cache
>> cpu0: TSC frequency 2891029960 Hz
>> cpu0: apic clock running at 99MHz
>> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
>> cpu at mainbus0: not configured
>> cpu at mainbus0: not configured
>> cpu at mainbus0: not configured
>> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
>> acpiprt0 at acpi0: bus 0 (PCI0)
>> acpiprt1 at acpi0: bus -1 (P0P1)
>> acpiprt2 at acpi0: bus 1 (RP01)
>> acpiprt3 at acpi0: bus 2 (RP02)
>> acpiprt4 at acpi0: bus -1 (RP05)
>> acpiprt5 at acpi0: bus 11 (RP06)
>> acpiprt6 at acpi0: bus -1 (RP07)
>> acpiprt7 at acpi0: bus -1 (RP08)
>> acpiprt8 at acpi0: bus -1 (PEG0)
>> acpiprt9 at acpi0: bus -1 (PEG1)
>> acpiprt10 at acpi0: bus -1 (PEG2)
>> acpiprt11 at acpi0: bus -1 (PEG3)
>> acpiprt12 at acpi0: bus 3 (RP03)
>> acpiprt13 at acpi0: bus 7 (RP04)
>> acpiec0 at acpi0
>> acpicpu at acpi0 not configured
>> acpitz at acpi0 not configured
>> "INT3F0D" at acpi0 not configured
>> "DLLK0533" at acpi0 not configured
>> "DLL0533" at acpi0 not configured
>> "PNP0401" at acpi0 not configured
>> "SMO8810" at acpi0 not configured
>> "*pnp0c14" at acpi0 not configured
>> "PNP0C0D" at acpi0 not configured
>> "PNP0C0C" at acpi0 not configured
>> "PNP0C0E" at acpi0 not configured
>> "ACPI0003" at acpi0 not configured
>> "PNP0C0A" at acpi0 not configured
>> "PNP0C0A" at acpi0 not configured
>> "PNP0C0A" at acpi0 not configured
>> "DELLABCE" at acpi0 not configured
>> "PNP0C31" at acpi0 not configured
>> pci0 at mainbus0 bus 0
>> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09
>> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09
>> wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
>> xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi
>> usb0 at xhci0: USB revision 3.0
>> uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
>> 3.00/1.00 addr 1
>> "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
>> em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address
>> b8:ca:3a:d8:5f:2e
>> ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int
>> 16
>> usb1 at ehci0: USB revision 2.0
>> uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev
>> 2.00/1.00 addr 1
>> "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not
>> configured
>> ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 

Hard disk controller not recognized

[Xianwen Chen]

Dear OpenBSD users,

I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The
installation was done by taking out the hard drive and hook it through
a USB reader to another machine.

I boot the hard drive through Legacy Boot menu. The boot process stops with
root device:

It is possible to boot through bsd.rd. However, the hard drive is not
recognized there.

Here is the dmesg from bsd.rd:

OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct  3 21:26:51 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 17064423424 (16273MB)
avail mem = 16543502336 (15777MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries)
bios0: vendor Dell Inc. version "A16" date 01/18/2016
bios0: Dell Inc. Latitude E6330
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR
ASF! SSDT SLIC BGRT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2891029960 Hz
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus -1 (RP05)
acpiprt5 at acpi0: bus 11 (RP06)
acpiprt6 at acpi0: bus -1 (RP07)
acpiprt7 at acpi0: bus -1 (RP08)
acpiprt8 at acpi0: bus -1 (PEG0)
acpiprt9 at acpi0: bus -1 (PEG1)
acpiprt10 at acpi0: bus -1 (PEG2)
acpiprt11 at acpi0: bus -1 (PEG3)
acpiprt12 at acpi0: bus 3 (RP03)
acpiprt13 at acpi0: bus 7 (RP04)
acpiec0 at acpi0
acpicpu at acpi0 not configured
acpitz at acpi0 not configured
"INT3F0D" at acpi0 not configured
"DLLK0533" at acpi0 not configured
"DLL0533" at acpi0 not configured
"PNP0401" at acpi0 not configured
"SMO8810" at acpi0 not configured
"*pnp0c14" at acpi0 not configured
"PNP0C0D" at acpi0 not configured
"PNP0C0C" at acpi0 not configured
"PNP0C0E" at acpi0 not configured
"ACPI0003" at acpi0 not configured
"PNP0C0A" at acpi0 not configured
"PNP0C0A" at acpi0 not configured
"PNP0C0A" at acpi0 not configured
"DELLABCE" at acpi0 not configured
"PNP0C31" at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09
vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09
wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
3.00/1.00 addr 1
"Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address
b8:ca:3a:d8:5f:2e
ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
"Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not configured
ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi
pci2 at ppb1 bus 2
iwn0 at pci2 dev 0 function 0 "Intel Centrino Ultimate-N 6300" rev
0x35: msi, MIMO 3T3R, MoW, address 3c:a9:f4:01:ed:24
ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi
pci3 at ppb2 bus 3
ppb3 at pci0 dev 28 function 3 "Intel 7 Series PCIE" rev 0xc4: msi
pci4 at ppb3 bus 7
ppb4 at pci0 dev 28 function 5 "Intel 7 Series PCIE" rev 0xc4: msi
pci5 at ppb4 bus 11
sdhc0 at pci5 dev 0 function 0 vendor "O2 Micro", unknown product
0x8221 rev 0x05: apic 2 int 17
sdhc0: SDHC 2.0, 50 MHz base clock
sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, dma
ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 21
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev
2.00/1.00 addr 1
"Intel QM77 LPC" rev 0x04 at pci0 dev 31 function 0 not configured
pciide0 at pci0 dev 31 function 2 "Intel 82801HBM RAID" rev 0x04: DMA,
channel 0 wired to native-PCI, channel 1 wired to native-PCI
pciide0: using apic 2 int 19 for native-PCI interrupt
"Intel 7 Series SMBus" rev 0x04 at pci0 dev 31 function 3 not configured
isa0 at mainbus0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay1
uhub3 at uhub1 port 1 configuration 1 interface 0 

Re: xterm not showing Norwegian alphabet

[Xianwen Chen]

Dear Ingao,

Thank you!

I am very interested in implementing UTF-8 input into csh(1).  Would you agree 
that a good startig point would be to look at how your implemented UTF-8 
support in ksh(1)?

I tried to find your commit on GitHub, which implement UTF-8 support in ksh(1). 
I could not find it. Was the change commited to a file in src/bin/ksh/? Which 
file was it? Do you remember the approximate time of the implementation? Such 
information will be helpful for me to find the implementation and to study it.

Sincerely,
Xianwen

On Sun, Feb 11, 2018 at 3:54 AM, Ingo Schwarze 
<schwa...@usta.de<mailto:schwa...@usta.de>> wrote:
Hi Xianwen Chen,

Xianwen Chen wrote on Sat, Feb 10, 2018 at 10:41:19PM +:

> I use C shell, csh. When I change the shell to Bourne shell, sh,

On OpenBSD, sh(1) is not a Bourne shell, but the same binary
as ksh(1), a Korn shell, which is reasonably POSIX-compatible
with various extensions.  You can see that with ls -i.

> I am able to type [non-ASCII characters].
>
> Could you check whether you can reproduce my problem by
> entering csh and typing [non-ASCII characters].

Some time ago, i hacked into ksh(1) and added minimal UTF-8 support
to both emacs and vi input mode, with very little disruption to the
existing code base.  I didn't bother to do anything similar for csh(1);
whatever Theo may say, it is not a very modern shell IMHO...  ;)

I did not test, but i would be very surprised if csh(1) were able
to work sensibly with UTF-8 input.  Of course, i wouldn't object
to similar work being done in csh(1).

> I think I would like to file a bug report.

Please don't, it is already well-known that no UTF-8 support was
added to OpenBSD csh(1).

Yours,
  Ingo

Re: xterm not showing Norwegian alphabet

[Xianwen Chen]

Dear Erling,

Thank you.

I did that. I actually set both LC_ALL and LC_CTYPE.

It was helpful that you stated it worked for you. I used your
information and investigated more. It turned out that the problem was
in the shell that I use.

I use C shell, csh. When I change the shell to Bourne shell, sh, I am
able to type æ, ø, and å.

Could you check whether you can reproduce my problem by entering csh
and typing æ, ø, and å? If it is confirmed, I think I would like to
file a bug report.

Sincerely,
Xianwen

On 2/10/18, Erling Westenvik <erling.westen...@gmail.com> wrote:
> On Sat, Feb 10, 2018 at 07:33:20PM +, Xianwen Chen wrote:
>> I am however not able to show or type Norwegian alphabet of ø, å, and
>> æ. ø is shown as C8. å is shown as C%. And æ is shown is C&.
>
> See https://www.openbsd.org/faq/faq8.html#locales. Take note of the
> following:
>
>   If logging in via xenodm(1), add export LC_CTYPE="en_US.UTF-8"
>   to your ~/.xsession before starting the window manager.
>
> Add the export command to the startup file (before invoking any window
> manager) and restart X. This at least solved my problems with Norwegian
> characters.
>
> Regards,
> Erling
>
>> I tried to copi ø, å, and æ from SeaMonkey to xterm. The same thing
>> happens.
>>
>> I tried to copy C8, C%, and C& from xterm back to SeaMonkey. They
>> remained two characters as C8, C%, and C&.
>>
>> Please help.
>>
>> Sincerely,
>> Xianwen

xterm not showing Norwegian alphabet

[Xianwen Chen]

Dear list,
I have a freshly installed OpenBSD 6.2 i386, with the following
environmental setting:

$env

LOGNAME=oe
WINDOWPATH=ttyC4
HOME=/home/oe
DISPLAY=:0
LC_ALL=en_US.UTF-8
PATH=/home/xc/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games:.
SHELL=/bin/csh
USER=oe
TERM=xterm
WINDOWID=8388621
XTERM_VERSION=XTerm/OpenBSD(330)
XTERM_LOCALE=en_US.UTF-8
XTERM_SHELL=/bin/csh
PWD=/home/oe
LC_CTYPE=en_US.UTF-8
EXINIT=set ai sm noeb

I am however not able to show or type Norwegian alphabet of ø, å, and
æ. ø is shown as C8. å is shown as C%. And æ is shown is C&.

I tried to copi ø, å, and æ from SeaMonkey to xterm. The same thing happens.

I tried to copy C8, C%, and C& from xterm back to SeaMonkey. They
remained two characters as C8, C%, and C&.

Please help.

Sincerely,
Xianwen

Re: iwi0 firmware error

[Xianwen Chen]

Hello Stefan,

Thank you very much! iwi0 works well with the newly compiled kernel!

Warm regards,

Xianwen

On 07/10/16 13:18, Stefan Sperling wrote:

On Sun, Jul 10, 2016 at 02:28:32AM +0200, Xianwen Chen wrote:

Hello,

I have not been able to use iwi0 on OpenBSD 5.9 i386 on ThinkPad R52.

The firmware was installed via
# fw_update

When I try to connect to an open wifi network:
# ifconfig iwi0 nwid HUAZHU-Hanting up

I obtain the following error messages when I run 'dmesg':

iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: fatal firmware error

The wireless network adapter worked a few days ago, when the laptop was
running Windows XP.

What shall I do to make iwi0 working?

Warm regards,

Xianwen


iwi(4) was accidentally broken in 5.9-release.

There is a patch in 5.9-stable which makes iwi(4) work again.
No errata was issued for this patch. I've included the patch below.

If you already have a CVS checkout from the OPENSD_5_9 tag, then the
steps you can follow are:

   cd /usr/src/sys
   cvs up net80211/ieee80211_node.c
   Now build and install a new kernel.

For more information about how to get the -stable source tree and how
to build the system from source, see http://www.openbsd.org/faq/faq5.html

Index: ieee80211_node.c
===
RCS file: /cvs/src/sys/net80211/ieee80211_node.c,v
retrieving revision 1.99
retrieving revision 1.99.2.1
diff -u -p -r1.99 -r1.99.2.1
--- ieee80211_node.c25 Jan 2016 15:14:22 -  1.99
+++ ieee80211_node.c5 May 2016 09:41:33 -   1.99.2.1
@@ -630,6 +630,8 @@ ieee80211_end_scan(struct ifnet *ifp)
goto notfound;
(*ic->ic_node_copy)(ic, ic->ic_bss, selbs);
ni = ic->ic_bss;
+
+   ic->ic_curmode = ieee80211_chan2mode(ic, ni->ni_chan);
  
  	if (ic->ic_flags & IEEE80211_F_RSNON)

ieee80211_choose_rsnparams(ic);

iwi0 firmware error

[Xianwen Chen]

Hello,

I have not been able to use iwi0 on OpenBSD 5.9 i386 on ThinkPad R52.

The firmware was installed via
# fw_update

When I try to connect to an open wifi network:
# ifconfig iwi0 nwid HUAZHU-Hanting up

I obtain the following error messages when I run 'dmesg':

iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: fatal firmware error

The wireless network adapter worked a few days ago, when the laptop was 
running Windows XP.


What shall I do to make iwi0 working?

Warm regards,

Xianwen

Text processor with a versioning feature like Google Docs

[Xianwen Chen]

Hi folks,

I like the versioning feature in Google Docs a lot. There I can review
past revisions of a document, which were generated automatically. In
LibreOffice Writer, such a feature can be improvised if I change the
user name in options each time I want to start a revision. That's not
convenient. Do you know if there is a text processor that has a
similar versioning feature like Google Docs?

Thanks!

Xianwen
--
Xianwen Chen x.che...@gmail.com
+47 984 21 622 | +1 307 223 2032
Student of economics
Norwegian University of Life Sciences

Re: Text processor with a versioning feature like Google Docs

[Xianwen Chen]

Great solution! Thank you Jan!

Xianwen
--
Xianwen Chen x.che...@gmail.com
+47 984 21 622 | +1 307 223 2032
Student of economics
Norwegian University of Life Sciences


On Thu, May 30, 2013 at 5:02 PM, Jan Stary h...@stare.cz wrote:

 vi(1) + cvs(1)

Re: Text processor with a versioning feature like Google Docs

[Xianwen Chen]

Great to know. Thank you Oldak!

Xianwen
--
Xianwen Chen x.che...@gmail.com
+47 984 21 622 | +1 307 223 2032
Student of economics
Norwegian University of Life Sciences


On Thu, May 30, 2013 at 8:11 PM, Oldak Quill oldakqu...@gmail.com wrote:

 emacs integrates well with version control too:

 https://www.gnu.org/software/emacs/manual/html_node/emacs/Version-Control-Systems.html

Suggestion for a more detailed manual for vi

[Xianwen Chen]

Hi,

I'm learning to use vi. I find that the buffer operation is different in 
vi than vim. For example, in vim, it is  ':bn', ':bp', and ':bd' to go  
to next and previous buffer, and to close a buffer. Vi does not seem to 
have them implemented.


Because of the  popularity of vim, a lot of documents that I found 
on-line are vim specific, like the example. I don't know how  to edit 
multiple files at once. I use ':e file' name and  vi closes current file 
before opening the new file.


I'll appreciate any suggestion. Thanks in advance!

Kind regards,

Xianwen

Re: Suggestion for a more detailed manual for vi

[Xianwen Chen]

Ted Unangst wrote:
I think the easiest option is to install vim and use that. 
I was going for  that option. I asked the question on the list anyway. I 
thought I might have missed something.

In general, our policy is to only document features that exist.
The list of features that don't exist would be a neverending list. If
you are reading something other than official openbsd documentation,
it's your responsibility to verify that it's correct.
I agree with you. The manual shall only display implemented functions. 
So there isn't a way to edit multiple documents with only one vi 
instance. This is a deal breaker for my day-to-day use of text editor. I 
need to yank between documents.


Trying to figure vi out on OpenBSD has been though.

Kind regards,

Xianwen

fetchmail SMTP error: 553 5.1.8

[Xianwen Chen]

Hi,

I use fetchmail to download emails. Some emails are with domain names 
that cannot be resolved by DNS server. Fetchmail prompts the SMTP error  
code 553 5.1.8 that 'domain of sender address does not exist'.


I guess this error code is from sendmail which refuses to rely emails 
with invalid domain names. Can I configure sendmail to not check domain 
name validility?


Kind regards,

Xianwen

Versioning file system?

[Xianwen Chen]

Hi fellas,

I'm looking for a versioning file system or a comparative 
implementation. The idea is that I want to store file changes for some 
periods of time. I also want to be able to delete earliest few periods' 
file changes when the harddisk is almost full.


I couldn't find information on availability of versioning file system in 
OpenBSD. Did I missi something?


Kind regards,

Xianwen

Re: Versioning file system?

[Xianwen Chen]

skrev Rodrigo Mosconi:


CVS? RCS?

Thank you. I believe CVS will work for my purpose!

Re: Versioning file system?

[Xianwen Chen]

skrev Zé Loff:

Not sure, but it sounds like you are looking for something like this:
http://blog.interlinked.org/tutorials/rsync_time_machine.html
Using rsync to create snapshots is amazing. I didn't know that I could 
do this. Thank you very much!

Re: Versioning file system?

[Xianwen Chen]

skrev L. V. Lammert

Much more useful than a time machine lookalike: rsnapshot

  http://www.rsnapshot.org/

No fancy gui (who needs it?), .. configurage for as may versions as you
like - hourly, daily, weekly, yearly, and keep each as long as you wish.

The key is using hardlinks on the target filesystem, so browse to any date
(e.g. daly.0) and you have a complete directory listing.

It's not CVS, but in some cases it is more usable.

Lee

Thank you Lee. I would go for rsnapshot if I didn't read
http://blog.interlinked.org/tutorials/rsync_time_machine.html
and
http://www.mikerubel.org/computers/rsync_snapshots/
for an hour before seeing your email. I now understand the method of 
configuring rsync to make snapshots. I think I will write my own script 
based on these two web pages.


Xianwen