Re: fstab problem

2012-01-14 Thread Bernt Hansson



2012-01-14 11:00, per...@pluto.rain.com skrev:

Bernt Hanssonb...@bananmonarki.se  wrote:


This is an old machine (1997), not sure it will boot from usb.
I'll check.


If it can boot from floppy, Plop will boot it from USB.
http://www.plop.at/en/bootmanagers.html


Thank you. I'll have a look at it.
___
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: disk problem(s)

2012-01-14 Thread Polytropon
On Sat, 14 Jan 2012 08:45:20 +0100, Bernt Hansson wrote:
 Hello list!
 
   7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 06:15:01 UTC 2010 
 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
 
 Whenever a program tries to make a directory on this slice it
 gets this error

It's a partition, not a slice. Partitions carry
file systems, slices carry partitions. :-)



 mkdir: spool/text/test: Too many links

So the problem seems to be related to directories, not
to any files (inodes) per se.



 This is the slice
 
 /dev/ad4s4d202G 37G149G20%/news/spool/text

The partition; ad4s4 would be the slice. :-)



 One can create a file without problems just not directories.
 
 Checked sysctl but don't know what to look for. A boot in the right end 
 would be helpful.

I would suggest to find out the reason, therefore
a short search though the src/ subtree reveals that
this message provided by mkdir is:

#if defined (EMLINK)
  ENTRY(EMLINK, EMLINK, Too many links),
#endif

As the mkdir program uses the mkdir() call, we find
man 2 mkdir with the error description for EMLINK:

The new directory cannot be created because
the parent directory contains too many
subdirectories.

How many subdirectories are there?

Could you, for example, try removing one and then
creating a new one (assumption: success), followed
by another try to create one (assumption: fail)?



Detail:

The mkdir() function can be found (for UFS2) in the
file /usr/src/sys/gnu/fs/ext2fs/ext2_vnops.c at
line  (sources of 8.2-STABLE i386 here). If
you examine what mkdir() does, you'll see that
the too many links is true when LINK_MAX is
exceeded. Per /usr/src/sys/gnu/fs/ext2fs/ext2_fs.h
we can determine that

#define EXT2_LINK_MAX   32000

is defined. Can you check if 32000 is the amount
of directories created?


-- 
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: access(FULLPATH, xxx);

2012-01-14 Thread Polytropon
On Sat, 14 Jan 2012 02:00:12 -0600 (CST), Robert Bonomi wrote:
 To repeat some advice from one of my Computer Science professors, many years
 ago, whenever I asked 'how does it work' questions: Try it and find out.

I bet my professor can beat up your professor. :-)

Mine used to say several times: Trial and error is NOT
a programming concept!

However, your suggestion of creating a simple test case,
together with consulting the documentation, is a fully
valid approach to discover what format path should be
in the int access(const char *path, int mode); function.
Luckily, we _have_ that kind of documentation in FreeBSD
where the answer is just man 2 access away. Other
operating systems (or excuses thereof) do not offer
this simple and still helpful thing.



 You see, the *ONLY* thing that matters is 'what the machine does'.  And,
 a trivial test case will give an _authoritative_ answer.   Anything that
 anybody says about 'how it works' is merely an *opinion*, and they could
 be wrong.  The test case will, however, ALWAYS give you the 'hard truth'
 about how it works in your environment.

Especially when interpreting the content of the manual
is debatable (as it is at least for me in this specific
case), a simple test would reveal the truth of what
will actually happen.




-- 
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: disk problem(s)

2012-01-14 Thread Polytropon
On Sat, 14 Jan 2012 09:22:36 +0100, Polytropon wrote:
 The mkdir() function can be found (for UFS2) in the
 file /usr/src/sys/gnu/fs/ext2fs/ext2_vnops.c at
 line  (sources of 8.2-STABLE i386 here). If
 you examine what mkdir() does, you'll see that
 the too many links is true when LINK_MAX is
 exceeded. Per /usr/src/sys/gnu/fs/ext2fs/ext2_fs.h
 we can determine that
 
   #define EXT2_LINK_MAX   32000
 
 is defined. Can you check if 32000 is the amount
 of directories created?

Shit, what have I done... of course the files
mentioned here do correspond to ext2 (Linux stuff),
and _not_ to UFS2.

The answer is in /usr/src/sys/sys/syslimits.h where
we find the following definition:

#define LINK_MAX 32767 /* max file link count */

Can you check _that_ number against the amount of
directories created?

By the way, in cases like this it's helpful if you
provide the _command_ that you tried and the current
directory from _where_ you've tried it.

Also see /usr/src/sys/ufs/ufs/ufs_vnops.c, lines 1748
and onward, to see the UFS mkdir() system call acting
with

if ((nlink_t)dp-i_nlink = LINK_MAX) {
error = EMLINK;
goto out;
}

when the LINK_MAX limit is reached.



Sorry for the confusion.


-- 
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: FreeBSD Mailling list and Slieve filter

2012-01-14 Thread Matthew Seaman
On 14/01/2012 05:25, Tobi wrote:
 Thanks!!!
 It works fine with this:
 
 if header :contains [List-ID] freebsd-questions@freebsd.org {
 fileinto INBOX.Mailinglisten.FreeBSD.freebsd-questions;
 stop;
 }

You'll find that whenever someone replies to one of your messages on the
list you'll often tend to get the response directly rather than via the
mailing list, so it won't be filed by this rule.

This might be considered a feature.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature


Re: disk problem(s)

2012-01-14 Thread Bernt Hansson

2012-01-14 09:22, Polytropon skrev:

How many subdirectories are there?


ls | wc -l
   32765



Could you, for example, try removing one and then
creating a new one (assumption: success), followed
by another try to create one (assumption: fail)?



That is a nono

I'll have to pop in another disk.




Detail:

The mkdir() function can be found (for UFS2) in the
file /usr/src/sys/gnu/fs/ext2fs/ext2_vnops.c at
line  (sources of 8.2-STABLE i386 here). If
you examine what mkdir() does, you'll see that
the too many links is true when LINK_MAX is
exceeded. Per /usr/src/sys/gnu/fs/ext2fs/ext2_fs.h
we can determine that

#define EXT2_LINK_MAX   32000

is defined. Can you check if 32000 is the amount
of directories created?

___
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: disk problem(s)

2012-01-14 Thread Polytropon
On Sat, 14 Jan 2012 10:12:48 +0100, Bernt Hansson wrote:
 2012-01-14 09:22, Polytropon skrev:
  How many subdirectories are there?
 
 ls | wc -l
 32765

Seems that you have reached LINK_MAX of 32767
(according to /usr/src/sys/sys/syslimits.h).
The difference of 2, I assume, is one for .
and one for .. hidden entries.



  Could you, for example, try removing one and then
  creating a new one (assumption: success), followed
  by another try to create one (assumption: fail)?
 
 
 That is a nono
 
 I'll have to pop in another disk.

As the voice from the GPS navigation system tends
to say: You have reached your destination. :-)

Re-arranging the content of the disk could be an
option, but if you're using that disk as some kind
of WORM medium (e. g. backup disk), I understand
the nono.



-- 
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: FreeBSD Mailling list and Slieve filter

2012-01-14 Thread Da Rock

On 01/14/12 19:02, Matthew Seaman wrote:

On 14/01/2012 05:25, Tobi wrote:

Thanks!!!
It works fine with this:

if header :contains [List-ID] freebsd-questions@freebsd.org {
 fileinto INBOX.Mailinglisten.FreeBSD.freebsd-questions;
 stop;
}

You'll find that whenever someone replies to one of your messages on the
list you'll often tend to get the response directly rather than via the
mailing list, so it won't be filed by this rule.
Actually, my experience shows that it will still *usually* result in a 
success- the various headers generally remain intact with replies, but 
it is one of the other header fields that changes. The above will work 
98% of the time.

This might be considered a feature.

chuckle :)
___
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: access(FULLPATH, xxx);

2012-01-14 Thread Robert Bonomi
 From owner-freebsd-questi...@freebsd.org  Sat Jan 14 02:32:15 2012
 Date: Sat, 14 Jan 2012 09:28:21 +0100
 From: Polytropon free...@edvax.de
 To: Robert Bonomi bon...@mail.r-bonomi.com
 Cc: freebsd-questions@freebsd.org
 Subject: Re: access(FULLPATH, xxx);

 On Sat, 14 Jan 2012 02:00:12 -0600 (CST), Robert Bonomi wrote:
  To repeat some advice from one of my Computer Science professors, many years
  ago, whenever I asked 'how does it work' questions: Try it and find out.

 I bet my professor can beat up your professor. :-)

 Mine used to say several times: Trial and error is NOT
 a programming concept!

As far as writing applications goes, that is _somewhat_ correct.  

However, 'trial and error' is _not_ the same thing as 'try it and find out'.
See the entire subject area of 'benchmarking'.

And,  the only way to definitively establish if an alternate approach is
'better' -- i.e. 'faster', or 'smaller', or 'more efficient', etc. -- *IS*
to run a trial.

Your professor undoubtedly would not of approved when I wrote bubble-sort
code that _out-performed_ any other sorting technique -- up to the limits
of memory.  Or when I re-wrote an application that used binary searches
of records, with a new version that used a brute-force linear search.  I
thought I could 'do it better/faster' than the existing code, but the only
way to definitively find out was to 'try it'.  And the 'trial' proved
out -- the replacement code was 'merely' somewhat over 100 times faster.
*grin*

As far as 'doing it once' for the purpose of answering a 'how does it work'
question -- where one has _not_ read the documentation, *OR* the existing 
documentation is _not_clear_, then simple experimentation -- to get *the* 
authoritative answer -- is entirly justified.

When I got the 'try it and find out' advice, I was asking questions about
situations where the language _specification_ was unclear -- there were
two 'reasonable interpretations' of what the language inthe speciication
said, and I just wanted to  know which one was the proper interpretation.

Now, given that the language in the specification _was_ abiguous and both 
interpretations were reasonsble, different compiler builders could have 
implemented differently, and 'try it and find out' was _necessary_ to 
establish what that particular implementation did.  grin


___
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: no hyperthreading in FreeBSD 9?

2012-01-14 Thread Marco Beishuizen

On Fri, 13 Jan 2012, the wise Mark Blackman wrote:


On 13 Jan 2012, at 16:30, Marco Beishuizen wrote:


Hi,

I just upgraded from 8-STABLE to 9-STABLE on my dual Xeon (nocona). Now I have 
in my boot messages:
...
root: /etc/rc.d/sysctl: WARNING: sysctl machdep.hlt_logical_cpus does not exist.
root: /etc/rc.d/sysctl: WARNING: sysctl machdep.hyperthreading_allowed does not 
exist.
...

So isn't hyperthreading not available anymore in FreeBSD 9?


http://svnweb.freebsd.org/base/release/9.0.0/UPDATING?r1=222852r2=222853;

Seems to imply HT is enabled by default and new sysctls are used to take
logical CPUs offline.

How many CPUs does your boot message suggest FreeBSD 9 is reporting?


Yeah, I just deleted the lines from sysctl.conf and it doesn't seem to 
make a difference at all (2 cpu's x 2 threads).


Sorry,
Marco
--
Who on earth would eat a charred caterpillar!?
No, no, you SINGE 'em!  You SINGE 'em and eat 'em!
___
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: upgrade from 8.2 to 9.0

2012-01-14 Thread Dick Hoogendijk

Op 13-1-2012 15:00, Polytropon schreef:

On Fri, 13 Jan 2012 14:42:03 +0100, Dick Hoogendijk wrote:

I possible I want my server to upgrade from 8.2-RELEASE to 9.0-RELEASE.
I guess the binary upgrade will not be a problem with freebsd-update -r
9.0-RELEASE fetch If so, I do like to hear the caveats.

Source update also shouldn't be a problem.
Setup your CVS supfile to get the 9.0-RELEASE
sources and follow the instructions in the
handbook and in /usr/src/Makefile's comment
header.
I will use the binary upgrade path. It seems easier for a non high-tech 
system ;-)
My system is running ZFS on root now, so I would very much like to hear 
if the binary upgrade through freebsd-update works well for such a 
system (w/ zfs on root). I don't want to get stuck with a system that 
won't boot again because something goes wrong with zfs.

___
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: access(FULLPATH, xxx);

2012-01-14 Thread Da Rock

On 01/14/12 19:54, Robert Bonomi wrote:

 From owner-freebsd-questi...@freebsd.org  Sat Jan 14 02:32:15 2012
Date: Sat, 14 Jan 2012 09:28:21 +0100
From: Polytroponfree...@edvax.de
To: Robert Bonomibon...@mail.r-bonomi.com
Cc: freebsd-questions@freebsd.org
Subject: Re: access(FULLPATH, xxx);

On Sat, 14 Jan 2012 02:00:12 -0600 (CST), Robert Bonomi wrote:

To repeat some advice from one of my Computer Science professors, many years
ago, whenever I asked 'how does it work' questions: Try it and find out.

I bet my professor can beat up your professor. :-)

Mine used to say several times: Trial and error is NOT
a programming concept!

As far as writing applications goes, that is _somewhat_ correct.

However, 'trial and error' is _not_ the same thing as 'try it and find out'.
See the entire subject area of 'benchmarking'.

And,  the only way to definitively establish if an alternate approach is
'better' -- i.e. 'faster', or 'smaller', or 'more efficient', etc. -- *IS*
to run a trial.

Your professor undoubtedly would not of approved when I wrote bubble-sort
code that _out-performed_ any other sorting technique -- up to the limits
of memory.  Or when I re-wrote an application that used binary searches
of records, with a new version that used a brute-force linear search.  I
thought I could 'do it better/faster' than the existing code, but the only
way to definitively find out was to 'try it'.  And the 'trial' proved
out -- the replacement code was 'merely' somewhat over 100 times faster.
*grin*

Ha! Love it... :D

As far as 'doing it once' for the purpose of answering a 'how does it work'
question -- where one has _not_ read the documentation, *OR* the existing
documentation is _not_clear_, then simple experimentation -- to get *the*
authoritative answer -- is entirly justified.

When I got the 'try it and find out' advice, I was asking questions about
situations where the language _specification_ was unclear -- there were
two 'reasonable interpretations' of what the language inthe speciication
said, and I just wanted to  know which one was the proper interpretation.

Now, given that the language in the specification _was_ abiguous and both
interpretations were reasonsble, different compiler builders could have
implemented differently, and 'try it and find out' was _necessary_ to
establish what that particular implementation did.grin
There appears to be 2 schools of thought on this subject: a classic case 
of the old vs the new, in this case punchcards/slow compilers vs 
gcc/all-in-one compile, link and goof todays tech. I saw a similar 
conversation about 5 years ago on the linux lists... :)


Technically (depending on their era) they're both right. For reference 
as far as the linux lists played out no one won the argument, but it was 
a helluva nostalgic/historical debate!


In the light of this conversation and given todays tech I'd say give it 
a shot unless you think something could break (as in fatal to service 
quality in production/hardware).

___
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: upgrade from 8.2 to 9.0

2012-01-14 Thread Mike Clarke
On Saturday 14 January 2012, Dick Hoogendijk wrote:

 My system is running ZFS on root now, so I would very much like to
 hear if the binary upgrade through freebsd-update works well for such
 a system (w/ zfs on root). I don't want to get stuck with a system
 that won't boot again because something goes wrong with zfs.

Have you considerd using manageBE 
http://anonsvn.h3q.com/projects/freebsd-patches/wiki/manageBE? With 
this tool you can set up cloned alternative Boot-Environments (BE) so 
that you can go back to your old BE if the new one doesn't work.

I'm in the process of upgrading to 9.0 and taking the opportunity of 
changing over to ZFS. I needed to re-arrange my filesystem structure to 
boot from tank/ROOT/someBEname/ instead of tank/ (and make sure the 
mountpoints of any descendent file systems are suitably adjusted) but 
it was worth the effort.

I installed 9.0-RC2 from the ISO onto a spare drive so I haven't done an 
8 to 9 binary upgrade but I have used freebsd-update to upgrade from 
9.0-RC2 to 9.0-RELEASE and that went through without any problems. 

-- 
Mike Clarke
___
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: upgrade from 8.2 to 9.0

2012-01-14 Thread Dick Hoogendijk

Op 14-1-2012 12:37, Mike Clarke schreef:

On Saturday 14 January 2012, Dick Hoogendijk wrote:


My system is running ZFS on root now, so I would very much like to
hear if the binary upgrade through freebsd-update works well for such
a system (w/ zfs on root). I don't want to get stuck with a system
that won't boot again because something goes wrong with zfs.

Have you considerd using manageBE
http://anonsvn.h3q.com/projects/freebsd-patches/wiki/manageBE? With
this tool you can set up cloned alternative Boot-Environments (BE) so
that you can go back to your old BE if the new one doesn't work.


I had not heard of this project before. Sounds very nice if it works. 
Manging BE's is one of the main things I miss in the FreeBSD ZFS 
support. Coming from (open)Solaris this was quite a disappointment. BE's 
rock!

___
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: access(FULLPATH, xxx);

2012-01-14 Thread Polytropon
On Sat, 14 Jan 2012 20:37:14 +1000, Da Rock wrote:
 On 01/14/12 19:54, Robert Bonomi wrote:
   From owner-freebsd-questi...@freebsd.org  Sat Jan 14 02:32:15 2012
  Date: Sat, 14 Jan 2012 09:28:21 +0100
  From: Polytroponfree...@edvax.de
  To: Robert Bonomibon...@mail.r-bonomi.com
  Cc: freebsd-questions@freebsd.org
  Subject: Re: access(FULLPATH, xxx);
 
  On Sat, 14 Jan 2012 02:00:12 -0600 (CST), Robert Bonomi wrote:
  To repeat some advice from one of my Computer Science professors, many 
  years
  ago, whenever I asked 'how does it work' questions: Try it and find out.
  I bet my professor can beat up your professor. :-)
 
  Mine used to say several times: Trial and error is NOT
  a programming concept!
  As far as writing applications goes, that is _somewhat_ correct.
 
  However, 'trial and error' is _not_ the same thing as 'try it and find out'.
  See the entire subject area of 'benchmarking'.
 
  And,  the only way to definitively establish if an alternate approach is
  'better' -- i.e. 'faster', or 'smaller', or 'more efficient', etc. -- *IS*
  to run a trial.
 
  Your professor undoubtedly would not of approved when I wrote bubble-sort
  code that _out-performed_ any other sorting technique -- up to the limits
  of memory.  Or when I re-wrote an application that used binary searches
  of records, with a new version that used a brute-force linear search.  I
  thought I could 'do it better/faster' than the existing code, but the only
  way to definitively find out was to 'try it'.  And the 'trial' proved
  out -- the replacement code was 'merely' somewhat over 100 times faster.
  *grin*
 Ha! Love it... :D

Mee too - except that I didn't want to show that
typical attitude. In fact, I tried to make a
(kinf of humourical) statement about a habit that
I could observe at many students when I was at
university.

Background:

When you write source code, you can make errors.
Compiler shows errors. Some students started
with trial  error to just silence the compiler.
One form was that all functional parts of the
program were enclosed in /* and */ (it was a
C class) - no errors, but no action. A different
approach was to arbitrarily (!) change the source
code, something like that:

void *foo(int blah, void *meow())(int ouch);

Hmmm... gives me segfaults. Maybe something's
wrong with the pointers?

void *foo(int blah, void **meow())(int ouch);

Not much better, segfaults too. How about that?

void *foo(int blah, void meow())(int *ouch);

Well... also not better. I've heared about parentheses,
maybe those can help?

void *foo(int blah), void *meow)(int ouch);

Shit, doesn't even compile anymore! Uhm... _what_ did
I change? Oh wait, I know:

void *foo(int blah, (void *)meow())(int ouch);

Just produces garbage, then segfaults... what could I
change next?

I think you get the idea.

Other students could not understand that even if a
program compiles without any errors, there _may_ be
the possibility that it doesn't do what they intended
it to do. They seemed to believe in some kind of
magical semantic compiler:

int x, y, sum;
x = 100;
y = 250;
sum = a - b;

They expected the compiler to notice what's wrong here
if you consider the _meaning_ of the identifiers. It's
not that obvious if you use x, y, and z. :-)



  As far as 'doing it once' for the purpose of answering a 'how does it work'
  question -- where one has _not_ read the documentation, *OR* the existing
  documentation is _not_clear_, then simple experimentation -- to get *the*
  authoritative answer -- is entirly justified.
 
  When I got the 'try it and find out' advice, I was asking questions about
  situations where the language _specification_ was unclear -- there were
  two 'reasonable interpretations' of what the language inthe speciication
  said, and I just wanted to  know which one was the proper interpretation.
 
  Now, given that the language in the specification _was_ abiguous and both
  interpretations were reasonsble, different compiler builders could have
  implemented differently, and 'try it and find out' was _necessary_ to
  establish what that particular implementation did.grin
 There appears to be 2 schools of thought on this subject: a classic case 
 of the old vs the new, in this case punchcards/slow compilers vs 
 gcc/all-in-one compile, link and goof todays tech. I saw a similar 
 conversation about 5 years ago on the linux lists... :)

I didn't want to complain about using a test case,
with determined variables (relative path vs. absolute
path) to see if the interpretation of man 2 access
was matching the actual inner workings of the function
in use. In fact, I would even judge this the _preferred_
method to be sure.



 In the light of this conversation and given todays tech I'd say give it 
 a shot unless you think something could break (as in fatal to service 
 quality in production/hardware).

Fully agree. Know your variables and construct a
test 

Re: disk problem(s)

2012-01-14 Thread Robert Huff

Bernt Hansson writes:
  2012-01-14 09:22, Polytropon skrev:
   How many subdirectories are there?
  
  ls | wc -l
  32765

... plus . and .. = 32767.
Suggestion: I don't know the content, or the core, but is
there a way to use a further level of sub-directories?  E.g.:

Papa
Quebec
Romeo

becomes

P/Papa
Q/Quebec
R/Romeo



Robert Huff



___
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: FreeBSD Mailling list and Slieve filter

2012-01-14 Thread RW
On Sat, 14 Jan 2012 19:44:04 +1000
Da Rock wrote:

 On 01/14/12 19:02, Matthew Seaman wrote:
  On 14/01/2012 05:25, Tobi wrote:
  Thanks!!!
  It works fine with this:
 
  if header :contains [List-ID] freebsd-questions@freebsd.org {
   fileinto INBOX.Mailinglisten.FreeBSD.freebsd-questions;
   stop;
  }
  You'll find that whenever someone replies to one of your messages
  on the list you'll often tend to get the response directly rather
  than via the mailing list, so it won't be filed by this rule.
 Actually, my experience shows that it will still *usually* result in
 a success- the various headers generally remain intact with replies,
 but it is one of the other header fields that changes. The above will
 work 98% of the time.

The problem occurs when you don't get the in-list copy, either because
the list doesn't send copies to addresses in Cc/To, or because some
mail systems (gmail) treat the delayed in-list copy as a duplicate. In
this case you can't use list-id reliably.

I think it's unusual for lists to suppress in-list copies, except as
an option, so this is mostly a gmail problem. I had to rewrite my
sieve rules when I switched to  gmail, before that list-id worked just
fine.
___
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


graphics tablets

2012-01-14 Thread ajtiM
Hi!

I like to buy a Wacom Bamboo Capture graphics tablet (USB or serial if I will 
find it. I have FreeBSD 9.0-RELEASE and I use GIMP and Inkscape on KDE 4.7.3.
Does anyone has expirience with a Bamboo Capture, please? 

Thanks in advance.

Mitja

http://jpgmag.com/people/lumiwa
___
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


Where to send bugs?

2012-01-14 Thread Коньков Евгений
Hi, Freebsd-questions.

What is better:
1. Send PR to freebsd-current
2. Send PR via site

or I must to send to both?

-- 
С уважением,
 Коньков  mailto:kes-...@yandex.ru

___
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: FreeBSD Mailling list and Slieve filter

2012-01-14 Thread Jerry
On Sat, 14 Jan 2012 13:08:51 +
RW articulated:

 On Sat, 14 Jan 2012 19:44:04 +1000
 Da Rock wrote:
 
  On 01/14/12 19:02, Matthew Seaman wrote:
   On 14/01/2012 05:25, Tobi wrote:
   Thanks!!!
   It works fine with this:
  
   if header :contains [List-ID] freebsd-questions@freebsd.org {
fileinto INBOX.Mailinglisten.FreeBSD.freebsd-questions;
stop;
   }
   You'll find that whenever someone replies to one of your messages
   on the list you'll often tend to get the response directly rather
   than via the mailing list, so it won't be filed by this rule.
  Actually, my experience shows that it will still *usually* result in
  a success- the various headers generally remain intact with replies,
  but it is one of the other header fields that changes. The above
  will work 98% of the time.
 
 The problem occurs when you don't get the in-list copy, either because
 the list doesn't send copies to addresses in Cc/To, or because some
 mail systems (gmail) treat the delayed in-list copy as a duplicate. In
 this case you can't use list-id reliably.
 
 I think it's unusual for lists to suppress in-list copies, except as
 an option, so this is mostly a gmail problem. I had to rewrite my
 sieve rules when I switched to  gmail, before that list-id worked just
 fine.

I have yet to experience a problem using the List-ID with sieve whether
the document was relayed via Google (GMail) or otherwise. Yes, you
don't get a copy of the message that you sent to the list, but that is
because Google (GMail) sucks. I have never experienced any other
failure problem using List-ID. Now, if you are specifically attempting
to receive mail from a list that has been specifically CC'd or BCC'd to
you, than that is another matter entirely. It just requires you to more
carefully construct your sieve rules.

I use a slightly differently constructed rule then the one shown above
although functionally equivalent:

if anyof (header :contains List-Id freebsd-questions.freebsd.org) {fileinto 
FreeBSD; stop;}

I have a rule prior to this one that basically files any document CC'd
to me into a special folder which, if I ever get ambitious, I
occasionally peruse.

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
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: FreeBSD Mailling list and Slieve filter

2012-01-14 Thread RW
On Sat, 14 Jan 2012 10:17:40 -0500
Jerry wrote:

 On Sat, 14 Jan 2012 13:08:51 +
 RW articulated:

  The problem occurs when you don't get the in-list copy, either
  because the list doesn't send copies to addresses in Cc/To, or
  because some mail systems (gmail) treat the delayed in-list copy as
  a duplicate. In this case you can't use list-id reliably.
  
  I think it's unusual for lists to suppress in-list copies, except as
  an option, so this is mostly a gmail problem. I had to rewrite my
  sieve rules when I switched to  gmail, before that list-id worked
  just fine.
 
 I have yet to experience a problem using the List-ID with sieve
 whether the document was relayed via Google (GMail) or otherwise.
 Yes, you don't get a copy of the message that you sent to the list,
 but that is because Google (GMail) sucks. I have never experienced
 any other failure problem using List-ID. Now, if you are specifically
 attempting to receive mail from a list that has been specifically
 CC'd or BCC'd to you, than that is another matter entirely.

The problem is that when someone uses reply to all gmail only gives
me the first copy it receives, and that's invariably the direct reply
which lacks a list-id header. 
___
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: upgrade from 8.2 to 9.0

2012-01-14 Thread Mike Clarke
On Saturday 14 January 2012, Dick Hoogendijk wrote:

 I had not heard of this project before. Sounds very nice if it works.
 Manging BE's is one of the main things I miss in the FreeBSD ZFS
 support. Coming from (open)Solaris this was quite a disappointment.
 BE's rock!

Yes, it's working fine here.

You can even upgrade a new environment while you continue working with 
the current one with

   manageBE create -n newBE -s sourceBE -p pool
   manageBE freebsd-upgrade -n newBE -p pool -r release
   manageBE activate -n newBE -p pool

Then reboot into the new BE and complete the upgrade with the 
final freebsd-update install step. But I needed to 
change chroot /${bootfs} near the end of the script 
to chroot /${pool}/ROOT/${bootfs} to get manageBE freebsd-upgrade 
command to work.

Along similar lines, if you need to do a massive ports upgrade which you 
suspect might go pear shaped then you can do it in a new BE without 
upsetting your working system:

   chroot /tank/ROOT/newBE mount -t devfs devfs /dev
   chroot /tank/ROOT/newBE portmaster -a
   chroot /tank/ROOT/newBE umount /dev

... then, if all went well,  activate the new BE and reboot.

-- 
Mike Clarke
___
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


Using lagg(4) for wired and wireless networks

2012-01-14 Thread Alex
Hi there. A portion of the documentation for link aggregation is
confusing me. In example 32-3 the user is required to match the HW
address of iwn0 with that of bge0. Why is this necessary? In example
32-2 this is not done. How come?

-- 
Alex
___
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


ipv6 in FreeBSD 9

2012-01-14 Thread Marco Beishuizen

Hi,

In 8.2 ipv6 was enabled by adding ipv6_enable=YES in rc.conf, and all 
worked fine. In FreeBSD 9 that changed to 
ipv6_activate_all_interfaces=YES. But now there are still some error 
messages at boot time, and ipv6 doesn't seem to work correctly:


...
root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see 
rc.conf(5).
root: /etc/rc: WARNING: $ipv6_enable is not set 
properly - see rc.conf(5).

...

I do not use a static IP adress, but DHCP. Wat do I need to do more 
to enable ipv6?


Thanks,

Marco
--
FORTUNE PRESENTS FAMOUS LAST WORDS: #4

Socrates:   I DRANK WHAT!?!?
Tarzan: Who greased the grape veee
Al Capone:  There's a violin in my violin case!
Pilot, TWA Fl. #343:What's a mountain goat doing 'way up here?
___
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: ipv6 in FreeBSD 9

2012-01-14 Thread Yuri Pankov
On Sat, Jan 14, 2012 at 06:07:01PM +0100, Marco Beishuizen wrote:
 Hi,
 
 In 8.2 ipv6 was enabled by adding ipv6_enable=YES in rc.conf, and all 
 worked fine. In FreeBSD 9 that changed to 
 ipv6_activate_all_interfaces=YES. But now there are still some error 
 messages at boot time, and ipv6 doesn't seem to work correctly:
 
 ...
 root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see 
 rc.conf(5).
 root: /etc/rc: WARNING: $ipv6_enable is not set 
 properly - see rc.conf(5).
 ...
 
 I do not use a static IP adress, but DHCP. Wat do I need to do more 
 to enable ipv6?

This works for me:

ifconfig_em0_ipv6=inet6 accept_rtadv
ip6addrctl_policy=ipv6_prefer

No other IPv6-related settings done anywhere else.


Yuri
___
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: ipv6 in FreeBSD 9

2012-01-14 Thread Marco Beishuizen

On Sat, 14 Jan 2012, the wise Yuri Pankov wrote:


In 8.2 ipv6 was enabled by adding ipv6_enable=YES in rc.conf, and all
worked fine. In FreeBSD 9 that changed to
ipv6_activate_all_interfaces=YES. But now there are still some error
messages at boot time, and ipv6 doesn't seem to work correctly:

...
root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see
rc.conf(5).
root: /etc/rc: WARNING: $ipv6_enable is not set
properly - see rc.conf(5).
...

I do not use a static IP adress, but DHCP. Wat do I need to do more
to enable ipv6?


This works for me:

ifconfig_em0_ipv6=inet6 accept_rtadv
ip6addrctl_policy=ipv6_prefer

No other IPv6-related settings done anywhere else.


No didn't work. Still the same error messages.

Marco

--
Kamikazes do it once.
___
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: Where to send bugs?

2012-01-14 Thread Vincent Hoffman
On 14/01/2012 15:02, Коньков Евгений wrote:
 Hi, Freebsd-questions.

 What is better:
 1. Send PR to freebsd-current
 2. Send PR via site

 or I must to send to both?

Normally I ask on the relevant mailing list first in case its simple
enough to get it resolved that way and to raise a little awareness ;) ,
then it's if not resolved or if i get asked to submit a PR I usually use
http://www.freebsd.org/send-pr.html to submit a pr. If you are asking
about using /usr/bin/send-pr I believe the default site is the correct one.


Vince
___
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


Solution: mysqld fails to run, can't create/find mysql.sock

2012-01-14 Thread Paul Beard
Woke up to a screenful of error messages about failed mysql backups and found 
that for some reason, mysql was refusing to run at all. The issue was not just 
a missing mysql.sock but an inability to create one. I could do it by hand or 
at least create a file with the same name and permissions but it would be 
removed on the next attempt and then not replaced. Turns out the permissions on 
/tmp were not right. I didn't note them beforehand but setting them 1777 solved 
it. 

I would be interested in knowing how those permissions got changed. I rebooted 
the system early on in the process as I kept seeing messages like this:
120114  9:39:04 [ERROR] Can't start server : Bind on unix socket: Permission 
denied
120114  9:39:04 [ERROR] Do you already have another mysqld server running on 
socket: /tmp/mysql.sock ?

Those are rubbish as error messages as they don't say the file can't be created 
or give any indication of the actual problem. 

This is all more a problem for the mysql developers than FreeBSD but I am 
posting it to the list in case anyone else gets bitten by it. 
--
Paul Beard

Are you trying to win an argument or solve a problem? 



Re: Solution: mysqld fails to run, can't create/find mysql.sock

2012-01-14 Thread Paul Beard

On Jan 14, 2012, at 11:15 AM, Chuck Swiger wrote:

 The meaning seems obvious enough; mysqld was unable to bind to the socket, 
 which is what perror() meant with Permission denied:


Really? I read this: 

 120114  9:39:04 [ERROR] Do you already have another mysqld server running on 
 socket: /tmp/mysql.sock ?

as there is an existing socket that seems to be in use: what's up with that?

The message references a file that does not exist (but that mysql will 
cheerfully remove if found). There was no existing socket. Those two lines, 
taken together, tell me that a. mysql can't run without a socket and b. it 
thinks another process is running, bound to a socket that doesn't exist. Clear 
as mud. 

How about 
[ERROR] socket: /tmp/mysql.sock not found 
and/or 
[ERROR] socket:/tmp/mysql.sock could not be created

perhaps with a helpful hint about permissions. 

If this was unusual, that would be one thing but I found quite a few references 
to the problem before I found the solution. 

Maybe it's a housekeeping thing but why would mysql need to destroy the file it 
uses for a socket and then recreate it when it could simply examine it and 
reuse it? 

 Anyway, doesn't the mysql port want to keep the socket under 
 /var/run/mysql/mysqld.sock or some such, to avoid issues with /tmp?

Apparently not, as I commented out any reference to it in my.cnf and still saw 
the same messages about /tmp/mysql.sock. It seems to work if spelled out 
explicitly. 
 
--
Paul Beard

Are you trying to win an argument or solve a problem? 



Re: Solution: mysqld fails to run, can't create/find mysql.sock

2012-01-14 Thread Chuck Swiger
On Jan 14, 2012, at 10:17 AM, Paul Beard wrote:
 I would be interested in knowing how those permissions got changed.

Someone or something running as root changed them.

 I rebooted the system early on in the process as I kept seeing messages like 
 this:
 120114  9:39:04 [ERROR] Can't start server : Bind on unix socket: Permission 
 denied
 120114  9:39:04 [ERROR] Do you already have another mysqld server running on 
 socket: /tmp/mysql.sock ?
 
 Those are rubbish as error messages as they don't say the file can't be 
 created or give any indication of the actual problem. 


The meaning seems obvious enough; mysqld was unable to bind to the socket, 
which is what perror() meant with Permission denied:

 13 EACCES Permission denied.  An attempt was made to access a file in a 
way forbidden by its file access permissions.

Either /tmp was unwritable for mysqld due to not having 1777 perms, or 
/tmp/mysql.sock probably already existed but was owned by root and not the user 
mysqld runs as.

Anyway, doesn't the mysql port want to keep the socket under 
/var/run/mysql/mysqld.sock or some such, to avoid issues with /tmp?

Regards,
-- 
-Chuck

___
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: resolved 3.6.13 firefox fonts are blurred on my 8.2 freebsd

2012-01-14 Thread akshay sreeramoju
hi chuck,

thanks for the tip that fixed it. http://tinypic.com/r/rlcdjd/5

i was launching my vnc server with depth 8 /usr/local/bin/vncserver :1
-depth 8 -geometry 1340x650,I changed that to /usr/local/bin/vncserver :1
-depth 24 -geometry 1340x650.

Best Regards

Akshay

On Thu, Jan 12, 2012 at 11:45 AM, Chuck Swiger cswi...@mac.com wrote:

 Hi--

 On Jan 12, 2012, at 11:38 AM, akshay sreeramoju wrote:
  The image shows, (not sure how bad it is showing for you), more or less
 the
  display I get from firefox and emacs. I will try to send a more detailed
  image tonight.

 You appear to be running in an 8 or 16-bit color mode; what does
 xdpyinfo say?
 Most likely, you want to run in 24/32-bit color mode instead, to avoid
 apps grabbing a limited palette of colors

 Regards,
 --
 -Chuck


___
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


9.0 buildworld problems

2012-01-14 Thread Dean E. Weimer
I am trying to build a test system to verify everything works on 
FreeBSD 9.0-RELEASE, I started with a standard install on a VMware 
virtual machine.  I used portsnap fetch extract to install the ports 
tree, copied the /etc/make.conf and /etc/src.conf from my existing 8.2 
system onto the new test system.


Contents of /etc/make.conf:
# Use OpenSSL from ports instead of base
WITH_OPENSSL_PORT=yes
# Avoid Building Ports Against X
WITHOUT_X11=yes
# Some Default Options From /usr/share/examples/etc/make.conf
CFLAGS= -O -pipe
NO_PROFILE=true
# Enable SMTP Authentication
SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
SENDMAIL_LDFLAGS=-L/usr/local/lib
SENDMAIL_LDADD=-lsasl2
# Enable Proxy For Ports Fetch
FETCH_ENV=http_proxy=http://192.168.5.1:3128
FETCH_ENV=ftp_proxy=http://192.168.5.1:3128
# added by use.perl 2012-01-14 12:46:15
PERL_VERSION=5.12.4

Contents of /etc/src.conf:
WITHOUT_BIND_DNSSEC=YES
WITHOUT_BIND_LIBS_LWRES=YES
WITHOUT_BIND_NAMED=YES
WITHOUT_BIND_UTILS=YES
WITHOUT_NTP=YES


I then installed openssl, vim-lite, and cvsup-without-gui from ports, 
copied the example standard-supfile to a new location, changed the host= 
line, left the rest as default options.  Ran cvsup to download source 
tree, ran make -j16 buildworld from the /usr/src directory.


The buildworld stoped here:
=== gnu/lib/libsupc++ (install)
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444   libsupc++.a 
/usr/obj/usr/src/tmp/usr/lib
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444  
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/exception 
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/new 
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/typeinfo 
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/cxxabi.h 
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/exception_defines.h 
/usr/obj/usr/src/tmp/usr/include/c++/4.2

1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error

I cleaned everything up and retried, it died at the same spot on the 
next run as well.  I have the full output of the buildwolrd process on 
my webserver, http://www.dweimer.net/buildworld.out.bz2


Interestingly enough at the same time I was building this system I was 
also testing an upgrade from source option on different virtual machine 
that was made from a restore of live system, after downloading the 
FreeBSD9.0 source tree and running buildworld from usr/src against 
copies of the same make.conf and src.conf file above, it built fine and 
the install process ran successfully.  The ports have all been rebuilt, 
and I am going to try a new buildworld to see if it succeeds or fails on 
that system now that its running 9.0 instead of 8.2 when the last 
buidlworld was ran on it.


--

Thanks,
 Dean E. Weimer
 dwei...@dweimer.net
 http://www.dweimer.net/
___
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: 9.0 buildworld problems

2012-01-14 Thread Joshua Isom

On 1/14/2012 3:02 PM, Dean E. Weimer wrote:

I am trying to build a test system to verify everything works on FreeBSD
9.0-RELEASE, I started with a standard install on a VMware virtual
machine. I used portsnap fetch extract to install the ports tree, copied
the /etc/make.conf and /etc/src.conf from my existing 8.2 system onto
the new test system.

Contents of /etc/make.conf:
# Use OpenSSL from ports instead of base
WITH_OPENSSL_PORT=yes
# Avoid Building Ports Against X
WITHOUT_X11=yes
# Some Default Options From /usr/share/examples/etc/make.conf
CFLAGS= -O -pipe
NO_PROFILE=true
# Enable SMTP Authentication
SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
SENDMAIL_LDFLAGS=-L/usr/local/lib
SENDMAIL_LDADD=-lsasl2
# Enable Proxy For Ports Fetch
FETCH_ENV=http_proxy=http://192.168.5.1:3128
FETCH_ENV=ftp_proxy=http://192.168.5.1:3128
# added by use.perl 2012-01-14 12:46:15
PERL_VERSION=5.12.4

Contents of /etc/src.conf:
WITHOUT_BIND_DNSSEC=YES
WITHOUT_BIND_LIBS_LWRES=YES
WITHOUT_BIND_NAMED=YES
WITHOUT_BIND_UTILS=YES
WITHOUT_NTP=YES


I then installed openssl, vim-lite, and cvsup-without-gui from ports,
copied the example standard-supfile to a new location, changed the host=
line, left the rest as default options. Ran cvsup to download source
tree, ran make -j16 buildworld from the /usr/src directory.

The buildworld stoped here:
=== gnu/lib/libsupc++ (install)
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libsupc++.a
/usr/obj/usr/src/tmp/usr/lib
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/exception 
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/new
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/typeinfo
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/cxxabi.h
/usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/exception_defines.h
/usr/obj/usr/src/tmp/usr/include/c++/4.2
1 error
*** Error code 2
1 error
*** Error code 2
1 error
*** Error code 2
1 error

I cleaned everything up and retried, it died at the same spot on the
next run as well. I have the full output of the buildwolrd process on my
webserver, http://www.dweimer.net/buildworld.out.bz2

Interestingly enough at the same time I was building this system I was
also testing an upgrade from source option on different virtual machine
that was made from a restore of live system, after downloading the
FreeBSD9.0 source tree and running buildworld from usr/src against
copies of the same make.conf and src.conf file above, it built fine and
the install process ran successfully. The ports have all been rebuilt,
and I am going to try a new buildworld to see if it succeeds or fails on
that system now that its running 9.0 instead of 8.2 when the last
buidlworld was ran on it.




Run `make -DNO_CLEAN buildworld`.

Because you used -j6, there's no way to know what went wrong without a 
full log, and even with a full log it'll be a pain.

___
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


Probable Hardware Failure

2012-01-14 Thread Doug Hardie
I have a pretty old desktop that has been around quite awhile.  It has started 
periodic crashes.  No log messages.  However, the core status files all show 
double fault.  I am confident this is a hardware issue, but is there any easy 
way to determine if its power or memory related?  Those are the primary 
candidates although memory is also possible.  We really need to replace the 
entire unit, but that might be a bit more salable if I can present convincing 
evidence of the cause of the problem.


___
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: 9.0 buildworld problems

2012-01-14 Thread Boris
Best is:

- to empty your make.conf
- make cleanworld
- make cleandir

and restart your buildword attempt.



On Sat, Jan 14, 2012 at 9:02 PM, Dean E. Weimer dwei...@dweimer.net wrote:
 I am trying to build a test system to verify everything works on FreeBSD
 9.0-RELEASE, I started with a standard install on a VMware virtual machine.
  I used portsnap fetch extract to install the ports tree, copied the
 /etc/make.conf and /etc/src.conf from my existing 8.2 system onto the new
 test system.

 Contents of /etc/make.conf:
 # Use OpenSSL from ports instead of base
 WITH_OPENSSL_PORT=yes
 # Avoid Building Ports Against X
 WITHOUT_X11=yes
 # Some Default Options From /usr/share/examples/etc/make.conf
 CFLAGS= -O -pipe
 NO_PROFILE=true
 # Enable SMTP Authentication
 SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
 SENDMAIL_LDFLAGS=-L/usr/local/lib
 SENDMAIL_LDADD=-lsasl2
 # Enable Proxy For Ports Fetch
 FETCH_ENV=http_proxy=http://192.168.5.1:3128
 FETCH_ENV=ftp_proxy=http://192.168.5.1:3128
 # added by use.perl 2012-01-14 12:46:15
 PERL_VERSION=5.12.4

 Contents of /etc/src.conf:
 WITHOUT_BIND_DNSSEC=YES
 WITHOUT_BIND_LIBS_LWRES=YES
 WITHOUT_BIND_NAMED=YES
 WITHOUT_BIND_UTILS=YES
 WITHOUT_NTP=YES


 I then installed openssl, vim-lite, and cvsup-without-gui from ports, copied
 the example standard-supfile to a new location, changed the host= line, left
 the rest as default options.  Ran cvsup to download source tree, ran make
 -j16 buildworld from the /usr/src directory.

 The buildworld stoped here:
 === gnu/lib/libsupc++ (install)
 sh /usr/src/tools/install.sh -C -o root -g wheel -m 444   libsupc++.a
 /usr/obj/usr/src/tmp/usr/lib
 sh /usr/src/tools/install.sh -C -o root -g wheel -m 444
  /usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/exception
 /usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/new
 /usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/typeinfo
 /usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/cxxabi.h
 /usr/src/gnu/lib/libsupc++/../../../contrib/libstdc++/libsupc++/exception_defines.h
 /usr/obj/usr/src/tmp/usr/include/c++/4.2
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 1 error
 *** Error code 2
 1 error

 I cleaned everything up and retried, it died at the same spot on the next
 run as well.  I have the full output of the buildwolrd process on my
 webserver, http://www.dweimer.net/buildworld.out.bz2

 Interestingly enough at the same time I was building this system I was also
 testing an upgrade from source option on different virtual machine that was
 made from a restore of live system, after downloading the FreeBSD9.0 source
 tree and running buildworld from usr/src against copies of the same
 make.conf and src.conf file above, it built fine and the install process ran
 successfully.  The ports have all been rebuilt, and I am going to try a new
 buildworld to see if it succeeds or fails on that system now that its
 running 9.0 instead of 8.2 when the last buidlworld was ran on it.

 --

 Thanks,
  Dean E. Weimer
  dwei...@dweimer.net
  http://www.dweimer.net/
 ___
 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


database apps that ignore sockets? [was: Solution: mysqld fails to run, can't create/find mysql.sock]

2012-01-14 Thread Paul Beard

On Jan 14, 2012, at 11:15 AM, Chuck Swiger wrote:

 Anyway, doesn't the mysql port want to keep the socket under 
 /var/run/mysql/mysqld.sock or some such, to avoid issues with /tmp?


Turns out some applications won't work if you move the socket if they are 
configured to access localhost. Seems like a misunderstanding of networking if 
you can specify a port number in a configuration file but the application looks 
to the filesystem for the socket. There is no way to specify a file location so 
it seems doomed to fail — as it did. 

The apps in question are net-mgmt/cacti and net-mgmt/cacti-spine. 
--
Paul Beard

Are you trying to win an argument or solve a problem? 



Re: Probable Hardware Failure

2012-01-14 Thread _
Memory is a rather broad term. If by memory you mean RAM, you could replace
your current RAM with another chip, supposing you have one around.

An interesting read on Double Fault is:

http://en.wikipedia.org/wiki/Double_fault

According to it, that would rather point to a software than a hardware
related problem.


On Sun, Jan 15, 2012 at 1:12 AM, Doug Hardie bc...@lafn.org wrote:

 I have a pretty old desktop that has been around quite awhile.  It has
 started periodic crashes.  No log messages.  However, the core status files
 all show double fault.  I am confident this is a hardware issue, but is
 there any easy way to determine if its power or memory related?  Those are
 the primary candidates although memory is also possible.  We really need to
 replace the entire unit, but that might be a bit more salable if I can
 present convincing evidence of the cause of the problem.


 ___
 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: Probable Hardware Failure

2012-01-14 Thread Doug Hardie

On 14 January 2012, at 18:11, _ wrote:

 Memory is a rather broad term. If by memory you mean RAM, you could replace 
 your current RAM with another chip, supposing you have one around.
 
 An interesting read on Double Fault is: 
 
 http://en.wikipedia.org/wiki/Double_fault
 
 According to it, that would rather point to a software than a hardware 
 related problem.
 
 
 On Sun, Jan 15, 2012 at 1:12 AM, Doug Hardie bc...@lafn.org wrote:
 I have a pretty old desktop that has been around quite awhile.  It has 
 started periodic crashes.  No log messages.  However, the core status files 
 all show double fault.  I am confident this is a hardware issue, but is 
 there any easy way to determine if its power or memory related?  Those are 
 the primary candidates although memory is also possible.  We really need to 
 replace the entire unit, but that might be a bit more salable if I can 
 present convincing evidence of the cause of the problem.

I doubt if its a direct software fault.  The system is running 7.2 and has been 
running that for several years without any problems.  Nothing has been changed 
on it.  However, a memory fault could easily end up in the kernel thus making 
it look like a software problem.

___
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