Date: Mon, 30 Mar 2009 12:32:49 +0000 From: =?windows-1254?Q?ZEKAY=DD_TOPCU?= <zekayi_@hotmail.com> To: <freebsd-questions@freebsd.org> Subject: RE: freebsd-questions Digest, Vol 253, Issue 1 Message-ID: <BAY124-W5091434C10067554AD4E10958D0@phx.gbl> In-Reply-To: <20090330120021.DF3FE10656BF@hub.freebsd.org> References: <20090330120021.DF3FE10656BF@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
artık bu e mail den bıktım almak istemiyorum allah allah silin yaaaaaaaa
Zekayi TOPCU
Sağlık Müdürlüğü
V.H.K.İ
Bilgi İşlem Şub.Md.
Cep :0 545 2676379
> From: freebsd-questions-request@freebsd.org
> Subject: freebsd-questions Digest, Vol 253, Issue 1
> To: freebsd-questions@freebsd.org
> Date: Mon, 30 Mar 2009 12:00:21 +0000
>
> Send freebsd-questions mailing list submissions to
> freebsd-questions@freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> or, via email, send a message with subject or body 'help' to
> freebsd-questions-request@freebsd.org
>
> You can reach the person managing the list at
> freebsd-questions-owner@freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-questions digest..."
>
>
> Today's Topics:
>
> 1. Re: [OT] - Best Practices(TM) for Configuration File Changes
> (Giorgos Keramidas)
> 2. Re: [OT] - Best Practices(TM) for Configuration File Changes
> (Glen Barber)
> 3. Re: [OT] - Best Practices(TM) for Configuration File Changes
> (Roland Smith)
> 4. Re: [OT] - Best Practices(TM) for Configuration File Changes
> (Glen Barber)
> 5. Re: Can't upgrade to 7.1-RELEASE (Jerry McAllister)
> 6. Re: [OT] - Best Practices(TM) for Configuration File Changes
> (Roger Olofsson)
> 7. Re: Software installasion (Was: Re: Wine without X)
> (Barnaby Scott)
> 8. Re: Can't upgrade to 7.1-RELEASE (Reinis Ivanovs)
> 9. Re: Software installasion (Was: Re: Wine without X) (Paul Schmehl)
> 10. Re: analyzing httpd-error.log (Charles Howse)
> 11. init panic in freebsd 7.1 (Tsu-Fan Cheng)
> 12. Re: Software installasion (Was: Re: Wine without X) (User Wblock)
> 13. Re: init panic in freebsd 7.1 (Polytropon)
> 14. Re: analyzing httpd-error.log (Glen Barber)
> 15. Webcam support in FreeBSD? (Yuri)
> 16. Re: Binary upgrade 7.1 i386 -> amd64 ? (Frederique Rijsdijk)
> 17. Re: analyzing httpd-error.log (Charles Howse)
> 18. Newsyslog mode on /var/log/security? (Roger Olofsson)
> 19. 6.x -> 7.1 (Grant Peel)
> 20. Re: 6.x -> 7.1 (fquest)
> 21. Where is the Perl XML::Parser port (af300wsm@gmail.com)
> 22. RE: Webcam support in FreeBSD? (Ramiro Caso)
> 23. Re: Where is the Perl XML::Parser port (Paul B. Mahol)
> 24. Re: Where is the Perl XML::Parser port (Anton Yuzhaninov)
> 25. Re: Newsyslog mode on /var/log/security? (Garance A Drosehn)
> 26. Cleaning up multiplicates in elf ldconfig path (Parv)
> 27. configuring the freebsd boot manager (Brett Wigins)
> 28. RE: configuring the freebsd boot manager (Ramiro Caso)
> 29. WireLess USB modem not detected . (dhaneshk k)
> 30. Re: Newsyslog mode on /var/log/security? (Roger Olofsson)
> 31. Re: Newsyslog mode on /var/log/security? (Garance A Drosehn)
> 32. installing freebsd 7.1 ( error mounting /dev/acd0
> input/output error) (ajeesh joseph)
> 33. Re: Stock OpenSSL is multithread or not? (Olivier Nicole)
> 34. Re: Cleaning up multiplicates in elf ldconfig path (Parv)
> 35. Re: configuring the freebsd boot manager (caleb)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 29 Mar 2009 15:11:54 +0300
> From: Giorgos Keramidas <keramida@ceid.upatras.gr>
> Subject: Re: [OT] - Best Practices(TM) for Configuration File Changes
> To: Glen Barber <glen.j.barber@gmail.com>
> Cc: freebsd-questions@freebsd.org
> Message-ID: <87bprkbkad.fsf@kobe.laptop>
> Content-Type: text/plain; charset=us-ascii
>
> On Sun, 29 Mar 2009 07:37:27 -0400, Glen Barber <glen.j.barber@gmail.com> wrote:
> > Hello, list.
> >
> > Before I pose my question, I am not intending to start a flame-war of
> > any sort -- I'm just searching for "different" ways of doing things.
> >
> > With so many different version control systems available (aside from
> > the traditional "keep current backups" solution), I am curious:
> >
> > Q: What is *your* favorite/suggestion solution to keep (working)
> > versions of configuration files, in case something goes awry?
> >
> > I am specifically targeting configuration files because they are what
> > I change the most, in avoidance of "It worked 10 minutes ago..."
> > situations.
>
> The base system of FreeBSD includes RCS[1]. I regularly use it to
> track changes to individual files. The advantage of RCS is that it is
> easy to use from a system that is barely `up', i.e. a system that has
> just been brought up to single user mode. No special daemons or other
> sort of service is required, no ports to be installed, and so on. I
> can usually just run something like:
>
> [1] http://www.gnu.org/software/rcs/
>
> # cd /boot
> # rlog loader.conf
>
> RCS file: RCS/loader.conf,v
> Working file: loader.conf
> head: 1.5
> branch:
> locks: strict
> access list:
> symbolic names:
> keyword substitution: kv
> total revisions: 5; selected revisions: 5
> description:
> ----------------------------
> revision 1.5
> date: 2009/03/27 17:58:59; author: root; state: Exp; lines: +2 -1
> Autoload acpi_ibm.ko for the extra Thinkpad X61s tunables.
> ----------------------------
> [more output snipped]
> #
>
> Whenever I want to look at a change, I can use `rcsdiff':
>
> # cd /boot
> # rcsdiff -u -r1.4 loader.conf
> ===================================================================
> RCS file: RCS/loader.conf,v
> retrieving revision 1.4
> diff -u -r1.4 -r1.5
> --- loader.conf 2009/02/17 20:26:14 1.4
> +++ loader.conf 2009/03/27 17:58:59 1.5
> @@ -9,6 +9,7 @@
> legal.intel_iwn.license_ack=1
>
> # Autoloaded modules.
> +acpi_ibm_load="YES"
> snd_hda_load="YES"
> #zfs_load="YES"
> if_iwn_load="YES"
> #
>
> The co(1) and ci(1) utilities are relatively easy to learn. Whenever
> a permanent change has to be made, I can use:
>
> # cd /path/to/file
> # rcsdiff -u filename
>
> If this shows changes they are probably uncommitted changes I have
> made without recording when or why. This is usually an indication of
> some sort of 'temporary hack'. I review the diff, and either commit
> it or throw it away. Then I check out a clean copy of the file, make
> the new permanent changes, review the changes one last time with the
> `rcsdiff' command, and commit them again.
>
> # co -l filename
> # vi filename
> # rcsdiff -u filename
> # ci -l filename
>
> As an extra bonus, when a system is fully up and running, there is
> very good integration of RCS with GNU Emacs, so I can edit the files
> directly from my Emacs session, view diffs with older revisions, roll
> a bunch of files back or forward through history, and do whatever else
> is supported by the VC mode[2] of Emacs:
>
> [2] http://www.emacswiki.org/cgi-bin/wiki/VersionControl
>
> RCS is not really 'modern', i.e. it does not support changesets with
> multiple files (each file has its own separate, per-file history), and
> it does not support elaborate file merging techniques (like some of
> the modern distributed VC systems). But it is always there, it does
> the Right Thing with file permissions and file ownership, and is well
> integrated with my favorite editor. That's more than enough for now :)
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 29 Mar 2009 08:24:09 -0400
> From: Glen Barber <glen.j.barber@gmail.com>
> Subject: Re: [OT] - Best Practices(TM) for Configuration File Changes
> To: raggen@raggens.net
> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
> Message-ID:
> <4ad871310903290524h70086066id9e3b16a763a9282@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi, Roger
>
> On Sun, Mar 29, 2009 at 8:20 AM, Roger Olofsson <240olofsson@telia.com> wrote:
> > For local configuration files there's a tool called rcs that can be used for
> > tracking changes and rollback.
> >
> > It's a part of the FreeBSD base system. Check the man pages for rcs(1) ci(1)
> > co(1) rcsdiff(1) and rcsintro(1) - rcsintro(1) is probably where you want to
> > start.
> >
> > It's also available on other *nix systems like AIX, Red Hat, Solaris etc.
> >
>
> I received a reply (off-list) mentioning the same tool. My response was:
>
> I was fairly certain that I would get rcs in a reply. I haven't used
> it too extensively, but it seems similar to cvs / svn -- which I
> personally like. I was more curious if people actually do use rcs for
> this purpose.
>
> It appears rcs is the "right tool for the job."
>
> Thanks for the reply!
>
> --
> Glen Barber
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 29 Mar 2009 14:45:24 +0200
> From: Roland Smith <rsmith@xs4all.nl>
> Subject: Re: [OT] - Best Practices(TM) for Configuration File Changes
> To: Glen Barber <glen.j.barber@gmail.com>
> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
> Message-ID: <20090329124524.GA48814@slackbox.xs4all.nl>
> Content-Type: text/plain; charset="us-ascii"
>
> On Sun, Mar 29, 2009 at 07:37:27AM -0400, Glen Barber wrote:
> > Hello, list.
> >
> > Before I pose my question, I am not intending to start a flame-war of
> > any sort -- I'm just searching for "different" ways of doing things.
> >
> > With so many different version control systems available (aside from
> > the traditional "keep current backups" solution), I am curious:
> >
> > Q: What is *your* favorite/suggestion solution to keep (working)
> > versions of configuration files, in case something goes awry?
> >
> > I am specifically targeting configuration files because they are what
> > I change the most, in avoidance of "It worked 10 minutes ago..."
> > situations.
>
> My configuration files are kept in git managed directories under
> ~/setup/<hostname>. Every <hostname> directory is its own
> repository. The reason that I'm using git is because it does what I
> need, is small and fast and doesn't require an external reporitory. For
> configuration files which are usually plain text all revision control
> systems would probably work OK.
>
> Every directory contains two perl scripts, check.pl and install.pl that
> respectively check the differences between files in the repository and
> in the filesystem and install files. Both these programs read a file
> called 'filelist.<username>'. This is a text file that has on every line
> a file in the reposirory, a permission, and its location in the
> filesystem (e.g. under /etc or /usr/local/etc for user root, or in $HOME
> for other users) and any post-install commands. Both scripts only
> process the filelists for the user that is running the script.
>
> Excerpt from filelist.root:
>
> # List of files that should be installed as root,
> # with their install locations.
> # Time-stamp: <2009-03-04 20:52:39 rsmith>
> # setup file perm system file commands
> etc/login.conf 644 /etc/login.conf cap_mkdb /etc/login.conf
> etc/make.conf 644 /etc/make.conf
> etc/manpath.config 644 /etc/manpath.config
> etc/master.passwd 600 /etc/master.passwd pwd_mkdb -p /etc/master.passwd
> etc/mergemaster.rc 644 /etc/mergemaster.rc
> etc/named.conf 644 /var/named/etc/namedb/named.conf
> etc/ntp.conf 644 /etc/ntp.conf /etc/rc.d/ntpd restart
>
> The file from the first column is installed in the location in the third
> column with the permissions listed in the second column. The rest of the
> line (if any) is interpreted as a list of commands and executed by a subshell.
>
> This system makes it easy to see if there are any differences between
> the configuration files in the repository and the real configuration
> files (e.g. after a mergemaster run). And it can install every file in
> its correct place. It also makes sure that users can only install their
> own files, by reading only that user's filelist.
>
> Roland
> --
> R.F.Smith http://www.xs4all.nl/~rsmith/
> [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
> pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 196 bytes
> Desc: not available
> Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20090329/17038cb5/attachment-0001.pgp
>
> ------------------------------
>
> Message: 4
> Date: Sun, 29 Mar 2009 08:57:31 -0400
> From: Glen Barber <glen.j.barber@gmail.com>
> Subject: Re: [OT] - Best Practices(TM) for Configuration File Changes
> To: Roland Smith <rsmith@xs4all.nl>
> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
> Message-ID:
> <4ad871310903290557v781c634fl6c8da854ea817ba8@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi, Roland.
>
> On Sun, Mar 29, 2009 at 8:45 AM, Roland Smith <rsmith@xs4all.nl> wrote:
> >
> > My configuration files are kept in git managed directories under
> > ~/setup/<hostname>. Every <hostname> directory is its own
> > repository. The reason that I'm using git is because it does what I
> > need, is small and fast and doesn't require an external reporitory. For
> > configuration files which are usually plain text all revision control
> > systems would probably work OK.
> >
> > Every directory contains two perl scripts, check.pl and install.pl that
> > respectively check the differences between files in the repository and
> > in the filesystem and install files. Both these programs read a file
> > called 'filelist.<username>'. This is a text file that has on every line
> > a file in the reposirory, a permission, and its location in the
> > filesystem (e.g. under /etc or /usr/local/etc for user root, or in $HOME
> > for other users) and any post-install commands. Both scripts only
> > process the filelists for the user that is running the script.
> >
>
> [snip]
>
> I currently use subversion for my University work (primarily because
> of how well it handles binary files). SVN seems to be a bit overkill
> for what I am looking for.
>
> >
> > The file from the first column is installed in the location in the third
> > column with the permissions listed in the second column. The rest of the
> > line (if any) is interpreted as a list of commands and executed by a subshell.
> >
> > This system makes it easy to see if there are any differences between
> > the configuration files in the repository and the real configuration
> > files (e.g. after a mergemaster run). And it can install every file in
> > its correct place. It also makes sure that users can only install their
> > own files, by reading only that user's filelist.
> >
>
> I'll have to play around with this -- interesting.
>
> Thanks!
>
>
> --
> Glen Barber
>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 29 Mar 2009 09:04:20 -0400
> From: Jerry McAllister <jerrymc@msu.edu>
> Subject: Re: Can't upgrade to 7.1-RELEASE
> To: Reinis Ivanovs <dabas@untu.ms>
> Cc: freebsd-questions@freebsd.org
> Message-ID: <20090329130420.GA63127@gizmo.acns.msu.edu>
> Content-Type: text/plain; charset=us-ascii
>
> On Sun, Mar 29, 2009 at 02:41:23AM +0200, Reinis Ivanovs wrote:
>
> > Hello,
> >
> > I'm trying to upgrade a 7.0 system to 7.1-RELEASE, and it isn't
> > working. I switch to the superuser, do "freebsd-update upgrade -r
> > 7.1-RELEASE", and then when I try running "freebsd-update install", I
> > get this:
> >
> > > .chflags: ///.profile: Operation not supported
> >
> > Any hints as to what could be the problem?
>
> Well, it looks like someone set the 'schg' flag on the .profile file.
>
> You need to do 'chgflags noscgg <FILENAME>' on the file - probably from root.
>
> ////jerry
>
>
> >
> > Best,
> > R. <http://dabas.untu.ms/>;
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
>
> ------------------------------
>
> Message: 6
> Date: Sun, 29 Mar 2009 14:20:17 +0200
> From: Roger Olofsson <240olofsson@telia.com>
> Subject: Re: [OT] - Best Practices(TM) for Configuration File Changes
> To: Glen Barber <glen.j.barber@gmail.com>
> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
> Message-ID: <49CF6781.5070401@telia.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>
> Glen Barber skrev:
> > Hello, list.
> >
> > Before I pose my question, I am not intending to start a flame-war of
> > any sort -- I'm just searching for "different" ways of doing things.
> >
> > With so many different version control systems available (aside from
> > the traditional "keep current backups" solution), I am curious:
> >
> > Q: What is *your* favorite/suggestion solution to keep (working)
> > versions of configuration files, in case something goes awry?
> >
> > I am specifically targeting configuration files because they are what
> > I change the most, in avoidance of "It worked 10 minutes ago..."
> > situations.
> >
> > Cheers,
> >
>
> Hi Glen,
>
> For local configuration files there's a tool called rcs that can be used
> for tracking changes and rollback.
>
> It's a part of the FreeBSD base system. Check the man pages for rcs(1)
> ci(1) co(1) rcsdiff(1) and rcsintro(1) - rcsintro(1) is probably where
> you want to start.
>
> It's also available on other *nix systems like AIX, Red Hat, Solaris etc.
>
> /R
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 29 Mar 2009 17:03:03 +0100
> From: Barnaby Scott <bds@waywood.co.uk>
> Subject: Re: Software installasion (Was: Re: Wine without X)
> To: FreeBSD Mailing List <freebsd-questions@freebsd.org>
> Message-ID: <49CF9BB7.7050206@waywood.co.uk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Mel Flynn wrote:
> > On Saturday 28 March 2009 13:06:44 Robert Huff wrote:
> >> Mel Flynn writes:
> >>> > Can I ask one more possibly really dumb question, to which I
> >>> > can find no answer: Is there a 'conventional', or sensible
> >>> > for one reason oranother, place to download application source to?
> >>>
> >>> Most systems I use or inherited use a variation of ~/src ~/cvs or
> >>> ~/svn, where src are the tarballs + their extracted source and
> >>> cvs/svn checkouts and/or exports.
> >> I have never done this, but if I were running a private ports
> >> tree I would be tempted to root it (if not on a separate partition)
> >> at "/usr/priv_ports" or something similar and have the structure
> >> minic /usr/ports whereever possible. The name would then be
> >> semi-intuitive, and a simple change of a few environment variables
> >> (perhaps in the login file of an account dedicated to working on
> >> those ports) would be all it took to change the framework.
> >
> > A private portstree (as in: uses the ports framework for compiling and
> > installing software, including registering the port in /var/db/pkg) is best
> > kept in /usr/ports/local. One needs to set VALID_CATEGORIES=local in
> > /etc/make.conf and optionally add SUBDIR+=local in /usr/ports/Makefile.local
> > if one cares about the ports ending up in the INDEX and make search.
> >
> > Ideally software not registering itself inside /var/db/pkg (as in software
> > compiled by hand) should NOT be installed in $LOCALBASE (/usr/local by
> > default) as there is no guarantee through the ports CONFLICTS mechanism, that
> > a port overwrites files installed by your hand-compiled software.
> >
>
>
> Many thanks to all who have helped on this one.
>
> I managed to get wine installed without X and it works :) However my
> application doesn't :(
>
> Most of the errors are concerned with MS Visual C++ libraries, which I
> have unconfirmed indications might be solved with 'winetricks'
> http://wiki.winehq.org/winetricks. However, I think using winetricks
> means I need X anyway. So, I will leave it for now and try again after a
> bit more research.
>
> Thanks for all the ideas about where to download/install custom apps -
> the one that appeals most at this stage is a jail, partly because I have
> never played with them, and I think I should progress my learning in
> that direction. However I find the other answers very useful insights
> too. Given that winetricks calls itself a 'quick and dirty script',
> along with the fact that the current wine port doesn't work, I think I
> see another manual installation coming on.
>
>
>
> ------------------------------
>
> Message: 8
> Date: Sun, 29 Mar 2009 19:47:23 +0300
> From: Reinis Ivanovs <dabas@untu.ms>
> Subject: Re: Can't upgrade to 7.1-RELEASE
> To: freebsd-questions@freebsd.org
> Message-ID:
> <5b826e210903290947j517e8f67o204835b8ca940c35@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Thanks, that did the trick. I commented out the chflags and the script
> finished successfuly. That makes sense, since the kernel security
> level was -1, so chflags shouldn't matter.
>
> R. <http://dabas.untu.ms/>;
>
>
>
> On Sun, Mar 29, 2009 at 16:04, Jerry McAllister <jerrymc@msu.edu> wrote:
> > On Sun, Mar 29, 2009 at 02:41:23AM +0200, Reinis Ivanovs wrote:
> >
> >> Hello,
> >>
> >> I'm trying to upgrade a 7.0 system to 7.1-RELEASE, and it isn't
> >> working. I switch to the superuser, do "freebsd-update upgrade -r
> >> 7.1-RELEASE", and then when I try running "freebsd-update install", I
> >> get this:
> >>
> >> > .chflags: ///.profile: Operation not supported
> >>
> >> Any hints as to what could be the problem?
> >
> > Well, it looks like someone set the  'schg'  flag on the  .profile  file.
> >
> > You need to do  'chgflags noscgg <FILENAME>'  on the file - probably from root.
> >
> > ////jerry
> >
> >
> >>
> >> Best,
> >> R. <http://dabas.untu.ms/>;
> >> _______________________________________________
> >> freebsd-questions@freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
> >
>
>
> ------------------------------
>
> Message: 9
> Date: Sun, 29 Mar 2009 12:21:32 -0500
> From: Paul Schmehl <pschmehl_lists@tx.rr.com>
> Subject: Re: Software installasion (Was: Re: Wine without X)
> To: Barnaby Scott <bds@waywood.co.uk>, FreeBSD Mailing List
> <freebsd-questions@freebsd.org>
> Message-ID: <8C62E22504764E6381B9B5EE@Macintosh-2.local>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> --On March 29, 2009 11:03:03 AM -0500 Barnaby Scott <bds@waywood.co.uk>
> wrote:
> >
> > Many thanks to all who have helped on this one.
> >
> > I managed to get wine installed without X and it works :) However my
> > application doesn't :(
> >
> > Most of the errors are concerned with MS Visual C++ libraries, which I
> > have unconfirmed indications might be solved with 'winetricks'
> > http://wiki.winehq.org/winetricks. However, I think using winetricks
> > means I need X anyway. So, I will leave it for now and try again after a
> > bit more research.
> >
>
> Sounds like missing dlls. You *may* be able to just copy the missing dlls
> into the wine lib directory and get the application to work. I would
> examine the error messages closely to see what dlls it trying to find and
> can't.
>
> Paul Schmehl, If it isn't already
> obvious, my opinions are my own
> and not those of my employer.
> ******************************************
> WARNING: Check the headers before replying
>
>
>
> ------------------------------
>
> Message: 10
> Date: Sun, 29 Mar 2009 12:33:40 -0500
> From: Charles Howse <chowse@charter.net>
> Subject: Re: analyzing httpd-error.log
> To: FreeBSD Questions <freebsd-questions@freebsd.org>
> Message-ID: <B832EFF4-F951-4830-9C96-944287DE8E8D@charter.net>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
>
> On Mar 28, 2009, at 11:51 PM, Olivier Nicole wrote:
>
> > Hi,
> >
> >> Webalizer is doing what it's supposed to with httpd-access.log, but
> >> when I give it the error log to process is coughs, spits and spills
> >> out errors with no data processed. My research hasn't turned up a
> >> good solution for webalizer and -error.log.
> >
> > The format of error log is pretty much different from the format of
> > transfer log. No wonder webalizer is not liking it. You may have to
> > write your own format for th error log.
>
> Well, can anyone suggest a port that will parse the error.log and
> output it to a web page that's easy to read?
>
> Also, in httpd.conf what level of detail should I set in the error.log
> to get the most information. It's currently set to 'warn', which I
> understand to be 'warn' and everything more critical than that. I
> don't care about the size of the log, or the amount of garbage per line.
>
>
> ------------------------------
>
> Message: 11
> Date: Sun, 29 Mar 2009 14:23:13 -0400
> From: Tsu-Fan Cheng <tfcheng@gmail.com>
> Subject: init panic in freebsd 7.1
> To: FreeBSD <freebsd-questions@freebsd.org>
> Message-ID:
> <f84c38580903291123o30fde6aeg9ecd196e8184bb40@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
> I was having a little trouble with my computer, first thought was
> that the mboard was fried, but later found out it was the power supply
> and replaced it. The computer started but failed to boot, here is what
> it's been complaining,
>
> exec /sbin/init error 8
> exec /sbin/init.bak error 8
> exec /rescue/init error8
>
> init: not found in path /sbin/.... (a lot of paths)
>
> panic: no init
>
>
> what is that??
>
> TFC
>
>
> ------------------------------
>
> Message: 12
> Date: Sun, 29 Mar 2009 12:32:57 -0600 (MDT)
> From: User Wblock <wblock@wonkity.com>
> Subject: Re: Software installasion (Was: Re: Wine without X)
> To: Barnaby Scott <bds@waywood.co.uk>
> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org>
> Message-ID: <alpine.BSF.2.00.0903291231061.10887@wonkity.com>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
> On Sun, 29 Mar 2009, Barnaby Scott wrote:
> > Thanks for all the ideas about where to download/install custom apps -
> > the one that appeals most at this stage is a jail, partly because I have
> > never played with them, and I think I should progress my learning in
> > that direction. However I find the other answers very useful insights
> > too. Given that winetricks calls itself a 'quick and dirty script',
> > along with the fact that the current wine port doesn't work,
>
> Today's updated wine-1.1.18,1 port works now.
>
> -Warren Block * Rapid City, South Dakota USA
>
>
> ------------------------------
>
> Message: 13
> Date: Sun, 29 Mar 2009 20:49:19 +0200
> From: Polytropon <freebsd@edvax.de>
> Subject: Re: init panic in freebsd 7.1
> To: Tsu-Fan Cheng <tfcheng@gmail.com>
> Cc: FreeBSD <freebsd-questions@freebsd.org>
> Message-ID: <20090329204919.96ac0671.freebsd@edvax.de>
> Content-Type: text/plain; charset=US-ASCII
>
> On Sun, 29 Mar 2009 14:23:13 -0400, Tsu-Fan Cheng <tfcheng@gmail.com> wrote:
> > init: not found in path /sbin/.... (a lot of paths)
> > panic: no init
> >
> > what is that??
>
> The init process is the "root" of the FreeBSD startup, and the last
> part of the OS loader cannot find it, so the OS cannot start.
>
> http://www.freebsd.org/cgi/man.cgi?query=init&apropos=0&sektion=8&manpath=FreeBSD+7.1-RELEASE&format=ascii
>
> You can use a live system CD of FreeBSD (6, 7) or FreeSBIE to boot
> the system with this CD, it should work. Then you can mount your
> / partition and check the existance of init which usually is
> /sbin/init. Don't forget to fsck the hard disk, maybe due to the
> failing power supply you had some damages on the hard disk (file-wise),
> or even worse...
>
>
>
>
> --
> Polytropon
> >From Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
>
>
> ------------------------------
>
> Message: 14
> Date: Sun, 29 Mar 2009 14:54:35 -0400
> From: Glen Barber <glen.j.barber@gmail.com>
> Subject: Re: analyzing httpd-error.log
> To: Charles Howse <chowse@charter.net>
> Cc: FreeBSD Questions <freebsd-questions@freebsd.org>
> Message-ID:
> <4ad871310903291154j74c35b0p545157b848adf8b9@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Sun, Mar 29, 2009 at 1:33 PM, Charles Howse <chowse@charter.net> wrote:
> >
> > On Mar 28, 2009, at 11:51 PM, Olivier Nicole wrote:
> >
> >> Hi,
> >>
> >>> Webalizer is doing what it's supposed to with httpd-access.log, but
> >>> when I give it the error log to process is coughs, spits and spills
> >>> out errors with no data processed. My research hasn't turned up a
> >>> good solution for webalizer and -error.log.
> >>
>
> What are the errors?
>
> >> The format of error log is pretty much different from the format of
> >> transfer log. No wonder webalizer is not liking it. You may have to
> >> write your own format for th error log.
> >
> > Well, can anyone suggest a port that will parse the error.log and output it
> > to a web page that's easy to read?
> >
>
> Webalizer is probably your best bet.
>
> > Also, in httpd.conf what level of detail should I set in the error.log to
> > get the most information. It's currently set to 'warn', which I understand
> > to be 'warn' and everything more critical than that. I don't care about the
> > size of the log, or the amount of garbage per line.
>
> The 'debug' log level will provide the most verbosity.
>
> --
> Glen Barber
>
>
> ------------------------------
>
> Message: 15
> Date: Sun, 29 Mar 2009 12:09:42 -0700
> From: Yuri <yuri@rawbw.com>
> Subject: Webcam support in FreeBSD?
> To: freebsd-questions@freebsd.org
> Message-ID: <49CFC776.6000207@rawbw.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> There are three Linux drivers supported under emulation code:
> devel/linux-kmod-compat
> <http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/linux-kmod-compat/>,
> multimedia/linux-gspca-kmod
> <http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/linux-gspca-kmod/>,
> multimedia/linux-ov511-kmod
> <http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/linux-ov511-kmod/>.
>
> I couldn't find hardware compatibility list for FreeBSD.
> There is one for Linux ov511 driver here:
> http://ovcam.org/ov511/cameras.html.
>
> Are any cameras really working under FreeBSD?
> Can they be used from Linux Skype on FreeBSD?
>
> Thanks,
> Yuri
>
>
> ------------------------------
>
> Message: 16
> Date: Sun, 29 Mar 2009 21:17:36 +0200
> From: Frederique Rijsdijk <frederique@isafeelin.org>
> Subject: Re: Binary upgrade 7.1 i386 -> amd64 ?
> To: <freebsd-questions@freebsd.org>
> Message-ID: <9367d26b7089f0f0002f1c031e1e1298@localhost>
> Content-Type: text/plain; charset="UTF-8"
>
>
> On Fri, 13 Mar 2009 09:05:12 +0100, Frederique Rijsdijk
> <frederique@isafeelin.org> wrote:
> > I'm planning to binary upgrade a machine that's now running i386
> > 7.1-RELEASE-p3 to AMD64.
>
> Just to follow up on my quest here..
>
> The upgrade went fine. Most ports were broken as expected. I gave up trying
> to recompile everything after a while, tripping over errors all over the
> place. Weird ones. The mountain of errors in front of me just never got any
> smaller.
>
> Ended up deleting all ports (pkg_delete -f \* is not something you do alot)
> and /usr/local/lib. This left me with configuration files of all the apps I
> had installed, as well as /var/db/ports/*. I simply recompiled the complete
> of apps that was installed, and after a day or so of compiling all is
> working again. No further work required. Amazing stuff!
>
> I find it amazing that even when things go really wrong in BSD (of course I
> did that :), it's quite easy to recover from such a aituation. Just all the
> port compiler options (/var/db/ports/*) and all the conf files of the apps
> is enough to recover - even from source. At the end of the day, it put a
> big smile on my face.
>
> Just had to say it!
>
>
> -- Frederique
>
>
>
>
> ------------------------------
>
> Message: 17
> Date: Sun, 29 Mar 2009 15:25:55 -0500
> From: Charles Howse <chowse@charter.net>
> Subject: Re: analyzing httpd-error.log
> To: FreeBSD Questions <freebsd-questions@freebsd.org>
> Message-ID: <8BDE67B0-B6B1-4AAC-A0FD-0E519E74CBAF@charter.net>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
>
> On Mar 29, 2009, at 1:54 PM, Glen Barber wrote:
>
> > On Sun, Mar 29, 2009 at 1:33 PM, Charles Howse <chowse@charter.net>
> > wrote:
> >>
> >> On Mar 28, 2009, at 11:51 PM, Olivier Nicole wrote:
> >>
> >>> Hi,
> >>>
> >>>> Webalizer is doing what it's supposed to with httpd-access.log, but
> >>>> when I give it the error log to process is coughs, spits and spills
> >>>> out errors with no data processed. My research hasn't turned up a
> >>>> good solution for webalizer and -error.log.
> >>>
> >
> > What are the errors?
>
> Intrusion attempts, (a few) bad links in my website, also I use the
> error.log to troubleshoot cgi scripts.
> >
> >
> >>> The format of error log is pretty much different from the format of
> >>> transfer log. No wonder webalizer is not liking it. You may have to
> >>> write your own format for th error log.
> >>
> >> Well, can anyone suggest a port that will parse the error.log and
> >> output it
> >> to a web page that's easy to read?
> >>
> >
> > Webalizer is probably your best bet.
> >
> >> Also, in httpd.conf what level of detail should I set in the
> >> error.log to
> >> get the most information. It's currently set to 'warn', which I
> >> understand
> >> to be 'warn' and everything more critical than that. I don't care
> >> about the
> >> size of the log, or the amount of garbage per line.
> >
> > The 'debug' log level will provide the most verbosity.
>
> Thanks, Glen.
>
>
>
>
> ------------------------------
>
> Message: 18
> Date: Sun, 29 Mar 2009 22:48:34 +0200
> From: Roger Olofsson <240olofsson@telia.com>
> Subject: Newsyslog mode on /var/log/security?
> To: User Questions <freebsd-questions@freebsd.org>
> Message-ID: <49CFDEA2.2080606@telia.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Dear mailing list,
>
> I seem to have forgotten something about /var/log/security and
> newsyslog.conf. I get wrong mode after the trim.
>
> Excerpt from /etc/newsyslog.conf:
> /var/log/security 644 7 5000 * JC
>
> Output from newsyslog -vn:
> chmod 600 /var/log/security.0.bz2
>
> Why is the mode not 644?
>
> /etc/rc.d/syslogd restart and newsyslog restart have been performed.
>
> /R
>
>
>
> ------------------------------
>
> Message: 19
> Date: Sun, 29 Mar 2009 16:39:56 -0400
> From: "Grant Peel" <gpeel@thenetnow.com>
> Subject: 6.x -> 7.1
> To: <freebsd-questions@freebsd.org>
> Message-ID: <C2A1D7DCE754443C86A7EAEEF1A7AB57@GRANTLAPTOP>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=original
>
> Hi all,
>
> We have (finally) made the decision to move our server (10 -Dell) from
> Toronto to a newer data center closer to our office in London.
>
> Before I ask this question, I would like to ensure everyone I will be
> reading all the docs I can find, but since the upgrade will be much work, I
> thought I would ask the question here anyways :-)
>
> Question: given the items below, should I expext the make and build of
> FreeBSD and the software below, to go pretty much as it did in 6.x? (Does
> anyone know of any showstoppers)?
>
> All software below has/will be built from ports.
>
> Synopsis:
>
> 10 Dell 1U Rack servers (Intel Based, SCSI) more or less standard entry
> level servers)
> All running
> -FreeBSD 6.x,
> -Apache 2.2.x
> -Mysql Server 4.x
> -PHP 4.x
> -Perl 5.x
> -Exim 4.6x
> -Spamassassin etc etc
>
> TIA,
>
> -Grant
>
>
>
> ------------------------------
>
> Message: 20
> Date: Sun, 29 Mar 2009 14:25:48 -0700
> From: fquest <fquest@ccstores.com>
> Subject: Re: 6.x -> 7.1
> To: Grant Peel <gpeel@thenetnow.com>
> Cc: freebsd-questions@FreeBSD.org
> Message-ID: <49CFE75C.1080404@ccstores.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Grant Peel wrote:
> > Hi all,
> >
> > We have (finally) made the decision to move our server (10 -Dell) from
> > Toronto to a newer data center closer to our office in London.
> >
> > Before I ask this question, I would like to ensure everyone I will be
> > reading all the docs I can find, but since the upgrade will be much
> > work, I thought I would ask the question here anyways :-)
> >
> > Question: given the items below, should I expext the make and build of
> > FreeBSD and the software below, to go pretty much as it did in 6.x?
> > (Does anyone know of any showstoppers)?
> >
> > All software below has/will be built from ports.
> >
> > Synopsis:
> >
> > 10 Dell 1U Rack servers (Intel Based, SCSI) more or less standard entry
> > level servers)
> > All running
> > -FreeBSD 6.x,
> > -Apache 2.2.x
> > -Mysql Server 4.x
> > -PHP 4.x
> > -Perl 5.x
> > -Exim 4.6x
> > -Spamassassin etc etc
> >
> > TIA,
> >
> > -Grant
>
> I did much similar with NO issues.
> HOWEVER. I 'upgraded' to MySQL 5.x
> BIG MISTAKE.
> 5 is considerably slower than 4. Do not move to 5 unless/until you need
> the journaling features (and other features) of 5.
>
> Otherwise, your transition should be seamless.
>
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "freebsd-questions-unsubscribe@freebsd.org"
> >
> >
>
>
> --
> Jim Pazarena fquest@ccstores.com
>
>
> ------------------------------
>
> Message: 21
> Date: Sun, 29 Mar 2009 22:07:42 +0000
> From: af300wsm@gmail.com
> Subject: Where is the Perl XML::Parser port
> To: Free BSD Questions list <freebsd-questions@freebsd.org>
> Message-ID: <0016364c6375e4128f046649311c@google.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
>
> Hi,
>
> I'm installing the latest gimp and get to a point in the install where it
> says:
>
> checking for perl... /usr/bin/perl
> checking for XML::Parser... configure: error: XML::Parser perl module is
> required for intltool
>
>
> So, I've done some searches at freshports.org and I cannot find the
> XML::Parser perl module anywhere in the ports tree. What is it under?
>
> Thanks,
> Andy
>
>
> ------------------------------
>
> Message: 22
> Date: Sun, 29 Mar 2009 18:56:26 -0300
> From: Ramiro Caso <misha_78@hotmail.com>
> Subject: RE: Webcam support in FreeBSD?
> To: <yuri@rawbw.com>, <freebsd-questions@freebsd.org>
> Message-ID: <BAY102-W136D95D3354AABDD3C74D1E18C0@phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> > Date: Sun, 29 Mar 2009 12:09:42 -0700
> > From: yuri@rawbw.com
> > To: freebsd-questions@freebsd.org
> > Subject: Webcam support in FreeBSD?
> >
> > There are three Linux drivers supported under emulation code:
> > devel/linux-kmod-compat
> > <http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/linux-kmod-compat/>,
> > multimedia/linux-gspca-kmod
> > <http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/linux-gspca-kmod/>,
> > multimedia/linux-ov511-kmod
> > <http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/linux-ov511-kmod/>.
> >
> > I couldn't find hardware compatibility list for FreeBSD.
> > There is one for Linux ov511 driver here:
> > http://ovcam.org/ov511/cameras.html.
> >
> > Are any cameras really working under FreeBSD?
> > Can they be used from Linux Skype on FreeBSD?
>
> Maybe you could check out:
>
> http://info.iet.unipi.it/~luigi/FreeBSD/usb-cameras.html
>
> That seems to me a place to start... (if you find out something, please share!! I have the same concern)
>
> >
> > Thanks,
> > Yuri
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
> _________________________________________________________________
> ¿Querés saber cómo va a estar el clima mañana? Ingresá ahora a MSN
> http://tiempo.ar.msn.com/
>
> ------------------------------
>
> Message: 23
> Date: Sun, 29 Mar 2009 23:21:21 +0100
> From: "Paul B. Mahol" <onemda@gmail.com>
> Subject: Re: Where is the Perl XML::Parser port
> To: af300wsm@gmail.com
> Cc: Free BSD Questions list <freebsd-questions@freebsd.org>
> Message-ID:
> <3a142e750903291521l6448396na8f9454b20ce3438@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 3/29/09, af300wsm@gmail.com <af300wsm@gmail.com> wrote:
> > Hi,
> >
> > I'm installing the latest gimp and get to a point in the install where it
> > says:
> >
> > checking for perl... /usr/bin/perl
> > checking for XML::Parser... configure: error: XML::Parser perl module is
> > required for intltool
> >
> >
> > So, I've done some searches at freshports.org and I cannot find the
> > XML::Parser perl module anywhere in the ports tree. What is it under?
>
> > whereis p5-XML-Parser
> p5-XML-Parser: /usr/ports/textproc/p5-XML-Parser
>
> --
> Paul
>
>
> ------------------------------
>
> Message: 24
> Date: Sun, 29 Mar 2009 22:48:50 +0000 (UTC)
> From: Anton Yuzhaninov <citrin@citrin.ru>
> Subject: Re: Where is the Perl XML::Parser port
> To: freebsd-questions@freebsd.org
> Message-ID: <gqotsi$nlh$1@ger.gmane.org>
>
> On Sun, 29 Mar 2009 22:07:42 +0000, af300wsm@gmail.com wrote:
> awgc> So, I've done some searches at freshports.org and I cannot find the
> awgc> XML::Parser perl module anywhere in the ports tree. What is it under?
>
> /usr/ports/textproc/p5-XML-Parser/
>
> --
> Anton Yuzhaninov
>
>
>
> ------------------------------
>
> Message: 25
> Date: Sun, 29 Mar 2009 17:49:00 -0400
> From: Garance A Drosehn <gad@FreeBSD.org>
> Subject: Re: Newsyslog mode on /var/log/security?
> To: raggen@raggens.net, User Questions <freebsd-questions@FreeBSD.org>
> Message-ID: <p06240805c5f59b1b34cd@[128.113.24.47]>
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>
> At 10:48 PM +0200 3/29/09, Roger Olofsson wrote:
> >Dear mailing list,
> >
> >I seem to have forgotten something about /var/log/security and
> >newsyslog.conf. I get wrong mode after the trim.
> >
> >Excerpt from /etc/newsyslog.conf:
> >/var/log/security 644 7 5000 * JC
>
>
> Are you sure that's the only line you have for /var/log/security in
> your /etc/newsyslog.conf file? The distributed config file has:
>
> /var/log/security 600 10 100 * JC
>
> Obviously you have a different entry from that, but did you remove
> the original entry?
>
> >Output from newsyslog -vn:
> >chmod 600 /var/log/security.0.bz2
> >
> >Why is the mode not 644?
> >
> >/etc/rc.d/syslogd restart and newsyslog restart have been performed.
>
> I tried changing the permissions-field in my newsyslog.conf from 600
> to 644, and newsyslog worked correctly for me.
>
> --
> Garance Alistair Drosehn = drosehn@rpi.edu
> Senior Systems Programmer or gad@FreeBSD.org
> Rensselaer Polytechnic Institute; Troy, NY; USA
>
>
> ------------------------------
>
> Message: 26
> Date: Sun, 29 Mar 2009 04:39:15 -1000
> From: Parv <parv@pair.com>
> Subject: Cleaning up multiplicates in elf ldconfig path
> To: f-q <freebsd-questions@freebsd.org>
> Message-ID: <20090329143915.GA1331@holstein.holy.cow>
> Content-Type: text/plain; charset=us-ascii
>
> I am on FreeBSD/i386 6.4-STABLE (around Mar 1, 2009). I failed to
> find a solution to the (cosmetic) problem of ldconfig path having
> duplicate directories (dmesg output wrapped for this email) ...
>
> ELF ldconfig path: /lib /usr/lib /usr/lib/compat \
> /usr/X11R6/lib /usr/local/lib \
> /misc/local/lib/compat \
> /misc/local/lib/gcc-4.2.4 \
> /misc/local/lib/gcc-4.3.3 \
> /misc/local/lib/gegl-0.0 \
> /misc/local/lib/gnash \
> /misc/local/lib/graphviz \
> /misc/local/lib/nss \
> /misc/local/lib/qt4 \
> /misc/local/lib/zsh \
> /misc/local/lib/compat
> /misc/local/lib/gcc-4.2.4 \
> /misc/local/lib/gcc-4.3.3 \
> /misc/local/lib/gegl-0.0 \
> /misc/local/lib/gnash \
> /misc/local/lib/graphviz \
> /misc/local/lib/nss \
> /misc/local/lib/qt4 \
> /misc/local/lib/zsh
>
>
> Note that /usr/X11R6 & /usr/local are symbolic links to /misc/local.
> Is that what is causing the "problem" (since /etc/rc.d/ldconfig
> reads the default paths of both /usr/X11R6/lib & /usr/local/lib)?
>
> If so, is it ok to eliminate the /usr/X11R6 symbolic link? And/Or,
> is there any other way to remove the multiplicates? I suppose I
> could stick in /etc/rc.conf this ...
>
> ldconfig_paths="/usr/lib/compat /usr/local/lib /usr/local/lib/compat/package"
>
>
> ... but then I would have make sure above does not miss any new
> paths added to /etc/defaults/rc.conf. Opinions or suggestions?
>
>
> - Parv
>
> --
>
>
>
> ------------------------------
>
> Message: 27
> Date: Mon, 30 Mar 2009 11:33:08 +1100
> From: Brett Wigins <s0x7c0@netspace.net.au>
> Subject: configuring the freebsd boot manager
> To: freebsd-questions@freebsd.org
> Message-ID: <49D01344.5010809@netspace.net.au>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi everyone,
>
> I am having some problems understanding how the freebsd boot manager
> works. I have installed FreeBSD and Linux on the same laptop HD and want
> to be able to select which one to boot when the computer starts. I
> installed the bootmanager to to the MBR during installation and when I
> boot the laptop I am presented with four choices;
>
> F1 - FreeBSD
> F2 - Linux
> F3 - ???
> F4 - Linux
>
> but I am only able to select F1, F2-F3 only make the laptop beep and
> doesnt load anything. The way I have set up the HD is for Partition 1 to
> be a FreeBSD Slice, Partition 2 the Linux / Partition 3 is Linux swap
> and Partition 4 is Linux /home. Any help would be great
>
> thanks,
>
> Brett
>
>
>
> ------------------------------
>
> Message: 28
> Date: Sun, 29 Mar 2009 22:28:38 -0300
> From: Ramiro Caso <misha_78@hotmail.com>
> Subject: RE: configuring the freebsd boot manager
> To: <s0x7c0@netspace.net.au>, <freebsd-questions@freebsd.org>
> Message-ID: <BAY102-W439A5F7783DF01D22CE056E18D0@phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> > Hi everyone,
> >
> > I am having some problems understanding how the freebsd boot manager
> > works. I have installed FreeBSD and Linux on the same laptop HD and want
> > to be able to select which one to boot when the computer starts. I
> > installed the bootmanager to to the MBR during installation and when I
> > boot the laptop I am presented with four choices;
> >
> > F1 - FreeBSD
> > F2 - Linux
> > F3 - ???
> > F4 - Linux
> >
> > but I am only able to select F1, F2-F3 only make the laptop beep and
> > doesnt load anything. The way I have set up the HD is for Partition 1 to
> > be a FreeBSD Slice, Partition 2 the Linux / Partition 3 is Linux swap
> > and Partition 4 is Linux /home. Any help would be great
>
> This is a silly question, actually: do you have LILO installed on your Linux boot partition?
> I have BootEasy on the MBR, and LILO on Linux boot, and it works just fine. Also:
>
> http://www.freebsd.org/doc/en/books/faq/disks.html#BOOTEASY-LOADER
>
> >
> > thanks,
> >
> > Brett
> >
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
> _________________________________________________________________
> Encontrá el auto de tus sueños en MSN
> http://xml.mercadolibre.com.ar/org-img/msn/autos.html
>
> ------------------------------
>
> Message: 29
> Date: Mon, 30 Mar 2009 05:25:59 +0000
> From: dhaneshk k <dhaneshkk@hotmail.com>
> Subject: WireLess USB modem not detected .
> To: <freebsd-questions@freebsd.org>
> Message-ID: <COL106-W5178D2461AD544AED82BA7B28D0@phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> List;
>
> when I attach a USB modem , I am seeing this message in dmesg output on FreeBSD6.2
>
> ugen0: Qualcomm, Incorporated Qualcomm CDMA Technologies MSM, rev 1.10/0.00, addr 2
>
> But it not showing /dev/xxxx in dmesg why ?
>
>
> If it detected what will be the entry in /dev/?
>
>
>
> Question1) Can this USB wireless modem will work with FreeBSD6.2 ? if not with a any other FreeBSD version by default?
>
> in FreeBSD-6.2 to enable this USB data card, is it needed to recompile the Generic kernel? if so which patch to add for recompilation ?
>
>
>
> Question 2) To use this modem to get wireless connection which steps I have to follow further more..
>
>
> Please help me with some tips to make it work in my FreeBSD Laptop.
>
> Thanks in Advance
> Dhanesh
>
>
>
>
> _________________________________________________________________
> So many new options, so little time. Windows Live Messenger.
> http://www.microsoft.com/india/windows/windowslive/messenger.aspx
>
> ------------------------------
>
> Message: 30
> Date: Mon, 30 Mar 2009 08:08:06 +0200
> From: Roger Olofsson <240olofsson@telia.com>
> Subject: Re: Newsyslog mode on /var/log/security?
> To: Garance A Drosehn <gad@FreeBSD.org>
> Cc: User Questions <freebsd-questions@FreeBSD.org>
> Message-ID: <49D061C6.6060104@telia.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>
> Garance A Drosehn skrev:
> > At 10:48 PM +0200 3/29/09, Roger Olofsson wrote:
> >> Dear mailing list,
> >>
> >> I seem to have forgotten something about /var/log/security and
> >> newsyslog.conf. I get wrong mode after the trim.
> >>
> >> Excerpt from /etc/newsyslog.conf:
> >> /var/log/security 644 7 5000 * JC
> >
> >
> > Are you sure that's the only line you have for /var/log/security in
> > your /etc/newsyslog.conf file? The distributed config file has:
> >
> > /var/log/security 600 10 100 * JC
> >
> > Obviously you have a different entry from that, but did you remove
> > the original entry?
> >
> >> Output from newsyslog -vn:
> >> chmod 600 /var/log/security.0.bz2
> >>
> >> Why is the mode not 644?
> >>
> >> /etc/rc.d/syslogd restart and newsyslog restart have been performed.
> >
> > I tried changing the permissions-field in my newsyslog.conf from 600
> > to 644, and newsyslog worked correctly for me.
> >
>
> Hi Garance,
>
> You are correct! I missed the original line. Silly me :^D
>
> Thank you very much!
>
> /R
>
>
>
> ------------------------------
>
> Message: 31
> Date: Mon, 30 Mar 2009 02:48:34 -0400
> From: Garance A Drosehn <gad@FreeBSD.org>
> Subject: Re: Newsyslog mode on /var/log/security?
> To: raggen@raggens.net
> Cc: User Questions <freebsd-questions@FreeBSD.org>
> Message-ID: <p06240806c5f61b303986@[128.113.24.47]>
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>
> At 8:08 AM +0200 3/30/09, Roger Olofsson wrote:
> >Garance A Drosehn skrev:
> >>At 10:48 PM +0200 3/29/09, Roger Olofsson wrote:
> >>>
> >>>I seem to have forgotten something about /var/log/security and
> >>>newsyslog.conf. I get wrong mode after the trim.
> >>>
> >>>Excerpt from /etc/newsyslog.conf:
> >>>/var/log/security 644 7 5000 * JC
> >>
> >>
> >>Are you sure that's the only line you have for /var/log/security in
> >>your /etc/newsyslog.conf file? The distributed config file has:
> >>
> >>/var/log/security 600 10 100 * JC
> >>
> >>Obviously you have a different entry from that, but did you remove
> >>the original entry?
> >
> >Hi Garance,
> >
> >You are correct! I missed the original line. Silly me :^D
>
> Well, I should probably change newsyslog to "do something different"
> (he says vaguely) when the same file is specified multiple times.
>
> >Thank you very much!
>
> You're welcome.
>
> --
> Garance Alistair Drosehn = drosehn@rpi.edu
> Senior Systems Programmer or gad@FreeBSD.org
> Rensselaer Polytechnic Institute; Troy, NY; USA
>
>
> ------------------------------
>
> Message: 32
> Date: Mon, 30 Mar 2009 12:45:59 +0530
> From: "ajeesh joseph" <ajeeshjoseph@in.com>
> Subject: installing freebsd 7.1 ( error mounting /dev/acd0
> input/output error)
> To: freebsd-questions@freebsd.org
> Message-ID: <1238397359.e46bc064f8e92ac2c404b9871b2a4ef2@mail.in.com>
> Content-Type: text/plain; charset=utf-8
>
> Hello,I was installing freebsd 7.0/7.1to my Ampro RB700,celeron processor,usb hdd 80gb using my CD drive.during the time of installation i get error "error mounting /dev/acd0 input/output error"could any one tell me how to solve this and how can i install the OS..regardsAjeesh
>
>
> ------------------------------
>
> Message: 33
> Date: Mon, 30 Mar 2009 16:08:58 +0700 (ICT)
> From: Olivier Nicole <on@cs.ait.ac.th>
> Subject: Re: Stock OpenSSL is multithread or not?
> To: on@cs.ait.ac.th
> Cc: freebsd-questions@freebsd.org
> Message-ID: <200903300908.n2U98wIU034944@banyan.cs.ait.ac.th>
>
> Hi,
>
> > I am trying to use Pound (/usr/ports/www/pound). From the
> > documentation I read;
> >
> > Warning: as Pound is a multi-threaded program it requires a
> > version of OpenSSL with thread support. This is normally the case
> > on Linux and Solaris (for example) but not on *BSD.
> >
> > Is that still true on FreeBSD 6.4 RELENG amd64? And should I install
>
> I think I have my answer as pound would not work with the default
> OpenSSL, but would work with the port OpenSSL, the stock on comes with
> no threads, while the port build by default with threads...
>
> Olivier
>
>
> ------------------------------
>
> Message: 34
> Date: Sun, 29 Mar 2009 23:35:35 -1000
> From: Parv <parv@pair.com>
> Subject: Re: Cleaning up multiplicates in elf ldconfig path
> To: f-q <freebsd-questions@freebsd.org>
> Message-ID: <20090330093535.GA2638@holstein.holy.cow>
> Content-Type: text/plain; charset=us-ascii
>
> in message <20090329143915.GA1331@holstein.holy.cow>,
> wrote Parv thusly...
> >
> ...
> > I failed to find a solution to the (cosmetic) problem of ldconfig
> > path having duplicate directories
> ...
> > I suppose I could stick in /etc/rc.conf this ...
> >
> > ldconfig_paths="/usr/lib/compat /usr/local/lib /usr/local/lib/compat/package"
> ...
>
> The last path above should have been "/usr/local/lib/compat/pkg".
>
>
> - Parv
>
> --
>
>
>
> ------------------------------
>
> Message: 35
> Date: Mon, 30 Mar 2009 21:27:56 +1100
> From: caleb <s0x7c0@netspace.net.au>
> Subject: Re: configuring the freebsd boot manager
> To: Ramiro Caso <misha_78@hotmail.com>, freebsd-questions@freebsd.org
> Message-ID: <49D09EAC.90008@netspace.net.au>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Ramiro Caso wrote:
> >> Hi everyone,
> >>
> >> I am having some problems understanding how the freebsd boot manager
> >> works. I have installed FreeBSD and Linux on the same laptop HD and want
> >> to be able to select which one to boot when the computer starts. I
> >> installed the bootmanager to to the MBR during installation and when I
> >> boot the laptop I am presented with four choices;
> >>
> >> F1 - FreeBSD
> >> F2 - Linux
> >> F3 - ???
> >> F4 - Linux
> >>
> >> but I am only able to select F1, F2-F3 only make the laptop beep and
> >> doesnt load anything. The way I have set up the HD is for Partition 1 to
> >> be a FreeBSD Slice, Partition 2 the Linux / Partition 3 is Linux swap
> >> and Partition 4 is Linux /home. Any help would be great
> >>
> >
> > This is a silly question, actually: do you have LILO installed on your Linux boot partition?
> > I have BootEasy on the MBR, and LILO on Linux boot, and it works just fine. Also:
> >
> > http://www.freebsd.org/doc/en/books/faq/disks.html#BOOTEASY-LOADER
> Hi Ramiro,
>
> Thanks for the reply. I tried a new approach because I dont think Ubuntu
> uses LILO. So instead I installed GRUB to the MBR and added an entry
> for freebsd in /boot/grub/menu.lst
>
> title FreeBSD 7.1, RELEASE
> root (hd0,3,a)
> kernel /boot/loader
> quiet
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
> End of freebsd-questions Digest, Vol 253, Issue 1
> *************************************************
_________________________________________________________________
Sürükle ve Bırak: Windows Live™ Photos ile fotoğraflarınızı kolayca paylaşımı.
http://www.microsoft.com/windows/windowslive/products/photos.aspx
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY124-W5091434C10067554AD4E10958D0>