custom iso with /etc/src.conf
Hi all, I know I can build custom iso with make release but this is my question: In order to get some custom build, e.g. for jails, I used to write some things to /etc/src.conf for not installing / compiling some software (games, daemons etc), so my jail is really thin. But now, I would REALLY love to make this jail system as default bsd system which I can install to pc from installer, which would be at iso. Well, this would not be just like jail, there would be kernel as well and so on ... From what I know, there are several stages in make release, from release(7) I see that release: Uses ``make installworld'' to install a clean system into a chroot(8) environment on the file system. Checks out the specified version of the source code and then rebuilds the entire system in the clean environment with ``make buildworld''. The detailed steps that follow are then executed to package up the different distributions, build the installation floppy disks, build release documenta- tion, and so on. I have cvs repository localy installed in /home/ncvs. But, if I compile it (/usr/src with /etc/src.conf) and than make release, it will fail because even I install it, it fails to buildworld in make release stage, because I have not make + compiler toolchain and other things in that clean system after installworld. So my question is, how to make it in that way, that I make release, full system is installed to chroot and than system suitable for my needs (/etc/src.conf options what to compile and what not) is build and isos are made. Thank you very much Stefan Miklosovic ___ 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
acroread9 - kernel module load error
Hello Installed this port but the kernel won't load and produces the following error: think# /usr/local/etc/rc.d/linux_adobe start kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec format error /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel module /usr/local/libexec/linux_adobe/linux_adobe.ko Has anyone else experienced this? Does anyone have any suggestions to fix it? best wishes jamie ___ 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
Critical issues with WD green drives
Hello. In a server of mine (7.3p4/i386) I replaced a 1TB Hitachi SATA drive (which worked perfectly), with two brand new Western Digital 2TB disks. Now I'm having critical problems, ranging from the disks getting stuck, to the box rebooting. Those are not the main disks in the box, so they are currently unmounted; I wasn't even able to run newfs on them, since every process that tries to use these disk will hang after a while (and can't be killed either). The box is based on an Intel S5000 motherboard and the drives are attached on the MB in an hot-swap enclosure. First, what I think might be the relevant part of dmesg: FreeBSD 7.3-RELEASE-p4 #1: Wed Dec 15 11:53:13 CET 2010 r...@x..xx:/usr/obj/usr/src/sys/X i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5405 @ 2.00GHz (2004.99-MHz 686-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce33dSSE3,DTES64,MON,DS_CPL,VMX,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 4 real memory = 2143289344 (2044 MB) avail memory = 2090176512 (1993 MB) ACPI APIC Table: INTEL S5000PSL FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs ... acpi0: INTEL S5000PSL on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 acpi_button0: Sleep Button on acpi0 acpi_button1: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xca2,0xca3,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci2 pci3: ACPI PCI bus on pcib3 pcib4: PCI-PCI bridge at device 0.0 on pci3 pci4: PCI bus on pcib4 ... pcib5: PCI-PCI bridge at device 0.2 on pci3 pci5: PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge irq 18 at device 2.0 on pci2 pci6: ACPI PCI bus on pcib6 ... pcib7: ACPI PCI-PCI bridge at device 0.3 on pci1 pci7: ACPI PCI bus on pcib7 ... pcib8: PCI-PCI bridge at device 3.0 on pci0 pci8: PCI bus on pcib8 pcib9: ACPI PCI-PCI bridge at device 4.0 on pci0 pci9: ACPI PCI bus on pcib9 pcib10: ACPI PCI-PCI bridge at device 5.0 on pci0 pci10: ACPI PCI bus on pcib10 pcib11: ACPI PCI-PCI bridge at device 6.0 on pci0 pci11: ACPI PCI bus on pcib11 pcib12: PCI-PCI bridge at device 7.0 on pci0 pci12: PCI bus on pcib12 pci0: base peripheral at device 8.0 (no driver attached) pcib13: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci13: ACPI PCI bus on pcib13 ... pcib14: ACPI PCI-PCI bridge at device 30.0 on pci0 pci14: ACPI PCI bus on pcib14 ... atapci1: Intel 63XXESB2 SATA300 controller port 0x40d8-0x40df,0x40f4-0x40f7,0x40d0-0x40d7,0x40f0-0x40f3,0x4020-0x403f mem 0xb900-0xb90003ff irq 20 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI called from vendor specific driver atapci1: AHCI Version 01.10 controller with 6 ports detected ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 ata3: [ITHREAD] ata4: ATA channel 2 on atapci1 ata4: [ITHREAD] ata5: ATA channel 3 on atapci1 ata5: [ITHREAD] ata6: ATA channel 4 on atapci1 ata6: [ITHREAD] ata7: ATA channel 5 on atapci1 ata7: [ITHREAD] ... ad4: 1907729MB WDC WD20EARS-00MVWB0 51.0AB51 at ata2-master SATA300 ad8: 1907729MB WDC WD20EARS-00MVWB0 51.0AB51 at ata4-master SATA300 ... GEOM_STRIPE: Device backup created (id=912470894). GEOM_STRIPE: Disk ad4 attached to backup. GEOM_STRIPE: Disk ad8 attached to backup. GEOM_STRIPE: Device backup activated. ... Following are some samples of the messages I get in the logs: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SMART taskqueue timeout - completing request directly ad8: WARNING - SMART taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue
acroread9 - kernel module load error
Jamie Paul Griffin writes: Installed this port but the kernel won't load and produces the following error: think# /usr/local/etc/rc.d/linux_adobe start kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec format error /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel module /usr/local/libexec/linux_adobe/linux_adobe.ko Has anyone else experienced this? Does anyone have any suggestions to fix it? It means your kernel and kernel sources are not in sync. The solution is to (re-)build the kernel and program using the same source tree. 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: acroread9 - kernel module load error
On Thu, Jun 02, 2011 at 08:23:22AM -0400, Robert Huff wrote: Jamie Paul Griffin writes: Installed this port but the kernel won't load and produces the following error: think# /usr/local/etc/rc.d/linux_adobe start kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec format error /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel module /usr/local/libexec/linux_adobe/linux_adobe.ko Has anyone else experienced this? Does anyone have any suggestions to fix it? It means your kernel and kernel sources are not in sync. The solution is to (re-)build the kernel and program using the same source tree. ok, thanks for the info. ___ 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: Install ImageMagick configured with Autotrace switch
On Wed, 1 Jun 2011, Angelo wrote:
Thanks Peter but I can't seem to build this thing.
Please don't top-post, and please trim responses.
I've tried just about everything I can think of to pass the argument
--with-autotrace and it throws exceptions or just ignores the command.
Patching the ImageMagick Makefile is not too bad:
--- graphics/ImageMagick/Makefile.orig 2011-06-02 08:13:35.0 -0600
+++ graphics/ImageMagick/Makefile 2011-06-02 08:22:51.0 -0600
@@ -40,6 +40,7 @@
OPTIONS=\
IMAGEMAGICK_16BIT_PIXEL 16bit pixel support on \
+ IMAGEMAGICK_AUTOTRACE Autotrace support off \
IMAGEMAGICK_BZLIB Bzlib support on \
IMAGEMAGICK_DJVUDJVU format support (needs threads) off \
IMAGEMAGICK_DOT GraphViz dot graphs support off \
@@ -228,6 +229,11 @@
CONFIGURE_ARGS+= --without-fftw
.endif
+.if defined(WITH_IMAGEMAGICK_AUTOTRACE)
+LIB_DEPENDS+= autotrace:${PORTSDIR}/graphics/autotrace
+CONFIGURE_ARGS+=--with-autotrace
+.endif
+
# Produce BZip compressed MIFF images
.if defined(WITHOUT_IMAGEMAGICK_BZLIB)
CONFIGURE_ARGS+= --without-bzlib
And that seems to produce a working ImageMagick, at least one that can
convert jpeg to svg. There may be correctness issues, like whether
autotrace requires other ImageMagick options to be enabled (like SVG).
The problem is that autotrace depends on ImageMagick, and the patched
ImageMagick now depends on autotrace. I don't know enough about either
port to fix that. Hopefully someone can, because this seems like a
useful addition.
___
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: src upgrading jails (no ezjail, no service jails)
On Wed, Jun 1, 2011 at 4:44 PM, Greg Larkin glar...@freebsd.org wrote: Those commands will update the base system in the jail directory jaildir1 with the latest bits that were previously compiled with make buildworld. don't believe they will disturb any other data in /usr/local, if that's what you are concerned about. Yeah, I ran it and it mostly worked, although running mergemaster -p -D /path/to/jail before installworld didn't really back up files like it normally does, but I was able to pull the most recent backup and fix that. I use ezjail here, and it will automate a lot of these steps for you. Is there a reason that you can't use it? I didn't create these jails with ezjails, so I was working under the impression that I could not use ezjail to upgrade them. Is that not correct? Alex ___ 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: acroread9 - kernel module load error
On Thu, Jun 02, 2011 at 08:23:22AM -0400, Robert Huff wrote: Jamie Paul Griffin writes: Installed this port but the kernel won't load and produces the following error: think# /usr/local/etc/rc.d/linux_adobe start kldload: can't load /usr/local/libexec/linux_adobe/linux_adobe.ko: Exec format error /usr/local/etc/rc.d/linux_adobe: WARNING: Unable to load kernel module /usr/local/libexec/linux_adobe/linux_adobe.ko Has anyone else experienced this? Does anyone have any suggestions to fix it? It means your kernel and kernel sources are not in sync. The solution is to (re-)build the kernel and program using the same source tree. ok, i've just been through make buildworld, etc. and rebuilt the port but still the same problem? ___ 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: Critical issues with WD green drives
On 06/02/11 18:02, Reid Linnemann wrote: I've gotten similar errors before with a failing power supply. After an electrical storm I started getting HD errors all over the place. I replaced drives, futzed with SATA cables, booted, rebooted, and when the machine got stable finally I just tried to leave it alone. Finally I bought a new atom board, thinking that some component on the mainboard had been killed by the storm. Problems persisted until my mini-itx case came in with a fresh (less powerful) power supply. Thanks, but in my case this is unlikely. I have reduntant power supplies and 4 SAS drives which work flawlessly. Only the two SATA have problems. bye Thanks av. ___ 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: Critical issues with WD green drives
On Thu, Jun 2, 2011 at 9:54 AM, Bruce Cran br...@cran.org.uk wrote: On Thu, 02 Jun 2011 14:16:01 +0200 Andrea Venturoli m...@netfence.it wrote: In a server of mine (7.3p4/i386) I replaced a 1TB Hitachi SATA drive (which worked perfectly), with two brand new Western Digital 2TB disks. Now I'm having critical problems, ranging from the disks getting stuck, to the box rebooting. Those are not the main disks in the box, so they are currently unmounted; I wasn't even able to run newfs on them, since every process that tries to use these disk will hang after a while (and can't be killed either). I'd guess this is probably due to their overly-aggressive power management. If you can, run wdidle3.exe from a Windows environment to turn off the default idle timer. -- Bruce Cran ___ 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 I've gotten similar errors before with a failing power supply. After an electrical storm I started getting HD errors all over the place. I replaced drives, futzed with SATA cables, booted, rebooted, and when the machine got stable finally I just tried to leave it alone. Finally I bought a new atom board, thinking that some component on the mainboard had been killed by the storm. Problems persisted until my mini-itx case came in with a fresh (less powerful) power supply. ___ 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: Critical issues with WD green drives
--- On Thu, 6/2/11, Reid Linnemann lr...@cs.okstate.edu wrote: From: Reid Linnemann lr...@cs.okstate.edu Subject: Re: Critical issues with WD green drives To: Bruce Cran br...@cran.org.uk Cc: freebsd-questions@freebsd.org Date: Thursday, June 2, 2011, 11:02 AM On Thu, Jun 2, 2011 at 9:54 AM, Bruce Cran br...@cran.org.uk wrote: On Thu, 02 Jun 2011 14:16:01 +0200 Andrea Venturoli m...@netfence.it wrote: In a server of mine (7.3p4/i386) I replaced a 1TB Hitachi SATA drive (which worked perfectly), with two brand new Western Digital 2TB disks. Now I'm having critical problems, ranging from the disks getting stuck, to the box rebooting. Those are not the main disks in the box, so they are currently unmounted; I wasn't even able to run newfs on them, since every process that tries to use these disk will hang after a while (and can't be killed either). I'd guess this is probably due to their overly-aggressive power management. If you can, run wdidle3.exe from a Windows environment to turn off the default idle timer. -- Bruce Cran ___ 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 I've gotten similar errors before with a failing power supply. After an electrical storm I started getting HD errors all over the place. I replaced drives, futzed with SATA cables, booted, rebooted, and when the machine got stable finally I just tried to leave it alone. Finally I bought a new atom board, thinking that some component on the mainboard had been killed by the storm. Problems persisted until my mini-itx case came in with a fresh (less powerful) power supply. My duh moment not too long ago. I found that the sata power adapters had pins that were to small for a proper connection to the power supply. ___ 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
FreeBSD Questions off line?
Aloha, I havent seen any FreeBSD questions on line for 2 days. Any body have any knowledge about this? ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Questions off line?
On Thu, Jun 2, 2011 at 4:01 PM, Al Plant n...@hdk5.net wrote: Aloha, I havent seen any FreeBSD questions on line for 2 days. Any body have any knowledge about this? Well, it's not offline, your mail came though just fine ... maybe no one has sent anything? -- A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD Questions off line?
The archives show 30+ messages yesterday and today. http://lists.freebsd.org/pipermail/freebsd-questions/2011-June/date.html Check your mail server, your subscription, etc. -- Noel Jones On 6/2/2011 3:01 PM, Al Plant wrote: Aloha, I havent seen any FreeBSD questions on line for 2 days. Any body have any knowledge about this? ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ 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 ___ 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: acroread9 - kernel module load error
On Thu, 2 Jun 2011 23:43:51 +0200, Patrick Lamaiziere patf...@davenulle.org wrote: We need a kernel module to see some pdf with acrobat now? I was thinking exactly the same (without further investigation). Luckily xpdf and gv, as well as Gnome's and KDE's PDF viewer don't need kernel modules. :-) -- 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: acroread9 - kernel module load error
Polytropon free...@edvax.de wrote: On Thu, 2 Jun 2011 23:43:51 +0200, Patrick Lamaiziere patf...@davenulle.org wrote: We need a kernel module to see some pdf with acrobat now? I was thinking exactly the same (without further investigation). I suspect it's because FreeBSD uses Linux Acroread, so we need the Linuxulator, plus (I suppose) an additional API or 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
Re: Building misc/freebsd-doc-en fails
On Sun, May 29, 2011 at 02:32:37PM +, Joe Altman wrote: There is this thread from 2009, and it looks like the same issue as the one in this message: http://lists.freebsd.org/pipermail/freebsd-questions/2009-December/209892.html It looks like I'll need to open a bug report with the Doc project team. After reading the thread referenced above, and looking at the output of my build, I noticed that the build was failing in different areas. So I decided to run make on the port multiple times, and eventually the port installed successfully. However, the port in my tree (dated # $FreeBSD: ports/misc/freebsd-doc-en/Makefile,v 1.36 2011/05/22 14:28:49 blackend Exp $) in a fresh tree made only through 2010, according to the copyright at the top of the handbook. Individual files in that doc tree were variously dated; the newest being 8/2010. So I ran make, multiple times, on the source; and that gave me a doc tree dated 2011. Most of the files there were dated 5/29/11. A few exceptions were found in image files dated 3/2010, which all loaded in SeaMonkey, except for some files in: advanced-networking, security, vinum, geom. I may have missed others in other books. To summarize: 1) It appears that make is, in this case, a hammer that must be applied more than once to either the source or the port. 2) Not all images are seen as valid, and according to make may have bad magic numbers. If building from source is used on a fresh tree, it may be possible to have make ignore all the errors by using the -k flag. 3) I have no idea how things will go with an upgrade to the doc source; I normally use portupgrade, so I suppose I will find out later. I've submitted a bug report. Best regards, Joe Hi, This might not be the same as an issue I had because I'm not really sure how the docs are built. I did not have doc in my cvs supfile at first. I have the following in my cvs supfile: src-all ports-all tag=. doc-all tag=. And my issue went away if I remember correctly. Regards, Mike ___ 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
