a naming scheme that doesn't suck.
Please consider it desirable to implement a scheme with file names
that, in lexical order, list oldest version first (or last). Newest
version somewhere in the middle is a bad design.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
Might this be an effect caused by removal of an old graphics driver?
https://lists.fedoraproject.org/pipermail/devel/2014-May/199459.html
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
I normally eschew Upgrade installation, because the result can mix old
and new files in ways that too often lead to mysterious problems,
sometimes months later.
There be rocks in the upgrade waters!
Yesterday I inadvertently failed to check New install when using the
F15RC3 DVD, and thus
F15 RC3 installed without any obvious problems.
Failure during attempt to create a virtual machine.
[root@hp ryniker]# virt-install --prompt
What is the name of your virtual machine?
MPLAB
How much RAM should be allocated (in megabytes)?
4096
What would you like to use as the disk (file path)?
I don't understand why Fedora maintainers decide to replace functional
software by software that lacks many essential features ...
I have no direct connection to Fedora decision-makers, but I doubt this
is something they decide to do. It happens because Fedora seeks to
package very recent
Try a broadcast ping, and see who responds. One of the responses from an
address you do not recognize as something else may be your print server.
Example:
# ping -b -I eth0 192.168.100.255
WARNING: pinging broadcast address
PING 192.168.100.255 (192.168.100.255) from 192.168.100.32 eth0: 56(84)
It would be more accurate to say The current Fedora releases are not
typically used as servers. I expect many are like me and use an older
Fedora release on servers: F9 in my case, because it does its job well
and any limitations do not impair its function.
It seems perfectly reasonable to
On Thu, 04 Aug 2011 14:11:43 +0530, Rahul Sundaram wrote:
On 08/04/2011 06:11 AM, Adam Williamson wrote:
I thought it'd be a good idea to take a step back and plan a strategy
for post-Alpha TC1.
We're in trouble for Alpha; we're a long way behind schedule, and we
have a lot of blocker bugs
Rahul Sundaram metherid at gmail.com writes:
I don't think Fedora should be installing extensions by default.
I side with Rahul Sundaram. The default configuration should follow
upstream choices as much as possible.
If alternative choices are useful for a significant population of Fedora
Well, no version of Windows yet sets up a GPT disk label, and anaconda
is supposed to leave existing MSDOS disk labels around.
I configured Windows Vista Ultimate 64-bit to use several disks in a
software RAID arrangement a year or two past. A BIOS update to this HP
system subsequently killed
Adam Williamson awill...@redhat.com wrote on Tue, 11 Oct 2011 18:00:03 -0700:
i.e. if you decide to maintain your config by hand then you have to try
and stop your distro doing it for you, and that's outside of the
distro's scope of support.
I have more than 150 entries in /etc/alternatives that
On Sun, 2011-10-16 at 21:46 -0700, Rob Healey wrote:
So when working with python files, why is there no specific mime type for
it?
Basically, because there is no need to tell the recipient of a Python
file how to specially format or interpret it. It is simply one of a
large set of text files.
I have experienced effects like those you described when Pulseaudio (or
perhaps something else in the audio-processing chain) must do sample-rate
conversion, such as from 44.1 KHz to 48KHz, to drive my USB speakers.
Sox has been an effective solution for me. Try play (a link to sox that
denotes
On Sat, 2011-04-02 at 10:49 -0400, Genes MailLists wrote:
Indeed ... there is something simplistically elegant about:
3
vs
multi-user.target
Or, you could look upon it as 'utterly cryptic'. At least
multi-user.target takes a shot at explaining itself. 3...3, well, not so
much.
--
Al Dunsmuir al.dunsm...@sympatico.ca wrote on Tue, 12 Apr 2011 12:36:53 -0400:
I think these [file names such as multi-user.target] should be
viewed more as keywords, or reserved phrases
and not subject to translation.
This is similar to a C program, where one has 3 cases:
- Comments and
Partition table invalid or corrupt.
I saw this message from GRUB when I re-used a disk that had been part of
a software RAID array for a Fedora installation. I do not recall now
whether fdisk or the Fedora installer wrote a new partition table, but
there were vestiges of the RAID format left on
users can renumber user files by:
(1) chown --from OLD_OWNER:OLD_GROUP NEW_OWNER:NEW_GROUP /
I think a --recursive option may be needed in the chown command.
There are thorns in these bushes. It is not only user and group ids in
new systems that must change: this change will upset
This is bug 747449, presumably just a case of a missing dependency. I
bumped into it when I invoked system-config-users. Because multiple
applications fail, and therefore can inflict pain on many users, does it
make sense to add something to Common Bugs?
The work-around (install
The thread for longer files is more likely to be in the middle of a
transfer, and thus capable of boosting its throughput, while the other
thread suffers low throughput due to starting or stopping the transfer of
an individual file.
Maybe. Certainly The thread for longer files is more likely to
But no, right clicking on empty space doesn't do diddly squat in the
Gnome 3 Applications screen.
I do not think a click on nothing is persuasively intuative as a way to
create an application launcher.
Who wants diddly squats littering the screen, anyway?
For programs that can be found through
If I plug it in while I'm logged in, it shows up. I log out and log back in,
and it still shows up.
If I reboot, plug it in during GDM, and then log in... it shows up. Under
what circumstance does it not show up for you?
If your USB stick is plugged in before you boot your system, where does it
Unknown media type in type 'all/all'
Not a new phenomenon. I see this in my F17 system, but also in
F14... even in F8, so it has been around for a long time.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
to prevent the user doing something silly like trying to install GNOME
but forgetting the X server and fonts.
I think the Package Manager copes with this very well, especially when
the installation source is a release DVD. Unlike the network
repositories, which can become inconsistant as
The installer must be able to successfully complete an upgrade
installation from a clean, fully updated default installation (from any
official install medium) of the previous stable Fedora release via any
officially supported upgrade mechanism. The upgraded system must meet
all release criteria.
I think we could link to
https://fedoraproject.org/wiki/Upgrading to define
'supported/recommendation upgrade mechanism'
OK, but to illustrate the problem with indirect references: the
Upgrading page you cite above says to read
You have convinced me, Adam. How much does it contribute to release
quality if excellent test criteria are perfectly validated, but the
documentation the end-user reads says Fedora does something different?
To that user, what he sees is clearly a fault.
QA may not be explicitly requested to vet
Upgrade installation is a bizarre beast, because the result is not well
defined. Yes, a newer set of packages is installed, but a new install
does that. The reason upgrade is so seductive is the notion all one's
configuration and personalization is carried into the upgraded system,
whereas a new
On 09/26/2012 10:37 AM, Kamil Paral wrote:
I personally split maintainers in the distribution into three
categories.
1. Packager
2, Maintainer
3. Upstream maintainer
Is this an argument for an additional Fedora package class? At present,
it seems there are two well-defined types:
Frank Murphy frankl...@gmail.com wrote on Fri, 26 Oct 2012 08:33:25 +0100:
So you agree, it's unneccessary.
For me to need at-spi*. Point made.
I think the point was at-spi is part of GTK, but this part is not
something it is reasonable to package separately, such as a language
package or some
we should make this possible via a command line parameter rather than a UI
option; it's an 'advanced' option that's only of use to multiboot
pokemoners (you know...gotta catch 'em all) and is a 'dangerous' option
for anyone who doesn't understand it - if you pick it when you don't know
what you're
[Adobe]
I want to know why they should {want} to screw us out of the internet
I doubt very much Adobe wants to limit our access to the Internet. Adobe
wants to apply its development resources in the way that maximizes its
profit.
Adobe may feel 64-bit Flash for Linux would be profitable (in
Bill Davidsen david...@tmr.com wrote:
If they don't have time to look at everything, then maybe they should stop
shipping kernels they haven't looked at! Really, people who needed 2.6.34
could
pull it from updates-untested and the rest of us could have working systems.
Back in the FC3-4-5-6
In my case (F13, x86_64 on a Lenovo X200) the .34 kernel made suspend fail.
On laptops I think working suspend/resume should be blocker for release. It
worked before, hence it is a regression.
F13 was released with a .33 kernel, therefore the question of blocking
the F13 release for this reason
I don't think GUI apps should be logging seemingly alarming messages
like this to stdout if they aren't actually a problem. If the
possibility that the referenced shared library isn't there is expected
and normal, then attempts to load it should fail silently.
Well, that's arguable.
since the current justification for having stable releases at all
is 'to handle upgrade cases we can't handle with yum'
What about installation from media such as DVD for users who cannot
reasonably access more than a gigabyte of updates from the Net?
--
test mailing list
Is this working-as-designed? Other than these messages,
system-config-network worked as expected.
[r...@vista ryniker]# system-config-network
(system-config-network-gui:24283): Gnome-WARNING **: Accessibility:
Fedora-14-Live-multi.iso is too large (5.2 gigabytes) for a normal DVD
with capacity of 4.7 gigabytes or so. Aha! It must be intended for a USB
flash drive with capacity of 8GB or greater...
[r...@ryniker ryniker]# cmd/livecd-iso-to-disk --format --reset-mbr
--overlay-size-mb 1024
I used an early F14 version of livecd-iso-to-disk, which may explain some
different behavior. There is one significant difference in how the
script is invoked: in the F13 version, the device argument can (must?) be
the base device, such as the /dev/sdc you used where you likely have a
/dev/sdc1
Doesn't FAT32 have a 4 GB limit on file size?
That should not be a factor in this case. There are multiple live
system images, but each one is a separate file well under 4GB. It is the
total space for all the files that exceeds 4GB.
--
test mailing list
test@lists.fedoraproject.org
To
Click: Edit - Preferences - Applications
Find the line in the first column (Content Type) for RDF file and
select your desired program. I had to select Use other and navigate to
my preference, acroread; you should choose your preferred application.
--
test mailing list
Some modestly interesting lines in my F14 .xsession-errors file suggest I
might benefit from some lessons in GNOMEish...
Failed to play sound: File or data not found
** Message: applet now removed from the notification area
** (nm-applet:1923): WARNING **: get_all_cb: couldn't retrieve
Adam Williamson awill...@redhat.com wrote:
It fails in this particular way because you don't have NM even
installed
I don't? This was a straightforward installation from the F14
installation DVD, updated to the current date. I see:
[ryni...@mini ~]$ rpm -q --all | grep Network
Yes, nm-applet complains this way (.xsession-errors) that NM is not running.
I agree that, in addition, nm-applet should let the GNOME user know when NM
service (/etc/inet.d/NetworkManager) is not running, instead of just removing
nm-applet icon from the panel.
I think of these ways to do that:
Probably not. There are too many possibilities to make reasonable any
default except do what the user explicitly says is desired.
The usual problems are hot-swap devices (USB, ESATA, etc.) that may be
present during installation but not later, and swap spaces intended for
other operating systems
John Reiser jrei...@bitwagon.com wrote on Fri, 07 Dec 2012 07:30:50 -0800
NO! NO! NO! Do NOT format any partition, including swap partitions,
except when explicitly requested. I want to share _some_ swap partitions,
but running mkswap destroys the UUID and/or label which other /etc/fstab
depend
Mateusz Marzantowicz mmarzantow...@osdf.com.pl wrote on Tue, 11 Dec
2012 07:15:57 +0100
Maybe there should be two groups of packages: important (core or
whatever) that must be installed and other (not important) that might
fail to install?
I think it better to start over with a minimal install
F18 TC1 x86-64 install DVD displays some complaints (the following indented
lines
appeared on the console, but I copied them later from /var/log/boot.log):
[[1;32m OK [0m] Started Show Plymouth Boot Screen.
[[1;32m OK [0m] Reached target Basic System.
dracut-pre-pivot[457]: cp:
It has been reported...
https://bugzilla.redhat.com/show_bug.cgi?id=849476
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Swap is a bit odd.
I don't see it as being any more or less odd than any other mount point. It's
either manual partitioning or not.
Swap is indeed odd. An unusual swap partition on an F18 target
installation disk can scuttle anaconda...
https://bugzilla.redhat.com/show_bug.cgi?id=886243
--
How does having two PVs on the same spindle increase latency?
Longer seeks - from one PV to the other - instead of two writes into the
same PV.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
I do not see this behavior; F18 updated to current level (without
updates-testing).
The firefox icon remains in my Favorites bar through logout-login, and
through reboot. Default Gnome desktop.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
True, a usage scenario can often be devised to manifest the worst aspects
of any allocation scheme. There are many other factors that can have so
much influence that I suspect the number of partitions and volume groups
may have little to do with actual performance.
Disk device caching and
I think new builds is a bad idea, a response to a worst-case event that
hopefully never happens. If the quality assurance process that generated
multiple alpha, beta, and release candidate builds has failed, another
try to fix one more bug will have less complete testing: it is too likely
to add
Does SELinux affect the problem?
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
The defining characteristic of the Live images is that they run
without installation on a user's disks. Beyond that, they have the
capability to install a minimal Fedora system to a local disk. Once
the size limit for a live image is increased beyond the capacity of a
CD (or other common media),
On Sat, 14 Dec 2013, at 11:25:40 -0800 Adam Williamson awill...@redhat.com
wrote:
One thing they've floated as an idea is to have a separate 'installation
environment' you could boot into from the live images - so you could
either boot into 'try it out' live mode, or 'install it'
Kamil Paral kpa...@redhat.com wrote on Fri, 20 Dec 2013 05:00:24 -0500
The bandwidth problem should be solved by a simple program:
a. you run it on computer A (lacking bandwidth) - it gathers the list of
installed packages and exports a file
b. then you run it on computer B (good bandwidth) -
So strange as it may seem - it appears that it has to be shut for more than a
short time to fail.
Might it be a hibernation issue? After some period of time, perhaps your
machine wants to move from suspend to hibernate.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
And no manpage for blkid.
There is a man page for blkid. It is part of:
util-linux-2.24-2.fc20.x86_64
If the man page is missing, perhaps other missing pieces contribute to
the problem. For example, swapon is also in util-linux.
--
test mailing list
test@lists.fedoraproject.org
To
Thank you for years of work to improve Fedora. All Fedora users benefit
to some extent from your efforts.
as WG's slowy turn into tiny little empires fighting amongst themselves
for components directions and maintenance...
Fedora (and linux in general) is growing larger. As this happens,
Might it be possible to defer construction of the yum database until
Firstboot?
Just want to make it clear this is something to consider for F20. I
think it is too late to make this sort of change in F19.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
Yeah, you have some sort of problem (configuration issue?) with your MTA:
2013-06-22 14:52:17 1UqSv3-0001aS-Kb = ryni...@ryniker.ods.org U=ryniker
P=local S=863
2013-06-22 14:52:18 1UqSv3-0001aS-Kb ** c...@omen.com R=dnslookup
T=remote_smtp: SMTP error from remote mail server after RCPT
Sounds like an unfortunate situation that should be addressed by use of a
Live system, which can repair or salvage data from the afflicted file
systems. If repair is possible, job done. If not possible, solution is
to re-install the operating system.
Rather than invest serious effort to make
This is recorded in my system journal (booting the iso install image from a USB
flash drive):
Aug 26 16:11:38 localhost kernel: ACPI Warning: \_SB_.PCI0.P0P1.PEGP._DSM:
Argument #4 type mismatch - Found [Integer], ACPI requires [Package]
(20130517/nsarguments-95)
Aug 26 16:11:38 localhost
Makes sense... the kernel is tainted after an oops. I was distracted
by thoughts about software with dubious provenance.
The first kernel oops (that taints the kernel) is documented here:
https://bugzilla.redhat.com/show_bug.cgi?id=1001806
--
test mailing list
test@lists.fedoraproject.org
To
On my last installation (TC4) anaconda's blue progress bar stalled at
approximately 40% while thousands of packages were installed. I suspect
this is Working as Designed. There is a continuing display of package
names as they are installed, as well as counts of installed packages and
total
Still bizarre; works for you, not for me. Today:
[root@lenovo ryniker]# yum distro-sync full
Loaded plugins: langpacks, refresh-packagekit
No packages marked for distribution synchronization
[root@lenovo ryniker]# yum groupinstall KDE Plasma Workspaces
Loaded plugins: langpacks,
There is both a group and environment with:
nameKDE Plasma Workspaces/name
I presume you mean this is a repository problem. I tried yum clean all
and that did not help, even though I understand this will reload all
metadata (like group information) from the repository.
Or do you mean I may
I still find the (maybe my own peculiar) F20 situation confusing. For example:
[root@lenovo ryniker]# yum -v group install kde-desktop-environment
Not loading blacklist plugin, as it is disabled
Loading langpacks plugin
Loading refresh-packagekit plugin
Not loading whiteout plugin, as
just fixed that in comps too, thanks!
Interested in others?
Group: base-x
Mandatory Packages:
-xorg-x11-drv-geode
-xorg-x11-drv-omap
Group-Id: printing
Mandatory Packages:
-ghostscript-cups
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
These packages still exist, and haven't been removed or renamed as far
as I can tell.
Yum does not appear able to find them... do you think this is a local problem?
[root@lenovo ryniker]# yum list updates
Loaded plugins: langpacks, refresh-packagekit
[root@lenovo ryniker]# yum repolist
No, they're arch-specific. (geode is 32-bit x86, omap is ARM.)
That makes sense. Should yum understand this better? I mean, should the
group list specify architecture dependencies: some packages are needed
for one architecture, others needed for a different architecture?
As things stand, I do
Well, a statically configured network interface might be expected to
just work.
With dynamic configuration, there must be successful contact with a DHCP
server, and the server must be willing to assign an IP address and
possibly provide other information (gateway, nameserver, host name) to
the
Unnecessary private designation for a bug report might be due to
https://bugzilla.redhat.com/show_bug.cgi?id=1011916
which complains that a bug reporter has to decide about private status
before possibly sensitive information in the report can be examined.
--
test mailing list
The usbmuxd problems reported by yum in your post are likely unrelated to
the lsb issue.
I have a similar usbmuxd problem in F20 Beta TC4. After installation,
during the first yum update I noticed a message about a usbmuxd
scriptlet error. This message vanished among messages from hundreds of
I installed F20 Beta TC4 (KDE) on a Samsung Book 9 plus with no serious
difficulty, but touchpad operation is sometimes erratic and I see this in
syslog:
Oct 16 02:47:18 localhost kernel: [3.407835] usb 2-7: unable to read config
index 0 descriptor/start: -71
Oct 16 02:47:18 localhost
Super simple passwords will no longer be allowed... increased security is
worth it.
No, you just made installation more bothersome - the user will then have
to set the passwords he wants after installation is complete. It is good
to warn about a weak password, but I feel I know better than you
Recapitiulation:
A security problem was recognized because the ssh daemon is enabled by
default on Fedora systems: with a weak root password, a remote attacker
might easily obtain unlimited access.
The direct solution would seem to be a change to the ssh daemon to
prohibit root login in its
we also have no data about the prevalence of weak passwords or attacks
on default-configured Fedora systems
On my firewall system, /var/log/secure is larger than 300 megabytes
(less than one month of data), most of it reports of failed login
attempts to root. I am very careful about passwords on
Fedora-Live-Workstation-x86_64-22-TC3.iso installed without problems
using an external USB drive on my Macbook Pro with 15-inch Retina
Display. I logged on using GNOME with Wayland for the user created during
installation - no problem.
That said, the system appears fragile, and network
Try:
yum grouplist hidden ids
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
I was pleased to see Fedora-Live-Workstation-x86_64-22_Beta-2 boot on my
Apple MacBook Pro 15 with retina display. Install to disk completed
after some fragility relating to my USB flash drive installation
target. Wrote zeros to the first MByte of the flash drive, then Fedora
would partition,
It is interesting to note a difference from F21, where the login
processes are true daemons in the sense they have no controlling
terminal. Now, for example, joachim.bac...@rhrk.uni-kl.de reports:
ps -u gdm
PID TTY TIME CMD
1243 ?00:00:00 systemd
1244 ?00:00:00
Works OK on my Macbook Pro: i7-4850HQ processor with Intel Iris Pro
Graphics 5200 plus Nvidia GT-750M graphics processor.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Auto Freeze Exeception seems too complicated an answer to this
question.
Either continue to call new background a blocker, or decide it is
desirable but not a blocking issue.
If lovely new art is not available, some generic Fnn background could
be used then replaced by an update after release,
When you change from the GRUB default boot item, the timer stops and no
default boot occurs. You must use a key to tell GRUB to boot the current
selection.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
I think you may be the victim of GNOME's "Do what you maybe probably
want." attitude. This is something you might be able to configure to
your taste, given sufficient knowledge about what specifications to
change.
I have a Lenovo machine with a Realtec card reader:
[ryniker@lenovo ~]$ lspci |
>> I do not like to sacrifice well-defined, predictable behavior for
>> convenience
>
>Convenience is what users need!
>
>> but others may argue this default behavior serves the
>> greater good.
>
>What is the *greater good*?
I think the perceived "good" is that users can load a disk and have a
I suspect you suffer from software that wants to help you and "Do the
right thing."
If you try to mount a device with no media, mount might simply fail (no
media present). Instead, at least for optical drives, it presumes the
desired media might be available in the tray and requests the device
>A month is a pretty long time in Fedora development
True, but a month is only available if the problem is reported on day 1.
If it takes a week or two for a user to report a problem, that interval
lessens the remaining time to EOL.
On the other hand, there is no prohibition against a fix after
>It's not like dnf-system-upgrade would magically stop working when N-2
>reaches EOL, so honestly, overall, I just don't really see the problem
>you're describing
Like most of Fedora, dnf-system-upgrade gets limited testing before
release. When N is released, a large number of users who did not
On Tue, 24 Nov 2015 10:46:55 -0800, Adam Williamson wrote:
> We have never really gone to any lengths to test or support N-1 upgrades
> with 3rd party repositories or non-repo software either. That's a
> different question.
>From a user's perspective, the value of system-upgrade depends on its
On Tue, 24 Nov 2015 07:52:47 -0500, Stephen Gallagher wrote:
> I've upgraded several family members directly from Fedora 21 to Fedora 23
> in the last week with no issues whatsoever (of course, I also curate
> their repository selection, so they don't end up with incompatible
> packages).
Aye,
System-upgrade across two releases raises an interesting End-of-Life
policy issue. If system-upgrade from N-2 to N is so important it will
block release of N until it works, how do we explain why it is no
longer important after four weeks when N-2 reaches End of Life?
Four weeks is little time
I believe a failure to upgrade from N-2 to N should not block the N
release. The reason is limited resources, both for tests and for changes
to fix problems. These resources are more valuable applied to the N
release than to something two releases in the past.
If someone wants to test a
The following worked for me:
dnf erase astronomy-bookmarks
(This also erased firefox.)
dnf upgrade
dnf install firefox
(This also installed astronomy-bookmarks)
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
I seem to have touched a sore spot on Mr. Murphy, and apologize if I
have unintentionally irritated him. If he is the designer of the
offline update mechanism, and I correctly perceive the implications of
his explanation, then I do scold him for failure to mitigate the
damage that might occur to a
I am unhappy with the suggestion that the semantics of kernel parameters
may depend on some notion about how "temporary" they are. If a kernel
parameter is specified, it is present; if not specified, it is absent.
It is proper to design parameter syntax and default values to favor
common usage.
The target VM has two virtual IDE drives, sda (8 GB) for / and sdb
(0.5GB) for /boot. Installation proceded normally until time to install
the bootloader, which failed. Pop-up window said bootloader installation
failed, and I chose to continue anyway in order to acquire as much log
information
Works for me. I used a Samsung 940X laptop and a Sandisk 80GB USB3
external SSD.
This is a UEFI machine, and I installed using manual partitioning to
re-use partitions on the external device, which contained an old Fedora
23 system. My purpose here was to preserve an encrypted /home partition.
1 - 100 of 134 matches
Mail list logo
