Re: When a System Dies; Getting back in operation again.

2009-05-04 Thread Jonathan McKeown
On Friday 01 May 2009 22:43:51 Jerry McAllister wrote:
 On Fri, May 01, 2009 at 12:07:22PM -0500, Martin McCormick wrote:
  Let's say we have a system that is backed up regularly and it
  vanishes in a puff of smoke one day. One can get FreeBSD
  installed on a new drive in maybe half an hour or so but we also
  need to get back to the right patch level and then we can say we
  are back where we started.

 What you want to do is use the fixit image to set up the disk.
 That means fdisk and bsdlabel and newfs it.   You can actually
 use sysinstall to do this as well.  Just let the installer come
 up and do the disk stuff, choose minimal install and then after
 it finishes making the disks, kill the rest of the install (or
 just let it finish and then overwrite it.

 But, I find it actually easier to do the fdisk, bsdlabel and newfs-s
 myself.  But, then I am used to it.

 Right after you get done making sure where your fixit is living,
 then use fdisk and bsdlabel to check for the way you have the disk
 set up currently.   Write it down or print it out and keep it
 near that installation/fixit disk.

[Lots of good stuff about creating the partitions]

 Now all you have to do is newfs each partition.   Just take the
 defaults.   Remember that newfs wants the full device spec, not
 just the drive identifier.

If you have kept the right information beforehand, you can actually restore 
your dumps onto ``bare metal'' without doing a partial install first, and 
with the same newfs settings for each partition as you originally had. You 
need to use bsdlabel and dumpfs -m and keep the output for rebuilding. The 
rest of this message is the details.

On your running system, create and keep two files. My system has one slice, 
ad6s1, and the usual partitions - a for root, d for /tmp, e for /var, f 
for /usr, and I've shown the commands you need, and the resulting file 
contents on my current system, below:

bsdlabel ad6s1 ad6s1.label

ad6s1.label contains:

# /dev/ad6s1:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a:  104857604.2BSD 2048 16384 8
  b:  8388608  1048576  swap
  c: 1562963220unused0 0 # raw part, don't 
edit
  d: 20971520  94371844.2BSD 2048 16384 28552
  e:  1048576 304087044.2BSD 2048 16384 8
  f: 124839042 314572804.2BSD 2048 16384 28552

I usually put all the spare space on a disk into /usr, so changing the first 
field on the f: line (the size) from 124839042 to * tells bsdlabel to do 
exactly that in case the replacement disk is a different size from the 
original.

We now need the newfs settings for all the 4.2BSD filesystems except c, so (in 
sh syntax)

for i in a d e f; do dumpfs -m ad6s1$i; done newfscmds.ad6s1

newfscmds.ad6s1 now contains:

# newfs command for ad6s1a (/dev/ad6s1a)
newfs -O 2 -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o 
time -s 262144 /dev/ad6s1a
# newfs command for ad6s1d (/dev/ad6s1d)
newfs -O 2 -U -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o 
time -s 5242880 /dev/ad6s1d
# newfs command for ad6s1e (/dev/ad6s1e)
newfs -O 2 -U -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o 
time -s 262144 /dev/ad6s1e
# newfs command for ad6s1f (/dev/ad6s1f)
newfs -O 2 -U -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o 
time -s 31209760 /dev/ad6s1f

take out the -s 31209760 in the command for ad6s1f (this is the size of the 
new filesystem and it defaults to the size of the partition - which we made 
to take up the rest of the disk).

Now you can save these two files somewhere. When it comes to a catastrophic 
failure and restore, boot a liveCD. Use fdisk to create your single large 
slice on the new disk with

fdisk -BI ad6

Use 

bsdlabel -R ad6s1 ad6s1.label

to restore the disklabel.

If your device name is different from before, you need to edit newfscmds.ad6s1 
to change the ad6 to the new device name wherever it occurs, but you then run 
the newfs commands in the file to create your filesystems with the same 
parameters (softupdates on/off, etc) as before.

You now have the basic structure of your previous disk, ready to have the 
root, /var/ and /usr dumps restored to make a running system identical to the 
destroyed one, with one last step:

bsdlabel -B ad6s1

to put the boot code on the slice. (I haven't tried this bit, so if you're 
going to use the boot code from your root partition, which is stored 
at /boot/boot, you'll need to check whether you can run bsdlabel -B on a 
mounted disk. If you can, the command would be

bsdlabel -B -b /mnt/boot/boot /dev/ad6s1

assuming you mounted /dev/ad6s1a on /mnt).

If you have a different device name, of course, you also need to edit your 
fstab before rebooting.

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

Re: lost+found

2009-05-04 Thread Alexander Tarasov
# - is a comment..
in bash cd without dirname always return you to a home-directory..
cd - returns you to previous location, for example..

2009/5/4 Ruben de Groot mai...@bzerk.org

 On Sat, May 02, 2009 at 11:06:27PM +0200, Polytropon typed:
  On Sat, 02 May 2009 15:45:13 -0400, PJ af.gour...@videotron.ca wrote:
   [~]# cd /tmp/lost+found/#123456
   [/tmp/lost+found/#123456]# ls
 
  Okay, it's empty.
 
 
 
   [/tmp/lost+found/#123456]# cd ..
 
  Strange, why does .. lead you from /tmp/lost+found/#123456
  to /tmp/lost+found/#123456, just as if cd wasn't executed?
 
 
 
   [/tmp/lost+found/#123456]# cd #123456 this returns and empty directory)
 
  Does /tmp/lost+found/#123456 contain another #123456? And
  why does this cd lead you to your (root's) home directory?

 Probably because the # is interpreted as comment. I can reproduce this
 in a bourne shell; not in (t)csh.

 Ruben
 ___
 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: clear old output in login screen?

2009-05-04 Thread Mike Clarke
On Monday 04 May 2009, per...@pluto.rain.com wrote:

 If I needed to do this, could not find a way to do it via
 configuration settings, and didn't want to hack the login
 source code, I would try renaming the login binary to
 something like login.real, and replacing it with an
 executable script containing something like:

   #!/bin/csh
   clear
   vidcontrol -C
   exec /usr/bin/login.real $@

But this wouldn't prevent someone scrolling back with the scroll lock 
key before logging in. I assume the OP's requirement is to stop people 
from seeing previous users console activity.

-- 
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: lost+found

2009-05-04 Thread Ruben de Groot
On Sat, May 02, 2009 at 11:06:27PM +0200, Polytropon typed:
 On Sat, 02 May 2009 15:45:13 -0400, PJ af.gour...@videotron.ca wrote:
  [~]# cd /tmp/lost+found/#123456
  [/tmp/lost+found/#123456]# ls
 
 Okay, it's empty.
 
 
 
  [/tmp/lost+found/#123456]# cd ..
 
 Strange, why does .. lead you from /tmp/lost+found/#123456
 to /tmp/lost+found/#123456, just as if cd wasn't executed?
 
 
 
  [/tmp/lost+found/#123456]# cd #123456 this returns and empty directory)
 
 Does /tmp/lost+found/#123456 contain another #123456? And
 why does this cd lead you to your (root's) home directory?

Probably because the # is interpreted as comment. I can reproduce this
in a bourne shell; not in (t)csh.

Ruben
___
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: Quagga problem

2009-05-04 Thread Steve Bertrand
Bc. Radek Krejca wrote:
 Hello,
 
   starting this day I have problem with quagga, I get this messages
   in my log:
 
 May  3 19:15:36 gw bgpd[7225]: Assertion `len  str_size' failed in file 
 bgp_aspath.c, line 619, function aspath_make_str_count
 May  3 19:15:36 gw kernel: pid 7225 (bgpd), uid 101: exited on signal 6
 May  3 19:15:36 gw bgpd[7225]: No backtrace available on this platform.
 
I have latest verison of port quagga, I looks as bug in quagga,
but I dont know. Do you have any idea for solution?

Here is a link to a patch within the Quagga code base that resolves this
issue:

http://tinyurl.com/c8alza

Steve
___
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: Broken Partition

2009-05-04 Thread Jerry McAllister
On Sun, May 03, 2009 at 06:26:42PM -0700, Chris Chambers wrote:

 Hi,
 
 Using partition magic, I freed some space from my msdos partition. Then 
 using sysinstall's fdisk and label, I attempted to add the space to my 
 freebsd partition. I broke the installation. The boot loader can not 
 find /boot/kernal. I tried mounting the partition under FixIt, but mount 
 says broken argument.

You cannot just slab it on the side of an existing slice with fdisk.
You have to create a brand new slice that uses up all the space.
There is something called   growfs(8)  in FreeBSD, but that works 
on FreeBSD filesystems (FreeBSD partitions) rather than slices.

So, you might be able to use the fixit to go back and restore the
slice to the way it was and get a backup of it.   I am not sure.
Do you have any information on exactly which sector it previously
started on?   

You would have to create a slice _identical_ to the old one (without
any extra added on) and then use fdisk and bsdlabel to restore the
labels _exactly_ as before.  Then you might be able to read stuff.
I am not sure what fsck would do with it because some links probably
have been wiped out.

If you can get it to where dump(8) can make a dump of the each of
the partitions in the slice (except swap and /tmp - don't back up swap
or bother with /tmp), then do that.

Then, go back to Partition Magic and delete the FreeBSD slice and then
create a completely new one that combines the space of what you shaved
off from MSdos with the previous FreeBSD slice.   Then you can go back
to sysinstall (or manually with fdisk-bsdlabel-newfs) and create the
new, larger FreeBSD slice, divide it in to partitions and make file
systems out of them with newfs.

I think you will be extremely lucky if you can pull off rescuing
the old FreeBSD slice though.  You will have to get it to start
on the same sector and have identical links.   You might have to
use backup superblocks that are built in to the filesystems if you
can get to them.

This probably stems from a misunderstanding on how slices, partitions
and filesystems work.   Although most everything is flexible, the
beginnings of each are rather fixed and cannot be arbitrarily shoved
around without being remade from scratch.

jerry


 
 Any ideas?
 
 Chris
 
 ___
 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: Filesystem and bigger files

2009-05-04 Thread Eygene Ryabinkin
Antonio, good day.

Mon, May 04, 2009 at 12:50:59PM +0200, Antonio Tommasi wrote:
 i've freebsd 7.0 in production and i've this hard-drive
 
 Filesystem   SizeUsed   AvailCapacity  Mounted on
 /dev/aacd0s1a  64G15G 44G 26%/
 
 In a directory (spamassassin) i've one file (auto-whitelist) with 
 dimension 4.0 TB and one file (bayes_learn) with dimension 1.0TB
 
 How is it possible? How this file are managed?

First, this isn't a proper question for the freebsd-net mailing list,
so I am redirecting it to freebsd-questions.

To answer your question: most likely, your filesystem is damaged and
should be fsck'ed.  Reboot in a single-user mode and run 'fsck -p
/dev/aacd0s1a' on your filesystem.  If it will correct the things --
it's good.  If not, run 'fsck /dev/aacd0s1a'.  It is always good to have
backups ;))  And the possible filesystem corruption is one of the
reasons why people prefer multiple partitions on the system, rather then
having one big and fat '/' partition.

Another possibility is that these files are sparse: they have holes
that aren't yet filled in.  Tb sizes are insane, but may be you directed
SA to do it.  Here is the illustration of sparse file creation and
its impact on the filesystem size:
-
Filesystem  1K-blocks Used   Avail Capacity  Mounted on
/dev/ad4s2f  24808094 14819988 800346065%/0

$ dd if=/dev/zero of=test.bin bs=1K count=1 seek=10M
1+0 records in
1+0 records out
1024 bytes transferred in 0.49 secs (20951060 bytes/sec)

$ ls -l test.bin
-rw-r--r--  1 usr  usr  10737419264  4 май 16:54 test.bin

$ df .
Filesystem  1K-blocks Used   Avail Capacity  Mounted on
/dev/ad4s2f  24808094 14820046 800340265%/0
-
-- 
Eygene
 ____   _.--.   #
 \`.|\.....-'`   `-._.-'_.-'`   #  Remember that it is hard
 /  ' ` ,   __.--'  #  to read the on-line manual
 )/' _/ \   `-_,   /#  while single-stepping the kernel.
 `-' `\_  ,_.-;_.-\_ ',  fsc/as   #
 _.-'_./   {_.'   ; /   #-- FreeBSD Developers handbook
{_.-``-' {_/#
___
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: When a System Dies; Getting back in operation again.

2009-05-04 Thread Jonathan McKeown
On Monday 04 May 2009 15:59:14 Jerry McAllister wrote:
 On Mon, May 04, 2009 at 10:31:16AM +0200, Jonathan McKeown wrote:

  If you have kept the right information beforehand, you can actually
  restore your dumps onto ``bare metal'' without doing a partial install
  first, and with the same newfs settings for each partition as you
  originally had. You need to use bsdlabel and dumpfs -m and keep the
  output for rebuilding. The rest of this message is the details.

 If you have a specific reason to want your new filesystems' to have
 identical superblock info, you can use dumpfs -m, but you don't need
 to worry about all that.   Just fdisk, bsdlabel and then let newfs
 take its defaults.

Which of your filesystems currently has softupdates disabled? You may not 
care - but the point is that using dumpfs in the way I described will 
preserve that information (along with all the other tuning options) for 
people who do care.

If you're restoring a complete machine from backup, the less you have to think 
about, the better. Knowing that my filesystems are going to be restored with 
whatever tuning options I was previously running with, without my having to 
try and remember, gives me peace of mind ahead of time.

Jonathan
___
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: When a System Dies; Getting back in operation again.

2009-05-04 Thread Jerry McAllister
On Mon, May 04, 2009 at 10:31:16AM +0200, Jonathan McKeown wrote:

 On Friday 01 May 2009 22:43:51 Jerry McAllister wrote:
  On Fri, May 01, 2009 at 12:07:22PM -0500, Martin McCormick wrote:
   Let's say we have a system that is backed up regularly and it
   vanishes in a puff of smoke one day. One can get FreeBSD
   installed on a new drive in maybe half an hour or so but we also
   need to get back to the right patch level and then we can say we
   are back where we started.
 
  What you want to do is use the fixit image to set up the disk.
  That means fdisk and bsdlabel and newfs it.   You can actually
  use sysinstall to do this as well.  Just let the installer come
  up and do the disk stuff, choose minimal install and then after
  it finishes making the disks, kill the rest of the install (or
  just let it finish and then overwrite it.
 
  But, I find it actually easier to do the fdisk, bsdlabel and newfs-s
  myself.  But, then I am used to it.
 
  Right after you get done making sure where your fixit is living,
  then use fdisk and bsdlabel to check for the way you have the disk
  set up currently.   Write it down or print it out and keep it
  near that installation/fixit disk.
 
 [Lots of good stuff about creating the partitions]
 
  Now all you have to do is newfs each partition.   Just take the
  defaults.   Remember that newfs wants the full device spec, not
  just the drive identifier.
 
 If you have kept the right information beforehand, you can actually restore 
 your dumps onto ``bare metal'' without doing a partial install first, and 
 with the same newfs settings for each partition as you originally had. You 
 need to use bsdlabel and dumpfs -m and keep the output for rebuilding. The 
 rest of this message is the details.

If you have a specific reason to want your new filesystems' to have
identical superblock info, you can use dumpfs -m, but you don't need
to worry about all that.   Just fdisk, bsdlabel and then let newfs
take its defaults.   You do not need an identical filesystem to
do a restore(8) on it.   Restore builds it from scratch in the correct
way - in fact in a better way than what it was before the system
was whacked.So, just build the new disk either manually or with
sysinstall and then restore the dumps within the filesystems.

Make sure you cd in to the mounted filesystem - note, since you
are running from a fixit, you are making up new mount points and
mounting the filesystems from the new disk.   Something like:

  mkdir /newroot
  mount /dev/ad0s1a /newroot
  cd /newroot
  restore -rf /dev/nsa0 
   (replace /dev/nsa0 with wherever you are reading the dump.  don't
forget to position the tape with mt fsf nn if it is a tape)

You can also skip the fdisk if you are running only FreeBSD from that
disk and don't mind using what is called a 'dangerously dedicated' disk.
It isn't really all that dangerous.  No weird creatures will climb out
and grab you by the throat at night.

If you do dangerously dedicated, the device addressing leaves out
the slice specifier (s1, s2, s3 or s4) and would look something 
like:   /dev/ad0a   instead of  /dev/ad0s1a.

jerry

 
 On your running system, create and keep two files. My system has one slice, 
 ad6s1, and the usual partitions - a for root, d for /tmp, e for /var, f 
 for /usr, and I've shown the commands you need, and the resulting file 
 contents on my current system, below:
 
 bsdlabel ad6s1 ad6s1.label
 
 ad6s1.label contains:
 
 # /dev/ad6s1:
 8 partitions:
 #size   offsetfstype   [fsize bsize bps/cpg]
   a:  104857604.2BSD 2048 16384 8
   b:  8388608  1048576  swap
   c: 1562963220unused0 0 # raw part, don't 
 edit
   d: 20971520  94371844.2BSD 2048 16384 28552
   e:  1048576 304087044.2BSD 2048 16384 8
   f: 124839042 314572804.2BSD 2048 16384 28552
 
 I usually put all the spare space on a disk into /usr, so changing the first 
 field on the f: line (the size) from 124839042 to * tells bsdlabel to do 
 exactly that in case the replacement disk is a different size from the 
 original.
 
 We now need the newfs settings for all the 4.2BSD filesystems except c, so 
 (in 
 sh syntax)
 
 for i in a d e f; do dumpfs -m ad6s1$i; done newfscmds.ad6s1
 
 newfscmds.ad6s1 now contains:
 
 # newfs command for ad6s1a (/dev/ad6s1a)
 newfs -O 2 -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o 
 time -s 262144 /dev/ad6s1a
 # newfs command for ad6s1d (/dev/ad6s1d)
 newfs -O 2 -U -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o 
 time -s 5242880 /dev/ad6s1d
 # newfs command for ad6s1e (/dev/ad6s1e)
 newfs -O 2 -U -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o 
 time -s 262144 /dev/ad6s1e
 # newfs command for ad6s1f (/dev/ad6s1f)
 newfs -O 2 -U -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o 
 time -s 31209760 /dev/ad6s1f
 
 take out the -s 31209760 in the command for ad6s1f (this is 

Re: install -s

2009-05-04 Thread Dan Nelson
In the last episode (May 01), Nathan Lay said:
 Should install -s really fail if strip fails?  I noticed cross-binutils
 strips everything it installs...in my case, one of the utilities it tries
 to strip is a script and install -s obnoxiously fails.  I set DONTSTRIP to
 get around this problem.
 
 For a point of reference, I'm running a recent 7-STABLE.

It's best that if strip fails, install fails.  strip could unlink the
original file but fail for some reason to rename the temp file to the
original name.

Your problem could be a bug in the cross-binutils Makefile; scripts
shouldn't be installed with install -s.  BSD-style Makefiles use PROG= and
SCRIPTS= definitions, and automake-generated Makefiles use foo_PROGRAMS= and
foo_SCRIPTS= to install executable binaries vs scripts.
 
-- 
Dan Nelson
dnel...@allantgroup.com
___
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: Groups problems

2009-05-04 Thread Maciej Milewski
Monday 04 May 2009 16:24:33 Shaun Friedle napisał(a):
 Hi,
 I seem to have a weird problem with groups, it seems like the system
 doesn't notice that I am in certain groups when it comes to file
 permissions, and if I run groups or id with no arguments it also has
 some groups missing from the list, but with my username as an argument
 it is complete. I've never encountered this before, does anyone know
 what the problem might be?

 [sh...@strange] ~ $ ls -lh /tmp/group_test
 -rw-rw-r--  1 www  mercurial 0B  4 May 14:08 /tmp/group_test
 [sh...@strange] ~ $ echo test  /tmp/group_test
 bash: /tmp/group_test: Permission denied
 [sh...@strange] ~ $ whoami
 shaun
 [sh...@strange] ~ $ grep shaun /etc/group
 wheel:*:0:root,shaun
 www:*:80:shaun
 shaun:*:1002:
 svn:*:1004:svn,shaun
 mercurial:*:1006:shaun,www
 [sh...@strange] ~ $ groups
 shaun wheel svn
 [sh...@strange] ~ $ groups shaun
 shaun wheel www svn mercurial
 [sh...@strange] ~ $ id
 uid=1002(shaun) gid=1002(shaun) groups=1002(shaun),0(wheel),1004(svn)
 [sh...@strange] ~ $ id shaun
 uid=1002(shaun) gid=1002(shaun)
 groups=1002(shaun),0(wheel),80(www),1004(svn),1006(mercurial)
Have you done relogin on this account?


-- 
Pozdrawiam,
Maciej Milewski
___
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: Groups problems

2009-05-04 Thread Armin Pirkovitsch
Have you relogged in after adding the user to the group file?
(su -l should do the trick as well if you can't log out/relog in for
some reason)

Otherwise you'll get exactly the behaviour you described below.

Armin

On Mon 04 May 2009, Shaun Friedle wrote:

 Hi,
 I seem to have a weird problem with groups, it seems like the system
 doesn't notice that I am in certain groups when it comes to file
 permissions, and if I run groups or id with no arguments it also has
 some groups missing from the list, but with my username as an argument
 it is complete. I've never encountered this before, does anyone know
 what the problem might be?
 
 [sh...@strange] ~ $ ls -lh /tmp/group_test
 -rw-rw-r--  1 www  mercurial 0B  4 May 14:08 /tmp/group_test
 [sh...@strange] ~ $ echo test  /tmp/group_test
 bash: /tmp/group_test: Permission denied
 [sh...@strange] ~ $ whoami
 shaun
 [sh...@strange] ~ $ grep shaun /etc/group
 wheel:*:0:root,shaun
 www:*:80:shaun
 shaun:*:1002:
 svn:*:1004:svn,shaun
 mercurial:*:1006:shaun,www
 [sh...@strange] ~ $ groups
 shaun wheel svn
 [sh...@strange] ~ $ groups shaun
 shaun wheel www svn mercurial
 [sh...@strange] ~ $ id
 uid=1002(shaun) gid=1002(shaun) groups=1002(shaun),0(wheel),1004(svn)
 [sh...@strange] ~ $ id shaun
 uid=1002(shaun) gid=1002(shaun)
 groups=1002(shaun),0(wheel),80(www),1004(svn),1006(mercurial)

-- 
Armin Pirkovitsch
a.pi...@inode.at
___
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


Groups problems

2009-05-04 Thread Shaun Friedle

Hi,
I seem to have a weird problem with groups, it seems like the system
doesn't notice that I am in certain groups when it comes to file
permissions, and if I run groups or id with no arguments it also has
some groups missing from the list, but with my username as an argument
it is complete. I've never encountered this before, does anyone know
what the problem might be?

[sh...@strange] ~ $ ls -lh /tmp/group_test
-rw-rw-r--  1 www  mercurial 0B  4 May 14:08 /tmp/group_test
[sh...@strange] ~ $ echo test  /tmp/group_test
bash: /tmp/group_test: Permission denied
[sh...@strange] ~ $ whoami
shaun
[sh...@strange] ~ $ grep shaun /etc/group
wheel:*:0:root,shaun
www:*:80:shaun
shaun:*:1002:
svn:*:1004:svn,shaun
mercurial:*:1006:shaun,www
[sh...@strange] ~ $ groups
shaun wheel svn
[sh...@strange] ~ $ groups shaun
shaun wheel www svn mercurial
[sh...@strange] ~ $ id
uid=1002(shaun) gid=1002(shaun) groups=1002(shaun),0(wheel),1004(svn)
[sh...@strange] ~ $ id shaun
uid=1002(shaun) gid=1002(shaun)
groups=1002(shaun),0(wheel),80(www),1004(svn),1006(mercurial)

--
Thanks,
Shaun Friedle
___
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


Questions about groups.

2009-05-04 Thread Old Crankbuster

Coming from Gnu/Linux, I see differences in group generation on regular
user generation, and there's a group I'm not familiar with - 'operator'.

What does that one do?

I'm familiar with 'staff' and I've added my normal user to that, and of
course 'wheel'.

I intend to use the system on a laptop in this case, and need to enable
regular user access to audio, cdrom/dvd read and write, usb access, and
network reconfiguration/dialout, games and so forth.

I am not seeing such things as plugdev,audio,cdrom in etc/group after
initial install.

Do I need to manually add such groups and then point relevant packages
to them?

Thanks,

-- 
Cheers


signature.asc
Description: Digital signature


Cannot mount smbfs share without requiring manual password

2009-05-04 Thread Ryan van Eerdewijk
Hi,

I have a strange issue. If I type:

mount_smbfs //theu...@theserver/myshare$ /mnt/here

... I will be prompted for theuser's password, I type it, and the share will 
mount fine. But I want this share to mount automatically at bootup. I haven't 
been able to get it to work through /etc/fstab or through an sh script. In fact 
typing:

mount_smbfs -N //theu...@theserver/myshare$ /mnt/here

gives me the following error:

mount_smbfs: unable to open connection: syserr = Authentication error

I have the following in my /etc/nsmb.conf file:

[theserver]
workgroup=MYWORKGROUP
addr=10.10.10.10

[theserver:theuser]
password=$$1571crypto'dpassword

I get the feeling that when mounting the smbfs share, it isn't even checking 
the nsmb.conf file. I've also tried a plain text password, and also including 
the same information in a /root/.nsmbrc file.

I'm running out of ideas. Any help is appreciated.

Thanks

Ryan V.
___
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: Broken Partition

2009-05-04 Thread John Nielsen
It is best to include the list in all replies, so that people other than 
the original responder can offer additional help and so people searching 
the list archives in the future will have a complete picture.

Also, not top-posting (putting replies in the context of the original 
message) is is preferred on this and many other lists. I've reformatted 
your message and added comments inline below.

On Monday 04 May 2009 04:18:37 am Chris Chambers wrote:
 On Sun May 03 John Nielsen wrote:
  On Sunday 03 May 2009 09:26:42 pm Chris Chambers wrote:
   Using partition magic, I freed some space from my msdos partition.
   Then using sysinstall's fdisk and label, I attempted to add the
   space to my freebsd partition. I broke the installation. The boot
   loader can not find /boot/kernal. I tried mounting the partition
   under FixIt, but mount says broken argument.
 
  When you say add the space to my freebsd partition what exactly did
  you do?

 Sorry, what I meant by add the space to my freebsd partition was:

 I created the free space, giving me:
 ad0s1
 ad0s2
 Free Space
 ad0s3

 I deleted and recreated ad0s3 in fdisk. Inside the label tool, I added
 swap space and mounted the remaining on / (as before).

You forgot to say I made a backup. If you really skipped that step then 
hopefully you'll remember next time..

Did you write down the original values from fdisk and bsdlabel? Putting 
them back may be your best bet for recovery.

I would avoid using _any_ swap until you have your data back.

If your new free space had been _after_ the FreeBSD slice on the disk you 
may have had better luck. Since you moved the _beginning_ of your slice 
that changed the relative offsets of everything else which is probably 
why your filesystem is broken (I am not a UFS expert). What is surprising 
is that the loader ran at all... unless you used bsdlabel -B or 
similar.

If you revert the fdisk and bsdlabel values, save your data and want to 
try again a safer approach would be to define a fourth slice to occupy 
the free space (yes it will be out of order but FreeBSD shouldn't care.. 
not sure about DOS or PartitionMagic). Then just use the slice as 
additional swap directly (no bsdlabel, just ad0s4). But do make a backup 
this time.

  What device nodes are listed for your disk from the fixit
  environment?

 Currently, the devices are:
 ad0s1 - DOS, type 7
 ad0s2 - DOS, type 7
 ad0s3
 ad0s3a - UFS
 ad0s3b - Swap
 ad0s3c - ?

The c partition is the raw partition and is always the same size as 
the underlying device (or should be). I don't know that it's used for 
much any more, but there are historical reasons it's there.

 I would settle for the ability to mount the drive so that I could
 retrieve a few files.

Try reverting the fdisk and bsdlabel values (see above).

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


ReturnCode Checking for FTP

2009-05-04 Thread Eddie Chen




Dear Sir,

I am looking of implementing FTP return code checking after a command
is issued
If the FTP command return   code   not equal from return code to be
check,  EXIT 255.

Command:   ? nnn. Where nnn is the return code to be check.




Visit our website at http://www.nyse.com



Note:  The information contained in this message and any attachment
to it is privileged, confidential and protected from disclosure.  If the 
reader of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the 
sender immediately by replying to the message, and please delete
it from your system. Thank you.  NYSE Euronext, Inc.

___
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: Cannot mount smbfs share without requiring manual password

2009-05-04 Thread Ray
On May 4, 2009 09:31:09 am Ryan van Eerdewijk wrote:
 Hi,

 I have a strange issue. If I type:

 mount_smbfs //theu...@theserver/myshare$ /mnt/here

 ... I will be prompted for theuser's password, I type it, and the share
 will mount fine. But I want this share to mount automatically at bootup. I
 haven't been able to get it to work through /etc/fstab or through an sh
 script. In fact typing:

 mount_smbfs -N //theu...@theserver/myshare$ /mnt/here

 gives me the following error:

 mount_smbfs: unable to open connection: syserr = Authentication error

 I have the following in my /etc/nsmb.conf file:

 [theserver]
 workgroup=MYWORKGROUP
 addr=10.10.10.10

 [theserver:theuser]
 password=$$1571crypto'dpassword

 I get the feeling that when mounting the smbfs share, it isn't even
 checking the nsmb.conf file. I've also tried a plain text password, and
 also including the same information in a /root/.nsmbrc file.

 I'm running out of ideas. Any help is appreciated.

 Thanks

 Ryan V.
 ___
 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

Hi Ryan,
What  You have is very similar to what I use, except I don't use the -N Flag 
on mount_smbfs. 
Ray
___
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


per protocol bandwidth filters for firewall

2009-05-04 Thread Tamar Lea
Hello all,
I have inherited the job of maintaining a FreeBSD firewall that sits behind
an ADSL line that connects 128 clients to the internet. I have not used
FreeBSD before but have some linux experience. The connections must be
always on though I am allowed to reboot if absolutely necessary. It is using
ipfilter and ipnat. There have been issues with clients taking up too much
bandwidth, so after several hours of careful testing I managed to redirect
all traffic on port 80 to a squid service using ipnat. This uses delay pools
to limit the max speed per user. However I would also like to limit the max
speed per user for streaming traffic on port 1935. Would this be possible
with the current setup and what programs or config would be able to do the
job?
Thanks,
Tamar
___
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: per protocol bandwidth filters for firewall

2009-05-04 Thread Matthew Seaman

Tamar Lea wrote:

Hello all,
I have inherited the job of maintaining a FreeBSD firewall that sits behind
an ADSL line that connects 128 clients to the internet. I have not used
FreeBSD before but have some linux experience. The connections must be
always on though I am allowed to reboot if absolutely necessary. It is using
ipfilter and ipnat. There have been issues with clients taking up too much
bandwidth, so after several hours of careful testing I managed to redirect
all traffic on port 80 to a squid service using ipnat. This uses delay pools
to limit the max speed per user. However I would also like to limit the max
speed per user for streaming traffic on port 1935. Would this be possible
with the current setup and what programs or config would be able to do the


Hmmm... out of the three possible choices for firewall implementations under
FreeBSD you have ended up with probably the least capable one.  ipfilter's 
unique selling point is that it is available on a large number of different

systems.  In this case I don't think that really counts for much.

The other two alternatives -- together with their associated QoS / traffic
shaping technologies are:

 ipfw + dummynet

This is a FreeBSD specific firewall implementation.  It's a first
match wins type ruleset which provides all the usual functionality:
NAT, stateful filtering etc.  It can be a bit tricky to manage on
a live system as remote updates to the ruleset have an unfortunate
tendency to lock you out of the system.

 pf + altq

This is the new and shiny firewall system ported from OpenBSD. 
It's a last match wins type ruleset, modified by 'quick' (immediately

applied) rules (similar to ipf), so more flexible than ipfw.  The
configuration file is also a lot more readable than ipfw IMHO.  You will
need to build a custom kernel to make use of ALTQ functionality as for
some reason that cannot be provided by a loadable kernel module like the
rest of pf(4).  This would be my personal preference for solving the
problem you describe.

Either of these two should serve you well and allow you to do the required
traffic shaping.  Note: while it is technically possible to run more than
one of the three firewall packages at once; that way madness lies, particularly
for fledgeling administrators.  It might be worth it for a short time if you
really, absolutely, no alternative, have to do a zero-downtime cut-over, but
the risks of something going wrong are significant.  A quick restart with new
software is hardly any more intrusive and a lot safer.

Cheers,

Matthew

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



signature.asc
Description: OpenPGP digital signature


base system openssl in 7.1

2009-05-04 Thread Josh Paetzel
I've been trying to figure out a way to run openssl's make test  
against the openssl included in FreeBSD RELENG_7_1


What I haven't been able to make go is make test in /usr/src/crypto/ 
openssl using various permutations of ./config


Can someone clue me in?

Thanks,

Josh Paetzel




___
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: per protocol bandwidth filters for firewall

2009-05-04 Thread Odhiambo ワシントン
On Mon, May 4, 2009 at 6:33 PM, Tamar Lea tamar...@gmail.com wrote:

 Hello all,
 I have inherited the job of maintaining a FreeBSD firewall that sits behind
 an ADSL line that connects 128 clients to the internet. I have not used
 FreeBSD before but have some linux experience. The connections must be
 always on though I am allowed to reboot if absolutely necessary. It is
 using
 ipfilter and ipnat. There have been issues with clients taking up too much
 bandwidth, so after several hours of careful testing I managed to redirect
 all traffic on port 80 to a squid service using ipnat. This uses delay
 pools
 to limit the max speed per user. However I would also like to limit the max
 speed per user for streaming traffic on port 1935. Would this be possible
 with the current setup and what programs or config would be able to do the
 job?


If you consider PF+ALTQ, you will be able to do what IPFilter/IPNAT is doing
now and much more - just like you desire. You will also find it quite easy
to convert the current firewall/nat rules into PF syntax.

Best of luck!


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Clothes make the man.  Naked people have little or no influence on
society.
  -- Mark Twain
___
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: Cannot mount smbfs share without requiring manual password

2009-05-04 Thread Tim Judd
On Mon, May 4, 2009 at 9:59 AM, Ray r...@stilltech.net wrote:

 On May 4, 2009 09:31:09 am Ryan van Eerdewijk wrote:
  Hi,
 
  I have a strange issue. If I type:
 
  mount_smbfs //theu...@theserver/myshare$ /mnt/here
 
  ... I will be prompted for theuser's password, I type it, and the share
  will mount fine. But I want this share to mount automatically at bootup.
 I
  haven't been able to get it to work through /etc/fstab or through an sh
  script. In fact typing:
 
  mount_smbfs -N //theu...@theserver/myshare$ /mnt/here
 
  gives me the following error:
 
  mount_smbfs: unable to open connection: syserr = Authentication error
 
  I have the following in my /etc/nsmb.conf file:
 
  [theserver]
  workgroup=MYWORKGROUP
  addr=10.10.10.10
 
  [theserver:theuser]
  password=$$1571crypto'dpassword
 
  I get the feeling that when mounting the smbfs share, it isn't even
  checking the nsmb.conf file. I've also tried a plain text password, and
  also including the same information in a /root/.nsmbrc file.
 
  I'm running out of ideas. Any help is appreciated.
 
  Thanks
 
  Ryan V.

 Hi Ryan,
 What  You have is very similar to what I use, except I don't use the -N
 Flag
 on mount_smbfs.
 Ray



A friend recently had this problem and it was due to capitalization.

IIRC, the username in the nsmb.conf file needs to be in all caps, whereas
the username that is given to the server is actually lowercase, or vice
versa.  It was found by a google search and just due to caps alone.

Try toggling the caps, I know, odd fix, but it worked for my friend


--Tim
___
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: When a System Dies; Getting back in operation again.

2009-05-04 Thread Doug Poland
On Mon, May 04, 2009 at 04:30:53PM +0200, Jonathan McKeown wrote:
 On Monday 04 May 2009 15:59:14 Jerry McAllister wrote:
  On Mon, May 04, 2009 at 10:31:16AM +0200, Jonathan McKeown wrote:
 
   If you have kept the right information beforehand, you can
   actually restore your dumps onto ``bare metal'' without doing a
   partial install first, and with the same newfs settings for each
   partition as you originally had. You need to use bsdlabel and
   dumpfs -m and keep the output for rebuilding. The rest of this
   message is the details.
 
  If you have a specific reason to want your new filesystems' to have
  identical superblock info, you can use dumpfs -m, but you don't need
  to worry about all that. ? Just fdisk, bsdlabel and then let newfs
  take its defaults.
 
 Which of your filesystems currently has softupdates disabled? You may
 not care - but the point is that using dumpfs in the way I described
 will preserve that information (along with all the other tuning
 options) for people who do care.
 
 If you're restoring a complete machine from backup, the less you have
 to think about, the better. Knowing that my filesystems are going to
 be restored with whatever tuning options I was previously running
 with, without my having to try and remember, gives me peace of mind
 ahead of time.
 
Excellent discussion.  Along the lines of the less you have to think
about,  is there a technique for restoring geom meta-data on bare
metal?  Say you have a system built upon gmirror and gjournal.  One must
manually create the mirror and journal before restoring from dump.  But
the vital geom meta-data describing your mirror/journal is on the dump.


-- 
Regards,
Doug
___
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


Cannot mount smbfs share without requiring manual password

2009-05-04 Thread Ryan van Eerdewijk
You, sir, are a genius. This solved it.

Much thanks,

Ryan V.
___
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: Questions about groups.

2009-05-04 Thread ill...@gmail.com
2009/5/4 Old Crankbuster crankbus...@gmail.com:

 Coming from Gnu/Linux, I see differences in group generation on regular
 user generation, and there's a group I'm not familiar with - 'operator'.

 What does that one do?

Members of operator can run /sbin/shutdown among
other things.
find / -group operator
can answer better than I ever could.


 I'm familiar with 'staff' and I've added my normal user to that, and of
 course 'wheel'.

 I intend to use the system on a laptop in this case, and need to enable
 regular user access to audio, cdrom/dvd read and write, usb access, and
 network reconfiguration/dialout, games and so forth.

 I am not seeing such things as plugdev,audio,cdrom in etc/group after
 initial install.

 Do I need to manually add such groups and then point relevant packages
 to them?


Various methods apply (for instance /dev/dspN.n is world
writable), man 5 devfs.conf is a good start for some of that.

Best of luck.

-- 
--
___
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: lost+found

2009-05-04 Thread Polytropon
On Mon, 4 May 2009 11:08:04 +0200, Ruben de Groot mai...@bzerk.org wrote:
 Probably because the # is interpreted as comment. I can reproduce this
 in a bourne shell; not in (t)csh.

Ah, thank you. According to the prompt, it didn't look
like csh in the first place, but not like plain sh, too.
Customized bash prompts usually include brackets 'n stuff.

Because I'm using csh mostly, I didn't see the problem
that cd #something == cd (which of course leads
to $HOME).

An attempt to rm #12345 in sh / bash should lead to
an error message (for incomplete rm command).

It's safe to use the Midnight Commander to cd into and
rm #something files and directories. :-)




-- 
Polytropon
From 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: Questions about groups.

2009-05-04 Thread Polytropon
On Mon, 4 May 2009 21:18:34 +0700, Old Crankbuster crankbus...@gmail.com 
wrote:
 
 Coming from Gnu/Linux, I see differences in group generation on regular
 user generation, and there's a group I'm not familiar with - 'operator'.
 
 What does that one do?

The operator groupt allows its users to perform some operator tasks,
without needing them to be in the wheel group. It's like a limited
root permissions group. You'll find some programs that are +x for
this group (for example /sbin/shutdown).



 I'm familiar with 'staff' and I've added my normal user to that, [...]

I've often seen that FreeBSD defaults to user name = group name
for the adduser script, but I usually use the staff group, as you
do. Further fine grained parameters for user and group preferences
can be set in an environment where you have more than one user.



 [...] and of
 course 'wheel'.

Why of course? :-)



 I intend to use the system on a laptop in this case, [...]

Typical single user setting.



 [...] and need to enable
 regular user access to audio, cdrom/dvd read and write, usb access, and
 network reconfiguration/dialout, games and so forth.

There are several groups that you can add your user to, but because
you're already in wheel, you don't have to (such as the dialer
group for ppp).



 I am not seeing such things as plugdev,audio,cdrom in etc/group after
 initial install.

No, they seem to be Linuxisms. :-)



 Do I need to manually add such groups and then point relevant packages
 to them?

No. What should happen then? How should that work? :-)

FreeBSD manages the things you're requiring through two important
files: /etc/devfs.conf (and /etc/devfs.rules) and /etc/devd.conf.

The devfs files control the virtual device file system. It allows
you to have permissions on a per-device file basis. These files are
those that are present from system startup on.

The devd file controls how the system should react if it detects
new devices while it's already running.

See the manpages for these files. Yes, they do exist. :-)



-- 
Polytropon
From 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


To file a PR, or not to file a PR. That is the question.

2009-05-04 Thread Doug Poland
Hello,

A server running 7.1-RELEASE(i386) recently starting deadlocking when
multiple UFS2 snaphosts are being manipulated (via sysutil/freebsd-snapshot).

Upon searching the PR database, I found a problem repart that appears
similar (kern/94769) but with my level of expertise, I'm not certain.
My question, should I go ahead a file a PR, in the hope that more
visability of the issue is better, and therefore more likely to receive
attention?  


-- 
Regards,
Doug
___
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: To file a PR, or not to file a PR. That is the question.

2009-05-04 Thread Bill Moran
In response to Doug Poland d...@polands.org:

 Hello,
 
 A server running 7.1-RELEASE(i386) recently starting deadlocking when
 multiple UFS2 snaphosts are being manipulated (via sysutil/freebsd-snapshot).
 
 Upon searching the PR database, I found a problem repart that appears
 similar (kern/94769) but with my level of expertise, I'm not certain.
 My question, should I go ahead a file a PR, in the hope that more
 visability of the issue is better, and therefore more likely to receive
 attention?  

You'll probably get more mileage by adding details of your problem to
the existing PR.  The person who's handling it will know how closely
the issues are related.

-- 
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
___
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


NIC

2009-05-04 Thread Jos Chrispijn
In order to speed up my LAN backups a little bit, I would like to 
replace my old 10/100 nic with a 10/100/1000 one.
Should be placed in an ancient Dell of 5 years old. Can someone pls 
advise on the type nic I should buy (not necessarily a Dell brand)?


thanks,
Jos Chrispijn

--
No one is listening until you make a mistake...
___
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: NIC

2009-05-04 Thread Jean-Paul Natola
I don't think dell has their own brand of NIC's  in my experience  intel  has
always great quality and support (drivers) for their nic cards

-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Jos Chrispijn
Sent: Monday, May 04, 2009 3:47 PM
To: FreeBSD Questions
Subject: NIC

In order to speed up my LAN backups a little bit, I would like to 
replace my old 10/100 nic with a 10/100/1000 one.
Should be placed in an ancient Dell of 5 years old. Can someone pls 
advise on the type nic I should buy (not necessarily a Dell brand)?

thanks,
Jos Chrispijn

-- 
No one is listening until you make a mistake...
___
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: NIC

2009-05-04 Thread Warren Block

On Mon, 4 May 2009, Jos Chrispijn wrote:

In order to speed up my LAN backups a little bit, I would like to replace my 
old 10/100 nic with a 10/100/1000 one.
Should be placed in an ancient Dell of 5 years old. Can someone pls advise on 
the type nic I should buy (not necessarily a Dell brand)?


The Intel cards are well regarded.  A Pro/1000 (PWLA8391GT) works well 
here.


Many other brands of gigabit cards are based on Realtek chipsets, which 
are not as well regarded.  The Realtek gigabit built into the MSI P45 
Neo-3 FR motherboard seems to work fine.


Probably everyone else will point this out also, but replacing the card 
alone won't give you gigabit; you also need a switch and maybe new 
wiring.


-Warren Block * Rapid City, South Dakota USA
___
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: NIC

2009-05-04 Thread Robert Huff

Jean-Paul Natola writes:

  I don't think dell has their own brand of NIC's in my experience
  intel has always great quality and support (drivers) for their
  nic cards

Conversely, cards based on RealTek chips have a reputation of
being both inexpensive /and/ cheap.  (This may or may not be true of
the wireless cards.)
The drivers for the Intel cards are written by Intel; I've got
a dual-port Pro/1000 GT, and the thing is a _rock_.



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: NIC

2009-05-04 Thread David Kelly
On Mon, May 04, 2009 at 04:31:16PM -0400, Robert Huff wrote:
 
   Conversely, cards based on RealTek chips have a reputation of
 being both inexpensive /and/ cheap.  (This may or may not be true of
 the wireless cards.)

The first generation of RealTek chips were little more than a shift
register and deserved a poor reputation for requiring a lot of CPU
resources. That got RT into market share and now have satisfactory
product.

   The drivers for the Intel cards are written by Intel; I've got
 a dual-port Pro/1000 GT, and the thing is a _rock_.

Ditto. Intel NICs are exceptionally well supported. If one must run
Windows, an Intel NIC and Intel driver provide a lot of features which
are otherwise missing.

-- 
David Kelly N4HHE, dke...@hiwaay.net

Whom computers would destroy, they must first drive mad.
___
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


FOR MARK

2009-05-04 Thread Warren Liddell
After finally managing to get some encoding options from this list 
everything went smoothley untill it got to the burning part .. below is 
the error i got


enterprise# ls
dvd.iso
enterprise# growisofs -dvd-video -Z /dev/cd1 dvd.iso
WARNING: /dev/cd1 already carries isofs!
About to execute 'mkisofs -dvd-video dvd.iso | builtin_dd of=/dev/pass1
obs=32k seek=0'
mkisofs: Unable to make a DVD-Video image.
:-( write failed: Input/output error

enterprise# growisofs -dvd-video -Z /dev/cd0 dvd.iso
Executing 'mkisofs -dvd-video dvd.iso | builtin_dd of=/dev/pass0 obs=32k
seek=0'
mkisofs: Unable to make a DVD-Video image.
:-( write failed: Input/output error

What am i missing//not doing correctly ?


___
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


Broken drive geometry / partitions on 7.2 install

2009-05-04 Thread Brad Waite
Hi all,

I was trying to install 7.2 RELEASE on top of a previous 6.4 RELEASE I'd set up
(but not deployed).  The server has a 40MB Intel service partition and the rest
of the drive for FreeBSD.  Here's what greeted me when doing the fdisk from the
install CD:



Disk name:  da0FDISK Partition Editor
DISK Geometry:  2209 cyls/255 heads/63 sectors = 35487585 sectors (17327MB)

Offset   Size(ST)End Name  PType   Desc  SubtypeFlags

 0 63 62- 12 unused0
63  64197  64259da0as1 4 Compaq Diagnostic   18
 6426030134993077758- 12 unused0
   3077758  641973141955da0cs1 4 Compaq Diagnostic   18
   3141956   32345629  354875584- 12 unused0



It says there's 2 service partition slices (type 18) and no FreeBSD slice.
Remember, I had successfully installed 6.4 on this drive and was able to boot
into both the service partition and FreeBSD.

I ended up deleting all the partitions and recreating them by hand.  I first
created the service partition slice with a size of 80262 (which is what
/sbin/fdisk under 6.4 reported), and the FBSD slice with a size of 35407260
(the remaining space).

After doing that, I was able to install 7.2 just fine and boot into it.  I was
also able to boot into the Intel service partition, since I hadn't blown over
any of the original slice.

However, this is what I get from /usr/sbin/sysinstall's fdisk now:



Disk name:  da0FDISK Partition Editor
DISK Geometry:  2209 cyls/255 heads/63 sectors = 35487585 sectors (17327MB)

Offset   Size(ST)End Name  PType   Desc  SubtypeFlags

 0 63 62- 12 unused0
63  64197  64259da0s1  4 Compaq Diagnostic   18
 64260   35423325   35487584da0s2  8freebsd  165



And /sbin/fdisk reports the same:



*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=2209 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2209 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 18 (0x12),(Compaq diagnostics)
start 63, size 64197 (31 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 3/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 64260, size 35423325 (17296 Meg), flag 80 (active)
beg: cyl 4/ head 0/ sector 1;
end: cyl 1023/ head 254/ sector 63


Notice that I have only 2 slices, but the service partition slice is 64194
blocks instead of the 80262.  On top of this, when I boot from the 7.2 install
CD again, fdisk shows the same screwed-up setup with 2 Compaq Diag slices with
no FBSD slice.

What on earth is happening?  Is my drive geometry hosed?  Is this some sort of
weird LBA issue?  I'm nervous about configuring and deploying this machine
acting as it is.  I also have an identical machine that's reporting the same 
thing.

Thanks.
___
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: FOR MARK

2009-05-04 Thread Polytropon
On Tue, 05 May 2009 07:25:47 +1000, Warren Liddell shin...@maydias.com wrote:
 After finally managing to get some encoding options from this list 
 everything went smoothley untill it got to the burning part .. below is 
 the error i got
 
 enterprise# ls
 dvd.iso
 enterprise# growisofs -dvd-video -Z /dev/cd1 dvd.iso

Hmmm... my growisofs doesn't have -dvd-video (only -dvd-compat),
so google(geowisofs -dvd-compat); and I found:

The -dvd-video option will be passed down to mkisofs(8)
and will instruct it to create a DVD-Video file system
layout. Beside this, the -dvd-video option implies -dvd-compat
growisofs(1) option.

Source:

http://www.freebsd.org/doc/en/books/handbook/creating-dvds.html
18.7.4

It seems that -dvd-video has to be given if you've NOT mastered
an ISO file already, read: when you work with the source files.



 WARNING: /dev/cd1 already carries isofs!

Not a blank media?



 About to execute 'mkisofs -dvd-video dvd.iso | builtin_dd of=/dev/pass1
 obs=32k seek=0'
 mkisofs: Unable to make a DVD-Video image.
 :-( write failed: Input/output error

The mkisofs tools seems to require the source files for the ISO
to be created, it cannot create a video DVD ISO file from a video
DVD ISO file.



 What am i missing//not doing correctly ?

Missing: Reading the handbook.
Not doing correctly: Command line options.
:-)




-- 
Polytropon
From 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: FOR MARK

2009-05-04 Thread Warren Liddell

What am i missing//not doing correctly ?



Missing: Reading the handbook.
Not doing correctly: Command line options.
:-)
  
I'll skip a lot of steps then an just use the standard growisofs for img 
files since DVStyler creates the DVD Video IMG once you've imported the 
mpeg file


/
/

___
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: Questions about groups.

2009-05-04 Thread Old Crankbuster
* ill...@gmail.com ill...@gmail.com [2009-05-04 14:39:34 -0400]:

 
 Various methods apply (for instance /dev/dspN.n is world
 writable), man 5 devfs.conf is a good start for some of that.
 
 
Ah.  Thanks.

-- 
Cheers


signature.asc
Description: Digital signature


Part II: Running SMP kernel but only one cpu

2009-05-04 Thread Duane
The bios in this old Micron dual PPro-180 full tower antique only
initializes the second CPU if the machine is cold-booted.  A simple
'reboot' results in a single processor machine regardless of the
kernel that is launched. This fact -- unknown to me before last night
-- was the source of a great deal of lost time!

My 6.4 SMP kernel (now customized) runs just fine, with both cpus
active, *except* for this message streaming constantly up the boot
console.

(from /var/log/messages:)

May  4 20:20:33 poobah kernel: interrupt storm detected on irq15:;
throttling interrupt source
May  4 20:21:02 poobah last message repeated 42 times
May  4 20:21:03 poobah login: ROOT LOGIN (root) ON ttyv1
May  4 20:21:03 poobah kernel: interrupt storm detected on irq15:;
throttling interrupt source
May  4 20:21:33 poobah last message repeated 30 times
May  4 20:23:33 poobah last message repeated 120 times
May  4 20:33:33 poobah last message repeated 599 times
May  4 20:40:01 poobah last message repeated 387 times
etc etc ad repetitum infinitum

Question1: Is this something I should go to some lengths to eliminate?

Question2: What the heck is it?


Best regards,

-- 
Duane
___
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: Questions about groups.

2009-05-04 Thread Old Crankbuster
* Polytropon free...@edvax.de [2009-05-04 21:02:29 +0200]:
 
  [...] and of
  course 'wheel'.
 
 Why of course? :-)
 

Umm, linuxism habit :-)


 There are several groups that you can add your user to, but because
 you're already in wheel, you don't have to (such as the dialer
 group for ppp).
 
 
 
  I am not seeing such things as plugdev,audio,cdrom in etc/group after
  initial install.
 
 No, they seem to be Linuxisms. :-)
 

:-)
 
 FreeBSD manages the things you're requiring through two important
 files: /etc/devfs.conf (and /etc/devfs.rules) and /etc/devd.conf.
 
 The devfs files control the virtual device file system. It allows
 you to have permissions on a per-device file basis. These files are
 those that are present from system startup on.
 
 The devd file controls how the system should react if it detects
 new devices while it's already running.
 
 See the manpages for these files. Yes, they do exist. :-)

Excellent.  Many thanks. :-)

-- 
Cheers 


signature.asc
Description: Digital signature


Emacs-ess

2009-05-04 Thread Daniel Underwood

How do I install emacs-ess. I don't see it in the ports.

Thanks in advance,
Daniel

(Sent from my iPhone)
___
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: Part II: Running SMP kernel but only one cpu

2009-05-04 Thread Adam Vande More

Duane wrote:

The bios in this old Micron dual PPro-180 full tower antique only
initializes the second CPU if the machine is cold-booted.  A simple
'reboot' results in a single processor machine regardless of the
kernel that is launched. This fact -- unknown to me before last night
-- was the source of a great deal of lost time!
  
Good you found a work around.  You might try ensuring your running 
latest avail bios as well.

My 6.4 SMP kernel (now customized) runs just fine, with both cpus
active, *except* for this message streaming constantly up the boot
console.

(from /var/log/messages:)

May  4 20:20:33 poobah kernel: interrupt storm detected on irq15:;
throttling interrupt source
May  4 20:21:02 poobah last message repeated 42 times
May  4 20:21:03 poobah login: ROOT LOGIN (root) ON ttyv1
May  4 20:21:03 poobah kernel: interrupt storm detected on irq15:;
throttling interrupt source
May  4 20:21:33 poobah last message repeated 30 times
May  4 20:23:33 poobah last message repeated 120 times
May  4 20:33:33 poobah last message repeated 599 times
May  4 20:40:01 poobah last message repeated 387 times
etc etc ad repetitum infinitum

Question1: Is this something I should go to some lengths to eliminate?
  
Yes, it's probably something you should eliminate. 

Question2: What the heck is it?
  
A poor explanation is the devices are fighting over an IRQ.  Generally, 
simplest fix is to find what devs are on that IRQ, and manually reassign 
one dev to a different IRQ.


Best regards,

  


___
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


May training courses - £109 p.p.

2009-05-04 Thread Sandra Keating

We still have places available on the following training courses running in 
May, at £109 plus VAT per person, which is inclusive of a full day’s training, 
lunch, refreshments, course materials, certificate of completion and membership 
to our website. You will receive the lowest rate by booking online at 
www.trainingforyoubyus.com. We also deliver all of our workshops 
in-house/on-site, at extremely competitive rates.  
Creative  Professional Writing Skills – Manchester, 13 May  London, 21 May
This workshop is aimed at those for whom professional writing is a staple of 
their working life. This workshop is designed to arm delegates with some simple 
techniques to radically improve the quality and results of their writing, be it 
for print or web publication.
 
Perfect Podcasts – Edinburgh, 15 May
This workshop is aimed at delegates who might know what a Podcast is, but who 
want to better understand how to create a perfect Podcast to market their 
business, educate a community, share an opinion or just to have fun. This 
practical workshop will help you create a podcast, using it as a simple and 
effective method to get a message across to thousands of people who may either 
visit your business or personal website or a dedicated podcasting site.
 
Presentation  Communication Skills – London, 18 May  Manchester, 28 May
This workshop is aimed at individuals and organisations who want to improve the 
way they present and communicate - both formally and informally - for 
effectiveness and profitability.  Every participant is provided with an 
opportunity to practice the techniques and skills needed to prepare and deliver 
a great presentation, and introduces the wide number of sources of noise or 
interference that can enter into the communication process. 
 
Effective Training Skills – Manchester, 13 May  London, 19 May
This workshop is aimed at those who are required to effectively train employees, 
colleagues or clients in an interesting, engaging and confident manner, in a way that 
is practical and designed to help delegates gain new skills, knowledge and 
understanding essential in the training of adults in the workplace. Specific topics 
covered include:-The Role of the Trainer; The Trainer  Adult Learners; Training 
Strategies; Training Needs Analysis; Feedback  Evaluation and Training Plans.
 
Media Strategies  Campaigns – London, 20 May
This workshop provides some practical guidelines on how to develop appropriate media 
strategies  manage effective media campaigns. One of the best ways of reaching 
your target audiences, influencing policy  practice and changing public opinion is 
to make use of the media. This programme is designed to help individuals and 
organisations develop strategies and campaigns to get the media working for them and 
with them.
 
Writing Press Releases – London, 22 May
This workshop is designed to equip delegates with the most important elements 
of the press release, which are a clear and engaging text, careful selection of 
recipients, and good timing of release. A well-written, well-distributed and 
well-timed press release is not difficult or expensive to produce, yet can be 
effective and useful. The key to writing an effective press release is getting 
it read and the information published.
 
Marketing  Customer Service Strategies – Birmingham, 26 May
When the economic climate is so difficult, the one thing that might just separate your 
organisation from the rest is the way you market your product, idea or service and look 
after your clients. The aim of this programme is to develop and improve your 
organisation through enhanced marketing skills and the service you provide to your 
clients. We focus on the key areas of finding new clients; promotion  publicity; 
creating a successful client experience; image  presentation skills. 
 
Media Relations: tv, Radio, Print – Manchester, 29 May 
This, our most popular workshop, is aimed at those who have to deal with the 
media on a local, national or international level, or perhaps who might want to 
use the media for their own benefit. This is an ideal way to learn, or brush up 
on, the skills required. It is a very practical workshop, where delegates are 
recorded being interviewed, with useful feedback provided and the opportunity 
to purchase a DVD copy.
 
Other courses include:
 
Handling Interviews
This workshop is aimed at those who have had very little interview experience, 
and who are looking to pick up the basic, solid skills, knowledge and 
attitudes, in order to successfully deal with interviews, and interviewers in a 
range of settings. 
 
PowerPoint Presentation Skills
This workshop is aimed at those who want to create professional presentations 
with PowerPoint. Each delegate will be given an opportunity to present this to 
the group, whereupon feedback will be given and practical ways in which to 
improve. This may take the form of help with your slides, your presentation 
technique, or simply 

Re: Emacs-ess

2009-05-04 Thread Giorgos Keramidas
On Mon, 4 May 2009 21:09:34 -0400, Daniel Underwood djuatde...@gmail.com 
wrote:
 How do I install emacs-ess. I don't see it in the ports.

You can probably just download the emacs-ess sources and extract them in
a personal directory for testing, i.e.:

% mkdir ~/elisp
% cd ~/elisp
% fetch http://ess.r-project.org/downloads/ess/ess-5.3.11.tgz
% tar xzvf ess-5.3.11.tgz

Then add in your ~/.emacs file the following:

(add-to-list 'load-path ~/elisp/ess-5.3.11)
(require 'ess-site)

If you see an *ESS* buffer then you are probably ready to go.  If not,
then see the detailed installation instructions in `ess-5.3.11/README'.

HTH,
Giorgos

___
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: Emacs-ess

2009-05-04 Thread Daniel Underwood
Giorgos, thanks a bunch--that was easy!  Your suggestions worked perfectly.

When I originally tried to install ess, i downloaded the tarball and
tried to build it's contents from source.  I did this because I
glanced at the tarball's contents and saw such things as Makeconf
and Makefile.

This, to me, begs the question: why the Makefile if there's no need to
compile? (Pardon my limited understanding.)

Thanks,
Daniel
___
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: Emacs-ess

2009-05-04 Thread Giorgos Keramidas
On Mon, 4 May 2009 22:45:42 -0400, Daniel Underwood djuatde...@gmail.com 
wrote:
 Giorgos, thanks a bunch--that was easy!  Your suggestions worked perfectly.

 When I originally tried to install ess, i downloaded the tarball and
 tried to build it's contents from source.  I did this because I
 glanced at the tarball's contents and saw such things as Makeconf
 and Makefile.

 This, to me, begs the question: why the Makefile if there's no need to
 compile? (Pardon my limited understanding.)

Byte-compiling Emacs Lisp code can make it slightly faster to load.

So there is a marginally small advantage to doing that.  But if you
don't keep closing and reopening Emacs, causing everything to reload
from scratch, it shouldn't matter very much if you load the source .el
files 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: Part II: Running SMP kernel but only one cpu

2009-05-04 Thread Tim Judd
On Mon, May 4, 2009 at 6:46 PM, Duane du...@cheekymonkey.us wrote:

 The bios in this old Micron dual PPro-180 full tower antique only
 initializes the second CPU if the machine is cold-booted.  A simple
 'reboot' results in a single processor machine regardless of the
 kernel that is launched. This fact -- unknown to me before last night
 -- was the source of a great deal of lost time!

 My 6.4 SMP kernel (now customized) runs just fine, with both cpus
 active, *except* for this message streaming constantly up the boot
 console.

 (from /var/log/messages:)

 May  4 20:20:33 poobah kernel: interrupt storm detected on irq15:;
 throttling interrupt source
 May  4 20:21:02 poobah last message repeated 42 times
 May  4 20:21:03 poobah login: ROOT LOGIN (root) ON ttyv1
 May  4 20:21:03 poobah kernel: interrupt storm detected on irq15:;
 throttling interrupt source
 May  4 20:21:33 poobah last message repeated 30 times
 May  4 20:23:33 poobah last message repeated 120 times
 May  4 20:33:33 poobah last message repeated 599 times
 May  4 20:40:01 poobah last message repeated 387 times
 etc etc ad repetitum infinitum

 Question1: Is this something I should go to some lengths to eliminate?

 Question2: What the heck is it?


 Best regards,

 --
 Duane



IRQ15 is typically your secondary IDE controller; but due to PCI (or E-ISA)
plugplay, including the PnP the BIOS may setup, lots of others can be on
that bus too.

Likely candidates are PCI devices, such as modems, NICs, sound cards, etc

I think you'd be able to find what's on IRQ15 by a simple:
  # grep -i irq15 /var/run/dmesg.boot


You will probably not be able to pull your secondary IDE controller off 15.
The possible other device that's been configured for irq15 might stop if you
disable PnP OS in the BIOS (if it exists), or setting irq15 to the
equivelant of 'reserved' in the BIOS might aleviate the problem.


Good luck.
___
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: Part II: Running SMP kernel but only one cpu

2009-05-04 Thread Duane
On 5/4/09, Tim Judd taj...@gmail.com wrote:

 IRQ15 is typically your secondary IDE controller; but due to PCI (or E-ISA)
 plugplay, including the PnP the BIOS may setup, lots of others can be on
 that bus too.

This box has one SCSI card running two SCSI drives. The IDE's are
disabled in the BIOS. But the SCSI card does feature in the problem:

   # grep -i irq15 /var/run/dmesg.boot

No 'irq15' is found. One can see that the interrupt storm begins
when the SCSI drives begin to spin up, IF the machine is booting with
two cpus initialized. dmesg.boot is attached for everyone's
edification and amusement!

Another interesting datapoint is that if the machine is booted in Safe
Mode the interrupt storm disappears, but  so does the second cpu.


Best regards,

-- 
Duane


dmesg.boot
Description: Binary data
___
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