├── LICENSE ├── README.md ├── doc ├── gparted-change-size.png ├── gparted-final.png ├── gparted-main.png ├── gparted-part-menu.png ├── image-install.md ├── shrink-rootsystem.md └── simple-usage.md ├── files └── usr │ └── local │ └── sbin │ └── pi-boot-switch └── tools └── install /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | {one line to give the program's name and a brief idea of what it does.} 635 | Copyright (C) {year} {name of author} 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | {project} Copyright (C) {year} {fullname} 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | Pi USB Boot Switcher 2 | ==================== 3 | 4 | Introduction 5 | ------------ 6 | 7 | Installation of Raspbian (or other similar distributions) on a SD-card 8 | is easy and straightforward. In contrast *running* the system directly 9 | from the SD-card is not optimal, especially if you have a lot of 10 | I/O-operations. A solution to the problem is to copy the installation 11 | to an usb device, typically a HDD or SSD, but an usb-stick will also 12 | boost performance (unless you happen to have a really slow one). 13 | 14 | To run a system from an USB device, you have two options: 15 | 16 | - Keep the boot partition with firmware and kernel on the SD-card, 17 | but move the system partition (also called root partition) to the 18 | usb device. This solution works with all available models. 19 | - use *usb boot*. This is a new feature available with a Pi3. In this 20 | case the boot partition will also reside on the usb device and you 21 | don't need a SD-card at all. This only works with a Pi3 and even 22 | then not every usb device supports the operation. 23 | 24 | The `pi-boot-switch`-script supports both options. The script allows you 25 | to 26 | 27 | - copy your root-partition from the SD-card to SD-card. 28 | - copy your root-partition from the SD-card to the usb device. 29 | - copy your root-partition from and to directories 30 | - copy your boot-partition from the SD-card to the usb device. 31 | - switch between multiple systems (a sort of bootmanager). 32 | - install new images directly to a target-partition. 33 | 34 | For a quick walkthrough read the document 35 | [doc/simple-usage.md](./doc/simple-usage.md "simple usage"). 36 | 37 | 38 | Installation 39 | ------------ 40 | 41 | To install the script, just run 42 | 43 | git clone https://github.com/bablokb/pi-boot-switch.git 44 | sudo tools/install 45 | 46 | This just installs the script in `files/usr/local/sbin/pi-boot-switch` to 47 | `/usr/local/sbin/pi-boot-switch`. 48 | 49 | 50 | Documentation 51 | ------------- 52 | 53 | After installation, Raspbian usually expands it's root-filesystem and 54 | claims all available space on the SD-card. A prerequisite for 55 | `pi-boot-switch` is free space, so you have to shrink the filesystem 56 | and partition to regain some of it. How to do that is covered in the 57 | document 58 | [doc/shrink-rootsystem.md](./doc/shrink-rootsystem.md "Shrinking the root-filesystem"). 59 | 60 | You can find a complete walkthrough of the most important options in the 61 | tutorial [doc/simple-usage.md](./doc/simple-usage.md "simple usage"). 62 | 63 | Installing an additional image using the option `-i` is covered in 64 | [doc/image-install.md](./doc/image-install.md "image installation"). 65 | 66 | Options not covered in these documents are either not yet implemented, 67 | or for special use. Please check the code before using them. 68 | 69 | For a short help just run 70 | 71 | $ > sudo pi-boot-switch -h 72 | 73 | pi-boot-switch: manage Raspberry Pi multiboot system 74 | 75 | usage: pi-boot-switch [options] 76 | Possible options: 77 | 78 | -I show partition info 79 | 80 | -c copy current partition (select target with -t) 81 | -t dest[=name] target partition/dir (required for -i or -c, e.g. '-t /dev/sdc') 82 | -C other copy from another partition/dir (select target with -t) 83 | -S target partition is on a SD-card, not an usb-device 84 | -F format target partition 85 | -k keep existing /home on target during copy (don't use -F) 86 | -U use UUIDs instead of device-names 87 | 88 | -L label set label of target partition (also available standalone) 89 | -D descr set description of target partition (also available standalone) 90 | 91 | -B copy /boot to partition dest and set dest as new /boot 92 | 93 | -s switch to partition dest for next boot (requires reboot) 94 | (select target with -t) 95 | -u update /home on dest from current partition before switching 96 | -R reboot immediately after switching 97 | 98 | -i image install image to target partition 99 | 100 | -v verbose operation 101 | -h show this help 102 | 103 | 104 | Armbian support 105 | --------------- 106 | 107 | Pi-boot-switch now also supports Armbian. Since Armbian uses a single 108 | partition for both the boot and root filesystem, you first have to 109 | convert the image. You can download a suitable script from my 110 | [armbian-convert project](https://github.com/bablokb/armbian-convert "armbian-convert-project"). This project contains a single file `armbian_convert.sh`, 111 | which will convert a typical armbian 7z-image with a single partition 112 | to an image with two partitions (one for boot and one for root). 113 | 114 | Once converted, you can install the image like any other image with 115 | e.g. `dd` to your sd-card and use it with `pi-boot-switch` to switch 116 | between partitions. 117 | 118 | Armbian uses UUIDs for referencing the root-device within `/boot/armbianEnv.txt`. 119 | The option `-U` will keep the UUIDs, without this option newly copied 120 | partitions will use device names. This does no harm but is not the Armbian 121 | way of doing it. 122 | 123 | Extlinux.conf support 124 | --------------- 125 | 126 | Like Armbian, most extlinux environments use UUIDs for referencing the root-device within `/boot/extlinux/extlinux.conf`. 127 | The option `-U` will keep the UUIDs. 128 | -------------------------------------------------------------------------------- /doc/gparted-change-size.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bablokb/pi-boot-switch/793994464ea03d5a58fa991050e65d347f9047ae/doc/gparted-change-size.png -------------------------------------------------------------------------------- /doc/gparted-final.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bablokb/pi-boot-switch/793994464ea03d5a58fa991050e65d347f9047ae/doc/gparted-final.png -------------------------------------------------------------------------------- /doc/gparted-main.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bablokb/pi-boot-switch/793994464ea03d5a58fa991050e65d347f9047ae/doc/gparted-main.png -------------------------------------------------------------------------------- /doc/gparted-part-menu.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bablokb/pi-boot-switch/793994464ea03d5a58fa991050e65d347f9047ae/doc/gparted-part-menu.png -------------------------------------------------------------------------------- /doc/image-install.md: -------------------------------------------------------------------------------- 1 | Install a Raspbian-Image to a target partition 2 | ============================================== 3 | 4 | Pi-boot-switch also supports the direct installation of a Raspbian-image 5 | to a given target-partition. To use this feature, you need at least a free 6 | system-partition (used as installation target). The best procedure is 7 | to download the image from raspberrypi.org and put it on an USB-stick. 8 | 9 | The script accepts images compressed with zip (download-format). You do 10 | not have to unzip it, but there must be enough free space on the 11 | partition where the image file resides to hold the unzipped image. 12 | 13 | Installation is straight forward, use a command like: 14 | 15 | sudo pi-boot-switch -i "path-to-image.zip" -t /dev/mmcblk0p3 -F 16 | 17 | This command only installs the image, to switch to the newly installed 18 | system, use the `-s` option. You can also use the `-L` option to 19 | set the label for the new system-partition. 20 | 21 | Note that this kind of installation of Raspbian is not supported by 22 | the foundation, so the system is in some small details different from 23 | a standard installation using dd or etcher. 24 | -------------------------------------------------------------------------------- /doc/shrink-rootsystem.md: -------------------------------------------------------------------------------- 1 | Shrinking the root filesystem 2 | ============================= 3 | 4 | After complete installation and configuration, the root-filesystem 5 | usually occupies the whole disk (execpt of course the small boot-partition). 6 | 7 | To reclaim space for additional system-partitions you first have to shrink 8 | the existing system-partition. This cannot be done while the system is 9 | active, so you have to shutdown the system first. 10 | 11 | Th shrink the partition you need a second (Linux) system. The recommended 12 | way is to install the desktop version of Raspbian (Pixel). After installation, 13 | you should additionally install the package `gparted` using the following 14 | commands from a terminal window: 15 | 16 | sudo apt-get update 17 | sudo apt-get -y install gparted 18 | 19 | To start the program, use the desktop-menu or run `sudo gparted` from 20 | a terminal. 21 | 22 | Gparted will display it's main window. Using the dropdown on the right 23 | (above the main pane), select the correct device. Be careful to choose 24 | the correct one, if unsure, you can use the menu to query the attributes 25 | of the device. 26 | 27 | ![](./gparted-main.png "main window of gparted"). 28 | 29 | As you can see in the screenshot, the second partition occupies almost all 30 | of the space of the device. The key symbol shows that the partition is 31 | mounted (due to the automounter of Raspbian). Before changing the partition 32 | size, you have to unmount the partition (available from the 33 | partition menu of gparted). 34 | 35 | After unmounting the partition, you can change the partition size again 36 | using the partition menu: 37 | 38 | ![](./gparted-part-menu.png "change the partition size using the menu"). 39 | 40 | In the next dialog, you can use the mouse to change the size, or you can 41 | enter the values directly: 42 | 43 | ![](./gparted-change-size.png "dialog to select partition parameters"). 44 | 45 | After changing the size of the second partition, you can also use 46 | gparted to add additional partitions for multiple system-partitions: 47 | 48 | ![](./gparted-final.png ""). 49 | 50 | In this screenshot you can see tow additional partitions. The third 51 | partition will be used as a second system-partition and the fourth 52 | partition as a data partition. 53 | 54 | To commit all changes, press the button with the green check mark. 55 | -------------------------------------------------------------------------------- /doc/simple-usage.md: -------------------------------------------------------------------------------- 1 | Simple Usage of pi-boot-switch 2 | ============================== 3 | 4 | Prerequisites 5 | ------------- 6 | 7 | This tutorial assumes that you installed your Raspbian system to a SD-card 8 | and configured it to your taste. It also assumes that you have a partitioned 9 | usb device (e.g. a HDD, SDD or an usb-stick) with three partitions: 10 | 11 | $ > fdisk -l /dev/sda 12 | 13 | Disk /dev/sda: 7,5 GiB, 8011120640 bytes, 15646720 sectors 14 | Units: sectors of 1 * 512 = 512 bytes 15 | Sector size (logical/physical): 512 bytes / 512 bytes 16 | I/O size (minimum/optimal): 512 bytes / 512 bytes 17 | Disklabel type: dos 18 | Disk identifier: 0x2052474d 19 | 20 | Device Boot Start End Sectors Size Id Type 21 | /dev/sda1 2048 165887 163840 80M c W95 FAT32 (LBA) 22 | /dev/sda2 165888 8554495 8388608 4G 83 Linux 23 | /dev/sda3 8554496 15646719 7092224 3,4G 83 Linux 24 | 25 | The first (small) partition will be our future boot partition. The other 26 | partitions will serve as system-partitions for two installations. They 27 | should be at least 2-8GB large, depending on your needs. For Raspbian-Lite, 28 | 2-4GB will do fine, for a full desktop installation you should at least 29 | reserve 8GB. Anyhow, space should be no problem on modern HDDs/SDDs. 30 | 31 | Note that you don't need to format the partitions, `pi-boot-switch` 32 | can do this for you. 33 | 34 | If you also want to boot from your usb-device, you should also prepare 35 | *usb boot* following [this guide](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md 36 | "USB boot"). 37 | 38 | Personally I don't use usb boot, because it slows down the boot-process and 39 | it is not reliable enough (too many usb devices are not supported). I keep 40 | the boot-partition on the SD-card and the root-partition on usb. 41 | 42 | 43 | Partition Information 44 | --------------------- 45 | 46 | The first step is to query partitition information using the option `-I`: 47 | 48 | $ > sudo pi-boot-switch -I 49 | Partition | Label | Role 50 | ----------------|------------------|--------------------- 51 | /dev/mmcblk0p1 | boot | current boot 52 | /dev/mmcblk0p2 | | current root / next root 53 | /dev/mmcblk0p3 | | 54 | /dev/sda1 | | 55 | /dev/sda2 | | 56 | /dev/sda3 | | 57 | 58 | Partitions on the SD-card are named like `/dev/mmcblk0p1`, partitions 59 | on the usb-device have a `/dev/sda` prefix (if you use multiple 60 | devices in parallel, you will also see `/dev/sdb` and so on). 61 | 62 | Since we booted from the SD-card, the current boot-partition should be 63 | `/dev/mmcblk0p1` and the current root-partition is `/dev/mmcblk0p2`. 64 | This will also be the next root-partition after a reboot. 65 | 66 | 67 | Copy the system-partition 68 | ------------------------- 69 | 70 | To copy the root-partition, run 71 | 72 | $ > sudo pi-boot-switch -c -t /dev/sda2 -F 73 | info: formatting partition /dev/sda2 with ext4 74 | info: mounting /dev/sda2 on /tmp/pi-boot-switch.FrSzev 75 | info: copying / to /tmp/pi-boot-switch.FrSzev 76 | info: fixing /etc/fstab on /dev/sda2 77 | info: copying /boot/ to /tmp/pi-boot-switch.FrSzev/_boot 78 | info: fixing /tmp/pi-boot-switch.FrSzev/_boot/cmdline.txt 79 | info: copied system to /dev/sda2 80 | info: use pi-boot-switch with option '-s /dev/sda2' to boot from new partition 81 | info: setting label for /dev/sda2: raspbian 8 82 | 83 | This will copy all files from the current root-partition to the new 84 | root-partition (passed in with the target-option `-t /dev/sda2`). Since we 85 | also used the option `-F`, the script will format `/dev/sda2` with 86 | the ext4-filesystem. If you already formatted your partition, just 87 | omit this option. 88 | 89 | You can also pass in the `-v` (verbose) option if you prefer 90 | to have more output. 91 | 92 | After the command has finished, run the info command again 93 | 94 | $ > sudo pi-boot-switch -I 95 | Partition | Label | Role 96 | ----------------|------------------|--------------------- 97 | /dev/mmcblk0p1 | boot | current boot 98 | /dev/mmcblk0p2 | | current root / next root 99 | /dev/mmcblk0p3 | | 100 | /dev/sda1 | | 101 | /dev/sda2 | raspbian 8 | 102 | /dev/sda3 | | 103 | 104 | As you can see, not much has changed. The partition `/dev/sda2` now 105 | has a label, but otherwise everything is as before. 106 | 107 | There are two things to note: using `-F` destroys all existing data on 108 | the target-partition, so be careful to select the correct partition. 109 | Secondly, also without `-F` a copy operation is destructive. The 110 | current root-partion is replicated to the target-partition and this 111 | will overwrite all files and in addition automatically delete all 112 | files on the target-partition which are not on the source-partition. 113 | 114 | There is one exception if you also use the option `-k`: in this case, 115 | the `/home`-directory is not copied to the target-partition. So you 116 | keep data in the home-directories, but you would still loose all 117 | configuration files e.g. in`/etc`. So make sure to backup all files 118 | needed before you replicate. 119 | 120 | 121 | Labelling the system-partition 122 | ------------------------------ 123 | 124 | The copy command will automatically label the selected partition, using 125 | information found in `/etc/os-release`. Since we want a more meaningful 126 | label, we change it with 127 | 128 | $ > sudo pi-boot-switch -t sda2 -L "production" 129 | info: setting label for /dev/sda2: production 130 | 131 | $ > sudo pi-boot-switch -I 132 | Partition | Label | Role 133 | ----------------|------------------|--------------------- 134 | /dev/mmcblk0p1 | boot | current boot 135 | /dev/mmcblk0p2 | | current root / next root 136 | /dev/mmcblk0p3 | | 137 | /dev/sda1 | | 138 | /dev/sda2 | production | 139 | /dev/sda3 | | 140 | 141 | Two things to note: the label is limited to 15 characters. Secondly, you 142 | do not need to pass the `/dev/` part for the partition name. This is 143 | not limited to labelling, `sda2` will always be a synonym for `/dev/sda2`. 144 | 145 | We also label the root-partition on the SD-card. Since this is our 146 | current root, we don't have to pass the `-t xxx` option: 147 | 148 | $ > sudo pi-boot-switch -L "original" 149 | info: setting label for /dev/mmcblk0p2: original 150 | 151 | Switching the system-partition 152 | ------------------------------ 153 | 154 | Until now, we only copied the system partition from the SD-card to the 155 | usb-device. The next command actually performs the switch: 156 | 157 | $ > sudo pi-boot-switch -s -t sda2 158 | info: copying /boot/ to /_boot 159 | info: mounting /dev/sda2 on /tmp/pi-boot-switch.FOT7cc 160 | info: copying /tmp/pi-boot-switch.FOT7cc/_boot/ to /boot 161 | info: unmounting /dev/sda2 162 | info: reboot the system to start from /dev/sda2 163 | 164 | $ > sudo pi-boot-switch -I 165 | Partition | Label | Role 166 | ----------------|------------------|--------------------- 167 | /dev/mmcblk0p1 | boot | current boot 168 | /dev/mmcblk0p2 | original | current root 169 | /dev/mmcblk0p3 | | 170 | /dev/sda1 | | 171 | /dev/sda2 | production | next root 172 | /dev/sda3 | | 173 | 174 | If you reboot the system now, it will boot from SD-card but the root-system 175 | will be mounted on the partition `/dev/sda2`. 176 | 177 | Note that switching the root-partition does not replicate user data. So 178 | don't be surprised that files you created (e.g. in /home/pi) are no longer 179 | there. They still exist, but on the original root-partition. 180 | 181 | To replicate user-data you have to add the option `-u`. This will copy all 182 | files from the `/home`-directory of the source-partition to the 183 | `/home`-directory of the target partition. 184 | 185 | 186 | Booting from the usb-device 187 | --------------------------- 188 | 189 | If we also want to boot from the usb-device, we also need to copy the 190 | boot-partition from the SD-card to the usb-device: 191 | 192 | $ > sudo pi-boot-switch -B -t sda1 -F 193 | info: formatting partition /dev/sda1 with Fat32 194 | mkfs.fat 3.0.27 (2014-11-12) 195 | info: mounting /dev/sda1 on /tmp/pi-boot-switch.GZGPMR 196 | info: copying /boot/ to /tmp/pi-boot-switch.GZGPMR 197 | fatlabel: warning - lowercase labels might not work properly with DOS or Windows 198 | info: fixing /boot in /etc/fstab on current root-partition 199 | info: testing /dev/mmcblk0p1 ... 200 | info: /dev/mmcblk0p1 is not a relevant partition 201 | info: testing /dev/sda2 ... 202 | info: found _boot, fixing /boot in /etc/fstab on partition /dev/sda2 203 | info: testing /dev/sda1 ... 204 | info: /dev/sda1 is not a relevant partition 205 | info: activate USB-boot to and remove SD-card to boot from /dev/sda1 206 | 207 | The option `-F` will again take care of formatting `/dev/sda1`. **Note that 208 | it is essential to first switch the system-partition and then copy 209 | the boot-partition**. Otherwise when booting from the usb-device the system will 210 | still try to mount the old root-partition from the (non-existent) SD-card. 211 | 212 | The command also updates the `/etc/fstab` of all systems to mount the 213 | new boot-partition. 214 | 215 | At this point you can shutdown the system, disconnect power, remove the 216 | SD-card and repower the system again. If you activated usb-boot as described 217 | in the prerequisites and your system (and device) is supported, 218 | then your system should boot normally. Running 219 | 220 | $ > sudo pi-boot-switch -I 221 | Partition | Label | Role 222 | ----------------|------------------|--------------------- 223 | /dev/mmcblk0p1 | boot | 224 | /dev/mmcblk0p2 | original | 225 | /dev/mmcblk0p3 | | 226 | /dev/sda1 | boot | current boot 227 | /dev/sda2 | production | current root / next root 228 | /dev/sda3 | | 229 | 230 | should confirm that you booted from `/dev/sda1` and your current root is 231 | `/dev/sda2`. 232 | 233 | 234 | Using a second system on the usb-device 235 | --------------------------------------- 236 | 237 | At this point we have an up and running Raspbian system labelled "production". 238 | One golden rule of IT is to never change a running system, at least not 239 | without a good backup. For this reason we copy the system to a new 240 | partition. This time we will use an all-in-one command to demonstrate that 241 | we can do all the steps we did above with separate commands with a 242 | single commandline: 243 | 244 | $ > sudo pi-boot-switch -c -t sda3 -s -L "test" -F 245 | info: formatting partition /dev/sda3 with ext4 246 | info: mounting /dev/sda3 on /tmp/pi-boot-switch.NPKDvD 247 | info: copying / to /tmp/pi-boot-switch.NPKDvD 248 | info: fixing /etc/fstab on /dev/sda3 249 | info: copying /boot/ to /tmp/pi-boot-switch.NPKDvD/_boot 250 | info: fixing /tmp/pi-boot-switch.NPKDvD/_boot/cmdline.txt 251 | info: copied system to /dev/sda3 252 | info: reboot the system to start from /dev/sda3 253 | info: copying /boot/ to /_boot 254 | info: mounting /dev/sda3 on /tmp/pi-boot-switch.xDgauR 255 | info: copying /tmp/pi-boot-switch.xDgauR/_boot/ to /boot 256 | info: unmounting /dev/sda3 257 | info: reboot the system to start from /dev/sda3 258 | info: setting label for /dev/sda3: test 259 | 260 | $ > sudo pi-boot-switch -I 261 | Partition | Label | Role 262 | ----------------|------------------|--------------------- 263 | /dev/mmcblk0p1 | boot | 264 | /dev/mmcblk0p2 | original | 265 | /dev/mmcblk0p3 | | 266 | /dev/sda1 | boot | current boot 267 | /dev/sda2 | production | current root 268 | /dev/sda3 | test | next root 269 | 270 | We use the option `-c` to initiate copying of the current root-partition 271 | to the *target*-partition (option `-t sda3`). We also switch to `/dev/sda3` 272 | using option `-s`. Finally, we label the target-partition using the 273 | option `-L`. Since we also want to format the target-partition, we use 274 | the option `-F`. Note that the order of the options is not relevant. 275 | 276 | So now we have two working installations, one on `/dev/sda2` and one on 277 | `/dev/sda3`. You can use `pi-boot-switch -s` to switch back and forth 278 | between both versions. Don't forget to reboot in between, since 279 | switching only changes the root-partition for the *next-boot*. 280 | 281 | 282 | Updating a partition 283 | -------------------- 284 | 285 | Let's assume you did some changes using the system on `/dev/sda3` 286 | (labelled 'test'). Once you are satisfied you want to go productive. In this 287 | case you can use the normal copy command (assuming you have booted the 288 | system on sda3): 289 | 290 | $ > sudo pi-boot-switch -c -t /dev/sda2 291 | 292 | Without the format option `-F` this will copy new or differing files. 293 | **Note that this command will also delete all files on `/dev/sda2` which 294 | are not on `/dev/sda3`. So be very careful that you don't loose any files 295 | you have created e.g. in your home-directory or in `/etc`!!** If you add 296 | the `-k`-option, user-data is not copied and the existing `/home`-directory 297 | on the target-partition will not be touched. 298 | -------------------------------------------------------------------------------- /files/usr/local/sbin/pi-boot-switch: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # ---------------------------------------------------------------------------- 3 | # Raspbian boot-switcher: manage Raspberry Pi multiboot system 4 | # 5 | # ---------------------------------------------------------------------------- 6 | # Author: Bernhard Bablok 7 | # License: GPL3 8 | # 9 | # Website: https://github.com/bablokb/pi-boot-switch 10 | # ---------------------------------------------------------------------------- 11 | 12 | # some constants ------------------------------------------------------------ 13 | 14 | BOOT_BACKUP="/_boot" 15 | FS_TYPE="ext4" 16 | REBOOT_DELAY="5" 17 | 18 | # set defaults -------------------------------------------------------------- 19 | 20 | setDefaults() { 21 | targetDevice="" 22 | targetDir="" 23 | rootDevice="" 24 | bootDevice="" 25 | verbose="" 26 | format="" 27 | isSD="" 28 | keepHome="" 29 | updateHome="" 30 | useUUID=0 31 | 32 | # operations 33 | info="" 34 | copy="" 35 | copyOther="" 36 | label="" 37 | description="" 38 | newBoot="" 39 | switch="" 40 | reboot="" 41 | install="" 42 | 43 | # environment 44 | if [ -f "/etc/armbian-release" ]; then 45 | if grep -q "DO NOT EDIT THIS FILE" "/boot/boot.ini"; then 46 | bootFile="armbianEnv.txt" 47 | bootSep="=" 48 | else 49 | bootFile="boot.ini" 50 | bootSep=" " 51 | fi 52 | bootParm="rootdev" 53 | useUUID=1 54 | elif [ -f "/boot/extlinux/extlinux.conf" ]; then 55 | bootFile="/extlinux/extlinux.conf" 56 | bootParm="root" 57 | bootSep="=" 58 | useUUID=1 59 | else 60 | bootFile="cmdline.txt" 61 | bootParm="root" 62 | bootSep="=" 63 | fi 64 | } 65 | 66 | # --- help ----------------------------------------------------------------- 67 | 68 | usage() { 69 | local pgm=`basename $0` 70 | echo -e "\n$pgm: manage Raspberry Pi multiboot system\n\ 71 | \nusage: `basename $0` [options]\n\ 72 | Possible options:\n\n\ 73 | -I show partition info 74 | 75 | -c copy current partition (select target with -t) 76 | -t dest[=name] target partition/dir (required for -i or -c, e.g. '-t /dev/sdc') 77 | -C other copy from another partition/dir (select target with -t) 78 | -S target partition is on a SD-card, not an usb-device 79 | -F format target partition 80 | -k keep existing /home on target during copy (don't use -F) 81 | -U use UUIDs instead of device-names 82 | 83 | -L label set label of target partition (also available standalone) 84 | -D descr set description of target partition (also available standalone) 85 | 86 | -B copy /boot to partition dest and set dest as new /boot 87 | 88 | -s switch to partition dest for next boot (requires reboot) 89 | (select target with -t) 90 | -u update /home on dest from current partition before switching 91 | -R reboot immediately after switching 92 | 93 | -i image install image to target partition 94 | 95 | -v verbose operation 96 | -h show this help 97 | " 98 | exit 3 99 | } 100 | 101 | # --- parse arguments and set variables ------------------------------------ 102 | 103 | parseArguments() { 104 | while getopts ":IcC:t:SFkUL:D:BsuRi:vh" opt; do 105 | case $opt in 106 | I) info=1;; 107 | c) copy=1;; 108 | C) copyOther=1; otherPartition="$OPTARG";; 109 | t) targetDevice="$OPTARG";; 110 | S) isSD=1;; 111 | F) format=1;; 112 | k) keepHome=1;; 113 | U) useUUID=1;; 114 | L) label=1; targetLabel="$OPTARG";; 115 | D) description="$OPTARG";; 116 | B) newBoot=1;; 117 | s) switch=1;; 118 | u) updateHome=1;; 119 | R) reboot=1;; 120 | i) install=1; srcImage="$OPTARG";; 121 | v) verbose="-v";; 122 | h) usage;; 123 | ?) echo "error: illegal option: $OPTARG" 124 | usage;; 125 | esac 126 | done 127 | 128 | shift $((OPTIND-1)) 129 | dirs=("$@") 130 | } 131 | 132 | # --- check arguments ------------------------------------------------------ 133 | 134 | checkArguments() { 135 | if [ -n "$targetDevice" ]; then 136 | 137 | # rename feature: extract name of target-device for use in fstab + cmdline.txt 138 | if grep -q '=' <<< "$targetDevice"; then 139 | IFS== read targetDevice targetDeviceName <<< "$targetDevice" 140 | [ "${targetDeviceName:0:4}" != "/dev" ] && \ 141 | targetDeviceName="/dev/$targetDeviceName" 142 | elif [ ! -d "$targetDevice" ]; then 143 | targetDeviceName="$targetDevice" 144 | fi 145 | 146 | if [ -d "$targetDevice" ]; then 147 | # targetDevice is actually a directory 148 | targetDir="$targetDevice" 149 | if [ $(find "$targetDir" | grep -v "lost+found" | wc -l) -gt 1 ]; then 150 | if [ -z "$format" ]; then 151 | msg "error: directory $targetDir is not empty!" 152 | exit 3 153 | fi 154 | fi 155 | if [ -z "$copy" -a -z "$copyOther" ]; then 156 | msg "error: a directory-target requires options -c or -C!" 157 | exit 3 158 | fi 159 | if [ -n "$isSD" ]; then 160 | msg "error: option -S not supported for directory-targets!" 161 | exit 3 162 | fi 163 | # disable unsupported options 164 | label="" 165 | switch="" 166 | description="" 167 | newBoot="" 168 | reboot="" 169 | else 170 | [ "${targetDevice:0:4}" != "/dev" ] && targetDevice="/dev/$targetDevice" 171 | if [ ! -b "$targetDevice" ]; then 172 | msg "error: $targetDevice does not exist!" 173 | exit 3 174 | fi 175 | fi 176 | 177 | if [ -n "$isSD" -a -z "$targetDeviceName" ]; then 178 | targetDeviceName="${targetDevice/sd?/mmcblk0p}" 179 | fi 180 | fi 181 | 182 | if [ -n "$copyOther" ]; then 183 | if [ -n "$copy" ]; then 184 | msg "error: options -c and -C are mutually exclusive!" 185 | exit 3 186 | elif [ -z "$otherPartition" ]; then 187 | msg "error: missing argument for option -C !" 188 | exit 3 189 | elif [ -d "$otherPartition" ]; then 190 | if [ ! -d "$otherPartition/_boot" ]; then 191 | msg "error: directory $otherPartition invalid source!" 192 | exit 3 193 | fi 194 | srcDir="$otherPartition" 195 | elif [ ! -b "$otherPartition" ]; then 196 | msg "error: $otherPartition is not a valid device!" 197 | exit 3 198 | fi 199 | fi 200 | } 201 | 202 | # --- write message to log and stderr -------------------------------------- 203 | 204 | msg() { 205 | echo -e "$1" >&2 206 | } 207 | 208 | # --- query mount-point of boot partition ---------------------------------- 209 | 210 | mountBoot() { 211 | if [ -d "/boot/firmware" ]; then 212 | # new mountpoint 213 | mp_part1="/boot/firmware" 214 | else 215 | mp_part1="/boot" 216 | fi 217 | findmnt -m "$mp_part1" > /dev/null || mount "$mp_part1" 218 | if [ $? -ne 0 ]; then 219 | msg "error: could not mount $mp_part1, aborting!" 220 | exit 3 221 | fi 222 | echo "$mp_part1" 223 | } 224 | 225 | # --- copy files of root-partition ----------------------------------------- 226 | 227 | copyRoot() { 228 | local src="$1" dst="$2" 229 | msg "info: copying $src to $dst" 230 | rsync $verbose -a -H -A -X -S -x --delete \ 231 | --exclude=/tmp/\*\* \ 232 | --exclude=/var/tmp/\*\* \ 233 | ${keepHome:+"--exclude=/home"} \ 234 | "$src" "$dst" 235 | # rsync destroys swap-files, so copy explicitly 236 | [ -f "$src/var/swap" ] && cp -a "$src/var/swap" "$dst/var/swap" 237 | sync 238 | } 239 | 240 | # --- copy files of boot-partition ----------------------------------------- 241 | 242 | copyBoot() { 243 | local src="$1" dst="$2" 244 | [ ! -d "$dst" ] && mkdir "$dst" 245 | msg "info: copying $src to $dst" 246 | rsync $verbose -a --delete --inplace --no-owner --no-group --modify-window=2 \ 247 | --exclude="pi-boot-switch.txt" --filter="P pi-boot-switch.txt" \ 248 | "$src" "$dst" 249 | sync 250 | } 251 | 252 | # --- query current root/boot device --------------------------------------- 253 | 254 | getCurrentDevice() { 255 | if [ "$1" = "UUID" ]; then 256 | findmnt -no UUID "$2" 257 | else 258 | findmnt -no SOURCE "$2" 259 | fi 260 | } 261 | 262 | # --- query next root device ----------------------------------------------- 263 | 264 | getNextRootDevice() { 265 | if [ -d "/boot/firmware" ]; then 266 | local nextRoot=$(sed -ne "s/.*${bootParm}${bootSep}\([^ ]*\) \?.*\$/\1/p" \ 267 | "/boot/firmware/$bootFile") 268 | else 269 | local nextRoot=$(sed -ne "s/.*${bootParm}${bootSep}\([^ ]*\) \?.*\$/\1/p" \ 270 | "/boot/$bootFile") 271 | fi 272 | if grep -qi UUID <<< "$nextRoot"; then 273 | nextRoot=$(blkid -l -o export -t "$nextRoot" | \ 274 | sed -ne "/DEVNAME/s/DEVNAME=//p") 275 | fi 276 | echo "$nextRoot" 277 | } 278 | 279 | # --- update fstab after copy ---------------------------------------------- 280 | 281 | updateFstab() { 282 | local part="$1" fstabPath="$2" 283 | msg "info: fixing / in /etc/fstab on $part" 284 | sed -i -e "/\W\/\W/s,^[^ \t]*,$part," "$fstabPath" 285 | 286 | bootPath="${fstabPath%%/*}/boot/firmware" 287 | if [ -d "$bootPath" ]; then 288 | # new mountpoint 289 | local mp_part1="/boot/firmware" 290 | local me_part1="\/boot\/firmware" # escaped version for sed below 291 | else 292 | local mp_part1="/boot" 293 | local me_part1="\/boot" 294 | fi 295 | msg "info: fixing $mp_part1 in /etc/fstab on $part" 296 | local currentBootDevice 297 | if [ $useUUID -eq 1 ]; then 298 | currentBootDevice="UUID=$(getCurrentDevice UUID $mp_part1)" 299 | else 300 | currentBootDevice=$(getCurrentDevice NAME $mp_part1) 301 | fi 302 | sed -i -e "/\W${me_part1}\W/s,^[^ \t]*,$currentBootDevice," "$fstabPath" 303 | } 304 | 305 | # --- update cmdline.txt after copy ---------------------------------------- 306 | 307 | updateCmdline() { 308 | local part="$1" cmdlinePath="$2" 309 | msg "info: fixing $cmdlinePath" 310 | sed --follow-symlinks -i \ 311 | -e "s,${bootParm}${bootSep}[^ ]*,${bootParm}${bootSep}$part," "$cmdlinePath" 312 | } 313 | 314 | # --- get default label ---------------------------------------------------- 315 | 316 | getLabel() { 317 | local ID VERSION_ID 318 | eval $(grep "^ID=\|^VERSION_ID=" "$1/etc/os-release") 319 | targetLabel="$ID $VERSION_ID" 320 | } 321 | 322 | # --- show partition information ------------------------------------------- 323 | 324 | doInfo() { 325 | declare -A role 326 | 327 | # fetch current roles of partitions 328 | local currentRoot=$(getCurrentDevice NAME /) 329 | local currentBoot=$(getCurrentDevice NAME "$mp_part1") 330 | local nextRoot=$(getNextRootDevice) 331 | 332 | role[$currentRoot]="curr root" 333 | if [ -n "${role[$nextRoot]}" ]; then 334 | role[$nextRoot]="curr/next root" 335 | else 336 | role[$nextRoot]="next root" 337 | fi 338 | role[$currentBoot]="curr boot" 339 | 340 | readDescription 341 | 342 | # check all partitions and print label, role and description 343 | 344 | echo "Partition | Label | Role | Description" 345 | echo "----------------|------------------|----------------|---------------" 346 | 347 | local part label rest 348 | ( while read part rest; do 349 | if grep -qw LABEL <<< "$rest"; then 350 | label=$(sed -e 's/.*LABEL="\([^"]*\)".*/\1/' <<< "$rest") 351 | else 352 | label="" 353 | fi 354 | part="${part%:}" 355 | printf "%-15s | %-16s | %-14s | %-s\n" "$part" "$label" "${role[$part]}" "${partDescription[$part]}" 356 | done < <( blkid | grep PARTUUID) 357 | ) | sort --version-sort 358 | } 359 | 360 | # --- read labels ---------------------------------------------------------- 361 | 362 | readLabels() { 363 | declare -A -g partLabels 364 | local part label rest 365 | while read part rest; do 366 | if grep -qw LABEL <<< "$rest"; then 367 | label=$(sed -e 's/.*LABEL="\([^"]*\)".*/\1/' <<< "$rest") 368 | else 369 | label="" 370 | fi 371 | partLabels["${part%:}"]="$label" 372 | done < <( blkid | grep PARTUUID) 373 | } 374 | 375 | # --- label current/target partition --------------------------------------- 376 | 377 | doLabel() { 378 | [ -z "$targetLabel" ] && return 379 | local device 380 | if [ -n "$targetDevice" ]; then 381 | device="$targetDevice" 382 | else 383 | device=$(getCurrentDevice NAME /) 384 | fi 385 | 386 | # query filesystem type 387 | local fstype=$(lsblk -nlo FSTYPE "$device" 2>/dev/null) 388 | 389 | if [ -z "$fstype" ]; then 390 | msg "error: $device has no filesystem" 391 | return 392 | fi 393 | 394 | msg "info: setting label for $device: $targetLabel" 395 | if [[ "${fstype,,}" =~ ext.* ]]; then 396 | e2label "$device" "$targetLabel" 397 | elif [ "${fstype,,}" = "vfat" ]; then 398 | if type -p fatlabel > /dev/null; then 399 | fatlabel "$device" "$targetLabel" 400 | else 401 | msg "warning: could not label $device - please install fatlabel" 402 | fi 403 | else 404 | msg "warning: could not label $device - unsupported filesystem type" 405 | fi 406 | } 407 | 408 | # --- add description for current/target partition ------------------------- 409 | 410 | doDescription() { 411 | local device 412 | if [ -n "$targetDevice" ]; then 413 | device="$targetDevice" 414 | # keep copy of description in _boot/pi-boot-switch.txt.self 415 | local mntDirTarget=`mktemp -d --tmpdir pi-boot-switch.XXXXXX` 416 | msg "info: mounting $targetDevice on $mntDirTarget" 417 | if mount "$targetDevice" "$mntDirTarget"; then 418 | mkdir -p "$mntDirTarget/_boot" 419 | echo "$description" > "$mntDirTarget/_boot/pi-boot-switch.txt.self" 420 | msg "info: umounting $targetDevice" 421 | umount "$mntDirTarget" && rm -fr "$mntDirTarget" 422 | fi 423 | else 424 | device=$(getCurrentDevice NAME /) 425 | mkdir -p "/_boot" 426 | echo "$description" > "/_boot/pi-boot-switch.txt.self" 427 | echo "$description" > "$mp_part1/pi-boot-switch.txt.self" 428 | fi 429 | 430 | # read current description 431 | readDescription 432 | partDescription["$device"]="$description" 433 | writeDescription 434 | } 435 | 436 | # --- read partition descriptions ------------------------------------------ 437 | 438 | readDescription() { 439 | declare -A -g partDescription 440 | if [ ! -f "$mp_part1/pi-boot-switch.txt" ]; then 441 | msg "info: no partition descriptions available" 442 | return 443 | fi 444 | 445 | msg "info: reading partition descriptions from $mp_part1/pi-boot-switch.txt" 446 | local part desc 447 | while read part desc; do 448 | partDescription["${part/:}"]="$desc" 449 | done < "$mp_part1/pi-boot-switch.txt" 450 | } 451 | 452 | # --- write partition descriptions ------------------------------------------ 453 | 454 | writeDescription() { 455 | declare -A -g partDescription 456 | 457 | msg "info: writing partition descriptions to /boot/pi-boot-switch.txt" 458 | local key 459 | for key in "${!partDescription[@]}"; do 460 | echo "$key: ${partDescription[$key]}" 461 | done > "$mp_part1/pi-boot-switch.txt" 462 | } 463 | 464 | # --- fix /etc/fstab on all root-devices ----------------------------------- 465 | 466 | fixAllFstab() { 467 | # replace bootDevice (devname) with uuid if necessary 468 | if [ $useUUID -eq 1 ]; then 469 | local uuid=$(lsblk -nlo UUID "$bootDevice") 470 | local bootDevice="UUID=$uuid" 471 | fi 472 | # fix current root partition 473 | if [ "$mp_part1" = "/boot/firmware" ]; then 474 | # new mountpoint 475 | me_part1="\/boot\/firmware" # escaped version for sed below 476 | else 477 | me_part1="\/boot" 478 | fi 479 | msg "info: fixing $mp_part1 in /etc/fstab on current root-partition $part" 480 | sed -i -e "/\W${me_part1}\W/s,^[^ \t]*,$bootDevice," "/etc/fstab" 481 | 482 | # create temporary mountpoint 483 | local tmpMnt=`mktemp -d --tmpdir pi-boot-switch.XXXXXX` 484 | 485 | # we only take partitions with label into account and skip the current root 486 | local part rest currentRoot=$(getCurrentDevice NAME /) 487 | while read part rest; do 488 | part="${part%:}" 489 | [ "$part" = "$currentRoot" ] && continue 490 | 491 | msg "info: testing $part ..." 492 | if ! mount "$part" "$tmpMnt"; then 493 | msg "info: could not mount $part: ignoring" 494 | continue 495 | fi 496 | if [ -d "$tmpMnt/_boot" ]; then 497 | if [ -d "$tmpMnt/boot/firmware" ]; then 498 | # new mountpoint 499 | tmp_mp_part1="/boot/firmware" 500 | tmp_me_part1="\/boot\/firmware" # escaped version for sed below 501 | else 502 | tmp_mp_part1="/boot" 503 | tmp_me_part1="\/boot" 504 | fi 505 | msg "info: found _boot, fixing $tmp_mp_part1 in /etc/fstab on partition $part" 506 | sed -i -e "/\W${tmp_me_part1}\W/s,^[^ \t]*,$bootDevice," "$tmpMnt/etc/fstab" 507 | else 508 | msg "info: $part is not a relevant partition" 509 | fi 510 | umount "$tmpMnt" 511 | done < <( blkid -s LABEL) 512 | 513 | # cleamup temporary mountpoint 514 | mount | grep -qw "$tmpMnt" || rm -fr "$tmpMnt" 515 | } 516 | 517 | # --- create and configure new boot-partition ------------------------------ 518 | 519 | doNewBoot() { 520 | local bootDevice="$targetDevice" 521 | if [ -z "$bootDevice" ]; then 522 | msg "error: no target boot device specified" 523 | exit 3 524 | elif [ ! -b "$bootDevice" ]; then 525 | msg "error: $bootDevice is no block device" 526 | exit 3 527 | fi 528 | 529 | # format partition 530 | if [ -n "$format" ]; then 531 | msg "info: formatting partition $bootDevice with Fat32" 532 | mkfs.fat $verbose -F 32 "$bootDevice" 533 | else 534 | msg "warning: not formatting $targetDevice!" 535 | fi 536 | 537 | # mount new boot partition 538 | local mntNewBoot=`mktemp -d --tmpdir pi-boot-switch.XXXXXX` 539 | msg "info: mounting $bootDevice on $mntNewBoot" 540 | if ! mount "$bootDevice" "$mntNewBoot"; then 541 | msg "error: could not mount $bootDevice, aborting!" 542 | rm -fr "$mntNewBoot" 543 | exit 3 544 | fi 545 | 546 | # mount and copy /boot or /boot/firmware 547 | copyBoot "$mp_part1/" "$mntNewBoot" # copy to new boot and ... 548 | if [ -f "/boot/pi-boot-switch.txt" ]; then 549 | # ... also copy excluded pi-boot-switch.txt 550 | cp -a "$mp_part1/pi-boot-switch.txt" "$mntNewBoot" 551 | fi 552 | 553 | umount "$mntNewBoot" && rm -fr "$mntNewBoot" 554 | if type -p fatlabel > /dev/null; then 555 | fatlabel "$bootDevice" "boot" 556 | else 557 | msg "warning: could not label $bootDevice - please install fatlabel" 558 | fi 559 | 560 | # change device for mountpoint /boot in all systems 561 | fixAllFstab 562 | 563 | msg "info: activate USB-boot to and remove SD-card to boot from $bootDevice" 564 | } 565 | 566 | # --- install an image to a partition -------------------------------------- 567 | 568 | doInstall() { 569 | msg "info: installing $srcImage to $targetDevice" 570 | 571 | # load kernel module for loop-mount 572 | modprobe loop 573 | 574 | # unzip image to temporary storage if necessary 575 | local imgFile didUnzip 576 | if [ "${srcImage##*.}" = "zip" ]; then 577 | msg "info: unzipping $srcImage to $srcImage.img" 578 | unzip -p "$srcImage" > "$srcImage.img" 579 | imgFile="$srcImage.img" 580 | didUnzip=1 581 | else 582 | imgFile="$srcImage" 583 | didUnzip=0 584 | fi 585 | 586 | # create loop-partitions 587 | local srcDevice 588 | srcDevice=`losetup --show -f -P "$imgFile" 2>/dev/null` 589 | if [ -z "$srcDevice" ]; then 590 | msg "error: could not setup loop-devices for $imgFile!" 591 | exit 3 592 | fi 593 | msg "info: src device is: $srcDevice" 594 | 595 | # loop-mount partitions of image 596 | # -> part1: boot 597 | # -> part2: root 598 | local mntDirSrc=`mktemp -d --tmpdir pi-boot-switch.XXXXXX` 599 | msg "info: mounting ${srcDevice}p2 on $mntDirSrc" 600 | if ! mount "${srcDevice}p2" "$mntDirSrc"; then 601 | msg "error: could not mount ${srcDevice}p2, aborting!" 602 | losetup -D "$imgFile" 603 | exit 3 604 | fi 605 | 606 | # TODO: change mountpoint to mp_part1 607 | if [ -d "$mntDirSrc/boot/firmware" ]; then 608 | # new mountpoint 609 | tmp_mp_part1="boot/firmware" 610 | else 611 | tmp_mp_part1="boot" 612 | fi 613 | msg "info: mounting ${srcDevice}p1 on $mntDirSrc/$tmp_mp_part1" 614 | if ! mount "${srcDevice}p1" "$mntDirSrc/$tmp_mp_part1"; then 615 | msg "error: could not mount ${srcDevice}p1, aborting!" 616 | umount "${srcDevice}p2" 617 | losetup -D "$imgFile" 618 | exit 3 619 | fi 620 | 621 | # copy files 622 | doCopy "$mntDirSrc/" 623 | msg "info: finished installing $srcImage to $targetDevice" 624 | 625 | # umount and release loop-partitions 626 | msg "info: cleaning up devices" 627 | umount "${srcDevice}p1" 628 | umount "${srcDevice}p2" && rm -fr "$mntDirSrc" 629 | losetup -D "$imgFile" 630 | 631 | # remove unzipped image 632 | if [ "$didUnzip" -eq 1 ]; then 633 | msg "info: removing temporary image" 634 | rm -f "$srcImage.img" 635 | fi 636 | } 637 | 638 | # --- copy files from another partition to target partition ---------------- 639 | 640 | doCopyOther() { 641 | local mntOther didMount=0 642 | 643 | if [ -z "$srcDir" ]; then 644 | # mount other partition if necessary 645 | mntOther=$(mount | grep -w "$otherPartition" | cut -f3 -d" ") 646 | if [ -z "$mntOther" ]; then 647 | didMount=1 648 | mntOther=`mktemp -d --tmpdir pi-boot-switch.XXXXXX` 649 | mount -o ro "$otherPartition" "$mntOther" 650 | fi 651 | else 652 | mntOther="$srcDir" 653 | fi 654 | 655 | # check if partition is valid 656 | if [ ! -d "$mntOther/_boot" ]; then 657 | msg "error: $mntOther is not a valid partition" 658 | if [ $didMount -eq 1 ]; then 659 | umount "$otherPartition" && rm -fr "$mntOther" 660 | fi 661 | return 3 662 | fi 663 | 664 | # copy files 665 | doCopy "$mntOther/" 666 | 667 | # cleanup 668 | if [ $didMount -eq 1 ]; then 669 | umount "$otherPartition" && rm -fr "$mntOther" 670 | fi 671 | return 0 672 | } 673 | 674 | # --- copy files to target partition --------------------------------------- 675 | 676 | doCopy() { 677 | if [ -z "$targetDevice" ]; then 678 | msg "error: no target partition selected" 679 | exit 3 680 | fi 681 | 682 | local src="$1" 683 | 684 | # add sanity check 685 | if [ -z "$targetDir" ]; then 686 | if mount | grep -qw "$targetDevice"; then 687 | msg "error: $targetDevice is mounted. Cowardly refusing to continue" 688 | exit 3 689 | fi 690 | fi 691 | 692 | # format target partition 693 | if [ -z "$targetDir" ]; then 694 | if [ -n "$format" ]; then 695 | msg "info: formatting partition $targetDevice with $FS_TYPE" 696 | if [ -n "$verbose" ]; then 697 | mkfs.$FS_TYPE -F -E "lazy_itable_init=0,lazy_journal_init=0" "$targetDevice" 698 | else 699 | mkfs.$FS_TYPE -q -F -E "lazy_itable_init=0,lazy_journal_init=0" "$targetDevice" 700 | fi 701 | else 702 | msg "warning: not formatting $targetDevice!" 703 | fi 704 | fi 705 | 706 | # query UUID of targetDevice 707 | if [ $useUUID -eq 1 -a -z "$targetDir" ]; then 708 | targetUUID=$(blkid -o export -s UUID "$targetDevice" | grep "UUID") 709 | fi 710 | 711 | if [ -z "$targetDir" ]; then 712 | # mount target partition 713 | local mntDirTarget=`mktemp -d --tmpdir pi-boot-switch.XXXXXX` 714 | msg "info: mounting $targetDevice on $mntDirTarget" 715 | if ! mount "$targetDevice" "$mntDirTarget"; then 716 | msg "error: could not mount $targetDevice, aborting!" 717 | exit 3 718 | fi 719 | else 720 | local mntDirTarget="$targetDir" 721 | fi 722 | 723 | # copy files 724 | copyRoot "$src" "$mntDirTarget" 725 | 726 | # fix fstab 727 | if [ $useUUID -eq 1 -a -z "$targetDir" ]; then 728 | updateFstab "$targetUUID" "$mntDirTarget/etc/fstab" 729 | elif [ -n "$targetDeviceName" ]; then 730 | updateFstab "$targetDeviceName" "$mntDirTarget/etc/fstab" 731 | fi 732 | 733 | # mount and copy /boot 734 | if [ -n "$copy" ]; then 735 | copyBoot "$mp_part1/" "$mntDirTarget/_boot" # copy to new root/_boot 736 | fi 737 | 738 | # fix /_boot/cmdline.txt 739 | if [ $useUUID -eq 1 -a -z "$targetDir" ]; then 740 | updateCmdline "$targetUUID" "$mntDirTarget/_boot/$bootFile" 741 | elif [ -n "$targetDeviceName" ]; then 742 | updateCmdline "$targetDeviceName" "$mntDirTarget/_boot/$bootFile" 743 | fi 744 | 745 | if [ -z "$targetDir" -a -z "$srcDir" ]; then 746 | # get label if empty 747 | local srcPart=$(findmnt -no SOURCE `stat --printf "%m" "$src"`) 748 | if [ -z "$targetLabel" -a -z "$(lsblk -nlo LABEL $targetDevice)" ]; then 749 | targetLabel=$(lsblk -nlo LABEL "$srcPart") 750 | if [ -z "$targetLabel" ]; then 751 | getLabel "$mntDirTarget" 752 | msg "info: using default label" 753 | else 754 | msg "info: using label from partition $srcPart" 755 | fi 756 | label=1 # force labelling 757 | fi 758 | fi 759 | 760 | # get description if empty 761 | if [ -z "$targetDir" -a -z "$srcDir" -a -z "$description" ]; then 762 | readDescription 763 | description="${partDescription[$srcPart]}" # forces update of description 764 | msg "info: using description from partition $srcPart" 765 | fi 766 | 767 | if [ -z "$targetDir" ]; then 768 | # umount target partition 769 | umount "$mntDirTarget" && rm -fr "$mntDirTarget" 770 | fi 771 | 772 | if [ -z "$install" ]; then 773 | msg "info: copied system to $targetDevice" 774 | if [ -z "$targetDir" ]; then 775 | if [ -z "$switch" -a -z "$switchSelect" ]; then 776 | msg "info: use ${0##*/} with option '-s -t $targetDevice' to boot from new partition" 777 | else 778 | msg "info: reboot the system to start from $targetDevice" 779 | fi 780 | fi 781 | fi 782 | } 783 | 784 | # --- switch root-partition ------------------------------------------------ 785 | 786 | doSwitch() { 787 | if [ -z "$targetDevice" ]; then 788 | msg "error: no target partition selected" 789 | exit 3 790 | fi 791 | local rootDevice="$targetDevice" 792 | 793 | # check if new rootDevice is identical to current root-device 794 | # i.e. we are at most undoing a switch 795 | local currentRoot=$(getCurrentDevice NAME /) 796 | if [ "$currentRoot" == "$rootDevice" ]; then 797 | # we just have to update /boot from /_boot 798 | copyBoot "/_boot/" "$mp_part1" 799 | return 800 | else 801 | # backup /boot (or /boot/firmware) to current root/_boot 802 | copyBoot "$mp_part1/" "/_boot" 803 | fi 804 | 805 | # check if new root is currently mounted 806 | if mount | grep -qw "$rootDevice"; then 807 | msg "error: target partition currently mounted, aborting!" 808 | exit 3 809 | fi 810 | 811 | # mount new-root 812 | local mntNewRoot=`mktemp -d --tmpdir pi-boot-switch.XXXXXX` 813 | msg "info: mounting $rootDevice on $mntNewRoot" 814 | if ! mount "$rootDevice" "$mntNewRoot"; then 815 | msg "error: could not mount $rootDevice, aborting!" 816 | exit 3 817 | fi 818 | 819 | if [ ! -d "$mntNewRoot/_boot/" ]; then 820 | msg "error: $rootDevice has no /_boot directory, aborting!" 821 | umount "$mntNewRoot" && rm -fr "$mntNewRoot" 822 | exit 3 823 | fi 824 | 825 | # copy /new/_boot -> /boot or /boot/firmware 826 | copyBoot "$mntNewRoot/_boot/" "$mp_part1" 827 | 828 | # update /home if requested 829 | if [ "$updateHome" = "1" ]; then 830 | msg "info: updating /home on $targetDevice" 831 | rsync $verbose -a -H -A -X -S -x /home "$mntNewRoot" 832 | fi 833 | 834 | # umount /new 835 | msg "info: unmounting $rootDevice" 836 | umount "$mntNewRoot" && rm -fr "$mntNewRoot" 837 | 838 | msg "info: reboot the system to start from $rootDevice" 839 | } 840 | 841 | # --- reboot the system ---------------------------------------------------- 842 | 843 | doReboot() { 844 | msg "info: rebooting the system in $REBOOT_DELAY seconds" 845 | sleep "$REBOOT_DELAY" 846 | shutdown -r now & 847 | } 848 | 849 | # --- main program --------------------------------------------------------- 850 | 851 | setDefaults 852 | parseArguments "$@" 853 | checkArguments 854 | 855 | # execute operation(s) 856 | 857 | mp_part1=$(mountBoot) 858 | if [ -n "$info" ]; then 859 | doInfo 860 | else 861 | # preserve order of execution (start with copy) 862 | if [ -n "$copy" ]; then 863 | doCopy "/" || exit 3 864 | elif [ -n "$copyOther" ]; then 865 | doCopyOther || exit 3 866 | elif [ -n "$install" ]; then 867 | doInstall || exit 3 868 | fi 869 | [ -n "$switch" ] && doSwitch 870 | [ -n "$newBoot" ] && doNewBoot 871 | [ -n "$label" ] && doLabel 872 | [ -n "$description" ] && doDescription 873 | [ -n "$reboot" ] && doReboot 874 | fi 875 | 876 | exit 0 877 | -------------------------------------------------------------------------------- /tools/install: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # -------------------------------------------------------------------------- 3 | # Boot-Switcher for Raspberry Pi multiboot systems 4 | # 5 | # This script installs all necessary files. 6 | # 7 | # Author: Bernhard Bablok 8 | # License: GPL3 9 | # 10 | # Website: https://github.com/bablokb/pi-boot-switch 11 | # 12 | # -------------------------------------------------------------------------- 13 | 14 | # --- defaults used during installation ---------------------------------- 15 | 16 | PACKAGES="unzip rsync" 17 | PROJECT="pi-boot-switch" 18 | 19 | # --- basic packages ------------------------------------------------------ 20 | 21 | check_packages() { 22 | local p 23 | for p in "$@"; do 24 | echo -en "Checking $p ... " >&2 25 | dpkg -s "$p" 2>/dev/null | grep -q "Status.*ok" || return 0 26 | echo "ok" >&2 27 | done 28 | return 1 29 | } 30 | 31 | install_packages() { 32 | if [ -n "$PACKAGES" ] && check_packages $PACKAGES; then 33 | echo -e "[INFO] installing additional packages" 2>&1 34 | apt-get update 35 | apt-get -y install $PACKAGES 36 | fi 37 | } 38 | 39 | 40 | # --- install specific files ---------------------------------------------- 41 | 42 | install_files() { 43 | echo -e "[INFO] installing project files" 2>&1 44 | 45 | for f in `find $(dirname "$0")/../files/ -type f`; do 46 | cp -v "$f" "${f#*files}" 47 | chown root:root "${f#*files}" 48 | done 49 | chmod 744 /usr/local/sbin/pi-boot-switch 50 | } 51 | 52 | # --- main program -------------------------------------------------------- 53 | 54 | install_packages 55 | install_files 56 | --------------------------------------------------------------------------------