Re: Install Fedora by hand ... feeling brave :-)
Dne 7.6.2015 v 16:12 David Timms napsal(a): Hi, I'm keen to install F22 on a laptop (shared with windows 7), but the installer bugs out due to problems in libparted when reading my disk (bz: 1223111): https://bugzilla.redhat.com/show_bug.cgi?id=1223111 The machine boots and runs the live iso via usb, but also can't do install to the HD due to the above. So, what would it take to set up Fedora by hand ? My first go is: boot live iso to runlevel 2 login: root mount /dev/sda6 /mnt mount /dev/sda5 /mnt/boot mount /dev/sda7 /mnt/home mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/proc mount -t tmpfs tmpfs /mnt/tmp ??? dnf --installroot=/mnt install filesystem kernel firefox grub2 grubby (workstation stuff) chroot /mnt passwd dnf reinstall kernel (to make initrd creation work.) useradd myuser passwd myuser usermod -G wheel ?? grub2-install /dev/sda grub2-mkconfig -o /boot/grub2/grub.cfg What other things will I need to do / what does Anaconda do ? My first effort looks like it may be hanging/dying on selinux parts; I was able to /etc/selinux/config to turn is to DISABLED and add selinux=0 to kernel command line. Since all my files are installed without SE context, boot fails with SE enforcing. If SE disabled then restorecon etc don't work. What's the steps, to bootstrap selinux ? I imagine someone has done / documented this before, but google search not fruitful. I was installing my laptop the same way you're describing. It worked fine for for me until Fedora 18. Unfortunately something changed and I installed Fedora 19 using Anaconda again (had no time to debug). I think the only missing steps are to create /etc/fstab and make selinux work by running `touch /.autorelabel` - daniel -- Daniel Mach Release Engineering, Red Hat -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Sun, 2015-06-07 at 07:41 -0400, Neal Gompa wrote: > Uhh, this might be a stupid question, but what actually prevents us > from integrating the FedUp process into install media (that is, not > live images)? I mean, yeah, it's nice that we can do upgrades online, > but what about when the system we need to upgrade doesn't necessarily > have online access? I'd like to be able to trigger the upgrade > environment from install media (like with a Fedora Server ISO). Nothing, really - it's *better* if you have access to the updates repos during the upgrade, but it's technically feasible to do the upgrade from local media/repos. To make that work, you'd need: a) a way to easily enable the media as a repo, and then b) run DNF in offline mode (so it's OK with the unreachable network repos), and then c) ensure that the media will be mounted in the same place after reboot (e.g. by adding it to /etc/fstab) so the upgrade can proceed. (this workflow might even work with the current dnf-plugin-fedup, but I haven't tried it...) So, yeah, the last one is the trickiest part. It's very hard to be certain about whether a given filesystem path will be there when you reboot. So we either need to just leave that up to the user, or write mount units for *everything* on the system and hope that systemd figures it out after we reboot. (It's on my TODO list, since the fedup supported this with --device, but.. I just don't have spare time right now.) -w -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
On Sun, Jun 7, 2015 at 1:41 PM, Neal Gompa wrote: > Uhh, this might be a stupid question, but what actually prevents us > from integrating the FedUp process into install media (that is, not > live images)? I mean, yeah, it's nice that we can do upgrades online, > but what about when the system we need to upgrade doesn't necessarily > have online access? I'd like to be able to trigger the upgrade > environment from install media (like with a Fedora Server ISO). > > Likewise, being able to upgrade from a netinstall ISO by triggering > the environment would be cool too. I don't know how practical it would > be, but it'd be nice if it could be done... > > On Wed, Jun 3, 2015 at 7:14 AM, Richard Hughes wrote: >> On 3 June 2015 at 11:55, Petr Hracek wrote: >>> Does it mean that using systemd Offline Updates there will not be a "Zero" >>> downtime feature. >>> Except rebooting because of kernel upgrade? >> >> Well, we'll certainly be using offline updates to do the actual transaction. >> >>> Will there be any possibility to inform user if API or ABI issues are >>> discovered after an upgrade? >> >> We won't be able to do the update if there are package conflicts. >> We're aiming to show the apps that are problems and offer to remove >> them, but we can't work magic. >> >>> E.g Database was changed and needs to be fixed after the upgrade? >> >> This needs to be done in the rpm post scripts. >> >>> QT and GUI for upgrade would be awesome? >>> Do you have any draft already? >> >> There are several mockups for GNOME Software already; these need more >> work but are almost there. I'm almost certain we'll be using >> gnome-software at least for the workstation spin although they'll of >> course be a command line tool to schedule to upgrade. I've been asked >> to spend some time to integrate bits of Wills work into PackageKit, >> which I'll start to do in a couple of weeks time. That can't really work because some time after release packages might be never than the ones on the install media and you might have packages installed that are not on the install media which could also cause issues (depsolv errors etc.) during the upgrade process. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Install Fedora by hand ... feeling brave :-)
Hi, I'm keen to install F22 on a laptop (shared with windows 7), but the installer bugs out due to problems in libparted when reading my disk (bz: 1223111): https://bugzilla.redhat.com/show_bug.cgi?id=1223111 The machine boots and runs the live iso via usb, but also can't do install to the HD due to the above. So, what would it take to set up Fedora by hand ? My first go is: boot live iso to runlevel 2 login: root mount /dev/sda6 /mnt mount /dev/sda5 /mnt/boot mount /dev/sda7 /mnt/home mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/proc mount -t tmpfs tmpfs /mnt/tmp ??? dnf --installroot=/mnt install filesystem kernel firefox grub2 grubby (workstation stuff) chroot /mnt passwd dnf reinstall kernel (to make initrd creation work.) useradd myuser passwd myuser usermod -G wheel ?? grub2-install /dev/sda grub2-mkconfig -o /boot/grub2/grub.cfg What other things will I need to do / what does Anaconda do ? My first effort looks like it may be hanging/dying on selinux parts; I was able to /etc/selinux/config to turn is to DISABLED and add selinux=0 to kernel command line. Since all my files are installed without SE context, boot fails with SE enforcing. If SE disabled then restorecon etc don't work. What's the steps, to bootstrap selinux ? I imagine someone has done / documented this before, but google search not fruitful. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: fedup for F23 and beyond
Uhh, this might be a stupid question, but what actually prevents us from integrating the FedUp process into install media (that is, not live images)? I mean, yeah, it's nice that we can do upgrades online, but what about when the system we need to upgrade doesn't necessarily have online access? I'd like to be able to trigger the upgrade environment from install media (like with a Fedora Server ISO). Likewise, being able to upgrade from a netinstall ISO by triggering the environment would be cool too. I don't know how practical it would be, but it'd be nice if it could be done... On Wed, Jun 3, 2015 at 7:14 AM, Richard Hughes wrote: > On 3 June 2015 at 11:55, Petr Hracek wrote: >> Does it mean that using systemd Offline Updates there will not be a "Zero" >> downtime feature. >> Except rebooting because of kernel upgrade? > > Well, we'll certainly be using offline updates to do the actual transaction. > >> Will there be any possibility to inform user if API or ABI issues are >> discovered after an upgrade? > > We won't be able to do the update if there are package conflicts. > We're aiming to show the apps that are problems and offer to remove > them, but we can't work magic. > >> E.g Database was changed and needs to be fixed after the upgrade? > > This needs to be done in the rpm post scripts. > >> QT and GUI for upgrade would be awesome? >> Do you have any draft already? > > There are several mockups for GNOME Software already; these need more > work but are almost there. I'm almost certain we'll be using > gnome-software at least for the workstation spin although they'll of > course be a command line tool to schedule to upgrade. I've been asked > to spend some time to integrate bits of Wills work into PackageKit, > which I'll start to do in a couple of weeks time. > > Richard > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- 真実はいつも一つ！/ Always, there's only one truth! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Reviving Fedora MIPS
On Fri, Jun 5, 2015 at 8:12 PM, Stephen Gallagher wrote: > Just to be clear; your GSoC proposal was refused because 1) you didn't > have a mentor and 2) the scope of your project was too large. > > This should not be construed as Fedora not showing interest. > Bootstrapping a new (or restarted) architecture is a major effort that > no one person can or should attempt without help. > > So if you want to work with Michal Toman on this, great! I know this, thanks for your information. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
rawhide report: 20150607 changes
Compose started at Sun Jun 7 05:15:04 UTC 2015
Broken deps for i386
--
[ambari]
ambari-server-1.5.1-3.fc22.noarch requires
mvn(com.sun.jersey:jersey-server)
ambari-server-1.5.1-3.fc22.noarch requires
mvn(com.sun.jersey:jersey-json)
ambari-server-1.5.1-3.fc22.noarch requires
mvn(com.sun.jersey:jersey-client)
ambari-server-1.5.1-3.fc22.noarch requires
mvn(com.sun.jersey.contribs:jersey-multipart)
ambari-server-1.5.1-3.fc22.noarch requires
mvn(com.sun.jersey.contribs:jersey-guice)
ambari-views-1.5.1-3.fc22.noarch requires
mvn(com.sun.jersey:jersey-core)
[apache-scout]
apache-scout-1.2.6-11.fc21.noarch requires mvn(org.apache.juddi:uddi-ws)
apache-scout-1.2.6-11.fc21.noarch requires
mvn(org.apache.juddi:juddi-client)
[boo]
boo-0.9.4.9-11.fc22.i686 requires mono(mscorlib) = 0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(System.Xml) = 0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(System.Core) = 0:3.5.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(System) = 0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Utilities) =
0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Tasks) =
0:2.0.0.0
boo-0.9.4.9-11.fc22.i686 requires mono(Microsoft.Build.Framework) =
0:2.0.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(mscorlib) = 0:2.0.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(System.Xml) = 0:2.0.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(System.Core) = 0:3.5.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(System) = 0:2.0.0.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(NAnt.DotNetTasks) =
0:0.90.3780.0
boo-devel-0.9.4.9-11.fc22.i686 requires mono(NAnt.Core) = 0:0.90.3780.0
[dmlite-plugins-memcache]
dmlite-plugins-memcache-0.5.0-7.fc20.i686 requires libprotobuf.so.8
[gambas3]
gambas3-gb-pdf-3.7.1-1.fc23.i686 requires libpoppler.so.49
[gdal]
gdal-1.11.2-6.fc23.i686 requires libpoppler.so.49
gdal-java-1.11.2-6.fc23.i686 requires libpoppler.so.49
gdal-libs-1.11.2-6.fc23.i686 requires libpoppler.so.49
gdal-perl-1.11.2-6.fc23.i686 requires libpoppler.so.49
[hadoop]
hadoop-common-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-servlet)
hadoop-common-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-server)
hadoop-common-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-json)
hadoop-common-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-core)
hadoop-hdfs-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-server)
hadoop-hdfs-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hadoop-mapreduce-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-server)
hadoop-mapreduce-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey.contribs:jersey-guice)
hadoop-tests-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-servlet)
hadoop-tests-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-server)
hadoop-tests-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-json)
hadoop-tests-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-core)
hadoop-tests-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-client)
hadoop-tests-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey.contribs:jersey-guice)
hadoop-yarn-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-server)
hadoop-yarn-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
hadoop-yarn-2.4.1-8.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hadoop-yarn-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey:jersey-client)
hadoop-yarn-2.4.1-8.fc22.noarch requires
mvn(com.sun.jersey.contribs:jersey-guice)
[hbase]
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-server)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-json)
hbase-0.98.3-4.fc22.noarch requires mvn(com.sun.jersey:jersey-core)
hbase-tests-0.98.3-4.fc22.noarch requires
mvn(com.sun.jersey:jersey-server)
hbase-tests-0.98.3-4.fc22.noarch requires
mvn(com.sun.jersey:jersey-json)
hbase-tests-0.98.3-4.fc22.noarch requires
mvn(com.sun.jersey:jersey-core)
[julia]
julia-0.3.7-2.fc23.i686 requires libLLVM-3.5.so
julia-devel-0.3.7-2.fc23.i686 requires libLLVM-3.5.so
[libreoffice]
1:libreoffice-pdfimport-5.0.0.0-3.beta1.fc23.i686 requires
libpoppler.so.49
[matreshka]
matreshka-servlet-devel-0.7.0-1.fc23.i686 requires
matreshka-servlet-lib{?_isa} = 0:0.7.0-1.fc23
matreshka-servlet-lib-0.7.0-1.fc23.i686 requires matreshka{?_isa} =
0:0.7.0-1.fc23
matreshka-spikedog-api-devel-0.7.0-1.fc23.i686 requires
matreshka-spikedog-api-lib{?_isa} = 0:0.7.0-1.fc23
matreshka-spiked
