Re: 486 Install??
Thomas F Simpson Jr wrote: I have a 486 DEEP GREEN system I would like to put some version of FreeBSD on (I have my reasons). I have other inquiries out on this, but if I correctly recall (and that is a real rusty recall at best), the max memory you could get on one of these beasts was 48MB, unless they made some bigger, recognizable, 72-pin modules. I have 8 MB of hard drive space free for a FreeBSD partition and I am actually running an Intel P24T Overdrive for my CPU. All work fine on the DOS 6.2.2 partition I need to run. Would any version of FreeBSD work with just 48MB of RAM? Or do I need to figure out a way to get more RAM on the board, IF POSSIBLE? Go for 4.x series. You can find it on ftp-archive.freebsd.org. Trying to pump 6.x or 7.x on that hardware is equal to masohism. -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrade 5.4 to 7 ????
Fraser Tweedale wrote: Full backup should be considered -essential-. You are crazy not to do it. If you take the build-from-source route, upgrade to the latest release from each major branch before upgrading to the newer version, as this is the most tested upgrade path. i.e., since you're running 5.4, upgrade to 5.5, then to 6.3, then to 7.0. That is my recommendation anyway. Hi there, just wanted to bump to this and confirm from live production example that this is very clean way to upgrade. For me it was: 5.0 in startup install then 5.4, then 6.0 then 6.1, 6.2 was last 6.x, followed by upgrade to 7.0. A complete rebuild order was followed thru all upgrade processes: 1. world 2. kernel (having in mind COMPAT_XY for prior major release) 3. ports Have in mind that you will need occasional reboots between those steps to make sure you can identify eventual problems, so have everything backed up. Hot spare host with identical content worked for me, but the standard backup with dump(8) can work too. YMMV Also having physical access or serial console might be very useful things to have if you are working on remote. -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kldload: exec format error on newly built GENERIC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Franks wrote: | I just added a device driver source file to the appropriate location | and rebuilt: | | dystant# cd /usr/src | dystant# make buildkernel KERNCONF=GENERIC | ... | dystant# make installkernel KERNCONF=GENERIC | dystant# init 6 | ... | [EMAIL PROTECTED] /usr/home/steve]$ sudo kldload ucp | kldload: can't load ucp: Exec format error | | ??? What am I doing wrong? | You are using some 3rd party driver for freebsd. Just like you got new kernel, get new driver for it. wtf is ucp anyway? cba to check google :/ - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfVowEACgkQo6C4vAhYtCAEYgCfXArpJL7ncCrDa2DcqCVdmiGt KD0An3RM+cmLore6XMxCrdsBytTTVMbX =x6yC -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: It is safe to build ports for 7.0 from a 6.3 chroot?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mel wrote: | | Minimize downtime of services provided by ports? | | Jose: take a look at Tinderbox - it does exactly what you want to do: build | ports for OS release X on OS release Y, using chroot. If you're unsure about | your own method, because of OSVERSION or similar, do it using Tinderbox. | IMHO, the usual procedure described in handbook will satisfy 95% of upgrade scenarios. Others can install compat6x port right after (or before) reboot. In any case, be free to try whatever scenario works for you, but I would ~ not like to be the one who inherits server with such 'messy-upgrade' :| - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfNO3kACgkQo6C4vAhYtCBl3wCeKyRqqDZP/gwpu77c4+stVFal FPsAn03vkueNmyMHISoVa87NEYMzmTQo =l7iW -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: It is safe to build ports for 7.0 from a 6.3 chroot?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mel wrote: | | Just cause it doesn't fall into your 95% slice, doesn't make it messy. It's in | fact cleaner then using compat6x, *because* compat6x doesn't fall into the | category of potential causes when things don't work. | FYI: tinderbox is based on the pointyhat build cluster, which makes all | the 'messy' packages for the FreeBSD package servers. | I will stop discussion right here, because it has tendency to bring out endless flame of you-know-what-about. Starter of this thread didn't even mention what services he is running and just by that is pointless to discuss about approaches in upgrade of anything. Hats off to tinderbox or however binary packages are made, but that has nothing to do on how to upgrade freebsd system. - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfNV/oACgkQo6C4vAhYtCCi7wCbBhCk7uphbo1vqK9CDxnGYx7S XycAniBYNk/QR6sUJkbBbMnCbNOZBRO1 =GXvR -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: It is safe to build ports for 7.0 from a 6.3 chroot?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jose Garcia Juanino wrote: | Hi everybody | | Actually, I do the following in order to update from 6.3 to 7.0: | | 1) dump my actual 6.3 filesystems /, /var and /usr into three new | ones: /rel70, /rel70/usr and /rel70/var (I use the dump command, of | course) | | 2) chroot /rel70 and mergemaster -p + buildkernel + buildworld + | installkernel + installworld + mergemaster -i and such stuff | | 3) Inside the chroot, rebuild the ports | | 4) Reboot the new release | | | Will I go into problems following this approach? The step 3) is the most | dangerous, I believe, as I have executing 7.0 commands on a 6.3 kernel | (even though only for compilation). 0) Do I need to reinvent wheel? Joke off. Really, why would you try alternate way of upgrading, when there's straight way to do it? - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfMnD0ACgkQo6C4vAhYtCDrTwCgoHSPgIoGgltE2plO4JsQ5Bb/ R50An3hFeeBfcNIyHlRD9za8lLnI3t0v =ZGrK -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: So How Hard Is Moving From 6.3 To 7.0?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Daneliuk wrote: | I have a stable 6.3 production server. I would stop right there. Question is why would you change something that simply works? - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfKic4ACgkQo6C4vAhYtCBqKwCeOCybASwKMu4HV7oTeJRmaeUa eiEAnjyKaPVDYXv/aiNIqeQQx+bbbhtO =Fxf9 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fix make on old 4.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mailing List wrote: | Hello, | | I have an old freebsd server with 4.7 and I can't add any software cause | make is broke. Any time I try to install software I get an error because | make/ports/whatever is so far out-of-date. I tried the EOL port-supfile | but I don't know what cvsup server still has them. Anyway, it there any | other way to fix 'make' and be able to install software? Thanks. | | J. Hi, simply try 4.11-RELEASE ports.tgz ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/4.11-RELEASE/ports/ports.tgz I doubt that any newer ports will work on that historic release. - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfJKlAACgkQo6C4vAhYtCB+cgCeL8L2Zb9TTYJahNYW2VMUOZv8 JcYAn11q6ATEjbVVBtJxuqSm/SSA1kdN =HL1Z -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using ZFS on FreeBSD 7.0
Joe S wrote: Thanks Dan. That answered my question. I'm really happy to replace Solaris with FreeBSD. All I have to do is import my zfs pool and then upgrade it...2 commands! That reminds me to ask, can you do it? Importing pools from solaris to freebsd or vice versa. -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Performance Issues on 6.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Natham wrote: | I dont. i check the performance for network trasfer only thats what i | mean (trought samba). When im rebuilding the RAID 1 i got about 40mb/s | from each disk. | I think its a network issue or samba, but i dont know where to look at. | Try with other services. Can you test network performance with some httpd or ftpd? - -- Best regards, Bogdan Culibrk [EMAIL PROTECTED] http://default.co.yu/~bc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfFCVUACgkQo6C4vAhYtCAqDgCgocwHOTTIZn/YlJ1sGdwfz6c0 UWcAnRMnkYhHbCWzgWN+y//2ERZzqma6 =LIR4 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gmirror on slice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Gerzo wrote:
| Hello people,
|
| I'm trying to set up a gmirror on two slices, but I am stuck
| somewhere. I am unable to find out what is wrong. Here's what I have
| done so far:
|
| I have 2 disks in the box. I have created 2 slices on both of them
| (ad{4,6}s1 and ad{4,6}s2) through sysinstall. (btw,
| http://www.freebsd.org/cgi/query-pr.cgi?pr=72895cat= is really
| annoying, lucky I had a remote console :-))
|
| Now I want to initialize gmirror on slice 1:
|
| ha-db1# gmirror label -v -b round-robin gm0 /dev/ad4s1
| gmirror: Can't store metadata on /dev/ad4s1: Operation not permitted.
| ha-db1# sysctl kern.geom.debugflags=16
| kern.geom.debugflags: 0 - 16
| ha-db1# gmirror label -v -b round-robin gm0 /dev/ad4s1
| gmirror: Can't store metadata on /dev/ad4s1: Operation not permitted.
|
| for additional information, I am including the following:
|
| ha-db1# fdisk -vp ad4
| # /dev/ad4
| g c1453521 h16 s63
| p 1 0xa5 63 72340632
| a 1
| p 2 0xa5 72340695 1392803370
|
| ha-db1# disklabel /dev/ad4s1
| # /dev/ad4s1:
| 8 partitions:
| #size offsetfstype [fsize bsize bps/cpg]
| a: 104857604.2BSD 2048 16384 8
| b: 25165824 1048576 swap
| c: 723406320unused0 0 # raw part,
don't edit
| d: 25165824 262144004.2BSD 2048 16384 28528
| e: 20960408 513802244.2BSD 2048 16384 28528
|
|
| Any ideas will be much appreciated.
|
Hi there,
sysinstall is piece of crap when it comes to gmirror'ing slices.
I recall that I had numerous problems with it and that I couldn't find
any solution nor workaround but doing slicing by hand.
Have serial console handy if you don't have physical access to the system.
I hope this 2857574857th whine about bugs in sysinstall will reach to
someone capable of fixing it.
- --
Best regards,
Bogdan Culibrk
[EMAIL PROTECTED] http://default.co.yu/~bc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkfBgl0ACgkQo6C4vAhYtCATQQCfbHB8pp29ExUSPLlrEjz/5HSE
H2cAn2YgErKzd4reBOcFGQZaDdZUsOEB
=Ui3B
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Default named issues in FreeBSD-6.2:Any hints most welcome
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dhaneshk k wrote: | | People: i have a strange issue with named services in my freeBSD-6.2-Release Box | | | (I have installed the OS from the ISO image from which I installed another box there named is running fine , but unfortunately in this box its not running ), I can't trace it what went wrong ? | | Named is not starting , named forcestart I tried but no use , | | later I found that ther is no executables as /usr/sbin/named | | rndc also not found | | whats went wrong with this box ?all named dirs files there but no /usr/sbin/named executables : | | | So how can I rebuild/reinstall this named services in this FreeBSd6.2 box , | | Expecting your valuable comments to fix this issue : | | | thanks in advance | Dhanesh | | | The following informations may be useful for you to judge whats wrong with my installation | | | [EMAIL PROTECTED] /usr/sbin]# find / -name named [...] | /usr/sbin/named.reconfig | /usr/sbin/named.reload Hi there, I'm not sure what kind of third party software of administrator you have there, but seems to me that your named binary is missing. However you can reinstall your binary from source tree located in: /usr/src/usr.sbin/named -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke5dxoACgkQo6C4vAhYtCCWfgCfQv4VWZYw1rySGIwcI1Uis1xA cL4AniojXemkoPH8Ylz1QC+n3nFlePhi =StWc -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PHP cli segfaults
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Drew Sanford wrote: | Hi, | do you use precompiled port or you built your own? | | Built from ports, as opposed to using a binary package, if that's what | you're asking. Hi, same thing happened to me couple of times and caused by: 1. Userland and kernel was out of sync 2. Dependencies that PHP relies on were cause of segfaults. Recursive portupgrade helps. 3. Messing with libmap.conf or CFLAGS, don't use -pthread nor high optimization flags. It's really hard to tell out of the bloom what might be causing it, but that's the price you need to pay if you are tracking unstable branch. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke5i1UACgkQo6C4vAhYtCAu7ACffvs4sxfGnewYFfOmEqQW4+AW 7fgAnjJt3lWZio6e+J5t+39bIbf653En =GIYe -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: issues with serial console output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthias Kellermann wrote: | Hi list, | | I'm trying to install a FreeBSD system on a remote server I can only | access via a serial console with 57600 baud. | | There is a Linux rescue system that I use for copying a FreeBSD HDD | image via dd to the harddisk. | | To access the FreeBSD installation via remote serial console I've done | the following things: | | /boot/loader.conf: | console=vidconsole,comconsole | boot_multicons=YES | comconsole_speed=57600 | | /boot.config: | -S57600 -Dh | | /etc/ttys: | # only changed the following line | ttyd0 /usr/libexec/getty std.57600 vt100 on secure | | I can see the loader and can choose between the different choices to | boot. After choosing the default entry all I get is this: | | /boot/kernel/acpi.ko text=0x44a7c data=0x24c0+0x1b8c | syms=[0x4+0x7d50+0x4+0xaae0] | lots of lines of question marks | | I don't get a login prompt nor the kernel messages. The console does not | response on my keyboard. Any ideas whats wrong? | | Matthias | Hi there, try using standard (also minimal) way, and that's 1. unplug your keyboard/monitor (if any) 2. -P in /boot.config 3. std.9600 in your /etc/ttys That worked for me dozens of times. It also gives you flexibility in case you decide to use keyboard/monitor at some point in future. Hope that helps -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke4+G8ACgkQo6C4vAhYtCBVjwCZAQ8d8YXKfBYmojSetVedrlQr XxcAnRlFQVkm9t3kEnFcrGklh0+Rdpha =c661 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PHP cli segfaults
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Drew Sanford wrote: | Command line programs for php seem to segfault on a 7.0RC1 box (yes, I | know, I should update to RC2) - for example: | | [EMAIL PROTECTED](~/bin)$ php -v | PHP 5.2.5 with Suhosin-Patch 0.9.6.2 (cli) (built: Feb 9 2008 13:03:20) | Copyright (c) 1997-2007 The PHP Group | Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies | zsh: segmentation fault (core dumped) php -v | | Any pointers? Just update and see if that fixes it? Thanks in advance. | | | uname output: | FreeBSD colossus.cotharyus.net 7.0-RC1 FreeBSD 7.0-RC1 #0: Sat Feb 9 | 11:43:37 CST 2008 Hi, do you use precompiled port or you built your own? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAke49TUACgkQo6C4vAhYtCDrYwCdFF5CzPr2D9f7bSYJR9kwY3fP v44AnitccXGi4uQQpbKyzmFdjjLCwpPn =aL8h -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
