Add isboot iSCSI boot driver to FreeBSD
Hi, isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you to boot your root partition using iSCSI. Installation is extremely simple: 1. extract the archive: # tar zxvf isboot-x.x.x.tar.gz 2. compile the module: # cd isboot-x.x.x/src # make 3. install the compiled module to the kernel directory: # make install 4. edit /boot/loader.conf, and add the following line: isboot_load="YES" This was first announced way back in June, 2010: https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html I've tested the current version (v0.2.10) and it works with FreeBSD 10.2 booting a ZFS on root installation: http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz I've used iSCSI boot with Ubuntu Server for a while and it's been very useful. I'm looking forward to FreeBSD having the same capability built-in. Cheers, Yonas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
dumpdev in loader.conf vs rc.d/dumpon
I have recently discovered 'dumpdev' kernel environment variable that is settable, for example, from loader.conf. To me it *seems* that this variable has to be set to a device name / path without the leading '/dev'. If that's so, then rc.d/dumpon must prepend '/dev' when passing the value of 'dumpdev' to dumpon(8). -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you to > boot your root partition using iSCSI. [,,,] > This was first announced way back in June, 2010: > > https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html > > I've tested the current version (v0.2.10) and it works with FreeBSD 10.2 > booting a ZFS on root installation: > > http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz > > I've used iSCSI boot with Ubuntu Server for a while and it's been very > useful. I'm looking forward to FreeBSD having the same capability built-in. +1. I have used this module in the past and it is extremely useful. Thanks for the pointer, I wasn’t aware it had been updated for FreeBSD 10.x so recently. I’ve also wondered why this is not part of FreeBSD by default. Aoyama-san, do you have any objection to this code being included in FreeBSD? If not, can you formally assign it a BSD or other friendly license? Thank you again for the work! Trasz (or anyone), is there other work to support iSCSI booting and/or IBFT on FreeBSD? Anything else isboot might conflict with? Any problems with integrating the code or with the code itself? In the mean time, I’m going to work on adding an isboot port to the tree to further ease installation and increase exposure. JN ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Port compilation fails on HEAD. works on 9 and 10 STABLE
met/mediatomb fails to compile with clang++36. Works fine with gcc++ and older versions of clang++. /usr/local/bin/clang++36 -DHAVE_CONFIG_H -I. -I.. -I../tombupnp/upnp/inc -I/usr/local/include -DLIBICONV_PLUG -I../src -I../tombupnp/ixml/inc -I../tombupnp/threadutil/inc -I../tombupnp/upnp/inc -I.. -I/usr/local/include-I/usr/local/include -I/usr/local/include/taglib -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -I/usr/local/include -O2 -pipe -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing -DLIBICONV_PLUG -MT libmediatomb_a-timer.o -MD -MP -MF .deps/libmediatomb_a-timer.Tpo -c -o libmediatomb_a-timer.o `test -f '../src/timer.cc' || echo './'`../src/timer.cc ../src/timer.cc:40:1: error: explicit specialization of 'mutex' after instantiation SINGLETON_MUTEX(Timer, true); ^ ../src/singleton.h:112:89: note: expanded from macro 'SINGLETON_MUTEX' ...recursive) template <> zmm::Ref Singleton::mutex = zmm::Re... ^ ../src/timer.h:82:18: note: implicit instantiation first required here AUTOLOCK(mutex); ^ ../src/sync.h:40:66: note: expanded from macro 'AUTOLOCK' #define AUTOLOCK(mutex) zmm::Ref mutex_autolock = mutex->... ^ 1 error generated. The macro in question is: #define SINGLETON_MUTEX(klass, recursive) template <> zmm::Ref Singleton::mutex = zmm::Ref(new Mutex(recursive)) //template zmm::Ref Singleton::mutex = zmm::Ref(new Mutex()); template zmm::Ref Singleton::instance = nil; template bool Singleton::singletonActive = true; Is this a problem with the code or the compiler? If it is the code, any suggestions on fixing it? I have no clue about C++, but I'd really like to get this working on HEAD. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dumpdev in loader.conf vs rc.d/dumpon
On Wed, Sep 23, 2015 at 7:37 AM, Andriy Gapon wrote: > > I have recently discovered 'dumpdev' kernel environment variable that is > settable, for example, from loader.conf. To me it *seems* that this variable > has to be set to a device name / path without the leading '/dev'. Why? > If that's so, > then rc.d/dumpon must prepend '/dev' when passing the value of 'dumpdev' to > dumpon(8). dumpon(8) opens the configured file (accessible in the normal namespace, i.e. "/dev/ada0s1b") and uses a magical ioctl on the device to configure it as the dump device. This is all documented in dumpon(8). Additionally, dumpon.c is short and quite legible. I don't see etc/rc.d/dumpon prepending /dev to anything. Best, Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dumpdev in loader.conf vs rc.d/dumpon
On 23/09/2015 18:59, Conrad Meyer wrote: > On Wed, Sep 23, 2015 at 7:37 AM, Andriy Gapon wrote: >> >> I have recently discovered 'dumpdev' kernel environment variable that is >> settable, for example, from loader.conf. To me it *seems* that this variable >> has to be set to a device name / path without the leading '/dev'. > > Why? Because that's how I read the code in sys/geom/geom_dev.c. Especially init_dumpdev() - I believe that devtoname() returns a device name without '/dev/'. >> If that's so, >> then rc.d/dumpon must prepend '/dev' when passing the value of 'dumpdev' to >> dumpon(8). > > dumpon(8) opens the configured file (accessible in the normal > namespace, i.e. "/dev/ada0s1b") and uses a magical ioctl on the device > to configure it as the dump device. This is all documented in > dumpon(8). Additionally, dumpon.c is short and quite legible. Indeed. > I don't see etc/rc.d/dumpon prepending /dev to anything. Right, that's why I posted my message (bug report). -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dumpdev in loader.conf vs rc.d/dumpon
On Wed, Sep 23, 2015 at 9:05 AM, Andriy Gapon wrote: > On 23/09/2015 18:59, Conrad Meyer wrote: >> On Wed, Sep 23, 2015 at 7:37 AM, Andriy Gapon wrote: > Because that's how I read the code in sys/geom/geom_dev.c. Especially > init_dumpdev() - I believe that devtoname() returns a device name without > '/dev/'. I don't think that's the primary use of the variable. >> I don't see etc/rc.d/dumpon prepending /dev to anything. > > Right, that's why I posted my message (bug report). I think the use of the variable "dumpdev" in GEOM probably could/should be dropped. Alternatively (perhaps it is a mechanism for collecting crash dumps before init / /etc/rc start?) the GEOM dumpdev code could skip over a "/dev/" prefix when comparing against devname(), so that the GEOM use of the variable matches the etc/rc.d/dumpon use of the variable. Best, Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dumpdev in loader.conf vs rc.d/dumpon
On 23/09/2015 19:44, Conrad Meyer wrote: > On Wed, Sep 23, 2015 at 9:05 AM, Andriy Gapon wrote: >> On 23/09/2015 18:59, Conrad Meyer wrote: >>> On Wed, Sep 23, 2015 at 7:37 AM, Andriy Gapon wrote: >> Because that's how I read the code in sys/geom/geom_dev.c. Especially >> init_dumpdev() - I believe that devtoname() returns a device name without >> '/dev/'. > > I don't think that's the primary use of the variable. See below. >>> I don't see etc/rc.d/dumpon prepending /dev to anything. >> >> Right, that's why I posted my message (bug report). > > I think the use of the variable "dumpdev" in GEOM probably > could/should be dropped. The way I found this variable was that I needed to set up a dump device before init. GEOM can do that, if dumpdev is set in kenv, as soon as a configured device is available. If a system survives until rc.d/dumpon can run, then why bother with setting dumpdev in kenv - dumpdev in rc.conf would work. > Alternatively (perhaps it is a mechanism for collecting crash dumps > before init / /etc/rc start?) Exactly. > the GEOM dumpdev code could skip over a > "/dev/" prefix when comparing against devname(), so that the GEOM use > of the variable matches the etc/rc.d/dumpon use of the variable. Yes, that's another option. But, IMO, dumpdev in kenv is only really useful if rc.d/dumpon doesn't have a chance to run. So, when rc.d/dumpon is able to run it can make a tiny concession to the way GEOM works. I do not have a strong opinion. Either option, rc.d/dumpon change or geom_dev change, is fine with me. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On Sep 23, 2015, at 9:16 AM, John Nielsen wrote: > On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > >> isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you to >> boot your root partition using iSCSI. > [,,,] >> This was first announced way back in June, 2010: >> >> https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html >> >> I've tested the current version (v0.2.10) and it works with FreeBSD 10.2 >> booting a ZFS on root installation: >> >> http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz >> >> I've used iSCSI boot with Ubuntu Server for a while and it's been very >> useful. I'm looking forward to FreeBSD having the same capability built-in. > > +1. I have used this module in the past and it is extremely useful. Thanks > for the pointer, I wasn’t aware it had been updated for FreeBSD 10.x so > recently. I’ve also wondered why this is not part of FreeBSD by default. > > Aoyama-san, do you have any objection to this code being included in FreeBSD? > If not, can you formally assign it a BSD or other friendly license? Thank you > again for the work! > > Trasz (or anyone), is there other work to support iSCSI booting and/or IBFT > on FreeBSD? Anything else isboot might conflict with? Any problems with > integrating the code or with the code itself? > > In the mean time, I’m going to work on adding an isboot port to the tree to > further ease installation and increase exposure. Proposed port here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203294 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Port compilation fails on HEAD. works on 9 and 10 STABLE
On 23 Sep 2015, at 21:57, Dimitry Andric wrote: > On 23 Sep 2015, at 17:38, Kevin Oberman wrote: >> >> met/mediatomb fails to compile with clang++36. Works fine with gcc++ and >> older versions of clang++. > > Try dropping the attached patch in net/mediatomb/files. I submitted it > in March, in PR198436: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 Eh, now with an actual patch. :) -Dimitry patch-timer.cc Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Port compilation fails on HEAD. works on 9 and 10 STABLE
On 23 Sep 2015, at 17:38, Kevin Oberman wrote: > > met/mediatomb fails to compile with clang++36. Works fine with gcc++ and > older versions of clang++. Try dropping the attached patch in net/mediatomb/files. I submitted it in March, in PR198436: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 but it did not get applied, because it apparently caused a build failure on 8.4 (for which the log is not available anymore, so no idea what the problem was). -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Add isboot iSCSI boot driver to FreeBSD
On 2015-09-23 11:16, John Nielsen wrote: > On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > >> isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you to >> boot your root partition using iSCSI. > [,,,] >> This was first announced way back in June, 2010: >> >> https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html >> >> I've tested the current version (v0.2.10) and it works with FreeBSD 10.2 >> booting a ZFS on root installation: >> >> http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz >> >> I've used iSCSI boot with Ubuntu Server for a while and it's been very >> useful. I'm looking forward to FreeBSD having the same capability built-in. > > +1. I have used this module in the past and it is extremely useful. Thanks > for the pointer, I wasn’t aware it had been updated for FreeBSD 10.x so > recently. I’ve also wondered why this is not part of FreeBSD by default. > > Aoyama-san, do you have any objection to this code being included in FreeBSD? > If not, can you formally assign it a BSD or other friendly license? Thank you > again for the work! > It appears to already have a standard BSD2 license on it. > Trasz (or anyone), is there other work to support iSCSI booting and/or IBFT > on FreeBSD? Anything else isboot might conflict with? Any problems with > integrating the code or with the code itself? > > In the mean time, I’m going to work on adding an isboot port to the tree to > further ease installation and increase exposure. > > JN > > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: Add isboot iSCSI boot driver to FreeBSD
Hi! > Proposed port here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203294 Builds on 10.2a+i, fails on current-amd64 and 9.3-amd64. Is this supposed to work on 9.3 or 11 ? -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Port compilation fails on HEAD. works on 9 and 10 STABLE
Hi! > > Try dropping the attached patch in net/mediatomb/files. I submitted it > > in March, in PR198436: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436 > > Eh, now with an actual patch. :) Thanks, helps to build it. Still fails on 9.3a, but I *have* to go to bed now. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On Sep 23, 2015, at 2:19 PM, Kurt Jaeger wrote: >> Proposed port here: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203294 > > Builds on 10.2a+i, fails on current-amd64 and 9.3-amd64. > > Is this supposed to work on 9.3 or 11 ? The README says 9.0-9.3 and 10.0-10.2. I’ve only tested it on 10.2. What is failing on the 9.3 build? Can you try 0.2.8 (instead of 0.2.10) and see if it works any better on 9.3? (Change the version in the Makefile, mv distinfo distinfo.prev; make fetch; make makesum). JN ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On Wed, Sep 23, 2015 at 1:10 PM, Allan Jude wrote: > On 2015-09-23 11:16, John Nielsen wrote: > > On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > > > >> isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you > to boot your root partition using iSCSI. > > [,,,] > >> This was first announced way back in June, 2010: > >> > >> https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html > >> > >> I've tested the current version (v0.2.10) and it works with FreeBSD > 10.2 booting a ZFS on root installation: > >> > >> http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz > >> > Yes , each file in the tar ball has BSD license at their beginning one by one . > >> I've used iSCSI boot with Ubuntu Server for a while and it's been very > useful. I'm looking forward to FreeBSD having the same capability built-in. > > > > +1. I have used this module in the past and it is extremely useful. > Thanks for the pointer, I wasn’t aware it had been updated for FreeBSD 10.x > so recently. I’ve also wondered why this is not part of FreeBSD by default. > > > > Aoyama-san, do you have any objection to this code being included in > FreeBSD? If not, can you formally assign it a BSD or other friendly > license? Thank you again for the work! > > > > It appears to already have a standard BSD2 license on it. > > > Trasz (or anyone), is there other work to support iSCSI booting and/or > IBFT on FreeBSD? Anything else isboot might conflict with? Any problems > with integrating the code or with the code itself? > > > > In the mean time, I’m going to work on adding an isboot port to the tree > to further ease installation and increase exposure. > > > > JN > > > > ___ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscr...@freebsd.org" > > > > > -- > Allan Jude > > Mehmet Erol Sanliturk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
Hi! > >> Proposed port here: > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203294 > > > > Builds on 10.2a+i, fails on current-amd64 and 9.3-amd64. > > > > Is this supposed to work on 9.3 or 11 ? > > The README says 9.0-9.3 and 10.0-10.2. I???ve only tested it on > 10.2. What is failing on the 9.3 build? I added a comment in the PR. It triggers some poudriere fail, which is very unusual. > Can you try 0.2.8 (instead of 0.2.10) and see if it works any > better on 9.3? (Change the version in the Makefile, mv distinfo > distinfo.prev; make fetch; make makesum). It does not work better. I really go do bed now 8-) and will further investigate tomorrow. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On 0923T0916, John Nielsen wrote: > On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > > > isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you to > > boot your root partition using iSCSI. > [,,,] > > This was first announced way back in June, 2010: > > > > https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html > > > > I've tested the current version (v0.2.10) and it works with FreeBSD 10.2 > > booting a ZFS on root installation: > > > > http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz > > > > I've used iSCSI boot with Ubuntu Server for a while and it's been very > > useful. I'm looking forward to FreeBSD having the same capability built-in. > > +1. I have used this module in the past and it is extremely useful. Thanks > for the pointer, I wasn’t aware it had been updated for FreeBSD 10.x so > recently. I’ve also wondered why this is not part of FreeBSD by default. > > Aoyama-san, do you have any objection to this code being included in FreeBSD? > If not, can you formally assign it a BSD or other friendly license? Thank you > again for the work! > > Trasz (or anyone), is there other work to support iSCSI booting and/or IBFT > on FreeBSD? Anything else isboot might conflict with? Any problems with > integrating the code or with the code itself? The basic problem with isboot is that it only works with the old iSCSI initiator, which is now marked obsolete. AFAIK there is no ready solution that works with the new one - however, it should be possible to use upcoming reroot support to achieve this: boot with a temporary rootfs, mounted from a ramdisk preloaded by loader(8), setup an iSCSI session, and then replace the temporary rootfs with the real one, mounted over iSCSI. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On Wed, Sep 23, 2015 at 11:25:20PM +0200, Edward Tomasz Napierala wrote: > On 0923T0916, John Nielsen wrote: > > On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > > > > > isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you > > > to boot your root partition using iSCSI. > > [,,,] > > > This was first announced way back in June, 2010: > > > > > > https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html > > > > > > I've tested the current version (v0.2.10) and it works with FreeBSD 10.2 > > > booting a ZFS on root installation: > > > > > > http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz > > > > > > I've used iSCSI boot with Ubuntu Server for a while and it's been very > > > useful. I'm looking forward to FreeBSD having the same capability > > > built-in. > > > > +1. I have used this module in the past and it is extremely useful. Thanks > > for the pointer, I wasn't aware it had been updated for FreeBSD 10.x so > > recently. I've also wondered why this is not part of FreeBSD by default. > > > > Aoyama-san, do you have any objection to this code being included in > > FreeBSD? If not, can you formally assign it a BSD or other friendly > > license? Thank you again for the work! > > > > Trasz (or anyone), is there other work to support iSCSI booting and/or IBFT > > on FreeBSD? Anything else isboot might conflict with? Any problems with > > integrating the code or with the code itself? > > The basic problem with isboot is that it only works with the old iSCSI > initiator, which is now marked obsolete. AFAIK there is no ready solution We have more then one iSCSI initiator? Other then iscsi_initiator(4)? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On 0924T0049, Slawa Olhovchenkov wrote: > On Wed, Sep 23, 2015 at 11:25:20PM +0200, Edward Tomasz Napierala wrote: > > > On 0923T0916, John Nielsen wrote: > > > On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: > > > > > > > isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you > > > > to boot your root partition using iSCSI. > > > [,,,] > > > > This was first announced way back in June, 2010: > > > > > > > > https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html > > > > > > > > I've tested the current version (v0.2.10) and it works with FreeBSD > > > > 10.2 booting a ZFS on root installation: > > > > > > > > http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz > > > > > > > > I've used iSCSI boot with Ubuntu Server for a while and it's been very > > > > useful. I'm looking forward to FreeBSD having the same capability > > > > built-in. > > > > > > +1. I have used this module in the past and it is extremely useful. > > > Thanks for the pointer, I wasn't aware it had been updated for FreeBSD > > > 10.x so recently. I've also wondered why this is not part of FreeBSD by > > > default. > > > > > > Aoyama-san, do you have any objection to this code being included in > > > FreeBSD? If not, can you formally assign it a BSD or other friendly > > > license? Thank you again for the work! > > > > > > Trasz (or anyone), is there other work to support iSCSI booting and/or > > > IBFT on FreeBSD? Anything else isboot might conflict with? Any problems > > > with integrating the code or with the code itself? > > > > The basic problem with isboot is that it only works with the old iSCSI > > initiator, which is now marked obsolete. AFAIK there is no ready solution > > We have more then one iSCSI initiator? Other then iscsi_initiator(4)? Sure we do, since 10.0-RELEASE: iscsi(4). "man iscsi_initiator" mentions this. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On Sep 23, 2015, at 3:25 PM, Edward Tomasz Napierała wrote: > On 0923T0916, John Nielsen wrote: >> On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: >> >>> isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you to >>> boot your root partition using iSCSI. >> [,,,] >>> This was first announced way back in June, 2010: >>> >>> https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html >>> >>> I've tested the current version (v0.2.10) and it works with FreeBSD 10.2 >>> booting a ZFS on root installation: >>> >>> http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz >>> >>> I've used iSCSI boot with Ubuntu Server for a while and it's been very >>> useful. I'm looking forward to FreeBSD having the same capability built-in. >> >> +1. I have used this module in the past and it is extremely useful. Thanks >> for the pointer, I wasn’t aware it had been updated for FreeBSD 10.x so >> recently. I’ve also wondered why this is not part of FreeBSD by default. >> >> Aoyama-san, do you have any objection to this code being included in >> FreeBSD? If not, can you formally assign it a BSD or other friendly license? >> Thank you again for the work! >> >> Trasz (or anyone), is there other work to support iSCSI booting and/or IBFT >> on FreeBSD? Anything else isboot might conflict with? Any problems with >> integrating the code or with the code itself? > > The basic problem with isboot is that it only works with the old iSCSI > initiator, which is now marked obsolete. AFAIK there is no ready solution > that works with the new one - however, it should be possible to use upcoming > reroot support to achieve this: boot with a temporary rootfs, mounted from > a ramdisk preloaded by loader(8), setup an iSCSI session, and then replace > the temporary rootfs with the real one, mounted over iSCSI. Ah, thank you for clarifying. I forgot that 10.x still supports the old initiator. The reroot approach sounds interesting but less straightforward. The beauty of isboot is that the kernel—loaded from a normal root disk that happens to be iSCSI-connected—knows how to re-establish its network and iSCSI connections just from the information in the iSCSI Boot Firmware Table, i.e. native iSCSI booting. I’d love to see the same approach continued with the new initiator. I suspect that a new implementation could re-use all of the IBFT code and most of the networking code, but I don’t know how hard the remaining pieces would be. I may have a chance to look in to it but a kernel programmer I am not, sadly. I think a “native” iSCSI reroot approach could be feasible at some point; for me that would mean that the loader could load the kernel and a standard-ish (or easily auto-generated) mfsroot from the iSCSI volume seamlessly, then something in the mfsroot parses the IBFT and sets up the network and iSCSI connections before switching root. JN ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Add isboot iSCSI boot driver to FreeBSD
On Sep 23, 2015, at 1:51 PM, John Nielsen wrote: > On Sep 23, 2015, at 9:16 AM, John Nielsen wrote: > >> On Sep 23, 2015, at 2:12 AM, Yonas Yanfa wrote: >> >>> isboot is a iSCSI boot driver written by Daisuke Aoyama that allows you to >>> boot your root partition using iSCSI. >> [,,,] >>> This was first announced way back in June, 2010: >>> >>> https://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html >>> >>> I've tested the current version (v0.2.10) and it works with FreeBSD 10.2 >>> booting a ZFS on root installation: >>> >>> http://www.peach.ne.jp/archives/isboot/isboot-0.2.10.tar.gz >>> >>> I've used iSCSI boot with Ubuntu Server for a while and it's been very >>> useful. I'm looking forward to FreeBSD having the same capability built-in. >> >> +1. I have used this module in the past and it is extremely useful. Thanks >> for the pointer, I wasn’t aware it had been updated for FreeBSD 10.x so >> recently. I’ve also wondered why this is not part of FreeBSD by default. >> >> Aoyama-san, do you have any objection to this code being included in >> FreeBSD? If not, can you formally assign it a BSD or other friendly license? >> Thank you again for the work! >> >> Trasz (or anyone), is there other work to support iSCSI booting and/or IBFT >> on FreeBSD? Anything else isboot might conflict with? Any problems with >> integrating the code or with the code itself? >> >> In the mean time, I’m going to work on adding an isboot port to the tree to >> further ease installation and increase exposure. > > Proposed port here: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203294 Thanks Allan and Mehmet for noticing the existing BSD license which I somehow overlooked in the source files. I have updated the PR above based on some feedback. Further testing welcome. JN ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Port compilation fails on HEAD. works on 9 and 10 STABLE
On Wed, Sep 23, 2015 at 1:39 PM, Kurt Jaeger wrote:
> Hi!
>
> > > Try dropping the attached patch in net/mediatomb/files. I submitted it
> > > in March, in PR198436:
> > >
> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198436
> >
> > Eh, now with an actual patch. :)
>
> Thanks, helps to build it. Still fails on 9.3a, but I *have* to go
> to bed now.
>
> --
> p...@opsec.eu+49 171 3101372 5 years to
> go !
>
Hmm. Looks like something is going wrong with Mk/Uses/iconv. The failing
test for iconv builds without -liconv.
Now it's time for me to get some sleep. Here is the relevant section of the
log:
configure:8520: checking iconv.h usability
configure:8537: cc -c -O2 -pipe -fstack-protector -fno-strict-aliasing
-I/usr/local/include conftest.c >&5
configure:8544: $? = 0
configure:8558: result: yes
configure:8562: checking iconv.h presence
configure:8577: cpp -I/usr/local/include conftest.c
configure:8584: $? = 0
configure:8598: result: yes
configure:8631: checking for iconv.h
configure:8638: result: yes
configure:9290: checking for iconv
configure:9346: cc -o conftest -O2 -pipe -fstack-protector
-fno-strict-aliasing -I/usr/local/include -lpthread -fstack-protector
conftest.c >&5
/tmp/ccLEMR46.o: In function `main':
conftest.c:(.text+0x7): undefined reference to `iconv'
configure:9353: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "MediaTomb"
| #define PACKAGE_TARNAME "mediatomb"
| #define PACKAGE_VERSION "0.12.1"
| #define PACKAGE_STRING "MediaTomb 0.12.1"
| #define PACKAGE_BUGREPORT "j...@mediatomb.cc"
#define PACKAGE "mediatomb"
| #define VERSION "0.12.1"
| #define EXTEND_PROTOCOLINFO 1
| #define UPNP_VERSION_STRING "0.12.1"
| #define UPNP_VERSION_MAJOR 0
| #define UPNP_VERSION_MINOR 4
| #define UPNP_VERSION_PATCH 1
| #define HAVE_DIRENT_H 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_WAIT_H 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE__BOOL 1
| #define HAVE_STDBOOL_H 1
| #define TIME_WITH_SYS_TIME 1
| #define HAVE_TIME_H 1
| #define HAVE_SYSLOG_H 1
| #define HAVE_STDDEF_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_ARPA_INET_H 1
| #define HAVE_FCNTL_H 1
| #define HAVE_LIMITS_H 1
| #define HAVE_NETDB_H 1
| #define HAVE_NETINET_IN_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_SYS_FILE_H 1
| #define HAVE_SYS_IOCTL_H 1
| #define HAVE_SYS_SOCKET_H 1
| #define HAVE_SYS_TIME_H 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_WAIT_H 1
| #define HAVE_LANGINFO_H 1
| #define HAVE_LOCALE_H 1
| #define HAVE_SYS_UTSNAME_H 1
| #define HAVE_SCHED_H 1
| #define HAVE_CTYPE_H 1
| #define HAVE_SCHED_GETPARAM 1
| #define HAVE_SCHED_SETPARAM 1
| #define HAVE_SCHED_GET_PRIORITY_MIN 1
| #define HAVE_SCHED_GET_PRIORITY_MAX 1
| #define HAVE_MKDIR 1
| #define HAVE_GETOPT_H 1
| #define HAVE_GETOPT_LONG 1
| #define HAVE_MKFIFO 1
| #define EXTERNAL_TRANSCODING 1
| /* end confdefs.h. */
| /* Define iconv to an innocuous variant, in case declares
iconv.
|For example, HP-UX 11i declares gettimeofday. */
| #define iconv innocuous_iconv
|
| /* System header to define __stub macros and hopefully few prototypes,
| which can conflict with char iconv (); below.
| Prefer to if __STDC__ is defined, since
| exists even on freestanding compilers. */
|
| #ifdef __STDC__
| # include
| #else
| # include
| #endif
|
| #undef iconv
|
| /* Override any GCC internal prototype to avoid an error.
|Use char because int might match the return type of a GCC
|builtin and then its argument prototype would still apply. */
| #ifdef __cplusplus
| extern "C"
| #endif
| char iconv ();
| /* The GNU C library defines this for functions which it implements
| to always fail with ENOSYS. Some functions are actually named
| something starting with __ and the normal name is an alias. */
| #if defined __stub_iconv || defined __stub___iconv
| choke me
| #endif
|
| int
| main ()
| {
| return iconv ();
| ;
| return 0;
| }
configure:9373: result: no
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
