config/binary_sysinux being ignored
Hi all, First of all, thanks so much to the live builder team for this excellent tool. It offers by far the most control over the build process. Is there anything else I need to do to have my customizations to syslinux take effect? I've put my own live.cfg and splash.png into config/binary_syslinux/ but when the build completes and I check the results, the files have not been incorporated into the ISO. The only way I can affect syslinux is by setting LB_SYSLINUX_SPLASH in config/binary. Of course, that doesn't allow me to change live.cfg. Any ideas? Thanks, Dan -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dfcc9cb.2090...@syrinx.net
Re: config/binary_sysinux being ignored
On 11-06-19 02:40 AM, Daniel Baumann wrote: live-build 2.x or 3.x? Sorry, 2.0.12-1. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dfdcbb1.9090...@syrinx.net
Re: config/binary_sysinux being ignored
On 11-06-19 06:13 AM, Daniel Ellison wrote: Sorry, 2.0.12-1. Also, building squeeze. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dfdd44a.8070...@syrinx.net
Re: config/binary_sysinux being ignored
On 11-06-19 07:02 AM, Daniel Baumann wrote: 2.x is only supported for RC fixes, please use 3.x. Thanks. I'll try 'testing', then (3.0~a17-1). in 3.x, you will need to use a custom syslinux-themes package if you want to change anything but the boot parameters (see syslinux-themes-debian[0] or syslinux-themes-progress[1] for examples). Ok, that's not a problem. Are there any other changes needed to my build in order to switch to 3.x? Sorry for the newbie questions. I just started with live builder last week. I already have a fully functioning distribution! Thanks again for such a great tool. Dan -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dfdebc7.50...@syrinx.net
Re: config/binary_sysinux being ignored
On 11-06-19 08:35 AM, Daniel Baumann wrote: since only the newest version of 3.x is supported, you should get what is in sid instead. Done. there were a few changes in the config tree, but if you populate it from auto/, then top of my head i don't think you have to change anything by hand. I populate from auto only for the things that might change per version of my distribution. I'll change it so that everything is done in auto/config. Thanks for your quick responses! -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dfdf088.5090...@syrinx.net
live.cfg menu item in syslinux theme not working
Hi all, I've created a syslinux theme .deb and it's in place and working. The only issue is that the "Start Live" menu item in live.cfg isn't working. I can start up the installer in either standard or expert mode, but choosing the "Start Live" entry has no effect. Here's the contents of the live.cfg file in my theme: label live menu label Start Live kernel /live/vmlinuz append initrd=/live/initrd.img boot=live config username=live hostname=live quiet label installgui menu label Install OS kernel /install/gtk/vmlinuz append initrd=/install/gtk/initrd.gz video=vesa:ywrap,mtrr vga=788 quiet label expertgui menu label Expert Install OS kernel /install/gtk/vmlinuz append initrd=/install/gtk/initrd.gz priority=low video=vesa:ywrap,mtrr vga=788 If the lines appear wrapped in your email client, they're not wrapped in the actual live.cfg file. Is there a way to find out why this entry is failing? Thanks, Dan -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dff6ed3.50...@syrinx.net
Re: config/binary_sysinux being ignored
On 11-06-19 07:02 AM, Daniel Baumann wrote: in 3.x, you will need to use a custom syslinux-themes package if you want to change anything but the boot parameters (see syslinux-themes-debian[0] or syslinux-themes-progress[1] for examples). [0] http://packages.qa.debian.org/syslinux-themes-debian/ [1] http://vcs.progress-linux.org/?p=packages/syslinux-themes-progress.git Hi all, In the interests of making it easier for people to get up to speed with the syslinux-themes system used by live-build 3.x, here is what I had to do to use my own theme. First, when Daniel says "you will need to use a custom syslinux-themes package", he means you need to actually create your own .deb file. You can't put your theme in chroot_local-includes and have it picked up during the build process. It needs to be a valid .deb file. Since I don't have my own repository, I put my theme's .deb in chroot_local-packages. Second, this is a good source for instructions on creating your own .deb file: http://ptspts.blogspot.com/2010/02/how-to-create-debianubuntu-package-deb.html. If you start with syslinux-themes-debian-squeeze, you can skip a few of the steps. Third, the name of your .deb has to start with "syslinux-themes-" for it to be found by the build scripts. Fourth, "lb config help" says "--syslinux-theme THEME_SUFFIX". THEME_SUFFIX is actually the name of your theme at the /usr/share/syslinux/themes/ level. So using the syslinux-themes-debian-squeeze package as an example, THEME_SUFFIX would be debian-squeeze. If any of this is incorrect, please feel free to correct me. I could find no information about this stuff online,o I thought I would contribute this little bit of documentation to the cause. Dan -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dff7494.6000...@syrinx.net
Re: live.cfg menu item in syslinux theme not working
On 11-06-20 01:13 PM, Daniel Baumann wrote: On 06/20/2011 06:01 PM, Daniel Ellison wrote: Is there a way to find out why this entry is failing? what does syslinux tell you when you try to boot it? When I type "live" at the "boot:" prompt, I get "Could not find kernel image: /live/vmlinuz". I assume that file is created by the build process. Or has its name or location changed between 2.x and 3.x? -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dff8469.2060...@syrinx.net
Re: live.cfg menu item in syslinux theme not working
On 11-06-20 01:40 PM, Daniel Baumann wrote: On 06/20/2011 07:33 PM, Daniel Ellison wrote: When I type "live" at the "boot:" prompt, I get "Could not find kernel image: /live/vmlinuz". depends on your config tree, look at binary/live and see what you get by default, lb3 does not mangle the kernel filename, so that would be /live/vmlinuz-2.6.39-2-amd64 or similar. I got vmlinuz-2.6.32-5-amd64 and initrd.img-2.6.32-5-amd64. I put those filenames in live.cfg just to see if it works. I did my build, got to the syslinux screen... and it still didn't work. At the "boot:" prompt I now get "Could not find kernel image: /live/vmlinuz-2.6.32-5-amd64". binary/live definitely contains these files. Is there any other information I could provide to clarify this? if you want it to be mangled, you can use a binary hook, such as: http://vcs.progress-linux.org/?p=images/standard.git;a=blob;f=config/binary_local-hooks/kernel.sh or include the explicit filename in your live.cfg. i still need to figure out a smart way to do that somewhat more automatic with a replace from the template that works with any number of installed kernels. Actually, for now the hook would work just fine, and makes it so that I don't have to remember to update my theme every time the kernel changes. For the moment I've renamed the two files back to vmlinuz and initrd.img and have installed that hook. I'm running the build again in the off chance that it works this time :) Thanks, Dan -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dff92ea.90...@syrinx.net
Re: live.cfg menu item in syslinux theme not working
On 11-06-20 02:35 PM, Daniel Ellison wrote: For the moment I've renamed the two files back to vmlinuz and initrd.img and have installed that hook. I'm running the build again in the off chance that it works this time :) Holy &^%&!! That worked! Hmmm... I don't like things that just start working for seemingly illogical reasons. But I'm not complaining. Dan -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dff9893.8050...@syrinx.net
Re: live.cfg menu item in syslinux theme not working
On 11-06-20 02:35 PM, Daniel Ellison wrote: For the moment I've renamed the two files back to vmlinuz and initrd.img and have installed that hook. I'm running the build again in the off chance that it works this time :) Just to clarify, I didn't actually rename any files. I changed the reference to the files in my live.cfg. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dff98fd.5030...@syrinx.net
A new Debian Squeeze-based Linux distribution created with live builder
Hi all, I just thought I would let everyone know about a new Debian Squeeze-based distribution that I built with the Debian live builder tools. Many thanks to Daniel Baumann for the tools and the help! I'm sure I'll need more help as I develop this distribution. The URL is http://journal.syrinxos.com/ Eventually I'll have a full website and forum, but this will do for now. If you try it out, please let me know what you think. Regards, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e025f2b.6020...@syrinx.net
Re: A new Debian Squeeze-based Linux distribution created with live builder
On 11-06-23 05:29 AM, Daniel Baumann wrote: On 06/22/2011 11:31 PM, Daniel Ellison wrote: I just thought I would let everyone know about a new Debian Squeeze-based distribution that I built with the Debian live builder tools. nice, do you like to submit an entry for live.debian.net/project/downstreamm ? Thanks! I would love to. What do you need from me? Or do I do it myself? Many thanks to Daniel Baumann for the tools and the help! I'm sure I'll need more help as I develop this distribution. you're welcome. s/Daniel Baumann/Debian Live Team/ s/\(Daniel Baumann\)/\1 and the Debian Live Team/ -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e031d07.4020...@syrinx.net
Re: A new Debian Squeeze-based Linux distribution created with live builder
On 11-06-23 07:43 AM, Daniel Baumann wrote: On 06/23/2011 01:01 PM, Daniel Ellison wrote: Thanks! I would love to. What do you need from me? Or do I do it myself? you can do it yourself if you want to, import the commit key (same as for live-manual), and commit to wiki-content.git. Ok, I'll do that. Thanks. s/\(Daniel Baumann\)/\1 and the Debian Live Team/ (jftr: here, one lists persons after 'groups', which i quite like (if mentioning individual persons at all, that is)) s/\(Daniel Baumann\)/The Debian Live Team and \1/ :) I'll change the credit on my site, as well. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e032e5f.6040...@syrinx.net
Changing architectures
Hi all, How do people handle building for various architectures? Do you have a separate config tree for each? Or do you "lb clean --purge" before building? I would have thought it was as easy as specifying a different parameter for --architectures, but switching from amd64 to i386 still results in an amd64 build. Is there anything else I'm missing? The manual isn't very specific on that subject. I may indeed be missing something extremely obvious here, but I can't find any information about this. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e0470e8.8060...@syrinx.net
Can't create an i386 ISO, but amd64 works fine
Hi all, I've successfully created amd64 ISOs several times. When I want to do the same for i386, I change "--architectures" to i386 and do lb clean --purge; lb config; lb build Eventually it says this: P: Begin executing preseed... P: Begin executing local preseeds... P: Begin queueing installation of package lists (install pass)... P: Begin queueing installation of local package lists (install pass)... P: Begin queueing installation of local packages... P: Begin installing packages (install pass)... Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: gdm : Depends: libglade2-0 (>= 1:2.6.1) but it is not going to be installed Depends: libgnomecanvas2-0 (>= 2.11.1) but it is not going to be installed Depends: libgtk2.0-0 (>= 2.18.0) but it is not going to be installed Depends: libpango1.0-0 (>= 1.14.0) but it is not going to be installed Depends: librsvg2-2 (>= 2.26.0) but it is not going to be installed Depends: gksu (>= 1.0.7) but it is not going to be installed Depends: librsvg2-common but it is not going to be installed Recommends: zenity but it is not going to be installed The "gdm" part is just an example. it says similar things about every package I have in my chroot_local-packagelists/syrinx.list The ISO is created with no errors when I set "--architectures" to amd64 and do the same set of commands. Is there anything I'm doing obviously wrong? I can provide my auto/config, syrinx.list etc. if needed. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e176707.5020...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-08 04:22 PM, Daniel Ellison wrote: The ISO is created with no errors when I set "--architectures" to amd64 and do the same set of commands. Is there anything I'm doing obviously wrong? I can provide my auto/config, syrinx.list etc. if needed. Any ideas on this? it's really bugging me now. :) -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e1ee0ba.9050...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-14 08:30 AM, Ben Armstrong wrote: On 07/08/2011 05:22 PM, Daniel Ellison wrote: Hi all, I've successfully created amd64 ISOs several times. When I want to do the same for i386, I change "--architectures" to i386 and do lb clean --purge; lb config; lb build I don't know if the dependency issues directly relate to this, but if you make major changes to your config you need to do more than this to rebuild your config. Changing architectures qualifies as a "major change". See chapter 6 at http://live.debian.net/manual. Thanks Ben. I'll take another look at the docs. I've read the whole thing a couple of times, but I find that parts become clearer after a bit of experience with the scripts, so a re-read might help. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e1ee609.9070...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-14 11:30 AM, Daniel Baumann wrote: i think i already mentioned to you at another occasion on this list, it's best to do different architectures from the same config tree. That wasn't me, I believe. You did point me to this URL: git://vcs.progress-linux.org/images/client-gnome.git but for me, that was a little too general. I didn't know what I was looking for. I'm still learning the live build system as I go. Btw, I _am_ trying to do different architectures from the same config tree. for using different (architecture or otherwise) configurations from the same config tree, one should use the auto mechanism and make sure, that the autogenerated config/* files are created through auto/config and removed through auto/clean. an examle doing this can be found here: http://vcs.progress-linux.org/?p=images/client-gnome.git;a=summary I already do use the auto mechanism. I use the provided examples for "clean" and "build" and have my own simple "config" script. I'll take a closer look at your more complex auto/config at the link you just provided. Also, it might be worth to publish your config tree so one can have a look at it. do you use public VCS for syrinx os? I don't yet use a public VCS but I plan to. I wanted to get the first release out for both amd64 and i386 before publishing everything. I didn't expect to be stuck on this step. I was thinking of using Launchpad for source publishing and bug tracking, though I've never used it before so I'm open to suggestions. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e1f17ca.1090...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-14 12:28 PM, Ben Armstrong wrote: Daniel meant to say "best to not do different architectures from the same config tree" I am sure. Ah, I suspected that was a typo. That's why I emphasized that I was indeed doing that. :) So generally people have a completely separate config setup for each architecture? Isn't that a lot of duplication? Good. That's what I was trying to steer you towards. If you're already doing it and your auto/clean works properly (by removing the old config/* top-level files) then all should be well. Yes, that's exactly what is being done. I noticed that Daniel's auto/clean script removes some files that his auto/config creates. That's the only difference between his example and what I use. Our auto/config files are necessarily different. As I said, I don't know if that has anything to do with the dependency issues or not. It may simply be a temporary issue with the archives. Different arches are not always updated simultaneously, as the autobuilders take time to kick in ... also, sometimes autobuilds on an architecture different from the maintainer's own architecture can fail for some reason, leading to uninstallable packages for a longer period of time until a fixed package is provided. Ah, there' a clue! I'm building on a 64 bit laptop with corresponding kernel. It doesn't seem to want to pick up *any* dependencies when I build i386. I looked at a diff between the logs of both build attempts and there's nothing different of any consequence until it fails for i386: "Some packages could not be installed." versus the amd64 build: "The following extra packages will be installed:" followed by a huge list of all files I specified and their dependencies. Does that sound like the behaviour expected from archive issues? Again, thanks so much to you and Daniel for the help so far. I think people are going to like the distribution that results from all of this! :) Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e1f1d9b.2050...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-14 01:06 PM, Ben Armstrong wrote:
Does that sound like the behaviour expected from archive issues?
More like a completely broken archive mirror (or broken apt caching proxy).
I was using:
--mirror-bootstrap http://ftp.ca.debian.org/debian/
--parent-mirror-bootstrap http://ftp.ca.debian.org/debian/
I just switched it to:
--mirror-bootstrap http://ftp.us.debian.org/debian/
--parent-mirror-bootstrap http://ftp.us.debian.org/debian/
(removing binary, bootstrap, chroot, common and source from config/ for
good measure) with the same result.
fyi, this is my auto/config:
#!/bin/sh
lb config noauto \
--distribution squeeze \
--architectures i386 \
--mirror-bootstrap http://ftp.us.debian.org/debian/ \
--parent-mirror-bootstrap http://ftp.us.debian.org/debian/ \
--volatile false \
--bootstrap debootstrap \
--binary-images iso-hybrid \
--syslinux-theme 'syrinx-debussy' \
--hostname debussy \
--username live \
--debian-installer live \
--debian-installer-gui true \
"${@}"
If I can't figure this out soon, I might skip the i386 build for now and
concentrate on getting the source to a public repository, setting up a
bug tracker, website, etc.
--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e1f3217.8070...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-14 09:28 PM, Ben Armstrong wrote: On 14/07/11 06:39 PM, Daniel Baumann wrote: On 07/14/2011 07:06 PM, Ben Armstrong wrote: if you do both arches from the same tree there would be a risk that one image is "tainted" with stuff from the wrong arch if you didn't take care. provided that one does a) ensure the generated config files in config/ are removed in auto/clean, b) the generated config files in config/* are created in auto/config, and c) one does a lb clean before 'switching' the architecture, i see no problem in having two archs configured in one tree. Not just lb clean, but lb clean --purge to get rid of cached bootstrap. That's why I'm not really keen on this approach, as if you're doing much switching between architectures, you'll lose the benefit of keeping the cache around. Now, if the caches existed in arch-specific directories, that would be another matter ... I haven't checked this ... This is how I assumed it worked in the first place, especially with the option being called "LB_ARCHITECTURES". I thought I would be able to specify multiple architectures like this: --architectures i386 amd64 and have them built by the one invocation (build platform-permitting). just to be clear: while i keep as described all architectures and distributions in one single config tree, i do check it out on the buildd freshly from git every time i want to build it. so, tainting is not so much of a problem. Ah, so you're already not benefiting from caching. otoh, if the config tree is not done well, the result can be that either the different architectures images are not really aequivalent (same package selection, etc), or, that the image can actually be built. so, as long as one makes sure that all the arch conditionals are configured properly for all architectures aequivalently, the images if built in a proper environment, will be fine. Sure. Well, I don't fundamentally disagree with you on any point of your approach, but as things stand I don't think there is one "ideal" solution. I guess it just depends on what tradeoffs you prefer. Having separate caches kept for each architecture would mitigate the caching issue. Perhaps that could be considered for a future release? This would allow people to have one "code base" for all architectures, simplifying the process and avoiding mistakes when trying to synchronize between architectures. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e204e6e.9000...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-14 05:39 PM, Daniel Baumann wrote: provided that one does a) ensure the generated config files in config/ are removed in auto/clean, b) the generated config files in config/* are created in auto/config, and c) one does a lb clean before 'switching' the architecture, i see no problem in having two archs configured in one tree. I am definitely doing all of the above. As a test, I separated my builds into one each for i386 and amd64, scrubbing them clean. The amd64 build succeeds while the i386 build fails in the same was as before. I'm now suspecting that my troubles have less to do with my configuration and more to do with the fact that I'm "developing" on a 64 bit machine/kernel and "compiling" to an i386 architecture. I have no 32 bit machines available, unfortunately. But I can set up a VM to test it out. In fact, it might be a smarter idea for the moment to build in a VM of the appropriate architecture. It would slow down the build process, but at least it would succeed! :) -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e2050d4.5060...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-15 10:31 AM, Daniel Baumann wrote: On 07/15/2011 04:27 PM, Daniel Ellison wrote: Having separate caches kept for each architecture would mitigate the caching issue. Perhaps that could be considered for a future release? sure. it's on todo with the whole multi-architecture thing, see live.debian.net/devel/rfc/. i'd expect this to be ready somewhen in september. Excellent! I look forward to that. I'll take a look at the RFCs and see if I have any Cs to add. :) -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e20510c.8090...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-15 11:31 AM, Daniel Baumann wrote: On 07/15/2011 05:16 PM, Ben Armstrong wrote: I don't see how that would be a problem. I have built i386 arch images fine on a 64 bit machine/kernel. ack; and if in doubt, you could do it in a chroot (enter in it with: linux32 chroot $directory, rather than chroot $directory) or an lxc. Ok, I created a brand-new i386 config set in an empty directory and then copied my auto scripts into it. I was able to create an i386 ISO. Finally! So now I knew it wasn't an architecture issue, as both you and Ben said. Next, I added in all of my configuration from the old config set one-by-one until it failed. It turns out to be my chroot-sources/wheezy.chroot and chroot-apt/preferences files! Without those two files, my i386 build completes successfully. These files don't cause any issues with an amd64 build, however. chroot-sources/wheezy.chroot: --begin-- deb http://ftp.ca.debian.org/debian wheezy main --end-- chroot-apt/preferences: --begin-- Package: libcairo2 Pin: release n=wheezy Pin-Priority: 600 Package: libpixman-1-0 Pin: release n=wheezy Pin-Priority: 600 Package: libxft2 Pin: release n=wheezy Pin-Priority: 600 Package: * Pin: release n=wheezy Pin-Priority: 1 Package: brasero Pin: version * Pin-Priority: -1 --end-- Is there anything in there that looks suspicious? (Aside from the begin/end markers that aren't actually in the files) -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e2093b0.60...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-15 03:29 PM, Daniel Baumann wrote: On 07/15/2011 09:23 PM, Daniel Ellison wrote: Is there anything in there that looks suspicious? (Aside from the begin/end markers that aren't actually in the files) not in particular, however, as soon as you build anything but stable (or stable with proper backports), you can have any breakage at any time, depending on the state of the testing repos you're pinning. as you know, i prefere using backports. if you could elaborate why you need which and what for, we might find a solution (some of the packages you're pinning i already have in my own backports, you could use those instead). I'm attempting to include newer versions of the packages related to font rendering and presentation. I don't like the default in Debian, so I'm configuring my distribution to render fonts more like Ubuntu does. If these packages are available as backports I could definitely add them that way instead. I've never done that, but I'm certainly willing to learn! One more detail: it fails with /just/ the wheezy.chroot file in place - no chroot-apt/preferences file. Sorry, I should have mentioned that before. It fails differently though: instead of the large list of packages to be installed, it only installs a minimal set: The following packages have been kept back: apt apt-utils aptitude gcc-4.4-base iproute iputils-ping libacl1 libattr1 libcwidget3 libdb4.8 libgcc1 libgdbm3 libpam-modules libpam0g libselinux1 libsigc++-2.0-0c2a libstdc++6 libudev0 libxapian22 man-db udev wget The following packages will be upgraded: adduser base-files bsdmainutils bsdutils cpio cron debconf debconf-i18n debianutils dpkg e2fslibs e2fsprogs gnupg gpgv grep groff-base hostname ifupdown initscripts insserv iptables isc-dhcp-client isc-dhcp-common libblkid1 libboost-iostreams1.42.0 libc-bin libc6 libcomerr2 libept1 liblocale-gettext-perl libncurses5 libncursesw5 libnewt0.52 libpam-runtime libreadline6 libsepol1 libslang2 libsqlite3-0 libss2 libssl0.9.8 libtext-charwidth-perl libtext-iconv-perl libusb-0.1-4 libuuid1 login lsb-base manpages module-init-tools mount nano ncurses-base ncurses-bin net-tools netbase netcat-traditional passwd perl-base procps readline-common rsyslog sed sensible-utils sysv-rc sysvinit sysvinit-utils tar tasksel tasksel-data tzdata util-linux vim-common vim-tiny whiptail Very odd. But if switching to backports works, then I can forget about this issue and move on. I'm still curious as to what is happening here, though. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e209a09.5070...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-15 05:02 PM, Daniel Baumann wrote: On 07/15/2011 09:50 PM, Daniel Ellison wrote: I don't like the default in Debian, so I'm configuring my distribution to render fonts more like Ubuntu does. can you elaborate (what packages, what changes, where can one see the diff, etc.)? Well to start, here are screenshots of both Debian Squeeze and SyrinxOS Debussy immediately after installation of the OS and then Chromium: Debian: http://syrinxos.com/public/stock-debian-squeeze.png Syrinx: http://syrinxos.com/public/stock-syrinx-debussy.png Everyone has their own opinion of what makes good font rendering (if they think about it at all). This is my personal preference. To me, it makes an immense difference to the look and feel of the OS. The files that I need to update are the ones I pin in chroot_apt/preferences: libcairo2 libpixman-1-0 libxft2 There's another one that needs to be included but refuses to be pinned for some reason: gtk2-engines-murrine That's a problem to be solved later. In the meantime I simply included the appropriate version in chroot_local-packages/ I also include a ".fonts.conf" in /etc/skel/ with p 1reset font preferences: true true mode="assign">hintslight true rgb mode="assign">lcddefault 84 I did a /lot/ of research to get this right, so maintaining it for the i386 ISO is very important to me. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e21d479.1090...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-16 02:12 PM, Daniel Ellison wrote: The files that I need to update are the ones I pin in chroot_apt/preferences: libcairo2 libpixman-1-0 libxft2 There's another one that needs to be included but refuses to be pinned for some reason: gtk2-engines-murrine Just to clarify, these are /all/ of the packages I need to pin for SyrinxOS. The packages needed for improved font rendering are only libcairo2 and libxft2. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e21f6ef.5030...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-15 03:50 PM, Daniel Ellison wrote: Very odd. But if switching to backports works, then I can forget about this issue and move on. I'm still curious as to what is happening here, though. None of the packages I need are in the squeeze backports. I ended up just putting the appropriate .deb files in chroot_local-packages for now instead of pinning the packages. This allowed me to build the i386 ISO and have it be the same as the amd64 ISO. For those who are interested, here's where you can get the i386 ISO: http://journal.syrinxos.com/post/7727056901/syrinxos-debussy-i386-is-now-available Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e235a18.5060...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-14 12:22 PM, Daniel Ellison wrote: On 11-07-14 11:30 AM, Daniel Baumann wrote: Also, it might be worth to publish your config tree so one can have a look at it. do you use public VCS for syrinx os? I don't yet use a public VCS but I plan to. I wanted to get the first release out for both amd64 and i386 before publishing everything. I didn't expect to be stuck on this step. I was thinking of using Launchpad for source publishing and bug tracking, though I've never used it before so I'm open to suggestions. Now that the i386 ISO of SyrinxOS has been released I’ve set up a public repository of the Debian Live configuration at launchpad.net. This is my first project at Launchpad, so I may need to make some changes as I understand more clearly how it works. https://launchpad.net/syrinxos Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e247d6f.8030...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-19 04:25 AM, Michal Suchanek wrote: On 19 July 2011 09:59, Daniel Bamann what changes did you apply to the two packages exactely? do you know why the changes are not included in the vanilla debian packages? As I understand it these are just from Wheezy, not patched. So these are in Debian proper, just not in stable. That's correct: they're not patched. These packages aren't in stable or backports, actually. In theory, the font rendering I'm after is already supported in wheezy. All that should be needed is a bit of configuration. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e254843@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-19 06:48 AM, Michal Suchanek wrote: On 14 July 2011 20:14, Daniel Ellison wrote: If I can't figure this out soon, I might skip the i386 build for now and concentrate on getting the source to a public repository, setting up a bug tracker, website, etc. Note that this might be a dependency issue rather than mirror issue. Yes, you are almost certainly correct here. Singular pinning does not work well with apt, it insists on getting all packages from the preferred release. If you pin cairo and it needs some dependency from testing which is not pinned it will not be installed (and you should get a message about "package xxx requires yyy>= something but something_lower is going to be installed"). Oddly, it gave me that message with /every/ package that I specified in my chroot_local/packagelists/syrinx.list. Actually, it said "but it is not going to be installed ". And I also found that by removing chroot_apt/preferences and leaving chroot-sources/wheezy.chroot (which simply contains "deb http://ftp.debian.org/debian wheezy main"), the i386 build still failed: It refused to install any of the packages I specified, instead building what I think was a "standard" build. With aptitude this tends to work better. It tries random solutions until it finds one that matches but tends to upgrade/downgrade unrelated packages in the process or it might find a solution that does not install anything. Now i386 and amd64 are quite different architectures wrt dependencies. i386 has "split libs" like libc6 + libc6-i686. If your pinning needs upgrade to one of these split libs it would not be surprising that the solution differs. Also some package builds may occasionally lag on i386 due to split lib error which is not present on other archs. This is excellent information! Thank for that. It really does clarify why things may go haywire after what /seems/ to be a simple configuration change. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e256c2d.9010...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-19 05:25 AM, Daniel Baumann wrote: On 07/19/2011 11:02 AM, Daniel Ellison wrote: As I understand it these are just from Wheezy, not patched. this is what confused me.. Daniel links in http://journal.syrinxos.com/post/6789632136/fonts-more-important-than-you-might-think to https://sites.google.com/site/quanli/davidturner%27slcdcleartype-likepatchesandpackagesfordebiansid which lists a bunch of patches and stuff, and, as far as i could see, ubuntu uses patched packages of some of the packages mentioned on above site. Ah, you missed one key piece of information on my journal page: "In addition, these tweaks are already present in the newer libraries involved". :) I linked to the other page in order to show what is being done to enable improved font rendering. I'll clarify in a comment to that post. So these are in Debian proper, just not in stable. fine; so let's just make the backports then and be done with it :) Woohoo! in fact, i've got the cairo already in my own backports (because of the mozilla backports) at archive.p-l.o; i'll do xft at latest after debconf too. unrelated to that, someone might want to engage with debian-backports to make them available there too. Excellent. As I said, I believe few people actually think about font rendering, but when it's right, the whole OS just feels better. All that should be needed is a bit of configuration. just to make sure that i've got it completely, the only thing to configure is that .fonts.conf thing and it's all set? Yes, in theory that is all you should need to do. It's easy to test: just drop my .fonts.conf in your home directory and log out/in. If you try it, please let me know how it goes. In future, I'll be putting the font configuration in /etc/fonts/conf.d so it's available to the system. Hey, SyrinxOS is still in alpha! :) Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e256f55.4070...@syrinx.net
Re: Can't create an i386 ISO, but amd64 works fine
On 11-07-19 10:41 AM, Daniel Baumann wrote: On 07/19/2011 01:49 PM, Daniel Ellison wrote: Yes, in theory that is all you should need to do. It's easy to test: just drop my .fonts.conf in your home directory and log out/in. If you try it, please let me know how it goes. will do, but after debconf (means, not until the first week of august). Sounds good to me! No rush. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e25a889.5090...@syrinx.net
Re: Vanillux live iso
On 11-08-11 10:06 PM, Fabrice Quenneville wrote: So i have now made a syslinux theme based on the progress one. I cannot find where to get it included tho, Any pointers on that ? Take a look at this message: http://lists.debian.org/debian-live/2011/06/msg00188.html -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e44ecc9.6080...@syrinx.net
Changed location of syslinux theme?
Hi all, I've been away for a while due to health problems with my wife. I'm the creator of SyrinxOS using the Debian live build tools. I'm now getting back into maintaining my distribution. The first thing I tried was simply rebuilding an ISO. The process was goilg well until I got: -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec56ac1.4040...@syrinx.net
Changed location of syslinux theme?
Sorry, hit the wrong key. :/ Hi all, I've been away for a while due to health problems with my wife. I'm the creator of SyrinxOS using the Debian live build tools. I'm now getting back into maintaining my distribution. The first thing I tried was simply rebuilding an ISO. The process was goilg well until I got: E: Unable to locate package syslinux-themes-syrinx-debussy For reference, I'm using the very latest live build tools (3.0~a39-1). The last time I built an ISO it worked fine. The syslinux-themes-syrinx-debussy_0-1_all.deb is still in config/chroot_local-packages. Any thoughts? -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec56c75.3040...@syrinx.net
Re: Changed location of syslinux theme?
On 17/11/11 06:53 PM, Daniel Baumann wrote: the layout of config/* did change since you last used 3.x, i suggest you have a look at the changelog and since your last used version and go on from there. we'll provide soon some sample configs that can be used for a more hands-on view on current stuff. Ah, that explains it! :) Thanks, Daniel. I'll take a look at the differences in layout. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec6660d.4060...@syrinx.net
Simple default ISO generation fails
Hi all, I can't successfully create an ISO from a fresh install of live-build. I set up a new virtual machine in KVM and installed standard Debian Squeeze using debian-6.0.3-amd64-netinst.iso. I then installed live-build_3.0~a39-1_all.deb. As root in the VM, I did "lb config", then "lb build". This produced an ISO that wouldn't get past the initial screen with the choice to enter the live system. Knowing why this happened, I placed a binary hook called kernel.binary (yes, it's executable) into config/hooks which renames vmlinuz and initrd.img: #!/bin/sh mv binary/live/vmlinuz-* binary/live/vmlinuz || true mv binary/live/initrd.img-* binary/live/initrd.img || true This is a script Daniel Baumann pointed out to me a few months ago. After that, I did an lb clean && lb build. I would expect the resulting binary-hybrid.iso to boot into Debian. It didn't. On running "kvm --cdrom binary-hybrid.iso" as per the 3.x manual, the VM starts up and allows me to get past the screen with the option to boot into a live system. As the boot process progresses, I see: Mount point '/filesystem.squashfs' does not exist. Skipping mount. Further along, I see: startpar: service(s) returned failure: udev console-setup live-boot ... failed! Obviously none of this should be happening. I couldn't have used a more stock, new system. And I did nothing else but install the latest live-build. Does anyone have any idea what might be going wrong? Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecfeb3b.9040...@syrinx.net
Re: Simple default ISO generation fails
On 25/11/11 02:23 PM, Daniel Ellison wrote: On running "kvm --cdrom binary-hybrid.iso" as per the 3.x manual, the VM starts up and allows me to get past the screen with the option to boot into a live system. As the boot process progresses, I see: Mount point '/filesystem.squashfs' does not exist. Skipping mount. Earlier in the boot sequence I see: Begin: Mounting "/live/image/live/filesystem.squashfs" on "//filesystem.squashfs" via "/dev/loop0" ... done. So it seems that squashfs is being mounted successfully. To clarify, I generate the ISO in the VM, then I copy it to my real system and run it with KVM there. There should be no difference, but I didn't want people thinking I had installed KVM in the VM. :) -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ecff381.7050...@syrinx.net
Re: Simple default ISO generation fails
On 25/11/11 02:58 PM, Daniel Ellison wrote: So it seems that squashfs is being mounted successfully. To clarify, I generate the ISO in the VM, then I copy it to my real system and run it with KVM there. There should be no difference, but I didn't want people thinking I had installed KVM in the VM. :) Is this not unusual behaviour? Or am I missing something? I started with a clean VM install of default Debian 6.0.3 and live-build 3.0 a39. Should I not be able to create a default ISO using the instructions in the manual? Or are there bugs I should be working around (aside from the vmlinuz and initrd.img renaming)? -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed3f2b6.8020...@syrinx.net
Re: Simple default ISO generation fails
On 2011-11-28, at 3:44 PM, Daniel Ellison wrote: > Is this not unusual behaviour? Or am I missing something? I started with a > clean VM install of default Debian 6.0.3 and live-build 3.0 a39. Should I not > be able to create a default ISO using the instructions in the manual? > > Or are there bugs I should be working around (aside from the vmlinuz and > initrd.img renaming)? I did check and the status page for live-build 3.x says that a wheezy build should work. As this is the default for 3.x it follows that I should be successful when simply producing a default ISO. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5942c103-f161-4700-a24c-8d0181c5d...@syrinx.net
Re: Simple default ISO generation fails
On 28/11/11 04:18 PM, Daniel Ellison wrote: On 2011-11-28, at 3:44 PM, Daniel Ellison wrote: Is this not unusual behaviour? Or am I missing something? I started with a clean VM install of default Debian 6.0.3 and live-build 3.0 a39. Should I not be able to create a default ISO using the instructions in the manual? Or are there bugs I should be working around (aside from the vmlinuz and initrd.img renaming)? I did check and the status page for live-build 3.x says that a wheezy build should work. As this is the default for 3.x it follows that I should be successful when simply producing a default ISO. This issue was never resolved. However, when I went ahead and set up my distribution under the latest 3.x, I was able to produce a working amd64 squeeze ISO. People just starting out with 3.x and who follow the manual to try producing a default ISO will be very confused, unless it was something I was doing wrong. I guess I'll never know. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed66889.4080...@syrinx.net
A new release of SyrinxOS, my Debian-based Linux distribution created with live build
Hi all, I've just released a new version of my Debian-based distribution SyrinxOS. It is built entirely with the Debian live build tools. You can read all about it here: http://journal.syrinxos.com/post/13556609295/syrinxos-debussy-0-4-0-alpha-squeeze-released If you do try it out, please let me know what you think. I see so many people here talking about using these tools, but I rarely see the results of using these tools. I thought I would provide results. :) Regards, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed696ce.30...@syrinx.net
Re: A new release of SyrinxOS, my Debian-based Linux distribution created with live build
On 2011-11-30, at 4:16 PM, Éclipse M wrote: > Thanks for sharing your new release. > Juste a word for your site... It should be better if you mention the iso size. Thats a great idea. As soon as I get home I'll add that information. Thanks M. Éclipse! -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/94fe4f6f-e6c9-4bf7-b2d4-51a8c0c49...@syrinx.net
Re: A new release of SyrinxOS, my Debian-based Linux distribution created with live build
On 30/11/11 04:31 PM, Daniel Ellison wrote: On 2011-11-30, at 4:16 PM, Éclipse M wrote: Thanks for sharing your new release. Juste a word for your site... It should be better if you mention the iso size. Thats a great idea. As soon as I get home I'll add that information. Thanks M. Éclipse! ISO size information is now included. Also, new screenshots have been been added for the new release. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ed782c3.8020...@syrinx.net
Re: A new release of SyrinxOS, my Debian-based Linux distribution created with live build
On 01/12/11 08:36 AM, Daniel Ellison wrote: ISO size information is now included. Also, new screenshots have been been added for the new release. A new SyrinxOS 0.4.1 ALPHA release, hot on the heels of the 0.4.0 ALPHA release. Read about it here: http://journal.syrinxos.com/post/13777219768/syrinxos-debussy-0-4-1-alpha-squeeze-released Thanks! -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4edcc9c0.1040...@syrinx.net
Re: A new release of SyrinxOS, my Debian-based Linux distribution created with live build
On 05/12/11 08:40 AM, Daniel Ellison wrote: A new SyrinxOS 0.4.1 ALPHA release, hot on the heels of the 0.4.0 ALPHA release. Read about it here: This will be the last release for a while. SyrinxOS is in good shape now, so I'll be concentrating on more back-end issues than anything else. You can read all about it and download the ISOs here: http://journal.syrinxos.com/post/13832906683/syrinxos-debussy-0-4-2-alpha-squeeze-released Let me know if you try it out! -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ede5f86.1000...@syrinx.net
Re: Simple default ISO generation fails
On 30/11/11 12:31 PM, Daniel Ellison wrote: This issue was never resolved. However, when I went ahead and set up my distribution under the latest 3.x, I was able to produce a working amd64 squeeze ISO. People just starting out with 3.x and who follow the manual to try producing a default ISO will be very confused, unless it was something I was doing wrong. I guess I'll never know. I would /really/ like to know what the issue is here. I want to build a wheezy binary-hybrid.iso. As I described earlier, I'm simply trying to create a stock wheezy image with no luck. I can't think of a way to simplify the process any more. I am able to produce a squeeze image of my distribution, so it's not like my setup is broken or anything. And besides, I was trying to produce a wheezy ISO in a VM, so it couldn't be my local development environment. Anyone? Bueller? -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee617fa.2080...@syrinx.net
Re: Simple default ISO generation fails
On 12/12/11 10:10 AM, Ben Armstrong wrote: And if this were generally happening to everyone, you would think there would be more complaints here, wouldn't you?*** I /totally/ agree! I guess nobody else is having this problem because something *is* different about your development environment. Have you tried building it again, but *not* in a VM? That's certainly one slightly odd aspect of your build environment that I think the average user would not have to deal with. Yes, I tried that this morning. In fact, that's why I came back to this thread: I'm not able to produce a stock wheezy ISO in my normal build environment. *** That being said, I have not, personally, built an image in some weeks, so I can't vouch for whether what you've tried recently "just works" in general or not. So it's important we not just drop the thread here and get more information about your problem to make sure we're not overlooking an important bug. I agree again. The only reason I tried building it in a VM was to make the attempt in as clean an environment as possible. I don't have a spare computer that I can experiment with, so a VM was the next best thing. I always try to get things as simple as possible when troubleshooting. Some would argue that a VM is not simple, but I use them all day every day. I have a handle on them. :) When I was having this issue a couple of weeks back I got around it by setting the whole thing up in my build environmant as my distribution, with all includes, etc. I'm trying the same thing right now for a wheezy build and will report back with the results. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee62414.3080...@syrinx.net
Re: Simple default ISO generation fails
On 12/12/11 10:56 AM, Daniel Ellison wrote: When I was having this issue a couple of weeks back I got around it by setting the whole thing up in my build environmant as my distribution, with all includes, etc. I'm trying the same thing right now for a wheezy build and will report back with the results. I spent /all day/ yesterday trying unsuccessfully to produce a bootable Wheezy image of any kind with live build. This morning in desperation I installed debian-testing-amd64-netinst.iso to an external USB hard drive and booted into Wheezy. I then installed live build a39 from the repos. I typed "lb config" in a terminal. When it was done, I copied the kernel rename hook script to config/hooks and did "lb build". Everything went as expected and a binary-hybrid ISO was produced. I copied that ISO to a USB thumb drive (/dev/sdd) with: dd if=binary-hybrid.iso of=/dev/sdd bs=4M;sync After it was finished, I booted into the USB drive. I got to the selection screen (which had "live" and "other options") and chose "live". The boot progressed until it said "Running /scripts/live-premount ... done". It then started producing: /init: line 7: /lib/udev/path_id: not found in an endless stream. This is an ISO produced in a brand new Wheezy install on an external USB hard drive with the live build in the repos and everything at default. To be clear, I have no problem producing any number of Squeeze variations on USB thumb or hard drives, in KVM virtual machines, whatever. They all work. I'm on the verge of giving up on live build. That would be sad because I really enjoy creating my own distribution and I don't know of any other reliable tools that will do the job. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee75c98.2030...@syrinx.net
Re: Simple default ISO generation fails
On 13/12/11 09:09 AM, Daniel Ellison wrote: This is an ISO produced in a brand new Wheezy install on an external USB hard drive with the live build in the repos and everything at default. To be clear, I have no problem producing any number of Squeeze variations on USB thumb or hard drives, in KVM virtual machines, whatever. They all work. Isn't this a big issue? I did my best to reproduce the problem in an environment that I knew was clean. And it wasn't running in a VM; it was on the bare hardware. I was not able to produce a working default Wheezy ISO using the instructions in the manual. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee8c4a3.6060...@syrinx.net
Re: Simple default ISO generation fails
On 14/12/11 12:27 PM, Ben Armstrong wrote: If I had more time, I'd be helping with this one more, but I'm sure you understand this is a quite busy time of year. Yeah, I hadn't taken that into account. :) Thanks for taking the time to respond. Keep in mind that if you're building wheezy images you are *not* using the latest versions of some components (e.g. live-boot, live-config and the corresponding back-end packages that are dependencies of each) unless you take special measures to use them (see live-manual about that). I'll take a look in the manual and see what's what. I'm thinking you're referring to section 3.3.3: "From 'snapshots'". Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee8e272.2090...@syrinx.net
Re: Simple default ISO generation fails
On 14/12/11 01:34 PM, Ben Armstrong wrote: On 12/14/2011 01:52 PM, Daniel Ellison wrote: I'll take a look in the manual and see what's what. I'm thinking you're referring to section 3.3.3: "From 'snapshots'". Actually (and you should check this, as I don't have it in front of me) I was thinking of the "APT pinning" example. Oh, ok. I added "--archives live.debian.net" to my auto/config, as per section 3.3.3, but it made no difference. :) I'll try pinning live-boot, live-config and their corresponding dependencies from sid. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee8f28b.1070...@syrinx.net
Re: Simple default ISO generation fails
On 14/12/11 02:01 PM, Daniel Ellison wrote: On 14/12/11 01:34 PM, Ben Armstrong wrote: Actually (and you should check this, as I don't have it in front of me) I was thinking of the "APT pinning" example. Oh, ok. I added "--archives live.debian.net" to my auto/config, as per section 3.3.3, but it made no difference. :) I'll try pinning live-boot, live-config and their corresponding dependencies from sid. I'm coming back to this as I've been totally unable to build a vanilla wheezy ISO using a wheezy development system. I did try the above-described pinning, with no difference in the result. Here's the Debian version I'm using in my development system: # cat /etc/debian_version wheezy/sid Here's the live build version: # lb --version live-build, version 3.0~a40-1 In a new, empty directory I do "lb config" then copy this "kernel.binary" script into config/hooks: #!/bin/sh mv binary/live/vmlinuz-* binary/live/vmlinuz || true mv binary/live/initrd.img-* binary/live/initrd.img || true I then do "lb build" and it produces a binary-hybrid.iso, which I write to a USB key with: dd if=binary-hybrid.iso of=/dev/sdd bs=4M;sync I reboot into the USB key, and as the boot process progresses, I see: Mount point '/filesystem.squashfs' does not exist. Skipping mount. Further along, I see: startpar: service(s) returned failure: udev console-setup live-boot ... failed! As detailed in a previous message, earlier in the boot sequence I DO see: Begin: Mounting "/live/image/live/filesystem.squashfs" on "//filesystem.squashfs" via "/dev/loop0" ... done. The system then drops into runlevel 2 and gives me a terminal login prompt. If there's anything I'm missing, leaving out, doing wrong, misunderstanding, please let me know. I would dearly love to create a wheezy build of my distribution. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f0c70b7.8070...@syrinx.net
Re: Simple default ISO generation fails
On 25/01/12 02:03 AM, Jake Norling aka Snow Keld wrote: i hold these packages to squeeze versions: live-boot live-boot-initramfs-tools live-config live-config-sysvinit this worked for me in october but some change in unstable after that time caused the live boot to fail with error: /init: line 7: /lib/udev/path_id: not found after much work i have solved the problem. udev package must have been the change, or something relating to it. i found that you MUST use the corresponding version of live-boot-initramfs-tools i suggest you use versions of udev and live-boot-initramfs-tools from the same dist. if you continue to fail then check version differences between testing and unstable, likely you need live-boot-initramfs-tools pulled from unstable. Thanks for the response, Jake/Snow. I'll try adding udev to my pinned sid live-* packages in chroot_apt/preferences and see what happens. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f204aa0.1010...@syrinx.net
Re: Simple default ISO generation fails
On 25/01/12 01:32 PM, Daniel Ellison wrote: Thanks for the response, Jake/Snow. I'll try adding udev to my pinned sid live-* packages in chroot_apt/preferences and see what happens. Unfortunately it made no difference. My config/chroot_apt/preferences now looks like this (with no line breaks): Package: live-boot live-boot-initramfs-tools live-config live-config-sysvinit udev Pin: release n=sid Pin-Priority: 1001 Package: * Pin: release n=sid Pin-Priority: 1 and I have deb http://ftp.us.debian.org/debian sid main in config/archives/sid.list.chroot Ah well, I'll keep on plugging at it. Thanks for the help! -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f206a6e.2040...@syrinx.net
Re: Simple default ISO generation fails
On 25/01/12 07:37 PM, Ben Armstrong wrote: Ah, never mind. Rechecked apt_preferences(5) on squeeze which says: *snip* So multiple packages in the same line should work. For the record, pinning with multiple packages on the same line does work: $ apt-cache policy live-boot Installed: 3.0~a24-1 Candidate: 3.0~a24-1 Package pin: 3.0~a24-1 Version table: *** 3.0~a24-1 1001 and so on. Similarly: $ apt-cache policy udev Installed: 175-3 Candidate: 175-3 Package pin: 175-3 Version table: *** 175-3 1001 etc. They all correspond to the correct sid versions. Same in *.packages. Believe me, I wish that HAD been the issue. Then I could have made some progress on a wheezy version of my distribution. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f2149b3.4000...@syrinx.net
Re: Simple default ISO generation fails
On 26/01/12 07:40 AM, Daniel Ellison wrote: Believe me, I wish that HAD been the issue. Then I could have made some progress on a wheezy version of my distribution. Just to reiterate, when I boot from the resulting wheezy binary-hybrid ISO into a live system, I see these warnings and errors, then get dropped into a command line: Creating compatibility symlink from /etc/mtab to /proc/mounts. ... (warning). Mount point '/filesystem.squashfs' does not exist. Skipping mount. ... (warning). startpar: service(s) returned failure: udev console-setup live-boot ... failed! Then, not surprisingly: INIT: Entering runlevel: 2. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f214cb4.4020...@syrinx.net
Re: Debian live system, booting difficulties
On 01/02/12 07:09 AM, christoffer krakou wrote: Hello people. I'm trying to build a live system using the Debian Live Builder, But i cannot get it to work. Just building the vanilla image with the default config produces an image wich never gets past the bootloader When i boot the hybrid-iso (i have tried using virtualbox and vmware player, with similar results), it gets to the syslinux boot menu. From here, i cannot boot the live kernel. If i exit the graphical menu and type "live", it simply says that the kernel is not found. i'm building the system using a Ubuntu 11.04 desktop. i've been trying for a few days now. What could be wrong? i feel i've tried everything You need to put a hook named (for example) "kernel.binary" into config/hooks that goes something like this: #!/bin/sh mv binary/live/vmlinuz-* binary/live/vmlinuz || true mv binary/live/initrd.img-* binary/live/initrd.img || true Make sure it's executable. This assumes you're using live build 3.x. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f29322b.9030...@syrinx.net
Re: Simple default ISO generation fails
On 07/02/12 07:54 AM, Daniel Baumann wrote: [ this time intentionally on CC to ensure you do not miss it :) ] Thank you! sorry for the late answer, didn't read the thread until now, and sorry that it took so long to fix things up; however, as of yesterday, all your issues are fixed with live-* in sid. it might take a while until stuff migrates to testing though (but, like you were told, you can use pinning in the meanwhile). That is FANTASTIC news! I'll try it out right away. Well, as soon as I can, anyway. If it works, I can finally get past this roadblock and start serious work on getting a wheezy ISO out the virtual door. It also means I can use it myself! :) Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f31203a.8020...@syrinx.net
Re: Simple default ISO generation fails
Ok. This morning I set up a completely clean wheezy/testing system using the latest netinst ISO from here: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/ I added nothing. In fact, it boots to a command line. No desktop, no X11, nothing. I did the following in that clean wheezy system: $ sudo su # apt-get install debootstrap # wget http://live.debian.net/archive/packages/live-build/3.0~a42-1/live-build_3.0~a42-1_all.deb # dpkg -i live-build_3.0~a42-1_all.deb # mkdir wheezy # cd wheezy # lb config # cp ~/kernel.binary config/hooks "kernel.binary" is a script to rename vmlinuz and initrd.img so that choosing "Live" in the boot menu works properly. The script is executable, and I know it's working by the fact that I can get past the initial boot screen. I then set things up to use the live boot/live config tools from sid by pinning them in config/chroot_apt/preferences: Package: live-boot live-boot-initramfs-tools live-config live-config-sysvinit Pin: release n=sid Pin-Priority: 1001 Package: * Pin: release n=sid Pin-Priority: 1 I have confirmed that the pinning works. I also added deb http://ftp.us.debian.org/debian sid main to config/archives/sid.list.chroot. Then: # lb build This /should/ produce a functioning live wheezy system. However, the resulting binary-hybrid.iso gives the same errors as I have described several times in the past. I even repeated the process with udev pinned to sid as well (as per a response earlier in this thread) with the same result. Can anyone reproduce this behaviour? -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f316233.9070...@syrinx.net
Re: Simple default ISO generation fails
On 07/02/12 12:51 PM, Daniel Baumann wrote: you need 3.0~a43-1. Ah, that would probably help. :) I usually get my live-build packages from http://live.debian.net/archive/packages/live-build/ But there doesn't seem to be a live-build_3.0~a43-1_all.deb available there. It seems like only the source for a43 is currently available. Is that correct? -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f316737.5000...@syrinx.net
Re: Simple default ISO generation fails
On 07/02/12 01:02 PM, Daniel Ellison wrote: But there doesn't seem to be a live-build_3.0~a43-1_all.deb available there. It seems like only the source for a43 is currently available. Is that correct? Never mind. Found it. :) -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f31678e.5070...@syrinx.net
Re: Simple default ISO generation fails
On 07/02/12 01:03 PM, Daniel Ellison wrote: Never mind. Found it. :) Didn't work! On my dev machine: # cat /etc/debian_version wheezy/sid # apt-cache policy live-build live-build: Installed: 3.0~a43-1 Candidate: 3.0~a43-1 Version table: *** 3.0~a43-1 0 100 /var/lib/dpkg/status 3.0~a42-1 0 500 http://ftp.ca.debian.org/debian/ wheezy/main amd64 Packages On the resulting binary-hybrid.iso booted into live: $ apt-cache policy live-boot live-boot: Installed: 3.0~a25-1 Candidate: 3.0~a25-1 Package pin: 3.0~a25-1 Version table: *** 3.0~a25-1 1001 $ apt-cache policy live-boot-initramfs-tools live-boot-initramfs-tools: Installed: 3.0~a25-1 Candidate: 3.0~a25-1 Package pin: 3.0~a25-1 Version table: *** 3.0~a25-1 1001 And so on. All versions seem to be correct. Booting into the live system gives exactly the same errors as described earlier in this thread, and I end up at a command prompt. It now seems to me that it has nothing to do with the versions of utilities I've been using. There's some other fundamental issue I'm missing. Does the sequence of operations I described a couple of messages ago make sense? I can't reboot right now (backing up 1.5 TB of data from a remote machine) but when I can, I'll actually boot my laptop from a USB stick with the binary-hybrid ISO copied onto it with "dd". Today I've been using a VM for that purpose. Up until I tried building a wheezy system at the end of last November, using a VM never once caused an issue, and in fact has been an excellent way to develop my distribution. Hopefully this has nothing to do with virtualization! :) Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f317b73.5030...@syrinx.net
Re: Simple default ISO generation fails
On 07/02/12 02:48 PM, Daniel Baumann wrote: what errors exactely? sorry, i'm kind of lost with all this back and forth. Early on in the boot sequence I see: Begin: Mounting "/live/image/live/filesystem.squashfs" on "//filesystem.squashfs" via "/dev/loop0" ... done. But later on I get: Mount point '/filesystem.squashfs' does not exist. Skipping mount. ... (warning). and later: startpar: service(s) returned failure: udev console-setup live-boot ... failed! Hopefully this has nothing to do with virtualization! :) i don't think so; building in a vm/container is safe, i do it all the time. That's good to hear. Just to eliminate that possibility, I'm building an ISO right now on my laptop, no VMs in sight. Hopefully (!) it'll fail in the same way. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f3181ff.20...@syrinx.net
Re: Simple default ISO generation fails
On 07/02/12 04:00 PM, Daniel Baumann wrote: startpar: service(s) returned failure: udev console-setup live-boot ... failed! what backend do you use, sysvinit? Yes, as in live-config-sysvinit. It's pinned to sid as are live-boot, live-boot-initramfs-tools, and live-config. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f326c01.1070...@syrinx.net
Re: Simple default ISO generation fails
On 08/02/12 04:32 PM, Daniel Baumann wrote: On 02/08/2012 01:35 PM, Daniel Ellison wrote: On 07/02/12 04:00 PM, Daniel Baumann wrote: startpar: service(s) returned failure: udev console-setup live-boot ... failed! i cannot reproduce that with a sid default image, files are available at http://unable-to-package.org/~daniel/live/ I downloaded your binary-hybrid.iso, fired it up in a VM, and got exactly the same errors. Just to make certain I got your ISO and wasn't mistakenly using an old one of mine, I downloaded your ISO again and got the same results. I then copied it to a USB key: sudo dd if=binary-hybrid.iso of=/dev/sdd bs=4M;sync I booted my laptop from that USB key - and got the same errors! When I first started up your ISO, I saw that it was 486/686-pae. I've been working in a 64 bit system, so I thought the problem might have been the difference between the two. But if your ISO did the same thing, then that narrows things down a LOT. It can't be my laptop hardware because the same thing happens in a VM. So what could it possibly be? Does the ISO you produced boots properly on your system, both VM and hardware? By the way, thanks for your continued efforts to help clear this up, Daniel. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f33b090.6070...@syrinx.net
Re: Simple default ISO generation fails
On 09/02/12 06:52 AM, Daniel Baumann wrote: On 02/09/2012 12:40 PM, Daniel Ellison wrote: So what could it possibly be? no idea; and, just to be unambigues: the '/filesystem.squashfs' error is just cosmetics (with newer sysvinit in wheezy/sid), the 'only' error that matters is the 'startpar: service(s) returned failure' one. Sorry, I should have said "error" and not "errors". I realize it's the startpar error that matters. The rest are (cosmetic) warnings. Does the ISO you produced boots properly on your system, both VM and hardware? yes. can you try it on some more hardware of yours to rule out specific issues with your system? I can, but I'll have to wait until this evening. All I have here at work is my laptop and a bunch of Apple hardware. Apple hardware /really/ doesn't like booting from anything USB. But... it does the same thing in a VM, so I'm not convinced it's my hardware. It /is/ a VM running on my same laptop, so maybe that has something to do with it. With this thought, I turned off hardware virtualization (VT-x) and even disabled PAE/NX. I also cut it down to 1 processor from 2. The same startpar error occurs. Just to remind us, I have no problem whatsoever working with squeeze images, either in a VM or on this laptop's hardware. also, can you build an image where the necessary components (live-boot init script for the beginning should be enough, maybe also live-config initscript later at some point) are run with set -x so that we can see the 'debug' log, so we can try to understand where and what the actual problem is. Sure! I'll have to explore how to run live-boot's init script with "set -x", but I'll definitely do that and make the debug log available. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f33b9ec.4060...@syrinx.net
Re: Bug#659199: Acknowledgement (live-build: live wheezy -> cp: cannot stat `/root/syslinux/vesamenu.c32': No such file or directory)
On 09/02/12 10:12 AM, Daniel Baumann wrote: On 02/09/2012 03:42 PM, upite...@lycos.com wrote: I've done what you suggest and still get this problem: and you are really, really sure that you're using live-build 3.0~a43-1 and have no tained build system? like i said, i cannot reproduce that at all, it just works. the next step would be to rule out the host systems configuration and build in a chroot: # debootstrap sid sid http://ftp.de.debian.org/debian/ # chroot sid # apt-get install live-build # mkdir debian-live # cd debian-live # lb config --mode debian -d wheezy -b hdd -p xfce # lb build In the interest of solving another problem, I followed these chroot steps exactly and got the same results as Piotr. It's looking in /root/syslinux for vesamenu.c32. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f33f091.90...@syrinx.net
Re: Simple default ISO generation fails
On 09/02/12 07:19 AM, Daniel Ellison wrote: On 09/02/12 06:52 AM, Daniel Baumann wrote: also, can you build an image where the necessary components (live-boot init script for the beginning should be enough, maybe also live-config initscript later at some point) are run with set -x so that we can see the 'debug' log, so we can try to understand where and what the actual problem is. Sure! I'll have to explore how to run live-boot's init script with "set -x", but I'll definitely do that and make the debug log available. In the wheezy development VM I set up with live build a43-1, there are no "live" or "lvm2" hooks in /usr/share/initramfs-tools/hooks. They DO exist in my regular development environment on my laptop. I'm assuming I would add "x" to the "set -e" command in the "live" hook. But where are the files? Has a newer version of initramfs-tools changed its structure? -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f33f33c.5040...@syrinx.net
Re: Simple default ISO generation fails
On 09/02/12 12:21 PM, Daniel Baumann wrote: On 02/09/2012 05:24 PM, Daniel Ellison wrote: I'm assuming I would add "x" to the "set -e" command in the "live" hook. But where are the files? Has a newer version of initramfs-tools changed its structure? /usr/share/initramfs-tools/hooks/ The mystery is solved. I didn't have live-boot installed in my wheezy development environment because it was an optional step, as I recall. I've now installed live-boot, added "x" to the "set -e" command in the initramfs-tools "live" hook and am now building a wheezy ISO. That is assuming this is what you were suggesting. If not, please feel free to correct my assumptions. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f340770.6030...@syrinx.net
Re: Simple default ISO generation fails
On 09/02/12 02:05 PM, Daniel Baumann wrote: On 02/09/2012 06:50 PM, Daniel Ellison wrote: The mystery is solved. I didn't have live-boot installed in my wheezy development environment because it was an optional step, as I recall. with 'development environment', do you mean the host system or the resulting live system? The host system. Which I now realize makes no difference whatsoever. you do not need anything except live-build (and it's depends) on the host system, but you will need live-boot and live-config (plus their backend packages like live-boot-initramfs and live-config-sysvinit) on the live system. I do have live-boot etc. on the live system. I just can't figure out how to affect the live-boot init script as you described. There's a "live" hook in chroot/usr/share/initramfs-tools/hooks after running "lb build", but this gets reconfigured in the process of creating the ISO. Sorry if I'm being dense here, but I don't know where I'm supposed to be enabling debugging with "set -x". -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f341d5d.2070...@syrinx.net
Re: Bug#659199: Acknowledgement (live-build: live wheezy -> cp: cannot stat `/root/syslinux/vesamenu.c32': No such file or directory)
On 2012-02-09, at 4:38 PM, Geert Stappers wrote: > On Thu, Feb 09, 2012 at 11:13:05AM -0500, Daniel Ellison wrote: >> On 09/02/12 10:12 AM, Daniel Baumann wrote: >>> On 02/09/2012 03:42 PM, upite...@lycos.com wrote: >>>> I've done what you suggest and still get this problem: >>> >>> and you are really, really sure that you're using live-build 3.0~a43-1 >>> and have no tained build system? >>> >>> like i said, i cannot reproduce that at all, it just works. >>> >>> the next step would be to rule out the host systems configuration and >>> build in a chroot: >>> >>> # debootstrap sid sid http://ftp.de.debian.org/debian/ >>> # chroot sid >>> # apt-get install live-build >>> # mkdir debian-live >>> # cd debian-live >>> # lb config --mode debian -d wheezy -b hdd -p xfce >>> # lb build >> >> In the interest of solving another problem, I followed these chroot >> steps exactly and got the same results as Piotr. It's looking in >> /root/syslinux for vesamenu.c32. >> > > The text >>> like i said, i cannot reproduce that at all, it just works. > means something like > provide information how to reproduce the error Thanks Geert. Actually, I DID provide that information! :) I didn't do what Piotr did, I followed Daniel's chroot steps as he was asking Piotr to do. I thought it was relevant information that I got the same error when in a chroot environment. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/60f7ed8a-3111-4820-a4b0-6e4117cfb...@syrinx.net
Re: Simple default ISO generation fails
On 10/02/12 09:01 AM, Daniel Ellison wrote: I'll try that tonight and we'll see what happens. I don't have a lot of hardware on which to test this out, so that's about all I'll be able to do. The nomodeset worked and the nx7400 was able to boot. Unfortunately, it also gave the same startpar error. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f35ccfe.7060...@syrinx.net
Re: Simple default ISO generation fails
On 10/02/12 07:25 AM, Daniel Baumann wrote: On 02/10/2012 12:34 PM, Daniel Ellison wrote: So that rules out my specific laptop as being at fault. ack. Which means it is an actual bug? If so, do I need to file a bug report? Or is that already taken care of? The same "startpar" error happened on all three laptops I have access to, using your ISO on a USB key. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f3c07b3.40...@syrinx.net
Re: Help debugging startpar live-boot failure
On 01/03/12 06:28 AM, Daniel Baumann wrote: On 03/01/2012 11:32 AM, Philip Newborough wrote: 'startpar: services(s) returned failure: live-boot ... failed!' please build an image with live-boot and live-config from debian-next branch in git, it's supposed to be fixed there. Ack! I've been tearing my hair out trying to get this to work (see "Simple default ISO generation fails"), and it's already fixed? Why didn't anyone say so? Ah well. Maybe it's not the same issue. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f4f5f2e.3000...@syrinx.net
Re: Help debugging startpar live-boot failure
On 01/03/12 06:24 AM, upite...@lycos.com wrote: I get the same error on my live wheezy hdd and cannot find out howto get it away. This may be related to the issue I've had with building a wheezy image. The error I get is: startpar: service(s) returned failure: udev console-setup live-boot ... failed! But the system does NOT boot: I'm dropped into a command prompt. It was determined that it had nothing to do with my development environment or live-build configuration. Daniel Baumann built a default wheezy binary-hybrid.iso which I downloaded and tested. It produced the same error on three different laptops, though it worked fine on his systems. BTW I didin't get it on live squeeze. Nor did I. I have a working build of both i386 and amd64 versions of my distribution. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f4f5e63.2090...@syrinx.net
Re: Simple default ISO generation fails
On 15/02/12 02:29 PM, Daniel Ellison wrote: On 10/02/12 07:25 AM, Daniel Baumann wrote: On 02/10/2012 12:34 PM, Daniel Ellison wrote: So that rules out my specific laptop as being at fault. ack. Which means it is an actual bug? If so, do I need to file a bug report? Or is that already taken care of? The same "startpar" error happened on all three laptops I have access to, using your ISO on a USB key. Was this ever resolved? I've been staying away because it was too frustrating not being able to create a Wheezy ISO with default configuration. As it was determined that the problem occurred for me on three different computers using an ISO created by Daniel Baumann, and that other people were having the same or similar issues, this must have been a true bug. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f8fead8.5070...@syrinx.net
Re: Simple default ISO generation fails
On 19/04/12 10:09 AM, Daniel Baumann wrote: included in live-config 3.0~a34-1. 3.0~a35-1 migrated on 2012-04-13, so wheezy is working out of the box since then again. Thanks, Daniel! So when building a wheezy ISO on a wheezy system, if I pin like this in chroot_apt/preferences: Package: live-boot live-boot-initramfs-tools live-config live-config-sysvinit Pin: release n=sid Pin-Priority: 1001 Package: * Pin: release n=sid Pin-Priority: 1 that bug should be covered? Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f90311b.9050...@syrinx.net
Re: Simple default ISO generation fails
On 19/04/12 12:20 PM, chals wrote: If you want to pin packages from sid in wheezy I would recommend you using a wildcard as explained in live-manual Package: live-* Instead of pinning packages by name. Because if you do not turn off apt recommends it will also install live-tools from sid instead of from wheezy Actually, I got that pinning example from an older version of live-manual! :) It must have changed recently. But I realize now that the wheezy live-* packages are the same versions as the sid live-* packages, so there's no need for pinning at all. Thanks for your reply. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f903ec2.3070...@syrinx.net
Re: Simple default ISO generation fails
On 19/04/12 12:34 PM, Ben Armstrong wrote: What are you guys talking about? Daniel said: "3.0~a35-1 migrated on 2012-04-13, so wheezy is working out of the box since then again" so I don't understand why you think pinning is required ... Yes, I've since realized that and have removed the sid pinning. -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f903f82.2090...@syrinx.net
Re: Simple default ISO generation fails
On 19/04/12 11:36 AM, Daniel Ellison wrote: On 19/04/12 10:09 AM, Daniel Baumann wrote: included in live-config 3.0~a34-1. 3.0~a35-1 migrated on 2012-04-13, so wheezy is working out of the box since then again. Thanks, Daniel! So when building a wheezy ISO on a wheezy system, if I pin like this in chroot_apt/preferences: Actually, it seems I don't have to pin any of the live-* packages now. the ones in wheezy are the same as those in sid. And I guess that's what you were saying above. :) I just tried a default ISO build and it failed in the same way. I did this (as root): # lb --version live-build, version 3.0~a46-1 ... # mkdir wheezy # cd wheezy # cp -R /usr/share/live/build/examples/auto . # lb config # mv ~/kernel.binary config/hooks # lb build kernel.binary is simply: #!/bin/sh mv binary/live/vmlinuz-* binary/live/vmlinuz || true mv binary/live/initrd.img-* binary/live/initrd.img || true When it finally produced an ISO, I got the same "startpar" error as I always had. I tried another build with: * live-boot_3.0~a27-1_all.deb * live-boot-initramfs-tools_3.0~a27-1_all.deb * live-config_3.0~a37-1_all.deb * live-config-sysvinit_3.0~a37-1_all.deb in packages.chroot. And... it worked! I have no idea which one(s) of those updated packages made the difference, but at this point I don't care. I can now go ahead and make a wheezy version of my distribution. Woohoo! Let the bells ring out and the banners fly! :) Hopefully this will be it. I'll come back in a while to update all concerned with the results. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f905696.5030...@syrinx.net
Re: Simple default ISO generation fails
On 19/04/12 02:16 PM, Daniel Ellison wrote: Hopefully this will be it. I'll come back in a while to update all concerned with the results. A big thanks to Daniel Baumann and Ben Armstrong for persevering with what must have been a very annoying thread. Also, thanks to Tim Gibbon who suggested that I try the updated packages. And of course, thanks to everyone else who suggested things to try in this thread. I feel like I've won an Academy Award! :) "I'd like to thank my parents..." -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f905a5a.30...@syrinx.net
Re: Simple default ISO generation fails
On 19/04/12 02:16 PM, Daniel Ellison wrote: And... it worked! I have no idea which one(s) of those updated packages made the difference, but at this point I don't care. I can now go ahead and make a wheezy version of my distribution. Woohoo! Let the bells ring out and the banners fly! :) Hopefully this will be it. I'll come back in a while to update all concerned with the results. I just finished successful wheezy builds of both amd64 and i386 versions of SyrinxOS (http://journal.syrinxos.com/). I'll be releasing new ISOs sometime in the next few days - once I figure out what has changed to cause nautilus/brasero, etc. to be pulled in automatically. There's always something! :) Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f955f59.6080...@syrinx.net
synaptic-pkexec fails in live wheezy environment
Does anyone have an idea why synaptic-pkexec would fail when run in a debian wheezy live environment, but if I install the system to HD from the same ISO synaptic-pkexec works fine? When run from a terminal in a live environment: $ synaptic-pkexec Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key (synaptic:2429): Gtk-WARNING **: cannot open display: 0:0 Same result with "sudo synaptic-pkexec". But if I install from the ISO with which I ran the live environment, synaptic-pkexec works fine. Wheezy ISO built with: live-build 3.0~a46-1 Synaptic version in ISO: 0.75.9 /usr/share/polkit-1/actions/com.ubuntu.pkexec.synaptic.policy exists in both the live and installed environments. Running synaptic-pkexec from the command line in an installed environment prompts for a password then starts synaptic. Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f96b4ec.7010...@syrinx.net
A Debian Wheezy-based release of SyrinxOS, my Linux distribution created with live build
Hi all, I've finally released a Wheezy version of SyrinxOS, my Debian-based Linux distribution built with the live build tools. You can read all about it here: http://journal.syrinxos.com/post/21722417863/syrinxos-debussy-2012-04-24-wheezy-released Thanks, as always, to Daniel Baumann and Ben Armstrong for their help on this mailing list. Also, a nod to Tim Gibbon for getting me on the right track to circumvent a bug I was experiencing. Regards, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f96ec59.1030...@syrinx.net
Re: A Debian Wheezy-based release of SyrinxOS, my Linux distribution created with live build
Just a quick update: I've just pushed out another release of SyrinxOS Wheezy. There have been a few changes, mostly to touch things up so I can get on with updating the Squeeze version. You can read about it here: http://journal.syrinxos.com/post/21910332543/syrinxos-debussy-2012-04-27-wheezy-released I would really appreciate some feedback, negative OR positive. I want to make this a rock-solid distribution targeting experienced Debian users. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9ab9ba.7020...@syrinx.net
Re: A Debian Wheezy-based release of SyrinxOS, my Linux distribution created with live build
On 27/04/12 11:23 AM, Daniel Baumann wrote: did you consider registering as a debian derivative? I would like to do that! How would I go about it? I'm guessing I would add a new derivative for SyrinxOS here: -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9ac06e.1090...@syrinx.net
Re: A Debian Wheezy-based release of SyrinxOS, my Linux distribution created with live build
On 27/04/12 11:51 AM, Daniel Ellison wrote: On 27/04/12 11:23 AM, Daniel Baumann wrote: did you consider registering as a debian derivative? I would like to do that! How would I go about it? I'm guessing I would add a new derivative for SyrinxOS here: Damn. That's the second time today I've accidentally sent a message before it was finished. Here: http://wiki.debian.org/Derivatives/Census I'll read about it and submit my distro as a derivative. Thanks, Daniel! -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9ac0e2.4080...@syrinx.net
Re: Bug console setup udeb?
On 02/01/13 10:23 AM, _ wrote:
After update debian installer git.
make build_cdrom_isolinux
generate all initrd
after boot:
debian installer freeze after selected language.
some try it?
I have a similar issue (as far as I can tell). live-build 3.0~b4-1,
building a wheezy binary-hybrid ISO, including the debian installer with
these lines in my auto/config:
--debian-installer live \
--debian-installer-gui true \
--debian-installer-distribution daily \
It worked earlier today, but now it freezes with a blank screen titled
"configure the keyboard" right after choosing a keymap ("American
English") from the "Keymap to use" screen.
--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50e45d4f.4070...@syrinx.net
