Re: Cannot make open-vm-tools on 9.1
Hi, > I have a strange thin happening to me. I upgraded two machines from > 8.3 to 9.1: > > FreeBSD sysl2.cs.ait.ac.th 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #3: Fri May > 31 > 14:59:20 ICT 2013 root@fbsd63:/usr/obj/usr/src/sys/GENERIC i386 > > I did both upgrade in parallel. > > On the first machine, I managed to intall open-vm-tools-nox11: > > open-vm-tools-nox11-425873_3,1 Open VMware tools for FreeBSD VMware guests > > but when I try to install it on the second machine, I have a compile > error (see below). > > Now I try to rebuild open-vm-tools on the first machine and I get the > same compile error. Replying to myself, I know. After spending 3 days trying to work out the problem (and installing a couple of other systems without problems), I decided to re-try an OS installation. I relaunched a cvsup to download the OS source and was surprised to see that a number of files were checked-out (which should not happen as I am using RELENG). So I suspect that my previous cvsup was interruped some how. After a make buildworld, kernel and installworld, everything is fine. Now I am puzzeled that the OS managed to build from incomplete sources and that the machine was sable. Best regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
perl threaded, python threaded
Hi, could anyone tell me why it is obviously that difficult to get perl or python working with threaded support? Each time I tested to use threaded feature in perl or python on different machines with different FreeBSD-versions something went wrong. When I switched back everything compiled smoothly. Maybe this was already discussed somewhere. Then please give me the link. Regards, kaltheat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 8.4-RELEASE buildworld failure
13.06.2013 19:24, Rick Miller пишет: > Hi all, > > I checked out releng/8.4, executed buildworld, and received the following > error. Wondering if someone might have experience with this scenario. Is it persistent? I.e. what if you remove /usr/obj and start once again? > ===> share/doc/psd/13.rcs/rcs_func (all) > groff -Tascii -P-c -mtty-char -ms > /usr/src/share/doc/psd/13.rcs/rcs_func/../../../../../gnu/usr.bin/rcs/doc/ > rcs_func.ms | gzip -cn > rcs_func.ascii.gz > ===> share/doc/psd/15.yacc (all) > touch _stamp.extra > make: don't know how to make ssA. Stop Is the processor over heating? Can you play with RAM? (toggle banks or else) > There is no src.conf and make.conf only sets PERL_VERSION. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Daily periodic cronjob generates core dump
Hi all, I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am receiving in security output this message: fbsd.domain.local kernel log messages: +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 +(try), uid 0: exited on signal 10 (core dumped) How can I detect where is the problem?? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Daily periodic cronjob generates core dump
C. L. Martinez writes: > I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I > am receiving in security output this message: > > fbsd.domain.local kernel log messages: > > +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + > > +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 > > +(try), uid 0: exited on signal 10 (core dumped) > > How can I detect where is the problem?? Have you added anything to the default system crontab? Are there any user crontabs? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 11:42 AM, Robert Huff wrote: > > C. L. Martinez writes: > >> I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I >> am receiving in security output this message: >> >> fbsd.domain.local kernel log messages: >> >> +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + >> >> +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid 76241 >> >> +(try), uid 0: exited on signal 10 (core dumped) >> >> How can I detect where is the problem?? > > Have you added anything to the default system crontab? Are > there any user crontabs? > > > Robert Huff > I have added a script to rebuild packages every week with poudriere: # /etc/crontab - root's crontab for FreeBSD # # $FreeBSD: release/9.1.0/etc/crontab 194170 2009-06-14 06:37:19Z brian $ # SHELL=/bin/sh PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin # #minute hourmdaymonth wdaywho command # */5 * * * * root/usr/libexec/atrun # # Save some entropy so that /dev/random can re-seed on boot. */11* * * * operator /usr/libexec/save-entropy # # Rotate log files every hour, if necessary. 0 * * * * rootnewsyslog # # Perform daily/weekly/monthly maintenance. 1 3 * * * rootperiodic daily 15 4 * * 6 rootperiodic weekly 30 5 1 * * rootperiodic monthly # # Adjust the time zone if the CMOS clock keeps local time, as opposed to # UTC time. See adjkerntz(8) for details. 1,310-5 * * * rootadjkerntz -a # # Rebuild all necessary packages for SIEM infrastructure 35 23 * * 4 root/root/bin/build_pkgs all ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Daily periodic cronjob generates core dump
C. L. Martinez writes: > > Have you added anything to the default system crontab? Are > > I have added a script to rebuild packages every week with poudriere: And if you comment that out? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 12:17 PM, Robert Huff wrote: > > C. L. Martinez writes: > >> > Have you added anything to the default system crontab? Are >> >> I have added a script to rebuild packages every week with poudriere: > > And if you comment that out? > > > Robert Huff > Uhmm .. I will try it ... but for what reason?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Daily periodic cronjob generates core dump
> > > Uhmm .. I will try it ... but for what reason?? > > It would be nice to see if anything else in the crontab might be causing it. You can also run `periodic security` as root and see if it manfiests the same way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Daily periodic cronjob generates core dump
On Fri, Jun 14, 2013 at 12:30 PM, Jason Birch wrote: >> >> Uhmm .. I will try it ... but for what reason?? >> > It would be nice to see if anything else in the crontab might be causing > it. > > You can also run `periodic security` as root and see if it manfiests the > same way. Running from console, no problem: root@fbsd:~ # periodic security Checking setuid files and devices: Checking negative group permissions: Checking for uids of 0: root 0 toor 0 Checking for passwordless accounts: Checking login.conf permissions: Checking for ports with mismatched checksums: fbsd.domain.local pf denied packets: +++ /tmp/security.NiYRT5WC 2013-06-14 12:44:34.0 + +block drop in log quick on ! lo0 inet from 127.0.0.0/8 to any [ Evaluations: 166898 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick on ! em0 inet from 172.16.0.0/24 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick inet from 172.16.0.109 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log quick on ! lo0 inet6 from ::1 to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop in log all [ Evaluations: 132328 Packets: 128574 Bytes: 12252183 States: 0 ] +block drop in log quick from to any [ Evaluations: 132328 Packets: 0 Bytes: 0 States: 0 ] +block drop out log quick from any to [ Evaluations: 166898 Packets: 0 Bytes: 0 States: 0 ] fbsd.domain.local login failures: fbsd.domain.local refused connections: -- End of security output -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Panic/reboot while trying to install 9.1 on a HP Proliant DL580G5
On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote: > Just guessing from what I see - > > The panic is "No usable event timer found!" > > . Hi Shane, Thanks much for the hints you sent me. Since I'm pretty swamped with work it took me a couple of days before I could go on with my tests. > Can you boot into single user mode? Nope - freezes at the exact same point during boot. > what does sysctl kern.eventtimer.choice show? Well - nothing to be honest: "variable 'kern.eventtimer.choice' not found" > Have you tried kern.eventtimer.periodic=0 or other values for > kern.eventtimer.timer? With "kern.eventtimer.periodic=0" - same result. What other values would be valid for "kern.eventtimer.timer"? > Is the panic the same without the loader adjustments? Yes, absolutely the same. > Does it boot 8.3 ? Haven't tried this, since I need to go to 9.1 on this system anyway. Besides that the server is in a remote DC so changing disks is not an easy thing to do. -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Daily periodic cronjob generates core dump
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/14/13 6:26 AM, C. L. Martinez wrote: > Hi all, > > I have a FreeBSD 9.1 host (fully patched) with ZFS. Every day I am > receiving in security output this message: > > fbsd.domain.local kernel log messages: > > +++ /tmp/security.AT1oDecp 2013-06-14 03:02:10.0 + > > +pid 75930 (try), uid 0: exited on signal 10 (core dumped) pid > 76241 > > +(try), uid 0: exited on signal 10 (core dumped) > > How can I detect where is the problem?? > > Thanks. You can safely ignore this message, as it's generated by autotools when you are building your packages with poudriere. See: http://lists.freebsd.org/pipermail/freebsd-questions/2010-February/213026.html Also check section 12.11.3 on this page for more details on suppressing the message: http://www.freebsd.org/doc/en/books/handbook/configtuning-configfiles.html Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG7LTMACgkQ0sRouByUApA/2ACeJ3lHSmx8/AyNMVHMJeesQ9nh nxgAn0S4nMRCKzTGrMAt8Z+lJsH8hMiT =NVU9 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Setting a lcoale globally
I would like to set the locale of my 9.1 server to LANG="en_US.ISO8859-1" globally, i.e., put the locale entry in one file, and then have the locale propagate as I go into other shells and run various scripts. I have spent some quality time with google, and the best I have been about to ascertain is that I need to sprinkle the LANG setting throughout the various ENV variables and .profile, .cshrc, .bashrc, and whatever files spread across my directory tree. That really seems counter-intuitive to me. Is it at all possible for me to specify in once place *somewhere" that the entire server is to use the locale setting LANG="en_US.ISO8859-1" ? I need a clue... thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
themerchantsolutions.com: You are now unsubscribed
** We have removed your email address from our list. We're sorry to see you go. Was this a mistake? Did you forward one of our emails to a friend, and they clicked the unsubscribe link not realizing they were in fact unsubscribing you from this list? If this was a mistake, you can re-subscribe at: Subscribe (http://blogspot.us6.list-manage.com/subscribe?u=37964f600b3d95d5cb34024a4&id=1bd9b49122) For questions or comments, please contact us at: cutt...@gmail.com (mailto:cutt...@gmail.com) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Setting a lcoale globally
On Fri, 14 Jun 2013 12:13:34 -0400, Mike. wrote: > I would like to set the locale of my 9.1 server to > >LANG="en_US.ISO8859-1" > > > globally, i.e., put the locale entry in one file, and then have the > locale propagate as I go into other shells and run various scripts. You can add this to /etc/csh.cshrc as it will be inherited by all interactive shells (login shells), unless of course they override it with ~/.cshrc: setenv LANG en_US.ISO8859-1 It's also possible to add it to /etc/profile and even make an addition to /etc/login.conf's "default" setting: default:\ :setenv=LANG=en_US.ISO8859-1:... ... I'm not fully sure about that, as I'm using a centralized con- figuration as suggested per /etc/csh.cshrc to have specific environment settings, shell configuration items and aliases _system-wide_ for all users. (Note that this might require your attention on system updates!) > I have spent some quality time with google, and the best I have been > about to ascertain is that I need to sprinkle the LANG setting > throughout the various ENV variables and .profile, .cshrc, .bashrc, and > whatever files spread across my directory tree. For _custom_ scripts, I would suggest to put that setting at the top of those scripts so they will make sure the correct $LANG is being set, independently from possible other users' values. > That really seems counter-intuitive to me. True. :-) > Is it at all possible for me to specify in once place *somewhere" that > the entire server is to use the locale setting LANG="en_US.ISO8859-1" ? >From my individual experience, adding it to the global C-Shell configuration works, but I can't predict that for your exact requirements. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Setting a lcoale globally
On Fri, Jun 14, 2013 at 12:13:34PM -0400, Mike. wrote: > > > I would like to set the locale of my 9.1 server to > >LANG="en_US.ISO8859-1" > > > globally, i.e., put the locale entry in one file, and then have the > locale propagate as I go into other shells and run various scripts. > > > I have spent some quality time with google, and the best I have been > about to ascertain is that I need to sprinkle the LANG setting > throughout the various ENV variables and .profile, .cshrc, .bashrc, and > whatever files spread across my directory tree. > > > That really seems counter-intuitive to me. > > > Is it at all possible for me to specify in once place *somewhere" that > the entire server is to use the locale setting LANG="en_US.ISO8859-1" ? > > I need a clue... > > > thanks. > > 24.3.3.1.1. Login Classes Method "This method allows environment variables needed for locale name and MIME character sets to be assigned once for every possible shell instead of adding specific shell assignments to each shell's startup file. User Level Setup can be performed by each user while Administrator Level Setup requires superuser privileges." Source: http://www.freebsd.org/doc/en/books/handbook/using-localization.html#login-class -- staticsafe O< ascii ribbon campaign - stop html mail - www.asciiribbon.org Please don't top post. Please don't CC! I'm subscribed to whatever list I just posted on. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Setting a locale globally
On 6/14/2013 at 9:12 PM Polytropon wrote: |On Fri, 14 Jun 2013 12:13:34 -0400, Mike. wrote: |> I would like to set the locale of my 9.1 server to |> |>LANG="en_US.ISO8859-1" |> |> |> globally, i.e., put the locale entry in one file, and then have the |> locale propagate as I go into other shells and run various scripts. | |You can add this to /etc/csh.cshrc as it will be inherited by |all interactive shells (login shells), unless of course they |override it with ~/.cshrc: | | setenv LANG en_US.ISO8859-1 That works for the login shell, but when I su to another user (e.g., root), LANG is no longer in the environment. | |It's also possible to add it to /etc/profile and even make an |addition to /etc/login.conf's "default" setting: | | default:\ | :setenv=LANG=en_US.ISO8859-1:... That works for the login shell, but when I su to another user (e.g., root), LANG is no longer in the environment. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Setting a locale globally
On Fri, 14 Jun 2013 15:54:06 -0400, Mike. wrote:
> On 6/14/2013 at 9:12 PM Polytropon wrote:
>
> |On Fri, 14 Jun 2013 12:13:34 -0400, Mike. wrote:
> |> I would like to set the locale of my 9.1 server to
> |>
> |>LANG="en_US.ISO8859-1"
> |>
> |>
> |> globally, i.e., put the locale entry in one file, and then have the
> |> locale propagate as I go into other shells and run various scripts.
> |
> |You can add this to /etc/csh.cshrc as it will be inherited by
> |all interactive shells (login shells), unless of course they
> |override it with ~/.cshrc:
> |
> | setenv LANG en_US.ISO8859-1
>
> That works for the login shell, but when I su to another user (e.g.,
> root), LANG is no longer in the environment.
That depends on _how_ you su. For example, if you use su -m,
the environment will not be modified, but the UID 0 is gained.
See "man su" for details.
But you are correct in terms of what I mentioned: If some
user-configuration changes or unsets $LANG, it will be gone,
and it may even be possible that the setting will not be
transmitted properly to a different shell ("inheriting
environment"), especially if the shell is not the default
login shell, but instead bash or zsh (when the setting is
being made for csh only).
> |It's also possible to add it to /etc/profile and even make an
> |addition to /etc/login.conf's "default" setting:
> |
> | default:\
> | :setenv=LANG=en_US.ISO8859-1:...
>
> That works for the login shell, but when I su to another user (e.g.,
> root), LANG is no longer in the environment.
Try su -m.
Anyway, login.conf should be the better solution compared
to the csh approach illustrated above. It should work
independently from the kind of shell.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Setting a locale globally
On Jun 14, 2013, at 1:51 PM, Polytropon wrote:
> On Fri, 14 Jun 2013 15:54:06 -0400, Mike. wrote:
>> On 6/14/2013 at 9:12 PM Polytropon wrote:
>>
>> |On Fri, 14 Jun 2013 12:13:34 -0400, Mike. wrote:
>> |> I would like to set the locale of my 9.1 server to
>> |>
>> |>LANG="en_US.ISO8859-1"
>> |>
>> |>
>> |> globally, i.e., put the locale entry in one file, and then have the
>> |> locale propagate as I go into other shells and run various scripts.
>> |
>> |You can add this to /etc/csh.cshrc as it will be inherited by
>> |all interactive shells (login shells), unless of course they
>> |override it with ~/.cshrc:
>> |
>> |setenv LANG en_US.ISO8859-1
>>
>> That works for the login shell, but when I su to another user (e.g.,
>> root), LANG is no longer in the environment.
>
> That depends on _how_ you su. For example, if you use su -m,
> the environment will not be modified, but the UID 0 is gained.
> See "man su" for details.
>
> But you are correct in terms of what I mentioned: If some
> user-configuration changes or unsets $LANG, it will be gone,
> and it may even be possible that the setting will not be
> transmitted properly to a different shell ("inheriting
> environment"), especially if the shell is not the default
> login shell, but instead bash or zsh (when the setting is
> being made for csh only).
>
>
>
>> |It's also possible to add it to /etc/profile and even make an
>> |addition to /etc/login.conf's "default" setting:
>> |
>> |default:\
>> |:setenv=LANG=en_US.ISO8859-1:...
>>
>> That works for the login shell, but when I su to another user (e.g.,
>> root), LANG is no longer in the environment.
>
> Try su -m.
>
> Anyway, login.conf should be the better solution compared
> to the csh approach illustrated above. It should work
> independently from the kind of shell.
>
Also, you can get the sudo(8) utility to preserve LANG by adding it to the
env_keep list in /usr/local/etc/sudoers
For example:
Step 1: (as root) visudo
Step 2: Find… (the default configuration)
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
Step 3: Un-comment the second line (of the two lines shown above).
Now whenever you use sudo(8) to execute a command, LANG (and a few others, like
LC_ALL) are preserved.
--
Devin
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Panic/reboot while trying to install 9.1 on a HP Proliant DL580G5
On 14/06/2013 23:33, Ewald Jenisch wrote: On Fri, Jun 07, 2013 at 10:41:01AM +0930, Shane Ambler wrote: Just guessing from what I see - The panic is "No usable event timer found!" I did say just guessing and thought someone more knowledgeable may have spoken by now. One thing I did find - there is a freebsd-proliant mailing list that may be more helpful than here. Thanks much for the hints you sent me. Since I'm pretty swamped with work it took me a couple of days before I could go on with my tests. Can you boot into single user mode? Nope - freezes at the exact same point during boot. what does sysctl kern.eventtimer.choice show? Well - nothing to be honest: "variable 'kern.eventtimer.choice' not found" Wondering if the system needs to be running to see that. Have you tried kern.eventtimer.periodic=0 or other values for kern.eventtimer.timer? With "kern.eventtimer.periodic=0" - same result. What other values would be valid for "kern.eventtimer.timer"? That's where the eventtimer.choice comes in. As an example on my asus mb I get kern.eventtimer.choice: LAPIC(600) HPET(550) HPET1(440) HPET2(440) HPET3(440) HPET4(440) i8254(100) RTC(0) I thought in single user mode you could see your list of available options. Is the panic the same without the loader adjustments? Yes, absolutely the same. Does it boot 8.3 ? Haven't tried this, since I need to go to 9.1 on this system anyway. Besides that the server is in a remote DC so changing disks is not an easy thing to do. If 8.3 boots it then you can patch and compile your own kernel that supports your hardware. Being remote it may not be helpful unless you can have some indication that it will boot 8.3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
