Anyone Tried to use iPXE to boot with iSCSI?
I was just trying some proof of concept testing to see if I could get a system booting with no local disk using iSCSI running from my FreeNAS box. I got started, by first booting a 9.1-RC1 CD, into live CD, created a /tmp/iscsi.conf used kldload to load the iscsi initiator, connected to the target, created a gpt boot partition, swap partition and just a single / volume using remianing space. Copied the bootcode, created the file system, extracted the system etc. Created a loader.conf file, added the iscsi_initiator_load=YES option, copied my /tmp/iscsi.conf file to the new file system at /etc/iscsi.conf created a /etc/fstab file using the gpart labels to mount / and swap partitions. Booted the system from the iPXE.iso, ran the necessary configuration options, connected to the iscsi volume, and booted from it. It does launch the bootcode, as expected, and then breaks failing to mount root. Whoch I actually expected, I have proved I can install to an iSCSI volume, I can connect to that iSCSI volume prior to loading the kernel, and load the kernel from it. What I can't seem to find any information on is how to mount iSCSI volumes at boot on FreeBSD, so that the kernel can mount the root partition. Does anyone have any idea how to do this, or if its even possible? -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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: What replaces csup?
mer...@stonehenge.com schreef op : Stas == Stas Verberkt lego...@legolasweb.nl writes: Stas On a side note, using Git does mean that everyone has to download a complete Stas repository. This makes using a csup-like architecture quite Stas heavy-weight. The entire history of the Linux kernel since switching to git 5 years ago is stored in a repo that is *less than half the size* of a single current checkout. The entire history of the XFree86 project ended up being a repo that was only 2-3 times the size of the current checkout. Seriously, don't be afraid of git simply because it has all the history. SVN is already worse because it has a single local backup copy for every live file, 2x right there. I may have been influenced here by the fact that, in KDE, the size became a problem, due to the large amounts of binary content in the repositories (artwork), which is, of course, not the case for FreeBSD. ___ 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: installation of yuma
thank you a lot Steve; it's worked very well. Best regards 2012/9/18 Steve O'Hara-Smith at...@sohara.org On Tue, 18 Sep 2012 14:25:03 + ahmed elouadrhiri ahmedelouadrh...@gmail.com wrote: Hi all; i tried to install yuma in freebsd by the command : make freebsd=1 and it give me : Makefile, line 14: Need an operator At a guess you need to use gmake (you may need to install it first from the ports). -- Steve O'Hara-Smith at...@sohara.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
fsck not working on messed-up file system
I have or had a problem with a file system (FreeBSD UFS2) messed up, either by errant software or system freeze/crash. I successfully cross-compiled, from FreeBSD 9.0-STABLE, a NetBSD 5.1_STABLE i386 system to install on 8 GB USB stick. I have both the NetBSD system source as well as pkgsrc and the FreeBSD ports tree on a FreeBSD partition originally used for FreeBSD 9.0-BETA1, hence I use /BETA1 as the mount point. This partition is /dev/ada0p9 in FreeBSD and /dev/dk6 in NetBSD. I subsequently built modular-xorg for this NetBSD installation, installating to USB stick but doing the heavy compiling on the hard-drive partition. NetBSD, especially with X, is rather freeze/crash-prone, meaning file system is not cleanly umounted. I then tried to cross-compile, from same NetBSD source tree, NetBSD 5.1_STABLE amd64 but was thrown in the debugger (db), not really knowing what to do there. Choosing reset did not provide clean file-system unmount. I had to run fsck /dev/ada0p9 on the reboot, got unreadable sectors and eventually a prompt to run fsck again. I did this but got to an infinite loop, where I got the same prompt again to run fsck again, with the same unreadable blocks. I got the same thing booting a backup installation of FreeBSD 9.0_STABLE amd64 on a USB stick. I eventually ran with script to capture the output onto another USB stick, sorry about all those ASCII 13s at the ends of the lines: Script started on Wed Sep 19 04:15:02 2012 fsck_ffs /dev/ada0p9 ** /dev/ada0p9 ** Last Mounted on /BETA1 ** Phase 1 - Check Blocks and Sizes CANNOT READ BLK: 7584192 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 7584318, 7584319, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1475900 files, 4638292 used, 21162419 free (61643 frags, 2637597 blocks, 0.2% fragmentation) * FILE SYSTEM STILL DIRTY * * PLEASE RERUN FSCK * Script done on Wed Sep 19 04:17:27 2012 Would this indicate a software bug, or is my Western Digital Caviar Green 3 TB hard drive failing? I booted that USB stick with NetBSD 5.1_STABLE i386, successfully mounted that partition, /dev/dk6 in NetBSD, but got the message about dirty flag. So I umounted and ran NetBSD fsck_ffs, and after removing some files, mainly in /pkgsrc directory, and salvaging some stuff, got apparent success, and now that file system is again accessible in both NetBSD 5.1_STABLE i386 and FreeBSD 9.0_STABLE amd64. Now I wonder if the file system is really fixed, with possibly some files in /pkgsrc subdirectories lost, or if the hard drive is starting to fail. Tom ___ 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: fsck not working on messed-up file system
On Wed, 19 Sep 2012 06:05:06 -0400 Thomas Mueller muelle...@insightbb.com wrote: THE FOLLOWING DISK SECTORS COULD NOT BE READ: 7584318, 7584319, ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1475900 files, 4638292 used, 21162419 free (61643 frags, 2637597 blocks, 0.2% fragmentation) * FILE SYSTEM STILL DIRTY * * PLEASE RERUN FSCK * Script done on Wed Sep 19 04:17:27 2012 Would this indicate a software bug, or is my Western Digital Caviar Green 3 TB hard drive failing? Either something was referencing sectors off the end of the disc, or the drive is failing. I'd be inclined to copy the data off somewhere safe and subject the disc to extensive tests with smartctl from smartmontools, then if it passes recreate the fileystem(s) and restore the data. -- Steve O'Hara-Smith at...@sohara.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: fsck not working on messed-up file system
Hi, On Wed, 19 Sep 2012 06:05:06 -0400 Thomas Mueller muelle...@insightbb.com wrote: Script started on Wed Sep 19 04:15:02 2012 fsck_ffs /dev/ada0p9 just to make sure: the partition was not mounted when you started fsck? Now I wonder if the file system is really fixed, with possibly some files in /pkgsrc subdirectories lost, or if the hard drive is starting to fail. You see it soon. I would not bother about a single problem like this. I have had it over and over again at a location with bad power supply with a normal PC without UPS. The hard disk is - one year later - still working in a different location without any new problems. Erich ___ 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: have desktop on freebsd
2012-09-19 07:23, saeedeh motlagh skrev: thanks Bernt, i deinstall it and then try startx. startx works and displays graphical page. but when i restart me system i do not have desktop yet. you know, startx displays graphical page when fbdev is installed too. please let me know if you have any idea or hint that can solved my problem becuase i don't have any idea anymore. thanks Try this; cd /usr/ports/x11-drivers/xorg-drivers make rmconfig Then when you run make double check you do not have fbdev marked. ___ 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: schg flags from installworld
On Tue 2012-09-18 (23:31), Gareth de Vaux wrote: Looking at /usr/src/share/mk/bsd.prog.mk and /usr/src/share/mk/bsd.lib.mk - bins and libs get installed with schg if PRECIOUSPROG and PRECIOUSLIB are set respectively in their makefiles, both of which can be overridden by setting NO_FSCHG, presumably in /etc/make.conf. Without this doing jail maintenance/upgrades is a nightmare on a host with a securelevel of 1 but I haven't seen this mentioned anywhere. For the record the override works, except with /usr/bin/passwd. There seems to be a missing 'if !defined(NO_FSCHG)' condition around the afterinstall in /usr/src/usr.bin/passwd/Makefile. ___ 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
Reprieve [was: Re: FreeBSD 9.1-RC1 Available... (fwd)]
Folks, Seems that those (like me) concerned about 9.1 release branch activity not having been exported to CVS, requiring moving to SVN and abandoning c*sup source updating 'all of a sudden', can relax migration schedules a bit, for now .. though it's been a good 'gee-up' for me, at least. Probably worth mentioning that this only ever affected RELENG_9_1, ie 9.1 BETAs and RCs, not RELENG_9 (ie 9-STABLE) sources. Thanks Bjoern! cheers, Ian -- Forwarded message -- Date: Tue, 18 Sep 2012 12:20:23 + (UTC) From: Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net To: FreeBSD Release Engineering Team r...@freebsd.org Cc: freebsd-stable freebsd-sta...@freebsd.org Subject: Re: FreeBSD 9.1-RC1 Available... On Thu, 23 Aug 2012, Ken Smith wrote: Hi, let me reply to the very initial email in this monster of public thread. With both the doc and ports repositories now moved to SVN it has been decided to not export the 9.1 release branch activity to CVS. So csup/cvsup update mechanisms are not available for updating to 9.1-RC1. If you would like to use SVN the branch to use is releng/9.1. RELENG_9_1 is now exported the CVS as well and will be for as long as things will be exported to CVS. It will take another few hours to get near your local mirror as they'll all be chewing on each other the next 12 hours. Enjoy! Any further discussions on src export I'll leave to other people wearing hats. /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-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: What replaces csup?
On Tue, Sep 18, 2012 at 6:41 AM, Warren Block wbl...@wonkity.com wrote: On Mon, 17 Sep 2012, pete wright wrote: On Mon, Sep 17, 2012 at 8:14 PM, Warren Block wbl...@wonkity.com wrote: csup updates just the files that have changed without all the overhead. svn export can get a copy of all the current files, but it copies all of them every time, not just the changes. yea i agree with you. i wonder if it would be worth the effort of sharing a svn export via rsync or httpd to make fetching delta's easier and/or more efficient from a base install? It's an interesting idea. If the repository files were directly accessible in a filesystem, that filesystem could be shared with rsyncd and some exclude settings without needing an export at all. With svn bdb, the files are not directly accessible, but I don't know for fsfs. Probably not, so a periodic export would still be required. i did some tinkering with this last night, with the thought of storing an export in a zfs filesystem and eventually making it available publicly via a jail. my findings were that an export of the 9.1 relng branch consumed ~750MB while a svn co consumed ~1.4G of disk space and a full export took roughly 10-15mins. i eventually decided that what I was doing wasn't really needed by the wider end-user community. after mulling this move from cvs/csup for a bit i came to the conclusion that really the need for a source checkout is not as important as it may have been several years ago. freebsd-update is a really great tool, and i reckon for a majority of users out there not having to rebuild the kernel+world to get updates is a good thing(tm). i also reckon running a GENERIC kernel is appropriate in maybe %90 of use-cases out there as well (i haven't had a need to build a custom kernel on various server and workstation platforms since 2008'ish frankly). in this context, going the binary distribution route seems like a really smart decision. having a majority of your users basically running the same builds of the world and kernel *should* decrease the amount of support bandwidth needed to get people updated and running current code. i also reckon having more people running the same binaries would be helpful in finding reproducible bugs and hopefully squash them. so back to my original point...for sites running many systems, or sites requiring specific builds - mirroring the source tree locally is still very doable, and fortunately there are many well known ways to do this (svn co, svn export, skv, etc..). you could even argue that having a svn checkout may make patching bugs easier as you could just import a svn diff, rebuild and test. i also feel, personally, that it is nice to allow someone else build the kernel+world and let me grab binary updates as needed. now i can spend my clock cycles on more important tasks, like building packages for my pkgng repo :) -pete -- pete wright www.nycbug.org @nomadlogicLA ___ 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: What replaces csup?
On Tue, Sep 18, 2012 at 5:44 AM, Stas Verberkt lego...@legolasweb.nl wrote: Jerry schreef op : On Tue, 18 Sep 2012 05:00:08 -0700 Michael Sierchio articulated: We are really behind the curve here. Git assumes (correctly) that disk space is inexpensive, much cheaper per byte than network bandwidth. By the time we adopt SVN completely, every serious project I know of will have moved from subversion to git. If you are going to make a sweeping change anyway, it makes no sense to do it in a half–assed manned. However, it does appear that in all too many instances, FreeBSD plays follow the leader rather then taking the bulls by the horns and getting ahead of the curve. I am sure I'll be hearing from the baby steps choir now. In any event, a comprehensive side-by-side evaluation of the two should be done by an impartial party. We should not be forgetting that Git and Subversion represent two different workflows. The latter stands for a centralistic development cycle, and the former for a distributed manner. Thus, this type of choice does not really have to do with big or small steps and leading of following, but more about the production cycle you want to have. If we were to use a Git-like system, the releng team would (probably) be in control on which patches are excepted from the pool of suggested changesets by the community of developers. This community would be more free in the manner in which they experiment, and there would be a less strong differentiation between committers and other people suggesting updates. On the other hand, our current approach has a controlled group of committers and the releng team only has the additional power of setting the schedule and taking the snapshot that becomes the release. (Gravely simplified.) It is a matter of taste. +1 one thing worth noting is that developers have been using mercurial for quite a bit of time now for FreeBSD development(1), to take advantage of the distributed model of that SCM. yet having the main tree under CVS in the past, and SVN currently, makes sense to me. i feel that it results in a cleaner public tree that is easier to navigate. so fortunately the project has been able to take advantage of both of of these philosophies of SCM. -pete (1) http://wiki.freebsd.org/LocalMercurial -- pete wright www.nycbug.org @nomadlogicLA ___ 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: What replaces csup?
On Mon, 17 Sep 2012 21:26:45 -0600, Warren Block wrote: For ports, it's probably worth saving the distfile directory along with local diffs. Move it back into place after the svn checkout of the ports tree. PMFJI. Newbie here: What's wrong with using SVN for src, and portsnap for ports? 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
Re: What replaces csup?
Walter Hurry writes: PMFJI. Newbie here: What's wrong with using SVN for src, and portsnap for ports? _Wrong_? Nothing. But a lot of people like the idea of using the same tool to solve nearly identical problems. Your experience may diverga. 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
Can't find kernel, finds slices but no files on them
Hi list! I must warn you, I'm quite new to FreeBSD (I'm mostly using Linux otherwise). I have inherited an old (yes, very old) BSD 4.7 machine on my work that I need to clone. I've setuped an identical copy of the slices on the target machine, ran dump the source machine and restore on the target machine, edited /etc/fstab to match the filesystems. I'm also running the GENERIC-kernel, I've done this using the FreeSBIE live CD. However, when I boot I get to BTX loader (so I guess boot0 and boot2 is correct), that can't load kernel nor kernel.old. see attached img1.png . I can't ls, as the loader says there is no such file or directory (also seen in img1.png). lsdev gives a correct answer, all slices are there with their correct size. echo $currdev returns disk1s1a as it should (see attached img2.png). Mounting the disks works, and their content is correct, with all file params set. Any ideas how to get this target machine to boot? Thanks in advance, Fritiof Hedman ___ 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: Can't find kernel, finds slices but no files on them
On Wed, 19 Sep 2012 23:28:30 +0200, Fritiof Hedman wrote: Hi list! I must warn you, I'm quite new to FreeBSD (I'm mostly using Linux otherwise). I have inherited an old (yes, very old) BSD 4.7 machine on my work that I need to clone. I've setuped an identical copy of the slices on the target machine, ran dump the source machine and restore on the target machine, edited /etc/fstab to match the filesystems. I'm also running the GENERIC-kernel, I've done this using the FreeSBIE live CD. What procedure did you use to clone? There basically is the one way, using dump + restore on partitions (not slices!), or dd on either partitions, slices, or the whole disk. However, when I boot I get to BTX loader (so I guess boot0 and boot2 is correct), that can't load kernel nor kernel.old. see attached img1.png . Images cannot be attached to list messages. :-( I can't ls, as the loader says there is no such file or directory (also seen in img1.png). You can use echo * in the loader stage, if I remember correctly. Enter ? for a list of the available loader commands (or was it help?). lsdev gives a correct answer, all slices are there with their correct size. echo $currdev returns disk1s1a as it should (see attached img2.png). Good, so the copy you've created seems to be okay. Mounting the disks works, and their content is correct, with all file params set. Any ideas how to get this target machine to boot? Maybe you just missed to prepare the boot attributes of the new disk properly? I suggest having a look at those documents: Disk Setup On FreeBSD http://www.wonkity.com/~wblock/docs/html/disksetup.html Backup Options For FreeBSD dump(8)/restore(8) http://www.wonkity.com/~wblock/docs/html/backup.html#_em_dump_8_em_em_restore_8_em I'm almost sure that you will need to re-initialize something within the boot chain (guess without further diagnostics)... -- 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: What replaces csup?
On Wed, 19 Sep 2012, Walter Hurry wrote: On Mon, 17 Sep 2012 21:26:45 -0600, Warren Block wrote: For ports, it's probably worth saving the distfile directory along with local diffs. Move it back into place after the svn checkout of the ports tree. PMFJI. Newbie here: What's wrong with using SVN for src, and portsnap for ports? That's another way. If there are any local changes to the ports tree, portsnap will overwrite them. I also find portsnap slower than either csup or svn. ___ 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: Can't find kernel, finds slices but no files on them
On 19 September 2012 23:37, Polytropon free...@edvax.de wrote: On Wed, 19 Sep 2012 23:28:30 +0200, Fritiof Hedman wrote: Hi list! I must warn you, I'm quite new to FreeBSD (I'm mostly using Linux otherwise). I have inherited an old (yes, very old) BSD 4.7 machine on my work that I need to clone. I've setuped an identical copy of the slices on the target machine, ran dump the source machine and restore on the target machine, edited /etc/fstab to match the filesystems. I'm also running the GENERIC-kernel, I've done this using the FreeSBIE live CD. What procedure did you use to clone? There basically is the one way, using dump + restore on partitions (not slices!), or dd on either partitions, slices, or the whole disk. I maybe not so sure about the nomenclature that is used in FreeBSD. However, I dumped / on the source machine, and restored on /mnt/tmp on the source machine. However, when I boot I get to BTX loader (so I guess boot0 and boot2 is correct), that can't load kernel nor kernel.old. see attached img1.png . Images cannot be attached to list messages. :-( Oh, I see. It essentilally says something like: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 638kB/1046464kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (r...@builder.freebsdmall.com, Wed Oct 9 12:33:26 GMT 2002) \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] can't load 'kernel' can't load 'kernel.old' Type '?' for a list of commands, 'help' for more detailed help. ok ls open '/' failed: no such file or directory ok I can't ls, as the loader says there is no such file or directory (also seen in img1.png). You can use echo * in the loader stage, if I remember correctly. Enter ? for a list of the available loader commands (or was it help?). echo * just prints a pretty asterisk :) lsdev gives a correct answer, all slices are there with their correct size. echo $currdev returns disk1s1a as it should (see attached img2.png). Good, so the copy you've created seems to be okay. Mounting the disks works, and their content is correct, with all file params set. Any ideas how to get this target machine to boot? Maybe you just missed to prepare the boot attributes of the new disk properly? I suggest having a look at those documents: Disk Setup On FreeBSD http://www.wonkity.com/~wblock/docs/html/disksetup.html Backup Options For FreeBSD dump(8)/restore(8) http://www.wonkity.com/~wblock/docs/html/backup.html#_em_dump_8_em_em_restore_8_em I'm almost sure that you will need to re-initialize something within the boot chain (guess without further diagnostics)... It was more or less that way I did id, the difference were that I mounted /usr under /, and not unmount each partition every time. I'm rerunning as the first document says that I should do (ie unmount the partition that I've just dumped and restored). I've justed tested to do as described in the document, with the very same result. Yeah, that's my guess as well. Maybe I should do the minimal install of the FreeBSD image first, boot into a live mode and then restore everything upon the disks? That would keep any boot flags on the disks right. But the thing that is annoying is that the loader can't browse the content of the disk. I guess that's the main issue here. Cheers, Fritiof -- 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: What replaces csup?
On Wed, Sep 19, 2012 at 1:11 PM, Walter Hurry walterhu...@gmail.com wrote: On Mon, 17 Sep 2012 21:26:45 -0600, Warren Block wrote: For ports, it's probably worth saving the distfile directory along with local diffs. Move it back into place after the svn checkout of the ports tree. PMFJI. Newbie here: What's wrong with using SVN for src, and portsnap for ports? my personal issue is the fact that csup and portsnap are both part of the base system whereas svn would require installation via ports or the pkg utility. it is frankly a minor inconvenience - and hopefully there will be a csup like utility for svn available in base one day. -pete -- pete wright www.nycbug.org @nomadlogicLA ___ 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: Can't find kernel, finds slices but no files on them
On Thu, 20 Sep 2012 00:22:20 +0200, Fritiof Hedman wrote: On 19 September 2012 23:37, Polytropon free...@edvax.de wrote: On Wed, 19 Sep 2012 23:28:30 +0200, Fritiof Hedman wrote: Hi list! I must warn you, I'm quite new to FreeBSD (I'm mostly using Linux otherwise). I have inherited an old (yes, very old) BSD 4.7 machine on my work that I need to clone. I've setuped an identical copy of the slices on the target machine, ran dump the source machine and restore on the target machine, edited /etc/fstab to match the filesystems. I'm also running the GENERIC-kernel, I've done this using the FreeSBIE live CD. What procedure did you use to clone? There basically is the one way, using dump + restore on partitions (not slices!), or dd on either partitions, slices, or the whole disk. I maybe not so sure about the nomenclature that is used in FreeBSD. The terminology is simple and as follows: A disk is a disk, e. g. /dev/ad0. A slice is a DOS primary partition on the disk, e. g. /dev/ad0s1. A partition is a subdivision of a slice, e. g. /dev/ad0s1a. Partitions can be used without a slice that encloses them, e. g. /dev/ad0a; this is called dedicated mode (because some obscure operating systems may have problems accessing something they cannot even understand). Tools like dump and restore operate on partitions. Tools like dd operate on everything. However, I dumped / on the source machine, and restored on /mnt/tmp on the source machine. I assume you did dump and restore via network? Like this? http://www.wonkity.com/~wblock/docs/html/backup.html#_tt_dump_tt_via_ssh Or this? http://www.wonkity.com/~wblock/docs/html/backup.html#_copying_filesystems Or did you have both disks in the same machine and transfer from one disk to the other? Anyway, if you have already reliably (!) confirmed that all data is in the location they are supposed to be, your copying procedure should have been fine. However, when I boot I get to BTX loader (so I guess boot0 and boot2 is correct), that can't load kernel nor kernel.old. see attached img1.png . Images cannot be attached to list messages. :-( Oh, I see. It essentilally says something like: BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 638kB/1046464kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (r...@builder.freebsdmall.com, Wed Oct 9 12:33:26 GMT 2002) \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] can't load 'kernel' can't load 'kernel.old' Type '?' for a list of commands, 'help' for more detailed help. ok ls open '/' failed: no such file or directory ok Did you try echo * and echo /boot/* (and related important directories) to make sure? Note that the * is _required_ in this specific case. I can't ls, as the loader says there is no such file or directory (also seen in img1.png). You can use echo * in the loader stage, if I remember correctly. Enter ? for a list of the available loader commands (or was it help?). echo * just prints a pretty asterisk :) I'm not sure if this is really the proper command at the ok prompt (which is the state prior to loading the kernel); I could shutdown my machine to check... As I'm not very often sitting at the low level prompts, Ok and boot:, I'm not really sure. It was more or less that way I did id, the difference were that I mounted /usr under /, and not unmount each partition every time. That's not required as long as your CWD within the hierarchy for restoring is correct, and the mountpoints you want to restore to are correctly accessible. For example, if you missed to mount /mnt/usr to (let's say) /dev/ad1s1e (the partition that would be /usr soon), stuff would go to the wrong place. Did you transfer a multi-partition system (typically /, /var, /tmp, /usr and /home) or do you have everything in one big / partition? I'm rerunning as the first document says that I should do (ie unmount the partition that I've just dumped and restored). I've justed tested to do as described in the document, with the very same result. You should not mount the partition you _dump from_ (even though it's possible); only the partition you _restore to_ has to be (!) mounted. It doesn't basically matter _where_ it is mounted. As you could already locate the data at the correct places, we can assume that you did everything correct. To be sure, you could fsck the destination disks's partitions. Make sure they are not mounted. That should be no problem from a FreeSBIE disc (which I also consider a very good tool). Yeah, that's my guess as well. Maybe I should do the minimal install of the FreeBSD image first, boot into a live mode and then restore everything upon the disks? As a lazyness graduate, this is what I do (when I don't have a scripted solution, e. g. for only _one_ use). :-) Make sure you have
Re: What replaces csup?
On Wed, 19 Sep 2012 16:18:02 -0600, Warren Block wrote: I also find portsnap slower than either csup or svn. That surprises me. Once the initial download and extract is done, I find portsnap fetch update to be miles faster than csup. However, each to his own, I suppose. ___ 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: Anyone Tried to use iPXE to boot with iSCSI?
- Original Message - From: dweimer dwei...@dweimer.net To: FreeBSD Questions freebsd-questions@freebsd.org Cc: Sent: Wednesday, September 19, 2012 1:53 AM Subject: Anyone Tried to use iPXE to boot with iSCSI? I was just trying some proof of concept testing to see if I could get a system booting with no local disk using iSCSI running from my FreeNAS box. I got started, by first booting a 9.1-RC1 CD, into live CD, created a /tmp/iscsi.conf used kldload to load the iscsi initiator, connected to the target, created a gpt boot partition, swap partition and just a single / volume using remianing space. Copied the bootcode, created the file system, extracted the system etc. Created a loader.conf file, added the iscsi_initiator_load=YES option, copied my /tmp/iscsi.conf file to the new file system at /etc/iscsi.conf created a /etc/fstab file using the gpart labels to mount / and swap partitions. Booted the system from the iPXE.iso, ran the necessary configuration options, connected to the iscsi volume, and booted from it. It does launch the bootcode, as expected, and then breaks failing to mount root. Whoch I actually expected, I have proved I can install to an iSCSI volume, I can connect to that iSCSI volume prior to loading the kernel, and load the kernel from it. What I can't seem to find any information on is how to mount iSCSI volumes at boot on FreeBSD, so that the kernel can mount the root partition. Does anyone have any idea how to do this, or if its even possible? -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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 Interesting project you've got there. I can't say mine is similar but I do have a machine which I'm using as a router which boots disklessly. Running 8.3-STABLE amd64, in fact I just rebuilt the world on both the server which serves this puppy it's OS and the /diskless partition where this puppy get's it's boot up from. Booting by pxe is not an easy thing to do. The docs are terrible and out of synch with the latest versions of the OS. I think there may have been some improvments on that end but it's still kind of a seat of the pants operation. I had several contacts in #FreeBSD on FreeNode who told me they had many diskless servers running yet when pressed for how they did it the answers they gave were vague and ambiguous, that is if they answered at all. I did finally find a site which explained most of it in an almost clear manner, but even that site was filled with typos and out of date information. The router I've built is great...no disks at all and until the reboot a few weeks ago it had been running 24/7 for 276 days...without one failure. We watch lots of NetFlix movies here, sometimes two or three at a time with my teenage kids here with their laptops. And I can still enjoy a quick download or two in my lab while all this bandwidth is being served. ___ 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
bash Shell Scripting Question
I just discovered a knowledge deficiency on my part that I can't seem to resolve. If one writes a loop of the following form: #!/usr/local/bin/bash ls -LF |grep \/ /tmp/files while read dirname; do cd $dirname #Do whatever commands to be repeated in each directory. done /tmp/files This works quite well but it is shall we say sloppy because it creates a file that then must be cleaned up and its name needs to be made unique, etc. The standard output of the `ls -LF |grep \/` command needs to look like a file and all should be well. I thought the redirection would pickup the standard output. Thanks for ideas. Martin McCormick ___ 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: bash Shell Scripting Question
On Wed, 19 Sep 2012 21:03:11 -0500 Martin McCormick wrote: #!/usr/local/bin/bash ls -LF |grep \/ /tmp/files while read dirname; do cd $dirname #Do whatever commands to be repeated in each directory. done /tmp/files How about: ls -LF | grep \/ | while read dirname; do cd $dirname # do stuff done or: find . -maxdepth 1 -type d | while read dirname; do cd $dirname # do stuff done or even: find . -maxdepth 1 -type d ! -name .* | while read dirname; do cd $dirname # do stuff done -- Mihai Donțu ___ 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: bash Shell Scripting Question
On Wed, 19 Sep 2012 21:03:11 -0500, Martin McCormick wrote:
I just discovered a knowledge deficiency on my part that
I can't seem to resolve.
If one writes a loop of the following form:
#!/usr/local/bin/bash
Just a sidenote: If you're not using bash-specific functionality
and intend to make your script portable, use #!/bin/sh instead.
ls -LF |grep \/ /tmp/files
while read dirname; do
Attention: dirname (/usr/bin/dirname) is a binary!
cd $dirname
#Do whatever commands to be repeated in each directory.
done /tmp/files
This works quite well but it is shall we say sloppy
because it creates a file that then must be cleaned up and its
name needs to be made unique, etc.
Correct. You could use different approaches which may or may
not fail due to the directory names you will encounter (like
directories with spaces or special characters).
#!/bin/sh
for DIR in `ls -LF | grep \/`; do
cd ${DIR}
# do stuff
done
Or you can use piping:
#!/bin/sh
ls -LF | grep \/ | while read DIR; do
cd ${DIR}
# do stuff
done
I'm quite confident there are even more elegant and fault-
tolerant solutions. You would maybe have to tweak the ls
command or play with IFS (space or newline).
The standard output of the `ls -LF |grep \/` command
needs to look like a file and all should be well. I thought the
redirection would pickup the standard output.
No, the and redirections basically operate on files,
while pipes redirect strandard output to standard input.
So for example,
somecommand /tmp/somefile
refers to a file that has to exist, while
somecommand `someothercommand`
does not take someothercommand's output (stdout), but instead
interprets it as a file specification and then reads from that
files (if existing).
--
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
