www.archive-org-2014.com » ORG » G » GRML

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 58 . Archive date: 2014-01.

  • Title:
    Original link path: /changelogs/README-0.4.txt
    (No additional info available in detailed archive for this subpage)

  • Title:
    Original link path: /changelogs/README-0.3.txt
    (No additional info available in detailed archive for this subpage)

  • Title:
    Original link path: /changelogs/README-0.2.txt
    (No additional info available in detailed archive for this subpage)

  • Title: grml.org - Download - Mirror List
    Descriptive info: Download - Mirror List.. NOTE:.. Please visit the.. download webpage.. if you don't need the full mirror list.. Download via bittorrent.. The torrent URLs are available at.. grml.. deb.. at.. Download via HTTP/FTP.. GeoIP.. (automatically try to figure out the best matching mirror):.. http://download.. grml.. org/.. Mirrors in Austria.. gd.. tuwien.. ac.. at (Vienna).. http://gd.. at//opsys/linux/grml/.. rsync://gd.. at/opsys/linux/grml/.. ftp://gd.. http://grml.. at//.. rsync://grml.. at/grml/.. mirror.. inode.. http://mirror.. at//data/grml/.. rsync://mirror.. at/mirror/grml/.. ftp://mirror.. at//grml/.. lagis..  ...   in Germany.. ftp.. fau.. de (Erlangen).. http://ftp.. de//grml/.. ftp://ftp.. gwdg.. de (Goettingen).. de//pub/linux/grml/.. rsync://ftp.. de/pub/linux/grml/.. halifax.. rwth-aachen.. de (Aachen).. de/grml/.. de.. leaseweb.. net (Frankfurt(?)).. net//grml/.. net/grml/.. netcologne.. de (Cologne).. Mirrors in Netherlands.. nl.. net (Haarlem, EvoSwitch DC).. Mirrors in United States of America.. rit.. edu (New York).. edu//grml/.. us.. net (Manassas, Virginia, PowerLoft DC).. If you are interested in providing a mirror or a bittorrent link for Grml please.. contact us.. /..

    Original link path: /download/mirrors/
    Open archive

  • Title: cheatcodes
    Descriptive info: cheatcodes..

    Original link path: /console/
    Open archive

  • Title:
    Descriptive info: The following packages from the Debian non-free section are included in this release Package: atmel-firmware ======================================================================== This Debian package is derived from atmel-firmware-1.. 2.. tar.. gz which is available on-line at: http://www.. thekelleys.. org.. uk/atmel/atmel-firmware-1.. gz The Debian package of atmel-firmware was created by Simon Kelley.. The bin files in the images were generated from header files included with the 2.. 1.. 1 release of the "Atmel drivers", released by Atmel corp in December 2002 and subsequent modifications, downloaded from atmelwlandriver.. sourceforge.. net The copyright on these files was modified (by Atmel corp) in November 2004 to the form shown below.. /***************************************************************************************/ /* Copyright (c) 2004 Atmel Corporation.. All Rights Reserved.. */ /* Redistribution and use of the microcode software ( Firmware ) is */ /* permitted provided that the following conditions are met: */ /* */ /* 1.. Firmware is redistributed in object code only; */ /* 2.. Any reproduction of Firmware must contain the above */ /* copyright notice, this list of conditions and the below */ /* disclaimer in the documentation and/or other materials */ /* provided with the distribution; and */ /* 3.. The name of Atmel Corporation may not be used to endorse */ /* or promote products derived from this Firmware without specific */ /* prior written consent.. */ /* */ /* DISCLAIMER: ATMEL PROVIDES THIS FIRMWARE "AS IS" WITH NO WARRANTIES OR */ /* INDEMNITIES WHATSOEVER.. ATMEL EXPRESSLY DISCLAIMS ANY EXPRESS, STATUTORY */ /* OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED */ /* WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND */ /* NON-INFRINGEMENT.. IN NO EVENT SHALL ATMEL BE LIABLE FOR ANY DIRECT, */ /* INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES */ /* (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR */ /* SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) */ /* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, */ /* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN */ /* ANY WAY OUT OF THE USE OF THIS FIRMWARE, EVEN IF ADVISED OF THE */ /* POSSIBILITY OF SUCH DAMAGE.. USER ACKNOWLEDGES AND AGREES THAT THE */ /* PURCHASE OR USE OF THE FIRMWARE WILL NOT CREATE OR GIVE GROUNDS FOR A */ /* LICENSE BY IMPLICATION, ESTOPPEL, OR OTHERWISE IN ANY INTELLECTUAL */ /* PROPERTY RIGHTS (PATENT, COPYRIGHT, TRADE SECRET, MASK WORK, OR OTHER */ /* PROPRIETARY RIGHT) EMBODIED IN ANY OTHER ATMEL HARDWARE OR FIRMWARE */ /* EITHER SOLELY OR IN COMBINATION WITH THE FIRMWARE.. */ /***************************************************************************************/ The atmel_fwl utility (perl and C verions) is Copyright (c) 2003 Simon Kelley and is distributed under the terms of the GNU General Public License This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 dated June, 1991.. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.. See the GNU General Public License for more details.. On Debian GNU/Linux systems, the text of the GNU general public license is available in the file /usr/share/common-licenses/GPL Package: bluez-firmware ======================================================================== This package was debianized by Edd Dumbill.. on Fri Nov 12 11:18:04 GMT 2004 It was downloaded from http://www.. bluez.. org/download.. html The BlueZ project has permission from Broadcom Corporation to distribute this firmware in conjunction with the BlueZ tools, available in Debian as bluez-utils, as long as the notice contained in /usr/share/doc/bluez-firmware/BCM-LEGAL.. txt accompanies the firmware.. This arrangement was made with BlueZ author Max Krasnyansky.. BCM firmware version 2.. 16 Copyright (c) 2000-2003 Broadcom Corporation Contact info: bluetooth_help@broadcom.. com Received: from enigma.. qualcomm.. com (enigma.. com [129.. 46.. 64.. 203]) by mail1.. com (8.. 12.. 1/8.. 1/1.. 0) with ESMTP id fB3MjfxX010506 for.. ; Mon, 3 Dec 2001 14:45:41 -0800 (PST) Received: from moria.. com (qualcomm.. com [199.. 106.. 114.. 68]) by enigma.. 11.. 3/1.. 0) with ESMTP id fB3Mjcun020569 for.. ; Mon, 3 Dec 2001 14:45:38 -0800 (PST) Received: from mms1.. broadcom.. com (mms1.. com [63.. 70.. 210.. 58]) by moria.. com with SMTP id OAA19783 for.. ; Mon, 3 Dec 2001 14:44:26 -0800 (PST) From: ochikubo@broadcom.. com Received: from 63.. 4 by mms1.. com with SMTP (Broadcom MMS-1 SMTP Relay (MMS v4.. 7)); Mon, 03 Dec 2001 14:45:21 -0800 X-Server-Uuid: 1e1caf3a-b686-11d4-a6a3-00508bfc9ae5 Received: from ltelsaochikubo ([10.. 13.. 17.. 128]) by mail-irva-1.. com (Post.. Office MTA v3.. 5.. 3 release 223 ID# 0-71992U7200L1200S0V35) with SMTP id com; Mon, 3 Dec 2001 14:45:34 -0800 To: "'Maksim Krasnyanskiy'".. cc: "'Tom Ramsthaler (E-mail)'".. , "'Scott Bibaud (E-mail)'".. , "'Daniel Hess (E-mail)'".. , "'Nick Kawaguchi (E-mail)'".. , "Lynn Couillard (E-mail)".. , "Robert Hulvey (E-mail)".. Subject: RE: Release of firmware with BlueZ port Date: Mon, 3 Dec 2001 14:38:08 -0800 Message-ID:.. X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.. 0.. 2416 (9.. 2910.. 0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.. 00.. 2462.. 0000 In-Reply-To:.. X-WSS-ID: 1012DF0B501255-01-01 X-UIDL: S+:"!4]]!!!gj!!c@]"! Status: RO Mime-Version: 1.. 0 Max, Good news.. We have Broadcom Corporate and Legal approval for release of our firmware as part of the BlueZ posting.. Send us a copy of it to load up when you have a chance (or let us know when its up and we will download it).. The BCM_LEGAL.. txt file should contain the following information: - - - - - - BCM firmware version 2.. 9 Copyright (c) 2000-2001 Broadcom Corporation Contact info: bluetooth_help@broadcom.. com BlueFW will have: BCM2033_md.. hex - BCM mini driver BCM2033_fw.. bin - BCM firmware BCM.. LEGAL.. txt - Legal info - - - - - - We are going to make another release of firmware in about 2 weeks and will definitely keep you in the loop.. Regards, Craig Package: firmware-atheros ======================================================================== The binary firmware may be downloaded from http://git.. kernel.. org/?p=linux/kernel/git/firmware/linux-firmware.. git The file ar9170.. fw was downloaded from http://www.. org/pub/linux/kernel/people/mcgrof/firmware/ar9170/2010-02-03/ Copyright (c) 2008-2010, Atheros Communications, Inc.. All rights reserved.. Redistribution.. Redistribution and use in binary form, without modification, are permitted provided that the following conditions are met: * Redistributions must reproduce the above copyright notice and the following disclaimer in the documentation and/or other materials provided with the distribution.. * Neither the name of Atheros Communications, Inc.. nor the names of its suppliers may be used to endorse or promote products derived from this software without specific prior written permission.. * No reverse engineering, decompilation, or disassembly of this software is permitted.. Limited patent license.. Atheros Communications, Inc.. grants a world-wide, royalty-free, non-exclusive license under patents it now or hereafter owns or controls to make, have made, use, import, offer to sell and sell ("Utilize") this software, but solely to the extent that any such patent is necessary to Utilize the software alone, or in combination with an operating system licensed under an approved Open Source license as listed by the Open Source Initiative at http://opensource.. org/licenses.. The patent license shall not apply to any other combinations which include this software.. No hardware per se is licensed hereunder.. DISCLAIMER.. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.. Package: firmware-bnx2 ======================================================================== The binary firmware may be downloaded from http://git.. git This file contains firmware data derived from proprietary unpublished source code, Copyright (c) 2004 - 2010 Broadcom Corporation.. Permission is hereby granted for the distribution of this firmware data in hexadecimal or equivalent format, provided this copyright notice is accompanying it.. Package: firmware-bnx2x ======================================================================== The binary firmware may be downloaded from http://git.. git Copyright (c) 2007-2010 Broadcom Corporation This file contains firmware data derived from proprietary unpublished source code, Copyright (c) 2007-2009 Broadcom Corporation.. Package: firmware-brcm80211 ======================================================================== The binary firmware may be downloaded from http://git.. git SOFTWARE LICENSE AGREEMENT Unless you and Broadcom Corporation (“Broadcom”) execute a separate written software license agreement governing use of the accompanying software, this software is licensed to you under the terms of this Software License Agreement (“Agreement”).. ANY USE, REPRODUCTION OR DISTRIBUTION OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS AGREEMENT.. 1.. DEFINITIONS.. “Broadcom Product” means any of the proprietary integrated circuit product(s) sold by Broadcom with which the Software was designed to be used, or their successors.. “Licensee” means you or if you are accepting on behalf of an entity then the entity and its affiliates exercising rights under, and complying with all of the terms of this Agreement.. 3.. “Software” shall mean that software made available by Broadcom to Licensee in binary code form with this Agreement.. 2.. LICENSE GRANT; OWNERSHIP 2.. License Grants.. Subject to the terms and conditions of this Agreement, Broadcom hereby grants to Licensee a non-exclusive, non-transferable, royalty-free license (i) to use and integrate the Software in conjunction with any other software; and (ii) to reproduce and distribute the Software complete, unmodified and as provided by Broadcom, and only for use with a Broadcom Product.. Restriction on Modification.. Licensee may not make any modifications to the Software.. Restriction on Distribution.. Licensee shall only distribute the Software under the terms of this Agreement and a copy of this Agreement accompanies such distribution.. 4.. Proprietary Notices.. Licensee shall not remove, efface or obscure any copyright or trademark notices from the Software.. Licensee shall include reproductions of the Broadcom copyright notice with each copy of the Software, except where such Software is embedded in a manner not readily accessible to the end user.. Licensee acknowledges that any symbols, trademarks, tradenames, and service marks adopted by Broadcom to identify the Software belong to Broadcom and that Licensee shall have no rights therein.. Ownership.. Broadcom shall retain all right, title and interest, including all intellectual property rights, in and to the Software.. Licensee hereby covenants that it will not assert any claim that the Software created by or for Broadcom infringe any intellectual property right owned or controlled by Licensee; provided however, the foregoing shall not apply in case the Agreement is terminated.. 6.. No Other Rights Granted; Restrictions.. Apart from the license rights expressly set forth in this Agreement, Broadcom does not grant and Licensee does not receive any ownership right, title or interest nor any security interest or other interest in any intellectual property rights relating to the Software, nor in any copy of any part of the foregoing.. No license is granted to Licensee in any human readable code of the Software (source code).. Licensee shall not (i) use, license, sell or otherwise distribute the Software except as provided in this Agreement, (ii) attempt to modify in any way, reverse engineer, decompile or disassemble any portion of the Software; or (iii) use the Software or other material in violation of any applicable law or regulation, including but not limited to any regulatory agency, such as FCC, rules.. 3.. NO WARRANTY OR SUPPORT 3.. No Warranty.. THE SOFTWARE IS OFFERED “AS IS,” AND BROADCOM GRANTS AND LICENSEE RECEIVES NO WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, BY STATUTE, COMMUNICATION OR CONDUCT WITH LICENSEE, OR OTHERWISE.. BROADCOM SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A SPECIFIC PURPOSE OR NONINFRINGEMENT CONCERNING THE SOFTWARE OR ANY UPGRADES TO OR DOCUMENTATION FOR THE SOFTWARE.. WITHOUT LIMITATION OF THE ABOVE, BROADCOM GRANTS NO WARRANTY THAT THE SOFTWARE IS ERROR-FREE OR WILL OPERATE WITHOUT INTERRUPTION, AND GRANTS NO WARRANTY REGARDING ITS USE OR THE RESULTS THEREFROM INCLUDING, WITHOUT LIMITATION, ITS CORRECTNESS, ACCURACY OR RELIABILITY.. No Support.. Nothing in this agreement shall obligate Broadcom to provide any support for the Software.. Broadcom may, but shall be under no obligation to, correct any defects in the Software and/or provide updates to licensees of the Software.. Licensee shall make reasonable efforts to promptly report to Broadcom any defects it finds in the Software, as an aid to creating improved revisions of the Software.. Dangerous Applications.. The Software is not designed, intended, or certified for use in components of systems intended for the operation of weapons, weapons systems, nuclear installations, means of mass transportation, aviation, life-support computers or equipment (including resuscitation equipment and surgical implants), pollution control, hazardous substances management, or for any other dangerous application in which the failure of the Software could create a situation where personal injury or death may occur.. Licensee understands that use of the Software in such applications is fully at the risk of Licensee.. 4.. TERM AND TERMINATION 4.. Termination.. This Agreement will automatically terminate if Licensee fails to comply with any of the terms and conditions hereof.. In such event, Licensee must destroy all copies of the Software and all of its component parts.. Effect Of Termination.. Upon any termination of this Agreement, the rights and licenses granted to Licensee under this Agreement shall immediately terminate.. Survival.. The rights and obligations under this Agreement which by their nature should survive termination will remain in effect after expiration or termination of this Agreement.. 5.. CONFIDENTIALITY 5.. Obligations.. Licensee acknowledges and agrees that any documentation relating to the Software, and any other information (if such other information is identified as confidential or should be recognized as confidential under the circumstances) provided to Licensee by Broadcom hereunder (collectively, “Confidential Information”) constitute the confidential and proprietary information of Broadcom, and that Licensee’s protection thereof is an essential condition to Licensee’s use and possession of the Software.. Licensee shall retain all Confidential Information in strict confidence and not disclose it to any third party or use it in any way except under a written agreement with terms and conditions at least as protective as the terms of this Section.. Licensee will exercise at least the same amount of diligence in preserving the secrecy of the Confidential Information as it uses in preserving the secrecy of its own most valuable confidential information, but in no event less than reasonable diligence.. Information shall not be considered Confidential Information if and to the extent that it: (i) was in the public domain at the time it was disclosed or has entered the public domain through no fault of Licensee; (ii) was known to Licensee, without restriction, at the time of disclosure as proven by the files of Licensee in existence at the time of disclosure; or (iii) becomes known to Licensee, without restriction, from a source other than Broadcom without breach of this Agreement by Licensee and otherwise not in violation of Broadcom’s rights.. Return of Confidential Information.. Notwithstanding the foregoing,  ...   WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS.. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.. Files: linux-nonfree/dvb-usb-dib0700-1.. 20.. fw Copyright: 2009, DiBcom License: Binary redistribution (DiBcom) Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.. Files: linux-nonfree/e100/* Copyright: 1999-2001, Intel Corporation License: BSD (Intel) All rights reserved.. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.. Neither the name of Intel Corporation nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.. IN NO EVENT SHALL CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.. Files: linux-nonfree/ene-ub6250/* Copyright: 2011, ENE Technology Inc.. License: Binary redistribution (ENE) Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.. Files: linux-nonfree/kaweth/* Copyright: 1999, Kawasaki LSI.. License: BSD 4-clause (Kawasaki LSI) Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1.. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Kawasaki LSI.. Neither the name of the company nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.. THIS SOFTWARE IS PROVIDED BY KAWASAKI LSI ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.. IN NO EVENT SHALL KAWASAKI LSI BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.. Files: linux-nonfree/matrox/* Copyright: 1999, Matrox Graphics Inc.. License: Binary redistribution (Matrox) All Rights Reserved.. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:.. The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.. IN NO EVENT SHALL MATROX GRAPHICS INC.. , OR ANY OTHER CONTRIBUTORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.. Files: linux-nonfree/mts_*.. fw Copyright: 2005, Multi-Tech Systems, Inc.. License: Binary redistribution (MTS) All firmware components are redistributable in binary form.. Files: linux-nonfree/r128/r128_cce.. bin, linux-nonfree/radeon/*_cp.. bin, linux-nonfree/radeon/R600_me.. bin, linux-nonfree/radeon/R600_pfp.. bin, linux-nonfree/radeon/RS780_*.. bin, linux-nonfree/radeon/RV*.. bin Copyright: 2000-2009, Advanced Micro Devices, Inc.. License: Binary redistribution (AMD permissive) All Rights Reserved.. The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software.. IN NO EVENT SHALL IN NO EVENT SHALL THE COPYRIGHT OWNER(S) AND/OR ITS SUPPLIERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.. Files: linux-nonfree/radeon/CEDAR_*.. bin, linux-nonfree/radeon/CYPRESS_*.. bin, linux-nonfree/radeon/JUNIPER_*.. bin, linux-nonfree/radeon/R600_rlc.. bin, linux-nonfree/radeon/R700_rlc.. bin, linux-nonfree/radeon/REDWOOD_*.. bin, Copyright: 2009-2010, Advanced Micro Devices, Inc.. License: Binary redistribution (AMD restrictive) All rights reserved.. REDISTRIBUTION: Permission is hereby granted, free of any license fees, to any person obtaining a copy of this microcode (the "Software"), to install, reproduce, copy and distribute copies, in binary form only, of the Software and to permit persons to whom the Software is provided to do the same, provided that the following conditions are met:.. No reverse engineering, decompilation, or disassembly of this Software is permitted.. Redistributions must reproduce the above copyright notice, this permission notice, and the following disclaimers and notices in the Software documentation and/or other materials provided with the Software.. DISCLAIMER: THE USE OF THE SOFTWARE IS AT YOUR SOLE RISK.. THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY KIND AND COPYRIGHT HOLDER AND ITS LICENSORS EXPRESSLY DISCLAIM ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.. COPYRIGHT HOLDER AND ITS LICENSORS DO NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE.. THE ENTIRE RISK ASSOCIATED WITH THE USE OF THE SOFTWARE IS ASSUMED BY YOU.. FURTHERMORE, COPYRIGHT HOLDER AND ITS LICENSORS DO NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF THE SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, CURRENTNESS, OR OTHERWISE.. DISCLAIMER: UNDER NO CIRCUMSTANCES INCLUDING NEGLIGENCE, SHALL COPYRIGHT HOLDER AND ITS LICENSORS OR ITS DIRECTORS, OFFICERS, EMPLOYEES OR AGENTS ("AUTHORIZED REPRESENTATIVES") BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, AND THE LIKE) ARISING OUT OF THE USE, MISUSE OR INABILITY TO USE THE SOFTWARE, BREACH OR DEFAULT, INCLUDING THOSE ARISING FROM INFRINGEMENT OR ALLEGED INFRINGEMENT OF ANY PATENT, TRADEMARK, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT EVEN IF COPYRIGHT HOLDER AND ITS AUTHORIZED REPRESENTATIVES HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.. IN NO EVENT SHALL COPYRIGHT HOLDER OR ITS AUTHORIZED REPRESENTATIVES TOTAL LIABILITY FOR ALL DAMAGES, LOSSES, AND CAUSES OF ACTION (WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE) OR OTHERWISE) EXCEED THE AMOUNT OF US$10.. Notice: The Software is subject to United States export laws and regulations.. You agree to comply with all domestic and international export laws and regulations that apply to the Software, including but not limited to the Export Administration Regulations administered by the U.. S.. Department of Commerce and International Traffic in Arm Regulations administered by the U.. Department of State.. These laws include restrictions on destinations, end users and end use.. Files: linux-nonfree/tehuti/bdx.. bin Copyright: 2007, Tehuti Networks Ltd.. Files: linux-nonfree/tigon/tg3*.. bin Copyright: 2000-2003, Broadcom Corporation.. Files: linux-nonfree/v4l-cx*.. fw License: Binary redistribution (Conexant) Conexant grants permission to use and redistribute these firmware files for use with Conexant devices, but not as a part of the Linux kernel or in any other form which would require these files themselves to be covered by the terms of the GNU General Public License.. These firmware files are distributed in the hope that they will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.. Package: firmware-myricom ======================================================================== The binary firmware may be downloaded from http://git.. git Copyright (c) 2006-2010, Myricom Inc.. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1.. Neither the name of the Myricom Inc, nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.. Package: firmware-netxen ======================================================================== The binary firmware may be downloaded from http://git.. git Copyright (c) 2003-2010 QLogic Corporation QLogic Linux Intelligent Ethernet (3000 and 3100 Series) Adapter Firmware Redistribution and use in binary form, without modification, for use in conjunction with QLogic authorized products is permitted provided that the following conditions are met: 1.. The name of QLogic Corporation may not be used to endorse or promote products derived from this software without specific prior written permission.. REGARDLESS OF WHAT LICENSING MECHANISM IS USED OR APPLICABLE,THIS PROGRAM IS PROVIDED BY QLOGIC CORPORATION "AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.. USER ACKNOWLEDGES AND AGREES THAT USE OF THIS PROGRAM WILL NOT CREATE OR GIVE GROUNDS FOR A LICENSE BY IMPLICATION, ESTOPPEL, OR OTHERWISE IN ANY INTELLECTUAL PROPERTY RIGHTS (PATENT, COPYRIGHT, TRADE SECRET, MASK WORK, OR OTHER PROPRIETARY RIGHT) EMBODIED IN ANY OTHER QLOGIC HARDWARE OR SOFTWARE EITHER SOLELY OR IN COMBINATION WITH THIS PROGRAM.. Package: firmware-qlogic ======================================================================== The files in this package were downloaded from http://git.. git The following notice applies to qlogic/1040.. bin, qlogic/1280.. bin, qlogic/12160.. bin: Copyright: Copyright (C) 1995, 1996, 1997, 1998, 1999, 2000 QLogic, Inc.. License: Redistribution and use in source and binary forms are permitted provided that the following conditions are met: 1.. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.. The following notice applies to sd7220.. fw: Copyright: Copyright (c) 2007, 2008 QLogic Corporation.. License: The OpenIB.. org BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.. The following notice applies to ql2100_fw.. bin, ql2200_fw.. bin, ql2300_fw.. bin, ql2322_fw.. bin, ql2400_fwbin, ql2500_fw.. bin: Copyright: Copyright (C) 2003-2006 QLogic Corporation License: You may redistribute the hardware specific firmware binary file under the following terms: 1.. Redistribution of source code (only if applicable), must retain the above copyright notice, this list of conditions and the following disclaimer.. The name of QLogic Corporation may not be used to endorse or promote products derived from this software without specific prior written permission REGARDLESS OF WHAT LICENSING MECHANISM IS USED OR APPLICABLE, THIS PROGRAM IS PROVIDED BY QLOGIC CORPORATION "AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.. Package: firmware-ralink ======================================================================== The binary firmware may be downloaded from http://git.. git Copyright (c) 2007, Ralink Technology Corporation All rights reserved.. * Neither the name of Ralink Technology Corporation nor the names of its suppliers may be used to endorse or promote products derived from this software without specific prior written permission.. Ralink Technology Corporation grants a world-wide, royalty-free, non-exclusive license under patents it now or hereafter owns or controls to make, have made, use, import, offer to sell and sell ("Utilize") this software, but solely to the extent that any such patent is necessary to Utilize the software alone, or in combination with an operating system licensed under an approved Open Source license as listed by the Open Source Initiative at http://opensource.. Package: firmware-realtek ======================================================================== The binary firmware may be downloaded from http://git.. git Files: realtek/rtl_nic/* Copyright: 2010-2013, Realtek Semiconductor Corporation License: Binary redistribution (Realtek permissive) Permission is hereby granted for the distribution of this firmware data in hexadecimal or equivalent format, provided this copyright notice is accompanying it.. Files: realtek/RTL8192E/*, realtek/RTL8192SU/*, realtek/rtlwifi/* Copyright: 2009-2010, Realtek Semiconductor Corporation License: Binary redistribution (Realtek restrictive) All rights reserved.. * Neither the name of Realtek Semiconductor Corporation nor the names of its suppliers may be used to endorse or promote products derived from this software without specific prior written permission.. Realtek Semiconductor Corporation grants a world-wide, royalty-free, non-exclusive license under patents it now or hereafter owns or controls to make, have made, use, import, offer to sell and sell ("Utilize") this software, but solely to the extent that any such patent is necessary to Utilize the software alone, or in combination with an operating system licensed under an approved Open Source license as listed by the Open Source Initiative at http://opensource.. Package: libertas-firmware ======================================================================== This package was debianized by Andres Salomon.. on Thu, 14 Feb 2008 21:45:25 +0000 The 8388 and 8686 firmware blobs were downloaded from.. , and have the following authors/copyright/license: Authors: OLPC and Marvell Corporation Copyright (c) 2006, One Laptop per Child and Marvell Corporation.. The rest of the firmware blobs were downloaded from.. , and have the following authors/copyright/license: Authors: Marvell International Ltd.. Copyright (c) Marvell International Ltd.. Package: zd1211-firmware ======================================================================== This package was debianized by Robert Jordens.. on Mon Sep 12 21:22:22 CEST 2005.. The current maintainer is Christian Kastner.. Files related to the Debian packaging are: Copyright © 2010 Christian Kastner.. Copyright © 2008-2010 Bart Martens.. Copyright © 2007 Joey Hess.. Copyright © 2005-2006 Robert Jordens.. These files are distributed under the GPL version 2 (see below).. Download site for the current firmware: http://sourceforge.. net/projects/zd1211/ Authors: firmware images generated by M.. Kiesel from the original source original source from: ZyDAS http://www.. zydas.. com.. tw (now defunct) Copyright: 2002, 2003, 2004, 2005, 2006 ZyDAS Inc.. 2006, 2007 Atheros Communications, Inc.. The original header files are distributed under the GPL version 2 or later.. The text of the GPL can be found at /usr/share/common-licenses/GPL-2.. They are at least freely distributable.. But since there is no freely available (under e.. g.. the GPL) source code for the firmware, this firmware must be considered non-free..

    Original link path: /files/grml32-full_2013.09/nonfree-licenses.txt
    Open archive

  • Title: grml2usb(8)
    Descriptive info: grml2usb(8).. Table of Contents.. JavaScript must be enabled in your browser to display the table of contents.. Name.. grml2usb - install grml ISO(s) on usb device for booting.. Synopsis.. grml2usb [ options ] ISO[s] device.. Important! The grml team does not take responsibility for loss of any data!.. Introduction.. grml2usb installs grml on a given partition of your usb device and makes it bootable.. It provides multi-iso support, meaning you can specify several grml ISOs on the command line at once and select the grml flavour you would like to boot on the bootprompt then.. Note that the.. first.. ISO specified on the grml2usb command line will become the default one (that s the one that will boot when just pressing enter on the bootprompt or wait until the boot timeout matches).. By default a compatible master boot record (MBR) is installed on the device (being for example /dev/sdX when executing.. grml2usb grml.. iso /dev/sdX1.. ) and syslinux is being used as default bootloader.. Avoid installation of the default MBR using the.. --skip-mbr.. option or if you encounter any problems with the default MBR consider using.. --syslinux-mbr.. instead.. Options.. The ISO[s] should be the path to one or multiple grml-ISOs and/or the path to the currently running live-system (being /lib/live/mount/medium).. The device either might be a device name like /dev/sdX1 or a directory.. When specifying a device name the device is mounted automatically.. When specifying a directory grml2usb is assuming that you did set up a bootloader on your own (or don t need one) and a bootloader won t be installed automatically.. The following options are supported:.. --bootoptions=.. Use specified bootoptions as default.. To use flavour name as a argument for a boot parameter use %flavour which will be expanded to the flavour name.. To add multiple bootoptions you can specify the option multiple time.. --bootloader-only.. Do.. not.. copy files but instead just install a bootloader.. Note that the boot addons are copied to /boot/addons at this stage as well.. If you want to skip copying the boot addons consider using the --skip-addons option.. --copy-only.. Copy files only but do.. install a bootloader.. --dry-run.. Avoid executing commands, instead show what would be executed.. Warning: please notice that the ISO has to be mounted anyway, otherwise identifying the grml flavour would not be possible.. --fat16.. Format specified partition with FAT16.. Important:.. this will destroy any existing data on the specified partition!.. --force.. Force any (possible dangerous) actions requiring manual interaction (like --fat16).. --grub.. Install grub bootloader instead of (default) syslinux.. --grub-mbr.. Install grub into MBR (Master Boot Record) instead of PBR (Partition Boot Record).. Check out.. the.. mbr-vs-pbr.. section in the FAQ of this document.. for further details.. --help.. Display usage information and exit.. --mbr-menu.. Install master boot record (MBR) with integrated boot menu: interactively choose the partition to boot from, with a timeout to load the default partition, or boot from floppy.. When NOT using the --mbr-menu option a MBR with LBA and large disc support but without an integrated boot menu is installed (so it s not visible at all but instead directly jumps to the bootloader - being grub or syslinux).. Note: This options is available only when using the default MBR and won t have any effect if you re using the.. option.. --quiet.. Do not output anything but just errors on console.. --skip-addons.. Do not install /boot/addons/ files (like dos, grub, memdisk, ).. --remove-bootoption=.. Remove specified bootoption (could be a regex) from existing boot options.. Use multiple entries for removing different bootoptions at once.. --skip-grub-config.. Skip generation of grub configuration files.. By default the configuration files for syslinux.. and.. grub will be written so you ve a working configuration file no matter whether you re using grub or syslinux as bootloader.. Do not touch/install the master boot record (MBR).. --skip-syslinux-config.. Skip generation of syslinux configuration files.. --syslinux.. This option is deprecated and is being left only for backwards compatibility reasons.. Syslinux is the default bootloader of grml2usb and therefore the.. option doesn t have any effects.. If you do not want to use syslinux as bootloader consider using the.. Install syslinux' master boot record (MBR, which is booting from the partition with the "active" flag set) instead of the default one.. If you encounter any problems with the default MBR you can try using the syslinux MBR instead.. If that works for you please.. let us know.. so we can adjust our default MBR accordingly.. -v.. ,.. --version.. Return version and exit.. --verbose.. Enable verbose mode.. Developers Corner.. Directory layout on usb device.. boot/ - |-- addons/ | |-- allinone.. img [grub - all in one image] | |-- bsd4grml/ [MirBSD] | |-- balder10.. imz [FreeDOS] | |-- memdisk [chainloading helper] | |-- memtest [memtest86+] |-- release/ | |-- grml/ | | |-- linux26 [Kernel] | | |-- initrd.. gz [initramfs] | |-- grml64 | | |-- linux26 [Kernel] | | |-- initrd.. gz [initramfs] | |-- grml-medium | | |-- linux26 [.. ] | | |-- initrd.. gz | |-- grml64-medium | | |-- linux26 | | |-- initrd.. gz | |-- grml-small | | |-- linux26 | | |-- initrd.. gz | `-- grml64-small | |-- linux26 | |-- initrd.. gz |-- grub/ | |-- grml.. png [graphical bootsplash background image for grub2] | |-- grub.. cfg [configuration file for grub2] | |-- menu.. lst [configuration file for grub1] | |-- splash.. xpm.. gz [splash screen for grub1] `-- syslinux/ |-- grml.. png [graphical bootsplash background image for syslinux] |-- syslinux.. cfg [main configuration file for syslinux] `-- [.. ] [several further config files for syslinux].. grml/ |-- grml2usb.. txt [not yet implemented] |--  ...   all.. grml2usb provides multi-ISO support, support for adding default bootoptions and selecting the bootloader (syslinux vs.. grub) without having to manually touch the ISO at all.. What s grml2iso?.. grml2iso is a script which uses grml2usb to generate a multiboot ISO out of several grml ISOs.. See.. man grml2iso.. Why is there a menu.. lst and a grub.. cfg inside /boot/grub/?.. grml2usb supports grub version 1 (grub1) as well as grub version 2 (grub2).. Whereas grub1 uses menu.. lst the new version grub2 needs grub.. cfg.. Providing both files allows grml2usb to install grub on the target device no matter which grub version is available on the host where grml2usb is executed on.. grub-install fails with 'The file.. /boot/grub/stage1 not read correctly"?!.. Check whether the partition has the right partition type.. For example do NOT use FAT16 (partition type 6) when using a ext3 filesystem on the partition but instead use the correct partition type (.. 83.. - Linux) then.. grub-install complains about /sbin/grub-install and/or xfs_freeze?!.. The following message:.. You shouldn't call /sbin/grub-install.. Please call /usr/sbin/grub-install instead! xfs_freeze: specified file ["/tmp/tmpqaBK6z/boot/grub"] is not on an XFS filesystem.. This is "normal".. grub-install sends those messages to stderr.. To avoid hiding any possible real error messages grml2usb doesn t ignore those messages.. 8.. grub-install complains about /boot/grub/device.. map?!.. grub-probe: error: Cannot open `/boot/grub/device.. map'.. This is "normal" (at least with grub1).. This isn t a problem, because the device.. map file will be generated on the target device anyway.. 9.. grub-install complains about a unary operator?!.. '/usr/sbin/grub-install: line 374: [: =: unary operator expected'.. Just ignore it.. (It usually doesn t appear on the second invocation on the same device.. ).. 10.. grub-install fails with grub-probe: error: unknown filesystem?!.. grub-probe: error: unknown filesystem Auto-detection of a filesystem module failed.. Please specify the module with the option `--modules' explicitly.. usually means that the device partition table says something else than the filesystem on the device.. For example using FAT16 as filesystem type and using FAT32 as filesystem on the partition will not work.. Either set filesystem type to FAT32 or format the partition using FAT16.. It is essential that device partition table and filesystem use the same filesystem type.. grub-setup fails after Attempting to install GRUB to a partition instead of the MBR?!.. grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR.. This is a BAD idea.. grub-setup: warn: Embedding is not possible.. GRUB can only be installed in this setup by using blocklists.. However, blocklists are UNRELIABLE and its use is discouraged.. grub-setup: error: Cannot read `/grub/core.. img' correctly.. appears when using grub2 versions older than 1.. 98 as those version introduced a regression which avoids that grub is being installed into a partition (PBR, Partition Boot Record) instead of MBR (Master Boot Record).. To work around this issue you can either 1) upgrade to grub versions =1.. 98, 2) install grub into the MBR (Master Boot Record) using the.. option of grml2usb or 3) switch to syslinux as bootmanager (just drop the.. option).. I m getting something like "Error: /usr/share/grml2usb/grub/splash.. gz can not be read"!?.. Looks like you ve only the grml2usb script itself available.. Please make sure you ve the grml2usb Debian package installed.. The most resent stable version is available via.. If you do not have a Debian system please see section.. in this FAQ.. Why do I have to use a FAT16/FAT32 filesystem?.. Syslinux (currently) does not support any other filesystems besides FAT16/FAT32 (though that s a sane default if you want to share your files with other (operating) systems).. If you want to use a different filesystem (like ext2/3) use the bootloader grub instead using grml2usb s.. FAT32 is supported since syslinux version 3.. 14.. Addons Hardware Detection Tool freezes.. This usually means that the machine you ran grml2usb on had syslinux 3.. x installed.. The version of hdt (Hardware detection tool) shipping with Grml 2010.. 12 and newer requires syslinux 4.. x.. 15.. I think I ve got a really cool idea!.. Great! Please check out.. the TODO file.. Feel free to.. report your wishes to the author.. Patches highly appreciated.. 16.. I ve problems with booting from USB.. I ve found a bug!.. Please.. report it to the author.. Please provide usage examples and output of your grml2usb commandline (consider using the "--verbose" option).. 8.. Usage examples.. # grml2usb /home/grml/grml_2013.. Install specified ISO on device /dev/sdX1.. iso /home/grml/grml_small_2013.. Install specified ISOs on device /dev/sdX1 for multibooting ISOs.. # grml2usb /lib/live/mount/medium /dev/sdX1.. Install currently running Grml live system on device /dev/sdX1.. # grml2usb /lib/live/mount/medium /home/grml/grml_2013.. Install currently running Grml live system and the specified ISO on device /dev/sdX1 for multibooting.. # grml2usb --fat16 /home/grml/grml_2013.. Install specified ISO on device /dev/sdX1 and format partition /dev/sdX1 with FAT16 filesystem.. # grml2usb --grub --grub-mbr /home/grml/grml_2013.. Install specified ISO on device /dev/sdX1 and use grub as bootloader (instead of syslinux being the default) and install a master boot record (MBR) to the MBR of /dev/sdX.. # grml2usb --bootoptions="lang=de ssh=mysecret" grml_2013.. iso /dev/sdX1 # grml2usb --bootoptions="lang=de" --bootoptions="ssh=mysecret" grml_2013.. Install specified ISO on device /dev/sdX1 and use "lang=de ssh=mysecret" as default bootoptions.. # grml2usb --remove-bootoption="vga=791" --remove-bootoption="nomce" grml_2013.. Install specified ISO on device /dev/sdX1 remove vga=791 and nomce from existing bootoptions.. # grml2usb --bootoptions="persistent-path=%flavour_name" grml64_2010.. 04.. iso grml_2010.. Install specified Isos on device /dev/sdx and add parameter persisten-path to every menu entry.. %flavour_name will be expanded to the flavour of the specific iso, e.. grml64 and grml.. 9.. Online Ressources.. Check out the.. grml2usb webpage.. and the.. grml2usb git repository.. 10.. Bugs.. Please report feedback, bugreports and wishes.. to the author.. 11.. Author.. Michael Prokop.. mika@grml.. Last updated 2013-01-10 13:55:49 CET..

    Original link path: /grml2usb/
    Open archive

  • Title: grml-debootstrap(8)
    Descriptive info: grml-debootstrap(8).. grml-debootstrap - wrapper around debootstrap for installing plain Debian.. grml-debootstrap [.. options.. ].. grml-debootstrap is a wrapper suite around debootstrap (and cdebootstrap if you want) for installing a plain Debian system (e.. via Grml) very fast and easy.. All you have to do is adjust a few variables in the configuration file /etc/debootstrap/config or specify some command line options and invoke grml-debootstrap.. If invoked without any configuration modifications or command line options a dialog based frontend will be available to control some basic configuration options.. A plain and base Debian system will be installed on the given device, directory or virtual image file then.. Customization of this process is possible as well.. The Grml team does not take responsibility for loss of any data!.. Options and environment variables.. --arch.. architecture.. Set target architecture you want to install.. Defaults to the architecture you are currently running.. If you re running an amd64 kernel and want to deploy an i386 system use this option.. Note: deploying amd64 from an i386 kernel does.. work.. Example: ".. --arch i386.. ".. --bootappend.. appendline-for-the-kernel.. Specify appendline for the kernel.. E.. ".. pci=nomsi.. -c.. --config.. file.. Use specified configuration file, defaults to /etc/debootstrap/config.. --chroot-scripts.. directory.. Execute chroot scripts from specified directory.. This allows customisation of the chroot setup, the executable script(s) present in the given directory are executed at the end of the chroot procedure.. Default directory: /etc/debootstrap/chroot-scripts/.. -d.. --confdir.. path.. Place of configuration files for debootstrap, defaults to /etc/debootstrap.. --debconf.. Use specified file for preseeding Debian packages instead of using the default confdir /debconf-selections.. --debopt.. params.. Extra parameters passed to the debootstrap command.. --filesystem.. filesystem.. Filesystem that should be created when installing to a partition.. If unset defaults to ext3.. Valid values are all filesystems that can be created through mkfs.. Skip user acknowledgement and do not prompt for user input.. --grmlrepos.. Enable Grml.. org s Debian repository (.. http://deb.. ) via the /etc/apt/sources.. list.. d/grml.. list configuration file.. This provides the option to install Debian packages from Grml s repository.. device.. Device where grub should be installed to.. Note that only the MBR (master boot record) can be used (/dev/sda, /dev/sdb, ).. Partitions (like /dev/sda1, /dev/sdb2, ) are NOT supported because grub2 doesn t support installation into the PBR (partition boot record) anymore.. Usage example:.. --grub /dev/sda.. Note: just do not set this option to avoid installation of grub.. -h.. Show summary of options and exit.. --hostname.. hostname.. Use specified hostname instead of the default (being.. -i.. --iso.. /mntpoint.. Specify mount point where you have a Debian ISO mounted loopback.. Using this option instead of the mirror option gives you the possibility to install the base-system without network access.. Make sure you mounted the according Debian-ISO to the given.. See section.. for a demonstration.. --keep_src_list.. Do not overwrite user provided /etc/apt/sources.. -m.. --mirror.. URL.. Specify mirror which should be used for apt-get/aptitude.. Corresponding with configuration variable MIRROR.. --nodebootstrap.. Skip debootstrap, only do configuration to the target.. --nopackages.. Skip installation of packages defined in /etc/debootstrap/packages.. --nopassword.. Do not prompt for the root password.. Note: Use the.. --password.. option if you want to set the root password during an automatic installation but don t want to use the interactive dialog.. -p.. --mntpoint.. Specify mount point that should be used for mounting the target system.. Corresponding with configuration variable MNTPOINT.. Note: this option has no effect if option -t is given and represents a directory.. --packages.. Use specified file as list for packages that should be installed instead of the default package list file confdir /packages.. password.. Use specified password as password for user root.. Use with caution, as your command line might be visible in the process list and the shell history.. It s meant for automatic installation only.. -r.. --release.. releasename.. Specify release of new Debian system.. Supported releases names: lenny, squeeze, wheezy (note: requires current version of debootstrap) and sid.. Corresponding with configuration variable RELEASE.. --pre-scripts.. Execute scripts from specified directory before executing the chroot script.. This allows customisation of the system before the chroot has been set up.. The environment variable $MNTPOINT is available inside the scripts for direct access of the chroot.. Default directory: /etc/debootstrap/pre-scripts/.. --scripts.. Execute scripts from specified directory.. This allows customisation of the system after the chroot has been set up.. Default directory: /etc/debootstrap/scripts/.. -t.. --target.. target.. Target partition (/dev/ )  ...   Main configuration file.. You have to adjust it according to your needs if you want to execute grml-debootstrap in the non-interactive mode without any special command line arguments.. /etc/debootstrap/chroot-script.. The script executed within the new Debian system as soon as the main system has been installed via [c]debootstrap.. /etc/debootstrap/locale.. gen.. Defines the default locales used for generating locales via locale-gen.. /etc/debootstrap/packages.. Defines the software packages which should be installed in the new Debian system by default.. /etc/debootstrap/extrapackages/.. Debian Packages dropped in this directory will be installed into the new Debian system by default (Control variable: EXTRAPACKAGES).. /etc/debootstrap/stages/.. The default directory for storing information about executed stages.. Every single function of grml-debootstrap will write.. done.. to the stages directory into a file named as the function itself if it has been executed successfully.. You can adjust the location of the directory via configuration variable STAGES via /etc/debootstrap/config.. Please notice that you have to remove the stages directory on your own if you want to re-execute grml-debootstrap after running it successfully once.. This should avoid recurrent execution by error of grml-debootstrap (which might delete present data).. Customization.. You can control execution of grml-debootstrap via adjusting /etc/debootstrap/config for some main stuff or via setting some selected variables via command line.. The packages which should be installed in the new Debian system can be defined via the file /etc/debootstrap/packages.. If you want to put existing files to the new Debian system you can place them into the (by default non-existing) directories boot, etc, share, usr and var in /etc/debootstrap/.. Every existing directory will be copied to the new Debian system then.. If you want to install additional packages that are not available via the Grml or Debian mirror drop them into /etc/debootstrap/extrapackages and make sure that EXTRAPACKAGES is set to "yes".. Automatic installation.. If environment variable AUTOINSTALL is set grml-debootstrap can be executed in a full automatic mode.. While this mode isn t really useful for interactive execution (just configure /etc/debootstrap/configure or specify the relevant variables on the command line instead) it is meant for use via boot option debian2hd on the Grml live system.. The boot option debian2hd (more precise: the kernelname at the bootprompt) supports the following boot options (they correspond with the command line options mentioned above):.. target=.. The target partition/directory of the new Debian system.. Usage example: target=/dev/sda1.. grub=.. Where do you want to install grub to? Usage example: grub=/dev/sda.. release=.. Defaults to Debian wheezy.. Supported relases: lenny, squeeze, wheezy and sid.. Usage example: release=sid.. mirror=.. Specify mirror which should be used for apt-get/aptitude instead of the default one (.. http://http.. net/debian.. Usage example: mirror=ftp://ftp.. password=.. Set password of user root without prompting for it but set it to the given argument.. Usage example: password=AiTh5ahn.. Usage example for automatic installation:.. debian2hd target=/dev/sda1 grub=/dev/sda mirror=ftp://ftp.. at/mirror/debian password=foobar.. You have to enter this command line at the bootprompt of the Grml live system.. Please make sure that /dev/sda1 is the partition where you really want to install your new Debian system.. Automatic installation within booting process is done in grml-autoconfig via setting environment variable AUTOINSTALL and creation of /usr/bin/grml-debootstrap_noninteractive with the available and relevant boot options for grml-debootstrap.. Supported Releases.. TableCurrent status.. Release /.. Tool debootstrap.. cdebootstrap.. Lenny.. works [1].. Squeeze.. works.. Wheezy.. Sid.. works [2].. lenny release.. [1] Please notice that lenny is the current old-stable release within Debian.. grml-debootstrap can handle the release but you really should not use lenny anymore unless you really know what you are doing.. Choose Debian 6.. 0 (squeeze) or Debian 7.. 0 (wheezy) instead.. Notice that you need to specify a mirror providing the lenny release, the default (.. ) doesn t provide it any longer nowadays.. Set the mirror to e.. http://archive.. org/debian/.. if you don t have your own lenny mirror.. When installing lenny to a new mdraid, grml-debootstrap will use md metadata format version 0.. 90.. This limits the device to a maximum size of 2TB, but has the advantage of grub-legacy actually being able to boot from it.. sid release.. [2] Please notice that sid is Debian/unstable and due to its nature might not be always installable.. What.. might.. work instead is deploying a stable or testing release and upgrade it after installation finished.. Probably.. Please send bugreports to Michael Prokop.. See also.. debootstrap (8), cdebootstrap (1).. Last updated 2013-02-19 00:04:27 CET..

    Original link path: /grml-debootstrap/
    Open archive

  • Title: grml-live(8)
    Descriptive info: grml-live(8).. grml-live - build framework based on FAI for generating a Grml and Debian based Linux Live system (CD/ISO).. grml-live [-a architecture ] [-c classe[s] ] [-C configfile ] [ -e extract_iso_name ] [-g grml_name ] [-i iso_name ] [ -o output_directory ] [-r release_name ] [-s suite ] [ -t template_directory ] [-v version_number ] [-U username ] [ -AbBFnNqQuVz].. Description.. grml-live provides the build system for creating a Grml and Debian based Linux Live-CD.. The build system is based on.. FAI.. (Fully Automatic Installation).. grml-live uses the "fai dirinstall" feature to generate a chroot system based on the class concept of FAI (see later sections for further details) and provides the framework to be able to generate a full-featured ISO.. It does not use all the FAI features by default though and you don t have to know FAI to be able to use it.. The use of FAI gives you the flexibility to choose the packages you would like to include on your very own Linux Live-CD without having to deal with all the details of a build process.. grml-live does.. use /etc/fai for configuration but instead (unless overridden using the.. '-D.. ' option).. This ensures that it does not clash with default FAI configuration and packages, so you can use grml-live and FAI completely independent at the same time!.. Please notice that you should have a fast network connection as all the Debian packages will be downloaded and installed via network.. If you want to use a local mirror (strongly recommended if you plan to use grml-live more than once) checkout mkdebmirror (see /usr/share/doc/grml-live/examples/mkdebmirror), debmirror(1), reprepro(1) (see /usr/share/doc/grml-live/examples/reprepro/ for a sample configuration), apt-cacher(1) and approx(8).. To avoid downloading the base system again and again check out.. the base tar.. gz feature.. -A.. Clean up all output directories before running the build process.. After finishing, clean up the Chroot target and Build target directories.. -a.. ARCHITECTURE.. Use the specified architecture instead of the currently running one.. This allows building a 32bit system on a 64bit host (though you can t build a 64bit system on a 32bit system/kernel of course).. Please notice that real crosscompiling (like building a ppc system on x86) isn t possible due to the nature and the need of working in a chroot.. Currently supported values: i386 and amd64.. -b.. Build the ISO without updating the chroot via FAI.. This option is useful for example when working on stable releases: if you have a working base system/chroot and do not want to execute any further updates (via "-u" option) but intend to only build the ISO.. -B.. Build the ISO without touching the chroot at all.. This option is useful if you modified anything that FAI or grml-live might adjust via Grml s FAI scripts.. It s like the.. -b.. option but even more advanced.. Use only if you really know that you do not want to update the chroot.. -c.. CLASSES.. Specify the CLASSES to be used for building the ISO via FAI.. By default only the classes GRMLBASE, GRML_FULL and I386/AMD64 (depending on system architecture) are assumed, resulting in a base system of about 350MB total ISO size.. If using a non-I386 system (like AMD64) you should specify the appropriate architecture as well.. Additionally you can specify a class providing a grml-kernel (see.. section in this document.. for details about available classes).. So instead of GRML_FULL you can also use GRML_SMALL and GRML_FULL.. All class names should be written in uppercase letters.. Do not use a dash, use an underscore.. So do not use "amd64" but "AMD64", do not use "FOO BAR" but "FOO_BAR".. -C.. CONFIGURATION_FILE.. The specified file is used as configuration file for grml-live.. By default /etc/grml/grml-live.. conf is used as default configuration.. If a file named /etc/grml/grml-live.. local exists it is used as well (sourced after reading /etc/grml/grml-live.. conf meant as main file for local configuration).. As a last option the specified configuration file is sourced so it is possible to override settings of /etc/grml/grml-live.. conf as well as of /etc/grml/grml-live.. local.. Please notice that all configuration files have to be adjusted during execution of grml-live, so please make sure you use /etc/grml/grml-live.. conf as a base for your own configuration file (usually /etc/grml/grml-live.. local).. Please also notice that the configuration file specified via this option is.. (yet) /etc/grml/grml-live.. local for configuration stuff used inside.. -d.. DATE.. Use specified date as build date information on the ISO instead of the default.. The default is the date when grml-live is being executed (retrieved via executing.. date +%Y-%m-%d.. The information is stored inside the file /GRML/grml-version on the ISO, /etc/grml_version in the squashfs file and in all the bootsplash related files.. This option is useful if you want to provide an ISO with release information for a specific date but have to build it in advance.. -d 2009-10-30.. -D.. CONFIGURATION_DIRECTORY.. The specified directory is used as configuration directory for grml-live and its FAI.. By default /etc/grml/fai is used as default configuration directory.. If you want to have different configuration scripts, package definitions, etc.. with without messing with the global configuration under /etc/grml/fai provided by grml-live this option provides you the option to use your own configuration throughout this documentation.. -e.. EXTRACT_ISO_NAME.. The squashfs inside the specified ISO will be extracted and used as the chroot.. This option is useful for remastering, in combination with -A and -b or -u.. -F.. Force execution and do not prompt for acknowledgment of configuration.. -g.. GRML_NAME.. Set the grml flavour name.. Common usage examples: grml, grml-small, grml64.. Please do NOT use blanks and any special characters like.. ;.. inside GRML_NAME, otherwise you might notice problems while booting.. -h.. Display short usage information and exit.. -i.. ISO_NAME.. Specify name of ISO which will be available inside $OUTPUT_DIRECTORY/grml_isos by default.. -I.. CHROOT_INSTALL.. Specify name of source directory which provides files that should become part of the chroot/ISO.. Not enabled by default.. Note: the files are installed under.. in the chroot so you have to create the rootfs structure on your own.. -n.. Skip creation of the ISO file.. This option is useful if you want to build/update the chroot and/or recreate the squashfs file without building an ISO file.. -N.. Bootstrap the chroot without building bootloader, squashfs, or finalizing the ISO.. Use this option if installation of some packages fails, you want to run custom commands or similar.. The main use of this option is to save time by skipping stages which aren t necessary for bootstrapping the chroot and which would get executed more than once when iterating through the initial bootstrapping.. Alternatively, use this option as a test run of grml-live.. Once you are satisfied with the state of your grml_chroot, use grml-live.. -u.. to build the remaining stages and finalize the ISO.. -o.. OUTPUT_DIRECTORY.. Main output directory of the build process of FAI.. Some directories are created inside this target directory, being: grml_cd (where the files for creating the ISO are located, including the compressed squashfs file), grml_chroot (the chroot system) and grml_isos (where the resulting ISO is stored).. -q.. Build the ISO without (re-)creating the squashfs compressed file using mksquashfs.. This option is useful if you just want to update parts outside the chroot in the ISO.. Consider combining this option with the build-only option.. -Q.. Build the ISO without generating a netboot package.. -r.. RELEASENAME.. Specify name of the release.. -s.. SUITE.. Specify the Debian suite you want to use for your live-system.. Defaults to "squeeze" (being current Debian/stable).. Supported values are: etch, lenny, squeeze, wheezy, sid.. Please be aware that recent Debian suites might require a recent version of debootstrap.. -t.. TEMPLATE_DIRECTORY.. Specify place of the templates used for building the ISO.. By default (and if not manually specified) this is /usr/share/grml-live/templates/.. -u.. Update existing chroot instead  ...   bug, please send us a bug report then).. How do I deploy grml-live on a plain Debian installation.. for details how to set up grml-live on a plain, original Debian system.. enough free disk space; at least 800MB are required for a minimal grml-live run (~400MB for the chroot [$CHROOT_OUTPUT], ~150MB for the build target [$BUILD_OUTPUT] and \~150MB for the resulting ISO [$ISO_OUTPUT] plus some temporary files), if you plan to use GRML_FULL you should have at least 4GB of total free disk space.. fast network access for retrieving the Debian packages used for creating the chroot (check out "local mirror" to workaround this problem as far as possible).. For further information see next section.. 12.. Current state of grml-live with squashfs-tools and kernel.. Use squashfs-tools =4.. 2-1 (available from Grml repositories as well as from Debian/testing and Debian/unstable) to build Grml (based) ISOs featuring kernel version 2.. 38-grml[64] or newer.. 13.. How do I deploy grml-live on a plain Debian installation?.. The easiest way to get a running grml-live setup is to just use Grml.. Of course using grml-live on a plain, original Debian installation is supported as well.. So there we go.. What we have: plain, original Debian squeeze (6.. 0) with debian-backports enabled.. (This is important for squashfs-tools.. What we want: build a Grml ISO based on Debian/wheezy for the amd64 architecture using grml-live.. Instructions.. # adjust sources.. list: cat /etc/apt/sources.. list EOF.. # grml stable repository: deb http://deb.. org/ grml-stable main # deb-src http://deb.. org/ grml-stable main.. # grml testing/development repository: deb http://deb.. org/ grml-testing main # deb-src http://deb.. org/ grml-testing main EOF.. # get keyring for apt: apt-get update apt-get --allow-unauthenticated install grml-debian-keyring.. # optionally(!) install basefile so we don't have to build basic # chroot from scratch, grab from http://daily.. org/ # mkdir -p /etc/grml/fai/config/basefiles/ # mv I386.. gz /etc/grml/fai/config/basefiles/ # mv AMD64.. gz /etc/grml/fai/config/basefiles/.. # install relevant tools apt-get install -t squeeze-backports squashfs-tools apt-get --no-install-recommends install grml-live.. # adjust grml-live configuration for our needs: cat /etc/grml/grml-live.. local EOF ## want a faster build process and don't need smaller ISOs? ## if so use zlib compression # SQUASHFS_OPTIONS="-comp gzip -b 256k" ## want to use a specific squashfs binary? # SQUASHFS_BINARY='/usr/bin/mksquashfs' ## install local files into the chroot # CHROOT_INSTALL="/etc/grml/fai/chroot_install" ## adjust if necessary (defaults to /grml/grml-live): ## OUTPUT="/srv/grml-live" FAI_DEBOOTSTRAP="wheezy http://cdn.. net/debian/" # ARCH="amd64" CLASSES="GRMLBASE,GRML_FULL,AMD64" EOF.. # just optional(!) - upgrade FAI to latest available version: cat /etc/apt/sources.. list EOF # fai: deb http://fai-project.. org/download squeeze koeln EOF.. # get gpg key of FAI repos and install current FAI version: gpg -a --recv-keys AB9B66FD; gpg -a --export AB9B66FD | apt-key add - apt-get update apt-get install fai-client fai-server fai-doc.. That s it.. Now invoking.. grml-live -V.. should build the ISO.. If everything worked as expected the last line of the shell output should look like:.. [*] Successfully finished execution of grml-live [running 687 seconds].. and the ISO can be found inside /grml-live/grml-live/grml_isos/ then.. What is $GRML_FAI_CONFIG?.. The variable.. $GRML_FAI_CONFIG.. is pointing to the directory /etc/grml/fai by default.. To provide you a maximum of flexibility you can set up your own configuration directory (e.. based on /etc/grml/fai) and use this directory running grml-live with the.. -D config_dir.. Now.. points to the specified directory instead of using /etc/grml/fai and all the configuration files, scripts and hooks will be taken from your.. I ve problems with the build process.. How to start debugging?.. Check out the logs inside the directory.. next to your grml_chroot, grml_isos, directories.. If you need help with grml-live or would like to see new features as part of grml-live you can get commercial support via.. Grml Solutions.. How do I install further files into the chroot/ISO?.. Just point the configuration variable CHROOT_INSTALL to the directory which provides the files you would like to install.. Note that the files are installed under.. in the chroot - so you have to create the rootfs structure on your own.. Usage example:.. echo "CHROOT_INSTALL=\$GRML_FAI_CONFIG/chroot_install" /etc/grml/grml-live.. local mkdir -p /etc/grml/fai/chroot_install/usr/src/ wget example.. org/foo.. gz mv foo.. gz /etc/grml/fai/chroot_install/usr/src/ grml-live.. Can I use my own (local) Debian mirror?.. Yes.. Set up an according sources.. list configuration as class file in FAI_DEBOOTSTRAP (if not already using a base.. tgz) inside /etc/grml/grml-live.. conf[.. local].. If you re setting up your own class file don t forget to include the class name in the class list (grml-live -c ).. If you want to use a local (for example NFS mount) mirror additionally then adjust MIRROR_DIRECTORY in /etc/grml/grml-live.. local] as well.. If you want to use a HTTP Proxy (like apt-cacher-ng), set APT_PROXY.. Example:.. APT_PROXY="http://localhost:3142/".. How do I add additional Debian package(s) to my CD/ISO?.. Just create a new class (using the package_config directory):.. # cat /etc/grml/fai/config/package_config/MIKA EOF PACKAGES aptitude.. vim another_name_of_a_debian_package and_another_one EOF.. and specify it when invoking grml-live then:.. # grml-live -c GRMLBASE,GRML_SMALL,AMD64,MIKA.. I fscked up my grml-live configuration.. How do I reset it to the defaults?.. Notice: this deletes all your grml-live configuration files.. If that s really what you are searching for just run:.. rm -rf /etc/grml/fai /etc/grml/grml-live.. conf dpkg -i --force-confnew --force-confmiss /path/to/grml-live_.. _all.. How do I create a base.. tgz?.. First of all create the chroot using debootstrap:.. BASECHROOT='/tmp/basefile' debootstrap squeeze "$BASECHROOT" http://cdn.. net/debian tar -C "$BASECHROOT" --exclude='var/cache/apt/archives/*.. deb' -zcf base.. gz.. /.. By default debootstrap builds a chroot matching the architecture of the running host system.. If you re using an amd64 system and want to build an i386 base.. tgz then invoke debootstrap using the.. Disclaimer: building an AMD64 base.. tgz won t work if you are using a 32bit kernel system of course.. Then move the base.. gz to /etc/grml/fai/config/basefiles/$CLASSNAME.. gz.. Use e.. I386 as $CLASSNAME for i386 chroots and AMD64 for amd64 chroots.. Now executing grml-live should use this file as base system instead of executing debootstrap.. Check out the output for something like:.. [.. ] ftar: extracting //etc/grml/fai/config/basefiles///AMD64.. gz to /srv/grml64_testing/grml_chroot// [.. ].. Existing base.. tgz can be found at.. http://daily.. Set up apt-cacher-ng for use with grml-live.. Make sure /etc/grml/grml-live.. local provides according APT_PROXY and FAI_DEBOOTSTRAP:.. # cat /etc/grml/grml-live.. local [.. ] APT_PROXY="http://localhost:3142/" [.. ] FAI_DEBOOTSTRAP="squeeze http://localhost:3142/cdn.. net/debian squeeze main contrib non-free".. Make sure apt-cacher-ng is running (.. /etc/init.. d/apt-cacher-ng restart.. All downloaded files will be cached in /var/cache/apt-cacher-ng then.. How do I revert the manifold feature from an ISO?.. The so called manifold feature Grml ISOs use by default allows one to use the same ISO for CD boot and USB boot.. If you notice any problems when booting just revert the manifold feature running:.. % dd if=/dev/zero of=grml.. iso bs=512 count=1 conv=notrunc.. To switch from manifold to isohybrid mode (an alternative approach provided by syslinux) then just execute:.. % isohybrid grml.. iso.. How do I create a base tar.. gz (I386.. gz or AMD64.. gz).. Execute the following commands (requires root):.. ARCH='amd64' # replace with i386 if necessary SUITE='squeeze' # using the current stable release should always work debootstrap --arch "$ARCH" --exclude=info,tasksel,tasksel-data "$SUITE" "$ARCH" http://debian.. de/debian cd "$ARCH" rm var/cache/apt/archives/*.. deb tar zcf.. /"${ARCH}".. gz *.. And finally place the generated tarball in /etc/grml/fai/config/basefiles/ (note that it needs to be uppercase letters matching the class names, so: AMD64.. gz for amd64 and I386.. gz for i386).. 14.. Download / install grml-live as a Debian package.. Debian packages are available through the grml-repository at.. deb.. If you want to build a Debian package on your own (using for example a specific version or the current development tree), just execute:.. org/grml-live cd grml-live debuild -us -uc.. 15.. Source.. The source of grml-live is available at.. https://github.. com/grml/grml-live/.. 16.. Please report feedback,.. bugreports.. and wishes.. to the Grml team.. !.. 17.. The most recent grml-live documentation is available online at.. org/grml-live/.. and for offline reading also available in different formats:.. org/grml-live/grml-live.. epub.. pdf.. 18.. Authors.. Last updated 2012-09-26 19:37:35 CEST..

    Original link path: /grml-live/
    Open archive

  • Title: grml-x(1)
    Descriptive info: grml-x(1).. grml-x - create xorg.. conf file and start X window system on grml-system.. grml-x [ options ] [ window-manager ].. grml-x creates the configuration file for the X server (X.. org) letting you override some options and then starts up X server with the specified window manager.. Implementation.. grml-x depends on the X server to configure itself.. It will generate a very minimal xorg.. conf, or, at your option, write some common options to it.. If an xorg.. conf file already exists, grml-x won t touch the file unless the.. option is specified.. If you specify a window manager, the x-window-manager alias will be updated.. Important! Please do.. run X or grml-x with root permissions! When used in grml live-cd mode running grml-x works as normal user as well (thanks to sudo).. Just switch to an appropriate console where user grml is logged in (for example on tty5 via pressing Alt-F5).. If you use grml-x on systems other than grml in live mode you can invoke it as user root but please use the.. --nostart.. option to avoid startup X server.. This allows you to generate a xorg.. conf file on harddisk systems as well as on distributions other than grml/Debian.. Note.. Notice that you do not have to use grml-x  ...   "30-65".. --mode width x height.. Set resolution for X server.. --module name.. Use name as module for X server.. --nostart.. Do not start X server.. Useful when you only want to generate xorg.. --vsync number.. Specify vertical sync frequencies.. Use a number like "50-60".. grml-x --mode "1280x1024 1024x768" wm-ng.. Use resolutions 1280x1024 and 1024x768 and start windowmanager wm-ng.. grml-x --module vesa openbox.. Use vesa-module and start windowmanager openbox.. grml-x --hsync "30-65" fluxbox.. Use 30-65kHz for horizontal sync frequency and start windowmanager fluxbox.. grml-x --display 8 ratpoison.. Use display 8 for Xserver and start windowmanager ratpoison.. grml-x --nostart -f fluxbox.. Force writing of config file but do not start X server.. Please do not forget to add a window manager as last option because grml-x changes the according exec-statement in $HOME/.. xinitrc.. Known problems and limitations.. Sometimes the X server does not find the correct resolution and/or frequency settings for the monitor.. Please adjust configuration manually using the --hsync and the --vsync options then.. Also check out the.. usage examples section.. in this manpage and the help output of grml-x running.. grml-x --help.. to us.. This manual page and grml-x itself have been written by Michael Prokop.. and are licensed under the GPL v2 or any later version.. Last updated 2010-12-02 18:47:32 CET..

    Original link path: /grml-x/
    Open archive

  • Title: grml.org - grml-terminalserver
    Descriptive info: grml-terminalserver.. Using grml-terminalserver you can boot grml via network.. If your computer is able to boot via.. PXE.. (Preboot Execution Environment) all you have to do is start grml-terminalserver on the host which should serve as booting server and boot Grml via network/PXE on the client(s) then.. If your computer can't handle PXE you can still try to boot Grml via network, because grml-terminalserver lets you create a floppydisk including a bootimage with your networkcard-driver to boot via network.. If that's still not  ...   root and follow the instructions.. Take a look at the manpages grml-terminalserver and grml-terminalserver-config.. Boot Grml without grml-terminalserver?.. Sure - of course you can boot Grml via PXE without having to use grml-terminalserver (for example if you already have a working NFS, tftp,.. infrastructure).. Take a look at.. the instructions in the grml-wiki.. Select ip address range for clients.. Are there any computers without PXE?.. Select networkcard drivers for non-PXE capable computers.. Write grub image to floppy disk?.. Known Issues / Further information.. grml-wiki..

    Original link path: /terminalserver/
    Open archive





  • Archived pages: 58