Re: want to install free bsd

[Manolis Kiagias]

Brian Guest wrote:

Dear [EMAIL PROTECTED]
   
  I would like to install freebsd 6.2 or 6.0 on my pentium three PC computer.

  At this moment my pentium three computer has XP installed on it i do not know
  which files from the freebsd website to download and write to a CDRW orCDR
  could you direct me to the wright files and walk me through the process of 
installing
  free bsd 
   
  thank you 
  brn_gst


   
-
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. 
___

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


  
Look at this list to find a mirror near your location, you will get a 
better download speed:


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

Download the i386 version iso image:

6.2-RELEASE-i386-disc1.iso

Burn it on CD using the "Create CD from ISO image" or similar option on 
your windows CD recording program.

Adjust your BIOS to boot from CD, then reboot

Read and follow the FreeBSD handbook carefully, particularly the 
installation chapter:


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

If you have no previous Unix or Linux experience, be patient and 
prepared to learn a lot of new stuff.


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

Re: 6.2 iso images

[Manolis Kiagias]

hal wrote:
> On freebsd.org the date of the ISO images is
> 1-12-2007.  There have been several updates
> since then.  Is there a repository of ISO images
> that are kept current?
>
> hal
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>
>
Maybe you would like to download a 6-STABLE ISO image?

Have a look at

ftp://ftp.freebsd.org/pub/FreeBSD/snapshots and in particular

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

Re: 6.2 iso images

[Manolis Kiagias]

hal wrote:
>
> On Oct  1, 2007, at Monday, Oct1, 2007 2:03 PM, Manolis Kiagias wrote:
>
>>>
>> Maybe you would like to download a 6-STABLE ISO image?
>>
>> Have a look at
>>
>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots and in particular
>>
>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200709
>
> BTW are the snapshots production worthy?
>
> hal
> ___
>
Although the most official response would probably be "only use RELEASE
on mission critical servers", I would say they are. A lot of people are
running STABLE with great results. 6.2 is a mature release now and
STABLE reflects this quality 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: security patches and release number question

[Manolis Kiagias]

Duane Winner wrote:
> Hi,
>
> Question about patch numbers and applying patches:
>
> Last night, I got the openssl security advisory, and this morning am
> starting to patch my servers.
>
> I've always just done a "make build world; make build kernel; make
> install kernel; make install world" when I've need to patch.
>
> Today, however, I thought I would just try to do the patch on the
> openssl libs as described in the advisory. I think it worked just
> fine, but my question is this:
>
> How do I keep track of which systems I've patched if I just do a
> "patch < patchfile" instead of the whole world/kernel thing?
>
> uname -an still shows 6.2-RELEASE-p7 instead of "p8"; I use this to
> keep track of which servers I've patched and which I haven't.
>
> Is there a way to handle this?
>
> Thanks,
> DW
>
>
This seems to be a common question among the "freebsd-update" utility
users as well (like myself :)).
The short answer is, the p-something number changes only if you
recompile the kernel after such an update.
So, if you just need this change to be reflected in your uname -a
output, just make buildkernel / make installkernel

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

Re: xmms crashing at startup

[Manolis Kiagias]

Robert Marella wrote:
> On Sat, 22 Sep 2007 09:46:36 -0400
> Robert Huff <[EMAIL PROTECTED]> wrote:
>
>   
>> Manolis Kiagias writes:
>>
>> 
>>>  I believe this started after upgrading to Xorg-7.3:
>>>  
>>>  [EMAIL PROTECTED]:~$ xmms
>>>  Gdk-ERROR **: BadMatch (invalid parameter attributes)
>>>serial 1492 error_code 8 request_code 72 minor_code 0
>>>  Gdk-ERROR **: BadMatch (invalid parameter attributes)
>>>serial 1493 error_code 8 request_code 72 minor_code 0
>>>  
>>>  I tried uninstalling and recompiling the port, nothing changed.
>>>  I also can't find anything meaningful about this in Google. Any
>>> ideas?
>>>   
>>  Same here, with slight variation:
>>
>> Gdk-ERROR **: BadMatch (invalid parameter attributes)
>>   serial 2435 error_code 8 request_code 72 minor_code 0
>>
>>
>>  Robert Huff
>> 
>
> Has anything been done to correct this? I am still experiencing this on
> two separate machines. One of which is running i386 and the other
> amd64. Both are running Stable and xorg 7.3
>
> [EMAIL PROTECTED] ~> xmms
> Gdk-ERROR **: BadMatch (invalid parameter attributes)
>   serial 1463 error_code 8 request_code 72 minor_code 0
>
> All ports are up to date as of today.
>
> Thanks
>
> Robert
>
>   
Still crashing here as well. Either xmms or xorg need an update, and I
can't seem to find any workaround either.

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

Re: C++ Compiler On FreeBSD

[Manolis Kiagias]

James Jeffery wrote:
> Evening to you all (or morning in some parts of the world).
>
> Im learning C++ from Sams Teach Yourself C++, now many will call this
> a dumb method, and the books pointless and stupid, but i have no knowledge
> of any lower level languages, so i do need to be spoon fed the basics.
>
> Im using Borland C++ compiler on XP and was wondering what compilers
> there are for FreeBSD that would allow me to compile and execute some
> of the examples i will practise from the book.
>
> Also if anyone wants to recommend any other books on C++ feel free. We
> are learning VB at college at the moment, i like it, but its not machine
> portable
> and i dont like the whole drag and drop way of creating a program, seems
> like
> cheating.
>
> Thanks for reading
>
> James
>
>   

Are you using the Jesse Liberty's book? (the 21 days thing ? :) )
This is actually quite good for a beginner in the language - just don't
try to finish it in 21 days...

On to your question, FreeBSD provides (and is actually compiled itself
by) the gcc compiler which will happily compile C and C++ programs. You
may as well wish to install a GUI frontend (like kdevelop), but this is
probably an overkill for the simple examples in the book.

P.S. Visual Basic (at least up to version 6) is the best and easiest way
to write the worst, most unreadable code... ever. Even worse, it may
actually work...sort of.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Marvel NFE driver in 6 CURRENT

[Manolis Kiagias]

stan wrote:
> I'm building a new machine which (I beleive) needs the NFE driver fr the
> onboard NIC's. 
>
> It appears that there is a third part (as in not in tree) driver for this
> chipset, Why is this not in 6.2 CURRENT? Are the issues with it?
>
>   

I am using this driver in 6.2-RELEASE:

http://www.f.csce.kyushu-u.ac.jp/~shigeaki//software/freebsd-nfe.html

I have no idea if it has been merged in STABLE or CURRENT, but it has
been running for about 50 days on 6.2-RELEASE/amd64 and had no problems
with it.

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

Re: freebsd-update port uname/internal patch level mismatch

[Manolis Kiagias]

Vinny wrote:
> Hi,
>
> I noticed that using freebsd-update on a freshly installed
> 6.2-RELEASE system yielded the following mismatch:
>
> $ uname -vp
> FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007
>  [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP  i386
>
> The results of running a freebsd-update fetch give:
>
> zcnew# freebsd-update fetch
> Looking up update.FreeBSD.org mirrors... 1 mirrors found.
> Fetching metadata signature from update1.FreeBSD.org... done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
>
> No updates needed to update system to 6.2-RELEASE-p8.
>
> So uname says -p4 and freebsd-update says -p8
>
> I know -p8 is correct.  The kernel was last patched in -p4 so
> maybe the uname information isn't updated if the kernel
> isn't updated...?
>

Exactly. But if you are willing to rebuild the kernel yourself (this is
not a difficult process) you will get -p8 in uname too.

> If there is something I'm doing wrong, please let me know.
>
> Thank you.
>
> Vinny

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

Re: Copying CD tracks

[Manolis Kiagias]

Rem P Roberti wrote:
> Is it possible to copy all of the audio tracks on a cd to a directory at
> one time.  The handbook gives instructions for copying one at a time,
> but there must be a way to do it all at once.
>
> Rem
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>   
In my ripping / ogg conversion script I use the following:

cdda2wav -D /dev/acd0 -B -L1 -cddbp-server=freedb.freedb.org
-cddbp-port=8880

Last two options will also get you the track titles. -B means bulk
copying (all tracks into separate files).

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

Re: Following directions doesn't seem to work: Adding users in NIS

[Manolis Kiagias]

David Benfell wrote:
> Hello all,
>
> Where are there working directions for adding users under NIS?
>
> The instructions in the FreeBSD handbook don't seem to result in
> added users being propagated out to slaves.  And the failure is
> silent, so I have no idea what I'm really supposed to be doing
> to make this work.
>
> All I know is that added users end up in the main /etc/passwd
> and /etc/master.passwd; the -Y option to pw seems to change nothing
> other than to consume time "updating" (but I don't know what, since
> the changes I'm looking for don't appear) various maps and "pushing"
> the maps.
>
> And, having evidently done the *wrong* thing, how do I fix the
> added users so they now appear in NIS?
>
> Thanks!
>
>   
The following comes from the handbook and works for me:

copy your master.passwd to /var/yp, i.e:

cp /etc/master.passwd /var/yp/master.passwd

Edit the copy of master.passwd and exclude all "irrelevant" accounts
(root,servers and so on)

Then run:

ypinit -m your-nis.domain

My real problem with nis is the fact the freebsd maps are not compatible
with linux clients, and I can't seem to get the Makefile right...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Following directions doesn't seem to work: Adding users in NIS

[Manolis Kiagias]

David Benfell wrote:
> On Mon, 15 Oct 2007 18:57:27 +0300, Manolis Kiagias wrote:
>   
>>>   
>>>   
>> The following comes from the handbook and works for me:
>>
>> copy your master.passwd to /var/yp, i.e:
>>
>> cp /etc/master.passwd /var/yp/master.passwd
>>
>> Edit the copy of master.passwd and exclude all "irrelevant" accounts
>> (root,servers and so on)
>>
>> Then run:
>>
>> ypinit -m your-nis.domain
>>
>> 
> So the message I'm getting here is that the procedure used to initially
> set up NIS is the same as that used to update NIS.  Further down that page,
> it claims that pw can be used to add users to an existing scheme
Reinitializing the maps like this should cause no problem, and you will
get all the new accounts.
I have not tried the update procedure from the handbook, I got stuck
with the linux client.

> :
>
> 
> 27.4.8 Important Things to Remember
>
> There are still a couple of things that you will need to do differently now 
> that you are in an NIS environment.
>
> *
>
>   Every time you wish to add a user to the lab, you must add it to the 
> master NIS server only, and you must remember to rebuild the NIS maps. If you 
> forget to do this, the new user will not be able to login anywhere except on 
> the NIS master. For example, if we needed to add a new user jsmith to the 
> lab, we would:
>
>   # pw useradd jsmith
>   # cd /var/yp
>   # make test-domain
>
>   You could also run adduser jsmith instead of pw useradd jsmith.
> 
>
>   
This looks more or less similar to Linux procedures ( usually make -C
/var/yp), but as I said I have not tried this on FreeBSD.
>> My real problem with nis is the fact the freebsd maps are not compatible
>> with linux clients, and I can't seem to get the Makefile right...
>> 
>
> Ouch!  I'm ultimately planning to add a Linux client.  In theory, I can get
> by with just NFS for this particular application, but it would be better to
> have NIS as well.
>
>
>
>   
Well I can tell you with certainty, it is not compatible out of the box,
and I have not managed to make it work (though I must admit I did not
put a lot of effort into this). Seems the exported master.passwd map
needs a filename change + internal changes, thus the NIS Makefile needs
to be modified. On the Linux side, the users are visible (e.g. you can
run id  and the user is there) but they cannot login.
If you Google "FreeBSD NIS Server Linux Clients" you will get some
patches for the NIS Makefile to make it Linux compatible. I was not
however successful with this. If you do try it and get it to work,
please report back.


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

Re: NIS interoperability with Linux, was Re: Following directions doesn't seem to work: Adding users in NIS

[Manolis Kiagias]

Olivier Nicole wrote:
>> Linux doesn't normally use master.passwd.  If I recall correctly, it
>> uses /etc/shadow instead (but I don't have such a box at hand right now
>> to check).  And yes, the internal format is different (and, again, I don't
>> remember details).
>> 
>
> If I am not wrong, NIS does not know anything about master.passwd or
> shadow, it has only passwd.byname passwd.byuid as password maps, both
> maps including password in them.
>
> Olivier
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>   
You are probably right, I don't remember the exact files right now, the
thing is the maps are not linux compatible, so if anyone has a NIS
Makefile for this, I'd be glad to get a copy. I already tried a patch I
found but was not successful.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [OT] proper editor

[Manolis Kiagias]

Byung-Hee HWANG wrote:
> Hi there, I'm beginner.
>
> Please recommend for proper editor so that ...
> I want to practice *Python* under best environment ...
>
> vim, emacs, gedit, or notepad.exe, ... 
>
> If you give me good advice about that, I'll study very hard ...
>
> So which one is best editor? ...
>
>   
There is no such thing as a "best" editor. Which one you know better NOW?
If the goal is to study Python (assuming no previous experience), go
along with the easiest for you. For starters, if you are using a  GUI,
go with Python's own IDLE environment. It is not "advanced", but neither
are you at this point. And it does have some advantages (like immediate
execution of commands to try out things).
Spending time learning a complex editor like vi or emacs, will certainly
pay up in the long run though.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: NIS interoperability with Linux, was Re: Following directions doesn't seem to work: Adding users in NIS

[Manolis Kiagias]

Lowell Gilbert wrote:
> Manolis Kiagias <[EMAIL PROTECTED]> writes:
>
>   
>> Olivier Nicole wrote:
>> 
>>>> Linux doesn't normally use master.passwd.  If I recall correctly, it
>>>> uses /etc/shadow instead (but I don't have such a box at hand right now
>>>> to check).  And yes, the internal format is different (and, again, I don't
>>>> remember details).
>>>> 
>>>> 
>>> If I am not wrong, NIS does not know anything about master.passwd or
>>> shadow, it has only passwd.byname passwd.byuid as password maps, both
>>> maps including password in them.
>>>
>>> Olivier
>>>   
>
>   
>> You are probably right, I don't remember the exact files right now, the
>> thing is the maps are not linux compatible, so if anyone has a NIS
>> Makefile for this, I'd be glad to get a copy. I already tried a patch I
>> found but was not successful.
>> 
>
> Don't patch anything.  Just edit /var/yp/Makefile to remove the
> comment character from the UNSECURE line, rebuild, and you're done.  
>
> This is fully explained inline in that file, as well as in the manual
> for ypserv(8).
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>   
I've read this the first time I tried and decided not to go with it.
The manual says:
"If you plan to use a FreeBSD system to serve non-FreeBSD
clients that have no support for password shadowing (which is
most of them), you will have to disable the password shadowing
entirely by uncommenting the UNSECURE=True entry in
 /var/yp/Makefile."

Linux certainly uses password shadowing, and I can see in my debian
server maps passwd.byname and shadow.byname files
If I perform ypcat passwd.byname from a client I get the standard passwd
file with no passwords (exactly like /etc/passwd)
The encrypted passwords are in the shadow.byname map.

Now, if I understand correctly, the above solution would put the
passwords in the passwd.byname map, thus making the system less secure,
where in fact I should be able to make FreeBSD export a shadow.byname
map that would be compatible with Linux.
Am I missing something here / are my assumptions wrong?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [OT] proper editor

[Manolis Kiagias]

Byung-Hee HWANG wrote:
> On Tue, 2007-10-16 at 08:47 +0300, Manolis Kiagias wrote:
>   
>> Byung-Hee HWANG wrote:
>> 
>>> Hi there, I'm beginner.
>>>
>>> Please recommend for proper editor so that ...
>>> I want to practice *Python* under best environment ...
>>>
>>> vim, emacs, gedit, or notepad.exe, ... 
>>>
>>> If you give me good advice about that, I'll study very hard ...
>>>
>>> So which one is best editor? ...
>>>
>>>   
>>>   
>> There is no such thing as a "best" editor. Which one you know better NOW?
>> If the goal is to study Python (assuming no previous experience), go
>> along with the easiest for you. For starters, if you are using a  GUI,
>> go with Python's own IDLE environment. It is not "advanced", but neither
>> are you at this point. And it does have some advantages (like immediate
>> execution of commands to try out things).
>> Spending time learning a complex editor like vi or emacs, will certainly
>> pay up in the long run though.
>> 
>
> Nope. I don't care what it costs. I don't care even if I have to learn a
> complex editor for long time ...
>
> To tell truth, I really want to learn Python with a complex editor like
> Emacs. I feel so sorry for I object to your professional opinion;; 
>
>   
:) :) This is not a professional opinion, it is just a way of thinking
that may or may not apply to you in this case (or generally).
You are welcome to start learning both Python and Emacs at the same
time, and delve deep at both. In fact, there are so many editors and
programming languages available in FreeBSD you can spend an entire
lifetime learning. It *is* my exact defintion of *having fun* !
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: NIS interoperability with Linux, was Re: Following directions doesn't seem to work: Adding users in NIS

[Manolis Kiagias]

Lowell Gilbert wrote:
> Manolis Kiagias <[EMAIL PROTECTED]> writes:
>
>   
>> I've read this the first time I tried and decided not to go with it.
>> The manual says:
>> "If you plan to use a FreeBSD system to serve non-FreeBSD
>> clients that have no support for password shadowing (which is
>> most of them), you will have to disable the password shadowing
>> entirely by uncommenting the UNSECURE=True entry in
>>  /var/yp/Makefile."
>>
>> Linux certainly uses password shadowing, and I can see in my debian
>> server maps passwd.byname and shadow.byname files
>> If I perform ypcat passwd.byname from a client I get the standard passwd
>> file with no passwords (exactly like /etc/passwd)
>> The encrypted passwords are in the shadow.byname map.
>>
>> Now, if I understand correctly, the above solution would put the
>> passwords in the passwd.byname map, thus making the system less secure,
>> where in fact I should be able to make FreeBSD export a shadow.byname
>> map that would be compatible with Linux.
>> Am I missing something here / are my assumptions wrong?
>> 
>
> I think you are assuming that Linux uses password shadowing over NIS.
> This is not possible, and no system does it.
>
> The FreeBSD security method in question just forces requests for the
> password maps to come from privileged ports.  This is a very minor
> security method, and other systems don't support it.
>
> Fundamentally, NIS assumes that you trust the machines you are
> serving.  Or at least are willing to let them have the encrypted
> passwords.  No OS can change this; it's not a Linux/FreeBSD issue.  
>
>
>   
I have experimented a bit further with my debian NIS server, and this is
what I found:

>From a NIS client, I can do with my standard user account:

[EMAIL PROTECTED]:~$ ypcat passwd.byname
user1:x:1010:1010:Joe User,,,:/home/user1:/bin/bash

and I get the standard, world-readable password file (the one without
the passwords)
However, the standard user cannot run:

This is the answer:
[EMAIL PROTECTED]:~$ ypcat shadow.byname
No such map shadow.byname. Reason: No such map in server's domain

As root, however:
[EMAIL PROTECTED]:~# ypcat shadow.byname
user1:$1$1233245435435345543545345sfsdfsfdf:13577:0:9:7:::
...

This seems to be consistent with the FreeBSD NIS Server behaviour
described in nis(8) manual page:

" To help prevent this, FreeBSD's NIS server handles the shadow password
 maps (master.passwd.byname and master.passwd.byuid) in a special
way: the
 server will only provide access to these maps in response to requests
 that originate on privileged ports.  Since only the super-user is
allowed
 to bind to a privileged port, the server assumes that all such requests
 come from privileged users.  All other requests are denied:
requests from
 non-privileged ports will receive only an error code from the server."

So, it seems linux handles this the same way. Difference is linux has a
shadow.byname map while FreeBSD has a master.passwd.byname map
(possibly  also internal differences in the files)

Now, if I understand correctly, If I where to add the UNSECURE feature
in the FreeBSD server, I expect the shadow passwords would be inserted
in the passwd.byname map which is world readable and hence a security
issue. (Perhaps I will do this experiment next and let you know of the
outcome)
This is hardly important for my home server scenario, but it would be, 
should I decide to implement a FreeBSD NIS server somewhere else.
Hence,  the best possible solution would be to get a Makefile for the
FreeBSD NIS server that would produce completely Linux compatible maps.



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

Re: NIS interoperability with Linux, was Re: Following directions doesn't seem to work: Adding users in NIS

[Manolis Kiagias]

Lowell Gilbert wrote:
> Manolis Kiagias <[EMAIL PROTECTED]> writes:
>
>   
>> I have experimented a bit further with my debian NIS server, and this is
>> what I found:
>>
>> >From a NIS client, I can do with my standard user account:
>>
>> [EMAIL PROTECTED]:~$ ypcat passwd.byname
>> user1:x:1010:1010:Joe User,,,:/home/user1:/bin/bash
>>
>> and I get the standard, world-readable password file (the one without
>> the passwords)
>> However, the standard user cannot run:
>>
>> This is the answer:
>> [EMAIL PROTECTED]:~$ ypcat shadow.byname
>> No such map shadow.byname. Reason: No such map in server's domain
>>
>> As root, however:
>> [EMAIL PROTECTED]:~# ypcat shadow.byname
>> user1:$1$1233245435435345543545345sfsdfsfdf:13577:0:9:7:::
>> ...
>>
>> This seems to be consistent with the FreeBSD NIS Server behaviour
>> described in nis(8) manual page:
>>
>> " To help prevent this, FreeBSD's NIS server handles the shadow password
>>  maps (master.passwd.byname and master.passwd.byuid) in a special
>> way: the
>>  server will only provide access to these maps in response to requests
>>  that originate on privileged ports.  Since only the super-user is
>> allowed
>>  to bind to a privileged port, the server assumes that all such requests
>>  come from privileged users.  All other requests are denied:
>> requests from
>>  non-privileged ports will receive only an error code from the server."
>>
>> So, it seems linux handles this the same way. Difference is linux has a
>> shadow.byname map while FreeBSD has a master.passwd.byname map
>> (possibly  also internal differences in the files)
>>
>> Now, if I understand correctly, If I where to add the UNSECURE feature
>> in the FreeBSD server, I expect the shadow passwords would be inserted
>> in the passwd.byname map which is world readable and hence a security
>> issue. (Perhaps I will do this experiment next and let you know of the
>> outcome)
>> This is hardly important for my home server scenario, but it would be, 
>> should I decide to implement a FreeBSD NIS server somewhere else.
>> Hence,  the best possible solution would be to get a Makefile for the
>> FreeBSD NIS server that would produce completely Linux compatible maps.
>> 
>
> Hmm.  What you're saying makes sense; unfortunately, I haven't had a
> network configured this way in a while, so I'm rather rusty on the
> details.  It sounds as though this is just a matter of the map names.
> Perhaps you could handle that with nicknames?
>
>   
It is a matter of names, but also there are changes internally in the
file. All can be handled by a modified Makefile, which I hope to be able
to patch
I have a few more urgent "experiments" with the test machine, so this
will have to wait for a while.
> I believe that the master.passwd.byname map is in the same FreeBSD-
> specific format as master.passwd, but that on all systems
> passwd.byname is the standard old format that YP always used.
>   
In fact, in Linux, shadow.byname is the exact same format as
/etc/shadow, so I believe your assumption about master.passwd.byname is
true.
> In most (not all, but most) cases, I don't think it's worth worrying
> about the "secure" modes available, whether you're taking the FreeBSD
> or the Linux map names and formats.  It's based on the assumption that
> someone untrusted can be on your network but can't use low-numbered
> TCP ports.  This is unusual in my experience.
>   
True, and as I said for my home network this is more of an "academic"
exercise.
However considering the (probable) outcome of the UNSECURE line in
Makefile, it would reduce the security of a host to pre-shadow days. The
hashes would be available to anyone, and then someone could discover
john the ripper and give brute force a try.  This is probably something
to keep in mind for more security-conscious environments. Combine it
with the fact it would affect all nis clients and not a single machine,
and you may get a serious security incident.
> Good luck.
> ___
>
>   

Thanks, should I decide to "wrestle" with the Makefile, I will need it :)

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

Re: The kernel source?

[Manolis Kiagias]

Roberth Sjonøy wrote:
> How do I get the kernel source for my kernel? I need it to install the
> nvidia-driver from ports, and is there anything else I need to do to
> make the kernel load the driver at startup?
>
> Regards, Roberth
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>   
Generally speaking, just edit the /etc/X11/xorg.conf and change
reference Driver "nv" to Driver "nvidia"
To load the kernel module, type (as root) kldload nvidia
To make it load automatically at startup, edit /boot/loader.conf and add
line nvidia_load="YES"

If you have not installed the kernel source when the system was
originally installed , you can do it now by running sysinstall again or
use csup as another poster said to download it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: xorg install problem

[Manolis Kiagias]

AN wrote:
> I am trying to install a new system with Gnome and xorg on 7.0 beta 1.
> Here are the steps I have taken:
>
> install 6.2 release
> cvsup to releng_7 as of 10/21/07
> buildworld -sucessful
> installworld -sucessful
> reboot into 7.0 beta
> set packagesite to ft2.nl.freebsd.org
> pkg_add xorg-7.3_1 - fails with message:
>
> 1 package addition failed
> pkg_add of dependency 'xorg-apps-7.3' failed
> 1 package addition failed
>
> I have used this procedure for a long time to install new systems, is
> it broken now because of the status of the new 7.0 release or am I
> having another problem?
>
> What is the proper procedure to get a system with:
>
> fbsd 7.0 beta
> xorg 7.3
> gnome
>
> Any help is appreciated.
>
> TIA
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>
>
It seems you should set PACKAGESITE like:

setenv PACKAGESITE  
ftp://ftp2.nl.freebsd.org/pub/FreeBSD/ports/i386/packages-7-current/Latest/

and use pkg_add -r xorg  (don't specify version numbers if you use Latest)

or

setenv PACKAGESITE  
ftp://ftp2.nl.freebsd.org/pub/FreeBSD/ports/i386/packages-7-current/All/

and use pkg_add -r  xorg-7.3_1.tbz  (the latest at this time)
(use export PACKAGESITE=... if you use bash shell)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Can login using root password, but not remotely with SSH

[Manolis Kiagias]

W. D. wrote:
> Brand new install of FreeBSD 6.2.  Can't log in with PuTTY.
>
> Remote PuTTY:
> Access denied Using keyboard-interactive authentication. 
>
> At computer terminal:
> PAM authentication error for root from 192.168.XXX.XXX 
>
> Any ideas?
>
> Thanks!
>
>
>   
You are probably trying to login as root via ssh. This is not
recommended and is disabled by default.
If you really want to change this, edit /etc/ssh/sshd_login, uncomment
the line PermitRootLogin No and change it to Yes.
Better still, create a normal user account, add it to the wheel group
and use it to ssh to the machine then, use su when needed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: tar Ignoring out-of-order file What Does that Mean?

[Manolis Kiagias]

Martin McCormick wrote:
>   I need to modify the first installation image for a
> headless installation of Freebsd6.2. The file in question is:
>
> 6.2-RELEASE-i386-disc1.iso
>
>   Thanks to a helpful member of the list, I found out that
> tar works on unpacking these images and it mostly does on this
> one, but there is a  complaint I get from tar that I haven't
> found on other images. If I do a
>
> tar tvf 6.2-RELEASE-i386-disc1.iso
>
> Here is what happens while looking at the contents list:
>
> 0   44232 Jan 12  2007 RELNOTES.HTM lr-xr-xr-x  1 0  0
> 0 Jan 12  2007 stand -> /rescue lr-xr-xr-x  1 0  0   0
> Jan 12  2007 sys -> usr/src/systar: Ignoring out-of-order file
>
> -r--r--r--  1 0  0   22916 Jan 12  2007 RELNOTES.TXT
>
> It appears that the entire image unpacks except for the
> ignored file. If one tries the extraction with
>
> tar xf 6.2-RELEASE-i386-disc1.iso
>
> The complaint about the out-of-order file is the only indication
> that anything is wrong.
>
>   In looking at the man page for tar, nothing jumps out at
> me  as to how to end up with the proper file structure that
> mkisofs can put back in to an image to put on a CDROM.
>
>   My thanks for any suggestions as I may be needing to do
> one of these installs in a day or so and it would be nice to
> know that all the image is there.
>
> Martin McCormick WB5AGZ  Stillwater, OK 
> Systems Engineer
> OSU Information Technology Department Network Operations Group
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>   
This is probably not a direct answer to your question, but might be helpful:

ISO images can be mounted as filesystems. In linux you would do
something like mount -o loop /path/to/your.iso   /path/to/mnt
In FreeBSD, you would need to create a memory disk and mount it, i.e.

mdconfig -a -f /path/to/your.iso

(response) md0

mount -t cd9660 /dev/md0  /path/to/mnt

you can then copy the files, and modify what you need.
In order to make boot CDs again,  you would need to use cdrecord with
suitable options, which I don't remember by heart.

BUT, you may look at the instructions on the following page:

http://www.pa.msu.edu/~tigner/bsddvd.html

there are instructions to create a bootable DVD from FreeBSD cdroms, and
I can confirm the procedure works perfectly.

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

Re: fsck gave up on me!

[Manolis Kiagias]

[EMAIL PROTECTED] wrote:
>
>   Hi,
>   I have been using FreeBSD 6.2 for a couple of months now with no major
>   snags.  Until now.  I did a portupgrade this morning and afterwards,
>   when I logged in as a user into Gnome, my desktop was missing most of
>   the programs (Accessories, System Tools, etc.).
>   I rebooted the machine and "that other" terminal screen came up
>   (Single User?) and I was prompted to "run fsck manually" so I did so.
>   Well, fsck gave up on me.  I have no idea what happened or why.  Can
>   anyone help me understand what is going on with my machine and any
>   possible actions I can take to resolve this?
>
>
>   Script started on Fri Nov  2 17:13:22 2007
>   You have mail.
>   root# fscd[Kk
>   ** /dev/ad1s1a (NO WRITE)
>   ** Last Mounted on /
>   ** Root file system
>   ** Phase 1 - Check Blocks and Sizes
>   CANNOT READ BLK: 524544
>   CONTINUE? [yn] y
>   THE FOLLOWING DISK SECTORS COULD NOT BE READ: 524544,
>   ** Phase 2 - Check Pathnames
>   ** Phase 3 - Check Connectivity
>   ** Phase 4 - Check Reference Counts
>   ** Phase 5 - Check Cyl groups
>   CANNOT READ BLK: 524544
>   CONTINUE? [yn] y
>   THE FOLLOWING DISK SECTORS COULD NOT BE READ: 524544,
>   CG 2: BAD MAGIC NUMBER
>   FREE BLK COUNT(S) WRONG IN SUPERBLK
>   SALVAGE? no
>   SUMMARY INFORMATION BAD
>   SALVAGE? no
>   fsck: /dev/ad1s1a: Segmentation fault: 11
>   kirkwood# exit
>   exit
>   Script done on Fri Nov  2 17:14:23 2007
>
>   Thank you in advance,
>   Larry
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>
>
It seems your hard disk is actually giving up on you:

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 524544,
CANNOT READ BLK: 524544

Do you have any manufacturer utilities to run on the disk? This looks
like a surface failure.
Does it make any "weird" noise like trying to read the same area again
and again? This is certainly a sign of disk failure

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

Re: FreeBSD 6.2-release and azalia sound chipset

[Manolis Kiagias]

Nicolas Letellier wrote:
> Hello,
>
> Two questions :
> it's a "binary" module ?
> I don't find the module for azalia. Where is it ?
>
> Thanks
>
> Nicolas
>
> Oliver Herold a écrit :
>> Hi,
>>
>> http://people.freebsd.org/~ariff/BINARY_MODULES/
>>
>> just follow the README.
>>
>> Cheers, Oliver
>>
>>
>> On Mon, Nov 05, 2007 at 10:51:37PM +0100, Nicolas Letellier wrote:
>>  
>>> Hello,
>>>
>>> I  installed 6.2 -release. I have the sound chipset azalia (Intel
>>> 82801H HD Audio).
>>> However, I don't find a module for this chipset. Where I can found
>>> it ? How install it ?
>>>
>>> Thanks you,
>>>
>>> Nicolas
>>>
>>> ___
>>> freebsd-questions@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>> To unsubscribe, send any mail to
>>> "[EMAIL PROTECTED]"
>>> 
>>
>>  

Please see my previous post on this, with complete instructions here:

http://lists.freebsd.org/pipermail/freebsd-questions/2007-August/155261.html

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

Re: List of sites using FreeBSD?

[Manolis Kiagias]

James wrote:

On Tue, 2007-11-06 at 10:15 +0100, Ewald Jenisch wrote:

  

Hi,

Does anybody out there know where I can find a list of sites running
FreeBSD?

I expected it on www.freebsd.org, but couldn't find it (maybe overlooked?)

Thanks in advance for any pointer.

-ewald

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




If you're looking for *large* installs, yahoo! is a freebsd shop, as is
kodak.

If you're looking for *everything*, well, shoot. You're not gonna find
it.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


  
You may also want to browse www.netcraft.com which maintains a list of 
the highest uptimes for lots of servers.

Just look at the top of the list :)


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

Re: Ports with GUI configs

[Manolis Kiagias]

RW wrote:
> On Mon, 12 Nov 2007 08:14:02 -0800
> "Mark D. Foster" <[EMAIL PROTECTED]> wrote:
>
>   
>> Vince wrote:
>> 
>>> Ashley Moran wrote:
>>>   
>>>   
 Hi

 I was just wondering, what is the motivation behind the GUI
 configuration for some ports?  Simply put, they drive me up the
 wall. I've lost count of the number of times I've come back to a
 big install to find it hanging on a config screen.  Possibly I'm
 missing something. 
 
>>> I agree though, I often suffer the same problem, coming back after
>>> a few hours to a build that should have finished to find its
>>> sitting on the first dependency.
>>>   
>>>   
>> Maybe it's been suggested before (in which case I add my vote) but a
>> timeout mechanism would solve this... give the user 10s to provide a
>> keypress else bailout and use the "default" options.
>>
>> 
>
> That would involve standing-over the build for hours or days in case
> you miss a 10-second window - it's just not practical IMO.
>
>
> Setting the menus is pretty easy to script, and you can also set BATCH
> to take the default options
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>   
And in fact you can make all these screens appear before actually compiling:

make config-recursive

(select all wanted options)

make install clean  (no more questions asked)

it is all in the manual: man ports
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Tkinter Libraries Needed

[Manolis Kiagias]

[EMAIL PROTECTED] wrote:

Right. I tried that a while back and forgot I had. This is what I get:



server726# cd /usr/ports/graphics/py-imaging
server726# make install clean
===>  Installing for py24-imaging-1.1.5
===>   py24-imaging-1.1.5 depends on file: 
/usr/local/lib/python2.4/site-packages/_tkinter.so - found
===>   py24-imaging-1.1.5 depends on file: /usr/local/bin/python - found
===>   py24-imaging-1.1.5 depends on shared library: jpeg.9 - found
===>   py24-imaging-1.1.5 depends on shared library: freetype.9 - found
===>   Generating temporary packing list
===>  Checking if graphics/py-imaging already installed
===>   An older version of graphics/py-imaging is already installed 
(py23-imaging-1.1.5)
  You may wish to ``make deinstall'' and install this port again
  by ``make reinstall'' to upgrade it properly.
  If you really wish to overwrite the old port of graphics/py-imaging
  without deleting it first, set the variable "FORCE_PKG_REGISTER"
  in your environment or the "make install" command line.
*** Error code 1

Stop in /usr/ports/graphics/py-imaging.
server726# make deinstall
===>  Deinstalling for graphics/py-imaging
server726# make reinstall
===>  Installing for py24-imaging-1.1.5
===>   py24-imaging-1.1.5 depends on file: 
/usr/local/lib/python2.4/site-packages/_tkinter.so - found
===>   py24-imaging-1.1.5 depends on file: /usr/local/bin/python2.4 - found
===>   py24-imaging-1.1.5 depends on shared library: jpeg.9 - found
===>   py24-imaging-1.1.5 depends on shared library: freetype.9 - found
===>   Generating temporary packing list
===>  Checking if graphics/py-imaging already installed
===>   An older version of graphics/py-imaging is already installed 
(py23-imaging-1.1.5)
  You may wish to ``make deinstall'' and install this port again
  by ``make reinstall'' to upgrade it properly.
  If you really wish to overwrite the old port of graphics/py-imaging
  without deleting it first, set the variable "FORCE_PKG_REGISTER"
  in your environment or the "make install" command line.
*** Error code 1

Stop in /usr/ports/graphics/py-imaging.
*** Error code 1

Stop in /usr/ports/graphics/py-imaging.

Ideas?
TIA,
Tony



/usr/ports/graphics/py-imaging



  

Maybe a long shot, but I would try something in the line of:

pkg_delete -f  "py23-imaging-1.1.5*"

or try

pkg_info | grep py23-imaging

to get the exact name and use it in pkg_delete


the try installing the new port.

Also make sure you have not missed any steps mentioned in 
/usr/ports/UPDATING
I've never had python23, but there are specific steps to follow 
upgrading e.g 2.4 to 2.5

Make sure you have not omitted any of  the relevant steps for your version.

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

Re: Port GUI Config

[Manolis Kiagias]

Donovan R. Palmer wrote:
> I went to compile a programme in the port tree tonight. When I did so, a GUI 
> popped up with different options. No probs.  However, later I decided I 
> wanted to compile it with different options. When I go to compile it, the GUI 
> doesn't pop up any more, so I assume it is using the options I picked out in 
> the first place.  Is there a way to bring back this GUI so I can select 
> different options? TIA
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>
>   
make rmconfig
see also man ports
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: hyperthreading CPU and broken scheduling?

[Manolis Kiagias]

Wojciech Puchar wrote:

i have machune with intel's CPU with hyperthreading.

it is detected right, but only first thread is ever used.

top shows at least 50% idle no matter what i run!

what's wrong?


root@:/usr62/src/sys/amd64/compile/serwer.tensor.gdynia.pl
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.13-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0xf62  Stepping = 2

Features=0xbfebfbff

DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0xe41d,>
  AMD Features=0x20100800
  AMD Features2=0x1
  Logical CPUs per core: 2
real memory  = 1072562176 (1022 MB)
avail memory = 1021456384 (974 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0  irqs 0-23 on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0:  on acpi0
acpi_throttle0:  on cpu0
cpu1:  on acpi0
acpi_throttle1:  on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6


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




To enable hyperthreading, try setting the following in /etc/sysctl.conf:

machdep.hyperthreading_allowed=1

and reboot (or execute sysctl machdep.hyperthreading_allowed=1 by hand).

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

Re: hyperthreading CPU and broken scheduling?

[Manolis Kiagias]

Wojciech Puchar wrote:

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




To enable hyperthreading, try setting the following in /etc/sysctl.conf:

machdep.hyperthreading_allowed=1

and reboot (or execute sysctl machdep.hyperthreading_allowed=1 by hand).

did /etc/rc.d/sysctl start  and works.

quite strange that FreeBSD disables hyperthreading at start.


IIRC there has been some discussion about possible vulnerabilities when 
hyperthreading is enabled. If you google around you will find it.

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

Re: Fw: Can I install Free BSD latest version on my laptop with dual boot?

[Manolis Kiagias]

[EMAIL PROTECTED] wrote:
> In addition to the bellow mail, I giving processor details
>
> AMD Turion? 64 Mobile Technology
>
> 
>
> Hi,
>
> Can I install Free BSD latest version on my laptop with dual boot (Windows 
> Vista + Free BSD), my system configuration details are as follows
>
> HP Compaq Presario V3000z
> RAM - 1.5 GB DDR II 533MHz
> NVIDIA Graphics Card 6150
> NVIDIA Chipset motherboard
> 80GB Fujitsu HDD
>
> Thanks in advance
>
> Cheers
> B.Manikandan
> UK
>
>
>   
Processor should pose no problem. Additionally, I find nvidia chipsets
to be widely compatible with FreeBSD. You don't mention devices like
wireless and ethernet, if you do know the models, you may be able to
find if they are supported in the release notes / hardware compatibility
of FreeBSD. The graphics card will be no problem with either the nv open
source driver or the proprietary Nvidia from ports (or from nvidia
directly).

About your questions on dual boot, since I have a notebook dual booting
(actually triple booting) Vista, FreeBSD and Linux I can give you some
hand on information:

- The info you have been given about Partition Magic, GParted and
PartedMagic should work fine. You could use any of these tools to shrink
your Windows Vista partition. Make sure Vista boots after this
operation. The new MS loader seems to break rather easily. In the event
it does not boot you will need a Vista DVD to boot and select to repair.
This sounds more frightening than it really is, it does not happen often
and the repair works (automatically).

- When installing FreeBSD, when asked about the boot manager select NOT
to install it. Do NOT let it touch the MBR. Vista uses a different
loader from XP and it will probably fail to boot afterwards.

- When installation is finished, you will not be able to boot into
FreeBSD, but fear not. Boot into Vista and install the free EasyBCD program:

http://neosmart.net/dl.php?id=1

With this, you can add the choice for FreeBSD to your Vista bootloader
(a new system called BCD) . It is trivially easy to setup  and works
extremely well.

Hope this helps.

Manolis

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

Re: FreeBSD on a PC with Windows

[Manolis Kiagias]

David Morton wrote:

I have been out of work so long (since being diagnosed as autistic and
scared) that even as an IT professional, I now get very anxious about
messing with my PC.

However, I got a magazine that included FreeBSD/i386 6.2 on the DVD and I
have always wanted to play with BSD.  My past experience included UNIX
System V, some Solaris 7 or 8, and other variants, so you know a bit of
history.

Anyway, I have a laptop preinstalled with Vista Home Premium and I would
like to also run BSD on it.  In reading your installation documentation, I
do not see anything that suggests I can install FreeBSD onto my PC without
wiping Windows.

I also have restricted web access so cannot access you web site, so I would
like to know if FreeBSD will install in a way that will not kill Windows on
my PC?

I have to ask this, because I once had an old PC and put Solaris on it, and
that required a dedicated drive.  The PC is now dead, so I have to make it
all work on one machine.

Thanks, David

David Morton
E: [EMAIL PROTECTED]
M: 0400 560 330
H: 03 6295 0278

80 Rocky Bay Road
Deep Bay, TAS 7112
AUSTRALIA


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


  
Since I have a laptop with vista and FreeBSD, I will give a few quick 
hints that will save you time and despair:


- You will need to "shrink" your windows partition to make room for 
FreeBSD to create it's slice.


Now, I don't know what type of laptop you got, but since it is a Vista 
laptop, it is obviously one of the newest models. In most cases, disk 
partitions on these are:


1. Recovery partition for the pre-installed OS
2. Main Windows installation
3. Data Partition

The first (recovery) partition does not have a drive letter assigned to 
it in Windows, so it is not directly "viewable" from Windows explorer. 
The size is usually around 7-8Gb.
The rest of the disk is usually split between C: (Windows) and D: (for 
user storage). If this is the case, you would probably prefer to shrink 
the partition assigned to D:, since Vista needs quite some space for 
itself and the applications. To shrink  the partition you could try 
Norton Partition Magic, or, even better, download and run the GParted 
live CD.


If you intend to experiment with ports, packages and the like on 
FreeBSD, I suggest you leave a couple of Gigabytes for the slice. It all 
depends of course on what you plan to install. Bear in mind FreeBSD's 
slice must be created as primary partition, so you must not have more 
than three primary partitions on your disk prior to creating the slice.


When installing FreeBSD, you will be asked whether you would like to 
install a Boot Manager. Answer NO (select to leave the MBR untouched). 
When installation is finished, reboot to Vista  (it will be your only 
option anyway), and download and install EasyBCD (it is a free program, 
google for it). With this, in a few clicks, you will create an option to 
boot FreeBSD in Vista's boot menu. It is trivial as the program detects 
the FreeBSD partition automatically.


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

Re: /usr/local/rc.d/apache22 start doesn't start Apache

[Manolis Kiagias]

Yuri wrote:
> I installed Apache port.
> But when I run "/usr/local/etc/rc.d/apache22 start" nothing happens.
> 'ps ax | grep httpd' returns nothing.
> So server wasn't started.
>
> Why nothing is printed and server not started with the first command?
> What is the right way to start the server?
>
> Thanks,
> Yuri
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>   
Edit /etc/rc.conf and add:

apache22_enable="YES"

then retry your command above.
It is nominal for every port that acts as a daemon to have a
corresponding portsomething_enable="YES"  variable.
If you really need to start it without registering the variable (e.g.
for testing purposes), try

/usr/local/etc/rc.d/apache22 onestart


in this case however, it will not restart automatically after system reboot.

See also:

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


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

Re: nvidia-xconfig

[Manolis Kiagias]

Dánielisz László wrote:

Hello!

I can not make my xorg.conf work with nvidia-xconfig. I do execute the command 
and it gives me always the following error:

(II) Primary Device is: PCI 01:00:0
(WW) NVIDIA(0): The NVIDIA GeForce2 MX/MX 400 GPU installed in this system is
(WW) NVIDIA(0): supported through the NVIDIA 96.43.xx Legacy drivers.
(WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for
(WW) NVIDIA(0): more information.  The 173.14.12 NVIDIA driver will ignore
(WW) NVIDIA(0): this GPU.  Continuing probe...
(EE) No devices detected.

Fatal server error:
no screens found

  


You are using the wrong version of the driver for your hardware.


Do you have any idea what should I try?


Laci

  


Uninstall the nvidia-driver, and install x11/nvidia-driver-96xx
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Firefox won't start

[Manolis Kiagias]

Joe Tseng wrote:

I recently did a ports update and after a bit of effort I got firefox3 to 
compile with no errors.  But now when I either select Firefox from the menu or 
start it from a terminal window nothing happens.  Firefox does not start and 
there's no indication of any problems.  When I use ps to see if it's hung I see 
nothing.  Ideas?

tia,

 - Joe

  


Check out the permissions on your ~/.mozilla directory. Sometimes (I 
believe if you use sudo to compile / upgrade firefox), this directory is 
created with root/wheel ownership and restrictive permissions

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

Re: Limiting closed port RST

[Manolis Kiagias]

Vlad GURDIGA wrote:

Hello,

I've started an Apache bechmark with ab today and a lot of such
messages from kernel appeared in /var/log/messages:

Sep 25 16:16:34 dev01 kernel: Limiting closed port RST response from
270 to 200 packets/sec
Sep 25 16:19:10 dev01 kernel: Limiting closed port RST response from
475 to 200 packets/sec
Sep 25 16:19:15 dev01 kernel: Limiting closed port RST response from
220 to 200 packets/sec
Sep 25 16:19:19 dev01 kernel: Limiting closed port RST response from
243 to 200 packets/sec

What do they mean?

  


This normally means someone is repeatedly attempting to connect to a 
closed port, i.e. you are getting port-scanned!
Normally the kernel limits this response so the connection is not 
overwhelmed by the replies


Maybe your benchmark attempts to also connect to a port other than 80? 
(i.e. 443 and you are not running https)


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

Re: Kernel panic! 7.0-RELEASE-p4

[Manolis Kiagias]

Walter Venable wrote:

Our box, without readily obvious provocation, started doing this today:
Panic: softdep_setup_inomapdep: dependency for new inode already exists.
cpuid: 0
physical memory: 1971 MB
dumping 78MB: 63 47 31 15

The system then immediately reboots, and hits the panic, reboots, etc.
What can I do??
  


Maybe boot into single user mode and run fsck?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Utility to extract iso files without burning

[Manolis Kiagias]

Warren Liddell wrote:
Im looking for a GUI or command line that will allow me to extract information 
within an ISO file... im using FreeBSD 7.1-PRERELEASE KDE4.1.1 AMD64
  


You can mount an iso and copy files from it.

First create a memory disk device to contain the file system:

mdconfig -a -t vnode -f /path/to/your.iso -u md0

Then mount the file system as you would mount a CD-ROM:

mount -t cd9660 /dev/md0   /mnt

After you finish, first unmount then detach the md0 device:

umount /mnt
mdconfig -d -u md0

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

Re: gmirror prerequisite question

[Manolis Kiagias]

Dino Vliet wrote:

Hey freebsd list,

I've bought a secondry HDD to attach to my server running freebsd 7.0. I want 
to enable gmirror on it (will reinstall everything from scratch), but I want to 
know if my hardware is setup correctly as a prerequisite for doing this 
operation.

The command 

dmesg | grep Seagate 


Yields:

ad4: 76319MB  at ata2-master UDMA33
ad6: 76319MB  at ata3-master UDMA33

Can I assume everything is ok now and can I start the reinstallation? Why I'm 
in doubt is because of the master/slave thing I was expecting but that seems 
something of the IDE world as I have bought two Sata hard drives and connected 
it with sata cables to my motherboard.

But just checking to be sure.

Brgds and thanks in advanced!
Dino

  


The concept of master / slave only exists in the IDE (PATA) world. SATA 
disks do not have these troubles, as there is only one per cable.
Your setup is absolutely fine. If you haven't  already, I suggest you 
read this excellent article:


http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html?page=1

I've set up quite a few gmirrors with this info.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: GEOM_JOURNAL: Timeout. Journal gjournal XXXX cannot be completed.

[Manolis Kiagias]

Laszlo Nagy wrote:

Hi,

I'm trying to add a new disk to my system. I'm ready with labeling the 
disk. It is an SCSI device with and UFS partition and a SWAP 
partition. The swap is turned off, and I would like to use it as 
journal space. There is a screenshot attached showing what happens 
after entering single user mode. swaps are turned off, and the journal 
cannot be initialized. The message says:


GEOM_JOURNAL: Timeout. Journal gjournal 2578807269 cannot be completed.

Why is that?

Thanks,

  Laszlo



Screenshots will not come through on the list, could you upload them 
somewhere and send a link?

Is the partition you are trying to journal mounted?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Minor problems with Xfce

[Manolis Kiagias]

James Butler wrote:

Greetings all,

I'm using 7-stable on my Thinkpad X31, with Xfce recently (2 weeks or
so) installed from packages. I have two minor problems with Xfce, at
least one of which could be HAL/DBUS related - I'd appreciate some
advice to rule out misconfiguration on my part.

Firstly, when I bring up the Xfce Exit dialog, the Restart and
Shutdown buttons are greyed out. I have read the Xfce FAQ on the
subject, which mentions that the session manager tries HAL shutdown
methods first, then falls back to sudo. I don't have sudo installed,
but I have both hald and dbus (system and session) running.

Checking the xsession error log after an attempted Exit reveals:

** Message: xfsm-shutdown-helper.c:215: HAL not available or does not
permit to shutdown/reboot the computer, trying sudo fallback instead.

and (as expected):

** (xfce4-session:1066): WARNING **: sudo was not found. You will not
be able to shutdown your system from within Xfce

Looking at xfsm-shutdown-helper.c I see that the session manager
probes HAL for shutdown support by trying a dummy method call:

/* this is a simple trick to check whether we are allowed to
   * use the org.freedesktop.Hal.Device.SystemPowerManagement
   * interface without shutting down/rebooting now.
   */
  message = dbus_message_new_method_call ("org.freedesktop.Hal",

"/org/freedesktop/Hal/devices/computer",

"org.freedesktop.Hal.Device.SystemPowerManagement",
  "ThisMethodMustNotExistInHal");

[snip]

/* if we receive org.freedesktop.DBus.Error.UnknownMethod, then
   * we are allowed to shutdown/reboot the computer via HAL.
   */
  if (strcmp (error.name, "org.freedesktop.DBus.Error.UnknownMethod") == 0)

So out of curiosity I tried this manually and got the 'correct' error:

$ dbus-send --system --print-reply  --dest=org.freedesktop.Hal
/org/freedesktop/Hal/devices/computer
org.freedesktop.Hal.Device.SystemPowerManagement.ThisMethodMustNotExistInHal
Error org.freedesktop.DBus.Error.UnknownMethod: Method
"ThisMethodMustNotExistInHal" with signature "" on interface
"org.freedesktop.Hal.Device.SystemPowerManagement" doesn't exist

Now I don't claim to understand much of this, so any help would be
greatly appreciated. I have provided the output of various commands
from the freebsd-gnome Bugging guide at
http://homepages.ihug.co.nz/~sweetnavelorange/.

My other problem is possibly unrelated, but any actions I perform
which would remove or update icons on the desktop (deleting a file,
emptying Trash) don't take effect until xfdesktop is restarted or I
log out and then in. Any ideas? Notably, automatic detection and
mounting of USB drives, which seems to be a fragile area for many HAL
users, works perfectly for me.

Thanks in advance,
-James Butler
  


Insert something like the following in your 
/usr/local/etc/PolicyKit/PolicyKit.conf (between the  tags):


   
  
 
  
   
   
  
 
  
   

Have a look at /usr/local/share/PolicyKit/policy. Examine the contents 
of the files there to see possible actions.

It may also help to have a look at this page, if you haven't already:

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

I have some annoyances with XFCE myself, but I haven't bothered 
seriously to fix them. I have the same no-icon-update problem on my 
desktop. I keep pressing F5 as a workaround. Like in your case, USB 
flash drive mounting works perfectly. Another thing that does not work 
for me, is clicking an http link in an app: it will not open firefox. 
Weird, as firefox is selected as the default / preferred browser.

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

Re: Minor problems with Xfce

[Manolis Kiagias]

James Butler wrote:


My other problem is possibly unrelated, but any actions I perform
which would remove or update icons on the desktop (deleting a file,
emptying Trash) don't take effect until xfdesktop is restarted or I
log out and then in. Any ideas? Notably, automatic detection and
mounting of USB drives, which seems to be a fragile area for many HAL
users, works perfectly for me.

Thanks in advance,
-James Butler
  


Just solved this one, quite silly it was ;)
It seems Thunar is not built with FAM (File Alteration Monitor) support, 
hence it does not know when it needs to update folder views (or the 
desktop for that matter). So, simply rebuild with FAM:


# cd /usr/ports/x11-fm/thunar

# make config

(Select FAM from the options dialog)

# make deinstall reinstall

Restart your X session. It will work then.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Minor problems with Xfce

[Manolis Kiagias]

James Butler wrote:

Manolis Kiagias <[EMAIL PROTECTED]> wrote:
  

James Butler wrote:


My other problem is possibly unrelated, but any actions I perform
which would remove or update icons on the desktop (deleting a file,
emptying Trash) don't take effect until xfdesktop is restarted or I
log out and then in. Any ideas? Notably, automatic detection and
mounting of USB drives, which seems to be a fragile area for many
HAL users, works perfectly for me.

Thanks in advance,
-James Butler
  
  

Just solved this one, quite silly it was ;)
It seems Thunar is not built with FAM (File Alteration Monitor)
support, hence it does not know when it needs to update folder views
(or the desktop for that matter). So, simply rebuild with FAM:

# cd /usr/ports/x11-fm/thunar

# make config

(Select FAM from the options dialog)

# make deinstall reinstall

Restart your X session. It will work then.



Aha! I will try this when I get home - thanks. Anyone know why Thunar
does not default to using FAM/gamin? gamin doesn't look too heavy.

Cheers,
James Butler

  


It seems the default options for Thunar do not include gamin for some 
reason. Although I already had it installed anyway.  If you installed 
from packages, these are built with the default options, so not having 
FAM support is expected.


P.S. Putting the questions list back on this

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

Re: brasero

[Manolis Kiagias]

Dánielisz László wrote:

hello!

I just installed Brasero and because a strange reason I can not select any dvd writer drive, I included device  atapicam to my kernel? 


Do you have any idea what can I try?


Laci


  


While I have not used brasero on FreeBSD, I know (from k3b) that you 
will need several other settings. It all boils down to giving a normal 
user permissions to use the CD/DVD recorder device.   Both brasero and 
k3b depend on ports like sysutils/cdrdao, sysutils/cdrtools and 
sysutils/dvd+rw-tools.  You can find these settings in the info for k3b:


cd /usr/ports/sysutils/k3b

make showinfo
___
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 get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Manolis Kiagias]

Giorgos Keramidas wrote:


Hi Manolis & everyone else,

`ipdivert.ko' works fine as a module too.  You don't really *have* to
recompile the kernel, but we probably have to update the relevant
Handbook bits to mention that `ipdivert.ko' can be kldload'ed now.

Adding a few options in `loader.conf' should preload IPFW and DIVERT in
the running kernel:

ipfw_load="YES"
ipdivert_load="YES"

Then the rest of the `rc.conf' options described in the current text
work as expected.

I can't boot my 6.2-RELEASE installation today to verify that this works
in that version too, but if you have one around and it seems to work,
let me know and I'll handle the doc bits :-)

  

FWIW, both modules load fine in my VMWare based 6.2-RELEASE.
___
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 get my Dad's Win2k system to access internet through my FreeBSD 6.2 system

[Manolis Kiagias]

Peter N. M. Hansteen wrote:

Manish Jain <[EMAIL PROTECTED]> writes:

  
I am poor at networking and need a little bit of help. My dad has a 
Windows 2000 machine with a network card but does not have a connection 
to the internet. 



When I started writing this, I thought that system had been abandoned
already, but it appears Microsoft will offer a measure of support
through next year sometime.  Do see that the system gets properly
updated before you put it on the net.

  
My freebsd 6.2 box is connected to the internet and has 
2 network cards, rl0 and rl1. rl0 connects to the ISP and rl1 is 
directly connected via a long Ethernet cable to the NIC on my dad's 
machine. While I can access the internet easily, I want my dad to be 
able to connect to the internet with my freebsd box serving as the 
gateway. Can anyone please explain to me in easy steps how to accomplish 
this ?



The keyword is that you need to set up your machine as a gateway.
There are numerous guides available on how to do that (including the
FreeBSD Handbook (free, online and likely already on your system) my
PF tutorial (http://home.nuug.no/~peter/pf/) contains more than a few
hints, as do several books available at better bookstores), but I
would recommend that you pick literature that enables you to learn the
basics of TCP/IP as well as the actual commands needed.  Looking into
packet filtering for basic protection won't hurt either.  With those
keywords in hand, you should be able to dig up something useful.

- Peter
  


Inspired by this discussion (and just replying to a random post) I tried 
for the first time to get a test machine as a gateway.

I tried the handbook's instructions, here:

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

These work flawlessly, you will need to recompile your kernel though. 
The rest of the setup is relatively simple.
I am more accustomed to using pf rather than IPFW though, and as I 
wanted to test this on my main system, I came up with this setup:


/etc/rc.conf

pf_enable="YES"
pf_rules="/etc/pf.conf"
pf_flags=""
gateway_enable="YES"

(Run  sysctl net.inet.ip.forwarding=1 *and* /etc/rc.d/routing restart if 
you do not wish to reboot after modifying rc.conf)


I added this rule before the filtering rules section in my /etc/pf.conf:

nat pass on rl1 from rl0:network to any -> rl1

(This is an excellent read: http://www.openbsd.org/faq/pf/  )

where rl1 is the Internet-facing card, and rl0 is the local network one.
Also added a few simple rules to allow traffic from rl0 as I am normally 
using pf for firewalling.


This also worked nicely, and has the added advantage of not having to 
recompile the kernel.


So the OP has quite a few options, and it may prove not to be very 
difficult after all.



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

Re: Disable CTRL-ALT-DEL

[Manolis Kiagias]

Olivier Nicole wrote:

Hi,

On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting
the system?

Best regards,

Olivier
  


There are two ways of doing this, both described in the FreeBSD FAQ here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Disable CTRL-ALT-DEL

[Manolis Kiagias]

Peter Boosten wrote:

Manolis Kiagias wrote:
  

Olivier Nicole wrote:


Hi,

On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting
the system?

Best regards,

Olivier
  
  

There are two ways of doing this, both described in the FreeBSD FAQ here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT



Hmmm, didn't know about the second one, and doesn't seem to be working
either (on both 7.0 and 6.3):

sysctl hw.syscons.kbd_reboot=0
sysctl: unknown oid 'hw.syscons.kbd_reboot'


Peter
  
It seems you are right. Just checked on 6.3 and 7.0 and it does not 
exist. It does exist in 6.2, however.

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

Re: Disable CTRL-ALT-DEL

[Manolis Kiagias]

andrew clarke wrote:

On Sat 2008-10-18 09:47:51 UTC+0200, Peter Boosten ([EMAIL PROTECTED]) wrote:

  

http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT
  

Hmmm, didn't know about the second one, and doesn't seem to be working
either (on both 7.0 and 6.3):

sysctl hw.syscons.kbd_reboot=0
sysctl: unknown oid 'hw.syscons.kbd_reboot'



That's odd..

$ sysctl hw.syscons.kbd_reboot
hw.syscons.kbd_reboot: 1

$ uname -a
FreeBSD blizzard.phoenix 6.3-RELEASE-p5 FreeBSD 6.3-RELEASE-p5 #0: Wed
Oct  1 05:34:19 UTC 2008 [EMAIL PROTECTED]
daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

  

What about this:

[EMAIL PROTECTED]:~]$ uname -a
FreeBSD atlantis.dyndns.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #10: 
Fri Oct 17 18:31:22 EEST 2008 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ATLANTIS  i386

[EMAIL PROTECTED]:~]$ sysctl -a |grep syscons
hw.syscons.kbd_debug: 1
hw.syscons.bell: 1
hw.syscons.saver.keybonly: 1
hw.syscons.sc_no_suspend_vtswitch: 0
[EMAIL PROTECTED]:~]$

(Actual sources are not yesterdays, I just rebuilt the kernel yesterday)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Disable CTRL-ALT-DEL

[Manolis Kiagias]

Jeremy Chadwick wrote:

On Sat, Oct 18, 2008 at 10:58:29AM +0300, Manolis Kiagias wrote:
  

Peter Boosten wrote:


Manolis Kiagias wrote:
  
  

Olivier Nicole wrote:



Hi,

On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting
the system?

Best regards,

Olivier

  

There are two ways of doing this, both described in the FreeBSD FAQ here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT



Hmmm, didn't know about the second one, and doesn't seem to be working
either (on both 7.0 and 6.3):

sysctl hw.syscons.kbd_reboot=0
sysctl: unknown oid 'hw.syscons.kbd_reboot'


Peter
  
  
It seems you are right. Just checked on 6.3 and 7.0 and it does not  
exist. It does exist in 6.2, however.



Hmm...

# sysctl hw.syscons.kbd_reboot=0
hw.syscons.kbd_reboot: 1 -> 0
# sysctl hw.syscons.kbd_reboot=1
hw.syscons.kbd_reboot: 0 -> 1
# uname -a
FreeBSD icarus.home.lan 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Thu Oct  2 
03:04:20 PDT 2008 [EMAIL 
PROTECTED]:/usr/obj/usr/src/sys/PDSMI_PLUS_RELENG_7_amd64 amd64

  

Mystery solved.
The sysctl only exists if you have not already compiled the kernel with 
options SC_DISABLE_REBOOT
I just checked, and all the systems that do not show this were compiled 
with SC_DISABLE_REBOOT

I installed a clean (vmware) 7.0 and hw.syscons.kbd_reboot exists.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Error with kernel PAE option

[Manolis Kiagias]

Robert Fitzpatrick wrote:

Trying to build my own kernel with PAE option and getting the following
error...

/usr/src/sys/dev/advansys/advansys.c: In function 'adv_action':
/usr/src/sys/dev/advansys/advansys.c:259: warning: cast from pointer to
integer of different size
*** Error code 1

I removed the PAE option keeping my SMP option in the kernel
configuration for this dual proc server and it builds fine. Any idea
what I can do for this error?

  

Have a look at:

/usr/src/sys/i386/conf/PAE

Is the device that is causing the problem listed with a "nodevice" entry?
I guess in your case, it is the "adv" device, and it is listed. This 
means it does not work with a PAE kernel.


How about going with the 64bit version of FreeBSD?

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

Re: Error with kernel PAE option

[Manolis Kiagias]

Robert Fitzpatrick wrote:

On Tue, 2008-10-21 at 18:43 +0300, Manolis Kiagias wrote:
  

Robert Fitzpatrick wrote:


Trying to build my own kernel with PAE option and getting the following
error...

/usr/src/sys/dev/advansys/advansys.c: In function 'adv_action':
/usr/src/sys/dev/advansys/advansys.c:259: warning: cast from pointer to
integer of different size
*** Error code 1

I removed the PAE option keeping my SMP option in the kernel
configuration for this dual proc server and it builds fine. Any idea
what I can do for this error?

  
  

Have a look at:

 /usr/src/sys/i386/conf/PAE

Is the device that is causing the problem listed with a "nodevice" entry?
I guess in your case, it is the "adv" device, and it is listed. This 
means it does not work with a PAE kernel.



Thanks, yes, I have nodevice in the PAE file for adv. What does this
mean and/or how can I address this problem? Should I just remove the
entry from the PAE file?
  


No.  The idea behind the "PAE" file is that whatever you see with 
nodevice is not supported by PAE kernels.  Even if you manage to compile 
a kernel with the device, you will just get into trouble.

The idea behind this file is that you change the line:

include GENERIC

on the top, to your own custom kernel configuration file.
Then you compile with

make buildkernel KERNCONF=PAE

which gets all your settings from your own file *minus* the ones that 
are incompatible with PAE  (the ones identified with nodevice)
 
  

How about going with the 64bit version of FreeBSD?



That was my first try, but the CPU appears not to support amd64 as there
are no AMD Features listed in dmesg.

  
Is it a 64bit CPU? The AMD64 version of FreeBSD supports the Intel 64bit 
(Core2 / Quad / Xeon / Pentium 4 / Pentium D) processors as well, 
regardless of the "AMD" in its name.

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

Re: Error with kernel PAE option

[Manolis Kiagias]

Robert Fitzpatrick wrote:

On Tue, 2008-10-21 at 20:30 +0300, Manolis Kiagias wrote:
  

Is it a 64bit CPU? The AMD64 version of FreeBSD supports the Intel
64bit 
(Core2 / Quad / Xeon / Pentium 4 / Pentium D) processors as well, 
regardless of the "AMD" in its name.



It is an Intel Xeon 2.4GHz processor, but I was told yesterday here on
the list that if LM does not appear in the AMD Features line of dmesg,
then it does not support amd64. I looked at another server we have here
now running amd64 FreeBSD and I see the AMD Features line with LM, but
on this server, no AMD Features line whatsoever. I am getting 'BTX
halted' when trying to install FreeBSD-amd64 on this server. The other
server we have running it has Xeon 3.0GHz procs, I thought that was
kinda weird that the two servers were really close in spec, but one
would not run amd64 :/

This would be my preferred option if I can get it to install.

  

Well, LM is the flag for x86-64. You are probably running a 32bit Xeon CPU.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: root | su

[Manolis Kiagias]

Jos Chrispijn wrote:

Is there a way of stopping root from su'ing to another user?

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


Root is supposed to be the almighty god on your machine (i.e. you...). 
No point trying to limit the abilities of root (especially if physical 
access is also provided).
And seriously,  root is a role not a person. If you find yourself trying 
to limit root's capabilities, you've probably surrendered the root 
password to the wrong person. If you need to give someone limited root 
access to a machine, just use security/sudo instead (with a carefully 
crafted sudoers file).

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

Re: NFS Help

[Manolis Kiagias]

Victor Farah wrote:

Hello
I have about 10 machines that are NFS clients, 5 are new and 5 are 
older.  Anyway the new machine mount from the NFS server just fine.
The older machines mount; and I can ls /mnt/data/; BUT when I ls 
/mnt/data/sc/ on the older machines this happens:

nfs server 192.168.10.162:/data: not responding
nfs server 192.168.10.162:/data: not responding
nfs server 192.168.10.162:/data: not responding
nfs server 192.168.10.162:/data: not responding

But on the new machines they work perfectly fine?
As well the old machines mount it as i stated before I can even ls the 
parent directory /mnt/data/ and it shows me all the directories on the 
mount, but anytime I ls or do anything inside there it does that or 
freezes.


Any idea's?


How "old" are these old systems? Do you have any ISA type ethernet cards?

Read Handbook's section 30.3.6:

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

I actually had this kind of trouble once, and it was due to  an ISA 
network card. I doubt you are really using an ISA card in a production 
system, but some of the remedies described in the section may give you a 
hint of what is going on.

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

Re: flash-9, 10 on FreeBSD

[Manolis Kiagias]

Kirk Strauser wrote:

On Tuesday 28 October 2008 13:31:13 Craig Butler wrote:

  

The way forwards has to be to jump onto the gnash band wagon  I
think that project is moving leaps and bounds.



Any idea how to get the Firefox plugin working?  I installed it with "PLUGIN" 
and "GTK" selected, and /usr/local/lib/browser_plugins/libgnashplugin.so is 
there, but "about:plugins" doesn't reflect it.
  
If it is firefox3 you are talking about, create a symbolic link to the 
actual plugins directory:


ln -s /usr/local/lib/browser_plugins/libgnashplugin.so   
/usr/local/lib/firefox3/plugins


(repeat for any other plugins you need from browser_plugins that do not 
work. Bear in mind that your browser may crash if they happen to be 
incompatible with firefox3)


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

Re: flash-9, 10 on FreeBSD

[Manolis Kiagias]

Kirk Strauser wrote:

On Oct 28, 2008, at 4:00 PM, Manolis Kiagias wrote:

If it is firefox3 you are talking about, create a symbolic link to 
the actual plugins directory:


ln -s /usr/local/lib/browser_plugins/libgnashplugin.so 
  /usr/local/lib/firefox3/plugins


Well, that seems pretty obvious now.  It leads me to wonder, though: 
what browsers *do* look in /usr/local/lib/browser_plugins?  Or is that 
just meant to be a convenient place to symlink into?

--
Kirk Strauser



The following excerpt from /usr/ports/UPDATING will completely answer 
your question :)


20080727:
 AFFECTS: users of www/firefox3
 AUTHOR: [EMAIL PROTECTED]

 Update to 3.0.1_1,1; it no longer seeks for plugins in 
lib/browser_plugins,
 because few plugins that built with Firefox 2 can cause Firefox 3 to 
crash.

 We are working on making some changes with plugins directory by using
 www/linux-mplayer-plugin/Makefile.npapi. If there are some other plugins
 that work with Firefox 3 and you would like to use, you can copy them to
 ~/.mozilla/plugins or /usr/local/lib/firefox3/plugins manually for now.

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

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Manolis Kiagias]

Aggelidis Nikos wrote:

hi to all the list,

i am trying to install ImageMagick 6.4.4.1_1 from the ports system.
The problem seems to be that i can't complete succesfully the tests of
imagemagick. In particular i fail in all the Magick++ tests

[snip]


  


If I remember well, this is a known issue.  Change to the port's 
directory, execute make config, and deselect IMAGEMAGICK_TESTS from the 
options dialog. It should build and install fine.

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

Re: build ImageMagick 6.4.4.1_1 from ports failed...

[Manolis Kiagias]

Aggelidis Nikos wrote:

Here are the configurations options:

===> The following configuration options are available for
ImageMagick-6.4.4.1_1:
 X11=on "X11 support"
 IMAGEMAGICK_TESTS=on "Run bundled self-tests after build"
 IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)"
 IMAGEMAGICK_PERL=on "Perl support"
 IMAGEMAGICK_MODULES=off "Modules support (broken)"
 IMAGEMAGICK_BZLIB=on "Bzlib support"
 IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support"
 IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)"
 IMAGEMAGICK_LCMS=on "LCMS support"
 IMAGEMAGICK_HDRI=off "High Dynamic Range Images (HDRI)"
 IMAGEMAGICK_TTF=on "Freetype support"
 IMAGEMAGICK_FONTCONFIG=on "Fontconfig support"
 IMAGEMAGICK_JPEG=on "JPG format support"
 IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)"
 IMAGEMAGICK_PNG=on "PNG format support"
 IMAGEMAGICK_TIFF=on "TIFF format support"
 IMAGEMAGICK_FPX=on "FPX format support"
 IMAGEMAGICK_JBIG=on "JBIG format support"
 IMAGEMAGICK_JPEG2000=on "JPEG2000 format support"
 IMAGEMAGICK_DOT=off "GraphViz dot graphs support"
 IMAGEMAGICK_WMF=off "WMF format support"
 IMAGEMAGICK_SVG=off "SVG format support"
 IMAGEMAGICK_PDF=on "PDF format support"
 IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support"
===> Use 'make config' to modify these settings

  

what platform and FBSD version?



#uname -a: FreeBSD apollo 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
24 19:59:52 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

  

did you build with perl support?


yes

  

If I remember well, this is a known issue.  Change to the port's directory,
execute make config, and deselect IMAGEMAGICK_TESTS from the options dialog.
It should build and install fine.



oh i didn't know this, but Anton stated that
  

I've passed all tests on i386



So you think i should disable the tests and recompile?

thank you all for your help so far,
nikos
  


AFAIR, there was a discussion about this not so long ago, and compiling 
without the tests was a proposed solution. In fact, I just checked my 
system and I have ImageMagick installed without the tests in the config 
options.

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

Re: XFCE4

[Manolis Kiagias]

joeb wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

FBSD1 wrote:
  

What port names need to be installed to create a XFCE4 desktop


environment?
  

I was looking for a mega port like kde3 has but could not identify one.
Thanks in advance.



I'm going to rake a random guess: x11-wm/xfce4 ?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Eitan Adler
Sent: Monday, November 03, 2008 12:14 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] ORG
Subject: Re: XFCE4

Thank you for your random guess, but research of the ports system seem to
indicate a whole suite of ports are needed to build a complete working
environment.
Waiting for a real user to fill in the details of what combination of ports
they used to build their XFCE4 desktop.

  


It is not really a random guess, x11-wm/xfce4 is the metaport you need 
to build for a working XFCE4 environment.
There are a couple of additional tools you may also wish to use in this 
environment. I would recommend graphics/ristretto for a lightweight 
image viewer,  sysutils/thunar-volman-plugin to handle mounting of 
external media, sysutils/xfce4-battery-plugin if running on a laptop.


Also, make sure to read:

Section 5.7.4:

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

For usb mounting:

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

For policy kit / hal settings:

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

and when compiling Thunar (the file manager) make sure to select FAM 
support from the options dialog.

___
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 upgrade to KDE4

[Manolis Kiagias]

[EMAIL PROTECTED] wrote:

Hi,

I'm using FreeBSD 6.2-p11 (yes, I've got to update). A couple days ago 
I updated my ports tree and went to update kde 3.5.6. At first I did a 
portupgrade on the KDE meta-port but, ironically, the only thing that 
updated was the meta-port (I did a portupgrade -r too). I should also 
say that I first looked in /usr/ports/UPDATING and there weren't any 
particular instructions (that I could find) for updating KDE. I opened 
the file in vim and searched for "kde" and "KDE." On both searches, 
nothing regarding the specific update of 3.5.x to 4.x was mentioned.


I'm having some problems updating the kdebase package now (since the 
meta-port didn't update the whole thing, I'm updating individually to 
3.5.10). It's having some compile time issues, something about an 
identifier not existing in a particular namespace or some-such error, 
I've got to look into it further. However, since I'm going through 
this loathsome process anyway, would it be advisable to just do a 
"deinstall" of the kde system and cd to /usr/ports/x11/kde (I think 
that's where it is) and install 4.x (if that's even how to do it)? I 
would really prefer to run 4.x.


Thanks for any help,
Andy


The Handbook has been recently updated with instructions on installing / 
running KDE4:


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

It is also possible to keep both versions installed (since KDE4 installs 
in a different directory).
If you decide to go along this path, I would advise you to set your PATH 
so that /usr/local/kde4/bin is before /usr/local/bin (when running 
KDE4). This will prevent inadvertently running kde3.x executables in 4.x.


There has been some discussion on the list concerning the usability of 
KDE4. FWIW, it worked for me but I am not a KDE person anyway (and have 
only used 3.X a couple of times) and don't need most of the features of 
such a desktop. YMMV.

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

Re: eps to jpg conversion - which program?

[Manolis Kiagias]

Laszlo Nagy wrote:


 Hi,

I need to convert eps files into jpeg files in batch mode. Gimp works 
perfectly, except that I cannot use an X display. I tried eps2png with 
no success:



%file test.eps
test.eps: DOS EPS Binary File Postscript starts at byte 30 length 
566887 TIFF starts at byte 566917 length 4741

%eps2png -jpg -width 1000 -verbose -output test.jpg test.eps
Producing jpg (jpeg) image.
Not EPS file: test.eps, skipped

What port should I use to convert EPS into JPG? I would like to use a 
program that shares the same library with Gimp, because we know that 
Gimp works great for this task.


Thanks,

  Laszlo



How about using 'convert' from graphics/ImageMagick?

It would be as simple as

convert myfile.eps  myfile.jpg

and there are myriads of options to fiddle if you wish. I've been using 
it with great success for quite some time now.

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

Re: Hashes in scp usernames (OpenSSH bug 472)

[Manolis Kiagias]

Christopher Key wrote:

Hello,

I've come upon OpenSSH bug 472, whereby scp refuses usernames 
containing a '#' character, dieing with 'invalid user name'.  Both 
rsync and ssh accept such usernames, and after looking at 
/usr/src/crypto/openssh/scp.c, it would appear that scp also allows 
such usernames for the source, but not the destination.


I've several questions:

1) Is there any specific reason why scp behaves like this, and 
specifically why does it only attempt to validate the destination user 
name and not the source?


2) Assuming it is safe to drop the username validation, I can quite 
happily modify the code as appropriate.  However, I'm not sure how to 
rebuild and update with minimum fuss.  I really only need to rebuild 
scp and install the new binary, can I do this easily without a full 
make buildworld; make installworld?


3) Assuming that there's no additional reason not to remove the 
username validation, how should I go about submitting a change request 
to get this modification made in CURRENT, and MFCed as appropriate?


Kind Regards,

Chris Key




I don't know whether any of this is a good idea (there might be a very 
good reason why it is programmed this way, generally stuff in 'secure' 
is rather sensitive), but to answer your second question, you would 
simply do:


# cd /usr/src/secure/usr.bin/scp
# make
# make install

Since OpenSSH comes from OpenBSD, it may be worth trying asking someone 
over there too.

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

Re: bsd.gnome.mk is broken in 6.3-RELEASE ? Cannot update x11 ports ?

[Manolis Kiagias]

Juri Mianovich wrote:

Clean install of 6.3-RELEASE.

cvsup _only_ ports/x11, ports/x11-wm, ports/x11-servers

Now enter ports/x11/xorg and attempt a 'make install'

  


The sample /usr/share/examples/cvsup/ports-supfile states:

# Be sure to ALWAYS cvsup the ports-base collection if you use any of the
# other individual collections below. ports-base is a mandatory collection
# for the ports collection, and your ports may not build correctly if it
# is not kept up to date.

You are probably missing an updated ports-base

Eventually it bombs out with:

===>Verifying install for /usr/local/libdata/pkgconfig/pixman-1.pc in 
/usr/ports/x11/pixman
Unknown modifier '9'

"/usr/ports/Mk/bsd.gnome.mk", line 643: Malformed conditional 
(${_USE_GNOME_ALL:Mltverhack:9}=="")
Unknown modifier '9'

Error expanding embedded variable.
*** Error code 2

Stop in /usr/ports/x11/xorg-libraries.
*** Error code 1

Stop in /usr/ports/x11/xorg.


I don't really care why.  I'm sure it's fascinating, whatever it is.  Can I 
just get a quick textual fix - some file to edit somewhere that fixes this ?

What _is_ fascinating is that I am the only person _ever_ to attempt cvsup'ing 
the x11 portions of the ports tree and then install xorg.  You'd think someone 
would have done this before now.

Thanks.


  

  
If you only cvsuped those three ports, you have an outdated version of 
the bsd.gnome.mk file (I checked the recent version and there is no such 
line).
In fact, to avoid any more issues, I would suggest you cvsup the entire 
tree. If you feel cvsup / csup is slow, try portsnap:


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-portsnap.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 7.1

[Manolis Kiagias]

Frank Bonnet wrote:

Hello

I don't want appears as an impatient and I KNOW people that
support FreeBSD are volunteers, I am a long time user of
our prefered OS

I just would like to have an estimation for the release of 7.1.

I have two new production servers that will come tomorrow
- If the release is a matter of days I'll wait
  a bit before installing them,
- If it is a matter of monthes I'll install them with another
  release.

Thanks a lot


I don't think it is a matter of days, we have not even reached RC status 
yet on 7.1
On  a production server you will probably wish to go with 
7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of 
freebsd-update(8) when it is released.
You probably don't want to risk 7.1-PRERELEASE on a server, but for 
anyone running workstations, desktops, laptops I think it is worth 
trying at this moment.

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

Re: 7.1

[Manolis Kiagias]

Ott Köstner wrote:

Manolis Kiagias wrote:

I don't think it is a matter of days, we have not even reached RC 
status yet on 7.1
On  a production server you will probably wish to go with 
7.0-RELEASE-p5. It would be trivial to upgrade to 7.1 by means of 
freebsd-update(8) when it is released.
You probably don't want to risk 7.1-PRERELEASE on a server, but for 
anyone running workstations, desktops, laptops I think it is worth 
trying at this moment.
I am a person, who made a mistake, installing 7.1 on my production 
server (actually RELENG_7 stable, which shows up as 7.1).


My question is, how stupid is that mistake? Is it better to reinstall 
7.0 before something really bad happens, or can I just let it run? 
What are the most serious bugs to expect?



Greetings,
O.K.



It all depends on the programs you run, your configuration, system load 
and so on. Bugs that may be present in the system, may simply not be 
applicable to you, if you are not using the specific part or feature 
that has the problem.  While it is difficult to assess without knowing 
specific details, I think 7.1 is generally stable at the moment. Maybe 
people using it in production servers (if any) can step in and share 
their experiences.

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

Re: FreeBSD Media Center

[Manolis Kiagias]

Gary Hartl wrote:
> Hi all;
>
>  
>
> I have an old laptop (Dell Inspiron 7500), P3 550mhz, 256mb ram 20 gig hdd.
>
>  
>
> I am wondering what the validity of putting FBSD on it running VLC or
> something like that feeding to my tv.
>
>  
>
> Anyone with any feedback on this.
>   


I believe it will work in this respect, though it will probably be
unable to run high bit rate movies.  It should play the average DivX
though.
I would go with a minimal X environment and mplayer (the command line
version) which I feel is the best in decoding media files (vlc is also a
good choice).

>  
>
> Or is there a FBSD Media Center project out either in alpha or beta?
>
>  
>
> Thanks 
>
>  
>
> Gary
>   

Well, mythtv is in the ports tree,  and is the first that comes to mind.
I've never used it myself and as I understand it is going to be kind of
an overkill for this machine of yours.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD and hardware??

[Manolis Kiagias]

Chad Perrin wrote:
> On Tue, Nov 18, 2008 at 02:18:13PM +0100, Wojciech Puchar wrote:
>   
>>> By constantly repeating that UNIX is no Windows replacement you are
>>>   
>> and i will repeat it because it's true. it's every other unix replacement.
>> 
>
> It did a quite admirable job of replacing MS Windows for me.  I don't
> know why you're so down on it.
>
>
>   
>> as linux tries for many years to be windows replacement - it's both low 
>> end unix and low end windows replacement, "windows for poor".
>> 
>
> 
>
> . . . and, as I said, FreeBSD is a great MS Windows replacement for me.
> I don't miss MS Windows *at all* when I'm using FreeBSD on my laptop
> every single day.
>
>   

(Responding to random post)

Could we please *close* this discussion now?
This is simply a waste of the list resources, people will always have
ideas on why an OS is better or worse than another. If the original
poster wanted to know something about all this, he would have probably
commented by now. Has it come to anyone's mind that the original post
was probably a simple act of trolling? (and someone is now amused by all
this?)

In the end, when someone is presented with the facts and can have a
hands on experience with a system (and it won't cost him a dime to do
so), he can decide whether he wants to use it, whether it can replace
his current system and whether he is willing to climb the steep learning
curve. Let's give people choice, we don't need to force this or any
other OS down anyone's throat.
Let's just help whoever comes in here - Some will appreciate FreeBSD
*and* the community and will stay. And it will be there choice.

Just my 2c
Over and out ;)

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

Re: Problem about ppp -nat

[Manolis Kiagias]

Pongthep Kulkrisada wrote:
> Hi All,
>
> I have just subscribed to freebsd-questions and I have a question about ppp 
> -nat.
>
> I have 2 computers. One is running FreeBSD-7.0R, the other is running WinXP. 
> The host running FBSD7.0R has been connecting to the outside world using 
> user-ppp without any problem for very long. Now I want to share internet 
> access to the other host behind NAT through this FBSD host.
> My FBSD machine has 2 interfaces i.e.
>   tun0 (connecting to ISP) with dynamic IP (of course)
>   fxp0 (for internal LAN) with static IP of 192.168.1.10
> My WinXP machine has 1 interface (internal LAN) with static IP of 192.168.1.11
>
> Previously I have a router acting as a gateway for all machines behind NAT. 
> But now I want FBSD machine to work as a gateway. I have never done this 
> before. I tried some googling with reading ppp(8) and ipfw(8). And I tried 
> masquerading but it didn't work. I have plenty configuration files. But the 
> relevant configurations are listed here.
>
> /etc/rc.conf
> # enable IP forwarding
> gateway_enable="YES"
> # previously I ran web-server, just disable it or comment it out, not sure 
> why!
> #apache_enable="YES"
>
> On the host running WinXP, I set its gateway and DNS server to the IP of ppp 
> host i.e. 192.168.1.10.
>
> I then inserted the following line as the first rule in /etc/ipfw.rules.
> /sbin/ipfw add allow all from any to any via fxp0
> (I know this rule is dangerous, but just for testing.)
>
> I then issue the ppp command.
> [EMAIL PROTECTED]:~# ppp -background -nat myisp
>
> FBSD host (running ppp) can access anywhere but WinXP host can't. I learned 
> from some site explaining that ppp itself has the capability of IP 
> masquerading. And it does not require natd(8). So I don't mention about natd 
> here.
> Anyone have a clue or who have done the correct configurations, please point 
> me out.
>
> Thank you in advance.
> Pongthep
>
>   

There are at least two ways that I know of to achieve this. One uses the
ipfw firewall, the other the pf firewall.
For the ipfw solution, look at the FreeBSD Handbook:

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

This worked fine for me, although I prefer to use pf. Here is how I
setup pf (Adjust for your interfaces as necessary)

My Internet interface is rl0, setup in rc.conf as:

ifconfig_rl0="inet 192.168.0.100 netmask 255.255.255.0"

My local interface is rl1, setup in rc.conf as:

ifconfig_rl1="inet 192.168.1.100 netmask 255.255.255.0"

(I also have a defaultrouter setting which probably does not apply to you)

I have nameserver entries in /etc/resolv.conf (or setup your own DNS
server if you wish)

Use this settings in rc.conf for pf:

pf_enable="YES"
pflog_logfile="/var/log/pflog"
pflog_flags=""
pf_rules="/etc/pf.conf"
pf_flags=""
gateway_enable="YES"

Run:
# sysctl net.inet.ip.forwarding=1
# /etc/rc.d/routing restart

Add net.inet.ip.forwarding=1 to /etc/sysctl.conf so it persists reboots

Add the following rule to /etc/pf.conf

nat pass on rl0 from rl1:network to any -> rl0

AFAIR, if rl0 has a dynamic address, you will have to write it with
parentheses, like:

nat pass on rl0 from rl1:network to any -> (rl0)

(Note that in /etc/pf.conf translation rules like the above, are placed
above filtering rules like pass or block etc)
You may have to adjust /etc/pf.conf filtering rules, assuming you have any.

Restart some services

# /etc/rc.d/netif restart
# /etc/rc.d/routing restart
# /etc/rc.d/pf restart

or simply reboot, and you should be set.

Note that in your client machine, you should set gateway to point to
your FreeBSD machine, but unless you are running your own DNS server,
DNS entries should point to your ISP.  If you combine this setup with a
DHCP server from the Ports Collection, you will have pretty much a
standard home router out of a FreeBSD machine. There are also other
capabilities, like port forwarding and so on, but I'll let you figure
them out yourself ;)


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

Re: Problem about ppp -nat

[Manolis Kiagias]

Pongthep Kulkrisada wrote:
> * Manolis Kiagias ([EMAIL PROTECTED]) wrote:
>   
>> This worked fine for me, although I prefer to use pf. Here is how I
>> setup pf (Adjust for your interfaces as necessary)
>>
>> My Internet interface is rl0, setup in rc.conf as:
>>
>> ifconfig_rl0="inet 192.168.0.100 netmask 255.255.255.0"
>>
>> My local interface is rl1, setup in rc.conf as:
>>
>> ifconfig_rl1="inet 192.168.1.100 netmask 255.255.255.0"
>> 
> 3. I haven't mentioned that I can't use this configuration. I have 2
> interfaces i.e. public and private LAN. But I have only one NIC card for
> private LAN. I don't have NIC card for public. I'm using 56k modem to
> connect the outside world. I think I can't add
>
> ifconfig_tun0="inet 192.168.0.100 netmask 0xff00"
>   

You won't of course put this in rc.conf. However  AFAIK tun0 is *still*
a network interface and can appear in firewall rules.
So the PF method I described should work, tun0 is considered the
"external" network interface, the rule would be:

nat pass on tun0 from rl1:network to any -> (tun0)

where rl1 would be the internal interface. Needless to say, I have no
way of testing the above as I don't have a modem.
Since obviously you want to use ipfw, I still suggest you go by the
handbook:

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

First, make sure Internet works normally on your FreeBSD host.  Then
apply the above instructions. The example in the handbook shows a line:

natd_interface="fxp0"

which in your case would be:

natd_interface="tun0"

It seems you already have these settings though, so I would review the
Handbook instructions and remove anything else from the configuration
which does not appear there. Once things are working, go back and add
firewall rules etc.  Handbook instructions worked for me (with two
ethernet cards though) "out of the box".

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

Re: freebsd-update and sources / custom kernel

[Manolis Kiagias]

andrew clarke wrote:
> On Tue 2008-11-25 07:16:44 UTC+0100, Zbigniew Szalbot ([EMAIL PROTECTED]) 
> wrote:
>
>   
>> I hope you can clear my doubts. When I use freebsd-update to update a
>> machine with a custom kernel, do I need to fetch sources before I
>> rebuild the kernel or are they fetched by freebsd-update utility?
>> 
>
> freebsd-update will update the kernel sources on the condition that
> the Components setting is configured correctly in freebsd-update.conf.
> Normally you'd use:
>
> Components src world kernel
>
> Then after a successful update, if you're not using the GENERIC
> kernel, you should rebuild the kernel with your custom settings.
> After the new kernel is installed you should reboot the machine.
>
>   

Correct, and let me also add that the above setting is the default one,
so unless you edited the file yourself (highly unlikely) you are already
getting the sources when using freebsd-update.

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

Re: Filesystem problems at boot and shutdown?

[Manolis Kiagias]

Rick Janssen wrote:
> I've been playing around with FreeBSD for some time now, still being
> unable to solve some problems. Let me explain.
>
> I'm trying to run a webserver on the machine. Just basic, nothing too
> fancy. Problem concerns the following: The website served is speedy as
> expected when accessed from local LAN, but when accessed from WAN via
> router, it's realy slow. So, to do some tests, this afternoon I requested
> some pages from an computer outside my LAN. Server was very slow again,
> even ssh slowed to a crawl. Suddenly, without reason I know off,
> everything sped up. I issued a reboot to check if the problem might have
> been 'solved'. This took a long time.
>
> Back home I checked the logs. It now appeared the long reboot-time was
> caused by a Syncing disk anomaly, which happens when the system prepares
> for shutting down.
>
> Nov 26 22:38:12 server kernel: Syncing disks, vnodes remaining...1 1 1 1 1
> 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
> 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 timed out
> Nov 26 22:38:12 server kernel: Waiting (max 60 seconds) for system process
> `bufdaemon' to stop...done
> Nov 26 22:38:12 server kernel: Syncing disks, buffers remaining... 184 185
> 186 1 185 185 185 185 184 184 185 185 185 184 184 185 1 184 184 184 184
> 185 185 185 1 184 184 184 184 184 185 184 184 185 185 1 185 184 184 184
> 184 184 184 1 185 184 184 184 184 185 184 184 185 1 185 184 184 184 184
> 184 184 185 1 184 184 185 184 184 184 184 185 184 184 185 1 185 185 184
> 184 184 185 184 184 184 185 1 184 184 185 184 184 185 184 184 185 185 184
> 184 184 184 184 1 184 184 184 1 184 184 185 1 185 184 184 1 184 185 184
> 184 185 185 184 184 ... etc etc...
> Nov 26 22:38:12 server kernel: Final sync complete
>
> So I figured, might as well run fschk -y in single user mode to fix
> potential problems. Now I got some new errors:
>
> Nov 26 20:48:11 server kernel: ad4: WARNING - WRITE_DMA48 UDMA ICRC error
> (retrying request) LBA=1364750271
> Nov 26 20:48:11 server kernel: ad4: FAILURE - WRITE_DMA48
> status=51 error=4 LBA=1364750271
> Nov 26 20:48:11 server kernel:
> g_vfs_done():ad4s1g[WRITE(offset=682932174848, length=131072)]error = 5
>
> So far, nothing serious has followed from these errors I know off. They
> only happen sporadically, during reboots.
>
> Are these to problems even related, or am I just unlucky? Anyone has some
> suggestions to fix them?
>
> Regards,
> Rick
>
>   
Unless there is some incompatibility between FreeBSD -> Your disk
controller -> Your disk, my best guess is you have a failing disk.  I
would also suggest you check cables, connections (I guess this is an 
ATA disk so you may wish the check whether the flat cable is the
80-conductor type and is plugged in correctly). Hopefully, if you are
just playing with the system, you don't have any critical data in there,
otherwise I would suggest you back up immediately.  Do you have a spare
disk to try and see what happens?
Whether your other problem depends on this: It could be, since your
webserver might be trying to read from a faulty area and keep retrying. 
Or indeed there is some incompatibility and the disk is constantly
under-performing. 
You did not mention the speed of you WAN connection, but FWIW I am
running a webserver behind a 1Mbps/256Kbps ADSL line and response is
good enough. SSH is definitely good enough to use in long vi sessions,
with lengthy documents.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Filesystem problems at boot and shutdown?

[Manolis Kiagias]

Rick Janssen wrote:
>> Rick Janssen wrote:
>> 
>>> I've been playing around with FreeBSD for some time now, still being
>>> unable to solve some problems. Let me explain.
>>>
>>> I'm trying to run a webserver on the machine. Just basic, nothing too
>>> fancy. Problem concerns the following: The website served is speedy as
>>> expected when accessed from local LAN, but when accessed from WAN via
>>> router, it's realy slow. So, to do some tests, this afternoon I requested
>>> some pages from an computer outside my LAN. Server was very slow again,
>>> even ssh slowed to a crawl. Suddenly, without reason I know off,
>>> everything sped up. I issued a reboot to check if the problem might have
>>> been 'solved'. This took a long time.
>>>
>>> Back home I checked the logs. It now appeared the long reboot-time was
>>> caused by a Syncing disk anomaly, which happens when the system prepares
>>> for shutting down.
>>>
>>> Nov 26 22:38:12 server kernel: Syncing disks, vnodes remaining...1 1 1 1
>>> 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
>>> 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 timed out
>>> Nov 26 22:38:12 server kernel: Waiting (max 60 seconds) for system process
>>> `bufdaemon' to stop...done
>>> Nov 26 22:38:12 server kernel: Syncing disks, buffers remaining... 184 185
>>> 186 1 185 185 185 185 184 184 185 185 185 184 184 185 1 184 184 184 184
>>> 185 185 185 1 184 184 184 184 184 185 184 184 185 185 1 185 184 184 184
>>> 184 184 184 1 185 184 184 184 184 185 184 184 185 1 185 184 184 184 184
>>> 184 184 185 1 184 184 185 184 184 184 184 185 184 184 185 1 185 185 184
>>> 184 184 185 184 184 184 185 1 184 184 185 184 184 185 184 184 185 185 184
>>> 184 184 184 184 1 184 184 184 1 184 184 185 1 185 184 184 1 184 185 184
>>> 184 185 185 184 184 ... etc etc...
>>> Nov 26 22:38:12 server kernel: Final sync complete
>>>
>>> So I figured, might as well run fschk -y in single user mode to fix
>>> potential problems. Now I got some new errors:
>>>
>>> Nov 26 20:48:11 server kernel: ad4: WARNING - WRITE_DMA48 UDMA ICRC error
>>> (retrying request) LBA=1364750271
>>> Nov 26 20:48:11 server kernel: ad4: FAILURE - WRITE_DMA48
>>> status=51 error=4 LBA=1364750271
>>> Nov 26 20:48:11 server kernel:
>>> g_vfs_done():ad4s1g[WRITE(offset=682932174848, length=131072)]error = 5
>>>
>>> So far, nothing serious has followed from these errors I know off. They
>>> only happen sporadically, during reboots.
>>>
>>> Are these to problems even related, or am I just unlucky? Anyone has some
>>> suggestions to fix them?
>>>
>>> Regards,
>>> Rick
>>>
>>>
>>>   
>> Unless there is some incompatibility between FreeBSD -> Your disk
>> controller -> Your disk, my best guess is you have a failing disk.  I
>> would also suggest you check cables, connections (I guess this is an
>> ATA disk so you may wish the check whether the flat cable is the
>> 80-conductor type and is plugged in correctly).
>> 
>
> The disk is a new SATA model (1TB Samsung), so that lessens the chances of
> the disk itself being defective somewhat. The mainboard is a MSI K9A2VM-F
> (AMD 780V / AMD SB700 chipsets)
>
>   

In fact, new disks *can* be faulty. Usually, the faults surface few days
/ weeks after initial use. I don't really trust a new disk on my system
until it runs for a couple of months. It will then run for years until
it reaches end-of-life due to wear.
I still suggest you try testing it with some programs like
sysutils/smartmontools

>> You did not mention the speed of you WAN connection, but FWIW I am
>> running a webserver behind a 1Mbps/256Kbps ADSL line and response is
>> good enough. SSH is definitely good enough to use in long vi sessions,
>> with lengthy documents.
>> 
>
> The connection is something similar. Should be no cause for the slowness.
>   

Since it works fine on the LAN, you need to check the router though.
Maybe some setting is slowing it down. Is it one of these cheap DSL
routers? You may want to turn off various features on the router like
firewalls, intrusion detections and so on (it goes without saying that
you will secure your FreeBSD system instead)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Temporarily blocking ports

[Manolis Kiagias]

Chris wrote:
>
> On Nov 29, 2008, at 1:11 PM, Jos Chrispijn wrote:
>
>>
>> From your reply on my message of 29-11-2008 21:47:
>>> An even tighter practice is to turn off all password logins and
>>> use only keyed connections. This is easier than it might seem
>>> though I'll admit I think of ssh as something only a select
>>> number of users may use and thus you know them by name
>>> and what IPs they are permitted to connect on.
>> I have been thinking of that as well, but don't think I should use
>> that yet with the knowledge I have on this.
>> Do you refer to manual of automatic key connections?
>>
> It's extremely easy.
>
> Generate your key and spread it to all systems you want
> to connect to. Have other users generate their key and do the
> same. After everyone is set, turn off password access in
> /etc/ssh/sshd_config, that file contains the docs in comments
> on how to do this. You change three parameters. Then sshd
> will need to be restarted. Be sure logins by key work first.
>
> This implies how to set up your keys. This was lifted from
> a helpful page on the net and modified but is pretty basic.
> Creates the keys in home directory of myuserid on system
> www.example.com, then moving the key to a second system
> called other.example.com such that myuserid can move
> between systems. The userid on the remote does not need
> to be the same string as on the local system though it's shown
> that way here.
>
> www$ cd # get to your home directory
> www$ ssh-keygen -t rsa
> Generating public/private rsa key pair.
> Enter file in which to save the key (/home/myuserid/.ssh/id_rsa):
> Enter passphrase (empty for no passphrase):
> Enter same passphrase again:
> Your identification has been saved in /home/myuserid/.ssh/id_rsa.
> Your public key has been saved in /home/myuserid/.ssh/id_rsa.pub.
> The key fingerprint is:
>  [EMAIL PROTECTED]
> www$ ssh [EMAIL PROTECTED] mkdir -p .ssh
> Password: 
> www$ cat .ssh/id_rsa.pub|ssh [EMAIL PROTECTED] 'cat >>
> .ssh/authorized_keys'
> Password:
>
> You are done setting up keys. Sample use of seamless login:
>
> www$ ssh other.example.com
> other$ host
> other.example.com
> other$ users
> myuserid  ttyp0Jul 14 05:28 (www.example.com)
> other$ exit
> www$
>
> I only use this on FreeBSD and OS-X. No idea on Putty and others.
>

Can be used on Putty too. There are some small helper programs you can
download along with Putty:

- Puttygen: This will convert your key to a format that can be used by putty
- Pageant: This works like  "ssh-agent". You simply supply the key, and
it is automatically used in your Putty connections

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

Re: Help me during Kernel Complie Command Error - make buildkernal KERNEL=KIMHYUN_KERNEL

[Manolis Kiagias]

Kim Hyun wrote:
> help me~my configuration kernel file is failed.
>
> my os is FreeBSD 7.2 Release
> my notebook's model is "Compaq Evo N150"
> memory ram is 311M
> cpu is "Intel pentium III (800.04-MHz 686-class CPU)"
>
>
> executig command 
> ===
> make buildkernal KERNEL=KIMHYUN_KERNEL
>
> ...
> ...
> /usr/src/sys/dev/fxp/if_fxp.c:87:23: error: miibus_if.h: No such file or
> directory
> mkdep: compile failed
> *** Error code 1
>
> Stop in /usr/obj/usr/src/sys/KIMHYUN_KERNEL.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
>   

You need 'device miibus' for fxp.
Uncomment this line in  your configuration file.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: freebsd-update problem 8.0Beta1 to 8.0Beta4

[Manolis Kiagias]

Fernando Apesteguía wrote:
> 2009/9/20 Fernando Apesteguía :
>   
>> Hi all,
>>
>> I'm having some problems trying to update from FreeBSD 8.0 Beta1 to 8.0 
>> Beta4.
>>
>> I upgraded from 7.2 to beta1 some time ago, using freebsd-update
>> without problems. Later
>> I did the same thing to reach beta2. Yesterday I tried it to get to
>> beta3 but I have a bunch
>> of errors like this one:
>>
>> /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory
>>
>> This is after the "preparing to download files" stage. I have plenty
>> of disk space left on my hard disk.
>> In an attempt to fix the problem I performed a rollback, so I went to
>> beta1 again. This process seemed
>> to work fine. However, whenever I try to upgrade to another higher
>> release number, I get those errors.
>>
>> Listing the contents of the /var/db/freebsd-update/files/ directory
>> shows a bunch of .gz files.
>> What can be wrong?
>>
>> I've googled, but I haven't been able to find a solution.
>> Any help?
>> Thanks in advance.
>> 
>
> Nobody on this issue?
> I've seen more people asking about this[1][2] but I couldn't find a solution.
>
> I made a back up of the /var/db/freebsd-update directory and renamed
> the files and merge directories. freebsd-update created them again,
> actually downloaded a bunch of files, but I got exactly the same
> error. I followed exactly the same procedure (described in the
> handbook) to go from 7.1 to 7.2 then to 8.0BETA1 and finally to
> 8.0BETA2. What is wrong with freebsd-update? If I did something wrong,
> how can I roll it back?
>
> Thanks for your time.
>
> [1] http://www.mail-archive.com/freebsd-questions@freebsd.org/msg214707.html
> [2] 
> http://lists.freebsd.org/pipermail/freebsd-questions/2009-January/190664.htm
>
>   

I encountered this once, and was not able to solve it, see here:

http://www.mail-archive.com/freebsd-questions@freebsd.org/msg186677.html

It was definitely not a disk / partition free space problem and it
manifested itself moving from RC to RELEASE.
In the end, I did a binary upgrade from CD. It has behaved ever since.

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

Announcing: FreeBSD 8.0-RC1 Custom XFCE build available

[Manolis Kiagias]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hey all,

For everyone who has been following my little project here:

http://freebsd-custom.wikidot.com

I am now pleased to announce the immediate availability of an 8.0-RC1
based XFCE custom DVD iso (i386 only).

Here are the direct download links:

http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/FreeBSD_8.0-RC1-XFCE-22092009.iso

Checksum and signature files:

http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/FreeBSD_8.0-RC1-XFCE-22092009.iso.CHECKSUM.MD5
http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/FreeBSD_8.0-RC1-XFCE-22092009.iso.CHECKSUM.SHA256
http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/FreeBSD_8.0-RC1-XFCE-22092009.iso.asc

Please note this is a test build of pre-release software, so treat
accordingly.  It has only been tested in VMWare so far, but I am about
to install as my main desktop soon as first tests were promising.

Make sure to read the README file:

http://freebsd.dev-urandom.com/iso/i386/xfce-desktop/README-8.TXT

as it contains important information on installation.

Note this release includes the latest openoffice 3.1.1 as well as
abiword / gnumeric for those who prefer them. Gnash has been dropped
(linux flash plugin works very well now) and avant-window-navigator is
also included (but is untested). Latest versions of well known
packages (gimp, inkscape, evince, firefox35 etc) are included as well.

As always, please report any problems, success stories, comments and
criticisms to mano...@freebsd.org

Thanks and happy FreeBSDing!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkq4um8ACgkQZ/MxGm4PtJR6CACeJO1PlVUOhutRFFPG5qduH1bE
As0AnR+CMYiMP0fhyPEwFgTDjhtVnoKP
=AcpI
-END PGP SIGNATURE-

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

Re: /dev files keep no permissions

[Manolis Kiagias]

herbs wrote:
> Hi Daemons,
> I wonder whats wrong there:
>
> I need to change the permissions from 
> /dev/speaker 600 to /dev/speaker 666
> --all works ok.
>
> Then I reboot the computer and the permissions of the file is back to 600.
>
> How to make it permanent? Is is normal that /dev files do what they
> want?
>
>   

Yes :)
The /dev filesystem is dynamic, it is recreated at every boot. For your
setting to persist, enter it in /etc/devfs.conf

The examples in there will help you out, although probably this is the
line you need:

perm speaker 0666
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Question about FreeBSD installation procedure

[Manolis Kiagias]

Bret Busby wrote:
> Hello.
>
> I have been interested in installing FreeBSD on my laptop (HP/Compaq
> NX5000, 2MB RAM), in a free 20MB partition.

I really hope you meant Gb here ;)

>
> I noticed that the Linux Format magazine to which I subscribe, in
> Issue 124, comes with FreeBSD 7.2 on the DVD.
>
>> From what I understand, FreeBSD (and possibly all BSD) uses hard disc
>> slices rather than partitions, and therefore cannot
> easily be installed in a free partition, but needs for hard disc
> slices to be used.

'Slice' is FreeBSD jargon for what Windows / DOS would call a 'primary
partition'. In short, FreeBSD can only be installed in your machine only
if you have free space *and* the possibility to create a primary
partition  in it .  Due to BIOS limitations, PC hardware only supports 4
primary partitions on any disk. 
If you already have 4 primary partitions and you are not willing to
delete one, you can't install FreeBSD as it won't install on what
Windows calls an "Extended partition".  But let's say you have a typical
laptop with two partitions for OS and data, and some free space at the
end. FreeBSD will happily install there.

>
> Is it yet possible to install FreeBSD into a hard disc partition,
> rather than needing to install into hard disc slices?
> I have attached a copy of the screenshot showing the partition table;
> I wanted to install FreeBSD into sda8.
>
> Can this be done.
>
> Thank you in anticipation.
>

The screenshot won't come through in the mailing list, if at all
possible upload it somewhere and send us a link.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: changing port options in Freebsd

[Manolis Kiagias]

Aflatoon Aflatooni wrote:
> What is the best way to change an option on an installed port? should I 
> deinstall and then reinstall with the updated options on the port?
>   

Yes.

> Also what was the command to change the options through make?
>   


make config. If you also wish to configure every dependency, use make
config-recursive. This is useful when you wish to run a port build
without attending every few minutes to press OK at the option dialogs
that pop up.
There are a lot more useful options in the manpages. Try man ports.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Question about FreeBSD installation procedure

[Manolis Kiagias]

Bret Busby wrote:
> On Sat, 26 Sep 2009, Manolis Kiagias wrote:
>
>>
>> Bret Busby wrote:
>>> Hello.
>>>
>>> I have been interested in installing FreeBSD on my laptop (HP/Compaq
>>> NX5000, 2MB RAM), in a free 20MB partition.
>>
>> I really hope you meant Gb here ;)
>>
>>>
>>> I noticed that the Linux Format magazine to which I subscribe, in
>>> Issue 124, comes with FreeBSD 7.2 on the DVD.
>>>
>>>> From what I understand, FreeBSD (and possibly all BSD) uses hard disc
>>>> slices rather than partitions, and therefore cannot
>>> easily be installed in a free partition, but needs for hard disc
>>> slices to be used.
>>
>> 'Slice' is FreeBSD jargon for what Windows / DOS would call a 'primary
>> partition'. In short, FreeBSD can only be installed in your machine only
>> if you have free space *and* the possibility to create a primary
>> partition  in it .  Due to BIOS limitations, PC hardware only supports 4
>> primary partitions on any disk.
>> If you already have 4 primary partitions and you are not willing to
>> delete one, you can't install FreeBSD as it won't install on what
>> Windows calls an "Extended partition".  But let's say you have a typical
>> laptop with two partitions for OS and data, and some free space at the
>> end. FreeBSD will happily install there.
>>
>>>
>>> Is it yet possible to install FreeBSD into a hard disc partition,
>>> rather than needing to install into hard disc slices?
>>> I have attached a copy of the screenshot showing the partition table;
>>> I wanted to install FreeBSD into sda8.
>>>
>>> Can this be done.
>>>
>>> Thank you in anticipation.
>>>
>>
>> The screenshot won't come through in the mailing list, if at all
>> possible upload it somewhere and send us a link.
>>
>
> See
> http://busby.net/bret/Screenshot--dev-sda-GParted.png
>
> However, with the response above, and, with all of the responses thus
> far, to the query, it appears that I cannot install FreeBSD on the
> computer, without a full system rebuild, involving removal of all of
> the installed operating systems and software from the computer, then
> repartitioning, or, slicing up, the hard drive, and then creating new
> logical, extended partitions, and then reinstalling each of the
> operating systems, and all of the software for each of the operating
> systems, trying to ensure that I then have at least all of the
> software that is currently installed on each operating system on the
> computer, and, the data that is currently present on the computer.

Judging from the screen shot, you should still be able to do it using
gparted to shuffle the partitions a bit. (I recommend using the gparted
or the parted magic live cd for this)
One possible way would be to delete sda8 and move the free space to the
end of the extended partition. Then resize the extended partition so the
free space is out of it. Create a primary partition out of the free
space (or let FreeBSD do it during install).
You still have primary partitions available, your current disk setup
includes one primary and one extended partition with many 'logical
partitions'. Granted, this will take some time but it will work.

>
> And, with being required to do all of that, I do not know what would
> happen, regarding issues such as the interrupt conflict that I
> encountered when trying to initially install Debian 3.1 on the
> computer, the interrupt conflict being between the WiFi card and the
> ethernet card, which reuired Ubuntu to resolve the conflict, then (at
> the time, as I was then a strictly Debian user) uninstalling Ubuntu to
> reinstall Debian 3.1, with the solution to the interrupt conflict,
> having used Mandriva Linux to do the partitioning, so as to retain the
> initial installation of MS Win XP, which I would probably lose, and
> have to install from scratch, as part of installing BSD on the system.

You could try simply booting the FreeBSD DVD or livefs CD and see what
devices get recognized and any potential problems, without committing to
installing anything.

>
> So, getting the system set up, initially, to get Debian 3.1 running
> (it has been superseded on the system, first by Debian 4, and, now, by
> Debian 5), took a fair bit of time and effort, and problem solving,
> using various operating systems, to get the one extra operating system
> installed.
>
> Due to the time and effort involved, and the apparent complexity, it
> all seems too difficult, to install BSD.
>

I would agree all this would be too difficult for someone doing a first

Re: just cloning

[Manolis Kiagias]

PJ wrote:
> Maybe this is what I really need since I want to set up 3 identical 7.2
> computers and back them up and update as needed. This should assure a
> minimum of headaches like what I have been experienceg lately.
> This link
> http://cabstand.com/usbflash.html
> seems to be about right, but I'd like to get some opinions on what would
> be the best way to go about this.
> I assume that I must do one difinitive installation on 1 computer. Then
> to clone, do I dump the partitions to a usb disk and restore to the
> other two computers; or do I follow the instructions on the above link.
> Obviously, it would be nice if it could be K.I.S.S.
>
>   

Can't tell about these instructions (would be nice to try them though)
but I can assure you I've used the dump/restore method numerous times
and it works great.
There are a few things one should take care of:

1. Don't forget to install MBR / boot blocks on your new disk after
restoring the dump(s)
(see also this post
http://lists.freebsd.org/pipermail/freebsd-questions/2009-July/201809.html)
2. Don't forget to manually create directories that you excluded from
your dump (like /dev /mnt)
3. Since you will (obviously) not dump /tmp don't forget to set the
sticky bit on it when you newfs and mount it - All sort of weird things
will happen if it is not set.
4. If the machines are identical it probably doesn't matter, but it
would be a good idea to label the partitions so you don't have to rely
on device names in fstab (as these change depending on the motherboard,
disk controller, sata connector used etc.), see
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-glabel.html

You can even restore by booting the FreeBSD live FS CD (or the DVD). As
I recall you may have to define TMPDIR to something writable (to a
directory in the USB disk you are using for the dumps) for restore to
work properly.  Restore will tell you about this if needed.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Updating the ports collection

[Manolis Kiagias]

Chris Stankevitz wrote:
>
> The FreeBSD handbook section 4.5.1 describes several methods for
> obtaining the ports collection including CVSup, Portsnap, and sysinstall.
>
> Section 4.5.1 also describes how to update the ports collection, but
> only for the CVSup and Portsnap methods.
>
> Q1: How do I update the ports collection after using sysinstall to
> obtain it?

You can use csup as explained in section 4.5.1.  This will update the
Ports Collection  you installed from CD/DVD
by fetching only the required newer files

Or, you can use portsnap too like this:

First time:
portsnap fetch extract

Subsequent times:
portsnap fetch update


If you are starting with an empty Ports tree (for example you skipped
installing it from CD during sysinstall) portsnap will be faster than
csup. (Note you can start with an empty tree and csup as well)

Anytime you decide to switch from csup to portsnap, always perform an
'extract'
>
> Q2: Is this explained in the handbook?  If so, where?
>

In section 4.5 as you noticed already. Portsnap is also revisited in
chapter 24:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-portsnap.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: gmirror, gjournal and glabel - which order?

[Manolis Kiagias]

Daniel Bye wrote:
> Hi all,
>
> I'm having a hard time trying to work out which order I should set up
> gmirror, glabel and gjournal on a new system. I want to journal my
> /home partition, label all the partitions for ease of reference, and
> use gmirror to save me in the event a disk goes bad. I am struggling
> to fit the pieces together conceptually in my mind. I understand the
> processes involved in setting each part separately - my problem is in
> trying to build this up in the right order so that it all makes sense.
>
> So far, I have labelled the primary drive and set up the journal. I have
> edited fstab to reflect the labels and journalled file system on /home.
> If I now build a mirror, don't I need to alter fstab to mount that and
> not the stuff in /dev/label? In which case, I guess I need to build the
> mirror first, and then set up labels and journals?
>
> I'm going round and round in circles here and none of the stuff I've
> read on the web enlightens me... :-/
>
> Any insights or suggestions would be taken as a great kindness!
>
> Dan
>
>   
When not mirroring,  I first create the journals and then label the
resulting ad.journal devices
In case you are doing a gmirror device, you would not really need the
separate label step - the gm device name won't change and gmirror is not
affected if the device names of the individual disks change (the disks
are marked as part of a mirror and scanned at startup).
When you are creating the composite gmirror device you are effectively
labeling it anyway i.e. gmirror label gm0...
Now if you follow the usual tutorials found in the web you would be
using gm0 / gm1 but you actually name it any way you wish.
If you really need to label the separate gmirrored partitions, do it
after setting up the mirror.

Concerning the order of journals and mirroring, I  create the journals
first, then mirror the result. This has always worked fine for me.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: GEOM label clarification

[Manolis Kiagias]

PJ wrote:
> If I understand correctly from the manual, giving the labels their slice
> name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that
> regardless of the disk, the boot will be from the disk being booted and
> not from another disk as happened to me recently - the fstab on disk ad4
> was referncing ad12 so the boot was from ad12 rather than ad4.
> The handbook says:
> "By permanently labeling the partitions on the boot disk, the system
> should be able to continue to boot normally, even if the disk is moved
> to another controller or transferred to a different system. For this
> example, it is assumed that a single ATA disk is used, which is
> currently recognized by the system as ad0."
> If the disk is moved to another system, it may no longer be ad0... So
> will it still boot correctly?
>
>   

In short, yes. I do this routinely all the time.
Assuming of course that the device is connected to a controller that
FreeBSD recognizes.
This should be a non-issue for standard ATA/SATA disks.

> Or should the ufsid labels be used?
>
>   

The ufsid is also an option if you do not wish to create the labels
yourself.
The advantage of user-created labels is that they are not 'cryptic' like
the ufsid ones
and you may actually remember them :)

> Will both of these contortions work?
>   

Yes, both will do.

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

Re: GEOM label clarification

[Manolis Kiagias]

PJ wrote:
> Manolis Kiagias wrote:
>   
>> PJ wrote:
>>   
>> 
>>> If I understand correctly from the manual, giving the labels their slice
>>> name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that
>>> regardless of the disk, the boot will be from the disk being booted and
>>> not from another disk as happened to me recently - the fstab on disk ad4
>>> was referncing ad12 so the boot was from ad12 rather than ad4.
>>> The handbook says:
>>> "By permanently labeling the partitions on the boot disk, the system
>>> should be able to continue to boot normally, even if the disk is moved
>>> to another controller or transferred to a different system. For this
>>> example, it is assumed that a single ATA disk is used, which is
>>> currently recognized by the system as ad0."
>>> If the disk is moved to another system, it may no longer be ad0... So
>>> will it still boot correctly?
>>>
>>>   
>>> 
>>>   
>> In short, yes. I do this routinely all the time.
>> Assuming of course that the device is connected to a controller that
>> FreeBSD recognizes.
>> This should be a non-issue for standard ATA/SATA disks.
>>
>>   
>> 
>>> Or should the ufsid labels be used?
>>>
>>>   
>>> 
>>>   
>> The ufsid is also an option if you do not wish to create the labels
>> yourself.
>> The advantage of user-created labels is that they are not 'cryptic' like
>> the ufsid ones
>> and you may actually remember them :)
>>
>>   
>> 
>>> Will both of these contortions work?
>>>   
>>> 
>>>   
>> Yes, both will do.
>>
>>   
>> 
> Thanks for the reassurance. Now to start labelling. Uh.. I guess that
> means that if I label 1 disk and then clone it to several others, they
> wil  all work from any system... Well, I guess I'll try it. Thanks again.
>
>
>   
How are going to clone it? Will the clone also  copy the labels?
For example, if doing a dump / restore (which I often do) I recreate the
partitions manually, newfs them, label them and then restore the
contents. In many cases I use a live (Fixit) system for this.

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

Re: GEOM label clarification

[Manolis Kiagias]

PJ wrote:
> NOW THIS SUCKS.
>
> SUM
>
> # glabel label rootfs/dev/ad12s1a
> glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted
>
> This is direct from the manual what the "<$#*(@)! is going on?
> No identical post on web, but similar say to ignore: "it's harmless?"
>
> I so, why is it there?
>
> There seem to be quite a lot of these kinds of stumbling blocks that are
> just plalin annoying...
>
> Is this an annoyance or what for the above situation?
>
>   

Is this your normal '/' filesystem, and is it mounted?
If it is reboot your system and select 'single user mode' from the
loader.menu
Then use glabel in the single user mode prompt.
This will not work if you just 'shutdown now', you have to reboot into
single user mode.

If it is not your real '/' at the moment, and it is not mounted, you
should be able to do it.
Booting from the fixit LiveCD will also work in any case.

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

Re: I hate to bitch but bitch I must

[Manolis Kiagias]

PJ wrote:
> Why is it that the manual pages, as thorough as they may be, are very,
> very confusing.
> Perhaps I am being too wary, but I find that too many 
> instructions/examples are stumbling blocks to appreciation of the whole
> system:
> for instance, let's look at the instructions for changing disk labels
> with glabel or is it tunefs ?
> man glabel(8):
>
> for UFS the file system label is set with
> tunefs(8)
> .
> what happened to glabel?
> man tunefs(8)
> The *tunefs* utility cannot be
> run on an active file system. To change an active file system, it must
> be downgraded to read-only or unmounted.
>
> So, you have to run tunefs from an active file system to modify another
> disk?
> but from man tunefs:
> BUGS
> This utility should work on active file systems.
> What in hades does this mean--just above it says cannot be run on active
> file systems. ???
>  To change the root file
> system, the system must be rebooted after the file system is tuned.
>
> You can tune a file system, but you cannot tune a fish.
> How cute... And fish eat bugs.
>
> Seriously, now to the manual:
> To create a permanent label for a UFS2 file system without destroying
> any data, issue the following command:
> # tunefs -L /home/ /dev/da3
>
> Oh? home is what? What does this have to do with the partitions?
> Here's from man glabel(8):
>
> EXAMPLES
> The following example shows how to set up a label for disk ``da2'', cre-
> ate a file system on it, and mount it:
> glabel label -v usr /dev/da2
> newfs /dev/label/usr
> mount /dev/label/usr /usr
> [...]
> umount /usr
> glabel stop usr
> glabel unload
>
> The next example shows how to set up a label for a UFS file system:
> tunefs -L data /dev/da4s1a
> mount /dev/ufs/data /mnt/data
>
> Am I to understand that glabel is only for a new system? What's with the
> newfs... I'm trying to set labels on an system that is already set up.
> And, the glabel examle above is not for UFS file systems? Oh, that's for
> tunefs?
> So why are we even dealing with this glabel?
>
> from manual:
> # tunefs -L /home/ //dev/da3/
> A label should now exist in /dev/ufs which may be added to /etc/fstab:
> /dev/ufs/home /home ufs rw 2 2
>
> Why? Is this necessary? and somewhere I saw "tunefs -L volume
> /dev/da0s1a" or something like that. Does that mean that each partition
> should be tunefsd? Maybe the guys who programmed this stuff understand;
> I sure don't. I just want to be able to set the labels according to what
> they say can be done... so shy not have a clear and concise explanation?
>
>   

Relax. You are having a bad day, and you are topping it by trying to
perform some stuff while you are not in the right state of mind.

If you do insist on continuing with this, do the following:
Make a list of your partitions - I'll assume a device name of /dev/ad1
for the disk. You should have:

ad1s1a for root => Label this as rootfs
ad1s1b for swap => Label this as swap
ad1s1e for tmp => Label this as tmpfs
ad1s1d for var => Label this as varfs
ad1s1f for usr => Label this as usrfs

If you are unsure of the device names, try ls /dev/ad* (or ls /dev/da*
if you are using SCSI disks, which I think you are not)

Now, reboot:
shutdown -r now
Press 4 and enter single user mode in the loader.
In the single user mode prompt type:

glabel label rootfs /dev/ad1s1a
glabel label swap /dev/ad1s1b
glabel label tmpfs /dev/ad1s1e
glabel label varfs /dev/ad1s1d
glabel label usrfs /dev/ad1s1f

You should get no error messages from these.
Type exit and continue to multiuser boot.

Change /etc/fstab:

change

 /dev/ad1s1a to /dev/label/rootfs
 /dev/ad1s1b to /dev/label/swap

and so on.

Reboot once again. Everything should work.

> Do people who write this stuff ever read it? Tell me t

Yes, we do. All the time actually.

> hat its clear and
> simple and to the point... so far, I have been running back and forth
> between half a dozen web pages trying to understand what is going on... 
> and doing things through a dense fog does not produce creative results!___
>
>   
You will have best results when trying with a clear mind.
Also having a test system (or a VMware / Virtualbox machine) will help
you learn and practice unknown procedures without the anxiety of
breaking something on your production system.



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

Re: GEOM label clarification

[Manolis Kiagias]

Polytropon wrote:
> On Sat, 17 Oct 2009 00:43:37 +0300, Manolis Kiagias  wrote:
>   
>> Is this your normal '/' filesystem, and is it mounted?
>> If it is reboot your system and select 'single user mode' from the
>> loader.menu
>> Then use glabel in the single user mode prompt.
>> This will not work if you just 'shutdown now', you have to reboot into
>> single user mode.
>> 
>
> Isn't it sufficient to unmount any partitions and keep /
> in -o ro mode, and then perform the glabel command, which
> is obviously best done in single user mode?
>
>   

I had variable results on a few systems and feel it is safest to perform
a clean single user mode boot.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: I hate to bitch but bitch I must

[Manolis Kiagias]

PJ wrote:
>
> Manolis, my state of mind is quite clear... and I'm coping with
> everything quite allright... I'm not about to get mad at anyone or
> anything...
> but tell me, honestly, when you see the stuff I have described above?
> Woldn't that confuse anyone in their right mind?
>
>   

I am sorry, but there is something here, either some mistake on your
part or some other weird problem on your system I can not think of.

I don't seem to remember glabel ever failing to store metadata, unless
1) The device is non-existing 2) The device is mounted.
As a matter of fact, I did the glabel stuff on a machine a few hours
ago. This was already fully installed, I rebooted single user and was
done in less than 2 minutes.
And yes, if you get a metadata error, it means nothing was done so you
are *not* to go and change fstab!

Could you  please send us /etc/fstab and the results of ls /dev/ad*


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

Re: I hate to bitch but bitch I must

[Manolis Kiagias]

PJ wrote:
> Manolis Kiagias wrote:
>   
>> PJ wrote:
>>   
>> 
>>> Manolis, my state of mind is quite clear... and I'm coping with
>>> everything quite allright... I'm not about to get mad at anyone or
>>> anything...
>>> but tell me, honestly, when you see the stuff I have described above?
>>> Woldn't that confuse anyone in their right mind?
>>>
>>>   
>>> 
>>>   
>> I am sorry, but there is something here, either some mistake on your
>> part or some other weird problem on your system I can not think of.
>>
>> I don't seem to remember glabel ever failing to store metadata, unless
>> 1) The device is non-existing 2) The device is mounted.
>> As a matter of fact, I did the glabel stuff on a machine a few hours
>> ago. This was already fully installed, I rebooted single user and was
>> done in less than 2 minutes.
>> And yes, if you get a metadata error, it means nothing was done so you
>> are *not* to go and change fstab!
>>
>> Could you  please send us /etc/fstab and the results of ls /dev/ad*
>>   
>> 
> Here are the outputs:
>
> fstab:
> # DeviceMountpointFStypeOptionsDumpPass#
> /dev/ad12s1bnoneswapsw00
> /dev/ad12s1a/ufsrw11
> /dev/ad12s1h/backupsufsrw22
> /dev/ad12s1g/homeufsrw22
> /dev/ad12s1d/tmpufsrw22
> /dev/ad12s1f/usrufsrw22
> /dev/ad12s1e/varufsrw22
> /dev/acd0/cdromcd9660ro,noauto00
> linproc  /usr/compat/linux/proc linprocfs rw 0 0
>
> df:
> Filesystem   1K-blocksUsedAvail Capacity  Mounted on
> /dev/ad12s1a   2026030  319112  154483617%/
> devfs1   10   100%/dev
> /dev/ad12s1h  50777034   4 46714868 0%/backups
> /dev/ad12s1g  50777034 6276538 4043833413%/home
> /dev/ad12s1d   4058062  36  3733382 0%/tmp
> /dev/ad12s1f  50777034 5729324 4098554812%/usr
> /dev/ad12s1e   2026030  176070  1687878 9%/var
> linprocfs4   40   100%/usr/compat/linux/proc
>
> # ls /dev/ad*
> crw-r-  1 root  operator0,  97 Oct 17 16:36 /dev/ad0
> crw-r-  1 root  operator0, 103 Oct 17 16:36 /dev/ad0s1
> crw-r-  1 root  operator0, 101 Oct 17 16:36 /dev/ad10
> crw-r-  1 root  operator0, 106 Oct 17 16:36 /dev/ad10s1
> crw-r-  1 root  operator0, 121 Oct 17 16:36 /dev/ad10s1a
> crw-r-  1 root  operator0, 122 Oct 17 16:36 /dev/ad10s1b
> crw-r-  1 root  operator0, 123 Oct 17 16:36 /dev/ad10s1c
> crw-r-  1 root  operator0, 124 Oct 17 16:36 /dev/ad10s1d
> crw-r-  1 root  operator0, 125 Oct 17 16:36 /dev/ad10s1e
> crw-r-  1 root  operator0, 126 Oct 17 16:36 /dev/ad10s1f
> crw-r-  1 root  operator0, 127 Oct 17 16:36 /dev/ad10s1g
> crw-r-  1 root  operator0, 102 Oct 17 16:36 /dev/ad12
> crw-r-  1 root  operator0, 107 Oct 17 16:36 /dev/ad12s1
> crw-r-  1 root  operator0, 128 Oct 17 16:36 /dev/ad12s1a
> crw-r-  1 root  operator0, 129 Oct 17 16:36 /dev/ad12s1b
> crw-r-  1 root  operator0, 130 Oct 17 16:36 /dev/ad12s1c
> crw-r-  1 root  operator0, 131 Oct 17 16:36 /dev/ad12s1d
> crw-r-  1 root  operator0, 132 Oct 17 16:36 /dev/ad12s1e
> crw-r-  1 root  operator0, 133 Oct 17 16:36 /dev/ad12s1f
> crw-r-  1 root  operator0, 134 Oct 17 16:36 /dev/ad12s1g
> crw-r-  1 root  operator0, 135 Oct 17 16:36 /dev/ad12s1h
> crw-r-  1 root  operator0,  99 Oct 17 16:36 /dev/ad4
> crw-r-  1 root  operator0, 104 Oct 17 16:36 /dev/ad4s1
> crw-r-  1 root  operator0, 108 Oct 17 16:36 /dev/ad4s1a
> crw-r-  1 root  operator0, 109 Oct 17 16:36 /dev/ad4s1b
> crw-r-  1 root  operator0, 110 Oct 17 16:36 /dev/ad4s1c
> crw-r-  1 root  operator0, 111 Oct 17 16:36 /dev/ad4s1d
> crw-r-  1 root  operator0, 112 Oct 17 16:36 /dev/ad4s1e
> crw-r-  1 root  operator0, 113 Oct 17 16:36 /dev/ad4s1f
> crw-r-  1 root  operator0, 114 Oct 17 16:36 /dev/ad4s1g
> crw-r-  1 root  operator0, 100 Oct 17 16:36 /dev/ad6
> crw-r-  1 root  operator0, 105 Oct 17 16:36 /dev/ad6s1
> crw-r-  1 root  operator0, 115 Oct 17 16:36 /dev/ad6s1a
> crw-r-  1 root  operator0, 116 Oct 17 16:36 /dev/ad6s1b
> crw-r-  1 root  operator0, 117 Oct 17 16:36 /dev/ad6s1c
> crw-r-  1 root  operator0, 118 Oct 17 16:36 /dev/ad6s1

Re: I hate to bitch but bitch I must

[Manolis Kiagias]

PJ wrote:
>
> manual: "it is assumed that a single ATA disk is used, which is
> currently recognized by the system as ad0. It is also assumed that the
> standard FreeBSD partition scheme is used, with /, /var, /usr and /tmp
> file systems, as well as a swap partition."
>
> Now, does that mean that glabel does not work if there are several disks
> on the system... it certainly does not say so nor does it adv ertise
> that this would not work if there are several ATA disks present..
> Previously I had also tried a reboot press 4 with exactly the same
> results
>
>   

It does say "Example" on top.
And then again:

For this *example* it is assumed that a single ATA disk is used,...

It doesn't say what will not work with it. It simply assumes some
defaults to give a reasonable example.
Now, don't tell me this is ambiguous too...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: I hate to bitch but bitch I must

[Manolis Kiagias]

Matthew Seaman wrote:
> Manolis Kiagias wrote:
>> PJ wrote:
>
>>> Now, does that mean that glabel does not work if there are several
>>> disks
>>> on the system... it certainly does not say so nor does it adv ertise
>>> that this would not work if there are several ATA disks present..
>>> Previously I had also tried a reboot press 4 with exactly the same
>>> results
>
>> Aha, as I said above then.
>> If you've done this and you are still getting the can't store metadata
>> message,
>> I am really out of ideas.
>
> Just a WAG, but
>
> sysctl kern.geom.debugflags=16
>
> possibly?
>
> Cheers,
>
> Matthew
>

Ha, yes, the "shoot in the foot" sysctl :)
Shouldn't be needed though - I was labelling a boot disk about half an
hour ago and nothing else than pure 'glabel label' was required.
There must be something else that stops it.

Maybe running glabel with -v will help the OP (hopefully with a more
detailed error message)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: I hate to bitch but bitch I must

[Manolis Kiagias]

PJ wrote:

(trimmed down)
>
> Is entirely possible that I mucked up somewhere and did not do the
> shutdown -r quite right... anyway, it is working fine now.
> I still have some minor questions, though...
> Can glabel be done on a dormant file system and then boot that file
> system to change the fstab? 

You mean glabel the file system but still leave it as a normal device
name in fstab?
Sure, no problem there. The file system can either be mounted using it's
/dev/adXX (or /dev/daXX)
device name, it's label, or even the ufsid (assuming it is a UFS
filesystem, see the section below the glabel example)
So basically you can reboot after creating the label without changing
the fstab if you wish and change it later when you are certain that
glabel worked as you expected.

> I would think that that would be about the
> same things ad doing it from a mounted system in SUM.
> Then, the last question... where does tunefs really come in? .. I ask
>   

As others have said (and as explained in Handbook section 19.6.1) tunefs
can only create labels for UFS filesystems. Glabel on the other hand is
not filesystem specific, you can label anything (for example, you have
already labeled the swap space which clearly is not a file system). That
makes glabel more suitable IMHO when the purpose is to completely
replace the device names in fstab.

So in short:

- If you wish to create permanent labels for anything including swap
space and 'alien' filesystems as well as UFS, use 'glabel label'
- If you wish to create temporary labels for anything including swap
space and 'alien' filesystems as well as UFS, use 'glabel create' (I
doubt this is very useful, but it is an option)
- If you wish to create permanent labels for UFS filesystems *only* you
have the option of using tunefs.
- If you do not wish to create labels yourself and you are only
interested in mounting UFS filesystems without using the device names,
you can use the ufsid labels that are created automatically when the
filesystem is first created.

>From all the solutions, the only  one that covers both UFS and the swap
space and is permanent is the 'glabel label' command (hence the example
in the Handbook)

I hope this clears it up :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Mouse and keyboard don't work in Xorg 7.4

[Manolis Kiagias]

Andrey Zhidenkov wrote:
> I've installed FreeBSD 7.2 with Xorg 7.4 server, but mouse (usb)
> and keyboard don't work. when I start X server the only way to exit
> is Ctrl-Alt-F* and kill the process.
>
> I've find out that Xorg now uses hal and dbus to configure mouse and
> maybe this is a problem.
>   

It will probably work fine if you add the following two lines into
/etc/rc.conf and reboot:

dbus_enable="YES"
hald_enable="YES"

Have  a look at the updated Handbook section that describes this
procedure in more detail:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Mouse and keyboard don't work in Xorg 7.4

[Manolis Kiagias]

Andrey Zhidenkov wrote:
> On Mon, Oct 19, 2009 at 10:30:27PM +0300, Manolis Kiagias wrote:
>   
>> Andrey Zhidenkov wrote:
>> 
>>> I've installed FreeBSD 7.2 with Xorg 7.4 server, but mouse (usb)
>>> and keyboard don't work. when I start X server the only way to exit
>>> is Ctrl-Alt-F* and kill the process.
>>>
>>> I've find out that Xorg now uses hal and dbus to configure mouse and
>>> maybe this is a problem.
>>>   
>>>   
>> It will probably work fine if you add the following two lines into
>> /etc/rc.conf and reboot:
>>
>> dbus_enable="YES"
>> hald_enable="YES"
>> 
> I've added yet, but it doesn't helps ;(. And when I reboot I can't found any
> hald or dbus messages in dmesg.
>
>   
>> Have  a look at the updated Handbook section that describes this
>> procedure in more detail:
>>
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html
>> 
> Thank you, I've readed.
>   

I also noticed you have a ServerFlags section with "AutoAddDevices off"
Could you try removing this and see if it works?
You may in fact try running X without an xorg.conf at all.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: WD External Disc Drive

[Manolis Kiagias]

Rob Hurle wrote:
> Dear All,
>
>   This may sound like a Windows problem, but please read on.  I made a
> mistake and bought a WD "My Passport" external 350GB disc drive for
> use on several Windows machines, on some of which I don't have admin
> access, and a couple of FreeBSD systems.
>
>   On first use on Windows the disc shows up only as a virtual CD (I
> assume this is the firmware), "unlock.exe" has to be run and the
> software installed (admin privileges necessary).  Once it's unlocked
> and the software installed, the big disc appears, the software can be
> uninstalled, and the big disc reformatted as NTFS.  From then on, the
> virtual CD can be ignored and the big disc used on any Windows system.
>
>   Now to FreeBSD.  The newly formatted (as NTFS) disc appears as two
> devices - /dev/cd0 (never seen this before)

This is how a USB cdrom appears to FreeBSD - as a SCSI device. No
problem there.

>  and /dev/da0s1 (the normal
> USB disc drive device).  They can be mounted as follows:
>
> freebsd [10:45] ~#mount_udf /dev/cd0 /mnt
> freebsd [10:45] ~#mount /usb0
>
> (/etc/fstab describes the NTFS file system type, and the virtual CD is
> a UDF file system).  We now have:
>
> freebsd [10:46] ~#df
> Filesystem 1K-blocksUsed   Avail  Capacity  Mounted on
> /dev/cd0582962582962 0   100%/mnt
> /dev/da0s1  311877845  2332729 309545116   1%/usb0
>
> If we look at each device, the virtual CD has the WD software, as expected:
>
> freebsd [10:45] ~#ll /mnt
> total 6300
> drwxr-xr-x   3 501  staff 2048 12 Sep  05:32  Extras
> -rwxrwxrwx  1 501  staff   3680544  5 Sep   08:20  Unlock.exe
> drwxrwxrwx  5 501  staff2048  5 Sep   08:30  User Manuals
> drwxr-xr-x3 501  staff2048 12 Sep  05:28  WD SmartWare
> -rwxrwxrwx  1 501  staff   2770208  5 Sep   08:20  WD SmartWare.exe
> -rwxrwxrwx  1 501  staff   695 19 Jun03:06  What is this.html
> -rwxrwxrwx  1 501  staff 88 19 Jun07:12  autorun.inf
>
> No problem.  Now for the FreeBSD problem.  If we look at what's on the
> big disc (newly formatted as NTFS on a Windows system):
>
> freebsd [10:45] ~#ll /usb0
> total 75200
> -rwxrwxrwx  1 root  wheel   2560 23 Apr  2009 $AttrDef
> -rwxrwxrwx  1 root  wheel 0 25 Oct 14:37 $BadClus
> -rwxrwxrwx  1 root  wheel 9746184 23 Apr  2009 $Bitmap
> -rwxrwxrwx  1 root  wheel   8192 25 Oct 14:37 $Boot
> drwxrwxrwx  1 root  wheel0 25 Oct 14:37 $Extend
> -rwxrwxrwx  1 root  wheel   67108864 25 Oct 14:37 $LogFile
> -rwxrwxrwx  1 root  wheel   4096 25 Oct 14:37 $MFTMirr
> -rwxrwxrwx  1 root  wheel 0 23 Apr  2009 $Secure
> -rwxrwxrwx  1 root  wheel   131072 23 Apr  2009 $UpCase
> -rwxrwxrwx  1 root  wheel 0 25 Oct 14:37 $Volume
> drwxrwxrwx  1 root  wheel0 25 Oct 15:54 MyStuff
> drwxrwxrwx  1 root  wheel0 25 Oct 16:23 RECYCLER
> drwxrwxrwx  1 root  wheel0 25 Oct 14:37 System Volume
> Information
>
> The only thing that shows up in Windows is the "MyStuff" directory,
> which I put there.  I can copy anything from "MyStuff" to anywhere
> else on the FreeBSD system, no worries.  But if I attempt to copy a
> new file into the "MyStuff" directory, I get the following:
>
> freebsd [10:46] ~#cp ~/tmp/test /usb0/MyStuff
> cp: /usb0/MyStuff/test: No such file or directory
> freebsd [11:08] ~#
>
>   

You are using the ntfs driver that is built-in the FreeBSD kernel. This
is read only - you will be able to read from the disc, but not write to it.

In order to be able to write to this disc, install sysutils/fusefs-ntfs
and use the ntfs-3g command to mount your disk.
If you are not going to use the disc to transfer data between Windows
and FreeBSD, I would advise you to repartition the disk and create an
NTFS partition for your windows data and a FreeBSD partition in UFS
format.  Just backup any data, and use windows disk management to create
an appropriately sized NTFS partition, leaving the rest of the disk
unallocated. Then use fdisk and bsdlabel (or sysinstall) in FreeBSD to
create a slice and partition for FreeBSD.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: WD External Disc Drive

[Manolis Kiagias]

Rob Hurle wrote:
>
>
>   Thanks for your comments too, about use of the FAT32 file system.  I
> had thought about that, but the NTFS seemed to be a bit more universal
> - I'm not sure that FAT file systems are recognised by default on Macs
> (for example).
>
>   
FAT (and almost to the same extent, FAT32) are widely recognizable:
FreeBSD, Windows, Linux, OS X.
The most important limitation though is maximum file size (<=4GB).
Depending on your usage, FAT32 may or may not be appropriate because of
this.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Effing HAL

[Manolis Kiagias]

Bruce Cran wrote:
> On Thu, 29 Oct 2009 23:15:08 +
> Freminlins  wrote:
>
>   
>> Yeah, thanks for that. I knew about that file, but don't often read
>> it. There's even more to the saga - Xkblayout doesn't work. This
>> whole HAL thing stinks horribly. IF X is built with HAL basically
>> certain options specified in xorg.conf no longer work. HAL thinks it
>> knows best. But it doesn't, cos it's broken.
>> 
>
> Xkblayout doesn't work because you need to use fdi files now.
> http://ubuntuforums.org/showthread.php?t=948154
> has some details - essentially you need to put some XML
> in /usr/local/etc/hal/fdi/policy/ that tells it what layout to use.
> It's rather frustrating that information is scattered in forums - I
> couldn't see any official-looking articles on configuring it.
>
>   
You were not looking in the right place then:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: freebsd 6.4 can't load kernel after upgrade

[Manolis Kiagias]

oscar Seo wrote:
> I'm a beginner in freebsd.
> my machine consists of freebsd-6.4 + i386 bootstrap loader,+ windowmaker
> after upgrade freebsd-6.4 using sysinstall then reboot the system,
> I got an error message as follows
> +++
> Loading /boot/defaults/loader.conf
> Unable to load a kernel!
> /
> can't load 'kernel'
>
> Type '?' for a list of commands, 'help' for more detailed help.
> OK _
> +++
>
> so I decided to reinstall freebsd-6.4 but I can't boot and re-install
> freebsd using CD-rom.
> what shall I do boot my system using installed freebsd or live-CD ?
> Thanks...
>
>   
You could try loading your old kernel. When you build a new kernel, your
old kernel is preserved under /boot/kernel.old

Type these commands in the loader prompt

unload (probably not needed here)
load kernel.old
boot

See section 12.3.3.3 for more examples and details

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html#BOOT-LOADER

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

Re: best way to install/update software and firewall choice

[Manolis Kiagias]

Guy Marcenac wrote:
> Hi,
>
> I am an old debian user and I am looking at freebsd for security reasons
> * I am very interested in the jail concept
> * I have to relearn iptables syntax each time I want to add a rule

Don't we all :)

>
> I am testing the system in vmware virtual machine.
>
> There is a point I don't fully understand. There are several ways of
> updating the system, from precompiled binaries or by recompiling the
> system and the ports (and using csup, portsnap, portupgrade ...).

To update your base system, you can use freebsd-update. This uses
precompiled binaries and also updates the relevant sources (assuming you
have them installed beforehand and you are using the default
freebsd-update configuration - which is recommended). However if you are
going to run jails, this advantage is more less defeated: you will have
to run 'make buildworld' anyway to install the result in the jails.

> I would prefer to use the first way because it is really faster, but
> it seems to me that when I want to update my jails, there is no other
> easy way than recompiling the whole world into my jails.
>
Yes, unless you can somehow run freebsd-update from inside a jail :)
Don't know if this will work though. It will probably fail trying to
patch the kernel.

If you use freebsd-update you will only 'make installworld' for the
jails, as the 'host' will be taken care of by freebsd-update binary
patching.  You still need the make buildworld step, so you don't really
gain much.

> The other point a bit confusing is that I dont know which firewall to
> use. My first guess would be to use pf, because it exists also on
> openbsd, but it seems that the default would go to ipfw.
>

I am using pf too. It is a matter of preference and features needed. I
suggest you read the Handbook chapter and decide for yourself.

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