Re: Live Systems Project: Feedback
Greetings, ...default username user and the default password live... reference http://live.debian.net/manual/stable/html/live-manual.en.html#508 Thanks. On Thu, Jan 15, 2015 at 8:07 AM, Midgley, Scott scott.midg...@mclaren.com wrote: Hi there. I build a live iso with your website and I can use it to install Debian without issue, but I have no idea what the username and password is to just use it live Thanks, Scott *Scott Midgley | Software Engineer | McLaren Applied Technologies* McLaren Technology Centre, Chertsey Road, Woking, Surrey GU21 4YH, UK P: +44 (0) 1483 215649 M: +44 (0) 7876 577755 F: +44 (0) 1483 261402 E: scott.midg...@mclaren.com W: http://www.mclaren.com/appliedtechnologies The contents of this e-mail are confidential and for the exclusive use of the intended recipient. If you are not the intended recipient you should not read, copy, retransmit or disclose its contents. If you have received this email in error please delete it from your system immediately and notify us either by email or telephone. The views expressed in this communication may not necessarily be the views held by McLaren Applied Technologies Limited. McLaren Applied Technologies Limited | McLaren Technology Centre | Chertsey Road | Woking | Surrey | GU21 4YH | UK | Company Number: 02322992
Processed: Add tag patch
Processing commands for cont...@bugs.debian.org: tags 775424 + patch Bug #775424 [live-build] live-build: xorriso must be called with iso level 3 to support larger live systems Added tag(s) patch. End of message, stopping processing here. Please contact me if you need assistance. -- 775424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.14213408352581.transcr...@bugs.debian.org
Live Systems Project: Feedback
Hi there. I build a live iso with your website and I can use it to install Debian without issue, but I have no idea what the username and password is to just use it live Thanks, Scott Scott Midgley | Software Engineer | McLaren Applied Technologies McLaren Technology Centre, Chertsey Road, Woking, Surrey GU21 4YH, UK P: +44 (0) 1483 215649 M: +44 (0) 7876 577755 F: +44 (0) 1483 261402 E: scott.midg...@mclaren.commailto:scott.midg...@mclaren.com W: http://www.mclaren.com/appliedtechnologies The contents of this e-mail are confidential and for the exclusive use of the intended recipient. If you are not the intended recipient you should not read, copy, retransmit or disclose its contents. If you have received this email in error please delete it from your system immediately and notify us either by email or telephone. The views expressed in this communication may not necessarily be the views held by McLaren Applied Technolgies Limited. McLaren Applied Technologies Limited | McLaren Technology Centre | Chertsey Road | Woking | Surrey | GU21 4YH | UK | Company Number: 02322992
Bug#775424: live-build: xorriso must be called with iso level 3 to support larger live systems
Package: live-build
Version: 4.0.3-1
Severity: normal
For building larger live systems (squashfs 4G) xorriso must be called
with iso level 3. We have been building our Debian Live based
distribution with this switch for the whole wheezy cycle and did not
notice any problem with it.
Please accept the attached patch to support larger Debian Live systems.
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages live-build depends on:
ii debootstrap 1.0.66
Versions of packages live-build recommends:
ii cpio2.11+dfsg-4
ii live-boot-doc 4.0.1-1
ii live-config-doc 4.0.2-1
ii live-manual-html [live-manual] 1:4.0.1-1
live-build suggests no packages.
-- no debconf information
diff --git a/scripts/build/binary_iso b/scripts/build/binary_iso
index 7abfc69..080cc65 100755
--- a/scripts/build/binary_iso
+++ b/scripts/build/binary_iso
@@ -80,7 +80,7 @@ then
fi
# Handle xorriso generic options
-XORRISO_OPTIONS=-R -r -J -joliet-long -l -cache-inodes
+XORRISO_OPTIONS=-R -r -J -joliet-long -l -cache-inodes -iso-level 3
# Handle xorriso live-build specific options
if [ ${LIVE_IMAGE_TYPE} = iso-hybrid ]
Bug#775322: Bootloader code issues and improvements
El 14/01/15 a las 04:54, jnqnfe escribió: Package: live-build Version: 5.0~a2-1 Reviewing the bootloader menu creation code, I have drawn up the following list of fixes and improvements needed. Some of these I have already reported and supplied patches for separately, but I'm listing them here again to provide a comprehensive set of issues. Where applicable, I'll specify the bug number of the separate bug report either specifically for the issue, or where a patch has been previously supplied already as part of addressing something else. I intend to wrap this bug report up with one or more sets of commits to address them all. Thank you for your recent hard work. Broken boot capability issues: --- #1) grub2 broken, with missing file error on boot due to files being placed in the wrong directory (#775316). Kernel parameter issues: --- #2) [install entries] user supplied kernel params added in wrong position in grub/grub2 (#775143). #3) [install entries] 'quiet' (d-i?) param excluded from rescue entries instead of expert entries in grub2 (#775143). #4) [install entries] the '--' delimiter prior to the (d-i?) quiet kernel parameter is not output for grub/grub2 (#775143). #5) [install entries] the '--' delimiter needs to be replaced now with '---' (#775128). #6) [live entries] user supplied kernel params added in wrong position in grub/grub2 (less important than for installer entries) (#775143). #7) [live entries] normal user supplied params being added to fail-safe entry instead of fail-safe user params in grub/grub2. #8) [live entries] unnecessary replacement of fail-safe-installer user params placeholder in syslinux #9) depreciated video/graphics kernel parameters are being used. Menu entry set issues: --- #10) [install entries] speech synthesis option missing, affecting accessibility I just write down here that I will have to review your mentioned: #1, #2, #3, #4, #5, #6, #7, #8 and #9 in my (#757883) (support for loopback.cfg file) so that it matches your improvements and fixes. Unless somehow your #18 is fixed so that the kernel is always renamed. That would probably mean that I could just do as the grml implementation [1] which would be as simple as always generating grub2 file and symlinking /boot/grub/loopback.cfg to /boot/grub/grub.cfg . #12) [live entries] too many entries added in grub/grub2 (redundant entries with kernel version specified) Do you mean the normal entry and the single entry per one kernel? Or do you actually mean repeated kernels? #13) memtest entry included in syslinux menus even if no memtest included #14) install entries included in syslinux menus even if no installer included What I had found out myself is that there were installer entries in grub2 but not in syslinux but that was when I checked it in Wheezy's Debian Live so that might explain it. In GIT it should be as you explain then. Other issues: --- #16) grub2 splash not being displayed I had also thought on this problem. I think there should a way of just reusing the current syslinux SVG file so that it generates a suitable image that can be used by grub2 as a background image. #17) grub splash displayed, but horribly (can this be fixed?) If it's grub1 I don't think it's worth maintaining it. But, I don't know what's the Debian's grub vs grub2 policy in Jessie actually. #18) grub/grub2 do not rename kernel files unlike syslinux. syslinux does this for a technical reason, but it might be desirable to do across the board anyway. This needs further consideration. Please check (#757883) (support for loopback.cfg file) where you can see how I re-use syslinux code to avoid syslinux being stubborn on renaming the kernel filenames. Don't get me wrong, I also prefer the kernel files to be renamed always so that the code is consistent accross all the bootloaders. #19) consider switching grub/grub2 code to work more like syslinux, with pre-constructed pieces of the menus in files, from which the full menu can be constructed by including chunks from those files, and replacing placeholders. Well, yes, we could do that with grub2 variables. My dream is defining these variables or settings once (in a xml file? in a ini file?) and then being translated into a syslinux file or to a grub2 file. Also to be considered, particularly in respect to #18 and #19 are bug #757697 (support arch autodetection) and the best way to allow derivatives (e.g. Kali) to replace menu components such as labels and splash. Yes, I also think that somehow a DerivativeName setting is missing so that we can easily replace Debian to e.g. Kali from a config file without too much effort. As of this moment I have written patches for 11 of these issues, some of which have already been posted separately. More to follow soon. Thank you again for your hard work. adrian15 [1]:
Bug#775424: live-build: xorriso must be called with iso level 3 to support larger live systems
Hi, some theoretical background: -iso-level 3 implies -iso-level 2 which allows file names with 32 characters rather than only 8+.+3 characters. So if the boot loader interprets ISO 9660 names rather than Rock Ridge names, previously truncated names might become longer. -iso-level 3 will not make any further difference towards the default level 1 with data files smaller than 4 GiB. So when not actually needed, it imposes no extra risk. Files of 4 GiB or larger will be represented by multiple file sections (aka extents). Modern Linux kernels have no problem with that, when reading data files from the mounted ISO filesystem. The BSDs and Solaris will show large files in various ill ways, though. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1395538774608190...@scdbackup.webframe.org
Bug#757697: RFE: Autodetection of architecture at boot time to load appropiate kernel
El 22/12/14 a las 01:19, Michal Suchanek escribió: Hello, On 10 August 2014 at 18:31, Adrian Gibanel Lopez adrian15...@gmail.com wrote: Source: live-config Severity: wishlist Dear Maintainer, If one has configured its Debian Live to have more than one architecture kernel this is what I am expecting would be the default behaviour is: (...) Upstream documentation: http://www.syslinux.org/wiki/index.php/Ifcpu64.c32 Thank you! While at this is it also possible to detect i486 vs i686-pae? You could do it with the current ifcpu64.c32 comboot module. This poses another problem, what to do when you have three or more than three different kernels? I prefer not to implement i486 vs i686-pae. I think it's better the patch to be accepted as-is and later to be improved if someone finds out a reasonable way of improving it for enabling i486 vs i686-pae. Thanks Michal adrian15 -- Support free software. Donate to Super Grub Disk. Apoya el software libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/ -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b7cad1.9050...@gmail.com
