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_s
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
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
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
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.
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
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/
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 ker
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 de
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
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
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.syr
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
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&#x
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 resul
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 insta
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'
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 do
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
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 fo
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://ft
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
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 h
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
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, rathe
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
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.)?
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, thes
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 approp
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 ou
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 D
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
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
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
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 t
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
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 goi
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 stuf
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
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.squ
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 i
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?
>
&g
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
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 le
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-re
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.
Éc
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
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
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
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.
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 wit
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
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 imag
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,
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,
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
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 b
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~a2
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
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
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-
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
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 t
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.debia
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/s
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:
Moun
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 UNSUBSCRIB
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
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 matt
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
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
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
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
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
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
al
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&q
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 te
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-boo
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
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: liv
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 inste
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 pi
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
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
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 banner
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-MAGI
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 Be
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-
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
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
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
91 matches
Mail list logo
