| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Since we are no longer stopping / re-starting mdraid container arrays, we
no longer need the workaround for the mdadm --stop on containers bug
in the MDRaidArrayDevice teardown method.
|
|
|
|
|
|
|
| |
Since BIOS RAID sets (containers in mdraid terminology) never change
there is no need to stop them and later restart them. Not stopping
(and thus also not starting) them also works around bug 523334, which
is the cause of bug 532971.
|
|
|
|
|
|
|
|
|
| |
Things being in the history means I don't have to type them. This
particular thing is fairly specific to get right, so it's a really good
candidate to go in there. So this patch adds it.
This also changes the "killall" that's already there to use the pid
file, so we know which process it'll pick.
|
|
|
|
|
|
| |
This changes SIGUSR2 to start a debugger that you can telnet to on port
8080. At the moment you need to do "C-] mode char\n" in your telnet
client to get it into character mode instead of line mode.
|
|
|
|
|
|
| |
Right now when you ssh in, you get errors in the log because sshd wants
to interact with /var/log/lastlog. These errors will just confuse
people, so create /var/log/lastlog when we start sshd.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The edc665e6fa2ba71e89eb83412738622e916c3a05 commit prevented SIGSEGV
but changed behavior of modopts to where we'd never get any values in
modopts.
What needed to happen is the else clause in addOption() needed to
initalize the .options array and add in the option value. That wasn't
happening, so strcat() calls in writeModulesConf() were causing SIGSEGV.
This patch also adds some realloc() and malloc() checks. Tested with
"radeon.nomodeset=1" and without that parameter on x86_64.
|
|
|
|
|
| |
We've got a lot of dead code here. This removes a bunch of it. Also,
it fixes gettimespecofday's math to yield the correct result.
|
|
|
|
|
|
| |
Since we don't want init to exit when we call udevadm, fork first. But
before we do that, may as well wait for our forked udevd to exit, so
there's some chance it's listening for connections.
|
|
|
|
|
|
|
|
|
|
|
| |
Currently if init exits unexpectedly, we get "Kernel panic - not
syncing: Attempted to kill init!" and then a useless kernel traceback
(hey, it went through do_exit()!, who'd'a thunk?) but nothing meaningful
about what went wrong in init. This patch attempts to rectify this
situation by adding the traceback handler from loader to init, as well as
triggering it (in both loader and init) if we exit without going through a
path we've specifically marked, by using doExit() instead of exit(3) or
_exit(2), as not needing a traceback.
|
|
|
|
|
|
| |
This fixes the vim magic to be something it'll actually do something
with. I probably got it wrong the first time, but hey, better usable
than not.
|
|
|
|
| |
This lets you set passwords to ssh into the anaconda environment.
|
|
|
|
|
|
|
|
| |
This makes a couple of changes:
- fixes bogus access test on libuser.conf in createLuserConf()
- adds appropriate logging to createLuserConf()
- createLuserConf returns the path it created.
- Users.* no longer chroot+del LIBUSER_CONF if the new root is /
|
|
|
|
| |
Log stdout/stderr of each ssh-keygen invocation to its own log file.
|
|
|
|
|
| |
The tabs in this file are driving me crazy, so fix them and add the
vim hint for formatting.
|
|
|
|
|
|
| |
If we don't have killall5, a symlink to it won't be very valuable, so
it's probably not such a bad idea to include the target of the simlink
that is pidof as well as the symlink itself.
|
|
|
|
|
|
| |
Under certain conditions, modopts is never initialized. This patch
fixes up that while preserving the existing functionality introduced
with 29e18c35.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This modifies the default partitioning as follows:
(1) For VGs <= 50 GB, we will continue to make swap and / as normal.
(2) For VGs >= 50 GB, / will cap at 50 GB and /home will consume the rest.
50 GB is fairly arbitrary, and was based on the fact that an Everything
install of Fedora right now is ~ 40 GB, plus some room for expansion. Very
few users are likely to do an Everything install so this should provide plenty
of space for upgrades and future growth. Additionally, this is only a default
partitioning suggestion and can always be overridden by the user.
|
|
|
|
|
| |
This allows us to disregard certain requests when there's not enough
space in the VG for the request to make any sense.
|
| |
|
|
|
|
| |
This prevents LVs from being named things like "lv__home".
|
|
|
|
|
|
| |
When we dump the anaconda object in python-meh, the object won't be named
"anaconda". It'll be named "obj". python-meh will stick that on the front
of every attribute, so we need to remove "anaconda".
|
| |
|
|
|
|
|
| |
Function names should be truthful, I think. It just makes everything
easier.
|
|
|
|
|
|
| |
Having things in .bash_history saves my fingers from pain later in life,
which is a noble goal. This also puts pidof and killall in the image,
because they're nice things, and we can have nice things.
|
|
|
|
|
| |
If we try to regexec() on NULL it segfaults, so let's try not to do
that...
|
|
|
|
|
|
| |
Makes sure that NFS options can be used in both parameters. Previously
this was only parsed for ks= and not for stage2= using two separate
code paths. Move this to a shared function in loader/nfsinstall.c.
|
|
|
|
|
|
| |
Part of the changes necessary for #475675, we need to take the
cio_ignore parameter (if it exists) given during installation and write
it to the parameter list in /etc/zipl.conf on the target system.
|
|
|
|
|
|
|
|
|
|
| |
Adding the user-specified hostname to the 127.0.0.1 line is breaking
virt systems, among other things. I'm not entirely sure we need this
functionality anymore (faking the hostname as 127.0.0.1).
This reverts the changes done in
1aa67d5a2cdacd45f92ba15aa9392ba7191a49c7, but looking at the comments
for #506384, you'll see the same complaints as #530343 has are present.
|
|
|
|
|
| |
stdout echo is on by default, add a parameter that lets us turn that off
if we want to.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
These are updated by msgfmt, but leave the po files in the repository as
is since they are updated by an external project. We'll keep the pot
file up to date, but that happens at 'make bumpver'. Since msgfmt
generates new po files for the release tarball, we need to reset all of
these files after a 'make release' or 'make archive'.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following install test case has been failing:
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_%28shrink%29_install
The problem was with the minSize property in Ext2FS. We use resize2fs
to get the minSize for ext2/3/4 filesystems, which is good because
resize2fs accounts for additional things an extX volume may need. The
problem is the value it reports is in blocks. We have to convert those
blocks to bytes, then to megabytes, then round up to account for any
fractional megabytes. Use dumpe2fs to get the block size and use
resize2fs as we have been, but modify the calculation of size.
Also the _setTargetSize() method in FS needed a change. minSize can be
less than or equal to newsize, not just less than.
|
|
|
|
|
| |
If the user selects Exit Installer, log a message indicating as much and
then exit.
|
|
|
|
|
|
| |
Rather than use ListboxChoiceWindow(), do what ButtonChoiceWindow() does
in snack, but add an additional row with a scrolling list box for
longText.
|
|
|
|
|
|
|
|
|
| |
If performing a kickstart install on s390, dasdfmt is only run if:
a) There is a UI available to prompt the user.
b) 'zerombr' is specified in the kickstart file.
The zerombr command will also skip the UI if there is one. The UI
prompt is a fallback.
|
|
|
|
|
|
|
|
| |
zerombr is used during storage.DASD.startup() if the user is performing
a non-interactive kickstart install. Since the full kickstart file is
not processed until after the storage object has initialized, we need to
include this flag in the early kickstart processing because it's used
during the storage object initialization.
|
| |
|
| |
|
|
|
|
|
|
| |
platform.X86.__init__ did: self.diskLabelType = foo instead of
self._diskLabelType = foo. So it was overriding the method from the
base class.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Up to F11 /dev/mdX in /etc/sysconfig/grub means that grub was installed into
mbrs of all /boot md device members' disks. When upgrading grub of such a
system, reinstall grub in the mbrs, and update values sysconfig file
accordingly (to hold e.g. /dev/sda). Here I'm not completly sure. What if after
installation the user reinstalled grub manually - restored mbrs and installed
it in /dev/mdX? He wouldn't be happy with our grub update then...
This is one of follow-up commits for commit
358a9a34f496fdd2b032edf12274a146b606d1a4, dealing with upgrade.
|
|
|
|
|
| |
This is one of follow-up commits for commit
358a9a34f496fdd2b032edf12274a146b606d1a4, dealing with upgrade.
|
|
|
|
|
| |
This is one of follow-up commits for commit
358a9a34f496fdd2b032edf12274a146b606d1a4, dealing with upgrade.
|