similar to: Booting from ZIP 750 ...

Hi, hackers : Yesterday night and this morning, I cvsup my system to latest STABLE branch source (RELENG_4). All make buildworld, buildkernel, and installkernel procedure was completed with no error. But when I boot into single user mode and try to make installworld, I always got " touch: not found " error. Does anyone encounter this situation ? I have no idea about that. :-( Here is

Hello, I have an amd64 laptop on which I did a fresh csup to RELENG_7. I did the canonical "buildworld", "buildkernel", "installkernel" and so far so good. However, when I attempt to "installworld", I get: ===> share/syscons/scrnmaps (install) ./armscii8-2haik8.mk armscii8-2haik8.tmp uuencode armscii8-2haik8.tmp armscii8-2haik8 >

Hello, I installed 4.8-RELEASE a few weeks ago, and since I let the effort sit stagnant for a while I decided to do the cvsup/buildworld/buildkernel/installkernel/installworld/mergemaster/MAKEDEV steps to get current. Went fine, rebooted, then noticed that just one CPU was recognized: FreeBSD 4.8-STABLE #0: Thu Jun 19 17:05:20 PDT 2003

David gave me some suggestions to check out on the servers, but so far, its all drawing a blank ... I have two servers right now that are updated to recent 4.8-STABLE kernels ... one was June 22nd, and the other was upgraded June 20th ... both of them have crashed since that date, and both of them tell me that they are unable to produce a core file, with the same errors: Jun 26 04:27:14 jupiter

# HG changeset patch # User Zhigang Wang <zhigang.x.wang@oracle.com> # Date 1342720736 14400 # Node ID ec9655b30a5fa5b5abb3e05505f681f9be559613 # Parent 43e21ce7f22151524b800a6cf0ac4ba1233b34a7 pygrub: add syslog support to pygrub Currently, when pygrub failed, we don''t know the reason because xend/xl will not capture the stderr message. This patch will log the error message to

hi to all FreeBSD user. i have a problem about updating from 4.8-RELEASED to 4.8-STABLE, here's exactly what i did: first: cvsup -g -L 2 stable-supfile, where my stable-supfile is located at /root. 2nd: cd /usr/src; make buildworld; make buildkernel KERNCONF=BUFDAEMON; make installkernel KERNCONF=BUFDAEMON 3rd: reboot; mergemaster -p; make installworld; mergemaster; reboot. after

I'm currently administering a machine about 1500mi from me with nobody local to the machine to assist me. Anyways, my only access to this machine is via SSH, no remote serial console or anything. When I try to do a "make installworld" I end up with install: rename: /lib/INS@aTxk to /lib/libcrypt.so.3: Operation not permitted very shortly thereafter. I cannot boot

hi all. it was happened that i have no upgrade my system long time. Before that i used for upgrading "classic" way. make buildworld make buildkernel make installkernel mergemaster make installworld But in current moment as i can see the upgrading is totally changed. As i understand commands sequence is next: #freebsd-update fetch #freebsd-update install #freebsd-update upgrade -r

Apparently I should of posted this here instead of in -questions, so here goes:- Hi I cvsup'ed the latest source on Saturday night at 9pm as I do every night onto my dev box this was then extracted in to my source tree and a new world built and new kernels for all my systems. On Sunday I performed a "make installkernel" followed by a "make installworld" and finally a

Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under

Dear folks, I'm recently investigating large scale deployment and upgrading FreeBSD RELEASE. It's our tradition to bump "RELEASE-pN" after a security patch is applied, however, it seems that there is less method to determine whether the userland is patched, which is somewhat important for large site managements. So is "uname -sr" the only way to differencate the

HI, i have updatete to 6.1-PRERELEASE and after the "installworld" step GRUB is unable to boot FreeBSD. After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no

hi guys, i have version 4.8-STABLE running. i've just update my stable-supfile and building, recompiling my custom kernel, my question is: if im going to cvsup my stable-supfile again, and compile the customed kernel again, do i have to: make buildworld, make installworld, mergemaster again or just make buildkernel KERNCONF & make install KERNCONF? hoping for your reply guys, thanks.

kfree() handles NULL pointers fine - checking is redundant. Signed-off-by: Jesper Juhl <juhl-lkml at dif.dk> --- linux-2.6.12-rc1-mm3-orig/fs/ext3/acl.c 2005-03-02 08:37:55.000000000 +0100 +++ linux-2.6.12-rc1-mm3/fs/ext3/acl.c 2005-03-25 22:41:41.000000000 +0100 @@ -197,8 +197,7 @@ ext3_get_acl(struct inode *inode, int ty acl = NULL; else acl = ERR_PTR(retval); - if (value) -

Hello, I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: cd /usr/src make buildworld make buildkernel KERNCONF=BLACK make installkernel KERNCONF=BLACK At this point I can reboot and all is good. After boot I install the new world: cd /usr/src mergemaster -p reboot into single user mode cd /usr/src make

Well, 4 days after previous upgrade i cvs'ed RELENG_4 from local cvs tree (updated hourly), made buildworld buildkernel installkernel, rebooted into single user, made installworld and mergemaster. Mergemaster updated newsyslog.conf, syslogd.conf, ok, rebooted... Wow... All scripts from /usr/local/etc/rc.d refused to load. And the system is in "Amnesiac" mode Attempt to run

Ok Please post the link for the bug report.. Thanks... ----- Original meddelelse ----- Fra: "Rowland penny" <rpenny at samba.org> Til: "samba" <samba at lists.samba.org> Sendt: mandag, 29. februar 2016 16:02:38 Emne: Re: [Samba] Segmentation Fault when trying to set root samba password, IPA as a backend On 29/02/16 14:57, Martin Juhl wrote: > Hi >

Hi, I have a question about: /sbin/installkernel I believe this line: LINK_PATH=/boot and usage of this variable... is a bug. What do others say? Using this script, as-is, I would need to chroot to make it work properly for a alternative INSTALL_PATH, right? who the heck is tyson? why did he re-write this? # # /sbin/installkernel - written by tyson at rwii.com # Cheers, AZ

Correct issue with not checking kmalloc return value. This fix now only uses one receive buffer for all hv_utils channels, and will do only one kmalloc on init and will return with a -ENOMEM if kmalloc fails on initialize. And properly clean up memory on failure. Thanks to Evgeniy Polyakov <zbr at ioremap.net> for pointing this out. And thanks to Jesper Juhl <jj at chaosbits.net>

Correct issue with not checking kmalloc return value. This fix now only uses one receive buffer for all hv_utils channels, and will do only one kmalloc on init and will return with a -ENOMEM if kmalloc fails on initialize. And properly clean up memory on failure. Thanks to Evgeniy Polyakov <zbr at ioremap.net> for pointing this out. And thanks to Jesper Juhl <jj at chaosbits.net>