Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db

[Aryeh M. Friedman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ian Smith wrote:
> On Sun, 6 Jan 2008, Aryeh M. Friedman wrote:
>
> If you don't have cvsup installed, run this command: #
> pkg_add -r cvsup-without-gui

 It is better to use all ports or all packages so either do:
>>>
>>> Why do you say that?  Do you know of unresolved issues
>>> regarding the interactions of port versus package
>>> installations?  Any references?
>>
>> I am not currently aware of any conflicts but the fact that they
>> have historical been more frequent then inter-port or
>> inter-package conflicts leads to the conculsion... unlike either
>> of the above they are harder to troubleshoot
>
> The only problems I've ever seen with installing packages is that
> at times the package-building farm gets a bit behind, when you
> might need to build a desired newly updated port from source, and
> that in some cases a package built with default options may not be
> what you want. php5 is one example of the latter, as the default
> options do not include mod_php5 which (I gather?) is why most
> people install php at all.

The main issue is assuming that certain things are installed because
that is the way the developers recommend it then you install a package
and find out that the maintainer had different ideas.   A very good
current example is boost vs. boost-python in regards to the
requirements for deluge and miro respectivally.   An other example is
the entire Java tree.
>
> And yes there are some ports that don't have packages for licencing
> etc reasons, though I can't recall ever having to install one of
> those.

I am the author (but not the maintainer) of such a port
(devel/thistest) and there is often very legit reasons for not
allowing packages... for example my license requires explicit
agreement before you can download the source and/or binaries (because
it has specific provisions regarding execution vs. source usage [see
my blog for more details...
http://www.flosoft-systems.com/flosoft_systems_community/blogs/aryeh/index.php]).
>
> Not everyone has fast hardware and good bandwidth, so installing
> from packages for really big ports - such as X, KDE or Gnome,
> j{dk,re}, OO and such - is almost mandatory on smaller systems.
> Release CDs install at least the former three as packages of
> course, for obvious reasons, and at least around release times, up
> to date packages can be expected.

My experience has been every time I have attempted to make the two
play together well it blows up.  It has been so long since I have used
a package vs. a port I can't site a specific example.
>
> I just think saying "it's better to use all ports or all packages"
> is poor and maybe misleading advice, particularly expressed without
> 'IMHO', as it implies problems that RE should know about -
> especially right now!

This is more of a long term issue that is being worked on by several
groups including the "ports 2.0" team that I am member of [see long
set threads in -ports@ regarding ports system re-engineering]... much
of the stuff I hint at in this thread is better spelled out there.
>
 cd /usr/ports/net/cvsup-without-gui make install clean

 or after doing the above do a pkg_delete -a (assuming that
 your working with a clean machine [no ports/packages
 instaleld except cvsup]
>>>
>>> Why wouldn't pkg_delete -a remove your just-installed
>>> cvsup-without-gui?
>>
>> Sorry for not being clear I meant before the reinstall (besides
>> make install would fail if you hadn't done a pkg_delete -a)
>
> Hmm ok - thought you might be suggesting that port installs don't
> update the package database in /var/db/pkg just the same as pkg_add
> does.
>
> For more info on the supfile, look at this file on your
> FreeBSD machine: /usr/share/examples/cvsup/ports-supfile
>
> Preferring cvsup to portsnap is kinda like preferring vim
> over emacs...  It's a holy war and the vi/cvsup side uses
> less disk space.

 Actually it is not like that at all.. cvsup/csup is the
 officially preferred method and any other method is a short
 cut of some kind...
>>>
>>> Please provide a reference URL to 'official' support of this
>>> claim?
>>
>> This is a case of actions by the developer community speaks
>> louder then words:
>>
>> 1. Csup is in the base system thus obvious preferred to either
>> cvsup or portsnap
>
> % which portsnap /usr/sbin/portsnap
>
>> 2. C(v)sup is more universal 3. The only way to maintain an
>> official local repo is via cvsup
>
> You're talking about updating sources, ports and CVS too.  We were
> just talking about maintaining the ports tree.  I sense nothing
> 'official'.

To me the "official" method should be the most general... and except
for my mistake that portsnap is not in the base system it is no where
near as general as c[v]sup namely portsnap is a kludge designed
for people who are to lazy to learn cvsup
>
 many of them have very subtle issues that the typical
 

Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db

[Ian Smith]

On Sun, 6 Jan 2008, Aryeh M. Friedman wrote:

 > >  > > If you don't have cvsup installed, run this command: # pkg_add -r
 > >  > > cvsup-without-gui
 > >  >
 > >  > It is better to use all ports or all packages so either do:
 > >
 > > Why do you say that?  Do you know of unresolved issues regarding the
 > > interactions of port versus package installations?  Any references?
 > 
 > I am not currently aware of any conflicts but the fact that they have
 > historical been more frequent then inter-port or inter-package
 > conflicts leads to the conculsion... unlike either of the above they
 > are harder to troubleshoot

The only problems I've ever seen with installing packages is that at
times the package-building farm gets a bit behind, when you might need
to build a desired newly updated port from source, and that in some
cases a package built with default options may not be what you want. 
php5 is one example of the latter, as the default options do not include
mod_php5 which (I gather?) is why most people install php at all. 

And yes there are some ports that don't have packages for licencing etc
reasons, though I can't recall ever having to install one of those.

Not everyone has fast hardware and good bandwidth, so installing from
packages for really big ports - such as X, KDE or Gnome, j{dk,re}, OO
and such - is almost mandatory on smaller systems.  Release CDs install
at least the former three as packages of course, for obvious reasons,
and at least around release times, up to date packages can be expected.

I just think saying "it's better to use all ports or all packages" is
poor and maybe misleading advice, particularly expressed without 'IMHO',
as it implies problems that RE should know about - especially right now!

 > >  > cd /usr/ports/net/cvsup-without-gui
 > >  > make install clean
 > >  >
 > >  > or after doing the above do a pkg_delete -a (assuming that your
 > >  > working with a clean machine [no ports/packages instaleld except cvsup]
 > >
 > > Why wouldn't pkg_delete -a remove your just-installed cvsup-without-gui?
 > 
 > Sorry for not being clear I meant before the reinstall (besides make
 > install would fail if you hadn't done a pkg_delete -a)

Hmm ok - thought you might be suggesting that port installs don't update
the package database in /var/db/pkg just the same as pkg_add does.

 > >  > > For more info on the supfile, look at this file on your FreeBSD
 > >  > > machine: /usr/share/examples/cvsup/ports-supfile
 > >  > >
 > >  > > Preferring cvsup to portsnap is kinda like preferring vim over
 > >  > > emacs...  It's a holy war and the vi/cvsup side uses less disk
 > >  > > space.
 > >  >
 > >  > Actually it is not like that at all.. cvsup/csup is the officially
 > >  > preferred method and any other method is a short cut of some kind...
 > >
 > > Please provide a reference URL to 'official' support of this claim?
 > 
 > This is a case of actions by the developer community speaks louder
 > then words:
 > 
 > 1. Csup is in the base system thus obvious preferred to either cvsup
 > or portsnap

% which portsnap
/usr/sbin/portsnap

 > 2. C(v)sup is more universal
 > 3. The only way to maintain an official local repo is via cvsup

You're talking about updating sources, ports and CVS too.  We were just
talking about maintaining the ports tree.  I sense nothing 'official'. 

 > >  > many of them have very subtle issues that the typical end-user should
 > >  > not notice but should be aware of...
 > >
 > > Issues such as?  And what other alternatives to c*sup and portsnap exist
 > > for ports tree management?
 > 
 > I can think of several off the top my head:
 > 
 > 1. Ftp ports.tar.gz and unpack

Sure.  Plus make fetchindex or such.

 > 2. Maintain a local repo like I do

Clearly not a job for portsnap :)

 > 3. Use portupgrade in conjunction with the above
 > 
 > I was specifically refeering to the 3rd option when I said there where
 > subtle issues.   Speicfically the way "make install" (recursive) and
 > "portupgrade -a" calculate the build order can lead to some issues
 > (like compiling the default OPTIONS before asking the user to select
 > OPTIONS)

It seems that here you're confusing port maintenance and upgrading
tools (portupgrade, portmaster etc and/or make install) with a choice
between c*sup and portsnap for maintaining the ports _tree_ and INDEX,
which is precisely all that portsnap is designed to do, and does well.

Sorry if I sound a bit harsh, but there seems to have been a flurry of
deprecation approaching folklore re installing from packages recently,
and I can't see that it's based on anything much factual.  My last big
portupgrade on this 300MHz 5.5-STABLE system began with 'portupgrade
-anPP' which fetched the vast bulk of a hundred or so ports as packages,
saving me many hours - if not days - of building.  YM probably V.

cheers, Ian

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/f

Re: port collection RELEASE6.2 lost after reinstall with CVSUP

['Frank Shute']

On Mon, Jan 07, 2008 at 12:34:50AM +0100, Walter Jansen wrote:
>
> Thanks for your effort Fank, but unfortunately the Handbook shows that your
> answer does not reflect the actual use of tags for fetching ports with
> cvsup. Your answer triggers me to look for other places where information
> can be found in order to reduce the confusion, and that is what I am
> grateful for.

Walter, show me in the handbook where my answer doesn't reflect the
reality of using tags for fetching ports. Thanks.

Read this (I know it's old):

http://www.freebsddiary.org/ports.php

//

NOTE: Don't worry about releases/version when cvsup'ing your
ports.  There is only one version of the Ports collection.  All
versions of FreeBSD use the same ports collection.  Therefore,
when updating your ports use this tag:

tag=.
//


You can use that tag for your src supfile too but you will get 8.0
which you don't want to do unless you are a developer.

> 
> 
> Have a good day!
> Walter
> 

You too.

-- 

 Frank 


 Contact info: http://www.esperance-linux.co.uk/misc/contact.html 

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

Re: port collection RELEASE6.2 lost after reinstall with CVSUP

[Frank Shute]

On Sun, Jan 06, 2008 at 09:24:15PM +0100, Erik Trulsson wrote:
>
> On Sun, Jan 06, 2008 at 08:05:17PM +, Frank Shute wrote:
> > On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote:
> > >
> > > Hi
> > > 
> > > Upon reading chapters of the Handbook about the Ports collection
> > > and CVSup, I wanted to CVSup the ports collection for the
> > > RELEASE  6.2. Stupidly using the wrong tag (tag=.), I
> > > erroneously but successfully installed the CURRENT version. I
> > > could have used SYSINSTALL for the RELEASE 6.2 ports, but for
> > > the sake of learning and training myself I did not. 
> > 
> > You used the right tag. There is only a current tag as you only have a
> > current ports tree to be used for all releases ie 6.2,6.3 & 7.0 (The
> > ports might work with older releases too).
> 
> Wrong.  The ports tree is not branched, but it is tagged and it does have
> tags corresponding to each FreeBSD release.

So if it's not branched but tagged, what's the difference between the
ports tree I get if I use RELENG_4_8  compared to RELENG_7_0 as tags
in my ports supfile?

> 
> 
> 
> > 
> > > 
> > >  
> > > 
> > > Problem: 
> > > 
> > >   - I ran CVSup again with the correct tag but though everything
> > >   in the process looked normal, the map usr/ports remains empty
> > >   and nor with whereis nor with pkg_xxx any information about
> > >   ports can be found.  
> > 
> > You ran cvsup again with the wrong tag.
> > 
> > > 
> > > Questions: 
> > > 
> > >   - What did I do wrong in the process?.  
> > 
> > Used the wrong tag second time around.
> > 
> > > 
> > >   - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea
> > > anyway (technically) ?  
> > 
> > No. Although there is no 6.2 ports collection, just CURRENT.
> 
> Of course there is a 6.2 ports collection.  What else would you call the
> ports tree shipped with FreeBSD 6.2?

A snapshot of the ports tree when the release was made.

> 
> 
> > 
> > > 
> > >  
> > > 
> > > Proces:
> > > 
> > > - I use the recently installed cvsup-without-gui, installed from ports 
> > 
> > Use csup(1) it's identical to cvsup but no dependencies as it's in
> > base & written in C.
> 
> Not quite identical.  There are a couple of features that cvsup(1) has, but
> which csup(1) does not yet have.
> To just check out a copy of the ports tree either should work fine though.

Features that a newbie wouldn't use. It's also difficult to build
cvsup when you don't necessarily have a ports tree.

Regards,

-- 

 Frank 


 Contact info: http://www.esperance-linux.co.uk/misc/contact.html 

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

Re: wpi error: bus_dmamem_alloc failed to align memory properly

[Benjamin Close]

vittorio wrote:

Context: HP laptop DV6000, centrino duo, FreeBSD 7.0-BETA4
When loading if_wpi I get the following line saying that "bus_dmamem_alloc 
failed to align memory properly"


wpi0:  mem 0xd800-0xd8000fff irq 16 at 
device 0.0 on pci2

bus_dmamem_alloc failed to align memory properly.
last message repeated 30 times
wpi0: Ethernet address: 00:19:d2:99:e3:cb
wpi0: [ITHREAD]
wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 
36Mbps 48Mbps 54



Therefore I'm unable to make wpi0 work at all.

Could you please tell me what should I do?

Ciao, Vittorio

  
The bus_dmamem_alloc message is harmless in your case. Due to 
limitations in the freebsd allocator, sometimes requesting a 16k aligned 
block of dma memory fails. As a temporary work around the wpi driver 
reattempts the allocation. If it truely does fail you'll not get a wpi0 
device showing up, which clearly you did :).


These warning messages will go away when I sync the next lot of updates 
to the driver which aren't quite ready yet.


Can you describe a little more what you mean by wpi doesn't work?

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

Re: unpack win32 exe file

[Lars Kristiansen]

Chris Whitehouse skrev:

Rob wrote:

Chris Whitehouse wrote:
I have a Windows executable file (.exe) which in a Windows 
environment would be run to extract some files which it contains. Is 
there any  way I can extract the files on my FreeBSD system? I've 
tried unzip, gunzip and archivers/upx with various extensions, zip, 
exe, gz etc but they all 


There are many types of self-extracting archive files under windows.  
If it's one that's based on PKZip, then there's a good chance you 
could get it with 7-Zip:  http://www.7-zip.org/  Otherwise, you need a 
windoze system or emulator I suspect.


  -Rob


Someone else suggested 7-zip as well but still no joy. I don't think 
it's worth installing Wine just for this so it's time to find a windows box


Was the result with 7zip negative?
http://www.freshports.org/archivers/p7zip/

Lars


thanks for replies

Chris
___
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: unpack win32 exe file

[Chris Whitehouse]

Rob wrote:

Chris Whitehouse wrote:
I have a Windows executable file (.exe) which in a Windows environment 
would be run to extract some files which it contains. Is there any  
way I can extract the files on my FreeBSD system? I've tried unzip, 
gunzip and archivers/upx with various extensions, zip, exe, gz etc but 
they all 


There are many types of self-extracting archive files under windows.  If 
it's one that's based on PKZip, then there's a good chance you could get 
it with 7-Zip:  http://www.7-zip.org/  Otherwise, you need a windoze 
system or emulator I suspect.


  -Rob


Someone else suggested 7-zip as well but still no joy. I don't think 
it's worth installing Wine just for this so it's time to find a windows box


thanks for replies

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

Re: Given the state of ZFS...

[Kris Kennaway]

Robert Atkinson wrote:

To get a quick answer, is there a way to remotely (besides serial console &
cd which I do not have), get an i386 (7.0) system to amd64?


Either reinstall, install the amd64 world+kernel onto another disk and 
boot that, or unmount your swap partition, newfs it and install there, 
then boot the kernel from that partition and copy back over onto the 
i386 partition.


Kris

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

Given the state of ZFS...

[Robert Atkinson]

To get a quick answer, is there a way to remotely (besides serial console &
cd which I do not have), get an i386 (7.0) system to amd64?

My Google searches were not fruitful.


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

Re: module loads from kldload, but gives "Unsupported file type" from loader.conf

[Joshua Isom]

On Jan 5, 2008, at 8:01 PM, Steve Franks wrote:


I successfully built snd_hda on my 6.3amd64 system, so I placed it in
loader.conf (snd_hda_load="YES"), when I boot, dmesg shows:

kldload: Unsupported file type

If I sudo kldload snd_hda, dmesg shows:

kldload: Unsupported file type
kldload: Unsupported file type
pcm0:  mem
0xfdff8000-0xfdffbfff irq 16 at device 27.0 on pci0
pcm0: 
pcm0: 

Note: on startup, there is one unsupported, after kldload, there is
two, but the module loads sucessfully!

Anyone heard of this ?!?

Steve


The same thing happens to me with green_saver.  It loads, it works, but 
something's unsupported.  I've never got an answer why it's reported as 
unsupported.



___
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] cvsup for ports -- Re: compact portsnap db

[Manolis Kiagias]

Gerard wrote:

On Sun, 06 Jan 2008 15:41:35 -0500
"Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote:

[snip]

  

1. Csup is in the base system thus obvious preferred to either cvsup
or portsnap



Correct me if I am wrong; however, I thought that 'portsnap' was part
of the base system.

  

Yes, portsnap is part of the base system, as is csup.
csup and cvsup are equivalent unless you need to create a local 
repository (i.e. getting the RCS ,v files)  which is not required for 
anyone simply wishing to use the ports tree  for building apps. This 
feature is only available in cvsup.

As for the OP, the tag to get the ports for FreeBSD 6.2-RELEASE would be:

RELEASE_6_2_0

This is mentioned in the handbook,

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html

(the paragraph text in A.7.2)

but may be it is not clear enough, since all the examples that follow 
refer to the src tree tags (which start with RELENG)

___
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] cvsup for ports -- Re: compact portsnap db

[Gerard]

On Sun, 06 Jan 2008 15:41:35 -0500
"Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote:

[snip]

> 1. Csup is in the base system thus obvious preferred to either cvsup
> or portsnap

Correct me if I am wrong; however, I thought that 'portsnap' was part
of the base system.

-- 

Gerard
[EMAIL PROTECTED]

I cannot conceive that anybody will require multiplications at the rate
of 40,000 or even 4,000 per hour ...

F. H. Wales (1936)



signature.asc
Description: PGP signature

Re: [HOW-TO] cvsup for ports -- Re: compact portsnap db

[Aryeh M. Friedman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


>
>
>  > > If you don't have cvsup installed, run this command: # pkg_add -r
>  > > cvsup-without-gui
>  >
>  > It is better to use all ports or all packages so either do:
>
> Why do you say that?  Do you know of unresolved issues regarding the
> interactions of port versus package installations?  Any references?

I am not currently aware of any conflicts but the fact that they have
historical been more frequent then inter-port or inter-package
conflicts leads to the conculsion... unlike either of the above they
are harder to troubleshoot
>
>  > cd /usr/ports/net/cvsup-without-gui
>  > make install clean
>  >
>  > or after doing the above do a pkg_delete -a (assuming that your
>  > working with a clean machine [no ports/packages instaleld except cvsup]
>
> Why wouldn't pkg_delete -a remove your just-installed cvsup-without-gui?

Sorry for not being clear I meant before the reinstall (besides make
install would fail if you hadn't done a pkg_delete -a)
>
>  > > For more info on the supfile, look at this file on your FreeBSD
>  > > machine: /usr/share/examples/cvsup/ports-supfile
>  > >
>  > > Preferring cvsup to portsnap is kinda like preferring vim over
>  > > emacs...  It's a holy war and the vi/cvsup side uses less disk
>  > > space.
>  >
>  > Actually it is not like that at all.. cvsup/csup is the officially
>  > preferred method and any other method is a short cut of some kind...
>
> Please provide a reference URL to 'official' support of this claim?

This is a case of actions by the developer community speaks louder
then words:

1. Csup is in the base system thus obvious preferred to either cvsup
or portsnap
2. C(v)sup is more universal
3. The only way to maintain an official local repo is via cvsup
>
>  > many of them have very subtle issues that the typical end-user should
>  > not notice but should be aware of...
>
> Issues such as?  And what other alternatives to c*sup and portsnap exist
> for ports tree management?

I can think of several off the top my head:

1. Ftp ports.tar.gz and unpack
2. Maintain a local repo like I do
3. Use portupgrade in conjunction with the above

I was specifically refeering to the 3rd option when I said there where
subtle issues.   Speicfically the way "make install" (recursive) and
"portupgrade -a" calculate the build order can lead to some issues
(like compiling the default OPTIONS before asking the user to select
OPTIONS)
>
> ooroo, Ian
>
>


- --
Aryeh M. Friedman
FloSoft Systems, Java Developer Tools
http://www.flosoft-systems.com
Developer, not business, friendly.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHgTz+jRvRjGmHRgQRAgj8AKCbgfQfoquUWiceLSGxOBQmNDLGxQCeJLGY
p2zteaiWHCoJ95O64urXoZs=
=P5jK
-END PGP SIGNATURE-

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

Re: port collection RELEASE6.2 lost after reinstall with CVSUP

[Erik Trulsson]

On Sun, Jan 06, 2008 at 08:05:17PM +, Frank Shute wrote:
> On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote:
> >
> > Hi
> > 
> > Upon reading chapters of the Handbook about the Ports collection and CVSup,
> > I wanted to CVSup the ports collection for the RELEASE  6.2. Stupidly using
> > the wrong tag (tag=.), I erroneously but successfully installed the CURRENT
> > version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the
> > sake of learning and training myself I did not.
> 
> You used the right tag. There is only a current tag as you only have a
> current ports tree to be used for all releases ie 6.2,6.3 & 7.0 (The
> ports might work with older releases too).

Wrong.  The ports tree is not branched, but it is tagged and it does have
tags corresponding to each FreeBSD release.



> 
> > 
> >  
> > 
> > Problem: 
> > 
> >   - I ran CVSup again with the correct tag but though everything in the
> > process looked normal, the map usr/ports remains empty and nor with whereis
> > nor with pkg_xxx any information about ports can be found. 
> 
> You ran cvsup again with the wrong tag.
> 
> > 
> > Questions: 
> > 
> >   - What did I do wrong in the process?.  
> 
> Used the wrong tag second time around.
> 
> > 
> >   - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea
> > anyway (technically) ?  
> 
> No. Although there is no 6.2 ports collection, just CURRENT.

Of course there is a 6.2 ports collection.  What else would you call the
ports tree shipped with FreeBSD 6.2?


> 
> > 
> >  
> > 
> > Proces:
> > 
> > - I use the recently installed cvsup-without-gui, installed from ports 
> 
> Use csup(1) it's identical to cvsup but no dependencies as it's in
> base & written in C.

Not quite identical.  There are a couple of features that cvsup(1) has, but
which csup(1) does not yet have.
To just check out a copy of the ports tree either should work fine though.



-- 

Erik Trulsson
[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: multiple postgresql servers in multiple jails?

[Marc G. Fournier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Talk about 'old email', but better then 'use different ports', which means you 
have to modify your clients for this ... after you install postgresql within 
the jail, vipw the password file and change the uid of the pgsql user (and 
chown the appropriate files) ... then you can run all instances on port 5432, 
which clients will expect, but without overrunning shared memory ...


- --On Tuesday, October 23, 2007 20:07:19 +0200 Oliver Peter <[EMAIL 
PROTECTED]> 
wrote:

> Does anybody have a running system with more than one jail hosting
> more than one postgres server?
>
> I can only have one pgsql database on one host at all.  I already
> tried to increase the shared memory off my machine with additional
> kernel [1] and sysctl parameters [2] and I also tried to change
> the numeric UID directly in the jails into a seperate one.  Same
> errors.
>
> Of course I already have defined  jail_sysvipc_allow="YES"  in
> rc.conf.  I have this issue on 6.2-RELEASE-p8 and 8.0-CURRENT with
> postgresql-server-8.2.5_1.
>
> 
> % psql
> psql: FATAL:  semctl(458753, 15, SETVAL, 0) failed: Invalid argument
> 
>
> Or some fun with perl/DBD
> 
> Out of memory during request for 108 bytes, total sbrk() is 534585344 bytes!
> Out of memory during request for 288 bytes, total sbrk() is 534585344 bytes!
> Out of memory during request for 288 bytes, total sbrk() is 534585344 bytes!
> 
>
> [1]
> options SYSVSHM
> options SYSVSEM
> options SYSVMSG
> options SHMMAXPGS=65536
> options SEMMNI=40
> options SEMMNS=240
> options SEMUME=40
> options SEMMNU=120
>
> [2] http://www.freebsddiary.org/jail-multiple.php
>
> --
> Oliver PETER, eMail: [EMAIL PROTECTED], ICQ# 113969174
> "Worker bees can leave.  Even drones can fly away.
>  The Queen is their slave."



- 
Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHgTgi4QvfyHIvDvMRArJ8AJ983aj4+QqbEbs/cFM6UIrby1DUJwCgwZfz
rg+dUi5ExXey99rpL/NLb/I=
=Z3xL
-END PGP SIGNATURE-

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

Re: port collection RELEASE6.2 lost after reinstall with CVSUP

[Frank Shute]

On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote:
>
> Hi
> 
> Upon reading chapters of the Handbook about the Ports collection and CVSup,
> I wanted to CVSup the ports collection for the RELEASE  6.2. Stupidly using
> the wrong tag (tag=.), I erroneously but successfully installed the CURRENT
> version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the
> sake of learning and training myself I did not.

You used the right tag. There is only a current tag as you only have a
current ports tree to be used for all releases ie 6.2,6.3 & 7.0 (The
ports might work with older releases too).

> 
>  
> 
> Problem: 
> 
>   - I ran CVSup again with the correct tag but though everything in the
> process looked normal, the map usr/ports remains empty and nor with whereis
> nor with pkg_xxx any information about ports can be found. 

You ran cvsup again with the wrong tag.

> 
> Questions: 
> 
>   - What did I do wrong in the process?.  

Used the wrong tag second time around.

> 
>   - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea
> anyway (technically) ?  

No. Although there is no 6.2 ports collection, just CURRENT.

> 
>  
> 
> Proces:
> 
> - I use the recently installed cvsup-without-gui, installed from ports 

Use csup(1) it's identical to cvsup but no dependencies as it's in
base & written in C.

> 
> - I deleted all entries and maps in/under /usr/ports (as recommended in the
> Handbook) 

All you need is the empty dir /usr/ports and c(v)sup will fill it.

> 
>  
> 
> - I modified the ports-supfile in usr/share/examples/cvsup and copied it to
> portswj-supfile  in the same map (not good practice I know now)
> 
> The settings in the -supfile where:
> 
>   *default host=cvsup15.FreeBSD.org  
> 
>   *default base=/var/db
> 
>   *default prefix=/usr
> 
>   *default release=cvs tag=RELENG_6_2_0_RELEASE   (the handbook suggests
> that this is a valid tag for ports)
> 
>   *default delete use-rel-suffix   (I could not find a meaning for this in
> the books, anyone can tell me please?)
> 
>   *default compress
> 
>   ports-all

Try this as your ports-supfile:

*default host=cvsup15.FreeBSD.org
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
*default compress
ports-all

and run: csup -L 2 /usr/share/examples/cvsup/ports-supfile

and it should download the current ports tree.

For the src supfile you should use the tag:

*default release=cvs tag=RELENG_6_3

as 6.3 is pretty close to release and you'll get 6.3RC2 probably.

or if you want 7.0RC2(?)

*default release=cvs tag=RELENG_7_0

For the src-supfile you only need to set that tag and the default host
and it should work.

Regards,

-- 

 Frank 


 Contact info: http://www.esperance-linux.co.uk/misc/contact.html 

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

wpi error: bus_dmamem_alloc failed to align memory properly

[vittorio]

Context: HP laptop DV6000, centrino duo, FreeBSD 7.0-BETA4
When loading if_wpi I get the following line saying that "bus_dmamem_alloc 
failed to align memory properly"

wpi0:  mem 0xd800-0xd8000fff irq 16 at 
device 0.0 on pci2
bus_dmamem_alloc failed to align memory properly.
last message repeated 30 times
wpi0: Ethernet address: 00:19:d2:99:e3:cb
wpi0: [ITHREAD]
wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 
36Mbps 48Mbps 54


Therefore I'm unable to make wpi0 work at all.

Could you please tell me what should I do?

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

Re: port collection RELEASE6.2 lost after reinstall with CVSUP

[Predrag Punosevac]

Erik Trulsson wrote:

On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote:
  

Hi

 


Upon reading chapters of the Handbook about the Ports collection and CVSup,
I wanted to CVSup the ports collection for the RELEASE  6.2. Stupidly using
the wrong tag (tag=.), I erroneously but successfully installed the CURRENT
version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the
sake of learning and training myself I did not.

 

Problem: 


  - I ran CVSup again with the correct tag but though everything in the
process looked normal, the map usr/ports remains empty and nor with whereis
nor with pkg_xxx any information about ports can be found. 

Questions: 

  - What did I do wrong in the process?.  




You used the wrong tag.

If you want the exact version of the ports tree that shipped with 6.2 the
correct tag to use is "RELEASE_6_2_0".  "RELENG_6_2_0_RELEASE" is the tag
used for the base system corresponding to 6.2-RELEASE.


  

  - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea
anyway (technically) ?  



If you actually want the ports tree as it was when 6.2-RELEASE was made,
then it is not a bad idea.  Most of the time one would like a more updated
version of the ports tree though.



  
 


Proces:

- I use the recently installed cvsup-without-gui, installed from ports 


- I deleted all entries and maps in/under /usr/ports (as recommended in the
Handbook) 

 


- I modified the ports-supfile in usr/share/examples/cvsup and copied it to
portswj-supfile  in the same map (not good practice I know now)

The settings in the -supfile where:

  *default host=cvsup15.FreeBSD.org  


  *default base=/var/db

  *default prefix=/usr

  *default release=cvs tag=RELENG_6_2_0_RELEASE   (the handbook suggests
that this is a valid tag for ports)



I doubt the handbook suggests that.  If it does it is wrong.

  

  *default delete use-rel-suffix   (I could not find a meaning for this in
the books, anyone can tell me please?)



Read the cvsup(1) manpage.

  

  *default compress

  ports-all

 


- I ran:  cvsup -L 2 /usr/share/examples/cvsup/portswj-supfile

The conversation looked OK, no error messages but also no scrolling list of
files

There is a logfile in  /var/db/sup ports-all, something like
.cvs:RELENG_6_2_0_RELEASE. It shows a list of all the elements of the
ports collection that looks normal and every record shows also
RELENG_6_2_0_RELEASE.

 




  



One idiotic question on the top of his troubles.

According to the disclaimer posted on the ports web-site. The ports tree 
supports only Stable and Current version of the OS.


Since Release is sort of more stable than the Stable I wonder if there 
is a frozen ports three with frozen packages for 6.2 release?


Personally, I was always following stable branch which is moving target 
as you know. One needs to portsnap fetch and update ports three

before every build up and also portupgrade has to be done fairly regularly.
Personally, I could not care less for the newest versions of the 
programs as long as the old one are stable so for me staying with 
release would be perfectly OK.




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

Two minute pause at acpi.ko message on old HP laptop with 7.0-RC1

[Xn Nooby]

I have an old zv5445us HP Pavillion laptop, essentially the zv5000
model, which pauses at the /boot/kernel/acpi.ko message during boot.
It hangs there, with a non-spinning ASCII character, for about 2
minutes - then it boots.  I tried entering the following commands in
to the loader.conf to no avail:

   set hint.atkbd.0.disabled="1"
   set hint.acpi.0.disabled="1"

I'm currently using FreeBSD 7.0-RC1, but it has the same behavior with
FreeBSD 6.3-RC2.

The machine seems to work okay after that, though I am having other
problems with the screen going blank when I try to configure X.  For
now, I was just trying to eliminate the 2 minute pause on acpi.ko.

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

Re: ipsec with dynamic ip clients

[Eric Masson]

Norman Maurer <[EMAIL PROTECTED]> writes:

Hi,

> Now I want to setup some config which allow some people to connection
> via ipsec client to this ipsec router. They have a dynamic ip so I think
> a certificate is the way to go. But im not sure how i need to setup the
> gif interface because the ip address will change probally.
>
> So any idea ? I couldn't find any docu :-/

http://shrew.net/?page=software

Take a look at vpn gateway configuration in the doc.

-- 
 GA> Je propose donc pour le vote :le déplacement de tous les groupes
 GA> avec renommage de fcol.moderated en fcol.modere
 Mes nommages madame.
 -+- FB in :  - Troll poli pour être honnête -+-
___
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] cvsup for ports -- Re: compact portsnap db

[Ian Smith]

On Sat, 05 Jan 2008 22:31:29 "Aryeh M. Friedman" <[EMAIL PROTECTED]> wrote:
 > Rudy wrote:
 > > Michael Lednev wrote:
 > >> Hello.
 > >>
 > >> Is there any way to compact /var/db/portsnap other than deleting
 > >> it and doing postsnap fetch?

Not really.  /var/db/portsnap/files contains one file for each port,
gzipped.  Mine's about 70MB with indices, containing a ports tree of
some 450MB.

I guess it depends whether that much space is more precious to you than
the time and bandwidth to fetch and then extract the whole tree afresh?

 > > I don't like portsnap -- granted I've never typed the portsnap
 > > command in my 10 years of FreeBSD use.  I use cvsup!

I didn't like it much until I'd tried it, either :)

c[v]sup works fine too of course, so trimming some discussion of that .. 

[..]

 > > If you don't have cvsup installed, run this command: # pkg_add -r
 > > cvsup-without-gui
 > 
 > It is better to use all ports or all packages so either do:

Why do you say that?  Do you know of unresolved issues regarding the
interactions of port versus package installations?  Any references?

 > cd /usr/ports/net/cvsup-without-gui
 > make install clean
 > 
 > or after doing the above do a pkg_delete -a (assuming that your
 > working with a clean machine [no ports/packages instaleld except cvsup]

Why wouldn't pkg_delete -a remove your just-installed cvsup-without-gui? 

 > > For more info on the supfile, look at this file on your FreeBSD
 > > machine: /usr/share/examples/cvsup/ports-supfile
 > >
 > > Preferring cvsup to portsnap is kinda like preferring vim over
 > > emacs...  It's a holy war and the vi/cvsup side uses less disk
 > > space.
 > 
 > Actually it is not like that at all.. cvsup/csup is the officially
 > preferred method and any other method is a short cut of some kind...

Please provide a reference URL to 'official' support of this claim?

 > many of them have very subtle issues that the typical end-user should
 > not notice but should be aware of...

Issues such as?  And what other alternatives to c*sup and portsnap exist
for ports tree management?

ooroo, Ian

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

Re: unpack win32 exe file

[Rob]

Chris Whitehouse wrote:
I have a Windows executable file (.exe) which in a Windows environment 
would be run to extract some files which it contains. Is there any  way 
I can extract the files on my FreeBSD system? I've tried unzip, gunzip 
and archivers/upx with various extensions, zip, exe, gz etc but they all 


There are many types of self-extracting archive files under windows.  If 
it's one that's based on PKZip, then there's a good chance you could get 
it with 7-Zip:  http://www.7-zip.org/  Otherwise, you need a windoze 
system or emulator I suspect.


  -Rob

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

Re: 7.0-PRERELEASE installworld fails

[Chris]

On Sun, 06 Jan 2008 17:28:08 +0300
Boris Samorodov <[EMAIL PROTECTED]> wrote:

> On Sun, 6 Jan 2008 08:17:24 -0600 Chris wrote:
> 
> > Additionally - mergemasted can be skipped if the Op does not have
> > custom tweaks to files in /etc.
> 
> Yes and no...
> 
> Yes to "mergemaster -p" -- it may be skipped in short jumps. But
> better safe than sorry -- as for me I use it always. It's not too
> hard anyway. ;-)
> 
> No to "mergemaster -i" -- this step is mandatory. One may (though
> rarely but nevertheless may) get an unbootable host without this
> step.

While this may be true - I never use mmaster with incremental upgrades.
I do however with full version jumps - never had a system go bad - of
course, your mileage may vary.


-- 
Best regards,
Chris

C-3PO:
R2 says that the chances of survival are 725 to 1.
Actually R2 has been known to make mistakes - from time
to time... Oh dear...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 7.0-PRERELEASE installworld fails

[Chris]

On Sun, 6 Jan 2008 06:37:29 -0800 (PST)
Unga <[EMAIL PROTECTED]> wrote:

> --- Boris Samorodov <[EMAIL PROTECTED]> wrote:
> 
> > On Sun, 6 Jan 2008 03:38:16 -0800 (PST) Unga wrote:
> > 
> > > --- Boris Samorodov <[EMAIL PROTECTED]> wrote:
> > 
> > > > > > This may be an overkill but should do the
> > job:
> > > > > > # rm -r /usr/src /usr/obj
> > > > > > 
> > > > > > # cd /usr/src
> > > > > > # make buildworld
> > > > > > # make kernel
> > > > > > # mergemaster -p
> > > > > > # make installworld
> > > > > > # mergemaster -i
> > > > 
> > 
> 
> Sure, I'll do it again exactly as above without even
> reboot after make kernel, lets see what happens.

Reboots are needed  - What Boris is stating (and I agree) is frop the
other crap your doing. IE:

"2. After installkernel, I rebooted to single-user mode
with the new kernel, adjkerntz -i, fsck -p, mount -u
/, mount -a, swapon -a, /usr/local/bin/bash and follow
your steps until make installworld."

> 
> As per Chris' reply, I did everything in single-user
> because in my machine I have only 512MB RAM, I use
> KDE, if I compile on multi-user mode it goes into
> swapping and makes the compilation very long.

KDE has nothing to do with this, unless you have /etc/ttys hacked to
start kdm on boot OR you are using root as a common user.

If KDM is not being used, loggin in as root provides a shell - this is
what you ought to be doing. 

I hope you not logging in a a user (into KDE) then doing your upgrade in
a term as root.

-- 
Best regards,
Chris

C-3PO:
R2 says that the chances of survival are 725 to 1.
Actually R2 has been known to make mistakes - from time
to time... Oh dear...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 7.0-PRERELEASE installworld fails

[Unga]

--- Boris Samorodov <[EMAIL PROTECTED]> wrote:

> On Sun, 6 Jan 2008 03:38:16 -0800 (PST) Unga wrote:
> 
> > --- Boris Samorodov <[EMAIL PROTECTED]> wrote:
> 
> > > > > This may be an overkill but should do the
> job:
> > > > > # rm -r /usr/src /usr/obj
> > > > > 
> > > > > # cd /usr/src
> > > > > # make buildworld
> > > > > # make kernel
> > > > > # mergemaster -p
> > > > > # make installworld
> > > > > # mergemaster -i
> > > 
> 

Sure, I'll do it again exactly as above without even
reboot after make kernel, lets see what happens.

As per Chris' reply, I did everything in single-user
because in my machine I have only 512MB RAM, I use
KDE, if I compile on multi-user mode it goes into
swapping and makes the compilation very long.

Best Regards
Unga



  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 7.0-PRERELEASE installworld fails

[Boris Samorodov]

On Sun, 6 Jan 2008 08:17:24 -0600 Chris wrote:

> Additionally - mergemasted can be skipped if the Op does not have
> custom tweaks to files in /etc.

Yes and no...

Yes to "mergemaster -p" -- it may be skipped in short jumps. But
better safe than sorry -- as for me I use it always. It's not too
hard anyway. ;-)

No to "mergemaster -i" -- this step is mandatory. One may (though
rarely but nevertheless may) get an unbootable host without this
step.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 7.0-PRERELEASE installworld fails

[Chris]

On Sun, 06 Jan 2008 16:44:45 +0300
Boris Samorodov <[EMAIL PROTECTED]> wrote:

> On Sun, 6 Jan 2008 03:38:16 -0800 (PST) Unga wrote:
> 
> > --- Boris Samorodov <[EMAIL PROTECTED]> wrote:
> 
> > > > > This may be an overkill but should do the job:
> > > > > # rm -r /usr/src /usr/obj
> > > > > 
> > > > > # cd /usr/src
> > > > > # make buildworld
> > > > > # make kernel
> > > > > # mergemaster -p
> > > > > # make installworld
> > > > > # mergemaster -i
> > > 
> 
> > I did above but its still the same story, installworld
> > fails:
> > --
> > >>> Installing everything
> > --
> > cd /usr/src; make -f Makefile.inc1 install
> > ===> share/info (install)
> > ===> lib (install)
> > ===> lib/csu/i386-elf (install)
> > cc -O2 -fno-strict-aliasing -pipe 
> > -I/usr/src/lib/csu/i386-elf/../common  -I/usr
> > /src/lib/csu/i386-elf/../../libc/include
> > -Wsystem-headers -Wall -Wno-format-y2k
> > -W -Wno-unused-parameter -Wstrict-prototypes
> > -Wmissing-prototypes -Wpointer-arit
> > h -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
> > -Wshadow -Wcast-align -Wunu
> > sed-parameter -Wchar-subscripts -Winline
> > -Wnested-externs -Wredundant-decls -Wno
> > -pointer-sign -c /usr/src/lib/csu/i386-elf/crt1.c
> > /usr/src/lib/csu/i386-elf/crt1.c:33:20: error:
> > stdlib.h: No such file or directory
> 
> 
> > The only difference what I did compared to your steps:
> 
> Please, do just what I suggested and see if it helps.
> 
> > 1. After download sources, rebooted to single-user
> 
> Single-user mode is not necessary here.
> 
> > mode, adjkerntz -i (as my CMOS is set to local time),
> > fsck -p, mount -u /, mount -a, swapon -a,
> 
> This is not needed at all (but seems to be harmless).
> 
> > /usr/local/bin/bash and follow your steps until make
> 
> Ah, don't use bash here (upgrade/build OS). Use standard shells.
> 
> > kernel (in fact, instead make kernel what I did was:
> > kernel-toolchain, buildkernel and installkernel)
> 
> > 2. After installkernel, I rebooted to single-user mode
> > with the new kernel, adjkerntz -i, fsck -p, mount -u
> > /, mount -a, swapon -a,
> 
> Those steps are needed at long jumps and should be harmless
> here.
> 
> > /usr/local/bin/bash and follow
> 
> Don't use bash here.
> 
> > your steps until make installworld.
> 
> > Before execute every step, I checked system time with
> > date, they were all local time.
> 
> There is no need to check it. Just don't touch time while OS
> building/installing.
> 
> > Have I deviated too much than you specified?
> 
> Yep.
> 
> > or is it
> > essentially the same?
> 
> No.
> 
> > Am I supposed to reboot with the
> > new kernel after make kernel?
> 
> Seems to be "yes" only for very long jumps. Actually I never had to
> do it myself.
> 
> > What else I could do to identify the cause?
> 
> ;-) Please, do just what I suggested.
> 
> 
> WBR

Dropping into single user mode is pointless if the device he's
upgrading does not serv more then one user (himself only).

Additionally - mergemasted can be skipped if the Op does not have
custom tweaks to files in /etc.

However, the above statement is untrue if upgrading from  versions, IE:
6 -> 7


-- 
Best regards,
Chris

"Does it worry you that you don't talk any kind of sense? "


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

Re: port collection RELEASE6.2 lost after reinstall with CVSUP

[Erik Trulsson]

On Sun, Jan 06, 2008 at 02:10:59PM +0100, Walter Jansen wrote:
> Hi
> 
>  
> 
> Upon reading chapters of the Handbook about the Ports collection and CVSup,
> I wanted to CVSup the ports collection for the RELEASE  6.2. Stupidly using
> the wrong tag (tag=.), I erroneously but successfully installed the CURRENT
> version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the
> sake of learning and training myself I did not.
> 
>  
> 
> Problem: 
> 
>   - I ran CVSup again with the correct tag but though everything in the
> process looked normal, the map usr/ports remains empty and nor with whereis
> nor with pkg_xxx any information about ports can be found. 
> 
> Questions: 
> 
>   - What did I do wrong in the process?.  


You used the wrong tag.

If you want the exact version of the ports tree that shipped with 6.2 the
correct tag to use is "RELEASE_6_2_0".  "RELENG_6_2_0_RELEASE" is the tag
used for the base system corresponding to 6.2-RELEASE.


> 
>   - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea
> anyway (technically) ?  

If you actually want the ports tree as it was when 6.2-RELEASE was made,
then it is not a bad idea.  Most of the time one would like a more updated
version of the ports tree though.



> 
>  
> 
> Proces:
> 
> - I use the recently installed cvsup-without-gui, installed from ports 
> 
> - I deleted all entries and maps in/under /usr/ports (as recommended in the
> Handbook) 
> 
>  
> 
> - I modified the ports-supfile in usr/share/examples/cvsup and copied it to
> portswj-supfile  in the same map (not good practice I know now)
> 
> The settings in the -supfile where:
> 
>   *default host=cvsup15.FreeBSD.org  
> 
>   *default base=/var/db
> 
>   *default prefix=/usr
> 
>   *default release=cvs tag=RELENG_6_2_0_RELEASE   (the handbook suggests
> that this is a valid tag for ports)

I doubt the handbook suggests that.  If it does it is wrong.

> 
>   *default delete use-rel-suffix   (I could not find a meaning for this in
> the books, anyone can tell me please?)

Read the cvsup(1) manpage.

> 
>   *default compress
> 
>   ports-all
> 
>  
> 
> - I ran:  cvsup -L 2 /usr/share/examples/cvsup/portswj-supfile
> 
> The conversation looked OK, no error messages but also no scrolling list of
> files
> 
> There is a logfile in  /var/db/sup ports-all, something like
> .cvs:RELENG_6_2_0_RELEASE. It shows a list of all the elements of the
> ports collection that looks normal and every record shows also
> RELENG_6_2_0_RELEASE.
> 
>  
> 

-- 

Erik Trulsson
[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: 7.0-PRERELEASE installworld fails

[Boris Samorodov]

On Sun, 6 Jan 2008 03:38:16 -0800 (PST) Unga wrote:

> --- Boris Samorodov <[EMAIL PROTECTED]> wrote:

> > > > This may be an overkill but should do the job:
> > > > # rm -r /usr/src /usr/obj
> > > > 
> > > > # cd /usr/src
> > > > # make buildworld
> > > > # make kernel
> > > > # mergemaster -p
> > > > # make installworld
> > > > # mergemaster -i
> > 

> I did above but its still the same story, installworld
> fails:
> --
> >>> Installing everything
> --
> cd /usr/src; make -f Makefile.inc1 install
> ===> share/info (install)
> ===> lib (install)
> ===> lib/csu/i386-elf (install)
> cc -O2 -fno-strict-aliasing -pipe 
> -I/usr/src/lib/csu/i386-elf/../common  -I/usr
> /src/lib/csu/i386-elf/../../libc/include
> -Wsystem-headers -Wall -Wno-format-y2k
> -W -Wno-unused-parameter -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arit
> h -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
> -Wshadow -Wcast-align -Wunu
> sed-parameter -Wchar-subscripts -Winline
> -Wnested-externs -Wredundant-decls -Wno
> -pointer-sign -c /usr/src/lib/csu/i386-elf/crt1.c
> /usr/src/lib/csu/i386-elf/crt1.c:33:20: error:
> stdlib.h: No such file or directory


> The only difference what I did compared to your steps:

Please, do just what I suggested and see if it helps.

> 1. After download sources, rebooted to single-user

Single-user mode is not necessary here.

> mode, adjkerntz -i (as my CMOS is set to local time),
> fsck -p, mount -u /, mount -a, swapon -a,

This is not needed at all (but seems to be harmless).

> /usr/local/bin/bash and follow your steps until make

Ah, don't use bash here (upgrade/build OS). Use standard shells.

> kernel (in fact, instead make kernel what I did was:
> kernel-toolchain, buildkernel and installkernel)

> 2. After installkernel, I rebooted to single-user mode
> with the new kernel, adjkerntz -i, fsck -p, mount -u
> /, mount -a, swapon -a,

Those steps are needed at long jumps and should be harmless
here.

> /usr/local/bin/bash and follow

Don't use bash here.

> your steps until make installworld.

> Before execute every step, I checked system time with
> date, they were all local time.

There is no need to check it. Just don't touch time while OS
building/installing.

> Have I deviated too much than you specified?

Yep.

> or is it
> essentially the same?

No.

> Am I supposed to reboot with the
> new kernel after make kernel?

Seems to be "yes" only for very long jumps. Actually I never had to
do it myself.

> What else I could do to identify the cause?

;-) Please, do just what I suggested.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

port collection RELEASE6.2 lost after reinstall with CVSUP

[Walter Jansen]

Hi

 

Upon reading chapters of the Handbook about the Ports collection and CVSup,
I wanted to CVSup the ports collection for the RELEASE  6.2. Stupidly using
the wrong tag (tag=.), I erroneously but successfully installed the CURRENT
version. I could have used SYSINSTALL for the RELEASE 6.2 ports, but for the
sake of learning and training myself I did not.

 

Problem: 

  - I ran CVSup again with the correct tag but though everything in the
process looked normal, the map usr/ports remains empty and nor with whereis
nor with pkg_xxx any information about ports can be found. 

Questions: 

  - What did I do wrong in the process?.  

  - Is cvsup for installation of RELEASE 6.2 ports collection a bad idea
anyway (technically) ?  

 

Proces:

- I use the recently installed cvsup-without-gui, installed from ports 

- I deleted all entries and maps in/under /usr/ports (as recommended in the
Handbook) 

 

- I modified the ports-supfile in usr/share/examples/cvsup and copied it to
portswj-supfile  in the same map (not good practice I know now)

The settings in the -supfile where:

  *default host=cvsup15.FreeBSD.org  

  *default base=/var/db

  *default prefix=/usr

  *default release=cvs tag=RELENG_6_2_0_RELEASE   (the handbook suggests
that this is a valid tag for ports)

  *default delete use-rel-suffix   (I could not find a meaning for this in
the books, anyone can tell me please?)

  *default compress

  ports-all

 

- I ran:  cvsup -L 2 /usr/share/examples/cvsup/portswj-supfile

The conversation looked OK, no error messages but also no scrolling list of
files

There is a logfile in  /var/db/sup ports-all, something like
.cvs:RELENG_6_2_0_RELEASE. It shows a list of all the elements of the
ports collection that looks normal and every record shows also
RELENG_6_2_0_RELEASE.

 

Regards,

Walter Jansen

 

   

 

 

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

Re: installing linux after freebsd (multi-boot)

[अनुज Anuj Singh]

hi,
Today I removed partitions from Fedora 7  installation , (kept /home
partition from FC7). Again went threw installation  I faced no problem
this time. Fedora 7 was installed without using LVM. on free space I
installed Ubntu7. server for test purpose. No error.
Sequence was Freebsd6.2 , Fedora Core 7 then RHEL4.

When I tried installation with deselecting many packages (minimal
installation) for RHEL5
without using LVM , I faced no problem, rebooted in mid to use
LVM+minimal RHEL5 again same error. Repetation with minimal
installation+ no LVM could not continued (found same error again).

Most likely it was due to partition table.

Now current partition table I have is.


Disk /dev/hdc: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot  Start End  Blocks   Id  System
/dev/hdc1   *   1127410233373+  a5  FreeBSD
   wrote:
> > "अनुज" == अनुज Anuj Singh <[EMAIL PROTECTED]> writes:
> अनुज> On Dec 31, 2007 1:29 PM, आशीष शुक्ल Ashish Shukla <[EMAIL 
> PROTECTED]> wrote:
> >> ,--[ On Mon, Dec 31, 2007 at 09:03:08AM +0530, अनुज Anuj Singh wrote:
> >>
> >> [snipped]
> >>
> >> | > >> On 30/12/2007,  <[EMAIL PROTECTED]> wrote:
> >> | > >>
> >> | > >>> Hello ,
> >> | > >>> I have freebsd6.2 installed with Fedora core 7 and rhe4.
> >> | > >>> I am installing rhel5 , when linux installation process starts 
> I get an
> >> | > >>> error of /dev/hdc1 busy , can not report to kernel about 
> partition
> >> | > >>> layout. In the past I installed linux then FreeBSD.
> >> | > >>> Is there some method that rhel5 installation can skip /dev/hdc1
> >> | > >>> (freebsd slice) ? saving my freebsd installation
> >>
> >> You get /dev/hdc1 busy error. At which step in installation, you get
> >> /dev/hdc1 busy error, hmm...? Are you trying to remove '/dev/hdc1'
> >> (FreeBSD slice), if yes, then you'll get error, and you probably need 
> to
> >> remove FreeBSD partitions (present in slice) first.
>
> अनुज> No I am not removing/mounting/using FreeBSD slice.
>
> अनुज> This is the log...
>
> अनुज> 03:29:50 INFO: moving (1) to step confirminstall
> अनुज> 03:30:13 INFO: moving (1) to step install
> अनुज> 03:30:13 INFO: moving (1) to step enablefilesystems
> अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol00, size of 1472
> अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol01, size of 2496
> अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol02, size of 672
> अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol03, size of 1024
> अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol04, size of 9984
> अनुज> 03:30:17 INFO: lv is VolGroup00/LogVol05, size of 9344
> अनुज> 03:30:17 INFO: removing lv LogVol03
> अनुज> 03:30:18 INFO: removing lv LogVol00
> अनुज> 03:30:18 INFO: removing lv LogVol04
> अनुज> 03:30:19 INFO: removing lv LogVol05
> अनुज> 03:30:19 INFO: removing lv LogVol02
> अनुज> 03:30:20 INFO: removing lv LogVol01
> अनुज> 03:30:21 INFO: pv is /dev/hdc11 in vg VolGroup00, size is 29996
> अनुज> 03:30:21 INFO: vgremove VolGroup00
> अनुज> 03:30:22 INFO: pvremove -ff -y /dev/hdc11
> अनुज> 03:30:22 INFO: pvcreate -ff -y -v /dev/hdc11
> अनुज> 03:30:23 CRITICAL: parted exception: Error: Error informing the 
> kernel
> अनुज> about modifications to partition /dev/hdc1 -- Device or resource 
> busy.
> अनुज> This means Linux won't know about any changes you made to /dev/hdc1
> अनुज> until you reboot -- so you shouldn't mount it or use it in any way
> अनुज> before rebooting.
> अनुज> 03:31:08 CRITICAL: Traceback (most recent call first):
> अनुज> File "/usr/lib/anaconda/partedUtils.py", line 876, in savePartitions
> अनुज> disk.commit()
> अनुज> File "/usr/lib/anaconda/packages.py", line 145, in turnOnFilesystems
> अनुज> anaconda.id.diskset.savePartitions ()
> अनुज> File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep
> अनुज> rc = stepFunc(self.anaconda)
> अनुज> File "/usr/lib/anacon

[BSDStats] Slight change in summary reporting ...

[Marc G. Fournier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I've just modified the code so that it reports on distinct hosts over the past 
60 days, vs just this past month ... for those that *may* have reported several 
times but have changed their OS (in theory, the only way that could happen is 
*if* they save/copy their /var/db/bsdstats file across a re-build, mind you), 
their last reported operating system is what will show up
...

This should make the statistics a bit more 'static', since we aren't reporting 
'from zero' at the start of each month ...

To view the current statistics, check out: http://www.bsdstats.org ...

- 
Marc G. Fournier   Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED]  MSN . [EMAIL PROTECTED]
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHgHVO4QvfyHIvDvMRAtSiAKDk32zdiiNCBU3dv3+Dr6aGzZLGRgCghhMe
mmvlJX5MbYOXxwhoJyadeSE=
=4inG
-END PGP SIGNATURE-

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

sound doesn't work randomly

[Mehul Ved]

Hi,
I have a Via8233 onboard sound card. After reading a few docs and
installing oss, I got sound to work but the problem is that it works
sometimes and just doesn't work other times. This only happens with
FreeBSD, with linux it's working fine all the time so I believe I can
rule out hardware problems.
Here is the sound card information that might be useful


pciconf -lv

[EMAIL PROTECTED]:17:5: class=0x040100 card=0x04301462 chip=0x30591106 rev=0x60 
hdr=0x00
vendor   = 'VIA Technologies Inc'
device   = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller'
class= multimedia
subclass = audio



kldstat

Id Refs AddressSize Name
 1   16 0xc040 33e03c   kernel
 21 0xc073f000 1ada4linux.ko
 31 0xc075a000 6170 snd_via8233.ko
 42 0xc0761000 22b88sound.ko
 51 0xc0784000 693310   nvidia.ko
 61 0xc0e18000 59f20acpi.ko
 72 0xc6191000 79000osscore.ko
 81 0xc6211000 5000 via8233.ko
 91 0xc6227000 2000 vmix.ko
---

---
/etc/rc.conf
oss_enable="YES"
---

---
/boot/loader.conf
snd_via8233_load="YES"
---

---
cat /dev/sndstat
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0:  at io 0xe700 irq 22 kld snd_via8233 (5p/1r/0v
channels duplex default)
---

cat  > /dev/dsp doesn't return any sound.

---
 ossdetect -v
Detected VIA VT8233/8235/8237
Detected OSS Transparent Virtual Mixing Architecture
---

---
 ossinfo -v
Version info: OSS 4.0 (b071114/200801041811) (0x00040003) CDDL
Platform: FreeBSD/i386 6.2-RELEASE FreeBSD 6.2-RELEASE #3: Sun Jan  6
14:16:34 IST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL (bsd.mehulved.com)

Number of audio devices:0
Number of audio engines:0
Number of MIDI devices: 0
Number of mixer devices:0


Device objects
 0: vmix0 OSS transparent virtual support

MIDI devices (/dev/midi*)

Mixer devices (/dev/mixer*)

Audio devices



 osstest -v
Sound subsystem and version: OSS 4.0 (b071114/200801041811) (0x00040003)
Platform: FreeBSD/i386 6.2-RELEASE FreeBSD 6.2-RELEASE #3: Sun Jan  6
14:16:34 IST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL


NOTICE! You don't have any audio devices available.
It looks like your audio hardware was not recognized
by OSS. Please contact 4Front technologies for help
(http://www.opensound.com/support.cgi). Don't forget to
include your soundon.log file to the support request.



 ossmix
SNDCTL_MIX_NREXT: Device not configured


I also checked

fstat | grep dsp

and killed any process if they were running.
None of it helped. All of a sudden again I have sound working right now.
Any other info will be needed?

Some links I refered to are
1)http://bsdtips.utcorp.net/mediawiki/index.php/Setting_up_your_sound_card
2)http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html
and some forums
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ipsec with dynamic ip clients

[Norman Maurer]

Hi all,

im using ipsec-tools + gif interfaces for connection some diffrent
offices via ipsec. This works perfectly!
Now I want to setup some config which allow some people to connection
via ipsec client to this ipsec router. They have a dynamic ip so I think
a certificate is the way to go. But im not sure how i need to setup the
gif interface because the ip address will change probally.

So any idea ? I couldn't find any docu :-/

bye
Norman


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

Re: 7.0-PRERELEASE installworld fails

[Unga]

--- Boris Samorodov <[EMAIL PROTECTED]> wrote:

> > > This may be an overkill but should do the job:
> > > # rm -r /usr/src /usr/obj
> > > 
> > > # cd /usr/src
> > > # make buildworld
> > > # make kernel
> > > # mergemaster -p
> > > # make installworld
> > > # mergemaster -i
> 

I did above but its still the same story, installworld
fails:
--
>>> Installing everything
--
cd /usr/src; make -f Makefile.inc1 install
===> share/info (install)
===> lib (install)
===> lib/csu/i386-elf (install)
cc -O2 -fno-strict-aliasing -pipe 
-I/usr/src/lib/csu/i386-elf/../common  -I/usr
/src/lib/csu/i386-elf/../../libc/include
-Wsystem-headers -Wall -Wno-format-y2k
-W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arit
h -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
-Wshadow -Wcast-align -Wunu
sed-parameter -Wchar-subscripts -Winline
-Wnested-externs -Wredundant-decls -Wno
-pointer-sign -c /usr/src/lib/csu/i386-elf/crt1.c
/usr/src/lib/csu/i386-elf/crt1.c:33:20: error:
stdlib.h: No such file or directory


The only difference what I did compared to your steps:
1. After download sources, rebooted to single-user
mode, adjkerntz -i (as my CMOS is set to local time),
fsck -p, mount -u /, mount -a, swapon -a,
/usr/local/bin/bash and follow your steps until make
kernel (in fact, instead make kernel what I did was:
kernel-toolchain, buildkernel and installkernel)

2. After installkernel, I rebooted to single-user mode
with the new kernel, adjkerntz -i, fsck -p, mount -u
/, mount -a, swapon -a, /usr/local/bin/bash and follow
your steps until make installworld.

Before execute every step, I checked system time with
date, they were all local time.

Have I deviated too much than you specified? or is it
essentially the same? Am I supposed to reboot with the
new kernel after make kernel?

What else I could do to identify the cause?

Regards
Unga


  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

can't start multi-xserver in freebsd7.0-rc1 with xorg7.3

[lveax]

hey all.

in an old computer with freebsd 6.2 with xorg7.2,i use

"startx" and "startx -- :1"

 to launch tow xserver for different application environment with tow
normal user.

but in freebsd7.0-rc1 with xorg7.3 i only can use root user to startx
use DISPLAY :1(startx -- :1),with a normal user it only output :

waiting for X server to begin accepting connections.

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

Installation issue with Compaq Presario V3420AU

[Suresh Ramasamy]

Hello all,

I'm currently trying to install FreeBSD into a Compaq Presario V3420AU 
with the following specs


Microprocessor: 2.0 GHz AMD Turion 64 X2 Dual-Core Mobile Technology TL-60
Memory: 2048 MB (2 x 1024 MB)
Video Graphics: NVIDIA GeForce Go 6150
Hard Drive 160 GB (5400 rpm)
Multimedia Drive Super Multi 8X DVD±RW with Double Layer Support
Display 14.1” WXGA High Definition BrightView Widescreen (1280 x 800)
Fax/Modem High speed 56K modem
Network Card Integrated 10/100 Ethernet LAN
Wireless Connectivity: Broadcom 802.11 a/b/g WLAN

Here's the problem

1. Installing with FreeBSD 7.0 RC1 amd64
- Boot up crashes with scrolling screen of the register values (non 
stop). Happens while the bootloader is running (-/|\).

2. Installing with FreeBSD 6.3 amd64
- Same issue as 1.
3. Installing with FreeBSD 6.3 i386 / 7.0 RC1 i386
- boot up with hint.acpi.0.disabled=1
- Shows error message with BTX Halted
- also tried setting hw.ata.ata_dma=0 and/or hw.ata.atapi_dma=0 , same 
problem


Here are the following register values shown on BTX Halted (for FreeBSD 
6.3 i386)


efl=00010002 eip=0003 eax=00449130 ecx=004f010f edx=0003fa40 
esp=000928b0


Values for FreeBSD 7.0 RC1 i386

efl=00010097 eip=00459160 eax=00459a30 ecx=a075 edx=00e2c3f0

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

Re: Asterisk-addons FreeBSD 7.0 :(

[Frank Shute]

On Sun, Jan 06, 2008 at 02:11:40AM -0600, David Alanis wrote:
>
> Good Day:
> 
> I just recently converted to FreeBSD and convinced my highly religious  
> (Gentoo) friend over as well. However, the ride has not been as smooth  
> as I would have liked. To make this story short, here is my late  
> Christmas wish-list regarding the lack-of documentation on the  
> installation of packages on FreeBSD.

Welcome to FreeBSD! And good work on the evangelisation :)

All the documentation you need is in the handbook:

http://www..freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html

If it's not in the handbook, it's in the comprehensive manpages.

If you decide to use ports (which you probably will coming from
Gentoo) then you want to read /usr/ports/UPDATING after you've
updated your ports tree with csup(1) and before you build a port.
UPDATING tells you of any gotchas you should be aware of before
building.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html

> Ah yeah, and in the process, I am  
> hoping to get help, pointers, or some type of recognition for  
> converting to the wonderful world of BSD! Please note, part of the  
> wish list comes with a bit of a Gentoo Linux bias having make.conf,  
> package.use, package.keywords, along with the USE="" flags so readily  
> available.

Your best bet to acquaint yourself with the system is reading the
handbook and asking questions here when you run into problems.

Forget your Gentoo biases, while it's similar in that you build from
source the process is quite different and requires less user
interaction. E.g If you want to fiddle with various knobs on some
piece of software (e.g apache) you will be presented with a curses
interface at the start of the build process where you set the knobs
you want.

> 
> Wish-list
> 
> 1.) Documentation about customization optimization-flags/configure  
> options (including which system files/location/make.conf may need to  
> be edited when building packages from ports (we did discover  
> portconf, but is this it?)

As I mentioned before, any configuration you may want to do is
presented to you when you build the port although there are clever
options you can use but as a beginner you're unlikely to want to use
them yet.

There's an example make.conf at /usr/share/examples/etc/make.conf
which shows you what switches you can put in /etc/make.conf (the one
that is parsed) and the manpage also tells you all about it.

You'll find though that your make.conf is fairly small.

A lot of people use portupgrade or portmaster to build and keep their
ports in order.

My choice is portupgrade.

I don't use portconf (nor do many others (I think) although it might
be a useful tool - I don't know) 

Most use pkgtools.conf(5) to do fancy things; those that do fancy
things with their ports. As a rule of thumb it's usually unnecessary.

But the pkgtools are useful. Start with pkg_info(1) and read on from
there. Most work with ports too.

One file you will have to edit is rc.conf(5)

> 
> 2.) We are also big into VoIP and just realized that FreeBSD 7.0 will  
> not build asterisk-addons on our home/production servers. So after  
> losing a ton of sleep we are now having to revert back to FreeBSD 6.2.  
> In short, can anyone fill us in to which FreeBSD distribution is  
> "known" to work splendid with the asterisk family?

In future when you have a port that wont build, post here & tell us
how you tried to build it. It should be as simple as:

# cd /usr/ports/net/asterisk-addons
# make install clean

If it fails, cut and paste the output where it fails and post it here.

FreeBSD 7.0 and 6.3 are in the final stages of being released so there
could still be some bugs but very few in the base system. The ports
are another matter but most should build.

Don't revert back to 6.2, it's probable that somebody knowledgeable
here can help you build your asterix bits given some debugging info.

If it can't be fixed on 7.0 you want to go back to RELENG_6_3 (cvs
tag) anyway since it's so close to release.

> 
> Thank you for your time,

No worries.

> FreeBSD rocks!

Yeah :)

> David A.
> 

-- 

 Frank 


 Contact info: http://www.esperance-linux.co.uk/misc/contact.html 

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

Re: How do I get sendmail working again

[Josh Tolbert]

On Sun, Jan 06, 2008 at 09:22:52AM +, Matthew Seaman wrote:
> There's your problem.  You've got two conflicting sets of daemon
> options -- effectively you're telling sendmail to bind to the
> same interfaces twice for port 25.
> 
> Just delete the DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl line
> and try again.
> 
>   Cheers,
> 
>   Matthew

Or just comment out both the IPv4 and IPv6 DAEMON_OPTIONS lines, leaving the
smtp/smtps lines alone. I didn't notice that in the config he posted; good
catch.

I sent Andy my box's .mc and it has both commented out.

Thanks,

Josh
-- 
Josh Tolbert
[EMAIL PROTECTED]  ||  http://www.puresimplicity.net/~hemi/

Security is mostly a superstition. It does not exist in nature, nor
do the children of men as a whole experience it. Avoiding danger
is no safer in the long run than outright exposure. Life is either
a daring adventure, or nothing.
-- Helen Keller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: How do I get sendmail working again

[Matthew Seaman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Andrew Falanga wrote:

[...]
> dnl Enable for both IPv4 and IPv6 (optional)
> DAEMON_OPTIONS(`Name=IPv4, Family=inet')  <-
> DAEMON_OPTIONS(`Name=IPv6, Family=inet6, Modifiers=O')
[...]
> DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl  <-
> DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA')dnl

There's your problem.  You've got two conflicting sets of daemon
options -- effectively you're telling sendmail to bind to the
same interfaces twice for port 25.

Just delete the DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl line
and try again.

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
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHgJ3s8Mjk52CukIwRCKmsAKCM/low+P7iOUFSybpFdQejJ+ZYygCfdRSq
n90ur8gEwn/AoRJxLsbgMWg=
=ZDaJ
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Users login configuration

[ivan dimitrov]

 Hi list, 
 
i have a freebsd server connected in local network behind a router. 
is there a way to configure the sshd to allow to login some (group of)  users 
with their passwords only from the local network and to allow  login other (and 
part of these) users only with key pairs from the  internet (on that side of 
the router)? 
 
Best Regards 
ivan 
 


   
-
Never miss a thing.   Make Yahoo your homepage.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Users login configuration

[ivan dimitrov]

Hi list,

i have a freebsd server connected in local network behind a router.
is there a way to configure the sshd to allow to login some (group of) 
users with their passwords only from the local network and to allow login other 
(and part of these) users only with key pairs from the internet (on that side 
of the router)?

Best Regards
ivan



   
-
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
___
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] cvsup for ports -- Re: compact portsnap db

[Michael Lednev]

Hello, Rudy.

On 6 января 2008 г., 5:43:54 you wrote:

>> Is there any way to compact /var/db/portsnap other than deleting it
>> and doing postsnap fetch?

R> I don't like portsnap -- granted I've never typed the portsnap
R> command in my 10 years of FreeBSD 
R> use.  I use cvsup!

Probably because portsnap is about 2 yo. The question is not "How to
update my ports tree", its "How to compact /var/db/portsnap". Thanks
for the answer anyway.

PS try csup. This is cvsup clone written in C. Comes with the base
system.

-- 
Best regards,
 Michael  mailto:[EMAIL PROTECTED]

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

xfce4-seesion/HAL/dbus error

[Jacob Shapleski]

> uname -a

FreeBSD 124.***.**.*** 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 
\ UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

> I get the following error message when I shutdown xfce4

** (xfce4-session:985): WARNING **: xfsm-shutdown-helper.c:94: Failed to 
connect to the system message bus: Failed to connect to socket 
/var/run/dbus/system_bus_socket: No such file or directory
** Message: xfsm-shutdown-helper.c:215: HAL not available or does not permit to 
shutdown/reboot the computer, trying sudo fallback instead.
unsetenv: not found
unsetenv: not found
Agent pid 977 killed

waiting for X server to shutdown The application 'xfce-mcs-manager' lost its 
connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed the application.
FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc" refcount is 2, should be 1; 
fixing.

> I have FreeBSD 6.2 running in VMware Workstation 6. Since installing from 6.2 
> iso yesterday, I have updated the ports collection using portsnap, and 
> installed the following ports: xorg, xfce4, sudo, firefox, emacs. Both HAL 
> and dbus were installed as dependencies. I have tried launching dbus manually 
> using # dbus-launch, and have trawled google for a fix with no success...

>Thanks in advance for your help :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Asterisk-addons FreeBSD 7.0 :(

[David Alanis]

Good Day:

I just recently converted to FreeBSD and convinced my highly religious  
(Gentoo) friend over as well. However, the ride has not been as smooth  
as I would have liked. To make this story short, here is my late  
Christmas wish-list regarding the lack-of documentation on the  
installation of packages on FreeBSD. Ah yeah, and in the process, I am  
hoping to get help, pointers, or some type of recognition for  
converting to the wonderful world of BSD! Please note, part of the  
wish list comes with a bit of a Gentoo Linux bias having make.conf,  
package.use, package.keywords, along with the USE="" flags so readily  
available.



Wish-list

1.) Documentation about customization optimization-flags/configure  
options (including which system files/location/make.conf may need to  
be edited when building packages from ports (we did discover  
portconf, but is this it?)


2.) We are also big into VoIP and just realized that FreeBSD 7.0 will  
not build asterisk-addons on our home/production servers. So after  
losing a ton of sleep we are now having to revert back to FreeBSD 6.2.  
In short, can anyone fill us in to which FreeBSD distribution is  
"known" to work splendid with the asterisk family?


Thank you for your time,
FreeBSD rocks!
David A.


This message was sent using IMP, the Internet Messaging Program.

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