date:20060921

On Wed, Sep 20, 2006 at 04:47:19PM -0700, Mike Peirson wrote:

> Hi all,
> First off, I'm new to FreeBSD and this mailinglist so I hope I am in the 
> right place. Anyways, right now I am having some problems with FreeBSD 
> booting up. I have tried to install 3 times now and keep getting the 
> same error. When I try to boot into FreeBSD, this eventually comes up:
> 
> Manual root filesystem specification:
>   : Mount  using filesystem 
> 
>eg. ufs:da0s1a
>   ? List valid disk boot devices
> abort manual input
> Mountroot>
> 

Hmmm.   this looks like there is no boot sector available.  I haven't
seen messages before just exactly like this, but sort of.

Maybe it would help if you described the sequence of things you
did or tried, such as for the install.

Which version did you install?
Did you initiate the install (boot) from a CD?  If not, what?
Did you choose to use the FreeBSD MBR?
Did you create a FreeBSD slice in sysinstall?
Did you mark that slice as bootable?
Did you create partitions within that FreeBSD slice?
Did you choose which things to install?
Did it appear to load things properly?

After installation finished and you got the congradulations message,
what did you do?

jerry

> This seems to be a prompt where I need to specify the location of the 
> root partition, but the problem here is that it hangs or freezes and I 
> cannot input any text. At first I thought it may be a result of FreeBSD 
> not properly recognizing my HDD's geometry but I manually fixed that and 
> it still is giving me this same issue. If anyone has had a similar 
> problem or knows how to fix this I would greatly appreciate any help. I 
> looked through the Handbook and googled this but I haven't found a 
> solution yet.
> -- 
> Michael Peirson
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to add flags to ifconfig at boot

2006-09-21 Thread Bill Schoolcraft

--- David Kelly <[EMAIL PROTECTED]> wrote:

> On Mon, Sep 18, 2006 at 12:38:30PM -0400, Robert Huff wrote:
> > 
> > David Kelly writes:
> > 
> > >  Or if one needs to ifconfig earlier in the startup process then
> put
> > >  one's script in /etc/start_if.em0
> > 
> > It is my understanding (and experience) this only works when
> > 
> > ifconfig_em0=""
> > 
> > in /etc/rc.conf.
> 
> True only if your options for ifconfig in rc.conf would clear or
> override whatever it is you put in /etc/start_if_em0. As long as its
> something that can be done with multiple ifconfigs then all is fine.
> 
> For example this works fine in /etc/start_if.xl0:
> 
> #!/bin/sh
> ifconfig xl0 lladdr 00:01:23:45:67:89
> 
> with this in rc.conf:
> ifconfig_xl0="DHCP"
> 
> -- 
> David Kelly N4HHE, [EMAIL PROTECTED]

Thank you very much for the above info David, I've always been
challenged with my (encrypted) wireless card though, and usually have
my own manual script that I run.  Always wanted to have it start
"automagically" when/if it is the card I'm using.

(question)

Besides the single line you have in /etc/rc.conf above to instruct DHCP
to be used, can one place all the following somehow in rc.conf or will
I have to get this going in a script location?

Currently I give my card a static ip but would like to have it grab
it's ipaddr by DHCP, here is the majority of the script, omitted are my
ping tests of the gateway at the end.

TIA
#

#!/bin/sh
ifconfig wi0 ssid nwname
ifconfig wi0 wepmode on
ifconfig wi0 192.168.1.222 broadcast 192.168.1.255 netmask
255.255.255.0
ifconfig wi0 up
wicontrol wi0 wepkey 0x1465466964
route add default 192.168.1.1

#

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

Re: mail to root



--- Roger 'Rocky' Vetterberg <[EMAIL PROTECTED]> wrote:

> jekillen wrote:
> > Hello again;
> > I have a question about how mail from the system
> is generated for root.
> > This question was prompted when I edited the
> Postfix aliases file and
> > ran newaliases, then did postfix reload, assuming
> the mail system was
> > running. I was informed that Postfix was not
> running. So the question,
> > how does mail generated by the system get
> delivered to the root account?
> > Here is my motive:
> > I have a server that I want to run headless. I
> want to be able to retrieve
> > mail to root from another machine via ssh login
> (on the same private net
> > work number/netmask 255.255.255.0). I cannot login
> to the system as
> > root over ssh. I don't know if I can read root
> mail with su (as wheel group
> > member). I tried this but maybe I'm not using the
> appropriate parameter.

su - root 
will load up roots environment and let you check his
mail. At least that worked for me last night...

> > Or maybe there isn't any. I don't know where to
> look for an answer to this
> > question, other than this knowledgeable
> group.Oh, man mail maybe?
> > Thanks in advance
> > Jeff K
> 
> I suggest you use .forward to get root's mail to
> another account.
> As root, do this:
>   echo username >> /root/.forward
> 
> That should forward root's mail to whatever username
> you specified.

probably the best solution for a headless box, then
you don't have to su'in in to the machine. Nor risk
snoops gaining the password of all passwords...

> 
> --
> R
> 


-brian

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

Re: downloading Free BSD

On Wed, Sep 20, 2006 at 09:29:11PM -0500, Ryan and Sabrina Tardi wrote:

> What do I do with the ISO files once they are downloaded?  Do I burn
> them directly to a CD then use the CD to install?  Forgive me for my
> ignorance of ISO files!

Exactly correct.
Burn them directly to a CD.
They are already bootable ISOs, so don't use any parameters on the
burner to convert them to ISOs or make them bootable.

Have fun. 

jerry

>  
> Ryan and Sabrina Tardi
> 155 Calder Rd.
> St. Andrews, MB R1A 4B6
> H 204.785.9781
> C 204.799.3968
> [EMAIL PROTECTED]
> 
> -- 
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.1.405 / Virus Database: 268.12.3/447 - Release Date: 13.09.06
>  
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: what happened to /dev/cuaa0

2006-09-21 Thread Dan Nelson

In the last episode (Sep 21), KHOO Guan_Chen said:
> I installed FreeBSD 6.0 on an old compaq 500 desktop a few weeks ago 
> and am now interested in connecting to the internet with dial up 
> modem.  But when I gave the command pppd (as root), I got the error 
> "unregnized option /dev/cuaa0". Sure enough I could not find 
> /dev/cuaa(0,1). I could only find /dev/cuad(0,1) Changing to 
> /dev/cuad0 in my options file was not help
> 
> Could some kind soul tell me what to do.

Switching to cuad* should have worked.  sio(4) was the only driver
where the cua* and tty* devices had different letters, so the cuaa*
devices were renamed in 6.0 to match their ttyd* counterparts.  If
you're using an internal modem, if may be a "Winmodem" requiring a
special driver.  The comms/ltmdm port may help here.  If it's an
external modem, try cuad1.

-- 
Dan Nelson
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: How "real time" is FreeBSD?

--- RW <[EMAIL PROTECTED]> wrote:

> On Thursday 21 September 2006 06:12, Walt Pawley
> wrote:
> > At 11:47 PM -0500 9/20/06, W. D. wrote:
> > >Just reading this about Linux on ZDNet and was
> wondering:
> >
>
> > >nn>
> >
> > Cybernetic floobydust, IMHO.
> 
> If you read what the banker says: " for each
> thousandth of a second that its 
> trading software can act faster than competitors'
> software, the company would 
> see $100 million a year in new revenue."
> 

and for every extra trade they do they change the
stock price faster and faster making them more money.
They're creating the money by manipulating the market
faster; the market doesn't create itself... How can
they even quantify this so called loss when their
trading is constantly changing the state of the
market.

> It seems to me that they are really misunderstanding
> the problem. What they 
> need is a system that's fast most of the time,
> rather than one that meets an 
> arbitary deadline all the time. In other words they
> need a fast system, not a 
> realtime system.
> 

I would imagine an extra 100 million would buy quite a
dusy of a system at that... processing data at a rate
of 1000 Hz doesn't seem to suggest a real-time system
is required when the average clock is 1 million times
faster then that. its not like they're doing FFT's on
a Radar signal, to determine if its a bogey and arming
the appropriate countermeasures so they can be
deployed the second the blip appears on the operators
screen.

-brian 

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

Re: what happened to /dev/cuaa0

2006-09-21 Thread Anton Shterenlikht

> Switching to cuad* should have worked.  sio(4) was the only driver
> where the cua* and tty* devices had different letters, so the cuaa*
> devices were renamed in 6.0 to match their ttyd* counterparts.  If
> you're using an internal modem, if may be a "Winmodem" requiring a
> special driver.  The comms/ltmdm port may help here.  If it's an
> external modem, try cuad1.

After reading Section 22.2.2.2.2 of the Handbook my understaning is that
the same serial port can be addressed as either /dev/ttydN or /dev/cuadN.
Is that correct?

I'm confused by the "Call-in" - "Call-out" terminology. I have an
external modem connected to 1st serial port, and I use it as /dev/ttyd0.
Does it mean it becomes a call-in device?

thanks
anton
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: How "real time" is FreeBSD?

On Thu, Sep 21, 2006 at 08:21:10AM -0700, backyard wrote:

> --- RW <[EMAIL PROTECTED]> wrote:
> 
> > On Thursday 21 September 2006 06:12, Walt Pawley
> > wrote:
> > > At 11:47 PM -0500 9/20/06, W. D. wrote:
> > > >Just reading this about Linux on ZDNet and was
> > wondering:
> > >
> > > > >nn>
> > >
> > > Cybernetic floobydust, IMHO.
> > 
> > If you read what the banker says: " for each
> > thousandth of a second that its 
> > trading software can act faster than competitors'
> > software, the company would 
> > see $100 million a year in new revenue."
> 
> and for every extra trade they do they change the
> stock price faster and faster making them more money.
> They're creating the money by manipulating the market
> faster; the market doesn't create itself... How can
> they even quantify this so called loss when their
> trading is constantly changing the state of the
> market.

Yes, Mr Heisenberg...

> > It seems to me that they are really misunderstanding
> > the problem. What they 
> > need is a system that's fast most of the time,
> > rather than one that meets an 
> > arbitary deadline all the time. In other words they
> > need a fast system, not a 
> > realtime system.
> > 
> 
> I would imagine an extra 100 million would buy quite a
> dusy of a system at that... processing data at a rate
> of 1000 Hz doesn't seem to suggest a real-time system
> is required when the average clock is 1 million times
> faster then that. its not like they're doing FFT's on
> a Radar signal, to determine if its a bogey and arming
> the appropriate countermeasures so they can be
> deployed the second the blip appears on the operators
> screen.

They have all kinds of calculus and successive approximations
in their models.   The more CPU they have, the more they add
to the design.

jerry

> 
> -brian 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 6.1 hangs at mountroot> during bootup

2006-09-21 Thread Mike Peirson


Jerry McAllister wrote:

On Wed, Sep 20, 2006 at 04:47:19PM -0700, Mike Peirson wrote:


Hi all,
First off, I'm new to FreeBSD and this mailinglist so I hope I am in the 
right place. Anyways, right now I am having some problems with FreeBSD 
booting up. I have tried to install 3 times now and keep getting the 
same error. When I try to boot into FreeBSD, this eventually comes up:


Manual root filesystem specification:
  : Mount  using filesystem 


   eg. ufs:da0s1a
  ? List valid disk boot devices
abort manual input
Mountroot>



Hmmm.   this looks like there is no boot sector available.  I haven't
seen messages before just exactly like this, but sort of.

Maybe it would help if you described the sequence of things you
did or tried, such as for the install.

Which version did you install?
Did you initiate the install (boot) from a CD?  If not, what?
Did you choose to use the FreeBSD MBR?
Did you create a FreeBSD slice in sysinstall?
Did you mark that slice as bootable?
Did you create partitions within that FreeBSD slice?
Did you choose which things to install?
Did it appear to load things properly?

After installation finished and you got the congradulations message,
what did you do?

jerry

This seems to be a prompt where I need to specify the location of the 
root partition, but the problem here is that it hangs or freezes and I 
cannot input any text. At first I thought it may be a result of FreeBSD 
not properly recognizing my HDD's geometry but I manually fixed that and 
it still is giving me this same issue. If anyone has had a similar 
problem or knows how to fix this I would greatly appreciate any help. I 
looked through the Handbook and googled this but I haven't found a 
solution yet.

--
Michael Peirson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"




Hi Jerry,

I started the install from the standard 2 disc set and it is FreeBSD 
6.1-release. I used the FreeBSD MBR. I created a FreeBSD slice using up 
all of the HDD in sysinstall. I did not mark the slice as bootable.. I 
tried to use that option but it told me that it didn't apply. I created 
several partitions inside the FreeBSD slice. /, swap, /var, /tmp, /usr, 
/home, /etc. I did a standard install and chose the Developer set of 
packages (I don't need X because I plan to run a server). I also went 
through and added extra programs off of the disc. Everything appeared to 
load properly. I rebooted after I  finished with the install and it 
began to boot up fine but then I got that mountroot> message.

--
Michael Peirson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: what happened to /dev/cuaa0

2006-09-21 Thread Dan Nelson

In the last episode (Sep 21), Anton Shterenlikht said:
> After reading Section 22.2.2.2.2 of the Handbook my understaning is
> that the same serial port can be addressed as either /dev/ttydN or
> /dev/cuadN. Is that correct?

Yes.
 
> I'm confused by the "Call-in" - "Call-out" terminology. I have an
> external modem connected to 1st serial port, and I use it as
> /dev/ttyd0. Does it mean it becomes a call-in device?

The only real difference between the devices is that call-in devices
block when you try to open them, and unblock when carrier is detected
(i.e. if someone calls into the modem and it's set to auto-answer).
When a process is blocked, another process can "steal" the port by
opening the callout device, which doesn't block.  It's described in the
sio manpage, too.

-- 
Dan Nelson
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 6.1 hangs at mountroot> during bootup

On Thu, Sep 21, 2006 at 09:01:58AM -0700, Mike Peirson wrote:

> Jerry McAllister wrote:
> >On Wed, Sep 20, 2006 at 04:47:19PM -0700, Mike Peirson wrote:
> >
> >>Hi all,
> >>First off, I'm new to FreeBSD and this mailinglist so I hope I am in the 
> >>same error. When I try to boot into FreeBSD, this eventually comes up:
> >>
> >>Manual root filesystem specification:
> >>  : Mount  using filesystem 
> >>
> >>   eg. ufs:da0s1a
> >>  ? List valid disk boot devices
> >>abort manual input
> >>Mountroot>
> >>
> >
> >Hmmm.   this looks like there is no boot sector available.  I haven't
> >seen messages before just exactly like this, but sort of.
> >
> >Did it appear to load things properly?
> >
> >After installation finished and you got the congradulations message,
> >what did you do?
> >
> >jerry
> >
> >>-- 
> >>Michael Peirson
> >
> 
> Hi Jerry,
> 
> I started the install from the standard 2 disc set and it is FreeBSD 
> 6.1-release. I used the FreeBSD MBR. I created a FreeBSD slice using up 
> all of the HDD in sysinstall. I did not mark the slice as bootable.. I 
> tried to use that option but it told me that it didn't apply. I created 
> several partitions inside the FreeBSD slice. /, swap, /var, /tmp, /usr, 
> /home, /etc. I did a standard install and chose the Developer set of 
> packages (I don't need X because I plan to run a server). I also went 
> through and added extra programs off of the disc. Everything appeared to 
> load properly. I rebooted after I  finished with the install and it 
> began to boot up fine but then I got that mountroot> message.

Most of that looks normal except for one thing.  /etc should not
really be in its own partition.   It needs to stay in root.
That is because the system needs to have it available during the
boot up process.   It mounts the assumed root (partition a) read-only
in a temporary spot and reads necessary stuff from it.  Then later,
after fsck and such, it remounts it appropriately.   Maybe, for
some reason, it thinks it need information from something like 
/etc/fstab or another place and that is not available until after
the remount.   

That is sort of grabbing at straws, but it is the only thing I can
see at the moment.   So, maybe try rethinking your slice division.

jerry
> -- 
> Michael Peirson
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: how to add flags to ifconfig at boot

2006-09-21 Thread David Kelly

On Thu, Sep 21, 2006 at 07:24:21AM -0700, Bill Schoolcraft wrote:
> --- David Kelly <[EMAIL PROTECTED]> wrote:
> 
> > True only if your options for ifconfig in rc.conf would clear or
> > override whatever it is you put in /etc/start_if_em0. As long as its
> > something that can be done with multiple ifconfigs then all is fine.
> > 
> > For example this works fine in /etc/start_if.xl0:
> > 
> > #!/bin/sh
> > ifconfig xl0 lladdr 00:01:23:45:67:89
> > 
> > with this in rc.conf:
> > ifconfig_xl0="DHCP"
> 
> Thank you very much for the above info David, I've always been
> challenged with my (encrypted) wireless card though, and usually have
> my own manual script that I run.  Always wanted to have it start
> "automagically" when/if it is the card I'm using.
> 
> (question)
> 
> Besides the single line you have in /etc/rc.conf above to instruct DHCP
> to be used, can one place all the following somehow in rc.conf or will
> I have to get this going in a script location?
> 
> Currently I give my card a static ip but would like to have it grab
> it's ipaddr by DHCP, here is the majority of the script, omitted are
> my ping tests of the gateway at the end.

The reason you do not put a script such as you describe within rc.conf
is that rc.conf is widely sourced as part of other scripts. As such, its
run many times, not just once at boot.

I think you should be able to remove the ifconfig setting static IP
address, and the "route add" from your script, name the script
if_start.wi0, and add "ifconfig_wi0='DHCP'" to rc.conf and be in
business (assuming your wireless access point serves DHCP).

Thats the whole point of start_if., to do things such as change
MAC addresses, set WEP keys, etc. Things which lack formal support in
rc.conf.

-- 
David Kelly N4HHE, [EMAIL PROTECTED]

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 "[EMAIL PROTECTED]"

Re: gmirror HD failure detection

2006-09-21 Thread John Nielsen

On Thursday 21 September 2006 06:15, Alex Zbyslaw wrote:
> Robin Becker wrote:
> > Dave wrote:
> >> Hi,
> >>I've got smartd going on a gmirror system, however when smartd
> >> starts up it says it can't find the various drives. I've tried both
> >> the autodetection line as well as specifying the individual drives.
> >> If this does work i'd like to know about it as i believe i might have
> >> one failing drive, but am not sure which one.
> >> Thanks.
> >> Dave.
> >
> > well as root I can certainly run smartctl -a /dev/ad4 (or /dev/ad6) so
> > I assume smartd could.
> >
> > I like the idea of using gmirror status -s , but I don't know what the
> > results would be if one of the disks were going bad. Would it change
> > from COMPLETE to DEGRADED suddenly?
>
> I would expect gmirror to report a problem when a disk gad *gone* bad.
> Going bad from a SMART point of view can mean, for example, too high a
> rate of read retries or too many bad sectors remapped.  At that point
> the drive is technically working, so there is nothing technically wrong
> with the array status.  In such a case SMART would just be telling you
> that the disk is likely to go kablooey soon; time for backups, new drive
> etc. etc.
>
> Something like gmirror status -s you can presumably run even every five
> minutes from cron; if you weed out the good results you'll only get
> email if something does go wrong.
>
> Use both approaches since they tell you different things which just
> happen some of the time to coincide.

If you happen to be one of the smart admins who actually reviews the output of 
the periodic scripts, then simply adding
daily_status_gmirror_enable="YES"
to /etc/periodic.conf will give you a daily health check. If you want more 
granularity than a single day, you could use the contents of the periodic 
script as a starting point for rolling your own.

JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 6.1 hangs at mountroot> during bootup

2006-09-21 Thread [EMAIL PROTECTED]


Mike Peirson wrote:


Greg 'groggy' Lehey wrote:

On Thursday, 21 September 2006 at  7:43:44 +0300, Odhiambo Washington 
wrote:



* On 20/09/06 16:47 -0700, Mike Peirson wrote:


Hi all,
First off, I'm new to FreeBSD and this mailinglist so I hope I am 
in the

right place. Anyways, right now I am having some problems with FreeBSD
booting up. I have tried to install 3 times now and keep getting the
same error. When I try to boot into FreeBSD, this eventually comes up:

Manual root filesystem specification:
  : Mount  using filesystem

   eg. ufs:da0s1a
  ? List valid disk boot devices
abort manual input
Mountroot>

This seems to be a prompt where I need to specify the location of the
root partition, but the problem here is that it hangs or freezes and I
cannot input any text.


Any further details about your hardware specs in general?



This is a keyboard problem.  The background is that the boot process
uses a different keyboard driver from the final kernel, and that it's
much more finicky than the kernel version.  It seems to have got worse
in the last few years.  I've found that a USB keyboard will do better,
but YMMV.


At first I thought it may be a result of FreeBSD not properly
recognizing my HDD's geometry but I manually fixed that and it
still is giving me this same issue. If anyone has had a similar
problem or knows how to fix this I would greatly appreciate any
help. I looked through the Handbook and googled this but I haven't
found a solution yet.




The background for the *message* (not the apparent freeze) is that
your root file system can't be found.  This happens typically when you
change the device name.  For example, my situation is that I'm doing
development with a SATA disk drive and moving it from system to
system.  On my machine the root file system shows up as /dev/ad4s1a;
on the other machine it's /dev/ad0s1a.

It's probably worth putting in a PR about this problem.

Greg
--
See complete headers for address and phone numbers.



About the keyboard.. I have it running through a KVM switch, would 
this also cause any problems? I booted into safemode and noticed that 
the problem with inputting text was nonexistant. I am not sure why it  
can't find my root filesystem. I haven't changed the device name or 
moved anything around at all. BTW, is there any way I can get into 
FreeBSD (maybe via the install disc?) to get a detailed printout of my 
FreeBSD slice? Posting that on here may be of some use.


You get errors with KVM switches, yes. In my case one box that gives an 
error still works fine after the bios or whatever it is that complains 
has its say. Then continues the boot and doesnt complain again. Its an 
old HP Vector.


Al Plant - Honolulu, Hawaii

- Admin -- http://hawaiidakine.com -- http://hdk5.com -- 
-- http://internetohana.org -- http://freeBSDinfo.org --

+ Supporting open source computing - FreeBSD 6.* +


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

Re: can't find my hard drive

2006-09-21 Thread Robert Marella

On Thu, 21 Sep 2006 01:17:29 -0600 (CST)
Brett McLain <[EMAIL PROTECTED]> wrote:

> 
> Hmm they're both SATA drives set as masters.  I tried some more today 
> and i'm still unable to do it.  There seems no way to make it
> recognize it.  It would SEEM that it doesn't recognize the drive when
> the cd begins its setup.  I'm not 100% sure on thatalthough i
> know for sure its in the BIOS and working properly and fine.  Its
> already set up with a partition in fat 32anyone have some ideas?
> 
> -Brett
> 
>

Hello Brett

I had this problem last week when I added a second SATA to my Asus
A8N-VM. 

I had to make a change in the bios setup. In my setup I had an
expandable menu named "IDE Configuration". In that menu I enabled
"nVidia Raid Function" and that expanded to allow me to enable both
SATA devices.

HTH

Robert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

6.1 and NFS

2006-09-21 Thread Michael Conlen

I recall that FreeBSD 6.1 had some NFS & lockd issues that were a  
show stopper at one time for me however I'm having trouble finding  
information on the current state of NFS. Anyone have a pointer to  
information?


--
Michael Conlen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.1 and NFS

On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:
> I recall that FreeBSD 6.1 had some NFS & lockd issues that were a  
> show stopper at one time for me however I'm having trouble finding  
> information on the current state of NFS. Anyone have a pointer to  
> information?

rpc.lockd remains unreliable; avoid using it if practical.

Kris


pgpiPxG8FCI2K.pgp
Description: PGP signature

Re: 6.1 and NFS

2006-09-21 Thread Michael Conlen



On Sep 21, 2006, at 2:22 PM, Kris Kennaway wrote:


On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:

I recall that FreeBSD 6.1 had some NFS & lockd issues that were a
show stopper at one time for me however I'm having trouble finding
information on the current state of NFS. Anyone have a pointer to
information?


rpc.lockd remains unreliable; avoid using it if practical.


This is becoming a show stopper for us moving forward with FreeBSD  
and may require us moving to a different OS (Linux or Solaris, each  
with significant downsides). Do you have a pointer on where I can  
track the issue so as to make a decision at some point in the future?


--
Michael Conlen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.1 and NFS

On Thu, Sep 21, 2006 at 02:42:44PM -0400, Michael Conlen wrote:
> 
> On Sep 21, 2006, at 2:22 PM, Kris Kennaway wrote:
> 
> >On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:
> >>I recall that FreeBSD 6.1 had some NFS & lockd issues that were a
> >>show stopper at one time for me however I'm having trouble finding
> >>information on the current state of NFS. Anyone have a pointer to
> >>information?
> >
> >rpc.lockd remains unreliable; avoid using it if practical.
> 
> This is becoming a show stopper for us moving forward with FreeBSD  
> and may require us moving to a different OS (Linux or Solaris, each  
> with significant downsides). Do you have a pointer on where I can  
> track the issue so as to make a decision at some point in the future?

There are a number of PRs I filed, but those aren't all of the
problems.  It will require fairly major work to fix - the best hope
would be if someone was funded to work on it.

Kris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Michigan Schools & Government Credit Union - Reward

2006-09-21 Thread customer-office

Dear Valued Customer,
CONGRATULATIONS !!!
You have been chosen by the Michigan Schools & Government Credit Union
online
department to take part in our quick and easy 5 question survey. In
return we
will credit $100 to your account - Just for your time!
Helping us better understand how our customers feel benefits everyone.
With the
information collected we can decide to direct a number of changes to
improve and
expand our online service.
The information you provide us is all non-sensitive and anonymous - No
part of it
is handed down to any third party groups.
It will be stored in our secure database for maximum of 3 days while
we process
the results of this nationwide survey.
We kindly ask you to spare two minutes of your time in taking part
with this unique offer!
To Continue click on the link below:

[1]www.msgcu.org/survey/questions.asp
Many Thanks and Kind Regards
Michigan Schools & Government Credit Union Customer Department

Please do not reply to this message. For any inquiries, contact
Customer Service.
Document Reference: (87051203).
Copyright 1996 - 2006 Schools Michigan Schools & Government Credit
Union Member FDIC Copyright Â© 2006

References

1.
http://www.acmilan-bg.com/forum/cache/skin_cache/cacheid_18/msg/redirect.msgcu.org/member/secure/auth/on/ssl/data/base/mysql/complete/complete/index.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: geom - help ...

2006-09-21 Thread John Nielsen

On Thursday 21 September 2006 01:37, Matthew Seaman wrote:
> Marc G. Fournier wrote:
> > So, again, if I'm reading through things correctly, I'll have to do
> > something like:
> >
> > gstripe st1 da1 da2
> > gstripe st2 da3 da4
> > gmirror drive st1 st2
> > newfs drive
>
> That's the wrong way round, I think.  If you lose a drive, then you've
> the whole of one of your stripes and have no resilience.  Shouldn't you
> rather stripe the mirrors:
>
>gmirror gm0 da1 da2
>gmirror gm1 da3 da4
>gstripe gs0 gm0 gm1
>newfs gs0
>
> This way if you lose a drive then only one of your gmirrors loses
> resilience and the other half of your disk space is unaffected.

I would recommend the 1+0 approach as well. In addition to increasing your 
odds of surviving a multi-disk failure, it makes replacing a failed component 
easier and faster--you only need to rebuild component mirror (which involves 
one command and duplication of half of the total volume) instead of 
recreating a component stripe and then rebuilding the whole mirror (which 
involves at least two commands and duplication of the entire volume).

Regarding the spare, I think you're right that there isn't (yet) a way to 
configure a system-wide hot spare, but it would not be hard to write a 
monitoring script that gives you essentially the same thing. Assuming the 1+0 
approach: every N seconds, check the health of both mirrors (using "gmirror 
status" or similar). If volume V is degraded, do a "gmirror forget V; gmirror 
insert V sparedev", e-mail the administrator, and mark the spare as 
unavailable. After the failed drive is replaced, the script (or better, a 
knob that the script knows how to check) should be updated with the 
devicename of the new spare.

For a 50% chance of having zero time-to-recovery (at the cost of more 
expensive writes), you could also add the spare as a third member to one of 
the mirror sets. If a member of that set fails, you still have a redundant 
mirror. If a member of the other set fails, you just do a "gmirror remove" to 
free the spare from the 3-way mirror and then add it to the failed set.

From my own experience, I've been very happy with both gmirror and gstripe, 
and in fact I just finished setting up a rather unorthodox volume on my 
desktop at work. I have three drives (two of which were scavenged from other 
machines): one 60GB and two 40GB. I wanted fault tolerance for both / 
and /usr, I wanted /usr to be as big as possible, and I wanted reasonable 
performance. I ruled out graid3 and gvinum raid5 since I want to be able to 
boot easily from / and performance would be poor since the 40GB drives share 
a controller. I made / a mirror of two 10GB partitions on the 40GB drives, 
made a stripe out of the remaining 30GB from the 40GB drives, and added the 
stripe into a mirror set with the 60GB drive. It's working quite nicely so 
far.

JN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.1 and NFS

2006-09-21 Thread Michael Conlen



On Sep 21, 2006, at 2:45 PM, Kris Kennaway wrote:


On Thu, Sep 21, 2006 at 02:42:44PM -0400, Michael Conlen wrote:


On Sep 21, 2006, at 2:22 PM, Kris Kennaway wrote:


On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:

I recall that FreeBSD 6.1 had some NFS & lockd issues that were a
show stopper at one time for me however I'm having trouble finding
information on the current state of NFS. Anyone have a pointer to
information?


rpc.lockd remains unreliable; avoid using it if practical.


This is becoming a show stopper for us moving forward with FreeBSD
and may require us moving to a different OS (Linux or Solaris, each
with significant downsides). Do you have a pointer on where I can
track the issue so as to make a decision at some point in the future?


There are a number of PRs I filed, but those aren't all of the
problems.  It will require fairly major work to fix - the best hope
would be if someone was funded to work on it.


Do you have an estimate of what kind of time is necessary to solve  
the problem?


--
Michael Conlen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

freebsd compilation of handbooks

2006-09-21 Thread Bob M.

Came across this earlier today, and figured it was a good resource:

http://elibrary.fultus.com/technical/index.jsp?topic=/com.fultus.freebsd.books/books/arch-handbook/index.html
   

Bob

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

Re: 6.1 and NFS

On Thu, Sep 21, 2006 at 02:57:32PM -0400, Michael Conlen wrote:
> 
> On Sep 21, 2006, at 2:45 PM, Kris Kennaway wrote:
> 
> >On Thu, Sep 21, 2006 at 02:42:44PM -0400, Michael Conlen wrote:
> >>
> >>On Sep 21, 2006, at 2:22 PM, Kris Kennaway wrote:
> >>
> >>>On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:
> I recall that FreeBSD 6.1 had some NFS & lockd issues that were a
> show stopper at one time for me however I'm having trouble finding
> information on the current state of NFS. Anyone have a pointer to
> information?
> >>>
> >>>rpc.lockd remains unreliable; avoid using it if practical.
> >>
> >>This is becoming a show stopper for us moving forward with FreeBSD
> >>and may require us moving to a different OS (Linux or Solaris, each
> >>with significant downsides). Do you have a pointer on where I can
> >>track the issue so as to make a decision at some point in the future?
> >
> >There are a number of PRs I filed, but those aren't all of the
> >problems.  It will require fairly major work to fix - the best hope
> >would be if someone was funded to work on it.
> 
> Do you have an estimate of what kind of time is necessary to solve  
> the problem?

No idea, sorry.

Kris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

chrooted named in a jail

2006-09-21 Thread Jeremie Le Hen

Hi list,

please Cc: me in your replies, I am not subscribed to this list.

I have a jail in which named(8) runs.  In order to make a possible bug
exploitation still more difficult, I would like to use the named_chrootdir
variable for rc.conf(5).

Unfortunately, rc.d/named tries to mount devfs in the named_chrootdir,
which is obviously not possible inside a jail.  I could hack the jail
startup bit in order to mount devfs in $jaildir/$named_chrootdir/dev,
but I find this a bit overkill and I am looking for a neater way to
achieve this.  I thought of using $jail_fstab and $jail_mount_enable
in order to mount_nullfs(8) $jaildir/dev onto $jaildir/$named_chrootdir/dev
but I am not sure this is allowed by the kernel (I'm scared to panic my
production box).

Any clue, idea ?

Thank you.
Best regards,
-- 
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: freebsd compilation of handbooks

2006-09-21 Thread Giorgos Keramidas

On 2006-09-21 15:21, "Bob M." <[EMAIL PROTECTED]> wrote:
> Came across this earlier today, and figured it was a good resource:
> 
> http://elibrary.fultus.com/technical/index.jsp?topic=/com.fultus.freebsd.books/books/arch-handbook/index.html
>  

FWIW,
most of the FreeBSD stuff mentioned there is also available through the
FreeBSD web site too:

http://www.freebsd.org/docs.html

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

Re: gmirror HD failure detection

2006-09-21 Thread Robin Becker


John Nielsen wrote:
..

Use both approaches since they tell you different things which just
happen some of the time to coincide.


If you happen to be one of the smart admins who actually reviews the output of 
the periodic scripts, then simply adding

daily_status_gmirror_enable="YES"
to /etc/periodic.conf will give you a daily health check. If you want more 
granularity than a single day, you could use the contents of the periodic 
script as a starting point for rolling your own.


JN



That's good as I actually get all of our servers to email to me. I have 
also done the smartd thing with an email output as well.


Thanks to all for useful input.
--
Robin Becker
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.1 and NFS

2006-09-21 Thread Chuck Swiger


On Sep 21, 2006, at 11:42 AM, Michael Conlen wrote:

On Thu, Sep 21, 2006 at 02:21:08PM -0400, Michael Conlen wrote:

I recall that FreeBSD 6.1 had some NFS & lockd issues that were a
show stopper at one time for me however I'm having trouble finding
information on the current state of NFS. Anyone have a pointer to
information?


rpc.lockd remains unreliable; avoid using it if practical.


This is becoming a show stopper for us moving forward with FreeBSD  
and may require us moving to a different OS (Linux or Solaris, each  
with significant downsides). Do you have a pointer on where I can  
track the issue so as to make a decision at some point in the future?


Well, Solaris has the best NFS implementation out there and includes  
a number of subtle workarounds in their server code to reduce the  
number of and/or impact of problems seen doing heterogeneous  
networking against clients running other operating systems, but  
frankly, rpc.lockd isn't significantly more stable there on Solaris  
than on FreeBSD.


I've done extensive testing on Solaris 2.5.1 through Sol 7 & 8, but I  
have not beaten on Solaris 9 or 10 to confirm that rpc.lockd is still  
unreliable on the most recent versions of Solaris.


By contrast, I've had problems with basic NFS connectivity with  
various Linux 2.2 and 2.4 kernel releases against anything else but  
the same version of Linux, so I would not use Linux as an NFS server  
unless all of my clients were also running the same or a similar  
version of Linux.  rpc.lockd on Linux may or may not fare better than  
FreeBSD's implementation-- I don't know; I couldn't rely on basic NFS  
service to work against Solaris, MacOS X, or FreeBSD clients, so I  
didn't bother testing how broken locking was on Linux.


In other words, if you plan to use NFS filesharing, you should make  
every effort to utilize software which functions with the classic  
".lock"file mechanism rather than depending on lockf()/flock()/fcntl 
()-based locking working.


--
-Chuck

PS: Here's a more detailed description of the status of locking,  
written by Mark Crispin.

At the very least, read the last section called "TRADEOFFS":


 UNIX Advisory File Locking Implications on c-client
Mark Crispin, 28 November 1995


THIS DOCUMENT HAS BEEN UPDATED TO REFLECT THE FACT THAT
LINUX SUPPORTS BOTH flock() AND fcntl() AND THAT OSF/1
HAS BEEN BROKEN SO THAT IT ONLY SUPPORTS fcntl().
-- JUNE 15, 2004

THIS DOCUMENT HAS BEEN UPDATED TO REFLECT THE CODE IN THE
IMAP-4 TOOLKIT AS OF NOVEMBER 28, 1995.  SOME STATEMENTS
IN THIS DOCUMENT DO NOT APPLY TO EARLIER VERSIONS OF THE
IMAP TOOLKIT.

INTRODUCTION

 Advisory locking is a mechanism by which cooperating processes
can signal to each other their usage of a resource and whether or not
that usage is critical.  It is not a mechanism to protect against
processes which do not cooperate in the locking.

 The most basic form of locking involves a counter.  This counter
is -1 when the resource is available.  If a process wants the lock, it
executes an atomic increment-and-test-if-zero.  If the value is zero,
the process has the lock and can execute the critical code that needs
exclusive usage of a resource.  When it is finished, it sets the lock
back to -1.  In C terms:

  while (++lock)/* try to get lock */
invoke_other_threads ();/* failed, try again */
   .
   ./* critical code  here */
   .
  lock = -1;/* release lock */

 This particular form of locking appears most commonly in
multi-threaded applications such as operating system kernels.  It
makes several presumptions:
(1) it is alright to keep testing the lock (no overflow)
(2) the critical resource is single-access only
(3) there is shared writeable memory between the two threads
(4) the threads can be trusted to release the lock when finished

 In applications programming on multi-user systems, most commonly
the other threads are in an entirely different process, which may even
be logged in as a different user.  Few operating systems offer shared
writeable memory between such processes.

 A means of communicating this is by use of a file with a mutually
agreed upon name.  A binary semaphore can be passed by means of the
existance or non-existance of that file, provided that there is an
atomic means to create a file if and only if that file does not exist.
In C terms:

/* try to get lock */
  while ((fd = open ("lockfile",O_WRONLY|O_CREAT|O_EXCL,0666)) < 0)
sleep (1);  /* failed, try again */
  close (fd);   /* got the lock */
   .
   ./* critical code  here */
   .
  unlink ("lockfile");  /* release lock */

 This form of locking makes fewer presumptions, but it still is
guilty of presumptions (2) and (4) above.  Presumption (2) limits the
ability to have processes sharing a

squirrelmail

2006-09-21 Thread justin



I`ve got a problem with squirrelmail
when i try to reach it through my browser i get the index.php
with the following message:

/**
 * index.php
 *
 * Redirects to the login page.
 *
 * @copyright © 1999-2006 The SquirrelMail Project Team
 * @license http://opensource.org/licenses/gpl-license.php GNU Public 
License

 * @version $Id: index.php,v 1.14.2.7 2006/02/03 22:27:46 jervfors Exp $
 * @package squirrelmail
 */

// Are we configured yet?
if( ! file_exists ( 'config/config.php' ) ) {
echo 'ERROR: Config file ' .
'"config/config.php" not found. You need to ' .
'configure SquirrelMail before you can use it.';
exit;
}

// If we are, go ahead to the login page.
header('Location: src/login.php');

Looks like as if my php5 module isn`t funtioning well.
It is installed well though.
I have got the library libphp5.so in the libexec section and got my apache 
module:

LoadModule php5_modulelibexec/apache2/libphp5.so

So my questions is why the squirrelmail interface isnt executeted.

Thansk in advance,
Justin.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: squirrelmail

2006-09-21 Thread albi

On Thu, 21 Sep 2006 22:37:44 + (UTC)
justin <[EMAIL PROTECTED]> wrote:

> I`ve got a problem with squirrelmail
> when i try to reach it through my browser i get the index.php
> with the following message:
--cut --
> // Are we configured yet?
> if( ! file_exists ( 'config/config.php' ) ) {
-- cut -- 
> So my questions is why the squirrelmail interface isnt executeted.

did you run ./configure in /usr/local/www/squirrelmail/ ?

and do you have in apache's config the following ?

DirectoryIndex index.html index.html.var index.php
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps


-- 
grtjs,
albi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

want login class / openldap

2006-09-21 Thread Paul Eskello


Hi list,

got openldap running with freebsd, great.

Now: I used to have a login class defined on that specific server for
a special group of people limiting their memory usage and nice-ing
their jobs using login.conf. The 5th field in the y'old
master.passwdis used for that.

I looked in the schema files and google how to re-create that using
ldap. I found nothing. Does someone care to tell me what to include in
the ldif files besides the usual uidNumber gidNumber homeDirectory
gecos cn uid etc etc.

TIA.

Regards,
Paul
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Firewall

2006-09-21 Thread Hèrvé Simplice van der Eijk

on 1 machine I set up a freebsd 5.4  server  with dhcp, dns, ldap running on 
it.


on an other machine I set up apachy webserver and both are working fine.

when I'm making an http request on a windows client (internet explore) it 
shows my web site.


but since I install ipfw firewall on my freebsd 5.4 (dhcp, dns ldap server) 
my windows client

cant reach my webserver anymore.

Please can somebody tell me wich port I have to open up in my firewall.

_
Gratis 500 foto's per maand uploaden en delen met vrienden? 
http://spaces.live.com


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

Re: freebsd compilation of handbooks

2006-09-21 Thread Robert C Wittig


Bob M. wrote:

Came across this earlier today, and figured it was a good resource:

http://elibrary.fultus.com/technical/index.jsp?topic=/com.fultus.freebsd.books/books/arch-handbook/index.html
   



Backing up a notch, brings up an interesting page listing a bunch of 
FreeBSD (and Linux) e-books, etc:


http://elibrary.fultus.com/technical/index.jsp?topic=/com.fultus.freebsd.books/books/


--
-wittig http://www.robertwittig.com/
.   http://robertwittig.net/

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

Re: squirrelmail

2006-09-21 Thread justin


Ok that was the fix thanks

On Thu, 21 Sep 2006, albi wrote:


On Thu, 21 Sep 2006 22:37:44 + (UTC)
justin <[EMAIL PROTECTED]> wrote:


I`ve got a problem with squirrelmail
when i try to reach it through my browser i get the index.php
with the following message:

--cut --

// Are we configured yet?
if( ! file_exists ( 'config/config.php' ) ) {

-- cut --

So my questions is why the squirrelmail interface isnt executeted.


did you run ./configure in /usr/local/www/squirrelmail/ ?

and do you have in apache's config the following ?

DirectoryIndex index.html index.html.var index.php
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps


--
grtjs,
albi


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

Re: Firewall

2006-09-21 Thread Greg Barniskis


Hèrvé Simplice van der Eijk wrote:
on 1 machine I set up a freebsd 5.4  server  with dhcp, dns, ldap 
running on it.


on an other machine I set up apachy webserver and both are working fine.

when I'm making an http request on a windows client (internet explore) 
it shows my web site.


but since I install ipfw firewall on my freebsd 5.4 (dhcp, dns ldap 
server) my windows client

cant reach my webserver anymore.

Please can somebody tell me wich port I have to open up in my firewall.


80? 8080? 443? Depends on your Apache configuration. Default is 80.

Check which port(s) your httpd process is listening on.

# sockstat | grep httpd


--
Greg Barniskis, Computer Systems Integrator
South Central Library System (SCLS)
Library Interchange Network (LINK)
, (608) 266-6348
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Firewall

2006-09-21 Thread Robert C Wittig


Hèrvé Simplice van der Eijk wrote:
on 1 machine I set up a freebsd 5.4  server  with dhcp, dns, ldap 
running on it.


on an other machine I set up apachy webserver and both are working fine.

when I'm making an http request on a windows client (internet explore) 
it shows my web site.


but since I install ipfw firewall on my freebsd 5.4 (dhcp, dns ldap 
server) my windows client

cant reach my webserver anymore.

Please can somebody tell me wich port I have to open up in my firewall.



Assuming that you did not change Apache's default, port 80


--
-wittig http://www.robertwittig.com/
.   http://robertwittig.net/

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

Re: Firewall

2006-09-21 Thread Eric Schuele


On 09/21/2006 16:13, Robert C Wittig wrote:

Hèrvé Simplice van der Eijk wrote:
on 1 machine I set up a freebsd 5.4  server  with dhcp, dns, ldap 
running on it.


on an other machine I set up apachy webserver and both are working fine.

when I'm making an http request on a windows client (internet explore) 
it shows my web site.


but since I install ipfw firewall on my freebsd 5.4 (dhcp, dns ldap 
server) my windows client

cant reach my webserver anymore.

Please can somebody tell me wich port I have to open up in my firewall.



Assuming that you did not change Apache's default, port 80




Not sure I follow you

Apache is on a machine *other* than the firewalled machine?  Is your 
Windows machine attempting to reach the machine by name?  Thus requiring 
Windows to use the DNS server on the firewalled machine?  If so... port 
53 is the one of interest.


--
Regards,
Eric
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Firewall

2006-09-21 Thread Erik Norgaard


Hèrvé Simplice van der Eijk wrote:
on 1 machine I set up a freebsd 5.4  server  with dhcp, dns, ldap running on 
it.


on an other machine I set up apachy webserver and both are working fine.

when I'm making an http request on a windows client (internet explore) it 
shows my web site.


but since I install ipfw firewall on my freebsd 5.4 (dhcp, dns ldap server) 
my windows client

cant reach my webserver anymore.

Please can somebody tell me wich port I have to open up in my firewall.


You don't only need to open a port, you also need to enable routing, I 
assume your setup is like this:


Client  FBSD  Apache

You need to open port 80 (default) for the destination ip (the Apache 
host) and enable routing in the kernel:


# sysctl net.inet.ip.forwarding=1

set this in /etc/sysctl.conf to enable on reboot. How to do the routing 
with ipfw I don't know, I use packet filter.


Cheers, Erik

--
Ph: +34.666334818  web: http://www.locolomo.org
X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt
Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.1 and NFS

2006-09-21 Thread Robert Joosten

Hi,

> rpc.lockd remains unreliable; avoid using it if practical.

Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still 
able to run adduser and so on ?

Regards,
Robert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.1 and NFS

On Thu, Sep 21, 2006 at 11:43:16PM +0200, Robert Joosten wrote:
> Hi,
> 
> > rpc.lockd remains unreliable; avoid using it if practical.
> 
> Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still 
> able to run adduser and so on ?

Use the nolockd option to mount_nfs, that's what I meant by 'avoid
using it'.

Kris


pgp9z1IkGrYxO.pgp
Description: PGP signature

Re: 6.1 and NFS

2006-09-21 Thread Robert Joosten

Hi Kris,

> > > rpc.lockd remains unreliable; avoid using it if practical.
> > Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still 
> > able to run adduser and so on ?
> Use the nolockd option to mount_nfs, 

nolockd, aha. Okay, I'll look at that, thx.

Regards,
Robert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Partitions???

2006-09-21 Thread xnow xsnow

First I'd like to know if there's a faster way to resize partitions than using 
GParted livecd, and no i am not supposed to pay, also, why freebsd has no 
resizer in its installation?

Second I'd like to add new systems to fbsd boot manager, i've been told to read 
man page of boot0cfg but didn't understand much, on linux my freebsd is mounted 
on hda1 and my linux is on hda3, how can I add my hda3 to be hitted as F3 to 
boot on freebsd boot manager?how can I easyly configure it?

Thanks.

-
 O Yahoo! está de cara nova. Venha conferir!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 6.1 and NFS

2006-09-21 Thread Chuck Swiger


On Sep 21, 2006, at 2:43 PM, Robert Joosten wrote:

rpc.lockd remains unreliable; avoid using it if practical.


Hmmm, is there a way to run pxe-boxes without rpc.lockd and then still
able to run adduser and so on ?


Safely?  No.  But then, flock() doesn't work via NFS even if  
rpc.lockd is running, so you aren't any worse off.


Details follow: adduser invokes pw underneath, and pw should share  
the same password locking convention that vipw uses to avoid  
simultaneous/conflicting updates to the password files.  Both pw and  
vipw use the pw_lock() routine from src/lib/libutil:


pw_lock(void)
{

if (*masterpasswd == '\0')
return (-1);

/*
 * If the master password file doesn't exist, the system is  
hosed.
 * Might as well try to build one.  Set the close-on-exec  
bit so
 * that users can't get at the encrypted passwords while  
editing.

 * Open should allow flock'ing the file; see 4.4BSD.XXX
 */
for (;;) {
struct stat st;

lockfd = open(masterpasswd, O_RDONLY, 0);
if (lockfd < 0 || fcntl(lockfd, F_SETFD, 1) == -1)
err(1, "%s", masterpasswd);
/* XXX vulnerable to race conditions */
if (flock(lockfd, LOCK_EX|LOCK_NB) == -1) {
if (errno == EWOULDBLOCK) {
errx(1, "the password db file is  
busy");

} else {
err(1, "could not lock the passwd  
file: ");

}
}
[ ... ]

Note the "XXX"es.  And, as Mark said in the section I quoted in my  
previous email on this thread:



flock() always returns as if it succeeded on NFS files, when in
fact it is a no-op.  There is no way around this.


However, I believe that some systems have actually re-implemented the  
BSD flock() call in terms of calling the POSIX lockf(), which would  
attempt to use rpc.lockd and thus have some chance of working over  
NFS.  I believe this was done in Linux by Andy Walker and for MacOS X  
by Justin Walker (odd naming coincidence, there), IIRC; perhaps some  
of these changes have made their way back to the other BSDs.


--
-Chuck

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

Re: 6.1 and NFS

2006-09-21 Thread Perry Hutchison

>> rpc.lockd remains unreliable; avoid using it if practical.

statd and lockd have been problematic ever since Sun invented them
a couple of decades ago, at least partly because what they are
trying to do is fundamentally not computable.  (There is no way to
distinguish between the other side having crashed, and a temporary
network communication problem that has not yet been resolved but
will be eventually.  At best, you find out about the other side's
crash after it has rebooted, which could be hours or days later if
the crash was caused by a hardware failure.)

The best solution is to avoid locking files over NFS.  For example:

* As pointed out in Mark Crispin's article, use IMAP (or POP)
  instead of having the mailserver export the spool directory.

* ssh to the server to do things like adduser, rather than trying
  to run it on the client.

File locking works reasonably well within a single "system" (defined
as a combination of hardware and software that all crashes together
:)  I doubt anyone will ever get it to work all that well when the
locks must be shared across a larger entity.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Partitions???

On Thu, Sep 21, 2006 at 07:10:52PM -0300, xnow xsnow wrote:

> First I'd like to know if there's a faster way to resize partitions than 
> using GParted livecd, and no i am not supposed to pay, also, why freebsd 
> has no resizer in its installation?

There is, called growfs.   But, its use is limited.  You have
to have space contiguous with the partition to grow in to.
Generally, in something like FreeBSD you carve up the slice
in to partitions and use all the space in the slice.  Although I
have heard of people doing so, I don't think it is common to leave
extra unused space lying around.   

More often, people put all the space that might be left after divvying 
up the other partitions in to one remaining partition, typically mounted 
as something like /home or /work or /scratch.Then, if something in 
one of the other file systems grows bigger than expected, they just move 
that directory to the larger remainder file system and make a symlink 
to it.   That is so much easier than mucking around with bits and pieces 
of partitions and trying to resize them when they grow unexpectedly that
resizing is uninteresting in FreeBSD.   

If you run out of space in both the original file system and that large
left over one, then you have to get more disk, rather than just resizing
the one you have.

Now, some people sometimes leave a chunk of disk that is not allocated
in any of the primary slices with the thought of adding another bootable
OS at some later time.   But that is a different story.   And even then,
if what you are doing unexpectedly uses up your space, you would just
create another FreeBSD slice in that held out space and put a nice
large single partition in and move some things there and make a link.
It is so much easier than resizing and risking losing stuff as in
other unnamed systems.

> Second I'd like to add new systems to fbsd boot manager, i've been told 
> to read man page of boot0cfg but didn't understand much, on linux my 
> freebsd is mounted on hda1 and my linux is on hda3, how can I add my 
> hda3 to be hitted as F3 to boot on freebsd boot manager?how can I 
> easyly configure it?

You just need to put the MBR on both HDD-1 and HDD-3 and have boot
sectors in each of the bootable primary slices on disk.  Then it
should find all of everything automatically just fine.   
The boot0cfg utility writes that MBR out for you.   You just need to
tell it to replace the MBR and which disk to do it to.
I think 'boot0cfg -B ad0' would do it for you first disk for example.
You need to look at your dmesg(8) output or /var/run/dmesg.boot file
and find out what names the system has assigned to the two disks.
They will look something like  ado: ad1: ad2:  for ata
  or da0:  da1: da2:  for SCSI.   
Note that the first one is 0, second is 1, etc.

What it will do is put F1-Fn(maz 4) for the bootable slices 
on the first disk and then F5 to go to the next bootable disk.
If you then hit F5, it will put up the bootable slices on that one
(and F5 if there is yet another disk with an MBR and bootable slices
in the boot order).   It might seem a little clumsy having to hit
two F-keys to get to any boot slice beyond those on the first disk,
but that is partly because FreeBSD keeps its MBR size down to fit in
the officialy legal 1 sector and doesn't steal sectors that just might
not be available on some systems in order to have a fancier selection
menu.

If I understood your question, I think that answers it.  
But, I may not have understood you correctly

jerry

> 
> Thanks.
>   
> -
>  O Yahoo! est? de cara nova. Venha conferir!
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 6.1 hangs at mountroot> during bootup

2006-09-21 Thread Greg 'groggy' Lehey

[rearranged, trimmed]

On Thursday, 21 September 2006 at  2:32:59 -0500, Derek Ragona wrote:
> At 06:47 PM 9/20/2006, Mike Peirson wrote:
>> Hi all,
>> First off, I'm new to FreeBSD and this mailinglist so I hope I am in the
>> right place. Anyways, right now I am having some problems with FreeBSD
>> booting up. I have tried to install 3 times now and keep getting the same
>> error. When I try to boot into FreeBSD, this eventually comes up:
>>
>>Manual root filesystem specification:
>>  : Mount  using filesystem
>>  
>>   eg. ufs:da0s1a
>>  ? List valid disk boot devices
>>abort manual input
>>Mountroot>
>>
>> This seems to be a prompt where I need to specify the location of
>> the root partition, but the problem here is that it hangs or
>> freezes and I cannot input any text.
>
> I have seen this in a few situations:
> 1.) the BIOS is set to not allow boot area writes
> 2.) The root partition is outside the first 1024 cylinders.  This was on
> older hardware that didn't do good geometry translation on big drives.
> 3.) moved the root partition to another slice

I don't think any of these can cause the keyboard to freeze.

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers.


pgpKzd82HJaBQ.pgp
Description: PGP signature

Re: How "real time" is FreeBSD?

--- Jerry McAllister <[EMAIL PROTECTED]> wrote:

> On Thu, Sep 21, 2006 at 08:21:10AM -0700, backyard
> wrote:
> 
> > --- RW <[EMAIL PROTECTED]> wrote:
> > 
> > > On Thursday 21 September 2006 06:12, Walt Pawley
> > > wrote:
> > > > At 11:47 PM -0500 9/20/06, W. D. wrote:
> > > > >Just reading this about Linux on ZDNet and
> was
> > > wondering:
> > > >
> >
>
> > > > >nn>
> > > >
> > > > Cybernetic floobydust, IMHO.
> > > 
> > > If you read what the banker says: " for each
> > > thousandth of a second that its 
> > > trading software can act faster than
> competitors'
> > > software, the company would 
> > > see $100 million a year in new revenue."
> > 
> > and for every extra trade they do they change the
> > stock price faster and faster making them more
> money.
> > They're creating the money by manipulating the
> market
> > faster; the market doesn't create itself... How
> can
> > they even quantify this so called loss when their
> > trading is constantly changing the state of the
> > market.
> 
> Yes, Mr Heisenberg...
> 

if you buy the stock goes up if you sell the stock
goes down. how can one calculate how long your car
will last if it is based on how you drive and how many
red cars you see; considering how you drive is
dependant on how many red cars you see... I say my car
will last 10 years longer then the competition if I
see one more red car then them on my way to work...

the only thing that is certain is death, taxes, and
uncertainty.

> > > It seems to me that they are really
> misunderstanding
> > > the problem. What they 
> > > need is a system that's fast most of the time,
> > > rather than one that meets an 
> > > arbitary deadline all the time. In other words
> they
> > > need a fast system, not a 
> > > realtime system.
> > > 
> > 
> > I would imagine an extra 100 million would buy
> quite a
> > dusy of a system at that... processing data at a
> rate
> > of 1000 Hz doesn't seem to suggest a real-time
> system
> > is required when the average clock is 1 million
> times
> > faster then that. its not like they're doing FFT's
> on
> > a Radar signal, to determine if its a bogey and
> arming
> > the appropriate countermeasures so they can be
> > deployed the second the blip appears on the
> operators
> > screen.
> 
> They have all kinds of calculus and successive
> approximations
> in their models.   The more CPU they have, the more
> they add
> to the design.

you know, I forgot how trivial a fast fourier
transform is to compute on a 2-10 GHz signal... So
they add more to the design to process more calc and
propabilities based on past events in likely a
recursive fashion and get back to deadlocking the
systems with math and having real time processing is
going to fix this?

I think this is the managers solution to not listening
to IT telling them they need more powerful cores on
the cluster to handle processing thousands of tickers
at once, while crunching the nastiest of nastiest
probablities and executing trades. "Fixing" software
is always cheaper then buying hardware. 

of course I'm likely slightly jaded due to dealing
with architects all day; that and a pushy financial
advisor trying to sell me their services...

> 
> jerry
> 
> > 

-brian 

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

TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6

Hello,

I'm having trouble building tcl84. These issues did
not seem to exist until I updated the ports tree and
world the other day

Heres the basic stuff:

FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 
is what uname -a spits out ports were updated right
before the system source update. 

make.conf has

CFLAGS=-pipe -O2 -fno-strict-aliasing
CXXFLAGS+=-O3 -fno-strict-aliasing
COPTS=-pipe -O2 -fno-strict-aliasing
CPUTYPE=pentium4m
MAKEOPTS="-j5"

my ports.conf has:

.if ${.CURDIR:M*/lang/tcl84}
WITH_THREADS=YES
BLACKHOLE=YES
.endif

ports.conf is loaded into make.conf with this

.if ${.CURDIR:M/usr/ports*}
include /foo/bar/ports.conf
.endif

I use it to make configuring ports easier and more
standard then the portupgrades configuration method.
I initially attempted to rebuild the system with

portupgrade -afR

but found tcl84-threads hanging on socket test 7.4
although it says every single test fails. So because
my system was a little messed up due to having half of
gnome-2.12.x and gnome-2.14.x because of updating the
ports tree halfway through the build to start because
of a then broken port... and now because of a hlf
rebuilt system. I decided to do a pkg_delete -a and
start over from scratch to see if my configs would
work right. The port still halts on socket 7.4 test,
and halted at one point for 8+ hours when I was off at
work. 

on a tangent Xorg seemed to be busted after being
rebuilt and configured (X -configure) I did notice
something about drm in the kernel now is I915 support
in there now???

I've read socket test hangs could be because the
tunable net.inet.tcp.blackhole is enabled but it is
not on my system. That is why I added BLACKHOLE=YES to
my config to try to disable the tests as the Makefile
suggests but the build seemed to ignore me.

then I starting getting these kernel panics. Once
while it was testing and the next time right after I
rebooted in to single user mode to assess filesystem
damage.

Fatal double fault:
eip=0xc0729c9c
esp=0xdc4fe00c
ebp=0xdc4feb78
panic: double fault

I suspect that my 2nd dimm banks memory controller has
finally shit the bed in my laptop, but post cause
maybe it is related. I'm not certain what a double
fault is exactly; not off a tennis court anyway...

I will see if I can find the reason for the double
faults by removing the likely unreadable memory stick
and attempt to update the source and ports trees and
see if that helps, but not before dumping my system to
tape. 

any help would be appreciated.

-brian


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

Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6

On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard wrote:
> Hello,
> 
> I'm having trouble building tcl84. These issues did
> not seem to exist until I updated the ports tree and
> world the other day
> 
> Heres the basic stuff:
> 
> FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 
> is what uname -a spits out ports were updated right
> before the system source update. 
> 
> make.conf has
> 

> CXXFLAGS+=-O3 -fno-strict-aliasing

Don't do that, it can cause problems

> MAKEOPTS="-j5"

Don't do that, it can cause problems

kris

pgpYJ9lxjmgGW.pgp
Description: PGP signature

Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6

--- Kris Kennaway <[EMAIL PROTECTED]> wrote:

> On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard
> wrote:
> > Hello,
> > 
> > I'm having trouble building tcl84. These issues
> did
> > not seem to exist until I updated the ports tree
> and
> > world the other day
> > 
> > Heres the basic stuff:
> > 
> > FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 
> > is what uname -a spits out ports were updated
> right
> > before the system source update. 
> > 
> > make.conf has
> > 
> 
> > CXXFLAGS+=-O3 -fno-strict-aliasing
> 
> Don't do that, it can cause problems

can you be a little more specific? I was just using 
CXXFLAGS+=-O3 
before I thought the aliasing issues because of type
casting could cause issues and so -fno-strict-aliasing
was what you had to do to make optimization above
level 1 work rigt. At least thats what reading about
-fno-strict-aliasing seemed to get at with FreeBSD
specifically. 

should it be
CXXFLAGS+=
dafaulting to O2 with no strict aliasing? given my 
CFLAGS=-pipe -O2 -fno-strict-aliasing

> 
> > MAKEOPTS="-j5"
> 
> Don't do that, it can cause problems

I know doing 
make -j5 buildworld or buildkernel or just about
anything else would/used to puke things. But I haven't
seen any issues with MAKEOPTS doing that. Perhaps
until now? I know specifically make -j5 on the shell
would cause the build to skip the build and fail on
the install or skip the build of the objects and fail
on linking the uncompiled library.

> 
> kris

dazed confused and ignorant...

-brian

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

next episode, continuing saga

2006-09-21 Thread jekillen


Hello again;
With FreeBSD and in general, If the monitor is turned off
is it safe to disconnect it from the machine while the machine
is running?
AMD64 socket 754 with separate PCI video card on ECS
motherboard; no Xwindows installed. if it makes a difference.

want to run the machine headless without shutting it down to
switch the monitor to another machine.

Thanks to the gracious responses on previous queries
I don't have to buy another KVM switch.
Jeff K

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

Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6

On Thu, Sep 21, 2006 at 06:29:52PM -0700, backyard wrote:
> 
> 
> --- Kris Kennaway <[EMAIL PROTECTED]> wrote:
> 
> > On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard
> > wrote:
> > > Hello,
> > > 
> > > I'm having trouble building tcl84. These issues
> > did
> > > not seem to exist until I updated the ports tree
> > and
> > > world the other day
> > > 
> > > Heres the basic stuff:
> > > 
> > > FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 
> > > is what uname -a spits out ports were updated
> > right
> > > before the system source update. 
> > > 
> > > make.conf has
> > > 
> > 
> > > CXXFLAGS+=-O3 -fno-strict-aliasing
> > 
> > Don't do that, it can cause problems
> 
> can you be a little more specific? I was just using 
> CXXFLAGS+=-O3 
> before I thought the aliasing issues because of type
> casting could cause issues and so -fno-strict-aliasing
> was what you had to do to make optimization above
> level 1 work rigt. At least thats what reading about
> -fno-strict-aliasing seemed to get at with FreeBSD
> specifically. 
> 
> should it be
> CXXFLAGS+=
> dafaulting to O2 with no strict aliasing? given my 
> CFLAGS=-pipe -O2 -fno-strict-aliasing

Just use the defaults (which is currently the same as your CFLAGS).

> > > MAKEOPTS="-j5"
> > 
> > Don't do that, it can cause problems
> 
> I know doing 
> make -j5 buildworld or buildkernel or just about
> anything else would/used to puke things. But I haven't
> seen any issues with MAKEOPTS doing that. Perhaps
> until now? I know specifically make -j5 on the shell
> would cause the build to skip the build and fail on
> the install or skip the build of the objects and fail
> on linking the uncompiled library.

The base system is fine, but many ports of third party software fail
to build (or the build misbehaves) with make -j.

Kris


pgpZjkWgO0Qov.pgp
Description: PGP signature

Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6