Re: gemeral questions (noobish)

[Fraser Tweedale]

On Sun, Aug 03, 2008 at 04:06:40PM +1000, Norberto Meijome wrote:
> On Sat, 2 Aug 2008 22:35:40 +0200
> mcassar <[EMAIL PROTECTED]> wrote:
> 
> > so most of you _do_ use or prefer csup/cvsup more than portsnap, right? 
> 
> Welcome! :)
> 
> yes and no :P I like portsnap. faster.
> 
> For my ports, i run this script ( ~/bin/update_ports.sh)
> 
> #!/bin/sh
> sudo portsnap fetch && sudo portsnap update
> 
> [snip]
> 

Did you know you can specifiy fetch and update at the same time?

sudo portsnap fetch update

...and save calling portsnap twice :)

frase



pgpdgJvWmlO6K.pgp
Description: PGP signature

Re: gemeral questions (noobish)

[Norberto Meijome]

On Sat, 2 Aug 2008 22:35:40 +0200
mcassar <[EMAIL PROTECTED]> wrote:

> so most of you _do_ use or prefer csup/cvsup more than portsnap, right? 

Welcome! :)

yes and no :P I like portsnap. faster.

For my ports, i run this script ( ~/bin/update_ports.sh)

#!/bin/sh
sudo portsnap fetch && sudo portsnap update
---
( sudo is the port security/sudo and it allows for fine grained control
root-access to certain commands only )

There are 2 ports that will help you with management of your ports/packages -
ports-mgmt/portupgrade and ports-mgmt/portmaster ( which
means /usr/ports/ports-mgmt/portupgrade/ , etc... )  - they can tell you what
needs updating,etc (can't remember if it is in the handbook...)

Anyway, for my src tree:
1) my /etc/make.conf has :
[...]
SUP_UPDATE=YES
SUP=/usr/bin/csup
SUPFLAGS=-g -L 2 -P m
SUPFILE=/usr/local/etc/standard-supfile
NO_PORTSUPDATE=true
[...]

-
the NO_PORTSUPDATE=true is so the std supfile doesn't pull in ports too. (maybe
i don't need it anymore, but it really doesn't break anything).

The /usr/local/etc/standard-supfile is :

*default host=cvsup5.FreeBSD.org
*default base=/var/db
*default prefix=/usr

## next line can have a date to peg src tree to a particular date : 
date=2007.12.05.01.00.00
*default release=cvs tag=RELENG_7 

*default delete use-rel-suffix

*default compress
src-all
--

and to update, 
cd /usr/src && sudo make update


Mind you, I am tracking STABLE. and use this because i have a custom kernel
(just because i can :P ). For those of my machines which use GENERIC,i just use
freebsd-update as explained by Giorgios already.

Any issues, just shoot more emails :)

Have fun!
B
_
{Beto|Norberto|Numard} Meijome

Quantum Logic Chicken:
  The chicken is distributed probabalistically on all sides of the
  road until you observe it on the side of your course.

I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

tracker could not connect to server --rtorrent

[luizbcampos]

   On using rtorrent a sudden message appears up on the screnn
--tracker could not connect to server -- I should warn udp ports are
disabled on rtorrent.rc despite my machine is behind pf.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Backspace Key Not Working

[Michael P. Soulier]

On 26/07/08 Schiz0 said:

> Hey,
> 
> I have an annoying problem that I'm not sure how to solve. Here's my setup:
> 
> PuTTy => My FreeBSD 6.2 box => Production FreeBSD 7.0 box
> 
> All via SSH, of course. Now, on my FreeBSD 6.2 box, the backspace key
> works fine all the time. However, when I connect from my 6.2 box into
> the production 7.0 box, the backspace key does not work all the time.
> In the console, it works fine (as in, it deletes what I type).
> However, when I'm in programs such as VIM, it displays "^?" instead of
> deleting. Is there a way to fix this?

Does it work in the terminal?

Lets see 

stty -a

in the shell. 

Also see

:h fixdel

in Vim. 

Mike
-- 
Michael P. Soulier <[EMAIL PROTECTED]>
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction." --Albert Einstein


signature.asc
Description: Digital signature

Re: undocumented tar --unlink switch

[Josh Carroll]

> Around line 37 of /usr/src/usr.sbin/pkg_install/add/extract.c
> there's an invocation of /usr/bin/tar with a --unlink switch,
> which I don't see mentioned in the tar(1) manpage.  Anyone
> happen to know what this does, or do I need to dig into the
> code?

My guess was that it was the long option version of -U:

 -U  (x mode only) Unlink files before creating them.  Without this
 option, tar overwrites existing files, which preserves existing
 hardlinks.  With this option, existing hardlinks will be broken,
 as will any symlink that would affect the location of an

A quick perusal of the source confirms.

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

Re: undocumented tar --unlink switch

[Dan Nelson]

In the last episode (Aug 02), [EMAIL PROTECTED] said:
> Around line 37 of /usr/src/usr.sbin/pkg_install/add/extract.c
> there's an invocation of /usr/bin/tar with a --unlink switch,
> which I don't see mentioned in the tar(1) manpage.  Anyone
> happen to know what this does, or do I need to dig into the
> code?

That's just the longopts version of -U.  They're mainly for gnutar
compatibility, and the manpage refers to them at the very end:

 There are alternative long options for many of the short options
 that are deliberately not documented.


-- 
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]"

undocumented tar --unlink switch

[perryh]

Around line 37 of /usr/src/usr.sbin/pkg_install/add/extract.c
there's an invocation of /usr/bin/tar with a --unlink switch,
which I don't see mentioned in the tar(1) manpage.  Anyone
happen to know what this does, or do I need to dig into the
code?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

The FreeBSD Diary: 2008-07-13 - 2008-08-02

[Dan Langille]

The FreeBSD Diary contains a large number of practical 
examples and how-to guides.  This message is posted weekly
to freebsd-questions@freebsd.org with the aim of letting people
know what's available on the website.  Before you post a question
here it might be a good idea to first search the mailing list 
archives  
and/or The FreeBSD Diary . 


-- 
Dan Langille
BSDCan - http://www.BSDCan.org/ - BSD Conference

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

Re: gemeral questions (noobish)

[mcassar]

thanks alot for that.

i mean, apart from your general overview of freebsd (system, project and 
community), which gives me an idea how things are done, what's happeniing and 
where things are, you really put me at ease with trying to figure out these 
warnings, or at least what to expect and where to start - i wasn't sure if it 
was up to my setup or what.

although i don't know if you misunderstood my saying *fix them* as in i should 
setup my system properly, or as in get to bug-tracing and the like; which is 
still out of my expertise and jurisdiction. or was that wishfull thinking? it 
is something i want to figure out eventually, but at the moment i'm still so 
fascinated by everything (system, community)  that i'm trying to catch up on 
as much as i can.

anyway, it's getting late here now and i honestly forgot what else i was going 
to say, except thanks for the welcome. appreciiated since i honestly still 
can't beleive i was missing out on this fbsd *stuff*

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

Re: Did a makeworld now my jails won't start!! Uh oh..

[Redd Vinylene]

I tried changing "camel_ruleset" and "box_ruleset" to
"devfsrules_jail" in rc.conf, it got rid of the "devfs_set_ruleset:
you must
specify a ruleset number" but whenever I try to SSH into one of my
jails I seem to have logged onto the main system.

I'm confused :(

On Sat, Aug 2, 2008 at 10:34 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
> Greetings, i just did a makeworld of my main system and both my jails
> (http://pastie.org/246273) but now my jails won't run. i get
>
> Starting jails:/etc/rc.d/jail: WARNING: devfs_set_ruleset: you must
> specify a ruleset number
> devfs rule: ioctl DEVFSIO_SAPPLY: No such process
>
> here's my main system's rc.conf http://pastie.org/246272
>
> thanks!
>
> --
> http://www.home.no/reddvinylene
>



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

Re: gemeral questions (noobish)

[mcassar]

On Saturday 02 August 2008 21:43:43 Robert Huff wrote:
> Michael Powell writes:
> >  I can only speak to cvsup or csup (which I use) but I'd like to point
> > out a very common mistake wrt either. It is a good idea to have two
> > different sup files, as they will need to download different collections
> > of material. For example this:
> >
> >  *default release=cvs tag=RELENG_7_0
> >  src-all
> >
> >  combination will pull down the system sources for the security updates
> > to RELEASE. Read in the Handbook about the tags and collections.
> >
> >  I keep a separate sup file for keeping the ports tree updated and the
> >  difference is here:
> >
> >  *default release=cvs tag=.
> >  ports-all
>
>   I have a file for src-, one for ports-, and one for doc-.
>
>
>   Robert Huff

so most of you _do_ use or prefer csup/cvsup more than portsnap, right? 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Did a makeworld now my jails won't start!! Uh oh..

[Redd Vinylene]

Greetings, i just did a makeworld of my main system and both my jails
(http://pastie.org/246273) but now my jails won't run. i get

Starting jails:/etc/rc.d/jail: WARNING: devfs_set_ruleset: you must
specify a ruleset number
devfs rule: ioctl DEVFSIO_SAPPLY: No such process

here's my main system's rc.conf http://pastie.org/246272

thanks!

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

Re: jail_box_ip=""

[Redd Vinylene]

Actually:

jail_box_ip=$( jot -w "66.252.2.%d" -s "," 124 4 )

gives me:

Aug  2 20:10:50 mother root: /etc/rc: WARNING: devfs_set_ruleset: you
must specify a ruleset number
Aug  2 20:10:58 mother root: /etc/rc: ERROR: jail: No IP address has
been defined for box

On Sat, Aug 2, 2008 at 9:16 PM, Lars Kristiansen
<[EMAIL PROTECTED]> wrote:
> Redd Vinylene skrev:
>>
>> Can something similar be used for my
>>
>> ifconfig_rl0_aliasN="inet 66.252.2.N netmask 255.255.255.255"
>>
>> as well?
>>
>
> This is not as elegant, but may help in a similar way:
>
> alia=-1;
> while [ "$alia" -lt '123' ] ; do
>  alia=$(($alia+1)) ;
>  ips=$(($alia+4)) ;
>  echo "ifconfig_rl0_alias$alia=\"inet 66.252.2.$ips netmask
> 255.255.255.255\"" ;
> done
>
>
> Regards
> Lars,
> arbeidsøkende, Oslo
>
>
>> On Sat, Aug 2, 2008 at 8:07 PM, Redd Vinylene <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> jail_box_ip=$( jot -w "66.252.2.%d" -s "," 124 4 )
>>>
>>> What a gorgeous solution ;)
>>>
>>> Thanks man!
>>>
>>> On Sat, Aug 2, 2008 at 7:37 PM, Matthew Seaman
>>> <[EMAIL PROTECTED]> wrote:

 Redd Vinylene wrote:
>
> Hey, I got a couple of hundred IPs, is there an easy way to add them
> all to jail_box_ip="ip1,ip2,ip3" without making like the longest line
> ever?
>
> Like this?
>
> jail_box_ip="66.252.2.4,\
> 66.252.2.5,\
> 66.252.2.6,\
>
> Unfortunately that doesn't look too good.
>
> Nor does:
>
> export x=$(cat ips);export jail_ips=''; for ip in $x; do export
> jail_ips="$jail_ips,$ip"; done; export jail_ips=$(echo $jail_ips | sed
> s/,$/''/ | sed s/^,//);
>
> Is there a more beautiful alternative?

 /etc/rc.conf is just /bin/sh code.  All you need to do is set
 the variables -- usually by assigning a static string, but you
 can use whatever constructs you want.  Well - within reason.  Making
 something as critical as the system boot process depend on a bunch of
 other files or processes is not a good idea on the whole.

 You can include multi-line whitespace in the variables by using single
 quotes:

 jail_box_ip='66.252.2.4,
66.252.2.5,
66.252.2.6,
   66.252.2.7'

 Assuming that the init script that processes this data isn't phased
 by the inclusion of a bit of whitespace.

 Or you can generate the required numbers, assuming they are
 consecutive:

 jail_box_ip=$( jot -w "66.252.2.%d" -s "," 5 4  )

   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


>>>
>>>
>>> --
>>> http://www.home.no/reddvinylene
>>>
>>
>>
>>
>
>



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

Re: Reducing 124 ifconfig lines in rc.conf to just 1

[Redd Vinylene]

On Sat, Aug 2, 2008 at 9:24 PM, Polytropon <[EMAIL PROTECTED]> wrote:
> Hi!
>
> On Sat, 2 Aug 2008 21:11:47 +0200, "Redd Vinylene" <[EMAIL PROTECTED]> wrote:
>> Greetings!
>>
>> I got 124 ifconfig lines going from ifconfig_rl0_alias0="inet
>> 80.252.2.3 netmask 255.255.255.255" to ifconfig_rl0_alias124="inet
>> 80.252.2.127 netmask 255.255.255.255".
>>
>> Is it possible reducing it all to just 1 line using a for loop or jot
>> or something?
>
> I'm thinking of a "two stage procedure" that can be implemented
> well with /etc/rc.conf. Stupid idea, I know, but it should work,
> allthough you could make it more tidy:
>
> # First create /etc/ifconfig.conf if not already there
> if [ ! -f /etc/ifconfig.conf ]; then
>echo "#!/bin/sh" > /etc/ifconfig.conf
>ALIAS=0
>while [ ${ALIAS} -lt 125 ]; do
>echo 'ifconfig_rl0_alias${ALIAS}="inet 80.252.2.`expr ${ALIAS} 
> + 4` netmask 255.255.255.255" >> /etc/ifconfig.conf
>ALIAS=`expr ${ALIAS} + 1`
>done
> fi
>
> # Now source it into /etc/rc.conf
> . /etc/ifconfig.conf
>
> # Done.
>
>
> --
> Polytropon
> From Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
>

That will probably work. Looks a bit messy though, I'll use it if
nobody else knows of a simpler solution.

Thanks!

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

Re: Reducing 124 ifconfig lines in rc.conf to just 1

[Redd Vinylene]

Cool!

But isn't that to define the entire class? In my case it's just *.3 to
*.127, do you mean I can just

ifconfig_rl0_aliases="inet 80.252.2.3/127 netmask 255.255.255.255"

or something? Probably not but worth a try ;)

On Sat, Aug 2, 2008 at 9:44 PM, Robert Huff <[EMAIL PROTECTED]> wrote:
>
> Redd Vinylene writes:
>
>>  I got 124 ifconfig lines going from ifconfig_rl0_alias0="inet
>>  80.252.2.3 netmask 255.255.255.255" to ifconfig_rl0_alias124="inet
>>  80.252.2.127 netmask 255.255.255.255".
>>
>>  Is it possible reducing it all to just 1 line using a for loop or jot
>>  or something?
>
>Have you examined CIDR notation?  ifconfig supports it.
>
>
>Robert Huff
>
>



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

Re: The best way to upgrade my FreeBSD and its jails

[Redd Vinylene]

Sorry,

JAILS=/usr/jail

for jail in $JAILS/*; do

  mergemaster -p -D $jail

  make installworld delete-old delete-old-libs DESTDIR=$jail

  mergemaster -i -U -D $jail

done

:)

On Sat, Aug 2, 2008 at 9:55 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
> Sorry,
>
> JAILS=/usr/jail
>
> for jail in $JAILS/*; do
>
>  mergemaster -p -D $jail
>
>  make installworld delete-old delete-old-libs DESTDIR=$jail
>
>  mergemaster -i -U -D $jail
>
> done
>
> :)
>
> On Sat, Aug 2, 2008 at 4:26 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
>> Slight improvement, set -e replaces all the && \:
>>
>> -
>>
>> # FreeBSD/i386 mother.naoshige.net
>>
>> set -e
>>
>> csup /etc/cvsupfile
>>
>> cd /usr/src
>>
>> make buildworld buildkernel
>>
>> mergemaster -p
>>
>> make installworld installkernel delete-old delete-old-libs
>>
>> mergemaster -i -U
>>
>> JAILS=/usr/local/jails
>>
>> for jail in $JAILS/*; do
>>
>>  mergemaster -p -D $JAILS/$jail
>>
>>  make installworld delete-old delete-old-libs DESTDIR=$JAILS/$jail
>>
>>  mergemaster -i -U -D $JAILS/$jail
>>
>> done
>>
>> chflags -R noschg /usr/obj/*
>>
>> rm -rf /usr/obj/*
>>
>> -
>>
>> Peace!
>>
>> On Sat, Aug 2, 2008 at 12:03 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
>>> Thanks a lot guys for your great design insight!
>>>
>>> I hope others will find this thread interesting as well. Here's the
>>> final upgrade script I decided to use (my shell is zsh):
>>>
>>> -
>>>
>>> # FreeBSD/i386 mother.naoshige.net
>>>
>>> csup /etc/cvsupfile
>>>
>>> cd /usr/src
>>>
>>> make buildworld buildkernel && \
>>>
>>> mergemaster -p && \
>>>
>>> make installworld installkernel delete-old delete-old-libs && \
>>>
>>> mergemaster -i -U && \
>>>
>>> JAILS=/usr/local/jails
>>>
>>> cd /usr/src
>>>
>>> for jail in $JAILS/*; do
>>>
>>>  mergemaster -p -D $JAILS/$jail && \
>>>
>>>  make installworld delete-old delete-old-libs DESTDIR=$JAILS/$jail && \
>>>
>>>  mergemaster -i -U -D $JAILS/$jail && \
>>>
>>> done
>>>
>>> chflags -R noschg /usr/obj/*
>>>
>>> rm -rf /usr/obj/*
>>>
>>> -
>>>
>>> Much obliged!
>>>
>>> On Sat, Aug 2, 2008 at 9:28 AM, Miroslav Lachman <[EMAIL PROTECTED]> wrote:
 Mikhail Goriachev wrote:
>
> Redd Vinylene wrote:
>
>> My dedicated server is mother, its two jails are camel and box. Is
>> this the best way to upgrade all of them?
>
>
> We probably should keep this to freebsd-jail@ only.
>
> Had a look at http://pastie.org/245821 and have a few notes for you:
>
> 1.- As Miroslav already mentioned - it is not a good idea to daisy chain
> everything. You should break the procedure into two steps. Firstly upgrade
> the host and make sure the upgrade went well. Once you're certain that
> everything is ok, then proceed upgrading jails.
>
> I personally disable jails (jail_enable="NO"), then reboot (to avoid any
> zombie jails), perform upgrade on all jails and then enable them back on.
>
> 2.- Your upgrading sequence is a bit off. Have a look at /usr/src/Makefile
> for further details and correct sequence:
>
> # make buildworld
> # make buildkernel
> # make installkernel
> # reboot
> # mergemaster -p
> # make installworld
> # make delete-old
> # mergemaster
> # reboot
> # make delete-old-libs
>
> 3.- You don't need kernels inside your jails. Having them won't hurt you,
> but they consume space. In other words, you shouldn't execute the 
> following
> (or similar):
>
> # make DESTDIR=$D installkernel
>
> 4.- The "make distribution DESTDIR=$D" should be executed only once - when
> a jail is created. Otherwise you're nuking your configurations in jail's
> /etc and probably somewhere else.

 One thing to note - If you do delete-old delete-old-libs you probably need
 to recompile all installed ports because of lib dependencies.

> Have a go at this, you might find some use for it:
>
> ---
> JAILSDIR=/usr/local/jails
>
> cd /usr/src
>
> for jail in `ls ${JAILSDIR}`; do
>mergemaster -pD ${JAILSDIR}/${jail}
>make installworld DESTDIR=${JAILSDIR}/${jail}
>mergemaster -iD ${JAILSDIR}/${jail}
> done
> ---

>>>
>>
>
>
>
> --
> http://www.home.no/reddvinylene
>



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

Re: Reducing 124 ifconfig lines in rc.conf to just 1

[Polytropon]

Hi!

On Sat, 2 Aug 2008 21:11:47 +0200, "Redd Vinylene" <[EMAIL PROTECTED]> wrote:
> Greetings!
> 
> I got 124 ifconfig lines going from ifconfig_rl0_alias0="inet
> 80.252.2.3 netmask 255.255.255.255" to ifconfig_rl0_alias124="inet
> 80.252.2.127 netmask 255.255.255.255".
> 
> Is it possible reducing it all to just 1 line using a for loop or jot
> or something?

I'm thinking of a "two stage procedure" that can be implemented
well with /etc/rc.conf. Stupid idea, I know, but it should work,
allthough you could make it more tidy:

# First create /etc/ifconfig.conf if not already there
if [ ! -f /etc/ifconfig.conf ]; then
echo "#!/bin/sh" > /etc/ifconfig.conf
ALIAS=0
while [ ${ALIAS} -lt 125 ]; do
echo 'ifconfig_rl0_alias${ALIAS}="inet 80.252.2.`expr ${ALIAS} 
+ 4` netmask 255.255.255.255" >> /etc/ifconfig.conf
ALIAS=`expr ${ALIAS} + 1`
done
fi

# Now source it into /etc/rc.conf
. /etc/ifconfig.conf

# Done.


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

Re: Reducing 124 ifconfig lines in rc.conf to just 1

[Polytropon]

Hi!

On Sat, 2 Aug 2008 21:11:47 +0200, "Redd Vinylene" <[EMAIL PROTECTED]> wrote:
> Greetings!
> 
> I got 124 ifconfig lines going from ifconfig_rl0_alias0="inet
> 80.252.2.3 netmask 255.255.255.255" to ifconfig_rl0_alias124="inet
> 80.252.2.127 netmask 255.255.255.255".
> 
> Is it possible reducing it all to just 1 line using a for loop or jot
> or something?

I'm thinking of a "two stage procedure" that can be implemented
well with /etc/rc.conf. Stupid idea, I know, but it should work,
allthough you could make it more tidy:

# First create /etc/ifconfig.conf if not already there
if [ ! -f /etc/ifconfig.conf ]; then
echo "#!/bin/sh" > /etc/ifconfig.conf
ALIAS=0
while [ ${ALIAS} -lt 125 ]; do
echo 'ifconfig_rl0_alias${ALIAS}="inet 80.252.2.`expr ${ALIAS} 
+ 4` netmask 255.255.255.255" >> /etc/ifconfig.conf
ALIAS=`expr ${ALIAS} + 1`
done
fi

# Now source it into /etc/rc.conf
. /etc/ifconfig.conf

# Done.


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

Re: gemeral questions (noobish)

[Robert Huff]

Michael Powell writes:
>  I can only speak to cvsup or csup (which I use) but I'd like to point out a
>  very common mistake wrt either. It is a good idea to have two different sup
>  files, as they will need to download different collections of material. For
>  example this:
>  
>  *default release=cvs tag=RELENG_7_0
>  src-all
>  
>  combination will pull down the system sources for the security updates to
>  RELEASE. Read in the Handbook about the tags and collections.
>  
>  I keep a separate sup file for keeping the ports tree updated and the
>  difference is here:
>  
>  *default release=cvs tag=.
>  ports-all

I have a file for src-, one for ports-, and one for doc-.


Robert Huff


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

Using CPUTYPE=core2, Penryn instructions support

[Jakub Lach]

Hello.

>From what I understand, gcc42 does not support core2 option. How it's
possible that
some people are using it with FreeBSD -CURRENT (and it's not used as mere
prescott alias).

http://www.nabble.com/Re%3A-CPUTYPE-p10787174.html

Is -CURRENT using newer version of gcc, despite licensing problems?

I'm interested in using full Penryn instructions, if that would be
possible...
-- 
View this message in context: 
http://www.nabble.com/Using-CPUTYPE%3Dcore2%2C-Penryn-instructions-support-tp18792525p18792525.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

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

Re: jail_box_ip=""

[Lars Kristiansen]

Redd Vinylene skrev:

Can something similar be used for my

ifconfig_rl0_aliasN="inet 66.252.2.N netmask 255.255.255.255"

as well?



This is not as elegant, but may help in a similar way:

alia=-1;
while [ "$alia" -lt '123' ] ; do
  alia=$(($alia+1)) ;
  ips=$(($alia+4)) ;
  echo "ifconfig_rl0_alias$alia=\"inet 66.252.2.$ips netmask 
255.255.255.255\"" ;

done


Regards
Lars,
arbeidsøkende, Oslo



On Sat, Aug 2, 2008 at 8:07 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote:

jail_box_ip=$( jot -w "66.252.2.%d" -s "," 124 4 )

What a gorgeous solution ;)

Thanks man!

On Sat, Aug 2, 2008 at 7:37 PM, Matthew Seaman
<[EMAIL PROTECTED]> wrote:

Redd Vinylene wrote:

Hey, I got a couple of hundred IPs, is there an easy way to add them
all to jail_box_ip="ip1,ip2,ip3" without making like the longest line
ever?

Like this?

jail_box_ip="66.252.2.4,\
66.252.2.5,\
66.252.2.6,\

Unfortunately that doesn't look too good.

Nor does:

export x=$(cat ips);export jail_ips=''; for ip in $x; do export
jail_ips="$jail_ips,$ip"; done; export jail_ips=$(echo $jail_ips | sed
s/,$/''/ | sed s/^,//);

Is there a more beautiful alternative?

/etc/rc.conf is just /bin/sh code.  All you need to do is set
the variables -- usually by assigning a static string, but you
can use whatever constructs you want.  Well - within reason.  Making
something as critical as the system boot process depend on a bunch of
other files or processes is not a good idea on the whole.

You can include multi-line whitespace in the variables by using single
quotes:

jail_box_ip='66.252.2.4,
66.252.2.5,
66.252.2.6,
   66.252.2.7'

Assuming that the init script that processes this data isn't phased
by the inclusion of a bit of whitespace.

Or you can generate the required numbers, assuming they are
consecutive:

jail_box_ip=$( jot -w "66.252.2.%d" -s "," 5 4  )

   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





--
http://www.home.no/reddvinylene







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

Re: gemeral questions (noobish)

[Giorgos Keramidas]

On Sat, 2 Aug 2008 18:32:53 +0200, mcassar <[EMAIL PROTECTED]> wrote:
> damn, thanks - I had mistaken stable to be what is release; i had come
> across the difference at some point but didn't realise when i tried
> cvsup (which i also mistook to be more recent than csup).

First of all, a hearty "welcome" :)

You've only been reading about FreeBSD for a month, but you already
managed to install fairly big packages, like KDE and XFCE, learn about
csup, supfiles, the ports, and a lot of other stuff.  Congratulations on
the progress, and we hope you will enjoy FreeBSD as much as many of us
also do.

> I only tried csup on ports once and wasn't too sure i should since the
> handbook or somewhere mentioned the ports tree should be empty the
> first time you run it; and got the impression you should only use
> either or (csup vs portsnap).

One of the important details about keeping up to date with FreeBSD is
that you usually have *two* options for almost everything:

- Update from the source

- Update from 'binaries'

(1) The source side of things

The full source to the base system and the full source of the Ports,
including change history (like who made a change, when, and why), is
available online.  This is an important part of the whole FreeBSD
"culture", and it works in several nice ways: (a) You can go "back" when
a change is made but you don't like it, (b) you can see who made a
particular change and why, and this works a lot of time both as a
tracking tool and, almost as importantly, (d) as educational.

So if you want to learn more about how a fairly large body of source
code is maintained for several different architectures by a large,
distributed team of enthusiastic volunteers, the full history of FreeBSD
is available for browsing.

The source for FreeBSD is available through a variety of means.  Tools
like CVSup, csup, and Subversion can be used to pull copies of the
source with or without its full history.  The same tools (CVSup and
csup) can be used to pull and periodically re-synchronize copies of the
source for: the base system, the Ports collection, our documentation, or
our web site.

If you plan to build several versions of the source tree, from one of
the various "branches" of development, it is nice to be able to switch
from one version to the other without heavy utilization of the network.
In this case, CVSup is a great way of pulling full "mirrors" of the CVS
repositories.  But this needs a fair amount of disk space (slightly more
than 2 GB the last time I checked for a full repository mirror of the
src/, doc/, www/ and ports/ repositories).

(2) The 'binary' side of things

On the other hand, if you don't really want to dig that far into the
"source" part of things, and you just want to get some work done, you
can use a second collection of "update tools" like:

* freebsd-update

  For updating the binaries of the base system.

* portsnap

  For downloading snapshots of the /usr/ports tree

* portupgrade with the -PP option

  For updating the installed third-party packages, using only the
  prebuilt binary packages of the FreeBSD port-builders team.

The choice between checking out the source from CVS and using the
prebuilt code whenever possible is something only *you* are qualified to
make for yourself.  Disk space constraints, limits to the time you can
put into keeping the system update, and the level of "bleeding edge" you
want to keep up with may influence your final decision and push towards
one or the other option.

The nice thing about it all is that you *do* have a choice :-)

> I hate to bother any further but have one thing to clarify about
> building attempts - when building anything, if that's ok. I only have
> a basic understanding of C so far, and can't really tell how critical
> warnings are - such as undefined this and that, defined but not
> used...etc, when building a port.  should i stop those and see how i
> should fix them or let them proceed as long as they're not errors? I
> can live with my current system for now, but have a few things i need
> to update eventually.

The short answer to "Should I bother?" is "Sure, please do.  Before you
start 'hacking' at ports, however, we should make it clear that a lot of
the existing problems are already fixed and it takes a certain amount of
dedication, time and effort to fix the remaining bits.".

The longer answer, which is slightly more interesting IMHO, is...

The number of broken, completely bogus or just 'unportable' assumptions
people make when they write software is mind-numbing.  It is often
utterly incomprehensible and absolutely stunning how many or how serious
assumptions some third-party tools make.

All this leads to a lot of the warnings you mentioned above.

The FreeBSD port maintainers commonly make an effort to fix these
problems as part of the "porting effort".  This is why many of the ports
have local, FreeBSD-specific patches.

If you look in a typical port, there 

Client only supports checkout mode

[kalin m]

hi all...

why would i get : "Client only supports checkout mode" when i do;
csup /cvsup_file

on a new freebsd 7 install

what does it mean?!


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

Reducing 124 ifconfig lines in rc.conf to just 1

[Redd Vinylene]

Greetings!

I got 124 ifconfig lines going from ifconfig_rl0_alias0="inet
80.252.2.3 netmask 255.255.255.255" to ifconfig_rl0_alias124="inet
80.252.2.127 netmask 255.255.255.255".

Is it possible reducing it all to just 1 line using a for loop or jot
or something?

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

Re: gemeral questions (noobish)

[mcassar]

On Saturday 02 August 2008 19:38:20 Michael Powell wrote:

> I can only speak to cvsup or csup (which I use) but I'd like to point out a
> very common mistake wrt either. It is a good idea to have two different sup
> files, as they will need to download different collections of material. For
> example this:
>
> *default release=cvs tag=RELENG_7_0
> src-all
>
> combination will pull down the system sources for the security updates to
> RELEASE. Read in the Handbook about the tags and collections.
>
> I keep a separate sup file for keeping the ports tree updated and the
> difference is here:
>
> *default release=cvs tag=.
> ports-all
>
> Please notice that if you use the "tag=." with "src-all" you will pull down
> HEAD, which is the "bleeding edge" of development and not what a beginner
> should be using. But when used with the ports "collection" you will get an
> up to date ports tree.

now this makes sense, i wasn't too sure from reading the handbook so i thought 
i'd play safe and use the example ports-supfiles, but then used the example 
stable-supfile instead of whichever is for release. lives and learns.

> > anyhow i think that only my nvidia driver instructions mentioned it
> > relies on what i think are system sources (kernel related - if i'm not
> > mistaken) - but i haven't touched that yet.
>
> Generally speaking before building something like the nvidia drivers using
> the ports system the best first step is to refresh the ports tree. With all
> dependencies tracked and updated you'll likely have more success. Notice,
> for instance, that the nvidia driver depends on having what we call
> the "linuxulator" installed. It'll do this for you but you may have to
> enter a line in your /boot/loader.conf to ensure the linux.ko kernel module
> gets loaded every time at boot. You will usually see some more instructions
> at the end if you need to do anything special. Also, be aware that the
> nvidia driver is only currently working with i386, _not_ amd64.

> Even if only using packages you should _still_ update the ports tree, as
> the package system relies on it for dependency tracking as well.
>
> > I hate to bother any further but have one thing to clarify about building
> > attempts - when building anything, if that's ok. I only have a basic
> > understanding of C so far, and can't really tell how critical warnings
> > are - such as undefined this and that, defined but not used...etc, when
> > building a
> > port.  should i stop those and see how i should fix them or let them
> > proceed as long as they're not errors? I can live with my current system
> > for now, but have a few things i need to update eventually.
>
> When you use ports and compile stuff, you may see all manners of warnings,
> errors, and sundry garbage spewing forth from the compiler. Most of this,
> most of the time, is benign and not something to get overly concerned about
> as it is fairly normal. The exception is if the build errors out and
> completely quits, and there is an error sequence that will indicate
> whereabouts it bombed. Sometimes ports do get broken and need fixing, but
> most ports have a person who maintains them. If/when many people see the
> same error someone usually notifies the port maintainer and he/she then
> looks into fixing it.
>
> But generally speaking, if the build completes and runs without segfaulting
> just ignore what you may have seen scrolling by while building. Most of the
> time it's just "noise".  :-)
>
> -Mike
>
with the nvidia-driver, i've tried both ways 
1-> using the ports tree off the install discs without updating (which has a 
ver 100...,, something and seems to work ok with xorg from packages) ,,,
2 -> after updating the ports tree (which has ver 173..something) and seems to 
work better if i update xorg from ports.
 
The thing is, this usually goes like dominos and ends up in updating one thing 
after another; and with at least 350 packages to update at once, i easily 
loose track and just hope for the best.

I've had different results from that with the system as a whole, generally 
with good improvements on one end, and some broken stuff on the other, but 
only seen a segmentation fault once, now that you mention it. (it was with 
firefox but only that one time - never happened before)

So overall i wanted to rule out those warnings with updates in general, know 
how critical they are and whether i needed to go through configuration files 
first and what not.

thanks for all the info - everything starts to make sense as you go.

mcassar
>
>
> ___
> 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: jail_box_ip=""

[Redd Vinylene]

Can something similar be used for my

ifconfig_rl0_aliasN="inet 66.252.2.N netmask 255.255.255.255"

as well?

On Sat, Aug 2, 2008 at 8:07 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
> jail_box_ip=$( jot -w "66.252.2.%d" -s "," 124 4 )
>
> What a gorgeous solution ;)
>
> Thanks man!
>
> On Sat, Aug 2, 2008 at 7:37 PM, Matthew Seaman
> <[EMAIL PROTECTED]> wrote:
>> Redd Vinylene wrote:
>>>
>>> Hey, I got a couple of hundred IPs, is there an easy way to add them
>>> all to jail_box_ip="ip1,ip2,ip3" without making like the longest line
>>> ever?
>>>
>>> Like this?
>>>
>>> jail_box_ip="66.252.2.4,\
>>> 66.252.2.5,\
>>> 66.252.2.6,\
>>>
>>> Unfortunately that doesn't look too good.
>>>
>>> Nor does:
>>>
>>> export x=$(cat ips);export jail_ips=''; for ip in $x; do export
>>> jail_ips="$jail_ips,$ip"; done; export jail_ips=$(echo $jail_ips | sed
>>> s/,$/''/ | sed s/^,//);
>>>
>>> Is there a more beautiful alternative?
>>
>> /etc/rc.conf is just /bin/sh code.  All you need to do is set
>> the variables -- usually by assigning a static string, but you
>> can use whatever constructs you want.  Well - within reason.  Making
>> something as critical as the system boot process depend on a bunch of
>> other files or processes is not a good idea on the whole.
>>
>> You can include multi-line whitespace in the variables by using single
>> quotes:
>>
>> jail_box_ip='66.252.2.4,
>> 66.252.2.5,
>> 66.252.2.6,
>>66.252.2.7'
>>
>> Assuming that the init script that processes this data isn't phased
>> by the inclusion of a bit of whitespace.
>>
>> Or you can generate the required numbers, assuming they are
>> consecutive:
>>
>> jail_box_ip=$( jot -w "66.252.2.%d" -s "," 5 4  )
>>
>>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
>>
>>
>
>
>
> --
> http://www.home.no/reddvinylene
>



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

Re: jail_box_ip=""

[Redd Vinylene]

jail_box_ip=$( jot -w "66.252.2.%d" -s "," 124 4 )

What a gorgeous solution ;)

Thanks man!

On Sat, Aug 2, 2008 at 7:37 PM, Matthew Seaman
<[EMAIL PROTECTED]> wrote:
> Redd Vinylene wrote:
>>
>> Hey, I got a couple of hundred IPs, is there an easy way to add them
>> all to jail_box_ip="ip1,ip2,ip3" without making like the longest line
>> ever?
>>
>> Like this?
>>
>> jail_box_ip="66.252.2.4,\
>> 66.252.2.5,\
>> 66.252.2.6,\
>>
>> Unfortunately that doesn't look too good.
>>
>> Nor does:
>>
>> export x=$(cat ips);export jail_ips=''; for ip in $x; do export
>> jail_ips="$jail_ips,$ip"; done; export jail_ips=$(echo $jail_ips | sed
>> s/,$/''/ | sed s/^,//);
>>
>> Is there a more beautiful alternative?
>
> /etc/rc.conf is just /bin/sh code.  All you need to do is set
> the variables -- usually by assigning a static string, but you
> can use whatever constructs you want.  Well - within reason.  Making
> something as critical as the system boot process depend on a bunch of
> other files or processes is not a good idea on the whole.
>
> You can include multi-line whitespace in the variables by using single
> quotes:
>
> jail_box_ip='66.252.2.4,
> 66.252.2.5,
> 66.252.2.6,
>66.252.2.7'
>
> Assuming that the init script that processes this data isn't phased
> by the inclusion of a bit of whitespace.
>
> Or you can generate the required numbers, assuming they are
> consecutive:
>
> jail_box_ip=$( jot -w "66.252.2.%d" -s "," 5 4  )
>
>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
>
>



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

Re: I can't make world without the "games" group?

[RW]

On Sat, 2 Aug 2008 18:48:27 +0200
"Redd Vinylene" <[EMAIL PROTECTED]> wrote:

> Adding WITHOUT_GAMES="YES" to /etc/src.conf most certainly didn't
> work.
> 
> Why does FreeBSD pack so much, pardon my language, bullshit anyway?

It's largely a consequence of having a coherent OS, rather than a kernel
and third-party packages.

> Yes, one or two (out of one or two million) might need it, but can't
> we make it available to them in some other way? As a module or a port
> or something?

Like I already said, that's been done, the actual games went to a port.
I don't see why you care so much about removing 3.2Mb.

BTW please stop cross-posting to bugs, if you think you've found a
bug, you should go through proper channels and file a PR.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: jail_box_ip=""

[Matthew Seaman]

Redd Vinylene wrote:

Hey, I got a couple of hundred IPs, is there an easy way to add them
all to jail_box_ip="ip1,ip2,ip3" without making like the longest line
ever?

Like this?

jail_box_ip="66.252.2.4,\
66.252.2.5,\
66.252.2.6,\

Unfortunately that doesn't look too good.

Nor does:

export x=$(cat ips);export jail_ips=''; for ip in $x; do export
jail_ips="$jail_ips,$ip"; done; export jail_ips=$(echo $jail_ips | sed
s/,$/''/ | sed s/^,//);

Is there a more beautiful alternative?


/etc/rc.conf is just /bin/sh code.  All you need to do is set
the variables -- usually by assigning a static string, but you
can use whatever constructs you want.  Well - within reason.  Making
something as critical as the system boot process depend on a bunch of
other files or processes is not a good idea on the whole.

You can include multi-line whitespace in the variables by using single 
quotes:


jail_box_ip='66.252.2.4,
 66.252.2.5,
 66.252.2.6,
66.252.2.7'

Assuming that the init script that processes this data isn't phased
by the inclusion of a bit of whitespace.

Or you can generate the required numbers, assuming they are
consecutive:

jail_box_ip=$( jot -w "66.252.2.%d" -s "," 5 4  )

Cheers,

Matthew

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



signature.asc
Description: OpenPGP digital signature

Re: gemeral questions (noobish)

[Michael Powell]

mcassar wrote:
[snip]
> 
> I only tried csup on ports once and wasn't too sure i should since the
> handbook or somewhere mentioned the ports tree should be empty the first
> time you run it; and got the impression you should only use either or
> (csup vs portsnap).

I can only speak to cvsup or csup (which I use) but I'd like to point out a
very common mistake wrt either. It is a good idea to have two different sup
files, as they will need to download different collections of material. For
example this:

*default release=cvs tag=RELENG_7_0
src-all

combination will pull down the system sources for the security updates to
RELEASE. Read in the Handbook about the tags and collections.

I keep a separate sup file for keeping the ports tree updated and the
difference is here:

*default release=cvs tag=.
ports-all

Please notice that if you use the "tag=." with "src-all" you will pull down
HEAD, which is the "bleeding edge" of development and not what a beginner
should be using. But when used with the ports "collection" you will get an
up to date ports tree.
 
> anyhow i think that only my nvidia driver instructions mentioned it relies
> on what i think are system sources (kernel related - if i'm not mistaken)
> - but i haven't touched that yet.

Generally speaking before building something like the nvidia drivers using
the ports system the best first step is to refresh the ports tree. With all
dependencies tracked and updated you'll likely have more success. Notice,
for instance, that the nvidia driver depends on having what we call
the "linuxulator" installed. It'll do this for you but you may have to
enter a line in your /boot/loader.conf to ensure the linux.ko kernel module
gets loaded every time at boot. You will usually see some more instructions
at the end if you need to do anything special. Also, be aware that the
nvidia driver is only currently working with i386, _not_ amd64.

Even if only using packages you should _still_ update the ports tree, as the
package system relies on it for dependency tracking as well.
 
> I hate to bother any further but have one thing to clarify about building
> attempts - when building anything, if that's ok. I only have a basic
> understanding of C so far, and can't really tell how critical warnings are
> - such as undefined this and that, defined but not used...etc, when
> building a
> port.  should i stop those and see how i should fix them or let them
> proceed as long as they're not errors? I can live with my current system
> for now, but have a few things i need to update eventually.
> 

When you use ports and compile stuff, you may see all manners of warnings,
errors, and sundry garbage spewing forth from the compiler. Most of this,
most of the time, is benign and not something to get overly concerned about
as it is fairly normal. The exception is if the build errors out and
completely quits, and there is an error sequence that will indicate
whereabouts it bombed. Sometimes ports do get broken and need fixing, but
most ports have a person who maintains them. If/when many people see the
same error someone usually notifies the port maintainer and he/she then
looks into fixing it.

But generally speaking, if the build completes and runs without segfaulting
just ignore what you may have seen scrolling by while building. Most of the
time it's just "noise".  :-)

-Mike
 


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

Re: I can't make world without the "games" group?

[[EMAIL PROTECTED]]

2008/8/2 Redd Vinylene <[EMAIL PROTECTED]>:
> Adding WITHOUT_GAMES="YES" to /etc/src.conf most certainly didn't work.
>
> Why does FreeBSD pack so much, pardon my language, bullshit anyway?
>

There can be, and has been, said the same about nearly every
part of the base system, at some point.

Perhaps these few utilities amuse one or two people, though
I suppose a "professional" operating system wouldn't include
anything like minesweeper or freecell . . .


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

Re: I can't make world without the "games" group?

[Mark Linimon]

On Sat, Aug 02, 2008 at 06:48:27PM +0200, Redd Vinylene wrote:
> Why does FreeBSD pack so much, pardon my language, bullshit anyway?

Because no one has done the necessary QA work to factor things out
and make them work.

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

Re: jail_box_ip=""

[Redd Vinylene]

Here's what I got so far: http://pastie.org/246189

And this is just wishful thinking I guess: http://pastie.org/246190

On Sat, Aug 2, 2008 at 7:08 PM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
> Hey, I got a couple of hundred IPs, is there an easy way to add them
> all to jail_box_ip="ip1,ip2,ip3" without making like the longest line
> ever?
>
> Like this?
>
> jail_box_ip="66.252.2.4,\
> 66.252.2.5,\
> 66.252.2.6,\
>
> Unfortunately that doesn't look too good.
>
> Nor does:
>
> export x=$(cat ips);export jail_ips=''; for ip in $x; do export
> jail_ips="$jail_ips,$ip"; done; export jail_ips=$(echo $jail_ips | sed
> s/,$/''/ | sed s/^,//);
>
> Is there a more beautiful alternative?
>
> Thanks!
>



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

Re: pxeboot

[davidcollins001]

Hi,

Thanks both for your replies. I think the top of that article applies
to me, in that I am trying to do something that I don't fully
understand!

I am fairly confident that I have the DHCP and TFTP setup correctly in
as much as I get pxeboot on the booted machine (and I have gotten it
working in linux).

So here is my understandin at the moment: At boot time the netcard
does its dhcp thing, gets an ip address pulls the "filename" from the
tftp server (which is pxeboot). At this point pxeboot executes and
acts much like loader. It mounts the nfs server at "option root-path"
specified in the dhcpd.conf on  the server, then loads boot/loader.rc
from the mounted drive, then all the lovelies of BSD loader begin.

I think that now I have this in my head straight I am able to get it
working. I tried the following in my boot/loader.rc. The main reason
for the oddities in my last email was that I didn't understand what
the .rc and .conf files did, the 3 read lines were mainly debugging
and trying to understand what was happening.

> echo Loading /boot/loader.rc
>
> set mfsroot_type="mfs_root"
> set mfsroot_name="/mfsroot
> set vfs.root.mountfrom="ufs:/dev/md0c"
>
> load -t mfs_root /mfsroot
>
> autoboot 5

At this point I still get the compter rebooting (I have gunzipped
mfsroot to avoid the bug with it).. I am not convinced that I have
loader.rc setup correctly. Where are the filenames in it relative to,
is it relative to the nfs mount point too, in which case should the
file be /boot/mfsroot? Is it possible to see an example of someones
loader.rc that works?

I have also tried tftp only pxeboot by making pxeboot with "make
-DLOADER_TFTP_SUPPORT=YES" but I don't think that I had the files
correctly located. Am I correct in thinking that in this case it will
search for boot/loader.rc relative to the tftp server path?

I found a book in my library that had a section on pxe booting, I was
sad to see that although they had described setting up the dhcp and
tftp servers they completely glossed over the actual setup of and how
to use pxeboot!

Thanks for help, it is greatly appreciated.
David
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

jail_box_ip=""

[Redd Vinylene]

Hey, I got a couple of hundred IPs, is there an easy way to add them
all to jail_box_ip="ip1,ip2,ip3" without making like the longest line
ever?

Like this?

jail_box_ip="66.252.2.4,\
66.252.2.5,\
66.252.2.6,\

Unfortunately that doesn't look too good.

Nor does:

export x=$(cat ips);export jail_ips=''; for ip in $x; do export
jail_ips="$jail_ips,$ip"; done; export jail_ips=$(echo $jail_ips | sed
s/,$/''/ | sed s/^,//);

Is there a more beautiful alternative?

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

Re: I can't make world without the "games" group?

[Redd Vinylene]

Adding WITHOUT_GAMES="YES" to /etc/src.conf most certainly didn't work.

Why does FreeBSD pack so much, pardon my language, bullshit anyway?

Yes, one or two (out of one or two million) might need it, but can't
we make it available to them in some other way? As a module or a port
or something?

Thanks!

On Fri, Aug 1, 2008 at 11:47 PM, darko gavrilovic
<[EMAIL PROTECTED]> wrote:
> On Fri, Aug 1, 2008 at 11:31 AM, Redd Vinylene <[EMAIL PROTECTED]> wrote:
>> Hello!
>>
>> Why can't I make world without the "games" group? I run a serious
>> server, not a kindergarten ;)
>>
>
> .. but you will miss out on all the murphy's law quotes.. one of the
> few enjoyments a sysadmin has left in this world.
>
>
>
>
>
> --
> regards,
> dg
>
> "..but the more you use clever tricks, the less support you'll get
> ..." -- M.W.Lucas
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: gemeral questions (noobish)

[mcassar]

On Saturday 02 August 2008 17:32:53 RW wrote:
> On Sat, 2 Aug 2008 15:50:48 +0200
>
> mcassar <[EMAIL PROTECTED]> wrote:
> > firstly - i have installed kde3 and xfce4 from packages (like most of
> > it -> xorg,etc) and have tried updates before with different results.
> > i don't mind messing things up, as long as i can somehow surf or
> > check mails - but would like to do a *proper* update.
> >
> > firstly, are [freebsd-update] and [cvsup stable src.all] necessary
> > before installing anything from ports?
>
> freebsd-update does a binary update to the base system, csup of src-all
> is for fetching source to rebuild the base system. You can build ports
> and base independently
>
> BTW you should be using csup (in the base system), not cvsup. cvsup was
> written in modulo2, csup is a rewrite in C with fewer dependencies
>
> Also if you are new to FreeBSD, you should probably not be using a
> stable branch, these are stable development branches. Consider using a
> security branch like RELENG_7_0, and later moving to RELENG_7_1 and so
> on.
>
> > and are ports considered
> > stable or current? or are they automatically matched to the installed
> > version?
>
> There's only one version of ports, the builds automatically adapt to
> your basesystem version.
>
> > also, do portsnap and cvsup ports do the same thing? i've tried cvsup
> > exactly after portsnap and it still seems to edit/update the ports
> > tree.
>
> They're more or less the same. portsnap is faster, but it's for ports
> only and is less flexible.
>
> > why i'm confused is that i get alot of warnings when many ports try
> > to build, and many hiccups in apps once they are installed, and i
> > don't know which way to go --- gcc manual and fixing my environment,
> > build options, etc,, or if it still something in the actual ports?
>
> You don't need to set much, if anything. Read the entries
> in /usr/ports/UPDATING before doing an upgrade. Most build problems
> will fix themselves within a day or two if you resync the ports tree.
>
>
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"

damn, thanks - I had mistaken stable to be what is release; i had come across 
the difference at some point but didn't realise when i tried cvsup (which i 
also mistook to be more recent than csup).

I only tried csup on ports once and wasn't too sure i should since the 
handbook or somewhere mentioned the ports tree should be empty the first time 
you run it; and got the impression you should only use either or (csup vs 
portsnap).

anyhow i think that only my nvidia driver instructions mentioned it relies on 
what i think are system sources (kernel related - if i'm not mistaken) - but 
i haven't touched that yet.

I hate to bother any further but have one thing to clarify about building 
attempts - when building anything, if that's ok. I only have a basic 
understanding of C so far, and can't really tell how critical warnings are - 
such as undefined this and that, defined but not used...etc, when building a 
port.  should i stop those and see how i should fix them or let them proceed 
as long as they're not errors? I can live with my current system for now, but 
have a few things i need to update eventually.

again, many thanks for the reply and clarifying.

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

Re: gemeral questions (noobish)

[RW]

On Sat, 2 Aug 2008 15:50:48 +0200
mcassar <[EMAIL PROTECTED]> wrote:


> firstly - i have installed kde3 and xfce4 from packages (like most of
> it -> xorg,etc) and have tried updates before with different results.
> i don't mind messing things up, as long as i can somehow surf or
> check mails - but would like to do a *proper* update.
> 
> firstly, are [freebsd-update] and [cvsup stable src.all] necessary
> before installing anything from ports? 

freebsd-update does a binary update to the base system, csup of src-all
is for fetching source to rebuild the base system. You can build ports
and base independently

BTW you should be using csup (in the base system), not cvsup. cvsup was
written in modulo2, csup is a rewrite in C with fewer dependencies

Also if you are new to FreeBSD, you should probably not be using a
stable branch, these are stable development branches. Consider using a
security branch like RELENG_7_0, and later moving to RELENG_7_1 and so
on.

> and are ports considered
> stable or current? or are they automatically matched to the installed
> version?

There's only one version of ports, the builds automatically adapt to
your basesystem version.

> also, do portsnap and cvsup ports do the same thing? i've tried cvsup
> exactly after portsnap and it still seems to edit/update the ports
> tree.

They're more or less the same. portsnap is faster, but it's for ports
only and is less flexible.

> why i'm confused is that i get alot of warnings when many ports try
> to build, and many hiccups in apps once they are installed, and i
> don't know which way to go --- gcc manual and fixing my environment,
> build options, etc,, or if it still something in the actual ports?

You don't need to set much, if anything. Read the entries
in /usr/ports/UPDATING before doing an upgrade. Most build problems
will fix themselves within a day or two if you resync the ports tree.

 

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

gemeral questions (noobish)

[mcassar]

hi,
i have a new freebsd 7-release installed and very new to anything outside 
windows and may have jumped into the deep end to soon- but freebsd is the 
only thing i liked and want to keep, mess around with and hopefully learn 
something; so all i know is what i got from the handbook and the net this 
past month, and hope i can ask a few quick questions where i am a bit unclear 
(only looking for short answers and some diretion if possible).

firstly - i have installed kde3 and xfce4 from packages (like most of it -> 
xorg,etc) and have tried updates before with different results. i don't mind 
messing things up, as long as i can somehow surf or check mails - but would 
like to do a *proper* update.

firstly, are [freebsd-update] and [cvsup stable src.all] necessary before 
installing anything from ports? and are ports considered stable or current? 
or are they automatically matched to the installed version?

also, do portsnap and cvsup ports do the same thing? i've tried cvsup exactly 
after portsnap and it still seems to edit/update the ports tree.

why i'm confused is that i get alot of warnings when many ports try to build, 
and many hiccups in apps once they are installed, and i don't know which way 
to go --- gcc manual and fixing my environment, build options, etc,, or if it 
still something in the actual ports?

i'll stop there, sorry for this, but the thing is that between an install off 
the offical discs and updates to date, i easily have 350+ packages to do at 
once and have been jumping around from manual to manual still unsure where to 
start.

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

Re: get periodic to not scan a partition

[RW]

On Sat, 2 Aug 2008 08:30:20 -0400
"B. Cook" <[EMAIL PROTECTED]> wrote:

> 
> On Aug 2, 2008, at 8:19 AM, RW wrote:
> 
> > On Sat, 2 Aug 2008 06:22:17 -0400
> > "B. Cook" <[EMAIL PROTECTED]> wrote:
> >
> >> hello all,
> >>
> >> I have a machine doing backups with backuppc (excellent program
> >> btw) and I have them being stored in /exports
> >>
> >> /dev/ad4s1h 57G 31G 21G60%/exports
> >>
> >> /dev/ad4s1h on /exports (ufs, local, noatime, soft-updates)
> >>
> >> it is now almost 6:20 am and periodic has been running since 3:01..
> >> and it will complete in another 4 hours..
> >>
> >> root 92866  0.6  0.1  3064  1488  ??  D 3:01AM   1:00.93
> >> find / exports -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm
> >> -o+x ) ( - perm -u+s -or -perm -g+s ) -print0
> >>
> >> is there something I can do to get periodic to not look
> >> in /exports?
> >
> > The above search is looking for setuid binaries, if you
> > mount /exports as noexec and/or nosuid then it wont get searched.
> >
> 
> I will see what happens when I do that.. as I remember it did  
> something to break the building of world and I think port building
> as well..
> 
> this /exports also holds /usr/obj /usr/src and /usr/ports they are  
> symlinks to here.

In that case I'd try disabling the search with
daily_status_security_chksetuid_enable=no in periodic.conf, and
possibly putting a modified version in /usr/local/etc/periodic/security.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: X won't start up; "No matching Device section"

[Helge Rohde]

On Saturday 02 August 2008 02:30:22 David Gurvich wrote:
> Have you loaded all the kernel modules you need and installed
> xf86-video-chips?

I am not aware of any kernel modules that i would have to load explicitely. 
And, yes, as indicated by the Xorg.log snippet, the chips driver is present.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: get periodic to not scan a partition

[B. Cook]

On Aug 2, 2008, at 8:19 AM, RW wrote:


On Sat, 2 Aug 2008 06:22:17 -0400
"B. Cook" <[EMAIL PROTECTED]> wrote:


hello all,

I have a machine doing backups with backuppc (excellent program btw)
and I have them being stored in /exports

/dev/ad4s1h 57G 31G 21G60%/exports

/dev/ad4s1h on /exports (ufs, local, noatime, soft-updates)

it is now almost 6:20 am and periodic has been running since 3:01..
and it will complete in another 4 hours..

root 92866  0.6  0.1  3064  1488  ??  D 3:01AM   1:00.93
find / exports -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm
-o+x ) ( - perm -u+s -or -perm -g+s ) -print0

is there something I can do to get periodic to not look in /exports?


The above search is looking for setuid binaries, if you mount /exports
as noexec and/or nosuid then it wont get searched.



I will see what happens when I do that.. as I remember it did  
something to break the building of world and I think port building as  
well..


this /exports also holds /usr/obj /usr/src and /usr/ports they are  
symlinks to here.


Again from what I remember having nosuid and/or noexec on /usr/obj and/ 
or /usr/ports was a 'problem' as well..





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

Re: get periodic to not scan a partition

[RW]

On Sat, 2 Aug 2008 06:22:17 -0400
"B. Cook" <[EMAIL PROTECTED]> wrote:

> hello all,
> 
> I have a machine doing backups with backuppc (excellent program btw)  
> and I have them being stored in /exports
> 
> /dev/ad4s1h 57G 31G 21G60%/exports
> 
> /dev/ad4s1h on /exports (ufs, local, noatime, soft-updates)
> 
> it is now almost 6:20 am and periodic has been running since 3:01..  
> and it will complete in another 4 hours..
> 
> root 92866  0.6  0.1  3064  1488  ??  D 3:01AM   1:00.93
> find / exports -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm
> -o+x ) ( - perm -u+s -or -perm -g+s ) -print0
> 
> is there something I can do to get periodic to not look in /exports?

The above search is looking for setuid binaries, if you mount /exports
as noexec and/or nosuid then it wont get searched. 

You may also need to curtail the locate search as someone already
mentioned, although that's only weekly and it only searches
directories that the user "nobody" can read. 

7 hours does seem a very long time though, these searches only take a
few minutes for 1.3TB on my desktop machine, and it's several years old.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: get periodic to not scan a partition

[Christian Hiris]

On Saturday 02 August 2008, B. Cook wrote:
> hello all,
>
> I have a machine doing backups with backuppc (excellent program btw)
> and I have them being stored in /exports
>
> /dev/ad4s1h 57G 31G 21G60%/exports
>
> /dev/ad4s1h on /exports (ufs, local, noatime, soft-updates)
>
> it is now almost 6:20 am and periodic has been running since 3:01..
> and it will complete in another 4 hours..
>
> root 92866  0.6  0.1  3064  1488  ??  D 3:01AM   1:00.93 find /
> exports -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm -o+x ) ( -
> perm -u+s -or -perm -g+s ) -print0
>
> is there something I can do to get periodic to not look in /exports?
>
> I have the BackupPC 'backup folders' and symlinks to /usr/src /usr/obj
> and /usr/ports.
>
> Thanks in advance
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
Set up PRUNEPATHS in /etc/locate.rc.

Cheers
ch

-- 
Christian Hiris <[EMAIL PROTECTED]> | OpenPGP KeyID 0x1A9BE943
OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

get periodic to not scan a partition

[B. Cook]

hello all,

I have a machine doing backups with backuppc (excellent program btw)  
and I have them being stored in /exports


/dev/ad4s1h 57G 31G 21G60%/exports

/dev/ad4s1h on /exports (ufs, local, noatime, soft-updates)

it is now almost 6:20 am and periodic has been running since 3:01..  
and it will complete in another 4 hours..


root 92866  0.6  0.1  3064  1488  ??  D 3:01AM   1:00.93 find / 
exports -xdev -type f ( -perm -u+x -or -perm -g+x -or -perm -o+x ) ( - 
perm -u+s -or -perm -g+s ) -print0


is there something I can do to get periodic to not look in /exports?

I have the BackupPC 'backup folders' and symlinks to /usr/src /usr/obj  
and /usr/ports.


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

Re: mount_msdosfs usb flash stick

[Wojciech Puchar]

da0s1


On Sat, 2 Aug 2008, joeb wrote:


On 6.2 release of FBSD trying to mount a usb flash memory stick. The stick
has a msdos file system on it and has been loaded with files using windows
xp. When I plug the stick into my FBSD box I get console msg about da0
device as usb flash memory stick. All looks good at this point. When is
issue this command,  mount_msdosfs /dev/da0 /mnt  I get this error msg  '
invalid argument' .  Also tried this format of the command with same
results.mount -t msdos /dev/da0 /mnt (note typing error on msdos in
first post. Sorry)


What am I doing wrong here?

___
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: "no toe capability on..."

[Nejc Škoberne]

Hey,


no toe capability on 0xc2e66400


Looks like this is was fixed 7/31/2008:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/tcp_offload.c.diff?r1=text&tr1=1.4.2.1&r2=text&tr2=1.4.2.2

That was fast!

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