Displaying 20 results from an estimated 10000 matches similar to: "Bootloader data in /boot vs package systems (and atomic updates)"
2014 Apr 23
0
Bootloader data in /boot vs package systems (and atomic updates)
On Tue, Apr 22, 2014 at 6:58 PM, Colin Walters <walters at verbum.org> wrote:
> Hi,
>
> I'm working on https://wiki.gnome.org/Projects/OSTree which is a
> general-purpose update system for Linux-based operating systems. It isn't a
> package system itself, but operates at the same level.
>
> A primary goal of OSTree is fully atomic updates, and the "swapped
2014 Apr 24
0
Bootloader data in /boot vs package systems (and atomic updates)
Colin Walters <walters at verbum.org> writes:
> I'm working on https://wiki.gnome.org/Projects/OSTree which is a
> general-purpose update system for Linux-based operating systems. It
> isn't a package system itself, but operates at the same level.
>
> A primary goal of OSTree is fully atomic updates, and the "swapped
> chroots" model works well for most
2014 Apr 24
2
Bootloader data in /boot vs package systems (and atomic updates)
On Apr 24, 2014 3:19 AM, "Ferenc Wagner" <wferi at niif.hu> wrote:
>
> Colin Walters <walters at verbum.org> writes:
> > However, syslinux relies on loadable modules in /boot. At present in
> > Fedora at least, the RPM package updates these, and it has a %post to
> > ensure that when a newer version of extlinux is installed, we update
> > both
2014 Apr 23
2
Bootloader data in /boot vs package systems (and atomic updates)
On Tue, Apr 22, 2014 at 8:16 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
>
> I think you mean the VBR since no Syslinux variant lives in the MBR
> and on Linux,
Right, thanks.
> Does the installation of an updated package of GRUB2 trigger an
> installation of modules during install on Fedora
It used to, but no longer does. There's some background here:
2014 Apr 23
1
Bootloader data in /boot vs package systems (and atomic updates)
On Wed, Apr 23, 2014 at 4:49 PM, Ady <ady-sf at hotmail.com> wrote:
>
> FWIW and just as one example, ArchLinux has its own script
Looks like the canonical source is here:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/syslinux-install_update?h=packages/syslinux
Right. Hmm. The painful thing will be transitioning the existing
package, as it would obviously break
2017 Mar 20
2
I/O error
Hi,
I'm trying to make Syslinux, OSTree and Qemu work together. So I've made
an image, installed Syslinux v. 6.0.3 on it with extlinux and try to
boot it. Unfortunately it stops on the stage of loading the kernel with
Loading
/boot/ostree/agl-17980142f6d5ef5e82153aa533ffb9775181f93248e62a4821f925cdf1b81c34/vmlinuz...
failed: I/O error
The vmlinuz file is just a normal bzImage (v.
2014 Apr 24
0
Bootloader data in /boot vs package systems (and atomic updates)
Gene Cumm <gene.cumm at gmail.com> writes:
> On Apr 24, 2014 3:19 AM, "Ferenc Wagner" <wferi at niif.hu> wrote:
>>
>> Colin Walters <walters at verbum.org> writes:
>>
>>> However, syslinux relies on loadable modules in /boot. At present in
>>> Fedora at least, the RPM package updates these, and it has a %post to
>>>
2017 Mar 21
2
I/O error
Thanks Ady,
tried current master and shortened path to /boot/vmlinuz. Same stuff.
OSTree doesn't really come into play at this stage, it is just booting
the kernel. So I would rather suspect that there is something between
ext4, extlinux and qemu.
On 03/21/2017 04:01 AM, Ady Ady via Syslinux wrote:
>> Hi,
>>
>> I'm trying to make Syslinux, OSTree and Qemu work
2009 Nov 06
3
Initial bootloader requirements of extlinux
I'm trying to understand what the extlinux bootloader code written into a
partition needs to successfully start. I have a disk with four partitions, the
second is marked active and contains a kernel, initrd and root FS and extlinux
has been run on it. If I use mbr.bin as the initial bootloader the system
boots fine.
I need this to work within an environment supplied by a third party. They
2009 Aug 08
2
Chainloading from Vista x64 bootloader to Extlinux?
Hi syslinux list,
Some months ago, hpa was kind enough to help me troubleshoot booting
Extlinux in a system with the following particulars:
* Windows Vista x64 bootloader in the MBR and Vista installed in /dev/sda1
* Extlinux 3.72 installed in the first sector of /dev/sda2 and Foresight
Linux installed in /dev/sda2 (at the time I tried, 3.72 was the default
bootloader in Foresight)
The problem
2016 Jun 07
1
request for access to https://wiki.centos.org/SpecialInterestGroup/Atomic/Download/
Hi,
I'd like to start documenting the "CentOS Atomic Host Continuous" stream (https://ci.centos.org/job/atomic-rdgo-centos7/)
I plan to create a new /SpecialInterestGroup/Atomic/Devel page.
May I please have access to do that?
My wiki username is ColinWalters. Thanks!
2017 Aug 04
2
bootloader installation improvements
I have some concerns about the Syslinux boot process, which I'm now
investigating in connection with my work on booting Live-CD images from
USB flashdrives. Some of these are related to what seems to be
inadequate documentation, but I think that there are also aspects of
Syslinux operation which could be fairly easily improved.
quoting from the official documentation:
Since version 5.00,
2008 Mar 21
12
[Bug 1450] New: Support for ConsoleKit on Linux through dbus calls
https://bugzilla.mindrot.org/show_bug.cgi?id=1450
Summary: Support for ConsoleKit on Linux through dbus calls
Classification: Unclassified
Product: Portable OpenSSH
Version: 4.7p1
Platform: Other
2014 May 27
2
Re: [PATCH 2/2] Use setfiles from the appliance for the SELinux relabel (RHBZ#1089100).
On Tuesday 27 May 2014 14:25:08 Richard W.M. Jones wrote:
> So I think an API which looks like this ...
>
> required params:
>
> None
>
> optional params:
>
> path =>
> Either a directory to be relabelled recursively, or a single
> file (defaults to "/").
>
> root =>
> Inspection root of guest. Optional, only
2014 May 27
3
Re: [PATCH 2/2] Use setfiles from the appliance for the SELinux relabel (RHBZ#1089100).
On Tuesday 27 May 2014 09:08:27 Richard W.M. Jones wrote:
> On Mon, May 26, 2014 at 11:21:59AM +0200, Pino Toscano wrote:
> > Rewrite the relabel API to read the policy configured in the guest,
> > invoking setfiles (added as part of the appliance, as part of
> > policycoreutils) to relabel the specified root. In case of failure
> > at
> > any point of the process,
2014 Jan 13
3
installing syslinux on a fresh system (SATA)
Hi
I understand you (mostly).
0) How do i "install the MBR code as well and to activate your partition."
1) "mount /dev/sda1 /mnt" -->> successfully completed.
2) "mkdir /mnt/extlinux" -->> successfully completed.
3) "extlinux --install /mnt/extlinux" -->> does not work.
Funny, but it it seems that there is no such thing as
2014 Apr 23
0
Bootloader data in /boot vs package systems (and atomic updates)
>
> > The alternative is an additional script that would run the installer
> > binary extlinux and copy *.c32 at the same time.
>
FWIW and just as one example, ArchLinux has its own script,
"syslinux-install_update -i -a -m".
-i : install SYSLINUX;
-a : mark partition as "active";
-m : install mbr boot code.
I have not checked whether currently the
2008 Feb 26
2
3.62-pre16: Compiling on old (2.4 kernel) distros
I have put a compile hack in for older distros and pushed it out as
syslinux-3.62-pre16; for those who have reported compilation problem on
older distros I would greatly appreciate if you could confirm if it
works now (it worked for me on a CentOS 3.9 VM.)
-hpa
2014 Jan 12
4
installing syslinux on a fresh system (SATA)
Hi!
It's funny, but I was unable to find an answer to my question.
I am building an embedded system (x86).
I want to install syslinux on a fresh system.
So, I am booting from a USB LINUX CD (Ubuntu 12.04 in this case).
1) I must have an ext2 partition (This is my application).
2) I understand that I must have a FAT partition (to install
syslinux). Correct ?
So, basically I understand that
2008 Jun 27
6
Last call for Syslinux 3.70
Hi all,
I have just released syslinux-3.70-pre25. Unless someone has something
big and scary that either I have managed to miss or was just stumbled
over, I'm going to release 3.70 final some time between tomorrow and Monday.
Thus, *please holler now* if there are any stop-ship problems still known...
-hpa