Re: Anyone here would consider to split the sanboot comand into two commands?

Jarrod Johnson <[email protected]>
Newsgroups gmane.network.etherboot.user
Message-ID <[email protected]>
Fascinating, two of the patches I recently submitted are relevant,
they did two things:
-Gave me the ability to only register drives without booting (sadly, I
was inelegant in that I immediately pxebooted, however, for my use
case it is  convenient to drive it by filename).  I made a separate
'iscsireg' function that could be wrapped by a 'sanregister' command
generically.
-Gave the ability to boot bios drive regardless of what is backing it.
(called it hdboot)

In any event, it seems a number of people agree that boot to a bios
drive is a convenient separate command to have, and people want to
register bios drives via san and not actually boot from them.

Keeping sanboot as a shortcut for the register/hdboot commands would
be convenient.

On Tue, Jul 21, 2009 at 1:19 PM, Kyle Kienapfel<[email protected]> wrote:
> http://git.etherboot.org/?p=gpxe.git;a=blob;f=src/arch/i386/interface/pcbios/iscsiboot.c
> 65         printf ( "Booting from BIOS drive %#02x\n", drive->drive );
> 66         rc = int13_boot ( drive->drive );
> 67         printf ( "Boot failed\n" );
> Looks like a willing coder could add a dont_boot option similar to the
> keep_san option for the use case you want. Lines 65-67 would get surrounded
> by the if statement
> On Tue, Jul 21, 2009 at 6:52 AM, Yiyi Hu <[email protected]> wrote:
>>
>> Lazy typer here...
>>
>> 21:32 < xinming_> mdc_mobile: I really hope that sanboot command will
>> be splited into 2 commands.
>> 21:32 < mdc_mobile> 2 commands?
>> 21:32 < xinming_> otherwise, re-installing system might be a pain.
>> 21:32 < mdc_mobile> Have you suggested this on Etherboot-Discuss?
>> 21:33 < xinming_> mdc_mobile: I mean, first do,    'ibft
>> iscsi:blabla:bleble.......'   then,  another sanboot command
>> 21:33 < xinming_> mdc_mobile: Not yet.
>> 21:33 < xinming_> mdc_mobile: as someone ever told me that's not
>> needed at all. :-)
>> 21:33 < xinming_> Otherwise, if we want to re-install the system, we
>> need to touch the server side.
>> 21:35 < mdc_mobile> Sounds like an interesting use case.  I would
>> definitely send an email to Etherboot-Discuss explaining this
>> scenario. I think you can "set root-path iscsi: .... "
>> 21:36 < xinming_> mdc_mobile: do you mean,   set root-path iscsi:...
>> will set the iBFT in the memory?
>> 21:37 < mdc_mobile> If there is no filename, root-path is where gPXE
>> tries to boot from.
>> 21:38 < mdc_mobile> I don't think it writes the iBFT though.
>> 21:38 < mdc_mobile> So we may need another command to do so.
>> 21:38 < xinming_> mdc_mobile: But still, it'll boot into the
>> going-to-be-deleted system.
>>
>> To summarize the conversation. Let's split the sanboot into 2
>> commands, to make people who want to re-install the system over iSCSI
>> more handy. Without the pain of touching the server doing something
>> like      dd if=/dev/zero of=file_image.
>>
>> Any ideas please?  :-)
>>
>> xinming
>>
>>
>> ------------------------------------------------------------------------------
>> Enter the BlackBerry Developer Challenge
>> This is your chance to win up to $100,000 in prizes! For a limited time,
>> vendors submitting new applications to BlackBerry App World(TM) will have
>> the opportunity to enter the BlackBerry Developer Challenge. See full
>> prize
>> details at: http://p.sf.net/sfu/Challenge
>> _______________________________________________
>> Etherboot-discuss mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Etherboot-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>
>

------------------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.