Odd Multi-User Mode BUILD Error: lang/gnat; why is it attempting to use csh???
Please CC me on a response as I am not a member of
freebsd-questions
Here it is:
gmake[2]: Entering directory
`/usr/ports/lang/gnat/work/gcc-34/gcc/fixinc'
/bin/csh ./genfixes machname.h
SHELL=/bin/sh: Command not found.
export: Command not found.
if: Expression Syntax.
gmake[2]: *** [machname.h] Error 1
gmake[2]: Leaving directory
`/usr/ports/lang/gnat/work/gcc-34/gcc/fixinc'
gmake[1]: *** [fixinc.sh] Error 2
gmake[1]: Leaving directory
`/usr/ports/lang/gnat/work/gcc-34/gcc'
gmake: *** [all-gcc] Error 2
*** Error code 2
this is obviously caused by the build attempting to
run the sh script with (t)csh instead causing a basic
syntax error to occur because of the incompatible
script syntax and puking the make. I say obviously
because dropping to single user mode and choosing
/bin/sh as my shell allowed the build to occur without
error.
I think the problem lies in
lang/gnat/work/gcc-34/gcc/fixinc/Makefile.in
referencing the variable
[EMAIL PROTECTED]@
and using it genrally like
cd $(srcdir) ; $(SHELL) ./genfixes $@
I don't know much about Makefile syntax but I know
changing every reference of SHELL to DINGLESHELL made
no difference. I attempted to force SHELL=/bin/sh to
no avail it was ignored and still ran
/bin/csh ./genfixes machname.h
SHELL=/bin/sh:Command not found
I even reset MAKE_SHELL=/bin/sh in make.conf and
forced the above Makefile.in to use
SHELL=${MAKE_SHELL} as a last resort but neither
futile attempts worked.
I believe the error is that the Makefile is ignoring
the setting of SHELL and using the environment SHELL
variable which is by default /bin/csh. Under Linux
this wouldn't be an error because as I recall they use
bash for everyone, even the big wheels... but for a
BSD this is an error, because root runs csh
My question is should [EMAIL PROTECTED]@ pickup the proper
/bin/sh and build things correctly, or is using SHELL
in the makefile in this manner an error under a BSD
that should be fixed by a patch worked out with the
maintainer. I don't know if this is an configure
error, or a one in a bluemoon thing. I am thoroughly
confused by this.
I guess I am wondering if anyone else has had similar
issues with the port as a search on google didn't seem
to find much. I need the GPL version so I can use
tasking, as my reason for using Ada needs the
intrinsic support for threading to be functional.
This also allows me to try out the adacore compile
prior to dropping whatever sum of money they want for
GNAT-Pro...
If I have to go single user to update the port I will.
I don't want to run /bin/sh as my root shell i suppose
i could try bash. which as an exercise i set as the
root shell and all went perfectly fine through the
build. I don't want to leave things this way because a
simple issue of deleting my ports will make logging in
as root require remembering to boot single user...
my build env:
2x 2800+ athlon-mp
1284M Ram (1gig + 256M registered ECC scrubbing on)
FreeBSD 6.2-p5
CFLAGS=-O2 -pipe
COPTFLAGS=-pipe -O
CPUTYPE?=athlon-mp
NO_RCMDS=YES
NO_PROFILE=YES
MAKE_IDEA=yes
WITH_OPENSSL_BASE=YES
X_WINDOW_SYSTEM=xorg
SENDMAIL_CFLAGS=-I/usr/local/include -DSASL=2
SENDMAIL_LDFLAGS=-L/usr/local/lib
SENDMAIL_LDADD=-lsasl2
thanks for any help, and thanks to the FreeBSD team, I
can't wait for 7.0 to be released, I think my LH6000
is going to love the optimized SMP routines... as will
the above machine, of course.
brian
again, Please CC me on a response as I am not a member
of freebsd-questions
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD HP Netserver LH 3000 hang at sysinstall
Hello, I have an HP Netserver LH 3000 Server w/ 2x 800 MHZ pIII 1128 MB RAM (HP Parts) Integrated Netraid, 4 drives 100 GB of storage Bios 4.06.33 PT MMC 10.46 netraid bios 2.04 firmware 1.12 I have scene posts that quote this hardware working with LH 3000/6000 (2-way piii, 6-way piii xeon) basically all applied updates available from HP short of the Ultra3 conversion, which they say don't do unless your migrating to ultra3; which I will be but lack the hardware and don't want more mess on my hands. FreeBSD 6.2-Release, 6.0-Release, and FreeSBIE 1.1 ( Rel_5.4 I think) tried to no avail. Would dig up my Rel_5.x disks but if FreeSBIE won't work... I can't boot with ACPI enabled have to hit 2 at loader screen. which is fine any computer rated at 1.2 KW isn't going to have power management... although with the bios updates I think it will work now, but I still have been hitting 2 most of the time. Everything works fine until sysintall loads. The keyboard just doesn't work. Caps lock etc al does nothing no Leds light up. Sometimes it seems during the probing devices message the keyboard appears to go through a bus reset, and it doesn't come back. sometimes it doesn't appear to reset at all; all leds lighting up and turning off again is what I mean by reset. I have tried two keyboards, both do the same. With FreeSBIE 1.1 I can get as far as md1.gzip loading 12454 blocks of 65535 or soemthing basically when it is loading up the Ramdrives and that is typed from memeory. usually it never leaves the splash screen. I haven't scene anything in my searches as to why I cannot get this thing to work. the biggest issues seem to be ACPI and EISA SCSI... I did see one thing on Interupts but I haven't found it again since. I have tried disabling SE SCSI, IRQ sharing, turning netraid back to LVD SCSI, pulling out option boards I'm not using (2 network cards). I've tried disabling hot swap PCI resources, changing the sharing methods from smart to fixed. My guess is the keyboard is sharing an IRQ with something FreeBSD doesn't like but I am not sure how to fix that, or if that is even the issue. I've considered putting jumpers on the hot swap RAID drives because I know FreeBSD doesn't like autoenumeration of SCSI devices, but I don't think this is a storage issue. And this (when I set the jumpers manually in the past) was a problem with finding drives not booting into sysinstall Has anyone had issues like this with FreeBSD on an HP netserver? I have seriously considered giving up and installing eComstation and running BSD in a virtual machine, but I would rather be running BSD on this box. Please respond to backyard1454-bsd (some-kind-of-symbol) yahoo (a-seperator) com as I am not on the questions list. Thanks for any help that can be offered, Brian McKeon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something Like Beagle
--- Tom Grove [EMAIL PROTECTED] wrote: backyard wrote: --- Tom Grove [EMAIL PROTECTED] wrote: Is there something like beagle that runs on FreeBSD? If not is it something that people would like to see ported? -Tom Beagle the personal data indexer, or open beagle the evolutionary computation system? The personel data indexer seems cool to me. the evolutionary computation system isn't something I would personally find useful. my two cents -brian I am referring to the data indexer. I understand that it uses something called iNotify within the Linux kernel and that is why it may not be a very nice port to *BSD. I am wondering if it would be possible to use something like kqueue to notify the calling program of a disk write like iNotify does. that sounds logical, but since beagle is a gnome item isn't there an existing gnome function that wraps kqueue into its API to do somekind of fast indexing or track file changes? Not a programmer sorry, but I seem to recall something along those lines when I was reading the descriptions to the ports I had installed while setting the knobs for my rebuild. I could look into that more if so desired... Just throwing out thought because I think that a desktop search tool would be well received with the desktop BSD community. -Tom I would tend to concur with that. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using portconf and /usr/local/etc/ports.conf
--- James Long [EMAIL PROTECTED] wrote:
Date: Mon, 9 Oct 2006 05:15:28 -0700 (PDT)
From: backyard [EMAIL PROTECTED]
Subject: Re: Using portconf and
/usr/local/etc/ports.conf
To: freebsd-questions@freebsd.org
Message-ID:
[EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
if ruby uses ncurses, that blue menu thing, you
have
to add BATCH=Yes as a build option to skip the
menu
and build it with the options you have selected.
You missed the point. If I were to set batch mode
on, then
I meant set BATCH as an option only to the ruby knob,
then it would only apply to that build.
it would just build WITHOUT the options I selected.
The fact
that the config box came up with RDOC and IPV6 still
selected
suggests to me that portconf isn't recognizing my
entries in
ports.conf.
maybe but if portconf doesn't automatically apply a
BATCH build then you WILL ALWAYS get a screen that
will default to what is in the Makefile, not what you
passed to make -DFOO -DBAR. Unless you use the
previous options but I'm not certain how to tell make
to use the existing options file.
don't know much about portconf
Thanks all the same.
is portconf supposed to automagically apply a batch
build??? I'm confused...
that is why I keep it simple with stuff like this
.if {CURDIR:M/usr/ports*}
include /foo/bar/ports.conf
.endif
in make.conf
I also do stuff like that to include sup files so I
can independantly update ports and src because when
both are set in the make.conf it seems to always
update both. sometimes this is not what I really want.
and in ports.conf
.if {CURDIR:M*/lang/ruby18}
# comment out all the build options
# from the Makefile copyed in for reference
#
BATCH=YES
WITHOUT_IPV6=yes
WITH_FOOBAR=YES
WITH_STUFF=no # == WITH_STUFF=YES, use WITHOUT_STUFF
.endif
there was a nice thing I found on google when
searching
retaining options portupgrade
or something along those lines. Why use ports to do
something make already understands. At least that is
my logic. especially if you have to type up a
configuration file anyway... You could keep things in
just make.conf but things get messy after a while.
good luck
-brian
Jim
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: .dmg files?
--- Drew Sanford [EMAIL PROTECTED] wrote: Is there any way to unpack a .dmg file (mac) on FreeBSD? I have checked in ports/archivers and can't find anything that looks like it will do it, and google turns up nothing of any use that I've found yet. Have I missed something, or can this really not be done? Drew http://vu1tur.eu.org/tools/ your lucky work is slow... :) cause a quick google on extension dmg found this little website. there are source files and perl scripts that supposedly do it for you. enjoy -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using portconf and /usr/local/etc/ports.conf
--- James Long [EMAIL PROTECTED] wrote:
I am trying to migrate my
/usr/local/etc/pkgtools.conf into
/usr/local/etc/ports.conf. I'm not sure I have the
ports.conf
syntax correct, or that the entries I'm making are
being
recognized.
I've installed the sysutils/portconf port
successfully, and
my make.conf is:
monitor : /root# cat /etc/make.conf
CPUTYPE?=p3
NO_PROFILE= true
USA_RESIDENT=YES
# 2005-12-19 to build sendmail without IPv6
NO_INET6=YES
# added by use.perl 2006-01-05 14:23:56
PERL_VER=5.8.7
PERL_VERSION=5.8.7
# Begin portconf settings
# Do not touch these lines
.if !empty(.CURDIR:M/usr/ports*)
exists(/usr/local/libexec/portconf)
_PORTCONF!=/usr/local/libexec/portconf
.for i in ${_PORTCONF:S/|/ /g}
${i:S/%/ /g}
.endfor
.endif
# End portconf settings
I have this line in /usr/local/etc/ports.conf for
ruby18:
lang/ruby18: WITHOUT_RDOC=1 | WITHOUT_IPV6=1
if ruby uses ncurses, that blue menu thing, you have
to add BATCH=Yes as a build option to skip the menu
and build it with the options you have selected.
I then get the build options dialogue box for ruby
1.8.5_1,1 with the
tick boxes for IPV6 and RDOC checked, even though I
have ports.conf
entries to turn them off.
Is this my goof, or is something wrong with
portconf?
don't know much about portconf, I configure my ports
directly with make.conf and a seperate file ports.conf
that gets included in the build when in the ports tree
I am. But whith what you describe the batch option
needs to be set because the build dialog uses it's own
defaults separate from command line flags, and if your
setting command line flags there is no need to use the
dialog box.
-brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: minimum requirements
--- free bsd [EMAIL PROTECTED] wrote: Thank you everyone for responding to my initial question. In hindsight I realize I worded my original inquiry inaccurately. What I am attempting to determine is how well or if ver 6.1 will work on a 4GB hard drive with a Pentium 4 - 3.06GHz cpu and 1GB ram? The machine has a 232GB hard drive but I have another 4GB drive sitting around being unused that I was thinking of adding to the machine to configure in a dual boot setup with the 4GB drive being totally allocated to FreeBSD. However, before attempting that task I am trying to determine whether or not it would be even feasible to use a 4GB drive to install v 6.1 or should I use a larger drive to install the many of FreeBSD's features? And if a larger drive how large of a drive would I need to utilize many or any of its features without limiting myself to a bare bones setup? Additionally, if the 4GB drive will work how limited would the install/capabilities/features be? I am not at all opposed to using a larger drive but at the present time do not have a clue as to what size drive I should use for the most flexibility regarding type of installation options. -art 4gb would get you a basic setup system with X. As long as you use packages for your installation. Building ports from source will likely run you out of space during port builds especially for the larger ports. you should be able to get the system, X, KDE OR Gnome, running and a few other ports here and there. You would be better off installing something like Icewm or XFCE as these would get you nice looking window managers without all the bloat and would be able to run the apps from the bigger desktops. once the dependant libraries are installed. the issue you may run into is in swap. With 1 gig or RAM you will only need a small amount of swap, maybe as little as 64Meg. This would only be an issue if you plan on getting core dumps from the kernel, because you will not have space. This is why typically it is recommended to have swap equal to Ram plus 1 meg. And this is for a single partition of swap. the core won't split over two swaps. All in all more hard drive space is probably a good idea just for /usr and or /home space depending on what your doing. It would be a must if you want to build things from source. These base system itself will be about 500 megs, ports will add on 300 megs or so, then its the ports you choose. 4 gig would work ok, but would get frustrating quick. I would go with at least 8 gig for a loaded system which for me is about 4.5 gigs total and like 300 packages installed mostly science packages and the dependancies of gnome2. If you want to build things I run with 10-15g slices for more space. and outside of building that is more then I generally need. Although for fairness I usually have multi-boot modes and share a data drive amongst the OSs. a list of the ports you want to use would help determine space because some use a ton, and some use very little. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Something Like Beagle
--- Tom Grove [EMAIL PROTECTED] wrote: Is there something like beagle that runs on FreeBSD? If not is it something that people would like to see ported? -Tom Beagle the personal data indexer, or open beagle the evolutionary computation system? The personel data indexer seems cool to me. the evolutionary computation system isn't something I would personally find useful. my two cents -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Good References and or Books for learning ADA
--- RW [EMAIL PROTECTED] wrote: On Thursday 05 October 2006 02:39, backyard wrote: Hello All, I'm looking to teach myself ADA using the Gnu Compiler Collection and GNATS as my compiler under an i386 FreeBSD 6.X system. I'm just curious if any ADA programmers out there can point me to some decent books/online resources for learning the basics and more advanced aspects of ADA. They would be most useful if they referenced ADA95 as that appears to be the standard gnats supports. When I did an ADA course, Barnes's Programming in Ada 95 was the standard text. That was about 8 years ago, but it's gone to a second edition since then. Thanks, Although it seems to get mixed reviews... Everyone says it isn't for beginners and some flat out blast the book. The biggest problem they say is it reads like a specification manual. I write specs at work so thats not a big deal to me, and nothing is more fun then looking through the IBC or NEC... I understand the basics of object oriented programming, classes, constructors, destructors but the syntax and semantics keeps me from writing C++ now... Does the book read like a specification manual or a tutorial? Honestly I would almost prefer the specification manual, I hate getting talked down too... But on the other hand incomprehensible specs aren't too good either. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange X problem
--- Paul Schmehl [EMAIL PROTECTED] wrote: --On Friday, October 06, 2006 15:10:21 -0400 Bob M. [EMAIL PROTECTED] wrote: Therein lies the problem. There *is* an entry in /etc/ttys: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure Guess I'll just start double-checking everything. Maybe there's a typo somewhere. Is your path to kdm correct? I've never used KDE, so I don't know for sure, but that entry in /etc/ttys is all you should need. find / -name kdm /usr/local/bin/kdm Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/ For FreeBSD, edit /etc/ttys and find the line like this: ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm off secure and edit it to this: ttyv8 /usr/local/bin/kdm xterm on secure * Most other distributions are a variation of one of these. At this stage, you can test kdm again by bringing your system to the runlevel that should now run kdm. To do so, issue a command like this: http://docs.kde.org/development/en/kdebase/kdm/configuring-your-system-for-kdm.html -nodaemon is the problem. that is for running kdm from the command line. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't get direct rendering with i915
--- Alexandre Vieira [EMAIL PROTECTED] wrote: Hello folks, I'm setting up my laptop (Acer 1644WLMi) and I noticed some days ago that I don't have direct rendering with i915+drm. Any one knows if it is supposed to be like this? the i915 drm module is still new to Release 6 of freebsd. I believe it is still in beta and not very functional. I am in the same boat as yourself with the i845 chip. I know with linux I could get a full screen console but I still have yet yo get vidcontrol to change the screen size for me. I believe the linux driver is being used as a basis for the freebsd one, but it hasn't fully been reverse engineered yet. Unless your doing OpenGL specific apps like CAD or games X will still run fine. If your doing KDE you might want to turn off all the animated and transparency junk. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Member of group wheel, but still can't shutdown system?
--- Jerry Bell [EMAIL PROTECTED] wrote: You need to be in the wheel group to be able to SU to root, but that won't give you permission to run shutdown. Only root can do that, I believe. or members of group operator. having to be root or su/sudoing is only an affliction of linux. only root can run reboot however, but the is generally frounded upon; running shutdown -r ensures a clean reboot. as a security side note the members of operator also get raw access to drives and tapes so they can run dumps of the system... -brian Hi All, I've just installed FreeBSD 6.1 and listed myself as a member of the wheel group during the add users portion of the installation. For some reason I have not put a finger on yet I cannot shutdown the system do not have permission to effect the command. Went back as root on a later session and re-entered my name in /etc/group to the wheel account to no avail, anybody got an idea as to where I need to look? Thanks, Tommy2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't get direct rendering with i915
--- Alexandre Vieira [EMAIL PROTECTED] wrote: On 10/5/06, backyard [EMAIL PROTECTED] wrote: --- Alexandre Vieira [EMAIL PROTECTED] wrote: Hello folks, I'm setting up my laptop (Acer 1644WLMi) and I noticed some days ago that I don't have direct rendering with i915+drm. Any one knows if it is supposed to be like this? the i915 drm module is still new to Release 6 of freebsd. I believe it is still in beta and not very functional. I am in the same boat as yourself with the i845 chip. I know with linux I could get a full screen console but I still have yet yo get vidcontrol to change the screen size for me. I believe the linux driver is being used as a basis for the freebsd one, but it hasn't fully been reverse engineered yet. Unless your doing OpenGL specific apps like CAD or games X will still run fine. If your doing KDE you might want to turn off all the animated and transparency junk. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hello, I don't know about your problem but I installed graphics/dri and everything works pretty fine now. Regards DRI fails to find /dev/agpgart is my problem. The driver doesn't seem to create the proper devices for DRI to even utilize. That seems to be my problem anyway. I haven't done much OpenGL with it anyway, and with only 8megs of VRAM max I don't plan on doing anything serious. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vr0: watchdog timeout FreeBSD 6.1-p10 Crashing my backups
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Oct 4, 2006, at 10:32 AM, perikillo wrote: My kernel file is this: machine i386 cpu I686_CPU You should also list cpu I586_CPU, otherwise you will not include some optimizations intended for Pentium or higher processors. are you sure about this??? This statement seems to contradict the handbook which says it is best to use only the CPU you have I would think I686_CPU would cause the build know it is higher then a pentium and thus use those optimizations. But if this is true... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Good References and or Books for learning ADA
Hello All, I'm looking to teach myself ADA using the Gnu Compiler Collection and GNATS as my compiler under an i386 FreeBSD 6.X system. I'm just curious if any ADA programmers out there can point me to some decent books/online resources for learning the basics and more advanced aspects of ADA. They would be most useful if they referenced ADA95 as that appears to be the standard gnats supports. I would also be interested in resources that describe integrating (I guess linking is more appropriate of a term) C/C++ libraries with ADA. This would mostly be for basic use with X Windows and Motif, GTK, or whatever makes the windows looks nice when I get that far, and OpenGL rendering, and likely ATLAS for crunching numbers. Unless there exists some ADA libraries for any of the above. I went to Borders today and couldn't find anything and a search online would comes up with millions of books that may or may not be useful. I guess I shouldn't be too supprised I couldn't even seem to find a book on Bind at Borders... thanks, -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Good References and or Books for learning ADA
--- Beech Rintoul [EMAIL PROTECTED] wrote: On Wednesday 04 October 2006 17:39, backyard wrote: Hello All, I'm looking to teach myself ADA using the Gnu Compiler Collection and GNATS as my compiler under an i386 FreeBSD 6.X system. I'm just curious if any ADA programmers out there can point me to some decent books/online resources for learning the basics and more advanced aspects of ADA. They would be most useful if they referenced ADA95 as that appears to be the standard gnats supports. I would also be interested in resources that describe integrating (I guess linking is more appropriate of a term) C/C++ libraries with ADA. This would mostly be for basic use with X Windows and Motif, GTK, or whatever makes the windows looks nice when I get that far, and OpenGL rendering, and likely ATLAS for crunching numbers. Unless there exists some ADA libraries for any of the above. I went to Borders today and couldn't find anything and a search online would comes up with millions of books that may or may not be useful. I guess I shouldn't be too supprised I couldn't even seem to find a book on Bind at Borders... I can't help you with ADA, but the O'Reilly book on bind is the best one. Borders can order it and get it to you in a couple of days. They even get them that fast up here in Alaska. Beech thanks, thats the one I was looking for and certain I'd scene before but no luck tonight. ofcourse I had no trouble finding the complete freebsd tonight which is what took me hours to find last time amungst the books on bind... the luck of the irish is a lie... does that book cover running bind within a jail? or just the general configuration of the service? -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Good References and or Books for learning ADA
--- Beech Rintoul [EMAIL PROTECTED] wrote: On Wednesday 04 October 2006 18:57, backyard wrote: --- Beech Rintoul [EMAIL PROTECTED] wrote: On Wednesday 04 October 2006 17:39, backyard wrote: Hello All, I'm looking to teach myself ADA using the Gnu Compiler Collection and GNATS as my compiler under an i386 FreeBSD 6.X system. I'm just curious if any ADA programmers out there can point me to some decent books/online resources for learning the basics and more advanced aspects of ADA. They would be most useful if they referenced ADA95 as that appears to be the standard gnats supports. I would also be interested in resources that describe integrating (I guess linking is more appropriate of a term) C/C++ libraries with ADA. This would mostly be for basic use with X Windows and Motif, GTK, or whatever makes the windows looks nice when I get that far, and OpenGL rendering, and likely ATLAS for crunching numbers. Unless there exists some ADA libraries for any of the above. I went to Borders today and couldn't find anything and a search online would comes up with millions of books that may or may not be useful. I guess I shouldn't be too supprised I couldn't even seem to find a book on Bind at Borders... I can't help you with ADA, but the O'Reilly book on bind is the best one. Borders can order it and get it to you in a couple of days. They even get them that fast up here in Alaska. Beech thanks, thats the one I was looking for and certain I'd scene before but no luck tonight. ofcourse I had no trouble finding the complete freebsd tonight which is what took me hours to find last time amungst the books on bind... the luck of the irish is a lie... does that book cover running bind within a jail? or just the general configuration of the service? I'm pretty sure it does, but my copy is at the office so I can't say for sure. However, the book is VERY detailed about all aspects of bind. It really is a must read for anyone serious about running nameservers. For example, it shows you how to split the nameserver so you can resolve your entire inside lan, but outside it will only resolve the servers you choose. It's also is very detailed about how to set up dynamic hosts. Beech -- that is one of the things I wanted to know how to do properly... This is Just O'Rielly; Bind or is it one of those in a nutshells books. Just want to make sure before I pick up the wrong one. I trust it covers version 9? if you don't mind and can remember when you get back to the office can you send the ISBN just in case I need to order it. or a quick search on Amazon came up with DNS and Bind 5th edition by Cricket Lui and Paul Albitz O'Reilly Publishing is this the one your refering too? -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restoring FreeBSD grub loader
--- Ivan \Rambius\ Ivanov [EMAIL PROTECTED] wrote: Hello, Thank you for your response. On 10/1/06, backyard [EMAIL PROTECTED] wrote: --- Ivan \Rambius\ Ivanov [EMAIL PROTECTED] wrote: Hello, I installed FreeBSD 6.1 on one machine with grub boot loader. In the beginning there was only one entry in grub - namely FreeBSD. Later, I had to install Windows XP on the machine and of course, it destroyed grub and now I cannot boot FreeBSD. I tried with booting from the FreeBSD installation disk choosing Fixit option, but I could not use successfully grub-install command. My question is: how can I restore the FreeBSD grub loader? Could you please give me any hints or advance. Thank you very much in advance. Regards Ivan -- I would suggest you make a grub booting floppy disk then you can escape to command mode once the disk loades and install grub with root (hd0,0,a) # or wherever it is setup (hd0 # again wherever it is assuming you have already placed the grub bootfiles on your hard drive and configured menu.lst you should be all set. I have only encountered one computer this method failed. In fact, I am using a laptop that does not have a floppy drive, so I could not use booting floppy disks. I use a USB floppy drive to boot my laptop and install grub. Although I haven't been able to use fdformat with the floppy drive so I use one of my desktops to prapare the disks. you could alternatively flip the kernel tunable that allows raw writes to the boot sectors of the disks. I don't recall what it is but I think the grub docs talk about it in the man or info pages. I'm supprised XP messed it up, 2000 seemed to respect existing bootloaders... I fixed the problem in the following way: I have another FreeBSD laptop, so I copied its boot sector using the command # dd if=/dev/ad0s1a of=/mnt/bootsect.bsd bs=512 count=1 I've used that method myself when grub hadn't been updated to support UFS2. I had completely forgotten about it though. Then I used bootsect.bsd to to boot in FreeBSD via the NT loader (I found this link useful: http://www.unixguide.net/freebsd/faq/09.10.shtml). After I boot to FreeBSD I installed the grub loader. to each their own; the beauty of Unix... glad you got it working. Regards Ivan -- -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restoring FreeBSD grub loader
--- Ivan \Rambius\ Ivanov [EMAIL PROTECTED] wrote: Hello, I installed FreeBSD 6.1 on one machine with grub boot loader. In the beginning there was only one entry in grub - namely FreeBSD. Later, I had to install Windows XP on the machine and of course, it destroyed grub and now I cannot boot FreeBSD. I tried with booting from the FreeBSD installation disk choosing Fixit option, but I could not use successfully grub-install command. My question is: how can I restore the FreeBSD grub loader? Could you please give me any hints or advance. Thank you very much in advance. Regards Ivan -- I would suggest you make a grub booting floppy disk then you can escape to command mode once the disk loades and install grub with root (hd0,0,a) # or wherever it is setup (hd0 # again wherever it is assuming you have already placed the grub bootfiles on your hard drive and configured menu.lst you should be all set. I have only encountered one computer this method failed. you could alternatively flip the kernel tunable that allows raw writes to the boot sectors of the disks. I don't recall what it is but I think the grub docs talk about it in the man or info pages. I'm supprised XP messed it up, 2000 seemed to respect existing bootloaders... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystem size
--- Weijer [EMAIL PROTECTED] wrote: Can anyone tell me if Freebsd 5.4 amd64 support file system more than 4TB ? I have a system disk and a raid 5 connected to a 3ware controller, installed system, but only see 96 GB on the 4 TB raid 5. Anyone can help me? My mailbox is spam-free with ChoiceMail, the leader in personal and corporate anti-spam solutions. Download your free copy of ChoiceMail from www.digiportal.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://www.freebsd.org/projects/bigdisk/index.html would answer your questions I believe -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd 6.1 floppy installation problem - boot loader finds only 16MB, but I have 256 MB - and it hangs
--- Vo¹tenák Vladimír [EMAIL PROTECTED] wrote: Hi I have an old HP NETSERVER PRO 2xpentium pro, 256 MB ram, and I tried to install the actual FREEBSD 6.1 there. I made 3 floppies: boot, kernel1 and kernel2. When it starts booting from the boot floppy, the loader show I only have 16 MB of RAM (instead 256MB I have there). Then it asks for kernel1 and 2 disk, and boot disk again. It gives me also the entry FREEBSD display with countdown - to choose boot type - default, no acpi, secure etc. I tried it all, but it alwaysl hangs after about 5 second after any choice. So I must just reboot. I think it is just because the lack of RAM, because, I think it requirets at least 24 MB of RAM. I have found something about this on the web, that it is necessary options MAXMEM=n to use all the RAM, because old BIOSes shows just first 16 MB or so, but I am just doing the installation. So how can I modify the kernel on the floppies to use such option during the installation from floppies? Or should I install from other media???Please can you help me with this??How can I make the installation boot floppy see all the RAM I have? Thank you very much for your reply. Greetings Vladimír Vo¹tenák make sure you don't have OS/2 compatability mode in your BIOS turned on. That will limit a system to 16 megs of RAM. I haven't played with an HP Netserver but I have several Kayaks that run things fine with about the same aged bios. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Want to install RELEASE-6.1, have 5.3 disks
--- Jason Artz [EMAIL PROTECTED] wrote: --- Chad Leigh -- Shire.Net LLC [EMAIL PROTECTED] wrote: On Sep 23, 2006, at 2:34 PM, Jason Artz wrote: Hello, I want to install FreeBSD 6.1 on my system, but I only have a version 5.3 CD. I can tell sysinstall to get 6.1 instead of 5.3 via FTP (under Options, Release name), but I read that using an old sysinstall to install a new version is a bad idea. I cannot figure out how to obtain a new sysinstall without making boot floppies (I have no floppy drive nor a CDRW). Can I install 5.3 and then somehow upgrade via FTP to 6.1? Or download the new sysinstall to my 5.3 installation, run it, and install 6.1 instead? What's the best method? Can you just download the 6.1 iso disks and make new installer disks? Otherwise, you can install 5.3 and use cvsup to upgrade to 6.1 through a source upgrade. Just follow the instructions carefully. Is there a way to do a binary install instead of downloading all the new sources and compiling them as an upgrade? I don't have a floppy or CDRW drive so I cannot burn new installer disks. I am stuck with 5.3 installer disks. It seems that there should be a way for me to do a fresh, binary install of 6.1 from 5.3. What if someone sent me a copy of 6.1s sysinstall and I ran it from the 5.3 environment? Would that allow me to do a proper, fresh 6.1 install via FTP? I have tried installing 6.1 with my sysinstall and it will not boot. Anyone have any ideas? Thanks, Jason ___ I thought if you went to the options in sysinstall and go to the part that says Release Name and it likely is going to say 5.3-RELEASE change that to 6.1-RELEASE and then do an ftp install. You should get the newer version of the system. I have used this to install 5.4-CURRENT in th past from 5.4 bootdisks. I would have to assume it should work for a newer release as the distribution is packed the same. I know this is how one would have sysinstall choose an arbirtrary custom built installation of FreeBSD from say an NFS mount. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Resizing Partitions, Losing Windows XP...
--- Jeff Cross [EMAIL PROTECTED] wrote: I really like the way I have my stuff setup within FreeBSD and would hate to have to recreate a lot of it as well as install applications over again. Could I do a dump of my current FreeBSD partition, reformat and partition the whole drive, install FreeBSD, and then restore my data to the new partition or would this cause issues? Any assistance is greatly appreciated! Jeff Cross http://www.averageadmins.com/ Yes failrly easily you can back everything up to tape first you must find a suitable backup medium such as a USB hard drive. I use a 5 gig seagate drive I picked up along the way. This allows a typcial root, var and about 5.6 gig of stuff on /usr. With compression things aught to work. You might want to clean up /usr/ports/distfiles, /usr/obj, and run a cd /usr/ports; make -DNOCLEANDEPENDS clean to get rid of any unnecessary files, but this is up to you. then... I would suggest booting to safe mode on your current FreeBSD install first of all then do a #fsck -p for paranoia #swapon -a for swap # mount -a -o ro to mount the partitions read only. this isn't required but if the drives are rw you need -L as a switch to the dump command below. mount -u /tmp dump will use /tmp then mount you backup media whereever you want I will use /mnt as my mount point I also assume you have separate partions for each drive. then this monster will backup everything (dump -0 -C 32 -f - / | bzip2 | dd of=/mnt/root.dbz2) (dump -0 -C 32 -f - /var | bzip2 | dd of=/mnt/var.dbz2) (dump -0 -C 32 -f - /usr | bzip2 | dd of=/mnt/usr.dbz2) then grab a coffee and wait for the tapes to be made. now to restore there are better ways to do it but this method has worked for me... reboot with the FreeBSD install disk go to fdisk and delete the old slices and create the new slice. Use all disk, I would not do this dangerously dedicated keep it compatible I've had boot issues with boot drives in dangerously dedicated mode. hit w to write the table it will ask if you are sure say yes and install the boot loader you want, standard MBR or the boot manager, your choice. reboot load up the cd and do bsdlabel mode setup root, usr, var, tmp, swap whatever you use as a partitioning scheme. this tool will require a root partitio to be specified to work. then w to write the label now go to fixit mode on the cd and you'll be at a prompt. if your backup media was Fat32, ext2, basically anything but UFS1 or 2 you will type sysctl kern.module_path=/dist/boot/kernel to let the kernel find the right modules to support fat32 then I generally do a mkdir /TAPE and mount the backup media there. you should also have the swap already loaded and root will be mounted on /mnt usr will be /mnt/usr and var will be /mnt/var next type #mdconfig -a -t swap -s 512m this will give you a md node prolly md1 512m is what I use (512 mb of swap) but less may work fine. #newfs md1 mkdir /junk; mount /dev/md1 /junk; cp /tmp/* /junk/; umount /junk; mount /dev/md1 /tmp restore will need this tmp directory to have space or things will get messy then I would #umount /mnt/var /mnt/usr /mnt then I usually reformat the partitions to get rid of annoying error messages about directories alrady being present during the restore #newfs -O 2 -L root -n /dev/ad0s1a (adjust your device as required the -L option isn't necessary #newfs -0 2 -L var -U -n /dev/ad0s1d #newfs =O 2 -L usr -U -n /dev/ad0s1e again adust the devices as required then remount root to /mnt then #bzip2 -dc /TAPE/root.dbz2 | (cd /mnt; restore -r -f -) mount var and usr then repeat for them with cd /mnt/usr and cd /mnt/var as required. make any changes to /mnt/etc/fstab as required, unmount everything and you should be good to go for a reboot. you may get some expected 23423234 got 234253546 messages in the restore. a few of them aren't a problem. As suggested by others MAKE SURE YOUR DUMPS ARE GOOD PRIOR TO DOING THE RESLICING AND PARTITIONING you can use that restore command to restore to whereever you want with the right change dir so find some free space and doit. even if you run a newfs on the windows slice and mount it unlabeled just to see the dumps are good, and assuming you don't care about windows being lost. after the reboot delete the restoresymtable files on each of the filesystems of course if you know fdisk and bsdlabel from the command line using a freesbie live cd would prolly make this easier and not require a reboot after the fdisk... I have had issues with the drives being able to boot up so I generally like to use grub. so readup on manually installing the MBR or boot manager just in case. I think my last restore I just chose the standard MBR and everything went fine. good luck -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail to root
--- Roger 'Rocky' Vetterberg [EMAIL PROTECTED] wrote: jekillen wrote: Hello again; I have a question about how mail from the system is generated for root. This question was prompted when I edited the Postfix aliases file and ran newaliases, then did postfix reload, assuming the mail system was running. I was informed that Postfix was not running. So the question, how does mail generated by the system get delivered to the root account? Here is my motive: I have a server that I want to run headless. I want to be able to retrieve mail to root from another machine via ssh login (on the same private net work number/netmask 255.255.255.0). I cannot login to the system as root over ssh. I don't know if I can read root mail with su (as wheel group member). I tried this but maybe I'm not using the appropriate parameter. su - root will load up roots environment and let you check his mail. At least that worked for me last night... Or maybe there isn't any. I don't know where to look for an answer to this question, other than this knowledgeable group.Oh, man mail maybe? Thanks in advance Jeff K I suggest you use .forward to get root's mail to another account. As root, do this: echo username /root/.forward That should forward root's mail to whatever username you specified. probably the best solution for a headless box, then you don't have to su'in in to the machine. Nor risk snoops gaining the password of all passwords... -- R -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How real time is FreeBSD?
--- RW [EMAIL PROTECTED] wrote: On Thursday 21 September 2006 06:12, Walt Pawley wrote: At 11:47 PM -0500 9/20/06, W. D. wrote: Just reading this about Linux on ZDNet and was wondering: http://news.zdnet.com/2100-9593_22-6117479.html?part=rsstag=feedsubj=zd nn Cybernetic floobydust, IMHO. If you read what the banker says: for each thousandth of a second that its trading software can act faster than competitors' software, the company would see $100 million a year in new revenue. and for every extra trade they do they change the stock price faster and faster making them more money. They're creating the money by manipulating the market faster; the market doesn't create itself... How can they even quantify this so called loss when their trading is constantly changing the state of the market. It seems to me that they are really misunderstanding the problem. What they need is a system that's fast most of the time, rather than one that meets an arbitary deadline all the time. In other words they need a fast system, not a realtime system. I would imagine an extra 100 million would buy quite a dusy of a system at that... processing data at a rate of 1000 Hz doesn't seem to suggest a real-time system is required when the average clock is 1 million times faster then that. its not like they're doing FFT's on a Radar signal, to determine if its a bogey and arming the appropriate countermeasures so they can be deployed the second the blip appears on the operators screen. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How real time is FreeBSD?
--- Jerry McAllister [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2006 at 08:21:10AM -0700, backyard wrote: --- RW [EMAIL PROTECTED] wrote: On Thursday 21 September 2006 06:12, Walt Pawley wrote: At 11:47 PM -0500 9/20/06, W. D. wrote: Just reading this about Linux on ZDNet and was wondering: http://news.zdnet.com/2100-9593_22-6117479.html?part=rsstag=feedsubj=zd nn Cybernetic floobydust, IMHO. If you read what the banker says: for each thousandth of a second that its trading software can act faster than competitors' software, the company would see $100 million a year in new revenue. and for every extra trade they do they change the stock price faster and faster making them more money. They're creating the money by manipulating the market faster; the market doesn't create itself... How can they even quantify this so called loss when their trading is constantly changing the state of the market. Yes, Mr Heisenberg... if you buy the stock goes up if you sell the stock goes down. how can one calculate how long your car will last if it is based on how you drive and how many red cars you see; considering how you drive is dependant on how many red cars you see... I say my car will last 10 years longer then the competition if I see one more red car then them on my way to work... the only thing that is certain is death, taxes, and uncertainty. It seems to me that they are really misunderstanding the problem. What they need is a system that's fast most of the time, rather than one that meets an arbitary deadline all the time. In other words they need a fast system, not a realtime system. I would imagine an extra 100 million would buy quite a dusy of a system at that... processing data at a rate of 1000 Hz doesn't seem to suggest a real-time system is required when the average clock is 1 million times faster then that. its not like they're doing FFT's on a Radar signal, to determine if its a bogey and arming the appropriate countermeasures so they can be deployed the second the blip appears on the operators screen. They have all kinds of calculus and successive approximations in their models. The more CPU they have, the more they add to the design. you know, I forgot how trivial a fast fourier transform is to compute on a 2-10 GHz signal... So they add more to the design to process more calc and propabilities based on past events in likely a recursive fashion and get back to deadlocking the systems with math and having real time processing is going to fix this? I think this is the managers solution to not listening to IT telling them they need more powerful cores on the cluster to handle processing thousands of tickers at once, while crunching the nastiest of nastiest probablities and executing trades. Fixing software is always cheaper then buying hardware. of course I'm likely slightly jaded due to dealing with architects all day; that and a pushy financial advisor trying to sell me their services... jerry -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
Hello,
I'm having trouble building tcl84. These issues did
not seem to exist until I updated the ports tree and
world the other day
Heres the basic stuff:
FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38
is what uname -a spits out ports were updated right
before the system source update.
make.conf has
CFLAGS=-pipe -O2 -fno-strict-aliasing
CXXFLAGS+=-O3 -fno-strict-aliasing
COPTS=-pipe -O2 -fno-strict-aliasing
CPUTYPE=pentium4m
MAKEOPTS=-j5
my ports.conf has:
.if ${.CURDIR:M*/lang/tcl84}
WITH_THREADS=YES
BLACKHOLE=YES
.endif
ports.conf is loaded into make.conf with this
.if ${.CURDIR:M/usr/ports*}
include /foo/bar/ports.conf
.endif
I use it to make configuring ports easier and more
standard then the portupgrades configuration method.
I initially attempted to rebuild the system with
portupgrade -afR
but found tcl84-threads hanging on socket test 7.4
although it says every single test fails. So because
my system was a little messed up due to having half of
gnome-2.12.x and gnome-2.14.x because of updating the
ports tree halfway through the build to start because
of a then broken port... and now because of a hlf
rebuilt system. I decided to do a pkg_delete -a and
start over from scratch to see if my configs would
work right. The port still halts on socket 7.4 test,
and halted at one point for 8+ hours when I was off at
work.
on a tangent Xorg seemed to be busted after being
rebuilt and configured (X -configure) I did notice
something about drm in the kernel now is I915 support
in there now???
I've read socket test hangs could be because the
tunable net.inet.tcp.blackhole is enabled but it is
not on my system. That is why I added BLACKHOLE=YES to
my config to try to disable the tests as the Makefile
suggests but the build seemed to ignore me.
then I starting getting these kernel panics. Once
while it was testing and the next time right after I
rebooted in to single user mode to assess filesystem
damage.
Fatal double fault:
eip=0xc0729c9c
esp=0xdc4fe00c
ebp=0xdc4feb78
panic: double fault
I suspect that my 2nd dimm banks memory controller has
finally shit the bed in my laptop, but post cause
maybe it is related. I'm not certain what a double
fault is exactly; not off a tennis court anyway...
I will see if I can find the reason for the double
faults by removing the likely unreadable memory stick
and attempt to update the source and ports trees and
see if that helps, but not before dumping my system to
tape.
any help would be appreciated.
-brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard wrote: Hello, I'm having trouble building tcl84. These issues did not seem to exist until I updated the ports tree and world the other day Heres the basic stuff: FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 is what uname -a spits out ports were updated right before the system source update. make.conf has CXXFLAGS+=-O3 -fno-strict-aliasing Don't do that, it can cause problems can you be a little more specific? I was just using CXXFLAGS+=-O3 before I thought the aliasing issues because of type casting could cause issues and so -fno-strict-aliasing was what you had to do to make optimization above level 1 work rigt. At least thats what reading about -fno-strict-aliasing seemed to get at with FreeBSD specifically. should it be CXXFLAGS+= dafaulting to O2 with no strict aliasing? given my CFLAGS=-pipe -O2 -fno-strict-aliasing MAKEOPTS=-j5 Don't do that, it can cause problems I know doing make -j5 buildworld or buildkernel or just about anything else would/used to puke things. But I haven't seen any issues with MAKEOPTS doing that. Perhaps until now? I know specifically make -j5 on the shell would cause the build to skip the build and fail on the install or skip the build of the objects and fail on linking the uncompiled library. kris dazed confused and ignorant... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TCL84 Build error Socket Tests Hang FreeBSD 6.1-Stable #6
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2006 at 06:29:52PM -0700, backyard wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: On Thu, Sep 21, 2006 at 06:11:52PM -0700, backyard wrote: Hello, I'm having trouble building tcl84. These issues did not seem to exist until I updated the ports tree and world the other day Heres the basic stuff: FreeBSD 6.1-STABLE #6 Sun Sept 17 22:03:38 is what uname -a spits out ports were updated right before the system source update. make.conf has CXXFLAGS+=-O3 -fno-strict-aliasing Don't do that, it can cause problems can you be a little more specific? I was just using CXXFLAGS+=-O3 before I thought the aliasing issues because of type casting could cause issues and so -fno-strict-aliasing was what you had to do to make optimization above level 1 work rigt. At least thats what reading about -fno-strict-aliasing seemed to get at with FreeBSD specifically. should it be CXXFLAGS+= dafaulting to O2 with no strict aliasing? given my CFLAGS=-pipe -O2 -fno-strict-aliasing Just use the defaults (which is currently the same as your CFLAGS). MAKEOPTS=-j5 Don't do that, it can cause problems I know doing make -j5 buildworld or buildkernel or just about anything else would/used to puke things. But I haven't seen any issues with MAKEOPTS doing that. Perhaps until now? I know specifically make -j5 on the shell would cause the build to skip the build and fail on the install or skip the build of the objects and fail on linking the uncompiled library. The base system is fine, but many ports of third party software fail to build (or the build misbehaves) with make -j. Kris well I'll see if I have any better luck with the more conservative CXXFLAGS and the removal of -j5 from MAKEOPTS. I have a conditional build directive for the system build so I can update ports and sys separately as having SUPFILE and PORTSUPFILE set seems to update both whether I'm in /usr/ports or /usr/sys with a make update. If -j5 is safe for the FreeBSD build I'll cut Makeopts into that knob, I hope thats the right way to use that term... thanks -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sshd brute force attempts?
--- Dan Mahoney, System Admin [EMAIL PROTECTED] wrote: On Tue, 19 Sep 2006, backyard wrote: In reality using passwords with SSH kinda defeats the purpose of SSH. Keeping passwords from being sent across the network as cleartext? -Dan ssh will encrypt them of course but... the nosey snoop watching over your shoulder can see the keys you type, or the tricky guy that has installed a STDIN monitor hack, or enabling debugging of the console by mistake and having it appear in the syslogs. Using keys means you never have to use a password, other then locking the key. The key should always have a different password from the login. Using keys is the point of SSH so you can eliminate passworded logins making sure no one sees them at all. -brian -- Of course she's gonna be upset! You're dealing with a woman here Dan, what the hell's wrong with you? -S. Kennedy, 11/11/01 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sshd brute force attempts?
--- Dan Mahoney, System Admin [EMAIL PROTECTED] wrote: Hey all, I've looked around and found several linux-centric things designed to block brute-force SSH attempts. Anyone out there know of something a bit more BSD savvy? My best attempt will be to get this: http://www.csc.liv.ac.uk/~greg/sshdfilter/index_15.html running and adapt it. I've found a few things based on openBSD's pf, but that doesn't seem to be the default in BSD either. Any response appreciated. -Dan -- Is Gushi a person or an entity? Yes -Bad Karma, August 25th 2001, Ezzi Computers, Quoting himself earler, referring to Gushi Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- well you could pretty much eliminate the problem by disabling password logins to sshd and only accepting keyed logins. Then only a key will work. Frequently changing the keys would ensure hackers would have to want to get in REALLY bad in order to gain unauthorized access by a brute force attempt. Depending on how hosts login and their systems, you could perhaps run a login script that regenerates keys automatically and distributes them to the user every so many days or whatever so the system appears passwordless to them, and secure to the outside. This may be more trouble then you are looking for though. In reality using passwords with SSH kinda defeats the purpose of SSH. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: quick question regarding /usr/obj
--- Migs [EMAIL PROTECTED] wrote: Erik Trulsson wrote: On Mon, Sep 18, 2006 at 05:06:09PM +0800, Migs wrote: I just did a rebuild recently, and saw in the handbook that i can take out /usr/obj with no problems... and seeing as its taking up 500mb, I do want to trim it out... However, in uname -a it shows FreeBSD shadow.meridiantelekoms.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Mon Sep 18 15:35:23 PHT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARMITAGE i386 and no reference of my kernel in /boot, aside from /boot/kernel... Now, my question is, is the custom kernel I built also /boot/kernel? or does it reside in /usr/obj/usr/src/sys/ARMITAGE? Yes. The kernel you built was built in /usr/obj/usr/src/sys/ARMITAGE/, but is installed into /boot/kernel/. Once you have installed the world+kernel that you built you can safely delete everything under /usr/obj/. The handbook did say it was OK to nuke, but didn't really explain what happened in that directory very clearly. Thanks! -- Migs Registered Linux user # 381619, but has shifted to FreeBSD Random Musings (http://lifelin.blogspot.com/) /usr/obj is left around so you can do partial upgrades (something you should know exactly what you are doing when attempted), and/or rebuild the kernel without having to go through a buildworld again. The updating instructions for FreeBSD recommend you manually delete this directory prior to an upgrade to avoid any possible troubles with only binaries being left around in the build dir. to free up space I haven't nuked this dir but will in my next backup. also it is nice to run cd /usr/ports make -DNOCLEANDEPENDS clean to clean up the ports tree and not have it take a week. the -DNOCLEANDEPENDS will just make it go directory by directory without redundantly running a clean on the dependancies for each port also your can safely delete /usr/ports/distfiles as each time you update ports some of these files become obsolete anyway. I believe a cd /usr/src make clean is supposed to delete the files in /usr/obj anyway, but given what the handbook says on updating this might not be so reliable. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rebooting into single user mode on a remote server
--- Bob [EMAIL PROTECTED] wrote: On Sunday 17 September 2006 23:51, backyard wrote: modems are relatively cheap. And, if you put it into call-back mode, it becomes one of the most secure methods of doing a remote serial console; plus you have the added advantage of the remote site footing the bill for the call :-) Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] and billing a client directly for working on their equipment is always better then waiting on POs... By call-back mode do you mean log into the system via network and have it call your local system for administration, or is it like a *69 scenario. Its been a while since I played with my modem. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: which xorg file??
--- Gary Kline [EMAIL PROTECTED] wrote: On Mon, Sep 18, 2006 at 11:20:20AM -0400, Jerry McAllister wrote: On Sun, Sep 17, 2006 at 05:52:54PM -0700, Gary Kline wrote: Folks, Which ports file do I build to fill the standard /usr/X11R6/bin file? I have 6.1-RELEASE and having migraines with getting the necessary files. If installing gnome|kde-lite is/may be part of it, can somebody clue me in? if you have gone to these directories within the ports system and did an install; xorg would have been installed as a dependancy along the way. so this could have solved things in a roundabout way. Well, if you did a fresh FreeBSD 6.1 install using sysinstall, the best thing would have been to check 'yes' for installing X. It would have done it all for you. As for installing afterward, I think you probably want /usr/ports/x11/xorg I checked the install last night and watched as x11/xorg was installing multiple X/xorg packages so this may be *it*. (I-hope, I-hope.) if xorg is installing now something will be there in a little while, patience grasshopper. xorg is just a meta-package This means its a Makefile that checks if the actual packages are installed: xorg-libraries xorg-clients xorg-servers xorg-documents xorg-nestedserver xorg-fonts-100dpi xorg-fonts-75dpi xorg-fonts-cyrillic xorg-fonts-type1 xorg-fonts-miscbitmaps xorg-fontserver and builds as required. you could manually go one by one and build them, then the meta-port would just install itself doing seamingly nothing... and thats from memory, so no quoteing (read the Makefile if your really curious), and finishing up tweaking my personal ports.conf configuration file in anticipation of an upgrade build... These can take a while to build. a good 3-6 hours depending on your hardware. and your MAKEOPTS in your make.conf... gary jerry tia, gary -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rebooting into single user mode on a remote server
--- Bob [EMAIL PROTECTED] wrote: On Monday 18 September 2006 13:51, backyard wrote: By call-back mode do you mean log into the system via network and have it call your local system for administration No modems like the US Robotics V.Everything can be programmed with a call-back feature. You dial up the modem, it askes you for a password, you supply the password, and it then hangs up on you, picks up the line, and calls back a configured phone number. You program the modem to call YOU back on a number which has a modem connected, and waiting for an inbound data call. your modem answers, and you are connected. You then negotiate access to the server (name/passwd) over the serial link. If the remote is connected to the the target serial port consol, you have a pretty hack-proof (nothing is really hack-proof) console access. The modem will only call a pre-set number, so even if someone got your password, the modem would only call you, not the hacker. Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] so thats why the Couriers were the Cadillacs of the phone lines... Never had one with such fancyness built-in to it. That is good to know for the future. I would concur security is an illusion we fill with smoke and mirrors to confuse management... I especially like messing with IT at my job when they tell me they have locked access off the network with a new administrators password and Windows Server 2003... Of course they don't lock the doors on the server room so I can go in there with a boot disk of my liking and gain access to whatever I want, or run a bulk tape eraser passed the RAIDS... :) now if I can just convince the head of IT he doesn't need that Courier V.Everything anymore... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Suggestions for embedded systems... ?
--- Brian J. McGovern [EMAIL PROTECTED] wrote: All, I've been browsing the FreeBSD site looking for a system I can embed in the car. Optimally, it will do video output via a RCA cable (ala your VCR) so I can plug it in to one of the new Alpine radios with an AUX in. Input will probably come via a USB gaming pad (arrow keys, a few buttons, and 16-20 keys). I'd like to have bluetooth and 802.11b/g for communicating with a base station and the in car GPS and phone audio systems. USB (4-6 ports) would be perfect - I can get the keyboard, bluetooth, 802.11g, and ODB II connectors in without a hub. Most I've seen boot from compact flash, but booting from a USB thumb drive or SD ram would also be useful. Audio would also be nice, but I can get away with the bluetooth link. The form factor should be as small as possible for under-seat, behind-dash, or trunk installation. I've seen the Soekris systems, and they're at a good price point, but while they'd support most of what I'd need, they don't seem to have RCA video output, which would be a major plus for real time color displays of status and information (has anyone played with the USB video options available? Does FreeBSD support them?) Suggestions? Comments? Projects already done? -Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Suggestions for embedded systems... ?
--- Brian J. McGovern [EMAIL PROTECTED] wrote:
All,
I've been browsing the FreeBSD site looking for a
system I can
embed in the car. Optimally, it will do video output
via a RCA cable (ala your
VCR) so I can plug it in to one of the new Alpine
radios with an AUX in. Input
will probably come via a USB gaming pad (arrow keys,
a few buttons, and 16-20
keys). I'd like to have bluetooth and 802.11b/g for
communicating with a base
station and the in car GPS and phone audio systems.
USB (4-6 ports) would
be perfect - I can get the keyboard, bluetooth,
802.11g, and ODB II
connectors in without a hub. Most I've seen boot
from compact flash, but
booting from a USB thumb drive or SD ram would also
be useful. Audio would
also be nice, but I can get away with the bluetooth
link.
The form factor should be as small as possible for
under-seat,
behind-dash, or trunk installation.
I've seen the Soekris systems, and they're at a
good price point, but
while they'd support most of what I'd need, they
don't seem to have RCA video
output, which would be a major plus for real time
color displays of status and
information (has anyone played with the USB video
options available? Does
FreeBSD support them?)
Suggestions? Comments? Projects already done?
-Brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
sorry about the blank one I dropped/catched the
keyboard with the wrong anykey...
http://www.aaeon.com/?TabIndex=ProductsTabID=DetailCate_ID={AEEE87FC-762C-45F1-AC39-54000B62A180}Item_ID={88258D2F-17B8-4FA5-80D3-31E93126D326}Product_ID={EE4FC77D-FCFD-40EE-AA27-3CFCEA592237}
is a PC104 board I found that seems to do what you
want. I've been comtemplating this for a while.
possibly when I finally fix my eldo... This might be a
little pricey I'm not certain. Good luck with the
project and keep us up to date. I am deffinately
interested in seeing one of these come to pass. if you
do opt for compact flash make sure its read-only, you
might want to use some sort of Harddrive. this one
does EIDE.
-brian
___
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 apply a patch set
--- Ahmad Arafat Abdullah [EMAIL PROTECTED] wrote: - Original Message - From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: Matthew Seaman [EMAIL PROTECTED] Subject: Re: how to apply a patch set Date: Mon, 18 Sep 2006 00:48:32 +0200 Matthew Seaman wrote: [EMAIL PROTECTED] wrote: Hello, I am trying to apply a patch set to FreeBSD 5.5 (this letter 'p' followed by a number, after the version in 'uname -a') - but somehow it did not work. I cvsup-ed the src using the standard 'stable-supfile' with '*default release=cvs tag=RELENG_5_5' - then I rebuild world. Now 'uname -a' reports 'FreeBSD 5.5 STABLE #0'. Before it was 'FreeBSD 5.5 RELEASE #0'. So instead of applying patch set I have moved to 'STABLE'. Could somebody tell me what have I done wrong? Actually - what is the difference between the 'pX' and the '#X' after the version? You've shifted your self onto the RELENG_5 code branch rather than the RELENG_5_5 branch. Yes... but how did it happen after I instructed the supfile to get 'RELENG_5_5'? Actually in the examples/cvsup I did not find any example how to do 'release'. Thank you for the other answers! Iv. i think I've read abt this long time ago.. but not pretty sure ( someone correct me if I'm wrong ).. u can try: *default release=cvs tag=RELENG_5_5_RELEASE anyway i never tried this! and i never encounter the prob u'va said since 4.x --- 6.1 ( and I'm normally/mostly using -pX than STABLE for my prod server ). Seems your method/tag tag=RELENG_5_5 is correct way to patch to -pX, i can't find any reason why your system patched into STABLE... could u please copy+paste here your stable-supfile config? TQ STABLE is the latest set of patches to the system. It will change the tag from RELEASE from the install to the STABLE set of patches versus the CURRENT set. STABLE is the major ones you want. CURRENT is all of them to date. If you cvsup to RELEASE you will downgrade and end up with what you started with when you installed from CD or whatever was available when the RELEASE cd was created for whatever system your getting. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rebooting into single user mode on a remote server
--- Ahmad Arafat Abdullah [EMAIL PROTECTED] wrote: - Original Message - From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: Daniel Gerzo [EMAIL PROTECTED] Subject: Re: rebooting into single user mode on a remote server Date: Sun, 17 Sep 2006 23:49:34 +0200 Daniel Gerzo wrote: Hello pobox, Saturday, September 16, 2006, 8:47:04 PM, you wrote: Hello, could somebody help me to understand the best way to enter into a single user mode on a remote server. I need it for the moment, during rebuilding world, when I have to reboot into single user mode before 'mergemaster -p'. I don't want to persuade you to something that is not officially supported, but I have never booted into single user mode while upgrading my FreeBSD boxes and I have never experienced any problems because of this. Just try to skip the reboot step and go ahead. It works(tm) for me this way. If you are paranoid, try to stop all running services except the ssh deamon. Phew... I hear this again and again. Only I am not sure I have the level of boldness to do this on a production machine. Isn't the following sequence of steps similar - 'shutdown -r now' (reboots in multi-user mode), and then immediately 'shutdown now' (drops to single user mode)? Iv. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] dudes, I never tried it, and not dare to try it.. because it's a remote server and single mode maybe ( I'm not sure dude ) cut off all network connections from inside and outside.. anyway for remote servers, i'm prefer make installwold in normal mode.. it's safer TQ the best possible only way is to use a serial console via a modem, which could drop out during the update, or a network accessable serial multiplexer. Those are expensive, modems are relatively cheap. Both require a serial console enabled kernel on the server. the only other way would be to have a cheap old box that can be connected to over the network with a null modem between it and the server. you would want this box to be UBER secured because it is a console to the system. There are ways of doing this so that a remote trigger is required to boot this system, but such methods require relays, a soldering iron, and some paranoia to complete. The gist of it is you will need a serial console on the server. Then you need a way to connect this serial line to your remote location. the easiest. cheapest, and least likely to fail is an old 486 or p1. p2 whatever you have lieing around that can be remoted connected to via ssh. if security is a concern you should use a key connection with no passwords. the user on that box doesn't have to be root, but he will need to be able to access the serial ports. then via a communications program available in ports take your pick you connect via a null modem to the server. you can then login and shutdown to single user mode on the server and upgrade to your hearts desires. -brian ___ 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 apply a patch set
--- Ahmad Arafat Abdullah [EMAIL PROTECTED] wrote: - Original Message - From: backyard [EMAIL PROTECTED] To: Ahmad Arafat Abdullah [EMAIL PROTECTED], [EMAIL PROTECTED] [EMAIL PROTECTED], Matthew Seaman [EMAIL PROTECTED] Subject: Re: how to apply a patch set Date: Sun, 17 Sep 2006 19:00:24 -0700 (PDT) --- Ahmad Arafat Abdullah [EMAIL PROTECTED] wrote: - Original Message - From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: Matthew Seaman [EMAIL PROTECTED] Subject: Re: how to apply a patch set Date: Mon, 18 Sep 2006 00:48:32 +0200 Matthew Seaman wrote: [EMAIL PROTECTED] wrote: Hello, I am trying to apply a patch set to FreeBSD 5.5 (this letter 'p' followed by a number, after the version in 'uname -a') - but somehow it did not work. I cvsup-ed the src using the standard 'stable-supfile' with '*default release=cvs tag=RELENG_5_5' - then I rebuild world. Now 'uname -a' reports 'FreeBSD 5.5 STABLE #0'. Before it was 'FreeBSD 5.5 RELEASE #0'. So instead of applying patch set I have moved to 'STABLE'. Could somebody tell me what have I done wrong? Actually - what is the difference between the 'pX' and the '#X' after the version? You've shifted your self onto the RELENG_5 code branch rather than the RELENG_5_5 branch. Yes... but how did it happen after I instructed the supfile to get 'RELENG_5_5'? Actually in the examples/cvsup I did not find any example how to do 'release'. Thank you for the other answers! Iv. i think I've read abt this long time ago.. but not pretty sure ( someone correct me if I'm wrong ).. u can try: *default release=cvs tag=RELENG_5_5_RELEASE anyway i never tried this! and i never encounter the prob u'va said since 4.x --- 6.1 ( and I'm normally/mostly using -pX than STABLE for my prod server ). Seems your method/tag tag=RELENG_5_5 is correct way to patch to -pX, i can't find any reason why your system patched into STABLE... could u please copy+paste here your stable-supfile config? TQ STABLE is the latest set of patches to the system. It will change the tag from RELEASE from the install to the STABLE set of patches versus the CURRENT set. STABLE is the major ones you want. CURRENT is all of them to date. If you cvsup to RELEASE you will downgrade and end up with what you started with when you installed from CD or whatever was available when the RELEASE cd was created for whatever system your getting. -brian ermm.. for me ( and as far as i know ) STABLE is a development patch and it will end up with the next RELEASE version.. such as 5.4-STABLE will be patch gradually until it became 5.5-RELEASE. Anyway 5.4-RELEASE-pX is a security fixes ( and possibly bugfix ) but it still remains as RELEASE and not migrating_into_the_next_version/release. some of the people ( like me ) just prefer to -pX rather than -STABLE. So far i'm not needed -CURRENT yet even RELEASE -pX is powerful enough and suits my needs for my prod servers.. are you running verision 6.1 or 5.5 on those servers? I'm fairly certain -pX only occurs on the latest production Release engines which to date is version 6.1. Release 5.x is no longer actively produced for production and the patches, bug fixes, and security updates are there to make servers built on RELENG_5 more secure, stable, etc. for this case ( back to the topics ), I think this guy do the right method for cvsup-ed to 5.5-RELEASE-pX but it end up with 5.5-STABLE. So i think we better help him and solve it since he maybe not need -STABLE like u said TQ p/s: Correct me if I'm wrong anyone! -- My point was I don't think you can get a RELEASE until you cvsup and STABLE becomes the next RELEASE. STABLE includes the security fixes and major bugfixes. CURRENT is all those plus new features... --- from: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html RELENG_5_5 The release branch for FreeBSD-5.5, used only for security advisories and other critical fixes. RELENG_5_5_0_RELEASE FreeBSD 5.5 RELENG_5 The line of development for FreeBSD-5.X, also known as FreeBSD 5-STABLE. A.7.2 Release Tags These tags refer to a specific point in time when a particular version of FreeBSD was released. The release engineering process is documented in more detail by the Release Engineering Information and Release Process documents. The src tree uses tag names that start with RELENG_ tags. The ports and doc trees use tags whose names begin with RELEASE tags. Finally, the www tree is not tagged with any special name for releases. - there doesn't seem to be a tag that gives you specific patchsets. And I would think a RELEASE like 5.X which
Re: Newbie Experience
--- Jeff Rollin [EMAIL PROTECTED] wrote: On 11/09/06, backyard [EMAIL PROTECTED] wrote: When I first installed FreeBSD, circa 2003, version 4.9, the two reasons I chose it over Redhat and Debian were the simplicity of the installation and good manual. The install process on REdhat and Debian was awkward, at least for me, and I could not make them work on my old compaq armada laptop. In contrast just following the manual and choosing default install parameters I got Freebsd working fast. During the installation I actually learned a lot about unix and Freebsd, the sort of details which are important to know anyway. It is hard to find the right balance between simplicity and functionality. It seems the balance in the Freebsd install is about right. anton I've only been around since FreeBSD 5.4 myself, and found during installs that sysinstall would get confused if you changed your mind and went backwards through the menus to reconfigure options. it seems like the one in 6.1 is a lot better, but maybe I just move back and forth less... That being said once it is installed it is a million times easier to maintain and upgrade then any Linux I've used. I had an old Digital 486 I had to install Redhat 7.3 thinking I could easily update to the latest kernel. I found I had to go through so many dependancies to do so I finally said whatever kernel was there was good enough. Talk about having to be a GNU guru to get things installed correctly without clobbering the old stuff and running into trouble... I'm unconvinced you could take FreeBSD 4 box and run the kernel from 6.1 on it without changing anything else. well cvsupping to Rel_5 and running a make buildworld make buildkernel make install kernel a reboot some mergemaster magic an installworld some more mergemaster magic and then cvsupping to Rel_6 and repeating is still lighttyears easier then watching the Linux kernel build stop, downloading the sources, configuring the dependancy properly, uninstalling the old, and reintalling the new. Especially when you will be tracing dependancies for weeks, unless your a pretty good programmer, which I am not, and know the dependancy chain of the core system. My point was the relative ease of upgrading, not the technical points of having missing object stubs. Of course you can't put a cummins deisel in a pinto without working on the frame first. Of late I was using Gentoo which I found to be FreeBSD like with its portage system, until recently when it seems they changed many system level interface stuff sometime after April 2006 and now I cannot seem to update it. The developers say you should not leave updating too long... True, if you are running FBSD 5.1 and need to update to 6.1, 5.3 is still there on the servers, but you do have to go through the steps of installing that intermediate version. well it was current as of april 8th when I made the tape. I went on vacation in May and got back on or about the 17th of May. Updating HAS NOT WORKED SINCE THEN. so if waiting 6 weeks is too long then so be it. I'm not going to constantly be emerging an update on a daily basis to stay current, especially since Openoffice seems to change its release tag everyother day on Gentoo and it puts a machine out of commission for 8-12 hours to build it. When: emerge --update --deep --newuse --emptytree world fails with PAM blocking, mozilla blocking, and now Xorg blocking as well as some other odds and ends thats when I say BSD is for me. to me it is incomprehensible why I cannot rebuild the system tree from scratch without software blocking the build. It was fun while it lasted, and it was nice to be away from winblows but in my experience linux is slower, a pain to configure, impossible to update, and a project started to emulate Unix. I'd much rather spend my time learning Unix, then fighting with the emulator. Even a full system rebuild has blocking packages that boggle my mind as they were compile from source originally... Stuff usually blocks if something about the way it's installed has changed in an incompatible way - X.org moving from monolithic to modular builds, for example. This doesn't seem to have anything to do with (binary) packages. well if I just delete the blockers and let them be fixed in the rebuild via them being dependancies it still fails. and use flags are basically useless in binary packages right? I don't like packages, I like to see that the port(age) will build on my machine, because I am a firm believer if you build it, it will run... Not to mention you can set the options you want. sysinstall isn't all that bad. It could be flashier, it could be graphical, it could be a lot of things. If it really bothers you that much you can make yourself a livecd system that brings up X and restores a basic install, or cvsups
Re: Newbie Experience
{expunged the old, typ}
I've only been around since FreeBSD 5.4
myself,
and
found during installs that sysinstall would
get
confused if you changed your mind and went
backwards
through the menus to reconfigure options. it
seems
like the one in 6.1 is a lot better, but maybe
I
just
move back and forth less...
That being said once it is installed it is a
million
times easier to maintain and upgrade then any
Linux
I've used. I had an old Digital 486 I had to
install
Redhat 7.3 thinking I could easily update to
the
latest kernel. I found I had to go through so
many
dependancies to do so I finally said whatever
kernel
was there was good enough. Talk about having
to be
a
GNU guru to get things installed correctly
without
clobbering the old stuff and running into
trouble...
I'm unconvinced you could take FreeBSD 4 box and
run
the kernel from 6.1 on
it without changing anything else.
well cvsupping to Rel_5 and running a make
buildworld
make buildkernel make install kernel a
reboot
some mergemaster magic an installworld some more
mergemaster magic and then cvsupping to Rel_6 and
repeating is still lighttyears easier then
watching
the Linux kernel build stop, downloading the
sources,
configuring the dependancy properly, uninstalling
the
old, and reintalling the new. Especially when you
will
be tracing dependancies for weeks, unless your a
pretty good programmer, which I am not, and know
the
dependancy chain of the core system. My point was
the
relative ease of upgrading, not the technical
points
of having missing object stubs. Of course you
can't
put a cummins deisel in a pinto without working on
the
frame first.
Shrug. I've had problems trying to recompile the
FreeBSD kernel too.
It happens, I will admit it. I find things like
enabling wpa_supplicant and forgeting device wlan is
what trips me up most, or things along those lines...
dependancies can be frustrating at best... And I have
had experiences where a patch had a few typos in the
commit and nothing works until it is recommitted
correctly. I'm not going to even try to say FreeBSD is
always sunshine and linux is farts. I still like the
fullscreen console on my linux console, vs the tiny
have utilized LCD on my FreeBSD console with my Dell
Inspiron 1100. Know there has to be a fix, but haven't
liked the answers I've read so far...
Of late I was using Gentoo which I found to be
FreeBSD
like with its portage system, until recently
when
it
seems they changed many system level interface
stuff
sometime after April 2006 and now I cannot
seem to
update it.
The developers say you should not leave updating
too
long... True, if you
are running FBSD 5.1 and need to update to 6.1,
5.3
is still there on the
servers, but you do have to go through the steps
of
installing that
intermediate version.
well it was current as of april 8th when I made
the
tape. I went on vacation in May and got back on or
about the 17th of May. Updating HAS NOT WORKED
SINCE
THEN. so if waiting 6 weeks is too long then so be
it.
6 weeks too long? 6 months, *maybe*.
yeah between that tape which was the last update I
recall doing (always TAPE things up before messing
with it, learned that the hard way too many
times) and me getting back home from Tortola to plug
in to the net and update portage and try to update. At
that point I was only updating, and PAM was Blocking.
I deleted it, the update failed at some point I got
sick turned off the box and without PAM could never
log back in. VERY FRUSTRATING, and I actually liked
Gentoo a whole lot. But updating the penguin has never
gone smooth for me in the long run...
I'm not going to constantly be emerging an update on
a
daily basis to stay current, especially since
Openoffice seems to change its release tag
everyother
day on Gentoo and it puts a machine out of
commission
for 8-12 hours to build it. When:
emerge --update --deep --newuse --emptytree world
fails with PAM blocking, mozilla blocking, and now
Xorg blocking as well as some other odds and ends
thats when I say BSD is for me. to me it is
incomprehensible why I cannot rebuild the system
tree
from scratch without software blocking the build.
It
was fun while it lasted, and it was nice to be
away
from winblows but in my experience linux is
slower, a
pain to configure, impossible to update, and a
project
started to emulate Unix. I'd much rather spend my
time
learning Unix, then fighting with the emulator.
That was my point, that BSD was rewritten from the
ground up to avoid ATT
patents. So whilst some might consider BSD real
unix, it's really only
emulating V7 with Berkeley extensions.
BSD was always trying to rewrite the original ATT
code, while being compatible with the
Re: Putting a command/script as a user's shell
--- Karol Kwiatkowski [EMAIL PROTECTED] wrote: Good day everyone, I'm trying to make it possible to restart (as in 'shutdown -r now') a FreeBSD based router from LAN network as easy as possible so it can be used by non-technical people. I'm sure some will ask why would I need that - it's an USB modem connecting to ADSL line that locks up sometimes and all my attempts to make it restart itself have failed. I came up with this idea: - add another user to the system, let it be 'restart' - add 'restart' to group operator - let 'restart' to login through SSH from LAN with a key (passwords forbidden) - put a restart command as it's shell (so it automagically restarts the router) Does that sound reasonably? Security is not an issue, it's secure enough for me. OK, now for technical question. I realise I cannot put arguments to the command in the shell area in passwd file, so I wrote a short script: $ cat /home/restart/restart.sh #!/bin/sh /sbin/shutdown -r now $ ls -l /home/restart/restart.sh -rwx-- 1 restart restart 33 Sep 11 15:24 put that as restart's user shell: # grep restart /etc/master.passwd restart:*:1017:1017::0:0:restart:/home/restart:/home/restart/restart.sh and tried locally but it's not working: # su - restart su: /home/restart/restart.sh: Permission denied I'm not sure where 'Permission denied' come from. Setup looks to be OK, here's what I get with /usr/bin/id as a shell: # su - restart uid=1017(restart) gid=1017(restart) groups=1017(restart), 5(operator) I'm sure I'm missing something here. Anyone have some pointers? Cheers, Karol -- Karol Kwiatkowski freebsd at orchid dot homeunix dot org OpenPGP: http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc make the shell script group executable and make it group operator maybe try making it owned by root. I think what is happening is it is running under the priveledges of restart not operator because operators groups cannot execute the command only the restart user can due to the priveledges. And when the restart.sh passes its group priveledges to the sript callout to shutdown it fails because shutdown can only run as operator. That would be my guess -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Experience
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Sep 11, 2006, at 12:15 PM, Jeff Rollin wrote: Discussions like these leave me lost for words... Perhaps, although it seems you recovered quickly. :-) Which is to say, apart from the occasional bug I really don't see what the problem is with sysinstall. I'm in that club myself. It takes a few times to get it down, but it is simple once you know the basic steps of getting FreeBSD on a box. The trick is of course understanding the basic steps which is where most don't take the time to research. I know I read through tha handbook a few times before I attempted my first go, and I know I messed up royally even still. But now its more frustrating to figure out what I want to do while the packages are downloading then anything else. Credits: It's highly functional. It can configure a lot of things about a FreeBSD system, either during or after the installation of the system. It's CLI/remote-serial-console friendly. Debits: It's oriented towards technical people. People who don't understand computers well in general, and the details of disk layouts in particular, tend to get hopelessly confused. Not only do they usually not know how to access the help inside sysinstall, many times the help text is not available, or is not comprehensible unless you have the already-mentioned technical background. I would have to concurr with this 100%. My first go at FreeBSD was a little rough do to this whole concept of two partitionings. I thought to myself now why would anyone want to do this. I wouldn't consider myself at the time a novice, but I wouldn't consider myself too bright either... Now it makes perfect sense to have one partition and multiple slices. It makes an fstab look a lot nicer. nothing more annoying then not having say a linux box boot because you selected the extended partitions number instead of the logical drive contained therein... and keeping track of a million partitions get old quick. Fortunately, the outstanding docs available for FreeBSD do a lot to walk people through the process, even novices. Unfortunately, people want to use computers without having to read the docs. Just ask your mom/grandparents/etc. :-) most people want to use everything without reading the manual. I think thats why there's labels on the toaster not to stick a fork in it, or a tag to not use a hair dryer in the shower... Personally I turn to the Cadillac shop manual when I want to tune up my eldo, it makes sense to me. I know software is the same way, but most people don't want to take any time figuring out what their doing; pardon my vulgarity but Taco Bell exists for a reason, man pages... To me it's the best thing this side of YaST for getting (certain areas of) system administration done. (Yeah, I know a lot of you probably hate YaST in particular or Linux in general... Why would you think that? I'd imagine that most of the people using FreeBSD end up having a Linux box or two around for one reason or another. I find it was for not reading the FreeBSD manuals... if people think FreeBSD is hard I cannot imagine what they think about Linux. Sure it has that flashy install program, well except Gentoo and maybe a few others, but upgrading the kernel can make setting up a FreeBSD box from scratch WITHOUT the manuals seem like a cake walk... I will admit to having a linux partition on my laptop, but only because I haven't taken the time to backup FreeBSD and give myself 15 more gigs... I will give Linux this, if I were building an embedded system I would probably go with Linux, but only because the obscure hardware sometimes in PC104s has vendor supported linux drivers. That and I understand how Linux boots better then FreeBSD, I'm hoping this will change soon; even have a Treo 650 lying around with X windows name all over it... might have to try OpenBSD for that one though... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Newbie Experience
--- Anton Shterenlikht [EMAIL PROTECTED] wrote: Needless to say, I was very disappointed. I feel that FreeBSD will never achieve broader acceptance (even with momentum building for alternative OS) among people with modest technical proficiency and fairly simple requirements (i.e., spreadsheets, word processing, presentations, email). FreeBSD has an awful out of the box experience. It's too bad, because I think FreeBSD is probably a better OS, but I'll never really know. Regards, too bad, you experienced that, the FreeBSD sysinstall is not that really hard, it may seem daunting at first because of its text mode but it is very straight forward, i guess you have to read the handbook over and over again to fully comprehend the things you missed why things like X is not working, it will also help if you will include the error messages as to why you can't run/install gnome or kde. imo you missed some dependencies that's why you're having a hard time. When I first installed FreeBSD, circa 2003, version 4.9, the two reasons I chose it over Redhat and Debian were the simplicity of the installation and good manual. The install process on REdhat and Debian was awkward, at least for me, and I could not make them work on my old compaq armada laptop. In contrast just following the manual and choosing default install parameters I got Freebsd working fast. During the installation I actually learned a lot about unix and Freebsd, the sort of details which are important to know anyway. It is hard to find the right balance between simplicity and functionality. It seems the balance in the Freebsd install is about right. anton I've only been around since FreeBSD 5.4 myself, and found during installs that sysinstall would get confused if you changed your mind and went backwards through the menus to reconfigure options. it seems like the one in 6.1 is a lot better, but maybe I just move back and forth less... That being said once it is installed it is a million times easier to maintain and upgrade then any Linux I've used. I had an old Digital 486 I had to install Redhat 7.3 thinking I could easily update to the latest kernel. I found I had to go through so many dependancies to do so I finally said whatever kernel was there was good enough. Talk about having to be a GNU guru to get things installed correctly without clobbering the old stuff and running into trouble... Of late I was using Gentoo which I found to be FreeBSD like with its portage system, until recently when it seems they changed many system level interface stuff sometime after April 2006 and now I cannot seem to update it. Even a full system rebuild has blocking packages that boggle my mind as they were compile from source originally... sysinstall isn't all that bad. It could be flashier, it could be graphical, it could be a lot of things. If it really bothers you that much you can make yourself a livecd system that brings up X and restores a basic install, or cvsups whatever system you want on your pc/sparc/whatever and builds it from source. that is the beauty of Unix. True Unix not an emulator like Linux. That and the fact you get an OS with a set of base software and a compiler out of the box. Linux is only the kernel, you have to make hundreds of independant software packages work together to get a system running. Each one with their own independant configuration files, and hundreds of man pages to read. Even the rc.d system is a separate package. now I'm sure things have progressed with Fedora Core where updating is nice and simple, but the shear amount of chaos that is Linux just drives me nutz. Sysinstall does take a few installs to get down pat, but once you do it can be setup almost in your sleep. You do need to get used to the differences of Unix vs most PC OSs whereby you need to in laymens term partition twice. A feature I love because it keeps fstab making sense. Like anything you can't expect to try something completely new without expecting to fall on your face a few times. I wouldn't just through on scuba gear and dive the Atlantic Ocean in search of the Titanic... I would expect to have to read, maybe take some classes (mess up FreeBSD bad and start over) and try in a pool instead of the ocean a few times (use non-mission critical machines to learn with) The unfortunate truth is Unix is not Microsoft Windows, well some might consider it unfortunate... Windows tells you what to do, what software you must use, what drivers you must use, where you must install things, what daemons listen to what ports and their is little you can do to change it. Unix is just a set of simple commands strung together in scripts and pipes that can do whatever you want it to do. X11 is not Unix it is a software package designed to allow netrocentric GUI applications to talk to a screen, keyboard and mouse. Its a monster in and of itself... Complete with its own documentation...
Re: Newbie Experience
--- Jerold McAllister [EMAIL PROTECTED] wrote: backyard writes: --- Chuck Swiger [EMAIL PROTECTED] wrote: On Sep 11, 2006, at 12:15 PM, Jeff Rollin wrote: Discussions like these leave me lost for words... Perhaps, although it seems you recovered quickly. :-) Which is to say, apart from the occasional bug I really don't see what the problem is with sysinstall. I'm in that club myself. It takes a few times to get it down, but it is simple once you know the basic steps of getting FreeBSD on a box. The trick is of some excised comprehensible unless you have the already-mentioned technical background. I would have to concurr with this 100%. My first go at FreeBSD was a little rough do to this whole concept of two partitionings. I thought to myself now why would anyone want to do this. I wouldn't consider myself at the time a novice, but I wouldn't consider myself too bright either... Now it makes perfect sense to have one partition and multiple slices. It makes an fstab look a lot nicer. Of course, I think you just said that backwards. I think by FreeBSD terminology you probably mean one slice and several partitions (a-h) in it... in the interest of not confusing a newbie in the future I would say yes I did. my biggest problem is mixing my own vernacular with what the rest of the world uses... At any rate having one slice for my Unix and partitioning that slice up with the filesystems I wish to populate is a good thing. After a while you even get used to what a-h is all about and to stay away from c unless you need to dd a mistaken gvinum configuration away... In retrospec this probably messes new folks up cause like myself they generally assume a partition is what we would call a slice... -brian jerry nothing more annoying then not having say a linux box boot because you selected the extended partitions number instead of the logical drive contained therein... and keeping track of a million partitions get old quick. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OpenOffice build crashes the compiler
--- Perry Hutchison [EMAIL PROTECTED] wrote: Anyone seen this and know how to get past it? Configuring out the failing component would be fine, if possible, since I really only need the word processor. Making: ../../../../unxfbsdi.pro/slo/SlideSorterView.obj g++-ooo -fmessage-length=0 -c -Os -fno-strict-aliasing -fvisibility=hidden -I. -I../../../../unxfbsdi.pro/inc/slsview -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/solver/680/unxfbsdi.pro/inc/offuh -I../inc -I../../inc -I../../../../inc/pch -I../../../../inc -I../../../../unx/inc -I../../../../unxfbsdi.pro/inc -I. -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/solver/680/unxfbsdi.pro/inc/stl -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/solver/680/unxfbsdi.pro/inc/external -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/solver/680/unxfbsdi.pro/inc -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/solenv/unxfbsdi/inc -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/solenv/inc -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/res -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/solver/680/unxfbsdi.pro/inc/stl -I/usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/solenv/inc/Xp31 -I/usr/local/diablo-jdk1.5.0/include -I/u! sr/local/diablo-jdk1.5.0/include/ In file included from /usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/sd/source/ui/slidesorter/view/SlideSorterView.cxx:54: ../../inc/DrawDocShell.hxx: In member function `void sd::DrawDocShell::SetSpecialProgress(SfxProgress*, Link*)': ../../inc/DrawDocShell.hxx:189: warning: declaration of 'pProgress' shadows a member of 'this' g++-ooo: Internal error: Killed: 9 (program cc1plus) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. dmake: Error code 1, while making '../../../../unxfbsdi.pro/slo/SlideSorterView.obj' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /usr/ports/editors/openoffice.org-2.0/work/OOD680_m1/sd/source/ui/slidesorter/view dmake: Error code 1, while making 'build_instsetoo_native' '---* *---' *** Error code 255 Stop in /usr/ports/editors/openoffice.org-2.0. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] http://lists.freebsd.org/pipermail/freebsd-ports/2005-March/021822.html is an old link but has a patch. http://archives.mandrivalinux.com/cooker/2003-10/msg02538.php sugests some missing symlinks might be the culprit. Please let me know is either of these resolve the isses, I'm looking to get OpenOffice built this weekend after I update my basic system... Both of these reference that Error 65280 some answers also suggest you might be running out of space in the build directory. You'll need at least 1.8G to build Openoffice (/usr/ports); I say at least because when I built it for Gentoo on my P4 it used up more like 5G and took 8-10 hours to build. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How do I give 2 parameters to programs in an unix enviroment?
--- Lasse Edlund [EMAIL PROTECTED] wrote: If I have two files foo and bar and try to run diff on them I write: $diff foo bar I can also write $cat foo | diff - bar But how do I give a program two (2) commands? not only to diff but to any program that wants double input... I wanna do $cat foo | cat bar | diff - - especially with echo commands that would be handy so I dont have to create files! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] diff foo bar is the the way a contruct like (cat foo; cat bar| diff - -) may work but I doubt it because they both are writing to the same STDOUT and so - - is more then likely invalid. (echo random junkola foo) (cat foo bar) or (echo random junkola foo) (cp foo bar) would be just as good. would echo the same thing to two files. I think what you want might be diff `cat foo` `cat bar` which is the the quote on the tilde key. check man eval if I'm using the right quote this will evaluate the command in the ` ` and pass its STDOUT as a parameter. For large files this might fail because of the limitation to the command line length, I'm not certain. the best thing might be look in /etc/rc for the last line which will be something like: echo `date` those are the quotes you want and this is the only way to do what I think you're asking. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Default Editor in profile
--- Huy Ton That [EMAIL PROTECTED] wrote: under my home directory for root under .profile I added the line: EDITOR=pico;export EDITOR where no such line existed for EDITOR before; this line exists in my personal account that I use and my default for external launched editors is now pico such that I can edit crontab stuff easily. However, when I ssh in and then su, I try to run crontab only to find it is still booting into 'vi' by default. Any ideas how I can get this loaded? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] yeah, I'm not sure what the switch is for su I think its -w check man, but you have to load your profile for root which is a switch to su. by default it uses the profile of the user running su. the switch loads the profile for the user your su'ing to. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Clevo D900K and 64 bit FreeBSD support???
I've been looking into replacing my current laptop/desktop with a Clevo D900K, AMD-64 machine. I'm just curious if anyone out there has any experience getting FreeBSD up and running on this machine and at what capacity (card reader, 8.1 sound card, WLAN+Bluetooth, Hardware RAID, etc.) I was going to go with the Nvidia Quadro graphics card and am curious on the status of 64bit native nvidia drivers. I know it wasn't/isn't supported as of yet. Also I was hoping to take an existing i386 system and move it to the 64bit system. Can I by properly specifying the environment rebuild an i386 system to 64bit? Or am I better off/ have too install a fresh 64bit system? I would imagine this could tick off a few ports like portupgrade that would make rebuilding tricky at best. I've linked to and included the machine spec for those savy enough to look at the general hardware and know it's level of support. thanks, -brian http://www.clevo.com.tw/products/D900K.asp link might make the following look a little nicer D900K Specification CPU #12290; AMD AthlonTM 64 X2 Processor 3800+/4200+/4600+ #12288; (2.00~2.40GHz, 1MB L2 cache, socket 939) #12290; AMD AthlonTM 64 X2 Processor 4400+/4800+ #12288; (2.20~2.40GHz, 2MB L2 cache, socket 939) #12290; AMD AthlonTM 64 Processor FX-53/FX-55/FX-57 #12288; (2.40~2.80GHz, 1MB L2 cache, socket 939) #12290; AMD AthlonTM 64 Processor 3000+/3200+/3400+/3500+/3800+ #12288; (1.80~2.40GHz, 512KB L2 cache, socket 939) #12290; AMD AthlonTM 64 Processor 3700+/4000+ #12288; (2.20~2.40GHz, 1MB L2 cache, socket 939) Core Logic #12290;VIA K8T890CE + VT8237R Display #12290;17.1 WXGA (1440x900) TFT / 17.1 WSXGA+ (1680x1050) / 17.1 WUXGA (1920x1200) TFT Memory #12290;Two 64-bit wide DDR data channels #12290;Two 200-pin SODIMM sockets, supporting DDR 400 #12290;Expandable Memory up to 2GB, based on 256/512/1024MB SODIMM Module Video Controller #12290;(Option) nVIDIA QuadroTM Fx 2500 #12288;High performance graphic chip #12290;512MB DDRIII Video RAM on board #12290;256-bit video memroy interface #12290;PCI-Express x16 #12290;Fully DirectX 9.0 support #12290;Modular Design #12290;OpenGL support #12290;(Option) nVIDIA GeForceTM Go #12288;7900 GTX High performance #12288;graphic chip #12290;256MB DDRIII Video RAM on board #12290;256-bit video memroy interface #12290;PCI-Express x16 #12290;Fully DirectX 9.0 support #12290;Modular Design #12290;H.264 encode support #12288; (HD-DVD/BD-DVD playback) #12290;(Option) nVIDIA GeForceTM Go 7900 #12288;GTX High performance graphic chip #12290;512MB DDRIII Video RAM on board #12290;256-bit video memroy interface #12290;PCI-Express x16 #12290;Fully DirectX 9.0 support #12290;Modular Design #12290;H.264 encode support #12288; (HD-DVD / BD-DVD playback) Storage #12290;One changeable Primary 2.5 HDD 9.5mm(H) #12290;Serial ATA HDD support #12290;Supporting Master mode IDE ATA-100/133 (Ultra DMA) #12290;One changeable Primary Bay for 12.7mm(H) DVD-ROM / Combo / DVD-Dual Driver #12290;(Option) One external USB 1.44MB Floppy Disk Drive #12290;(Option) One changeable Secondary 2.5 HDD 9.5mm(H) #12290;(Option) One changeable Secondary Bay for 12.7mm(H) DVD-ROM / Combo / DVD-Dual Driver Keyboard#12290;Full size keyboard, with Numeric Pad, Multi-Language support #12290;Built-in Touchpad with scrolling function Sound System#12290;AC'97 2.2 Compliant Interface #12290;3D stereo enhanced sound system #12290;Virtual 8-channel audio output #12290;Sound-Blaster PROTM compatible #12290;S/PDIF Digital output #12290;SRS (Sound Retrieval System® ) / WOW 3D sound technology #12290;1x Built-in Microphone #12290;4x Built-in Speakers #12290;1x Built-in Sub woofer #12290;1x Built-in Audio DJ Console for music CD (MP3 format compatible) I/O Ports #12290;4x USB 2.0 ports #12290;2x Mini IEEE1394a ports #12290;1x S-Video jack for TV output (HDTV support) #12290;1x Serial port #12290;1x Parallel port (LPT1), supporting ECP/EPP #12290;1x Infrared Transfer port #12290;1x DVI port #12290;1x PS/2 port #12290;1x Headphone jack #12290;1x Microphone jack #12290;1x S/PDIF output jack #12290;1x Line-in jack for Audio input #12290;1x RJ-45 port for LAN #12290;1x RJ-11 port for Modem #12290;1x DC-In jack #12290;1x CATV input jack (optional function with TV-Tuner module) #12290;1x S-Video jack for Video input (optional function with TV-Tuner module) Slot#12290;Built-in 10-in-1 Card Reader (MS/MS Pro/SD/MMC/CF/SM/MicroDrive/MS DUO/Mini SD/RSMMC) #12290;1x Type II PCMCIA socket Communication #12290;Infrared Transfer : 115.2Kbps SIR/4Mbps FIR, IrDA 1.1 compliant #12290;10/100/1000BASE-T Fast Ethernet onboard #12290;Integrated V.90/56K Azalia Modem (V.92 compliant) #12290;(Option) 802.11b/g MiniPCI Wireless LAN Module #12290;(Option) BluetoothTM Class II V2.0 Module, combo with 802.11b/g Wireless LAN Module #12290;(Factory option) 1.3M-pixel Video Camera module Power #12290;Full Range 220W AC adapter - AC input 100~240V, 47~63Hz,
Re: solaris
--- White Hat [EMAIL PROTECTED] wrote: --- Freminlins [EMAIL PROTECTED] wrote: On 06/09/06, White Hat [EMAIL PROTECTED] wrote: I have tried Open Office. No matter what anyone says, it is just not as full featured as Word 2003. It is not even close. yeah cause most users want to use an MDI instead of a PDF (inside joke, anyone in the telecomm industry who does work for cell carriers or one in particular might get) True, but also compare the cost. Not even close... Immaterial. the singularly most important feature is suitability to task. If it is free and it does not work, what good is it? ...but most users only care about writing letters and resumes; openoffice does this fine. Even spits out a PDF for me to email away with a coversheet. And then there is always SunOffice... Since spending money seems to be the solution for all of the problems I have with windows and the lack of integrated features it contains. Maybe I should go out and get a Quad AMDx2 motherboard and fill it with FX series chips to handle XP being slower then Warp, but alas windows still has no real support for 64-bit chips. Oh and it sure would be a pain to have to reinstall EVERYTHING because the PNP windows machine won't let me switch a motherboard on it. He/she does not want to read tons of manuals and spend hours in a frustrating attempt to get it to run. if I buy a chain saw I take the time to read the manufacturers suggested method to adjust the chain tension. Maybe I'm not the normal person, but stuff never works out of the box, and not taking the time to read the manual is the users fault. and unlike windows products the online help for FreeBSD and GNU in general is incredible. Windows expects the use is an idiot and makes no attempt to explain how the command line switches work, or what registry keys do, or what the blue-screen-o-death errors refer to. This is where you are completely wrong. I work for an ISP. I'm not responsible for tech support but I keep my ear to the ground. A VERY large number of callers have problems configuring Outlook Express, for example. No matter what the polls say, the experience is often very different. They may not read the manuals (because they are no longer supplied), they just ring a call centre instead. Yes, the lack of documentation is a shame. Usually it can be obtained for an additonal cost which I suppose is better than nothing. The same lack of documentation plagues every facet of software today. Of course, it has been a boon for the after market book manual publishers. BTW, you have failed to document so called help line assistants who are nothing more than company mouth pieces who have at most a superficial knowledge of the product that they are suppose to be assistant a customer with. I had the experience of talking with a customer support moron who tried to sell me a new router while I attempted to explain the router was fine, but the installation CD was defective. I eventually just sent it back for a replacement. Usually these individuals are barely equipped to handle the job they are given. which is why If i spend 300 on a license for windows and 600 for a license for office I should get the manual. Online help is useless in the windows world. Nothing is more frustrating then having an error code thrown in windows and the help system not having any clue on what the error code is, but plenty of information about how simple setting this thing up is. Even more frustrating is the 15 chapters on how you click the mouse and use the start menu. However, you have made my point. If a user cannot decipher how to configure a simple thing like Outlook Express, and there are programs available that will do it for them, then how are they suppose to be capable of handling a CLI OS like FreeBSD? It boggles the mind -- at least mine. Worse, the configuration of OE is handled by a wizard. It is truly sad when a user cannot configure something when it is simplified down to that level. I never thought the average user should have to set it all up. I'm working towards deploying the system amongst friends already configured becuase once it is it don't break, is easy to use, and lightyears faster. Make a PKzip of your windows install and try to copy it to another machine. It doesn't happen, but if someone took the time to setup FreeBSD they could copy it on a million machines, and the users would never be the wiser. Why can't I just zip up my windows machine and keep a tape ready to go? why should it be an ordeal to get it configured again. This is basically what Apple did with Mac, and if they would just release OS X on PC I wonder how fast the windows market would shrink. As projects like PCBSD and DesktopBSD advance it will be easier and easier to convince folks windows is NOT the only kid on the block. The average user does not care about configuring
Re: solaris
--- White Hat [EMAIL PROTECTED] wrote: Yes, the lack of documentation is a shame. In Windows, yes. In FreeBSD I can't see a lack. You are kidding right. I can find vastly more documentation available for a win32 machine than for FBSD. In fact, the lact of documentation is one of the reasons that support groups like this evolved. To my great dismay, I am forced to search for and then download documentation via the web. Even then, that is often dated. Not anyones fault, it is just the way it goes. The same lack of documentation plagues every facet of software today. No it doesn't. FreeBSD is well documented. It is above average, I will agree. However, if it were really perfect then this forum would not exist. No, it is forums like this that help improve the documentation in general. And hopefully give the basic outline when things are solved to allow documentation to be written. Just like Microsofts Forum for their MCSE people. However, you have made my point. No I haven't. I have contradicted your point. You said A very large majority of users simply want to use their PCs for email, occasional word processing and possible game playing. I am saying that using XP as you suggested is not as easy as you suggest for a very large number of people. If that were true, MS would not rule 90+ percent of the PCs in use today. if they didn't make OEM pc manufacturers sign contracts REQUIRING they distribute MS-DOS/Windows or loose their OEM status to deal microsoft products this number would likey be a lot smaller. Probably with Warp or Linux as its major competitor. Why do you think users in third rate countries pirate MS when they could get FBSD for free? Doom3? Maybe just because they can make money doing it, that is the usual motivation for theifs. That and a license in a country like Argentina (per our Argentinian friends in the forum) costs on the order of $1000 US dollars. I would not want to insult anyone; however, if you cannot install an MS operating system then perhaps you should consider another hobby. Even my wife's sister can handle that project, and that is a woman who considers a can opener a high tech device. Installing is simple, making a restorable backup with included utilities of the whole system is next to impossible. Even with Sysinstall... Nothing more fun then having a Microsoft unintended installation fail, only to reboot and restart and having it magically work fine. Please do me one favor, do not CC me. I am continually getting two copies of these. I subscribe to the list. I don't send you duplicate copies and therefore would appreciate the same cutesy. Perhaps my address was already inserted by a previous poster. If so, please do remove it. Thank You! your welcome I think, I did delete the CC... -- White Hat [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: solaris
--- Giorgos Keramidas [EMAIL PROTECTED]
wrote:
On 2006-09-05 22:50, Bill-Schoolcraft
[EMAIL PROTECTED] wrote:
If just a relatively small handful of dedicated
FreeBSD coders can
produce an OS that will install on damm near
ANYTHING I always found
it troubling that SUN Microsystems, with all it's
resources, could
not, at the least, make their x86 OS (think
Solaris-10) install with
support, for lets say, what FreeBSD had for 4.2?
I mean, all the drivers are available, wouldn't
one think that they
could at least support what FreeBSD supports in
terms of number of
devices?
I don't speak officially *for* FreeBSD, but let's be
a bit realistic
shall we? There are both good and bad points for
both FreeBSD and
Solaris. I'm sure someone can find hardware on
which FreeBSD can not
be installed at all. The same can be said for
Solaris. In the end,
it is all a matter of what hardware you have and
what your particular
application requires :-)
Having said that, I am more comfortable with the
FreeBSD-way of doing
most things, so when I have the choise and *both*
systems can be used,
I usually pick FreeBSD just because it is the one I
know best.
I think to be fair, SUN is mostly concerned with
making an OS for THEIR hardware and systems, and it is
nice of them to release an x86 version for free.
FreeBSD.org is only concerned with releasing an OS and
since they don't develop hardware they must support
more stuff because they have more hackers at their
disposal making obscure equipment work. And if it
didn't work the relatively small group of users would
shrink even more, or run Linux; {shudders.}
SUN sells to the military and those with deep pockets
who can afford their equipment, FreeBSD is just trying
to keep the spirit of BSD alive and well. It makes
sense that SUN will only use a few configurations of
PCs that are likely to be found in a military
contractor, or enterprise corporations arsenal;
especially on a system (V10) they release without
making money. Its unfortunate but that is life; I'm
sure in their minds if you can get it to run on a PC
they hope you will buy a Sparc of Sunfire, or whatever
line their up too now. It's advertising.
I think the important thing to remember in all this is
every system using one version of UNIX over another is
one more machine not running NT. And since NT is
single handedly stealing code, and destroying
internationally set standards I think the more UNIX
the merrier. Even if you're running a Mac... I find
the most important thing is trying to get people to
realize a computer isn't ment to tell you what you can
or cannot do, an Administrator should be able to kill
any running process on a system, you should be able to
choose what software is installed on your computer,
your web browser or PNP system shouldn't allow Viruses
or software in general to be installed on your machine
without your knowledge or consent, and most
importantly you should be able to take your hard drive
out of your machine and put it in another one and keep
on going.
Solaris is cool if it will run, FreeBSD will run if
Solaris won't; lets band together and destroy
Micrsoft... :)
-brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: solaris
--- Giorgos Keramidas [EMAIL PROTECTED] wrote: On 2006-09-04 15:52, backyard [EMAIL PROTECTED] wrote: I would recommend the second drive option. Me too. Not for the same reasons though. I have attempted installing Solaris 10 on multiple computers and all if ever seems to do is corrupt the drive on me. Once I got it to boot up and go into their version of X windows. After installing the Bonus pack with KDE and such never turned on again. Very frustrating. good luck, I've given up until I have a Sun Box to play with. I have installed Solaris 10 on *dozens* of systems at work. Very few of them were real Sun hardware and there has been exactly *one* case where something went wrong. It turns out this case was *my* fault. The only case when Solaris can be a pain to install is when you try it out on a system with hardware that is not supported by the drivers shipped with Solaris. Even in those cases, some times just adding one of the supported NICs, or a VGA, or booting from ATA disks and using SATA disks only for extra storage, can really work wonders... Solaris 10 is a wonderful system, it works flawlessly for various tasks that I use it at work (I prefer FreeBSD for my home systems), and the people who answer questions on comp.unix.solaris are knowledgeable, (usually) kind, and cool. So, please, don't be so hasty in accusing Solaris for problems you have had until now ;-) don't get me wrong I don't doubt it is a great system to use, which is why I kept on trying to get it installed on many different machines; from laptops to desktops, to servers, and my commodore... and I will admit I installed without really looking at the hardware compatability list... That being said ususally the boot loader will not load Solaris for me. The funny thing is when I had it on a machine with windows it would boot windows, just not Solaris. That or it would appear as thought the kernel became corrupt and would just lock out at the loader prompt. The one time I got it running it seemed very complete and working well, just wish I didn't try to Bonus Pack At any rate I have no luck with the system for whatever reason, and I've never installed it on anything but fairly generically configured systems with mundane basic hardware I would have to assume would work on a production OS. It just doesn't like me, so I stick with FreeBSD, and want to look into some of the other BSD variants. Even Linux is getting tiresome to me... nothing more frustrating then having a good TAPE and not being able to upgrade anything in my Gentoo system since April of 2006 for whatever reason. And really don't understand why a full system rebuild has a few packages blocking a complete rebuild. I mean I obviously got them installed one by one before. That just doesn't make sense unless my use flags are overly tweaked... Anyway I ment good luck without sarcasm at all. I just suggested a second drive because I PERSONALLY have never had any luck with Solaris, and felt it should be noted to someone who might otherwise not be as familiar with its setup and configuration as a person such as yourself with great luck using the system. I hope everything does go well because I know its a great system. Besides if I NEED a Tadpole dual Sparc laptop to run Solaris, then thats a sacrifice I will just have to make... 8^) -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Device Drivers and Kernel Modules
--- Lowell Gilbert [EMAIL PROTECTED] wrote: David Wassman [EMAIL PROTECTED] writes: I am trying to figure out which would be best, to load all the device drivers through compiling them into the kernel or to load them at boot through loader.conf. I would think that loader.conf would be more convenient as changing hardware wuld not require a rebuild of the kernel. Is there a draw back to loading devices this way other than a longer boot up time (which should not be an issue as the system is 24-7)? There is little difference for your purposes. I have also heard that loading modules through the loader.conf saves on RAM performance as the module in question is not loaded into memory until it is used as opposed to being loaded with the kernel. If this makes no sense, i appologize. I remember reading it somewhere on a mailing list several years ago and can't find the reference anymore. From memory it stated modules such as cd9660 could be loaded through entering CD9660_load=YES in loader.confand that it would not be used in memory until a cd was mounted. I am assuming this is true (if it is) for other modules as well. It isn't true at all. Loading a module really does load it into memory. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] In general if it is hot pluggable modules are the best with the appropriate configurations in the daemons that track hardware changes. If it won't come out during the system running then in the kernel is the best. Unless your running an old system recompiling a kernel is 15 minutes of time away. And since its a server you likely will not be constantly updating your base, but even still a new world and kernel should only be an hour tops away, unless you using older equipment. Generally Cardbus/PCMCIA cards you would want modules so you can save a second or two booting and a few k of RAM have them load and unload as needed, Gvinum is recommended as a module so you can restart it, USB dongles (bluetooth and such) and what not (although drives I generally put in the kernel) Personally I put all the hardware I plan on using in the kernel because it can make life slightly easier. That and unless your doing embedded development or running a 486 you will probably have enough RAM for the additional overhead. In a server scenario your going to be pluggin in hard drives which is and should be built it. I doubt your going to have a sound card, and probably not even DRI modules to contend to. You should have enough RAM where having everything in the kernel isn't going to matter much. This DOES NOT mean use every option when building, but if your server has the hardware, enable it. I believe using modules uses slightly more RAM because the kernel needs the hooks to the module and then the module on top of the hooks, versus just having the code in the kernel, but this is my understanding of things. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sshd login stalling
--- Noah [EMAIL PROTECTED] wrote: Okay I cant seem to figure out why sshd logins are stalling. I see that I am coming from an IP address that does not have Reverse mapping. So I added the lines below to /usr/local/etc/ssh/sshd_config and /etc/ssh is sym linked to /usr/local/etc/ssh --- snip --- lrwxr-xr-x 1 root wheel18 Sep 4 23:01 ssh - /usr/local/etc/ssh UseDNS no VerifyReverseMapping no snip --- cheers, Noah just a thought but if /etc/ssh is linked to /usr/local/etc/ssh wouldn't that just cause troubles from the ghetco? My understanding is /usr/local/etc is for local specific configurations so that a site specific configuration in /etc can be loaded and appended by the stuff in /usr/local/etc. Wouldn't symlinking one to the other force the same config files to be loaded twice??? And if so wouldn't that possibly confuse the daemon? Maybe I'm not entirely clear on how all that works myself. but my understanding is /etc is read first and then appended by /usr/local/etc. Although I can see how this would allow NFS to be used on diskless clients using generic /etc while allowing system specific configurations to be stored elsewhere and linked in as needed. I am just under the impression that /usr/local/etc is not for this purpose. of course I'm not the brightest tool in the shed... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sshd login stalling
--- Noah [EMAIL PROTECTED] wrote: backyard wrote: --- Noah [EMAIL PROTECTED] wrote: Okay I cant seem to figure out why sshd logins are stalling. I see that I am coming from an IP address that does not have Reverse mapping. So I added the lines below to /usr/local/etc/ssh/sshd_config and /etc/ssh is sym linked to /usr/local/etc/ssh --- snip --- lrwxr-xr-x 1 root wheel18 Sep 4 23:01 ssh - /usr/local/etc/ssh UseDNS no VerifyReverseMapping no snip --- cheers, Noah just a thought but if /etc/ssh is linked to /usr/local/etc/ssh wouldn't that just cause troubles from the ghetco? My understanding is /usr/local/etc is for local specific configurations so that a site specific configuration in /etc can be loaded and appended by the stuff in /usr/local/etc. Wouldn't symlinking one to the other force the same config files to be loaded twice??? And if so wouldn't that possibly confuse the daemon? Maybe I'm not entirely clear on how all that works myself. but my understanding is /etc is read first and then appended by /usr/local/etc. Although I can see how this would allow NFS to be used on diskless clients using generic /etc while allowing system specific configurations to be stored elsewhere and linked in as needed. I am just under the impression that /usr/local/etc is not for this purpose. of course I'm not the brightest tool in the shed... Well currently if I am coming from an IP address the has reverse mapping then things work fine there is no stalling whatsoever. When I removed the sym link between /etc/ssh and /usr/local/etc/ssh things work fine now. these is still stalling experienced when coming from an machine with a non-reverse mapped IP. other clues? cheers, Noah do you have a firewall setup or any other packet filtering going on on the box? Is this problem only with sshd or do all daemons have trouble with a host that doesn't do reverse-lookups? Perhaps the IP stack is just blocking the packets coming in from non-fully qualified hosts. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: solaris
--- Bill-S [EMAIL PROTECTED] wrote: At Mon, 4 Sep 2006 it looks like Chad Leigh -- Shire.Net LLC composed: On Sep 4, 2006, at 8:57 AM, dick hoogendijk wrote: On 03 Sep Chad Leigh -- Shire.Net LLC wrote: I am not sure about installing Solaris into an existing partition. I remember one of the FBSD's (a RC, but still) destroying my partition table. That's the reason I ask. I know that I don't have to use the main option (that's for the whole disk). But if there are no problems know of with the sol installer, than I'm a little less worried. I have no space to backup my XP and FBSD disk parts (at the moment). btw there is a Solaris X86 mail list at http://groups.yahoo.com/ group/solarisx86/ They might be better able to help out in determining the danger of installing in your situation. A second drive of course would somewhat give some relief for this install. I have, one a few of my boxes here, a BIOS enabled F8 key for selecting which disk to boot off of. AMI I believe is the BIOS type. -- I would recommend the second drive option. I have attempted installing Solaris 10 on multiple computers and all if ever seems to do is corrupt the drive on me. Once I got it to boot up and go into their version of X windows. After installing the Bonus pack with KDE and such never turned on again. Very frustrating. good luck, I've given up until I have a Sun Box to play with. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A question about programming RS-232
--- stan [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 11:26:04PM +0600, ?? ? wrote: Hello. I have a question I can't deal myself. And nobody can help me in resolving my problem. Problem: I have a hand-made device, I want to control from FreeBSD 6.1 (I am porting this application from Windows equivalent). But I don't know, in what device /dev/ I should write to get reults. I tryed to write bytes into /dev/ttyd0, /dev/cuad0, but got nothing. :( Start off by using minicom (or cu) to talk to the device. By doing this you can sort through baud rate/parity,hardware issues. Once you have that working, then move on to code. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] does your handmade device use RS-232? If its PIC or some such microcontroller based they claim to be RS-232 compliant but they do not always use +12V and -12V levels. MAX-232 chips can correct this. I assume if it worked in windows for you this might not the case, but you never know. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: Re: A question about programming RS-232
--- stan [EMAIL PROTECTED] wrote: Date: Sun, 3 Sep 2006 16:49:51 -0400 From: stan [EMAIL PROTECTED] To: backyard [EMAIL PROTECTED] Subject: Re: A question about programming RS-232 On Sun, Sep 03, 2006 at 01:39:00PM -0700, backyard wrote: --- stan [EMAIL PROTECTED] wrote: On Sun, Sep 03, 2006 at 11:26:04PM +0600, ?? ? wrote: Hello. I have a question I can't deal myself. And nobody can help me in resolving my problem. Problem: I have a hand-made device, I want to control from FreeBSD 6.1 (I am porting this application from Windows equivalent). But I don't know, in what device /dev/ I should write to get reults. I tryed to write bytes into /dev/ttyd0, /dev/cuad0, but got nothing. :( Start off by using minicom (or cu) to talk to the device. By doing this you can sort through baud rate/parity,hardware issues. Once you have that working, then move on to code. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] does your handmade device use RS-232? If its PIC or some such microcontroller based they claim to be RS-232 compliant but they do not always use +12V and -12V levels. MAX-232 chips can correct this. I assume if it worked in windows for you this might not the case, but you never know. I'm not the orignal poster on this. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) oops must have clicked a little too quick on this one -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is the new version going to be easier to get working?
--- David Kelly [EMAIL PROTECTED] wrote: Having 21 computers here I figured I would finally be rid of MSwindows, and have a complete LAN system that was more reliable. Why would you want to make things reliable? With Windows your career is secure knowing you will have to be kept around to keep them running. Microsoft cleverly backs a certification program to make sure its graduates never recommend anything other than what they have been trained. Not-MSCE certified thought; use OS/2 Microsoft's copy was corrupted after the portsnap Seven computers I have tried with all three BSDs and not one of them managed to produce a working network connection. did you plug them in? if these computers are HP's (Kayaks) with a scsi controller with a ethernet port on the controller then you might be sol out of the gate. FreeBSD Rel_5 never supported them for me Rel_6 does. I know pcBSD uses rel_6 I know desktopbsd use rel_5. Although outside these obscure cases I have not found a modern PC with a card FreeBSD didn't support when I booted it up. it seems like most things I find are MII bus based. The only thing I achieved was that now I can almost visualise every screen from the installations. Start by forgetting about the installation screens. They are only there to get the most basic things running well enough to get the system installed on disk(s). After one is running from the installed image one almost never returns to sysinstall. ifconfig(8) is probably the most important tool, from command line, that you need to diagnose network configuration and ultimately configure the connection. ping(8) is equally useful. If you have a DHCP server the machine is to use then as root where fxp0 is my NIC: # dhclient fxp0 If that works then /etc/rc.conf needs this line: ifconfig_fxp0=DHCP If your machine's address is static then this sets 192.168.10.12 on a /24 net: ifconfig_fxp0=inet 192.168.10.12/24 If you have run sysconfig multiple times then you likely have conflicting replications in /etc/rc.conf (only the last reference applies). Manually edit and reconcile the differences. I am baffled by how anyone is able to get a bsd networked system working. I guess I just have to stick with a windowsOS. someone must have; you're on the internet talking to us. its too bad you can only use NetBIOS/Netbuie(gave up trying to spell that)/SMB on that there windows network. I mean who would have ever thought of coming up with a TCP/IP reference specification... OK, no skin off my nose. Your problem solving skills are terrible. When (supposedly?) looking for help you do nothing but complain without saying anything specific about what wasn't working or the hardware involved. I highly recommend Microsoft products to people such as yourself. MCSE comment(sort of):because microsoft is so much stabler, and network friendly, with full POSIX compliance..., an ActiveViri component integrated into their full international standards compliant Web Browser... I've generally had more trouble setting up windows networks then anything BSD/GNU. Nothing more fun then having a 5 year old NIC that is supported in everything but Windows 2000. Makes connecting to the internet to download the driver a lot of fun. *BSD can be intimidating to some because you have full control, which can be good and very bad at times. some people like to drive their pretty lamborginis that their daddies bought em. some like to tweak a frame and engine with all the simple tools they have in their garage so they can take that poor kids pink slip. of course some like to be told what to do, and that they must install this browser they do not use or want, a java system that violates US Patent Law, and if they tweak the install scripts to stop this; ...Windows Has detected the configuration files have been modified... -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. some people just want an excuse to stick with windows; I'm coo-coo for coco puffs myself. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI lock in the last halt process
--- bsd [EMAIL PROTECTED] wrote: Hello, I have configured with a 6.1 RELEASE FreeBSD. When I am trying to shut down the computer - I reach the prompt - all processes seems to halt correctly - then the server seems to be stucked with the ACPI process indefinitely ?? First of all I don't know what ACPI is related to ? Second how could I avoid that problem in the future ? --- Here are the info related to acpi on my dmesg log : acpi_alloc_wakeup_handler: can't alloc wake memory acpi0: A M I OEMRSDT on motherboard acpi0: Power Button (fixed) acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 acpi_button0: Power Button on acpi0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 Thanks. «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ Gregober --- PGP ID -- 0x1BA3C2FD bsd @at@ todoo.biz «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ P Please consider your environmental responsibility before printing this e-mail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] what kind of computer is this? Do you have the latest BIOS installed on the computer in question? What BIOS version are you using? Did the machine do this on other releases or is this the first FreeBSD it has seen? ACPI is the most current flashier version of APM with some PNP thrown in; in laymens terms... It configures devices, provides power management, and allows the computer to setup hardware so specific versions of windows can or cannot use certain resources on the machine. Sometimes this does cause issues with the non-windows users because devices are left unconfigured or features disabled. Sometimes this leaves the hardcore users rewriting their ACPI to include support for FreeBSD natively or fix the errors that came with the ACPI from the OEM. shutdown puts in a system call to ACPI to shutoff the computer. That is why it matters. It seems like your system should shutdown properly due to the power button fixed line above. At least it not being able to properly shutdown is a known issue with the machine. Does the computer hard lock or do you mean you get stuck at a # prompt but no powerdown? shutdown now will bring you to single user mode shutdown -p now should (only in linux does it not for me...)shutdown the machine. to avoid this problem in the future you should fill in some of these blanks. Describe what: When I am trying to shut down the computer - I reach the prompt - all processes seems to halt correctly - then the server seems to be stucked with the ACPI process indefinitely ?? means exactly. I know its tricky to get verbatium what is going on, but when does it die? I had a dell with this problem, had to update the bios and turn on acpi for it to work right, would only halt the machine for me (shutdown -h now [turns off pc in linux... sorry tux is a new enemy...]) also a uname -a may be a nice thing to include. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP detection
--- Jordi Carrillo [EMAIL PROTECTED] wrote: 2006/8/31, Skylar Thompson [EMAIL PROTECTED]: Michal Mertl wrote: No! Kernel threads (e.g. handling interrupts) aren't that much different to normal processes. Logical CPUs on a single HTT capable CPU share most of the CPU logic, especially all the external stuff (handling interrupts). Scheduling handling of interrupts on the secondary/logical core wouldn't probably help performance at all (if that is at all possible). Could you clarify note 20031022 in /usr/src/UPDATING? It states that HTT CPUs are used for interrupts if they are detected, even if they aren't used by regular processes. Was this something that just showed up in pre-6.x releases? -- -- Skylar Thompson ([EMAIL PROTECTED]) -- http://www.cs.earlham.edu/~skylar/ Another question that's wondering me is why FreeBSD with the SMP kernel the gnome system monitor (Applications-System Tools-System Monitor) only shows one CPU when Linux with a SMP kernel shows two CPUs -- http://jordilin.wordpress.com I'm assuming you talking about an HT SMP scenario... Linux is running the second core, but *BSD will not unless you tell it too. I'll check with my dually once I get home but I'm fairly certain even if your running an SMP kernel if the other CPU isn't used, it isn't going to tell you what processes are running on it, because nothing is scheduled to run on it. Linux doesn't care about the possible exploits and so by default runs both HT cores. Look at it like this I have two hands, I could put two P99C-ASs in them, but if only one has a magazine in it why and I going to claim I got two pieces??? Basically by not setting the ...hyperthreading_allowed... variable you have removed the magazine from one of your cores... But I will check because I seem to recall there being some kind of issue like this with my 5.4 box that I just kind of shrugged off at the time. I thought it was with KDE not gnome though... It should show both or all your cores and what is running. But it can't show you what is running on a CPU the kernel has disavowed. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP detection
--- Skylar Thompson [EMAIL PROTECTED] wrote: Jordi Carrillo wrote: 2006/8/30, backyard [EMAIL PROTECTED]: --- Jordi Carrillo [EMAIL PROTECTED] wrote: I've read that SMP should be disabled for performance issues (I did not know that before installing freebsd). I have a P4 3GHz with hyperthreading technology. I have the SMP-GENERIC kernel and it only launches one cpu. So, I've decided to disable SMP from BIOS. Is that ok?, knowing that I have a Smp enabled kernel? or should I install one without smp? If so, is there a way to install one already precompiled? Thanks in advance -- http://jordilin.wordpress.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] if the system runs with one cpu now and you don't enable smp with HT with the sysctl variable then you should be ok. If your not doing SMP then recompiling the kernel for single processor mode will make things run a little quicker because the SMP code won't come into play. with HT disabling in FreeBSD is more for the security issues about a potential exploit whereby one process in one pipe can access the priveledged information of a process in another pipe because the two cores share one processor cache and thus one cache table. To my knowledge this hasn't been exploited yet. If you just install the generic kernel you it should be only the uniprocessor one. I would just do a: cd /usr/src make buildworld make KERNCONF=GENERIC buildkernel make KERNCONF=GENERIC installkernel as opposed to a binary version assuming you haven't updated yet you won't have to install world but I believe it must have the build in the source tree to build a kernel. On your P4 though the difference between SMP and uniproc may not be worth the trouble because I don't think much of a gain would be made. on a P1 a much different story... if you aren't concerned with bad users or hackers hitting the box I would just enable HT with the sysctl variable. This will not make things run slower at all, just (in theory) less secure, which is why the veriable was created in the first place as I recall. If you are concerned I would wait until you update your system and then just build a GENERIC/CUSTOM kernel without the SMP option set. -brian I will disable smp from bios. If I have a smp kernel, I suppose there will be no problem after all. Would that be ok? The problem with having SMP enabled is that the smp kernel only detects one cpu and the system monitor only features one cpu as well as gkrellm (in Linux it shows two cpus). When compiling the system monitor shows the cpu at a maximum of 50%, so what's going on with the other 50%? writing machdep.hlt_logical_cpus to 2 in loader.conf does not solve anything. I believe FreeBSD uses the other logical CPU to handle hardware interrupts, which can still help performance. You can check dmesg to see how it's actually handling it. -- -- Skylar Thompson ([EMAIL PROTECTED]) -- http://www.cs.earlham.edu/~skylar/ While that is one method of hamdling SMP I'm fairly certain FreeBSD does not use this model. The problem with one CPU handling interrupts and one handling processes is if your doing a 9000x9000 element matrix inversion to calculate say the wave function for uranium (yeah not right, but this be some nasty math so bear with me); then even if the math library is thread aware, one CPU will be frying eggs, and the other one will be twiddling it's thumbs waiting on interrupts to process. Most likely an ACPI_THERMALZONE... From memory on my readings of Implementation of FreeBSD 5.4 ( I think thats the title, but the Black Book written by the BSD gurus...) It was decided the SMP scheduler would handle processes and interrupts simultainiously as scheduled and modified with affinities to avoid switching which CPU cache has the running process. This might be why HT is slower because it only has one CPU cache so trying to keep things on one core doesn't improve performance at all because either core can access the cache. Since HT was not the brightest thing Intel could have done (kind of like 20-bit addressing...) and since AMD has Dual cores they need to compete with I don't think tweaking scheduler code to remove affinities on HT would be in the works. I don't even know if that would help either, just thinking out loud. But Interrupts are handled by both CPUs once the additional CPUs are launched by the boot CPU via the kernel. The scheduler is designed to keep all the pipes in the plant running with process/interuppts. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd
Re: SMP detection
--- Michal Mertl [EMAIL PROTECTED] wrote: Skylar Thompson wrote: Jordi Carrillo wrote: 2006/8/30, backyard [EMAIL PROTECTED]: --- Jordi Carrillo [EMAIL PROTECTED] wrote: I've read that SMP should be disabled for performance issues (I did not know that before installing freebsd). I have a P4 3GHz with hyperthreading technology. I have the SMP-GENERIC kernel and it only launches one cpu. So, I've decided to disable SMP from BIOS. Is that ok?, knowing that I have a Smp enabled kernel? or should I install one without smp? If so, is there a way to install one already precompiled? Thanks in advance -- http://jordilin.wordpress.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] if the system runs with one cpu now and you don't enable smp with HT with the sysctl variable then you should be ok. If your not doing SMP then recompiling the kernel for single processor mode will make things run a little quicker because the SMP code won't come into play. with HT disabling in FreeBSD is more for the security issues about a potential exploit whereby one process in one pipe can access the priveledged information of a process in another pipe because the two cores share one processor cache and thus one cache table. To my knowledge this hasn't been exploited yet. If you just install the generic kernel you it should be only the uniprocessor one. I would just do a: cd /usr/src make buildworld make KERNCONF=GENERIC buildkernel make KERNCONF=GENERIC installkernel as opposed to a binary version assuming you haven't updated yet you won't have to install world but I believe it must have the build in the source tree to build a kernel. On your P4 though the difference between SMP and uniproc may not be worth the trouble because I don't think much of a gain would be made. on a P1 a much different story... if you aren't concerned with bad users or hackers hitting the box I would just enable HT with the sysctl variable. This will not make things run slower at all, just (in theory) less secure, which is why the veriable was created in the first place as I recall. If you are concerned I would wait until you update your system and then just build a GENERIC/CUSTOM kernel without the SMP option set. -brian I will disable smp from bios. If I have a smp kernel, I suppose there will be no problem after all. Would that be ok? The problem with having SMP enabled is that the smp kernel only detects one cpu and the system monitor only features one cpu as well as gkrellm (in Linux it shows two cpus). When compiling the system monitor shows the cpu at a maximum of 50%, so what's going on with the other 50%? writing machdep.hlt_logical_cpus to 2 in loader.conf does not solve anything. I believe FreeBSD uses the other logical CPU to handle hardware interrupts, which can still help perormance. You can check dmesg to see how it's actually handling it. No! Kernel threads (e.g. handling interrupts) aren't that much different to normal processes. Logical CPUs on a single HTT capable CPU share most of the CPU logic, especially all the external stuff (handling interrupts). Scheduling handling of interrupts on the secondary/logical core wouldn't probably help performance at all (if that is at all possible). When FreeBSD sees logical CPUs it means HTT is either enabled in BIOS or that disabling HTT in BIOS does not hide the CPUs to FreeBSD (bug in BIOS/FreeBSD). Until you enable scheduler to schedule tasks to HTT cores (with machdep.hyperthreading_allowed=1 in loader.conf) (disabled by default due to mentioned security/performance reasons) machine won't utilize the logical HTT CPUs. Therefore total CPU utilization won't be more than 50%, because there are the (unused) logical CPUs which don't get scheduled tasks. are you sure about this??? I would have figured the scheduler wouldn't see the other core at all without this option set and so it wouldn't be used in calculating load at all. 50% on a compile is fairly normal from my experience. I don't have too much experience with HT as I always opt for true SMP so I can't speak with authority on the matter. but if top isn't showing CPU 1 or 0 next to a process then it isn't computing the load on multiple cores... Also if dmesg |grep cpu doesn't show application cpu1 (and on through all your cores)... launched then the system isn't looking at the HT core at all. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo
Re: who do you install freebsd without sysinstall?
--- Ruslan Ermilov [EMAIL PROTECTED] wrote: [ added freebsd-questios@ ] On Thu, Aug 31, 2006 at 02:08:59AM +0200, Thomas Vogt wrote: Hello In this emails http://docs.freebsd.org/cgi/getmsg.cgi?fetch=244762+0+current/cvs-src you wrote that you don't install freebsd with sysinstall. May I ask you how you do this? Maybe in some way like this: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/fbsd-from-scratch/? I'm just curious. Plenty of options, depending on the available environment and needs. 1) Add a spare disk to an existing FreeBSD box, and populate it using installworld/installkernel/distribution targets and specifying DESTDIR pointing to a mounted spare disk. 2) Boot from live-system on CD-ROM, prepare and partition the disk(s), install distributions manually through install.sh scripts. 3) Boot from live-system on CD-ROM, prepare and partition the disk(s), CVSup, build/install from sources. 4) Boot in a PXE/TFTP/NFS diskless environment (details are in the Handbook), install distributions using a shell script as above. Distributions may come from either remote CD-ROM media, or be prepared by make release and made available over NFS to diskless clients. A modification of this approach includes a mass deployment option that involves writing (relatively simple) local installation scripts that automate the tasks. Many other options... Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer Out of curiosity... So If I made a custom boot cd I could boot a dead box, setup the drives and slices, CVSUP the system I want to build, tweak the build environment for the proper temporary build locations and build a system from source and install that system to the now live box, boot it and be done? I've always wondered about this because I always remake the system I've just installed because I'm usually dealing with deprecated hardware and all the architecture tweaks I could use help... If that run on is confusing basically to setup FreeBSD like a gentoo install from scratch with a system CD. also along these lines how do I make the system allow me to seed the entropy engine? Usually after an install it asks to fill in a screen full of junk, but with a custom install it doesn't do this for me, at least not the last time I tried. Just curious, especially if I attempt the above procedure. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: shared cache -- Re: SMP detection
--- Chad Leigh -- Shire.Net LLC [EMAIL PROTECTED] wrote: On Aug 30, 2006, at 12:12 PM, backyard wrote: with HT disabling in FreeBSD is more for the security issues about a potential exploit whereby one process in one pipe can access the priveledged information of a process in another pipe because the two cores share one processor cache and thus one cache table. To my knowledge this hasn't been exploited yet. How is this any different than say an Intel Core Duo or Core 2 Duo? I believe they have a shared cache as well for each (real) processor core. Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net I would say there is no difference if what you say is true. A Multi-Core chip is only true SMP if the two cores share no resources internally and thus are capable of running process separate from each other entirely. independantly and with their own internal caches. The process shouldn't have to wait on a lock to access it's cache, which I would have to assume occurs on these HT machines; which is probably why they have degraded performance. The cache should only be shared if a process explicity copies its content to the other cores cache. If should not be possible for both Cores to see the same internal cache. To my knowledge the AMDx2 follow this model with independant cores only sharing a common die. This ensures the context and priveledge of one running process cannot be compromised by a non-priveldeged process waiting on say a login attempt to root, and then grabbing the password from the common cache before the privelidged process can clean up. I don't think this flaw has been exploited yet, but the boys at OpenBSD found it (from memory, pretty sure it was one of them) and it has spread through the BSD community as it has potentially dire consequences. Personally I'm done with Intel so I don't think I'll ever have this issue. Afterall they're still the reason my computer boots up with 640k of RAM... I also think AMD has come from being a clone to being on top of the market, but this is my personal opinion. The fact Core Duos are only 32-bit means Intel is still only concerned with shortend gains on the Windows market, not long term migration to 64-bit PCs like everyone else... And banking on Microsoft has never been a solid idea; its too bad banks use Windows; there's a security nightmare, but a topic in and of itself... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: who do you install freebsd without sysinstall?
--- Ruslan Ermilov [EMAIL PROTECTED] wrote: On Thu, Aug 31, 2006 at 07:53:28AM -0700, backyard wrote: Out of curiosity... So If I made a custom boot cd I could boot a dead box, setup the drives and slices, CVSUP the system I want to build, tweak the build environment for the proper temporary build locations and build a system from source and install that system to the now live box, boot it and be done? Basically yes. When booting from CD though, I'll have to mdconfig(8) and re-mount at least /tmp, maybe /var as well. also along these lines how do I make the system allow me to seed the entropy engine? Usually after an install it asks to fill in a screen full of junk, but with a custom install it doesn't do this for me, at least not the last time I tried. Just curious, especially if I attempt the above procedure. Well, it does this only if the below conditions are met: 1) You have enabled sshd(8) in sysinstall(8), so it's enabled in /etc/rc.conf. 2) This is the first boot, /etc/rc.d/sshd needs to generate new SSH keys but random(4) hasn't been seeded yet. (random(4) is seeded by the /random and /var/db/random/* files.) So, if you did a custom install and then rebooted for the first time, but did not yet enable sshd(8), the cron(8) will save some entropy, so the time you need it to generate SSH keys there will already be some entropy available. But if you absolutely need to reseed manually, boot into single-user mode, and type rm /entropy /var/db/entropy/* Then proceed with normal booting. If sshd(8) is enabled, it will ask you to enter some entropy. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer ok, I figured it was something simple enough like that... how does cron save entropy??? I've noticed saving entropy files at shutdown but have always wondered what it is using. or does it just read from /dev/random? -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP detection
--- Jordi Carrillo [EMAIL PROTECTED] wrote: 2006/8/31, backyard [EMAIL PROTECTED]: --- Michal Mertl [EMAIL PROTECTED] wrote: Skylar Thompson wrote: Jordi Carrillo wrote: 2006/8/30, backyard [EMAIL PROTECTED]: --- Jordi Carrillo [EMAIL PROTECTED] wrote: I've read that SMP should be disabled for performance issues (I did not know that before installing freebsd). I have a P4 3GHz with hyperthreading technology. I have the SMP-GENERIC kernel and it only launches one cpu. So, I've decided to disable SMP from BIOS. Is that ok?, knowing that I have a Smp enabled kernel? or should I install one without smp? If so, is there a way to install one already precompiled? Thanks in advance -- http://jordilin.wordpress.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] if the system runs with one cpu now and you don't enable smp with HT with the sysctl variable then you should be ok. If your not doing SMP then recompiling the kernel for single processor mode will make things run a little quicker because the SMP code won't come into play. with HT disabling in FreeBSD is more for the security issues about a potential exploit whereby one process in one pipe can access the priveledged information of a process in another pipe because the two cores share one processor cache and thus one cache table. To my knowledge this hasn't been exploited yet. If you just install the generic kernel you it should be only the uniprocessor one. I would just do a: cd /usr/src make buildworld make KERNCONF=GENERIC buildkernel make KERNCONF=GENERIC installkernel as opposed to a binary version assuming you haven't updated yet you won't have to install world but I believe it must have the build in the source tree to build a kernel. On your P4 though the difference between SMP and uniproc may not be worth the trouble because I don't think much of a gain would be made. on a P1 a much different story... if you aren't concerned with bad users or hackers hitting the box I would just enable HT with the sysctl variable. This will not make things run slower at all, just (in theory) less secure, which is why the veriable was created in the first place as I recall. If you are concerned I would wait until you update your system and then just build a GENERIC/CUSTOM kernel without the SMP option set. -brian I will disable smp from bios. If I have a smp kernel, I suppose there will be no problem after all. Would that be ok? The problem with having SMP enabled is that the smp kernel only detects one cpu and the system monitor only features one cpu as well as gkrellm (in Linux it shows two cpus). When compiling the system monitor shows the cpu at a maximum of 50%, so what's going on with the other 50%? writing machdep.hlt_logical_cpus to 2 in loader.conf does not solve anything. I believe FreeBSD uses the other logical CPU to handle hardware interrupts, which can still help perormance. You can check dmesg to see how it's actually handling it. No! Kernel threads (e.g. handling interrupts) aren't that much different to normal processes. Logical CPUs on a single HTT capable CPU share most of the CPU logic, especially all the external stuff (handling interrupts). Scheduling handling of interrupts on the secondary/logical core wouldn't probably help performance at all (if that is at all possible). When FreeBSD sees logical CPUs it means HTT is either enabled in BIOS or that disabling HTT in BIOS does not hide the CPUs to FreeBSD (bug in BIOS/FreeBSD). Until you enable scheduler to schedule tasks to HTT cores (with machdep.hyperthreading_allowed=1 in loader.conf) (disabled by default due to mentioned security/performance reasons) machine won't utilize the logical HTT CPUs. Therefore total CPU utilization won't be more than 50%, because there are the (unused) logical CPUs which don't get scheduled tasks. are you sure about this??? I would have figured the scheduler wouldn't see the other core at all without this option set and so it wouldn't be used in calculating load at all. 50% on a compile is fairly normal from my experience. I don't have too much experience with HT as I always opt
Re: SMP detection
--- Jordi Carrillo [EMAIL PROTECTED] wrote: I've read that SMP should be disabled for performance issues (I did not know that before installing freebsd). I have a P4 3GHz with hyperthreading technology. I have the SMP-GENERIC kernel and it only launches one cpu. So, I've decided to disable SMP from BIOS. Is that ok?, knowing that I have a Smp enabled kernel? or should I install one without smp? If so, is there a way to install one already precompiled? Thanks in advance -- http://jordilin.wordpress.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] if the system runs with one cpu now and you don't enable smp with HT with the sysctl variable then you should be ok. If your not doing SMP then recompiling the kernel for single processor mode will make things run a little quicker because the SMP code won't come into play. with HT disabling in FreeBSD is more for the security issues about a potential exploit whereby one process in one pipe can access the priveledged information of a process in another pipe because the two cores share one processor cache and thus one cache table. To my knowledge this hasn't been exploited yet. If you just install the generic kernel you it should be only the uniprocessor one. I would just do a: cd /usr/src make buildworld make KERNCONF=GENERIC buildkernel make KERNCONF=GENERIC installkernel as opposed to a binary version assuming you haven't updated yet you won't have to install world but I believe it must have the build in the source tree to build a kernel. On your P4 though the difference between SMP and uniproc may not be worth the trouble because I don't think much of a gain would be made. on a P1 a much different story... if you aren't concerned with bad users or hackers hitting the box I would just enable HT with the sysctl variable. This will not make things run slower at all, just (in theory) less secure, which is why the veriable was created in the first place as I recall. If you are concerned I would wait until you update your system and then just build a GENERIC/CUSTOM kernel without the SMP option set. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP detection
--- Jordi Carrillo [EMAIL PROTECTED] wrote: 2006/8/30, backyard [EMAIL PROTECTED]: --- Jordi Carrillo [EMAIL PROTECTED] wrote: I've read that SMP should be disabled for performance issues (I did not know that before installing freebsd). I have a P4 3GHz with hyperthreading technology. I have the SMP-GENERIC kernel and it only launches one cpu. So, I've decided to disable SMP from BIOS. Is that ok?, knowing that I have a Smp enabled kernel? or should I install one without smp? If so, is there a way to install one already precompiled? Thanks in advance -- http://jordilin.wordpress.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] if the system runs with one cpu now and you don't enable smp with HT with the sysctl variable then you should be ok. If your not doing SMP then recompiling the kernel for single processor mode will make things run a little quicker because the SMP code won't come into play. with HT disabling in FreeBSD is more for the security issues about a potential exploit whereby one process in one pipe can access the priveledged information of a process in another pipe because the two cores share one processor cache and thus one cache table. To my knowledge this hasn't been exploited yet. If you just install the generic kernel you it should be only the uniprocessor one. I would just do a: cd /usr/src make buildworld make KERNCONF=GENERIC buildkernel make KERNCONF=GENERIC installkernel as opposed to a binary version assuming you haven't updated yet you won't have to install world but I believe it must have the build in the source tree to build a kernel. On your P4 though the difference between SMP and uniproc may not be worth the trouble because I don't think much of a gain would be made. on a P1 a much different story... if you aren't concerned with bad users or hackers hitting the box I would just enable HT with the sysctl variable. This will not make things run slower at all, just (in theory) less secure, which is why the veriable was created in the first place as I recall. If you are concerned I would wait until you update your system and then just build a GENERIC/CUSTOM kernel without the SMP option set. -brian I will disable smp from bios. If I have a smp kernel, I suppose there will be no problem after all. Would that be ok? The problem with having SMP enabled is that the smp kernel only detects one cpu and the system monitor only features one cpu as well as gkrellm (in Linux it shows two cpus). When compiling the system monitor shows the cpu at a maximum of 50%, so what's going on with the other 50%? writing machdep.hlt_logical_cpus to 2 in loader.conf does not solve anything. -- machdep.hyperthreading_allowed=1 in loader.conf from my reading on the web... is the variable you should probably be setting, the other variable will disable cpu's on the system or limit how many are used. It does not turn on HT. Linux does not have an option like this to disable HT, I believe it must be passed to the kernel at boot and I don't know what the exact switch is but the Linux community is not as concerned with the potential exploit as the *BSD community is and so they let HTs run under their SMP kernel. 50% is running idle, this is pretty normal, At least on the systems I've seen when it is building the system. You have to remember most of compiling is reading code and libraries then putting it together and back on the hard drive. Compiling is I/O intensive more then CPU intensive. If you set MAKEOPTS=-j5 in make.conf you will compile quicker use more cpu power, but it will maybe spike around 80%. usually this is set by 2X CPU_CORES +1 but it makes my dual p3 550Mhz Xeon build a system with the quickness... You maybe able to get away with -j9 as my little formula might be based on Linux more then BSD and I know generally BSD allows for more make processes to be going at once. maybe 4x CPU_CORE +1 is more in order. Experiment until your loaded as high as you want to, but its nice to have Gnome/KDE going while you're building a system and watching a movie; so having 50% to play with isn't a bad thing... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
XML transformation and processing with Zope -- or something better suggestions welcome
I have a client who wishes to automate their order processing system for their online business. presently they download reports from their business frontend and upload them manually to their shipper. Both systems can use XML and a precursory look at the document tags suggests a simple XSLT transform should be able to translate the tags fairly simply. I was thinking of using Zope to setup a server that will get the orders from the website, transform them, and then upload them to the shipper. I built Zope3 last night and went to bed... In the morning I tried to build the zope-xml* pluggins. However they start building python 2.3.5-1, despite python 2.4.x that was built for zope3. I'm fairly certain I can't have more then one version of python but maybe I'm mistaken. I didn't want to deal with it when I woke up so I stopped the builds. Just wondering if anyone has any familiarity with Zope, its pitfalls and merits, or if there is an easier way to do what I described above. My client doesn't care about keeping a local copy of the orders but I want to for error control and checking purposes. I was going to use xmlcatmgr for this purpose. I would setup two catalogs one for raw and processed orders. At this point I care more about keeping each order processing unit if you will in its own little compartment, perhaps a simple db by date would be more in order with XML as the content. any kind of pointers would be appreciated as this is my first real task building a system that does something real... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fdisk: ERROR: failed to adjust; setting sysid to 0
--- mark burdett [EMAIL PROTECTED] wrote: Hi, I was wondering what is the proper procedure for using fdisk to setup slices on large disks/arrays? I seem to be getting an ERROR when fdisk tries to adjust the partition to start on a head boundary and end on a cylinder boundary. Should I ignore the warning re: partition does not end on a cylinder boundary and write the partition table? Or should I attempt to set all the correct numbers by hand, since the automatic correction fails? I've attached the warnings and errors I saw on fdisk. --mark fileserver1# fdisk -u *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=364716 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=364716 heads=255 sectors/track=63 (16065 blks/cyl) Do you want to change our idea of what BIOS thinks ? [n] Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 1564195181 (763767 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 165/ sector 59 Do you want to change it? [n] The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 1564195248, size 2147478417 (1048573 Meg), flag 0 beg: cyl 86/ head 166/ sector 1; end: cyl 640/ head 254/ sector 63 Do you want to change it? [n] The data for partition 3 is: UNUSED Do you want to change it? [n] yes Supply a decimal value for sysid (165=FreeBSD) [0] 165 Supply a decimal value for start [0] 3711673665 Supply a decimal value for size [0] 2147490495 fdisk: WARNING: partition does not end on a cylinder boundary fdisk: WARNING: this may confuse the BIOS or some operating systems Correct this automatically? [n] y fdisk: ERROR: could not adjust partition to start on a head boundary and end on a cylinder boundary. fdisk: ERROR: failed to adjust; setting sysid to 0 Explicitly specify beg/end address ? [n] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] As long as your not using DOS/Winblows/OS-2 you shouldn't have problems. Microsft/PC os's have the requirement that partition boundarys end on and begin on cylinder boundaries. The main thing is the BIOS, some of them will accept it some won't as they are setup to use DOS, et al. And I belive it would only mess up booting the system. This can be hit or miss so I would try it. If they aren't boot drives, and newfs completes sucessfully on the partitions then all should be ok. Any particular reason you are partitioning multiple partitions for FreeBSD? this should only be done if your planning on having multiple versions of FreeBSD/OpenBSD/NetBSD going. bsdlabel is where you slice the drive into different pieces for your filesystems. I have a scsi setup that I used a dangerously dedicated mode whose scsi bios says the partition table is corrupt, low level format required on one or more drives but FreeBSD don't care and boots up fine. These aren't the boot drives, but if BSD is only warning you then it won't care in the end. It just likes to try and play nice with other OSs unlike the other OSs. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fdisk: ERROR: failed to adjust; setting sysid to 0
--- mark burdett [EMAIL PROTECTED] wrote: should be ok. Any particular reason you are partitioning multiple partitions for FreeBSD? this For some reason, when we ordered the server w/ freebsd pre-installed, the vendor created a slice which was less than half the size of the full raid array (2TB). Perhaps because sysinstall was having trouble with a slice larger than 2TB? This page -- http://www.freebsd.org/projects/bigdisk/ -- may be out of date, but it reports: sysinstallNot doneA full audit is needed. Reports exist of problems with 1TB partitions. --mark wish I could say I had problems getting my system to see a full 2TB as one partition... informative link though, it sounds like when they implement what they want the only solution to upgrade is to pray. That or hope once the userland suite is update is complete; some kind of update, dump, use the new tools to prepare the drives, and restore. can't wait for that one. although I don't have the problem of having Terabytes to worry about yet... good luck -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new 6.1 install will not boot
--- Greg Barniskis [EMAIL PROTECTED] wrote: Perry Hutchison wrote: Well, you're at least as far as having the disk sliced up in a workable way, or the bootstrap wouldn't start at all. This jumps out as not only being bad, but happening right before meltdown. acpi: bad RSDP checksum (210) I suspect it's a red herring, since I was getting that message at that point when everything was working (with the 10GB drive). That could be. I thought it might be a symptom of the BIOS version being the root of the problem, and of course once that's foo all bets are off. After a CD boot, is there a reasonably simple way to have sysinstall reinstall just the kernel -- or the package containing it -- without starting completely over? Yeah, see what Derek wrote. Never done that, myself, or even heard of the kernel not getting installed. The BIOS version is A08. Dunno if it is the latest, but I do have ACPI turned off in the BIOS. I guess it is arguably a BIOS bug for an RSDP to exist when ACPI is disabled, and/or a FreeBSD bug to be complaining about ACPI when it is disabled. Whose bug? is often largely a matter of semantics when two pieces of software fight. It's likely that for historical hardware, only FreeBSD developers could fix the conflict at this point, but that seems unlikely unless (after you get things otherwise working) you're willing to do extensive trial and error, debugging operations, etc. You're probably right about it being a red herring for your immediate boot problem, but ACPI issues do cause all kinds of trouble, so keep an eye on it. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] going to jump in but ignore if my assumptions are wrong... I remeber in this thread somewhere it was saying you had a Dell GX1??? I've installed FreeBSD 6.0 on such a system and upgraded to 6.1-p3. The A08 BIOS is old, A10 is what I have. I think thats the latest but I'm not positive. ACPI needs to be turned on in the BIOS in order for shutdown -p to function otherwise you must manually shut it off after the halt. Whatever you do DO NOT INSTALL GRUB. It doesn't work at all and just corrupts the root partition. At least this has been my experience, only machine so far I've encountered. I would update the bios first to A10 or the latest (let me know if A10 ain't the latest), make sure ACPI is turned on and then find yourself a 6.0 iso to install and then upgrade it. Especially if there is a problem with 6.1 installing a kernel. Maybe this has been asked but the install did ask you which distribution you wanted right? Sometimes sysinstall gets confused when I change my mind on things and never asks for the distributions I want to install. This always ends with an unusable system. even though it appears to be installing something. good luck, if this is an GX1 it should work eventually, and if memory serves me the A10 bios fixed some ACPI issues from previous version. Although it seems that all Dell updates fix ACPI issues so maybe I'm just getting confused. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: More newbie questions
--- E. Gad [EMAIL PROTECTED] wrote: Svein Halvor Halvorsen [EMAIL PROTECTED] wrote: Subhro wrote: yourself. However remember to cvsup your ports tree before you start using it to get the required software. Refer to the handbook for understanding how ports work. For most people portsnap would be a better way of updating one's ports tree. Firstly, it's in the base system and thus doesn't require any third party software. Secondly, most newbies find it easier to use. as long as your remember to install it as a port during the install or add it with sysinstall or pkg_add. cvsup-nogui then doing a: make update in /usr/src or /usr/ports will automagically use the default examples and update things. As long as your going from a 6.x base it will continue on Rel_6.x. If you started with 5.x it will continue to update 5.x. Ports will always update to the latest and greatest as it uses a different tag. I find this very easy, I'm also afraid of change. Though portsnap is more secure because it uses encryption and I've heard signs the updates. To each their own though one way of the other updating your SRC and PORTS is an important thing to learn how to do. Svein Halvor Hmm porstnap seemed to have worked ok. I installed the portupgrade suite through pkg_add. Somethings still not happy. Because when took a stab at installing: nvidia-driver nvidia-glx xorg and compat 5 as a dependency for nvidia-driver/nvidia-glx nvidia can't find something and I don't know what because the first part of the message scrolls of the screen- (remember I'm not in xorg yet) if you don't have X yet then I don't think the nvidia drivers will install because they are quite dependant on X. no X required here... hit scroll lock and then PgUp and PgDn this will let you view the scroll back buffer and see what you cannot see. the up and down arrows will work too. -What the newbie here has done so far to help itself- Just as a guess-reinstalled linux_base because I remembered reading on a Just Some Guys 'Blog abut the same problem thinking it couldn't hurt anything since I hadn't installed hardly much of anything- cd /usr/ports/emulators/linux_base. make deinstall make clean make install Ran that for 15 minuts-it ran into some sort of error 1! (repeated 5 times) Undaunted-re- did make etc. Somethng about rpm something not found (cd'd into linux_bas-fc4) ran make install clean-but it says it can't find the ftp servers- Any guesses what I'm doing wrong? install archivers/rpm should fix that but it should know to do it itself. Unless your stuck using that particular dist of linux I would try to gentoo stage3 base. a chroot to the /compat/linux and you can use their portage system to install and update linux apps fairly easy. The reason I got away from linux in the first place was the nightmare of updating it, but at least Gentoo uses a ports system that makes it less of a nightmare. Of course I am biased because I do run Gentoo on my laptop and would want the emulation base to be compatible if I package up native Gentoo apps to my FreeBSD system. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: More newbie questions-again?
--- E. Gad [EMAIL PROTECTED] wrote: backyard [EMAIL PROTECTED] wrote: --- E. Gad wrote: Svein Halvor Halvorsen wrote: Subhro wrote: yourself. However remember to cvsup your ports tree before you start using it to get the required software. Refer to the handbook for understanding how ports work. For most people portsnap would be a better way of updating one's ports tree. Firstly, it's in the base system and thus doesn't require any third party software. Secondly, most newbies find it easier to use. as long as your remember to install it as a port during the install or add it with sysinstall or pkg_add. cvsup-nogui then doing a: make update in /usr/src or /usr/ports will automagically use the default examples and update things. As long as your going from a 6.x base it will continue on Rel_6.x. If you started with 5.x it will continue to update 5.x. Ports will always update to the latest and greatest as it uses a different tag. I find this very easy, I'm also afraid of change. Though portsnap is more secure because it uses encryption and I've heard signs the updates. To each their own though one way of the other updating your SRC and PORTS is an important thing to learn how to do. Svein Halvor Hmm porstnap seemed to have worked ok. I installed the portupgrade suite through pkg_add. Somethings still not happy. Because when took a stab at installing: nvidia-driver nvidia-glx xorg and compat 5 as a dependency for nvidia-driver/nvidia-glx nvidia can't find something and I don't know what because the first part of the message scrolls of the screen- (remember I'm not in xorg yet) if you don't have X yet then I don't think the nvidia drivers will install because they are quite dependant on X. no X required here... hit scroll lock and then PgUp and PgDn this will let you view the scroll back buffer and see what you cannot see. the up and down arrows will work too. -What the newbie here has done so far to help itself- Just as a guess-reinstalled linux_base because I remembered reading on a Just Some Guys 'Blog abut the same problem thinking it couldn't hurt anything since I hadn't installed hardly much of anything- cd /usr/ports/emulators/linux_base. make deinstall make clean make install Ran that for 15 minuts-it ran into some sort of error 1! (repeated 5 times) Undaunted-re- did make etc. Somethng about rpm something not found (cd'd into linux_bas-fc4) ran make install clean-but it says it can't find the ftp servers- Any guesses what I'm doing wrong? install archivers/rpm should fix that but it should know to do it itself. Unless your stuck using that particular dist of linux I would try to gentoo stage3 base. a chroot to the /compat/linux and you can use their portage system to install and update linux apps fairly easy. The reason I got away from linux in the first place was the nightmare of updating it, but at least Gentoo uses a ports system that makes it less of a nightmare. Of course I am biased because I do run Gentoo on my laptop and would want the emulation base to be compatible if I package up native Gentoo apps to my FreeBSD system. -brian About that nvidia-thing here's the messages: libtool cannot find the library /usr/local/lib/libintl.la or undhandled argument in /usr/local/libintl.la gmake[2]:***[dump] Error 1 gmak[2]:leaving director /usr/ports/archivers/rpm/work/rpm-3.0.6/tools gmake[2]:[all-recursive]-Error 1 gmake[1]leaving director /usr/ports/archivers/work/rpm-3.0.6 gmake *** [all-recursive-am- Error 2 Error code 2 Stop in /usr/ports/archivers/rpm Errror code 1 Stop in /usr/ports/archivers/rpm Error code 1 ---snip stop in /usr/ports/emulators/linux_base-fc4 /* Why is it having issues with this? */ Stop in /usr/ports/x11/nvidia-driver. command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall542.0 make reinstall **Fix the installation problem and try again ***Listing failed packages(*skiped/ !FAILED) !xll/driver(install error) packages processed: 0 well it looks like gettext is messed up or rpm can't find the proper library to link to. Try (re)installing gettext. The rest happens because rpm is missing and I think nividia's drivers are packaged as an rpm. I don't know why fedora-core is popping up. perhaps you need to set LINUX_BASE=gentoo in make.conf. I think that is the correct syntax but man make.conf should have the right syntax. I think for whatever reason rpm has something to do with the fedora-core base source. I'm not positive but building it in the past I seem to recall something going on with fedora-core. that or i seem to recall nvidia used a self running and extracting rpm which is linked to fedora core because redhat obviously created the redhat
Re: GRUB Problems with Dell Optiplex GX1
--- Garrett Cooper [EMAIL PROTECTED] wrote: On Aug 21, 2006, at 6:41 PM, backyard wrote: --- Garrett Cooper [EMAIL PROTECTED] wrote: backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garrett #menu.lst default 0 timeout 7 fallback 1 #password --md5 some kind of password that is encypted splashimage (fd0)/boot/grub/opt/smurffed.xpm.gz title BSD root (hd0,0,a) kernel /boot/loader title Hold the Phone halt title Reset me reboot title Floppy Boot lock root (fd0) chainloader #EOF menu.lst here is my menu.lst off my grub install floppy. this was created by building grub 0.97 from ports on my HP Kayak. the floppy was then prepared as below: fdformat /dev/fd0 newfs -O1 -n /dev/fd0 mount /dev/fd0 /mnt mkdir -p /mnt/boot/grub/opt I then copied the grub files from the /usr/local/share/grub/i386-freebsd if memory serves me correct to the /mnt/boot/grub folder. then copied in my splashimages, then prepared menu.lst as described. I then ran grub and setup the floppy to boot grub. now to install on a system I: mkdir -p /boot/grub/opt mount /dev/fd0 /mnt; cp -R /mnt/boot/grub /boot/grub change menu.lst as required to reference hardrives or different boot options like a windows partition or linux or whatever needs to be started up. boot the system with the floppy and go to grub console. make sure I can find /boot/grub/menu.lst then... root (hd0,0,a) # or whatever setup (hd0) # again depends and usually I take the floppy out, reboot, and grub asks me what I want to boot up. as far as the exact output from grub I don't know, but it didn't give any errors. it just said: checking for /boot/grub/menu.lst found installing stage1 success installing stage1_5 success installing stage2. success the typical everything is ok message. I have heard in later reading that a missing splashimage can mess things up, I will have to make sure I remembered to change the root for the image to the harddrive. But I have also read that this just happens sometimes with grub and certain machines. this is the only time I've seen it happen. I personally love me some grub. it just makes things easier in my world; at least usually. -brian Ok, it seems like your installation process at least is ok; perhaps the location of the installed grub is incorrect though. Could you do the following? 1.Run fdisk and verify that the partition you actually have your root installed on is the first one. 2.Replace all references to just / (root) in all partition names to the proper device name, plus root, e.g.: root (hd0,0,a) kernel (hd0,0,a)/boot/loader I know it seems a bit redundant, but it's saved me from some issues with installing grub on my linux box. 3.Remove the splashedimage reference. It's referring to your floppy and if the floppy isn't there I could see some possible issues occurring with booting grub, as you mentioned earlier in the email. -Garrett I'll give this a whirl and report back as to what happens, but I think I just have one of the machines that grub just doesn't like very much. Its just a good thing it happened to be the one machine I have that will never see anything but BSD on it. Like I said GRUB was just to put an inappropriate splash screen up to tick off my friends should they ever turn the thing on with a monitor plugged into it... That being said it's still annoying when things don't work out the way you want. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hangs during dump with 6.0 and current ports
I've had problems with dump and restore on machines lacking memory before. Perhaps the dump is just running the system out of memory? I know I've had issues restoring my /usr filesystem with 512M RAM unless I had a swapfile active. I also find it helps to make sure /tmp has got enough space on it at least on restores. Maybe you need some more swap space? Since its dumping live filesystems and your running services then the snapshot would have to be buffered somewhere, and in your case swap would likely be where. -brian --- Martin Werner [EMAIL PROTECTED] wrote: Hi, I'm running 6.0 on a Celeron 800MHz with 128MB and just updated the system to current ports (incl. perl 5.8.8). The systems is running apache, mysql, postfix and dovecot with a minor load (especially at the time when the system is backed-up) The issue I have is that my backup-script using dump will keep the system in a state where the IP-Stack is still there (can ping an scan ports), but no requests whatsoever are accepted and due to that I can't access the system via ssh and tell what's going on. The last time I had a ssh-session open with top: Here is the first few lines output: snip -- last pid: 948; load averages: 0.00, 0.00, 0.00 up 0+00:37:51 08:54:13 72 processes: 1 running, 62 sleeping, 9 waiting CPU states: 0.0% user, 0.0% nice, 0.4% system, 0.4% interrupt, 99.2% idle Mem: 59M Active, 16M Inact, 39M Wired, 288K Cache, 22M Buf, 480K Free Swap: 357M Total, 69M Used, 288M Free, 19% Inuse PID USERNAME THR PRI NICE SIZERES STATE TIME WCPU COMMAND 591 mysql 5 200 56884K 1680K kserel 0:05 0.00% mysqld 658 root1 960 24344K 15948K select 0:04 0.00% perl5.8.8 908 root1 960 2416K 1436K RUN 0:03 0.00% top 722 root1 960 26132K 0K WAIT 0:02 0.00% perl5.8.8 - end -- Here is the script I am running via cron: --- snip --- #!/bin/sh dump=/sbin/dump wput=/usr/local/bin/wput chflags=/bin/chflags dt=`date +%Y%m%d` destpath=/usr/dump logfile=$destpath/backup.log lvl= lvl=$1 if [ x$lvl != x ] then echo Backup Level: $lvl $logfile else echo No Backup-Level specified - exiting $logfile exit 911 fi # / src1=/dev/ad0s1a # /var src2=/dev/ad0s1d # /usr src3=/dev/ad0s1f dest1=root_ad0s1a_$dt.gz dest2=var_ad0s1d_$dt.gz dest3=usr_ad0s1f_$dt.gz # Ausnahmen NO BACKUP $chflags -R nodump /usr/ports/ $logfile 21 $chflags -R nodump /usr/src/$logfile 21 $chflags -R nodump /usr/obj/$logfile 21 $chflags -R nodump /usr/dump/ $logfile 21 $chflags -R nodump /usr/swapfile2 $logfile 21 # Fullbackup Level 0 Monatlich $dump -$lvl -h 0 -Lauf - $src1 | gzip -2 | dd of=$destpath/$dest1 $logfile 21 $dump -$lvl -h 0 -Lauf - $src2 | gzip -2 | dd of=$destpath/$dest2 $logfile 21 $dump -$lvl -h 0 -Lauf - $src3 | gzip -2 | dd of=$destpath/$dest3 $logfile 21 end --- The chflags are executed correctly, the first two dumps are done and during the 3rd dump execution against the /usr Mount-Point the system ends up in the state described above. There is no dump in /var/crash - nothing in /var/log/messages - dmesg aswell just states that the filesystems were not properly dismounted (couldn't have guessed that :-) I'd have a hard time trying to directly access the system (only have remote access) therefore I can't tell whats on the console at the time of the hang. Thanks for any help in advance Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GRUB Problems with Dell Optiplex GX1
I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
--- Garrett Cooper [EMAIL PROTECTED] wrote: backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garret #menu.lst default 0 timeout 7 fallback 1 #password --md5 some kind of password that is encypted splashimage (fd0)/boot/grub/opt/smurffed.xpm.gz title BSD root (hd0,0,a) kernel /boot/loader title Hold the Phone halt title Reset me reboot title Floppy Boot lock root (fd0) chainloader #EOF menu.lst here is my menu.lst off my grub install floppy. this was created by building grub 0.97 from ports on my HP Kayak. the floppy was then prepared as below: fdformat /dev/fd0 newfs -O1 -n /dev/fd0 mount /dev/fd0 /mnt mkdir -p /mnt/boot/grub/opt I then copied the grub files from the /usr/local/share/grub/i386-freebsd if memory serves me correct to the /mnt/boot/grub folder. then copied in my splashimages, then prepared menu.lst as described. I then ran grub and setup the floppy to boot grub. now to install on a system I: mkdir -p /boot/grub/opt mount /dev/fd0 /mnt; cp -R /mnt/boot/grub /boot/grub change menu.lst as required to reference hardrives or different boot options like a windows partition or linux or whatever needs to be started up. boot the system with the floppy and go to grub console. make sure I can find /boot/grub/menu.lst then... root (hd0,0,a) # or whatever setup (hd0) # again depends and usually I take the floppy out, reboot, and grub asks me what I want to boot up. as far as the exact output from grub I don't know, but it didn't give any errors. it just said: checking for /boot/grub/menu.lst found installing stage1 success installing stage1_5 success installing stage2. success the typical everything is ok message. I have heard in later reading that a missing splashimage can mess things up, I will have to make sure I remembered to change the root for the image to the harddrive. But I have also read that this just happens sometimes with grub and certain machines. this is the only time I've seen it happen. I personally love me some grub. it just makes things easier in my world; at least usually. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cinelerra for *BSD ??? or something similar in Ports?
Just wondering if anyone has ever heard of a port of cinelerra to FreeBSD. Or if anyone knows of any comperable video editting software for FreeBSD available in Ports. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cinelerra for *BSD ??? or something similar in Ports?
--- Andrew Pantyukhin [EMAIL PROTECTED] wrote: On 8/14/06, backyard [EMAIL PROTECTED] wrote: Just wondering if anyone has ever heard of a port of cinelerra to FreeBSD. Not until we port alsa. ok, well then if I got through the trouble of setting up my gentoo base install with all the dependancies for Cinelerra, I should be able to build it and run it in emulated mode right??? Theorized speculation is a good enough answer for me right now. Or will ALSA still not compile in the Native emulated mode under a chroot to /compat/linux environment? time to mess with portage I guess... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cinelerra for *BSD ??? or something similar in Ports?
--- Andrew Pantyukhin [EMAIL PROTECTED] wrote: On 8/14/06, backyard [EMAIL PROTECTED] wrote: --- Andrew Pantyukhin [EMAIL PROTECTED] wrote: On 8/14/06, backyard [EMAIL PROTECTED] wrote: Just wondering if anyone has ever heard of a port of cinelerra to FreeBSD. Not until we port alsa. Or will ALSA still not compile in the Native emulated mode under a chroot to /compat/linux environment? It might, but it won't work for sure. well thats unfortunate. Any similar existing ports at our disposal? -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using putty as a ssh client on FreeBSD
--- Josh Paetzel [EMAIL PROTECTED] wrote: I'm trying to use putty on my FBSD 6.1-R box to access another FreeBSD box. I can get in fine using the command line ssh client but when I attempt to use putty I get the following error: Unable to use key file /usr/home/jpaetzel/.ssh/id_rsa (OpenSSH SSH-2 private key) Can anyone point out to me what I am doing wrong? -- Thanks, Josh Paetzel ___ I'm pretty sure putty uses a different form of encryption with their key files. I know they do in the Windows version anyway. They have a tool you can use to convert your key into something putty likes. Try to find putty-keygen or something along those lines; perhaps as a separate port. I've had issues like this connecting to my FreeBSD boxes from Windows with putty, but ultimately found a way to import the BSD key into puttys format with their key-generator program. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting more than 4 OSes from a hard disk?
Windows 2000+ can boot on an extended partition as can linux, the BSDs, I think OS/2 warp+ can as well. So you can still only have 4 primary partitions, but you probably only need one that has a bootloader like GRUB on it marked active and the OSs installed all on extended partitions. I've even supprisingly confirmed if GRUB is installed windows won't install it's own bootloader. At least with Win2000sp4 this was the case the one time I tried... I would use GRUB cause its simple, fits on a floppy and is easy to install from that booting floppy. It shouldn't require any special booting options other then boot from harddrive. I would guess BSD doesn't care where it boots from in terms of sectors on the HD, but making a bootloader do this is something I wouldn't be able to answer. Although I know Grub allows you to chainload an arbritary number of sectors from the bootsector so I would look into that for exotic boots as you allude too. -brian --- Girish Venkatachalam [EMAIL PROTECTED] wrote: Dear all, I was wondering if the 4 primary parition booting limit still exists. Is it possible to have Windoze Linux FreeBSD OpenBSD NetBSD on the same box in such a way that we can boot into any of them? I am particularly interested in the x86 arch with IDE disks. I think this is possible on other archs with SCSI. What boot manager am I supposed to use? Does it require setting something on the BIOS? Does FreeBSD support booting from a point way off the first sector? Thanks. regards, Girish __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: /etc/fstab error and I can't start the system normally
--- micman [EMAIL PROTECTED] wrote: On Aug 7, 2006, at 1:26 PM, micman wrote: Hello. PROBLEM I tried and configured FreeBSD 6.1 for many days and I mounted my FAT extended partition to exchange my files between Windows and my new Operating System. That was OK. After I tried to mount automatically at boot this partition and I make an error (grammatical error): I wrote acd0s5 instead of ad0s5 in /etc/ fstab. Now, when I start the system, I receive this message at the end of the boot process: Can't open (No such file or directory) /dev/acd0s5: UNEXPECTED INCONSISTENCY; RUN fsck_msdosfs MANUALLY. THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: msdosfs: /dev/acd0s5 (/mnt/win) Automatic file system check failed; help! Aug 7 20:08:07 int: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: QUESTIONS Can I rewrite the file /etc/fstab in text mode? If it's possible, how can I do this? I tried fsck_manually and also to boot by option '6' (Escape to loader) but I was not able to resolve the problem. If someone can help me, thank you. __ get into a console maybe by booting single user. remote root as read/write you may or may not have to remount root as write but... mount -u / ee /etc/fstab fix the error hit [esc] cc [esc] a and you should be good to go. hope that helps -brian I have tried. Result: can't exec mount -u / for single user: No such file or directory and ee: not found About ee in the FreeBSD command reference I have tried this: This is a simpler alternative to 'vi' and is installed as part of the FreeBSD base system. However it may not always be available (there is /rescue/vi for emergencies when /usr is not mounted, but no emergency 'ee'). I have tried 'vi': not found But in my /rescue 'vi' is listed and I have this message: no terminal database found __ You can go to single user mode (4) from the boot menu and then mount - o rw / . Then you can edit /etc/fstab. Pramod Venugopal I have tried. Result: can't exec mount -o rw / for single user: No such file or directory ___ Thank you for your answers. yeah sorry about the ee thing for some reason it is not in the rescue directory only vi is which will work, but not my favorite editor. to get ee you would have to mount /usr and its in /usr/bin if I'm not mistaken. you might have to use absolute paths to get programs to run like /usr/bin/ee /etc/fstab or /rescue/vi /etc/fstab if your gungho about things. as for the mount error that is odd. did you check the output of just a plain mount if it tells you root is mounted r/w which I think would be so unless it says readonly then you don't have to worry about that step. Bur single user mode always puts root in readonly. I haven't experienced it puking during boot because of a bad line in fstab though so I am not certain how that works. Your best bet is probably to boot from the FreeBSD install disk, run Fixit shell from the CD/DVD-Rom option. then type /dist/sbin/mount /dev/ad0s(insert your bsd slice \ here)a /mnt then run ee /mnt/etc/fstab or /dist/usr/bin/ee /mnt/etc/fstab I don't think the absolute paths to everything is necessary, but I'll give them anyway to cover the bases. note if your want to mount that msdosfs for whatever reason you have to do this sysctl kern.module_path=/dist/boot/kernel /dist/sbin/mount_msdosfs /dev/ad0s5 /foobar I've had to deal with that little problem before. the fixit shell does not load all the kernel modules you might need only a subset, and mount -t msdosfs doesn't seem to work anytime I try it so that one REQUIRES the absolute path to work. good luck -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: so for kicks, i just ...
--- RW [EMAIL PROTECTED] wrote: On Monday 07 August 2006 02:57, Jonathan Horne wrote: i just decided to take a box, and installworld, without going to single user mode. from what i can see, the update was completely successful. of course, other then myself (su'd to root), there were no other users logged in). i wonder how many people are brave enough, and do actually installworld without changing to single user mode? i wonder what is truly at risk from not going to single mode? I always do that on point releases. but given the infrequency of releases it doesn't seem worth saving any effort there. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I used to do it on every install and only had issue once, which was more and issue with mergemaster and going line by line and not knowing to answer l and r... with the merge option, something another installworld fixed for me... But like yourself I never have anybody but myself logged in. I got some old serial multiplexors with a 10-base2 ethernet connection for a serial console. for when I need to actually worry about real users. Has anybody had SERIOUS problems installingworld with load on the system? It just seems like a potentially bad idea, and have since started going to single user for my updates nowadays. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/fstab error and I can't start the system normally
--- micman [EMAIL PROTECTED] wrote: Hello. PROBLEM I tried and configured FreeBSD 6.1 for many days and I mounted my FAT extended partition to exchange my files between Windows and my new Operating System. That was OK. After I tried to mount automatically at boot this partition and I make an error (grammatical error): I wrote acd0s5 instead of ad0s5 in /etc/fstab. Now, when I start the system, I receive this message at the end of the boot process: Can't open (No such file or directory) /dev/acd0s5: UNEXPECTED INCONSISTENCY; RUN fsck_msdosfs MANUALLY. THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: msdosfs: /dev/acd0s5 (/mnt/win) Automatic file system check failed; help! Aug 7 20:08:07 int: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: QUESTIONS Can I rewrite the file /etc/fstab in text mode? If it's possible, how can I do this? I tried fsck_manually and also to boot by option '6' (Escape to loader) but I was not able to resolve the problem. If someone can help me, thank you. [EMAIL PROTECTED] get into a console maybe by booting single user. remote root as read/write you may or may not have to remount root as write but... mount -u / ee /etc/fstab fix the error hit [esc] cc [esc] a and you should be good to go. hope that helps -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
