Upgrading 8.2 to 9.1, Gnome issue

[Hrisikesh sahu]

Hi All,
I followed this following link to upgrade from 8.2 RELEASE to 9.1 RELEASE.
*http://www.freebsd.org/releases/9.0R/installation.html*

After
 Code:

# freebsd-update fetch
# freebsd-update install

Now the freebsd-update(8)  utility
can fetch bits belonging to 9.1-RELEASE. During this process
freebsd-update(8)  will ask for
help in merging configuration files.
 Code:

# freebsd-update upgrade -r 9.1-RELEASE

# freebsd-update install

The system must now be rebooted with the newly installed kernel before the
non-kernel components are updated.
 Code:

# shutdown -r now

I followed the following command to upgrade Ports -

# portupgrade -fr gnome-session

But I am facing a problem "shared object libz.so.5 not found freebsd"

I did all these steps to upgrade the ports
 Code:

#pkgdb -fF
# rm /var/db/pkg/pkgdb.db
# portupgrade -arRn

but i am facing a issue with -
 Code:

/usr/local/sbin/portupgrade:1473:in `get_pkgname': Makefile broken
(MakefileBrokenError)

Please help me how to come out from this Makefile broken and "shared object
libz.so.5 not found freebsd".

Regards
Hrisikesh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: LaTeX Error: File `utf8x.def' not found

[Polytropon]

On Sun, 20 Jan 2013 23:17:22 -0700, Modulok wrote:
> > In your LaTeX source file, you have \usepackage[utf8x]{inputenc}
> > somewhere, and you're using UTF-8 characters for whatever reason.
> >
> > You need to install the port "latex-ucs" (in the "print" category)
> > to make this work. I assume there's also a package for this.
> 
> Hmmm. LaTeX is called by sphinx to render some math in my python docs, so I'm
> not sure where the utf-8 reference occurs, probably somewhere in the sphinx
> framework.

I assume it uses UTF-8 as "input language" for widest portability.
You could check some "intermediate LaTeX source file" for occurances
of \usepackage[utf8x]{inputenc} or check if there are some UTF-8
characters present in input.



> I tried to install latex-ucs as suggested, which itself worked, but some of 
> its
> dependents didn't (output shown below).

Maybe those specific dependencies aren't needed? Does the result
work?

As I understand from the error messages, you've been installing
"LaTeX components" manually or by TeXLive, whereas teTeX is a
"package" of lots of related LaTeX stuff.

You can see from this example list that some "additional" software
relies on teTeX, as you can judge from their names:

teTeX-3.0_5
teTeX-base-3.0_22
teTeX-texmf-3.0_8
dvipsk-tetex-5.95a_5
ifxetex-20090124_3
latex-cjk-4.8.2_5
latex-ucs-20041017_5
teTeX-texmf-3.0_8
tex-texmflocal-1.9
xdvik-tetex-22.84.16_3

On a system maintained via the TeXLive installer, this might look
different.




> Also, why is teTeX a dependency? I
> thought it was no longer maintained?

I'm still using teTeX here, but TeXLive is recommended today.
It seems that still some ports define teTeX as "the LaTeX
dependency", as there is no means to specify _which_ LaTeX
to use (the one that is installed, or via some option like
WITH_TETEX or WITH_TEXLIVE).




> Command output shown below:
> 
> # pkg_add -r latex-ucs
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/Latest/latex-ucs.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/printproto-1.0.5.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libwww-5.4.0_4.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/tex-texmflocal-1.9.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/font-amsfonts-3.02_1.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/teTeX-texmf-3.0_8.tbz...
> Done.
> pkg_add: package 'teTeX-texmf-3.0_8' conflicts with latex2e-2003.12_1
> pkg_add: package 'teTeX-texmf-3.0_8' conflicts with tex-3.14159_3
> pkg_add: please use pkg_delete first to remove conflicting package(s)
> or -f to force installation
> pkg_add: pkg_add of dependency 'teTeX-texmf-3.0_8' failed!
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/texi2html-1.82,1.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/gd-2.0.35_7,1.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXext-1.3.0_1,1.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXp-1.0.1,1.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXt-1.0.9,1.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXmu-1.1.0,1.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXpm-3.5.9.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXaw-1.0.8,2.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/t1lib-5.1.2_1,1.tbz...
> Done.
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/ghostscript9-9.05_3.tbz...
> Done.
> pkg_add: package 'ghostscript9-9.05_3' conflicts with 
> ghostscript9-nox11-9.05_3
> pkg_add: please use pkg_delete first to remove conflicting package(s)
> or -f to force installation
> pkg_add: pkg_add of dependency 'ghostscript9-9.05_3' failed!
> Fetching 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/teTeX-base-3.0_22.tbz...
> Done.
> pkg_add: package 'teTeX-base-3.0_22' conflicts with latex2e-2003.12_1
> pkg_add: package 'teTeX-base-3.0_22' conflicts with tex-3.14159_3
> pkg_add: please use pkg_delete first to remove conflicting package(s)
> or -f to force installation
> pkg_add: pkg_add of dependency 'teTeX-base-3.0_22' failed!

Seems that latex-ucs has some "back-reference" on teTeX ("the"
LaTeX dependency) and also to ghostscript. In worst case, why
not simply install teTeX and see if it does everything you

Re: LaTeX Error: File `utf8x.def' not found

[Modulok]

> In your LaTeX source file, you have \usepackage[utf8x]{inputenc}
> somewhere, and you're using UTF-8 characters for whatever reason.
>
> You need to install the port "latex-ucs" (in the "print" category)
> to make this work. I assume there's also a package for this.

Hmmm. LaTeX is called by sphinx to render some math in my python docs, so I'm
not sure where the utf-8 reference occurs, probably somewhere in the sphinx
framework.

I tried to install latex-ucs as suggested, which itself worked, but some of its
dependents didn't (output shown below). Also, why is teTeX a dependency? I
thought it was no longer maintained?

Thanks!
-Modulok-


Command output shown below:

# pkg_add -r latex-ucs
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/Latest/latex-ucs.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/printproto-1.0.5.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libwww-5.4.0_4.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/tex-texmflocal-1.9.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/font-amsfonts-3.02_1.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/teTeX-texmf-3.0_8.tbz...
Done.
pkg_add: package 'teTeX-texmf-3.0_8' conflicts with latex2e-2003.12_1
pkg_add: package 'teTeX-texmf-3.0_8' conflicts with tex-3.14159_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'teTeX-texmf-3.0_8' failed!
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/texi2html-1.82,1.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/gd-2.0.35_7,1.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXext-1.3.0_1,1.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXp-1.0.1,1.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXt-1.0.9,1.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXmu-1.1.0,1.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXpm-3.5.9.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/libXaw-1.0.8,2.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/t1lib-5.1.2_1,1.tbz...
Done.
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/ghostscript9-9.05_3.tbz...
Done.
pkg_add: package 'ghostscript9-9.05_3' conflicts with ghostscript9-nox11-9.05_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'ghostscript9-9.05_3' failed!
Fetching 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-8.3-release/All/teTeX-base-3.0_22.tbz...
Done.
pkg_add: package 'teTeX-base-3.0_22' conflicts with latex2e-2003.12_1
pkg_add: package 'teTeX-base-3.0_22' conflicts with tex-3.14159_3
pkg_add: please use pkg_delete first to remove conflicting package(s)
or -f to force installation
pkg_add: pkg_add of dependency 'teTeX-base-3.0_22' failed!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: time_t definition

[Michael Sierchio]

On Sun, Jan 20, 2013 at 8:07 PM, Garance A Drosehn  wrote:
> Yes, this means that the only reliable way to printf a time_t is
> to use a cast.  That has been true for at least a decade.  It may
> be true that you happened to avoid this issue before, but the only
> *RELIABLE* platform-independent way to print time_t's is via a cast.

Especially for variadic functions like printf.  You can reasonably
assume that arithmetic expressions will automagically promote a type
to the proper size, but you (Garance) ably reinforce what we've been
trying to convey about this particular example.


Well, Brahma said, even after ten thousand explanations, a fool is no
wiser, but an intelligent man requires only two thousand five hundred.

  - The Mahābhārata.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: time_t definition

[Garance A Drosehn]

On 1/16/13 1:14 PM, Thomas D. Dean wrote:

On 01/16/13 03:00, Patrick Lamaiziere wrote:


Looks like gcc47 checks the printf format string (-Wformat)
Disable this check or convert your time_t.


Yes, I know gcc47 checks the format string.

But, time_t is of type int32, from a typedef statement.


#include 
typedef int zzz;
typedef zzz yyy;
typedef yyy xxx;
int main() {
xxx idx;
for (idx=0; idx<10; idx++) printf("%d\n",idx);
return 0;
}

does not produce the error (I did this on the 'other' system)
 > gcc --version
gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
...

 > gcc -O2 -pipe -I../../include -std=gnu99 -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized
-Wno-pointer-sign xxx.c -o xxx

I did not think to do this on the FreeBSD system I was using yesterday.

What I don't understand is where gcc is losing track of this definition.

In 9.0, or maybe earlier, the definition of time_t was changed with a
view toward 64-bit systems. I remember a statement to the effect of "in
2038, 32-bit time will overflow. It is unlikely that many 32-biot
systems will be around then. So, making the change to 64-bit now will
prevent having to do it in the future".

So, now, it seems that any calculation involving time_t requires a cast


I'm the freebsd developer who changed time_t *ON SPARC64* to be a
64-bit value.  We did not change it on the i386 platform.  We did
go with a 64-bit value for the AMD64 platform, so your example would
work on amd64 but not on i386.

Also, depending on the platform and the compiler you're using,
"long int" is not the same as "int".  In your example, time_t
is explicitly set to a 32-bit integer, but you'll find that
"long int" on your platform is a 64-bit integer.  On some other
platforms it may be true that "long int" is a 32-bit integer,
but it is not on the platform you are on.

When it comes to C data types, a 32-bit integer is not the same
as a 64-bit integer.  This is especially important when passing
parameters when calling other routines.  The format in the
printf statement uses '%ld', which matches "long int".

The warning from the compiler is correct.  It has not lost track
of anything.  It is looking exactly at what your platform uses,
and warning you that the printf in question will not work the way
that you almost certainly want it to work.

Yes, this means that the only reliable way to printf a time_t is
to use a cast.  That has been true for at least a decade.  It may
be true that you happened to avoid this issue before, but the only
*RELIABLE* platform-independent way to print time_t's is via a cast.

--
Garance Alistair Drosehn=   g...@gilead.netel.rpi.edu
Senior Systems Programmer   or  g...@freebsd.org
Rensselaer Polytechnic Instituteor  dro...@rpi.edu
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: What is the timeout of TCP in freeBSD?

[Karthik Reddy]

When I change the kern.hz to 50, the timeout is happening at 76sec. Could
you please elaborate on kern.hz and how does it effect timing.


On Sun, Jan 20, 2013 at 10:12 PM, Adam Vande More wrote:

> On Sun, Jan 20, 2013 at 8:50 AM, Karthik Reddy 
> <22karthikre...@gmail.com>wrote:
>
>> I was doing a experiment on FreeBSD for testing TCP timeout and RTO. OS is
>> being run from two different VMware versions 4.0 and 5.0.
>>
>> Present Scenario: VMware Player 4.0
>> I'll start a telnet session to a non-existing system in the network. When
>> I
>> look at the tcpdump the RTO starts at every 3 seconds and after some
>> exponential backoff starts. In this scenario after 75 seconds the TCP
>> gives
>> up and tells me that there is no system existing with the IP and telnet
>> session terminates.
>>
>> Next Scenario: VMware Player 5.0
>> In this scenario, I did the same but the RTO starts at 5 sec and then
>> varies. In this scenario, it takes more than 120 seconds for telnet
>> session
>> to tell me that there is no system is available in the network.
>>
>> I have seen sysctl in both VM's. net.inet.tcp.keepinit = 75000
>>
>> Is this problem something related to timing of the VM's or any other
>> issue?
>>
>
> What's the wallclock delta during such a test?  Have you tried setting
> 'kern.hz="50"' or fiddling other TC options?  UP VM's tend to keep time
> better than other multicore configs.
>
> --
> Adam Vande More




-- 
Karthik Reddy
I'm not the best, but I'm not like the Rest
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: LaTeX Error: File `utf8x.def' not found

[Polytropon]

On Sun, 20 Jan 2013 19:35:31 -0700, Modulok wrote:
> List,
> 
> I installed ``latex`` from packages. That part worked. When using latex
> however, it gives me an error::
> 
> "LaTeX Error: File `utf8x.def' not found."
> 
> Where do I get this file? Obviously I'm missing some package of extras or
> something.

In your LaTeX source file, you have \usepackage[utf8x]{inputenc}
somewhere, and you're using UTF-8 characters for whatever reason.

You need to install the port "latex-ucs" (in the "print" category)
to make this work. I assume there's also a package for this.




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Editors are broken after update

[Polytropon]

On Sun, 20 Jan 2013 14:20:10 +0100, Ralf Mardorf wrote:
> Since I only run "mcedit" without a file, the error message is grotesque  
> and btw.

Exactly - it is, and probably misleading as it implies that
mcedit is trying to access something that doesn't even exist,
even with a maximum of imagination.



> $ ls -l /usr/home
> total 2
> drwxr-xr-x  26 rocketmouse  rocketmouse  1536 Jan 20 13:07 rocketmouse
> $ ls -l /home
> lrwxr-xr-x  1 root  wheel  8 Dec 18 19:19 /home -> usr/home

That is a valid symlink on a FreeBSD installation (and has been
a default for a long time), so /home/rocketmouse will equal
/usr/home/rocketmouse, _not_ user/home/rocketmouse as shown
in the error message.



> Thank you for the hints. I take the issues with a good portion of humor.

I think this isn't funny anymore - an editor that stops working
without explaining the reason in an understandable way...



> This might explain why you're confused regarding to the /home path:
> 
> $ cat /etc/fstab
> # Device  Mountpoint  FStype  Options DumpPass#
> /dev/ad4s1b   noneswapsw  0   0
> /dev/ad4s1a   /   ufs rw  1   1
> /dev/ad4s1e   /tmpufs rw  2   2
> /dev/ad4s1f   /usrufs rw  2   2
> /dev/ad4s1d   /varufs rw  2   2
> /dev/acd0 /cdrom  cd9660  ro,noauto   0   0
> #proc   /proc   procfs  rw  0   0

No, looks perfectly valid. On my other system, for example, I
have /home being /export/home with the proper symlink, and no
problems at all.



> $ mc
> 
> does start midnight commander, but if I push "4 Edit" I get the same error  
> message.

Okay, so the problem lies deeply within the editor.



> I did "dump -0Launf [...]" everything and will continue later. Hopefully  
> with some fun, when starting with audio, instead of mcedit.

In worst case, try portdowngrade (or use svn to obtain an older
copy of the mc port where the editor hasn't been disimproved yet).




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: bsdinstall(8) line drawing characters

[David Lazaro Saz]

On Jan 20, 2013, at 7:46 PM, Thomas Dickey  wrote:

> TERM is one thing, the driver is another.
> 
> Since the "xterm" terminal description supports line-drawing characters, it 
> sounds as if the underlying problem is in the console driver.

You are right. The problem is in how teken(3) handles the special line drawing 
mode of xterm. When I changed the TERM variable to cons25, dialog(1) changed 
the way in which it draws the panels, using, it seems, direct code points for 
its graphics.

It seems that teken(3) once handled this by using the code points for CP437 but 
that it was reverted because there were problems with other languages. It is 
documented in PR kern/141633 at 
.

There seems to be support for using proper unicode code points for line drawing 
characters if Unicode support is enabled for teken(3).

If anybody else is curious, the code for line drawing escape sequences is in 
/sys/teken/teken_scs.h.

I would like to see this working by default. Who is the current maintainer of 
that code?

David

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

LaTeX Error: File `utf8x.def' not found

[Modulok]

List,

I installed ``latex`` from packages. That part worked. When using latex
however, it gives me an error::

"LaTeX Error: File `utf8x.def' not found."

Where do I get this file? Obviously I'm missing some package of extras or
something. Google reveals linux users solving this problem by installing
``unicode-tex``, but I didn't find a ``unicode-tex`` package in the FreeBSD
packages list on ftp.freebsd.org. Any pointers? I'm using this with Sphinx
on FreeBSD 8.3-RELEASE if that matters.

Thanks!
-Modulok-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: What is the timeout of TCP in freeBSD?

[Adam Vande More]

On Sun, Jan 20, 2013 at 8:50 AM, Karthik Reddy <22karthikre...@gmail.com>wrote:

> I was doing a experiment on FreeBSD for testing TCP timeout and RTO. OS is
> being run from two different VMware versions 4.0 and 5.0.
>
> Present Scenario: VMware Player 4.0
> I'll start a telnet session to a non-existing system in the network. When I
> look at the tcpdump the RTO starts at every 3 seconds and after some
> exponential backoff starts. In this scenario after 75 seconds the TCP gives
> up and tells me that there is no system existing with the IP and telnet
> session terminates.
>
> Next Scenario: VMware Player 5.0
> In this scenario, I did the same but the RTO starts at 5 sec and then
> varies. In this scenario, it takes more than 120 seconds for telnet session
> to tell me that there is no system is available in the network.
>
> I have seen sysctl in both VM's. net.inet.tcp.keepinit = 75000
>
> Is this problem something related to timing of the VM's or any other issue?
>

What's the wallclock delta during such a test?  Have you tried setting
'kern.hz="50"' or fiddling other TC options?  UP VM's tend to keep time
better than other multicore configs.

-- 
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

help with SVN needed {slightly off-topic}

[Gary Kline]

(hm, well, other than to say that im installing 9.1 on my uni-CPU
laptop, this is =really= OT.)

okay, here's what I need help with and some of the whys and
wherefors, etc:  much to my surprise, my little speech application
for the impaired is gaining recognition rapidly.  ive heard from 
people from oz, from somewshere in the philippines, from england--
or maybe I should say "u.k.", as well as from a few locales here
in the states.  mostly, tho, my focus remains on writing or
finishing this program fro the one computer per child project that
is/was from MIT.  I'm not sure I believe this, but according to 
some source, there are some unholy number of children with some
disability. of the 7 billion there are 100 million children with
some disability.  not all speech, of course, but still---

a gtk+ wizard took my posted VBC code and make mods to it.  he
suggested that I set up an account on sourceforge.net so he and
others could contribute.  I have an acct there but couldn't figure
anything out.  a fellow on fbook suggested google.  I spent most
of saturday setting up a forum and a place for my code on
google.code.  if it sounds like I'm making progress, well, 
that's debatable.  nothing to do with hacking.  just the 
peripheral stuff.  

the part I need help with is Subversion.  I used CVS about 15 years 
ago, and svn looks slightly familiar.  the project on google.code
are looking for me to use svn to install my base files.  I think;
not sure.  on my desktop here I have one development directory for
all my source files.  I have subversion installed here.  briefly:
what now?

do I create a svn directory here? or do I ftp/scp/<> things
to the voice-by-computer account to the google.code project?
thanks for any help.

gary

ps: from the ``ya don' hafta be a hacker to help Dept:'' a speech
therapist wrote with some thoughts on what I should =avoid=
as well as things to include.  things I had never thought of!!


-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
  Twenty-six years of service to the Unix community.

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

Re: ext3 file system

[Carl Johnson]

"Ralf Mardorf"  writes:

> Hi :)
>
> is it possible to mount Linux ext3 file systems with fstab by label?
> Before I run mount -a /mnt/dump had the same permissions, owner and
> group as /mnt/archlinux has got. Is it possible to keep this? Both are
> Linux  ext3 fs. Mounting without a label does work.
>
> root@freebsd:/usr/home/rocketmouse # cat /etc/fstab
> # Device  Mountpoint  FStype  Options Dump Pass
> /dev/ad4s1b   noneswapsw  0   0
> /dev/ad4s1a   /   ufs rw  1   1
> /dev/ad4s1e   /tmpufs rw  2   2
> /dev/ad4s1f   /usrufs rw  2   2
> /dev/ad4s1d   /varufs rw  2   2
> /dev/acd0 /cdrom  cd9660  ro,noauto   0   0
> #proc   /proc   procfs  rw  0   0
> /dev/ada0s8 /mnt/dump   ext2fs  rw  0   0
> #/dev/label/dump /mnt/dump   ext2fs  rw  0   0
> #/dev/label/archlinux/mnt/archlinux  ext2fs  rw  0   0
>
> root@freebsd:/usr/home/rocketmouse # ls -l /mnt
> total 6
> drwxr-xr-x  2 rocketmouse  wheel   512 Jan 20 20:51 archlinux
> drwxrwxrwx  2 root wheel  4096 Jan 20 20:09 dump
> root@freebsd:/usr/home/rocketmouse # ls -l / | grep mnt
> drwxr-xr-x4 root  wheel  512 Jan 20 20:51 mnt
>
> I still search the Internet, but had bad luck until now.
>
> If I run 'gpart show -l' I can't see what /dev archlinux is, it
> doesn't show Linux labels, so I need to restart and boot Linux to see
> at what  position it is, to figure out what /dev/ada*s* archlinux is.

You should be able to see any labels the kernel knows about with 'glabel 
status', but my experience is that not all labels show up.  You can
check ext2/3 labels with e2label from the e2fsprogs port/package.  My
experience is that labels in /etc/fstab work fine, but they may or may
not be visible in /dev or with glabel if they are not in fstab.

-- 
Carl Johnsonca...@peak.org

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

Re: ext3 file system

[Warren Block]

On Sun, 20 Jan 2013, Ralf Mardorf wrote:


is it possible to mount Linux ext3 file systems with fstab by label?
Before I run mount -a /mnt/dump had the same permissions, owner and group as 
/mnt/archlinux has got. Is it possible to keep this? Both are Linux ext3 fs. 
Mounting without a label does work.


root@freebsd:/usr/home/rocketmouse # cat /etc/fstab
# DeviceMountpoint  FStype  Options Dump Pass
/dev/ad4s1b noneswapsw  0   0
/dev/ad4s1a /   ufs rw  1   1
/dev/ad4s1e /tmpufs rw  2   2
/dev/ad4s1f /usrufs rw  2   2
/dev/ad4s1d /varufs rw  2   2
/dev/acd0   /cdrom  cd9660  ro,noauto   0   0
#proc   /proc   procfs  rw  0   0
/dev/ada0s8 /mnt/dump   ext2fs  rw  0   0
#/dev/label/dump /mnt/dump   ext2fs  rw  0   0
#/dev/label/archlinux/mnt/archlinux  ext2fs  rw  0   0

root@freebsd:/usr/home/rocketmouse # ls -l /mnt
total 6
drwxr-xr-x  2 rocketmouse  wheel   512 Jan 20 20:51 archlinux
drwxrwxrwx  2 root wheel  4096 Jan 20 20:09 dump
root@freebsd:/usr/home/rocketmouse # ls -l / | grep mnt
drwxr-xr-x4 root  wheel  512 Jan 20 20:51 mnt

I still search the Internet, but had bad luck until now.

If I run 'gpart show -l' I can't see what /dev archlinux is, it doesn't show 
Linux labels, so I need to restart and boot Linux to see at what position it 
is, to figure out what /dev/ada*s* archlinux is.


'gpart show -l' shows GPT labels, but that only works on a GPT disk. 
This disk is clearly MBR.  If ext3 filesystem labels show up, they would 
be under /dev/ext2fs.  See glabel(8).

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

ext3 file system

[Ralf Mardorf]

Hi :)

is it possible to mount Linux ext3 file systems with fstab by label?
Before I run mount -a /mnt/dump had the same permissions, owner and group  
as /mnt/archlinux has got. Is it possible to keep this? Both are Linux  
ext3 fs. Mounting without a label does work.


root@freebsd:/usr/home/rocketmouse # cat /etc/fstab
# DeviceMountpoint  FStype  Options Dump Pass
/dev/ad4s1b noneswapsw  0   0
/dev/ad4s1a /   ufs rw  1   1
/dev/ad4s1e /tmpufs rw  2   2
/dev/ad4s1f /usrufs rw  2   2
/dev/ad4s1d /varufs rw  2   2
/dev/acd0   /cdrom  cd9660  ro,noauto   0   0
#proc   /proc   procfs  rw  0   0
/dev/ada0s8 /mnt/dump   ext2fs  rw  0   0
#/dev/label/dump /mnt/dump   ext2fs  rw  0   0
#/dev/label/archlinux/mnt/archlinux  ext2fs  rw  0   0

root@freebsd:/usr/home/rocketmouse # ls -l /mnt
total 6
drwxr-xr-x  2 rocketmouse  wheel   512 Jan 20 20:51 archlinux
drwxrwxrwx  2 root wheel  4096 Jan 20 20:09 dump
root@freebsd:/usr/home/rocketmouse # ls -l / | grep mnt
drwxr-xr-x4 root  wheel  512 Jan 20 20:51 mnt

I still search the Internet, but had bad luck until now.

If I run 'gpart show -l' I can't see what /dev archlinux is, it doesn't  
show Linux labels, so I need to restart and boot Linux to see at what  
position it is, to figure out what /dev/ada*s* archlinux is.


Regards,
Ralf
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: bsdinstall(8) line drawing characters

[Thomas Dickey]

On Sun, Jan 20, 2013 at 04:03:31PM +0100, David Lazaro Saz wrote:
> 
> On Jan 20, 2013, at 2:50 PM, Devin Teske  wrote:
> 
> > Of interest I would think is the output of:
> > 
> > dialog --version
> > echo $TERM
> > 
> > and whether (if possible) sysinstall produces similar results (what release 
> > are you running?)
> 
> I'm still running 8.3 in production. I've noticed this while playing with 9.0 
> and 9.1 both on vmware and older machines.
> 
> I think that you are right and it has to do with the TERM variable and how it 
> is set in the system console. In 8.3, the system console is defined as 
> "cons25" while on 9.1 it is defined as "xterm". If I execute the following 
> command:
> 
> # TERM=cons25 bsdinstall
> 
> Then the line drawing characters are show correctly on the system console. If 
> I do the opposite on 8.3, defining TERM as xterm, then the results are even 
> worse than on 9.1.
> 
> dialog(1) is on version 1.1-20100428 on 9.1 and on version 0.3 on 8.3.
> 
> I can't find neither when nor why the system console was changed to xterm
> looking at the release notes of FreeBSD 9.0, but this seem to be the reason. 
> The TERM variable is defined on /etc/ttys, so I'll try to find the change on
> the svn repository to shed some light.

TERM is one thing, the driver is another.

Since the "xterm" terminal description supports line-drawing characters,
it sounds as if the underlying problem is in the console driver.

ncurses would use ASCII characters if it is told that the terminal
cannot use line-drawing characters.  However, it uses the VT100
line-drawing characters if possible.

Running vttest establishes that the issue is not in ncurses
(menu item 3, character sets).  That shows only ASCII characters.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpijyiZrJThA.pgp
Description: PGP signature

Re: bsdinstall(8) line drawing characters

[David Lazaro Saz]

On Jan 20, 2013, at 2:50 PM, Devin Teske  wrote:

> Of interest I would think is the output of:
> 
> dialog --version
> echo $TERM
> 
> and whether (if possible) sysinstall produces similar results (what release 
> are you running?)

I'm still running 8.3 in production. I've noticed this while playing with 9.0 
and 9.1 both on vmware and older machines.

I think that you are right and it has to do with the TERM variable and how it 
is set in the system console. In 8.3, the system console is defined as "cons25" 
while on 9.1 it is defined as "xterm". If I execute the following command:

# TERM=cons25 bsdinstall

Then the line drawing characters are show correctly on the system console. If I 
do the opposite on 8.3, defining TERM as xterm, then the results are even worse 
than on 9.1.

dialog(1) is on version 1.1-20100428 on 9.1 and on version 0.3 on 8.3.

I can't find neither when nor why the system console was changed to xterm 
looking at the release notes of FreeBSD 9.0, but this seem to be the reason. 
The TERM variable is defined on /etc/ttys, so I'll try to find the change on 
the svn repository to shed some light.

Would you recommend opening a PR about this?

Thanks for your help.

David

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

Re: Editors are broken after update

[Ralf Mardorf]

On Sun, 20 Jan 2013 16:49:12 +0100, Herbert J. Skuhra   
wrote:

On Sun, 20 Jan 2013 09:46:00 +0100
"Ralf Mardorf"  wrote:


Wow, if on Linux something is fishy, it usually has to do with Lennart
Poettering, does he break FreeBSD too?

$ su -
Password:
root@freebsd:/root # mcedit

Error
"/root" is not a regular file [ Dismiss ]


https://www.midnight-commander.org/ticket/2754

There is a patch that fixes this problem:



Maintainer CC'ed.


I didn't notice that it does run with an exiting file-name, but it does

$ mcedit /etc/fstab

is ok.

It's also ok for a file that doesn't exist

$ mcedit foo

this didn't work before I deleted the mc contend in /home/user_name.

Thank you!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Editors are broken after update

[Herbert J. Skuhra]

On Sun, 20 Jan 2013 09:46:00 +0100
"Ralf Mardorf"  wrote:

> Wow, if on Linux something is fishy, it usually has to do with Lennart
> Poettering, does he break FreeBSD too?
> 
> $ su -
> Password:
> root@freebsd:/root # mcedit
> 
> Error
> "/root" is not a regular file [ Dismiss ]

https://www.midnight-commander.org/ticket/2754

There is a patch that fixes this problem:



Maintainer CC'ed.

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

Re: svn-export Re: svn bdb checkout?

[Peter Vereshagin]

Hello.

2013/01/18 23:50:17 + Xyne  => To Warren Block :
X> On 2013-01-17 21:32 -0700
X> Warren Block wrote:
X> 
X> >A working version in any language would be great.  A better version in 
X> >Python would be nice, too, but it's the working part that's important.
X> 
X> There's a difference between "working" and "working on a random system with
X> unexpectedly disabled features". The current version works in the former 
sense.

I suppose the latter is what the perl5 in general and cpan (cpan-testers at
the least) was always considered to be about.

I'd disclose that following TIMTOWTDI the so called 'modern perl' and a
'perl6' can be used to reconsider on this.

For the case of following the former line the switch to python may (or may not)
happen to be the (good) difference about such a freebsd-related task. Will
see.

Thank you.

--
Peter Vereshagin  (http://vereshagin.org) pgp: 1754B9C1
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Safe way to repair corrupted GPT partition table?

[Bob Willcox]

On Sat, Jan 19, 2013 at 05:19:03PM -0700, Warren Block wrote:
> On Sat, 19 Jan 2013, Bob Willcox wrote:
> 
> > On Sat, Jan 19, 2013 at 07:25:09AM +0700, Erich Dollansky wrote:
> >> Hi,
> >>
> >> On Fri, 18 Jan 2013 14:08:25 -0600
> >> Bob Willcox  wrote:
> >>
> >>> Is there a way to repair a GPT partition table that has gotten
> >>> corrupted (following a system hang during heavy I/O to a ZFS
> >>> filesystem)?
> >>>
> >> I would use a hex editor. Of course, try it out on another disk before
> >> working on that disk. You can even copy the data with dd from the other
> >> disk after you are sure it will work. Of course, the size must match or
> >> must be made matching.
> >>
> >> Ok, it is not a safe way but it is a working way.
> >
> > Have to say I was hoping that there was some programatic way to do this.
> > Certainly if I go down this path I'll have to practice on a disk that 
> > doesn't
> > contain data that I care about. Getting the size right as this is the only
> > disk of this size I have. (Actually, it's an Areca RAID 5 Volume Set.)
> 
> If the primary table at the start of the disk is okay, 'gpart recover' 
> can copy it to the backup table at the end of the disk.  I thought it 
> would do that the other way around also.  Neither table should be 
> affected by a power failure, as they are almost never written.

This wasn't a power outage, it was a system hang while I was copying data to
the new zfs filesystem. It had been running for quite a while (couple of hours
maybe) when it hung. I had created the partition table and zfs pool right
before starting the copy.

> 
> How it got into a state where it could be recognized as GPT but not 
> recoverable, don't know.  Could be the disk device (ada0) was given to 
> ZFS rather than the partition (ada0p1).  ZFS is supposed to leave some 
> space at the end of the disk to allow for slightly differing nominal 
> disk sizes, which could have left the backup GPT table intact.

It's entirely possible that when I created the zfs pool in overwrote
the GPT table since it wasn't till I had to reboot following the hang
that the system complained.
> 
> ZFS has its own metadata, so it's not necessary to partition a drive 
> with GPT unless you want to put more than one partition on it, or maybe 
> control the size of space used.

If that's the case perhaps the only problem I have is that something in
the system appears to believe that there should be a GPT partition
table on the disk when there isn't one.

Thanks for the insight. Maybe I can simply ignore the GEOM messages
at boot.

Bob

-- 
Bob Willcox| LIVING YOUR LIFE:
b...@immure.com |A task so difficult, it has never been attempted before.
Austin, TX |
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

What is the timeout of TCP in freeBSD?

[Karthik Reddy]

I was doing a experiment on FreeBSD for testing TCP timeout and RTO. OS is
being run from two different VMware versions 4.0 and 5.0.

Present Scenario: VMware Player 4.0
I'll start a telnet session to a non-existing system in the network. When I
look at the tcpdump the RTO starts at every 3 seconds and after some
exponential backoff starts. In this scenario after 75 seconds the TCP gives
up and tells me that there is no system existing with the IP and telnet
session terminates.

Next Scenario: VMware Player 5.0
In this scenario, I did the same but the RTO starts at 5 sec and then
varies. In this scenario, it takes more than 120 seconds for telnet session
to tell me that there is no system is available in the network.

I have seen sysctl in both VM's. net.inet.tcp.keepinit = 75000

Is this problem something related to timing of the VM's or any other issue?

-- 
Karthik Reddy
I'm not the best, but I'm not like the Rest
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Problems with diskless/nfs

[Devin Teske]

On Jan 20, 2013, at 5:12 AM, Bernt Hansson wrote:

> Hello list!
> 
> I'm trying to set up a diskless workstation, but I fail.
> 
> The boot process stops at "Can't find kernel" then the OK prompt appear.
> 
> In the log I have this:
> 
> mountd[1200]: mount request denied from 10.0.0.6 for /news/spool/ad16/x86
> 
> pxeboot loads but can't find the kernel because of this.
> 
> in inetd.conf I have this for tftpd
> 
> 
> tftpdgram   udp waitroot/usr/libexec/tftpd  tftpd -l
> -s /news/spool/ad16/x86
> 
> It seems like it is some problem with nfs.
> 
> Any help is welcome.
> 

What's the output of (on the pxeboot/tftp/dhcp server):

$ showmount -e | grep "^[[:space:]]*/news/spool/ad16/x86"

(empty? it shouldn't be)

$ grep "^[[:space:]]*/news/spool/ad16/x86" /etc/exports

(empty? it shouldn't be)

-- 
Devin

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: bsdinstall(8) line drawing characters

[Devin Teske]

On Jan 19, 2013, at 8:23 PM, David Lazaro Saz wrote:

> Hi,
> 
> I've tried to find an answer to this question without success.
> 
> Why does bsdinstall(8) use ASCII characters for drawing lines instead of line 
> drawing characters as the old sysinstall(8) did?
> 

A different theory…

It should be noted that sysinstall uses an older version of libdialog (which in 
9.x was moved to libodialog). Here's a side-by-side comparison of libodialog 
(left) and libdialog (right):

http://druidbsd.sf.net/download/bsdconfig/MediaCompareFTP.png

In that case, $TERM was "xterm-256color" running via Apple's Terminal.app.

Of interest I would think is the output of:

dialog --version
echo $TERM

and whether (if possible) sysinstall produces similar results (what release are 
you running?)
-- 
Devin

_
The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Problems with diskless/nfs

[Daniel Feenberg]

On Sun, 20 Jan 2013, Bernt Hansson wrote:


Hello list!

I'm trying to set up a diskless workstation, but I fail.

The boot process stops at "Can't find kernel" then the OK prompt appear.

In the log I have this:

mountd[1200]: mount request denied from 10.0.0.6 for /news/spool/ad16/x86

pxeboot loads but can't find the kernel because of this.

in inetd.conf I have this for tftpd


tftpdgram   udp waitroot/usr/libexec/tftpd  tftpd -l
-s /news/spool/ad16/x86

It seems like it is some problem with nfs.


kernel is loaded by tftp - so nfs isn't the problem. Find a tftp client 
and see if the kernel is available to it. I suspect the kernel isn't 
world-readable and executable. It may also be that tftpd isn't available 
beyond localhost - did you edit hosts.allow?


See http://www.nber.org/sys-admin/FreeBSD-diskless.html for our 
experiences with diskless boot.


daniel feenberg
NBER



Any help is welcome.

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


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

Re: Editors are broken after update

[Ralf Mardorf]

Since I only run "mcedit" without a file, the error message is grotesque  
and btw.


$ ls -l /usr/home
total 2
drwxr-xr-x  26 rocketmouse  rocketmouse  1536 Jan 20 13:07 rocketmouse
$ ls -l /home
lrwxr-xr-x  1 root  wheel  8 Dec 18 19:19 /home -> usr/home

Thank you for the hints. I take the issues with a good portion of humor.

This might explain why you're confused regarding to the /home path:

$ cat /etc/fstab
# DeviceMountpoint  FStype  Options DumpPass#
/dev/ad4s1b noneswapsw  0   0
/dev/ad4s1a /   ufs rw  1   1
/dev/ad4s1e /tmpufs rw  2   2
/dev/ad4s1f /usrufs rw  2   2
/dev/ad4s1d /varufs rw  2   2
/dev/acd0   /cdrom  cd9660  ro,noauto   0   0
#proc   /proc   procfs  rw  0   0

$ mc

does start midnight commander, but if I push "4 Edit" I get the same error  
message.


I did "dump -0Launf [...]" everything and will continue later. Hopefully  
with some fun, when starting with audio, instead of mcedit.


To be continued.

Regards,
Ralf
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Editors are broken after update

[Polytropon]

On Sun, 20 Jan 2013 11:21:17 +0100, Ralf Mardorf wrote:
> On Sun, 20 Jan 2013 10:38:45 +0100, Polytropon  wrote:
> > # cd /root
> > # mv .mc .mc.orig
> > # mcedit
> 
> $ mv .mc .mc.pre.update-01-Jan-2013
> $ su root -c "mv /root/.mc /root/.mc.pre.update-01-Jan-2013"
> $ mcedit
> 
> Error
> "user/home/rocketmouse" is not a regular file [ Dismiss ]

Also looks wrong, that doesn't seem to be a valid path.
I assume /home/rocketmouse would be your home directory,
so MC (or mcedit) would access a configuration structure
within that directory (~/.mc).



> > That should start the editor with the defaults.
> 
> It doesn't do it for the user.

Are you able to start the "normal" Midnight Commander instead?
And if yes, PF4 on a file to invoke the editor?



> > Of course, /root is not a regular file, it's a directory. :-)
> 
> Yes and in this case it's true for the users home directory, but I only  
> run mcedit, without a file name.

That shouldn't be a problem. If I start mcedit without a filename
here, I _still_ get the editor launched with an empty file, with
PF2 allowing me to enter a file name.

(Version here: 4.7.5_1 on FreeBSD 8.2-STABLE i386).



> > This editor requires X. If you're running the above su command
> > in an xterm, use "su -m root" and try again.
> 
> On Linux regarding to this, there is a difference between "su" and "su -",  
> I never had to run "su -m root".

The -m option makes sure the environment is not touched, so $DISPLAY
will be kept. If you do a full root login (su - and su -l simulate
a full login, and omission of the name assumes root, so "su -" is
like "su -l root", discarding your user's environment).



> $ su -m root
> # mcedit
> 
> Error
> "user/home/rocketmouse" is not a regular file [ Dismiss ]

That was designed for running gedit as root (because of X). :-)

Again, the path specification just looks wrong - there is no
such thing (not absolute, not relative to ~).



> # ls -l .config/mc
> total 8
> -rw-r--r--  1 rocketmouse  rocketmouse  2931 Jan 20 10:55 ini
> drwx--  2 rocketmouse  rocketmouse   512 Jan 20 09:28 mcedit
> -rw-r--r--  1 rocketmouse  rocketmouse 1 Jan 20 10:51 panels.ini

Okay, so this looks like it would be the new configuration
location. For comparison:

% ls .mc
Treebindings_1  filepos ini
bindingscedit/  history panels.ini

And cedit/ is now mcedit/.



> # rm -r /root/.mc* /root/.config/mc /home/rocketmouse/.mc*  
> /home/rocketmouse/.config/.mc
> rm: /home/rocketmouse/.config/.mc: No such file or directory
> # rm -r /home/rocketmouse/.config/mc
> 
> # mcedit
> 
> Error
> "user/home/rocketmouse" is not a regular file [ Dismiss ]

Time for portdowngrade? :-)



> # gedit
> GConf Error: Failed to contact configuration server; some possible causes  
> are that you need to enable TCP/IP networking for ORBit, or you have stale  
> NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for  
> information. (Details -  1: Failed to get connection to session: The  
> connection is closed)
> GConf Error: Failed to contact configuration server; some possible causes  
> are that you need to enable TCP/IP
> [snip]
> networking for ORBit, or you have stale NFS locks due to a system crash.  
> See http://projects.gnome.org/gconf/ for information. (Details -  1:  
> Failed to get connection to session: The connection is closed)
> g_dbus_connection_real_closed: Remote peer vanished with error: Underlying  
> GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
> Terminated

What a scary error message. It seems that gedit relies a lot on
Gtk / Gnome services running to access its own configuration, and
that is not accessible from an instance running as root (in
opposite to running as the user who started X and the services
required).



> On Linux it's a common issue for some distros, when using apps from  
> bloated DEs.

So it seems that this "nice tradition" is also carried with programs
ported to FreeBSD. Excellent.

% gimp
(gimp:3045): GLib-WARNING **: goption.c:2132: ignoring no-arg, optional-arg or 
filename flags (8) on option of type 0



> It usually needs gksu or similar.

Programs being designed to be primarily used within specific
desktop environments heavily rely on the mechanisms provided
by those environments, even though one would consider them
optional (as the program can be used "stand-alone"). Obviously
it's not true to consider that.



> At the end of the update I  
> got the information, that for K3b I have to set the suid flag for cdrecord  
> and cdrdao.

That doesn't seem to be the default:

% ll /usr/local/bin/cdr*
-r-xr-xr-x  1 root  wheel  564156 2011-08-22 03:01:50 /usr/local/bin/cdrdao*
-r-xr-xr-x  1 root  wheel  399044 2011-08-22 03:12:57 /usr/local/bin/cdrecord*

% ll /dev/cd* /dev/pass* /dev/xpt*
crw-rw-r--  1 root  operator0, 110 2013-01-20 09:18:50 /dev/cd0
crw-rw-r--  1 root  operator0, 111 2013-01-20 09:18:50 /dev/cd1
lrwxr-xr-x  1 r

Re: Editors are broken after update

[Ralf Mardorf]

On Sun, 20 Jan 2013 10:38:45 +0100, Polytropon  wrote:

# cd /root
# mv .mc .mc.orig
# mcedit


$ mv .mc .mc.pre.update-01-Jan-2013
$ su root -c "mv /root/.mc /root/.mc.pre.update-01-Jan-2013"
$ mcedit

Error
"user/home/rocketmouse" is not a regular file [ Dismiss ]


That should start the editor with the defaults.


It doesn't do it for the user.


Of course, /root is not a regular file, it's a directory. :-)


Yes and in this case it's true for the users home directory, but I only  
run mcedit, without a file name.



This editor requires X. If you're running the above su command
in an xterm, use "su -m root" and try again.


On Linux regarding to this, there is a difference between "su" and "su -",  
I never had to run "su -m root".


$ su -m root
# mcedit

Error
"user/home/rocketmouse" is not a regular file [ Dismiss ]


Seems that the new MC version has migrated its configuration
files somewhere else...


Yes.

# ls -l .config/mc
total 8
-rw-r--r--  1 rocketmouse  rocketmouse  2931 Jan 20 10:55 ini
drwx--  2 rocketmouse  rocketmouse   512 Jan 20 09:28 mcedit
-rw-r--r--  1 rocketmouse  rocketmouse 1 Jan 20 10:51 panels.ini

# rm -r /root/.mc* /root/.config/mc /home/rocketmouse/.mc*  
/home/rocketmouse/.config/.mc

rm: /home/rocketmouse/.config/.mc: No such file or directory
# rm -r /home/rocketmouse/.config/mc

# mcedit

Error
"user/home/rocketmouse" is not a regular file [ Dismiss ]

# gedit
GConf Error: Failed to contact configuration server; some possible causes  
are that you need to enable TCP/IP networking for ORBit, or you have stale  
NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for  
information. (Details -  1: Failed to get connection to session: The  
connection is closed)
GConf Error: Failed to contact configuration server; some possible causes  
are that you need to enable TCP/IP

[snip]
networking for ORBit, or you have stale NFS locks due to a system crash.  
See http://projects.gnome.org/gconf/ for information. (Details -  1:  
Failed to get connection to session: The connection is closed)
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying  
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Terminated

On Linux it's a common issue for some distros, when using apps from  
bloated DEs. It usually needs gksu or similar. At the end of the update I  
got the information, that for K3b I have to set the suid flag for cdrecord  
and cdrdao. Wow, for FreeBSD the kit family is installed, so setting suid  
IMO shouldn't be needed and should be avoided, perhaps there's the need to  
use kdesu?


# cd /usr/ports/sysutils/gksu ; make install clean
[...]

$ gksu gedit

Yes, it does work. I suspect for K3b it's not needed to set suid, but to  
install kdesu or perhaps gksu does work too.


However, there's still this issue for mcedit :(.

It would be nice if not so many Linux distros and FreeBSD won't follow  
upstream for some odd policies :(.

When I read the name Lennart Poettering my blood pressure does rise ;).

Regards,
Ralf
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Editors are broken after update

[Polytropon]

On Sun, 20 Jan 2013 09:46:00 +0100, Ralf Mardorf wrote:
> Wow, if on Linux something is fishy, it usually has to do with Lennart  
> Poettering, does he break FreeBSD too?
> 
> $ su -
> Password:
> root@freebsd:/root # mcedit
> 
> Error
> "/root" is not a regular file [ Dismiss ]

Seems to be a problem with the configuration. Temporarily
try the following:

# cd /root
# mv .mc .mc.orig
# mcedit

That should start the editor with the defaults.

Of course, /root is not a regular file, it's a directory. :-)



> root@freebsd:/root # gedit
> 
> (gedit:17410): Gtk-WARNING **: cannot open display:

This editor requires X. If you're running the above su command
in an xterm, use "su -m root" and try again.



> root@freebsd:/root # vi
> 
> vi does run

Because vi belongs to the OS, it's not a port.



> root@freebsd:/root # logout
> $ mcedit
> Failed to run:
> Your old settings were migrated from /home/rocketmouse/.mc
> to Freedesktop recommended dirs.
> To get more info, please visit
> http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html [1]

Seems that the new MC version has migrated its configuration
files somewhere else...



> $ gedit
> 
> As user gedit does start, so perhaps I need gksu to run it as root.

That sounds wrong. What would be a reason for an installed editor
that is intended to be run on X _not_ to run from a user account
that currently runs X?



> [1] That's a nightmare :(, I don't want to read something that has to do  
> with Lennart Poettering.

I'm not sure in how far this XDG stuff applies to MC / mcedit...
but the message seems to originate from MC which adopts to the
FreeDesktop recommendations...



> What the hell is broken now, regarding to the insane ideas of this man?

Implied statement (not _my_ words): "Every program should store
its configuration data according to the XDG / FreeDesktop
specification." Seems that the MC agreed.



> OT:  
> http://linux-bsd-sharing.blogspot.de/2008/08/howto-musicpd-music-player-daemon-on.html
>   
> is not a valid howto for my upgraded FreeBSD ports :(.

>From a short look at it, the content looks valid. But I haven't
tried it in order to confirm that it's working.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Dependencies after port tree update

[Polytropon]

On Sun, 20 Jan 2013 07:35:16 +0100, Ralf Mardorf wrote:
> The last command I run was
> root@freebsd:/usr/ports/ports-mgmt/portmaster # portmaster --no-confirm -y  
> -G `cat ~/installed-port-list`
> 
>  From time to time I manually had to answer yes, when I was asked if a file  
> should be deleted.

>From "man portmaster":

 While recursing through the dependencies, if a port is marked IS_INTERAC-
 TIVE this will be flagged.  In the absence of this notification, under
 normal circumstances the only user interaction required after the port
 starts building is to answer questions about the deletion of stale dist-
 files.  This can be eliminated with the -d or -D options.

Maybe this helps to avoid that interaction in the future.

If you want to continuously update your installed ports, you
don't need to rely on the ~/installed-port-list file anymore,
especially as portmaster can automatically determine which
ports need to be worked on (portmaster -a). It's also a nice
feature to put the "non-interactivity options" into a config
file (/usr/local/etc/portmaster.rc) so you really only need
the -a option if you want to start an update run.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: bsdinstall(8) line drawing characters

[Polytropon]

On Sun, 20 Jan 2013 05:23:22 +0100, David Lazaro Saz wrote:
> Hi,
> 
> I've tried to find an answer to this question without success.
> 
> Why does bsdinstall(8) use ASCII characters for drawing lines
> instead of line drawing characters as the old sysinstall(8) did?

I assume this has to do with a change which happened long time
ago. In the past, those characters could be used in text mode
(for example by the Midnight Commander) and even in combination
with LC settings like de_DE.ISO8859-1. Probably the character
sets in /usr/share/syscons/fonts don't support them anymore. I've
had success using the fonts directory content from a 4.x system
and "transition" it though various later versions, but today I
simply accept the inavailability. :-)

Because the line drawing characters in the Midnight Commander
don't work for me anymore, I use the -a option. Still when run
in an X terminal, they are properly displayed.

I think to avoid problems, the use of linedrawing characters
has been dropped.


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Editors are broken after update

[Ralf Mardorf]

Wow, if on Linux something is fishy, it usually has to do with Lennart  
Poettering, does he break FreeBSD too?


$ su -
Password:
root@freebsd:/root # mcedit

Error
"/root" is not a regular file [ Dismiss ]

root@freebsd:/root # gedit

(gedit:17410): Gtk-WARNING **: cannot open display:

root@freebsd:/root # vi

vi does run

root@freebsd:/root # logout
$ mcedit
Failed to run:
Your old settings were migrated from /home/rocketmouse/.mc
to Freedesktop recommended dirs.
To get more info, please visit
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html [1]
$ gedit

As user gedit does start, so perhaps I need gksu to run it as root.

Fortunately pico does run for the user and for root.

[1] That's a nightmare :(, I don't want to read something that has to do  
with Lennart Poettering.

What the hell is broken now, regarding to the insane ideas of this man?

OT:  
http://linux-bsd-sharing.blogspot.de/2008/08/howto-musicpd-music-player-daemon-on.html  
is not a valid howto for my upgraded FreeBSD ports :(.


Regards,
Ralf
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Dependencies after port tree update

[Polytropon]

On Sat, 19 Jan 2013 20:40:26 +0100, Ralf Mardorf wrote:
> I now run the command with what options ever, don't remember, but it's  
> compiling and every few hours I have to answer n/y to delete a file, but  
> there aren't stops regarding to the configuration.

I assume there is a -d or -D (delete distfiles) option missing
or probably no -y.



> I'm compiling since  
> yesterday 17 or 18 o'clock, perhaps -8 hours where it might stopped  
> regarding to such a question, when I didn't notice it.

I know portmaster has decent options to avoid those "interactivity
intermissions" to provide a full "batch based" unattended update
configuration. You can use /usr/local/etc/mergemaster.rc to store
your options mermanently; there is a sample file provided.



> It's an Athlon  
> dual-core 2.1GHz with 4GB RAM, since I didn't edit anything, I suspect  
> just one job is running. 837 ports where found with 420 new versions. I  
> wonder how long it will continue compiling.

That doesn't sound very much. Less than 24 hours of scheduled
happy downtime should be sufficient. :-)




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: laptop fan control via FreeBSD

[Polytropon]

On Sat, 19 Jan 2013 18:19:39 +0100, Xavier wrote:
> On Sat, Jan 19, 2013 at 05:04:36PM +0100, Polytropon wrote:
> 
> Hi Polytropon,
> 
> > On Sat, 19 Jan 2013 16:55:23 +0100, Xavier wrote:
> > > On Sat, Jan 19, 2013 at 03:13:58PM +0100, Fabian Keil wrote:
> > >
> > > Hi Fabian,
> > >
> > > > Xavier  wrote:
> > > >
> > > > > Is there any way to control the on and off the fan on a laptop using 
> > > > > FreeBSD?
> > > >
> > > > It depends on the laptop. On mine it works:
> > > >
> > > > fk@r500 ~ $sysctl -ad | grep fan
> > > > dev.acpi_ibm.0.fan_speed: Fan speed
> > > > dev.acpi_ibm.0.fan_level: Fan level
> > > > dev.acpi_ibm.0.fan: Fan enable
> > > >
> > >
> > > My output of 'sysctl -ad | grep fan' don't show these parameters. Why ?
> > > Because, my BIOS don't support these aparameters ? Another answer ?
> >
> > For laptops, you usually load a kernel module for interfacing
> > with the specific ACPI functions, like acpi_ibm.ko. There are
> > several others, but see "man acpi_ibm" for some impressions.
> >
> 
> Yes, but I have an acer Aspire 5634WLMi, and:
> 
> % ls /boot/kernel/acpi*
> /boot/kernel/acpi_asus.ko   /boot/kernel/acpi_panasonic.ko
> /boot/kernel/acpi_asus.ko.symbols
> /boot/kernel/acpi_panasonic.ko.symbols
> /boot/kernel/acpi_dock.ko   /boot/kernel/acpi_sony.ko
> /boot/kernel/acpi_dock.ko.symbols
> /boot/kernel/acpi_sony.ko.symbols
> /boot/kernel/acpi_fujitsu.ko/boot/kernel/acpi_toshiba.ko
> /boot/kernel/acpi_fujitsu.ko.symbols
> /boot/kernel/acpi_toshiba.ko.symbols
> /boot/kernel/acpi_hp.ko /boot/kernel/acpi_video.ko
> /boot/kernel/acpi_hp.ko.symbols
> /boot/kernel/acpi_video.ko.symbols
> /boot/kernel/acpi_ibm.ko/boot/kernel/acpi_wmi.ko
> /boot/kernel/acpi_ibm.ko.symbols/boot/kernel/acpi_wmi.ko.symbols
> 
> I don't have an acer kernel module for ACPI.

Two options:

If you can derive from the documentation of your Acer laotop
if it is _compatible_ to one of the implementations provided
by the system, use that instead.

You can do "trial & error" to see if one of the modules works,
even though the name is different. In worst case, load them
all (by using * wildcard) and check with "kldstat".




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"