On Tue, 4 Jun 2019 18:49:29 -0500
Roger Heflin wrote:
> I would check these modules in dracut: dracut --list-modules, some of
> them are rescue and debug and a few other modules may help.
>
> The tools may allow you to get a prompt inside the boot when it fails
> and/or give you some tools to
On Tue, 4 Jun 2019 20:58:48 -0500
Chris Adams wrote:
> Once upon a time, stan via users said:
> > I'm not sure that the issue is in dracut, since it is systemd that
> > prints the final messages. But, this is still something I will
> > implement, just in case.
>
> Check SELinux - rsync
On Tue, 4 Jun 2019 20:58:48 -0500
Chris Adams wrote:
> Once upon a time, stan via users said:
> > I'm not sure that the issue is in dracut, since it is systemd that
> > prints the final messages. But, this is still something I will
> > implement, just in case.
>
> Check SELinux - rsync
On 6/4/19 8:50 PM, Ranjan Maitra wrote:
On Tue, 4 Jun 2019 18:57:14 -0700 Samuel Sieb wrote:
I would recommend disabling the hardware RAID if possible and use the
Linux software RAID instead. RAID0 is combining the two drives for more
space (and speed) not redundancy and you should have
On Tue, 4 Jun 2019 18:57:14 -0700 Samuel Sieb wrote:
> On 6/4/19 6:40 PM, Ranjan Maitra wrote:
> > On Tue, 4 Jun 2019 18:24:42 -0700 Samuel Sieb wrote:
> >
> >> On 6/4/19 5:45 PM, Ranjan Maitra wrote:
> >>> On Tue, 4 Jun 2019 10:27:24 -0700 Samuel Sieb wrote:
> >>>
> On 6/4/19 8:20 AM,
On Wed, 05 Jun 2019 12:44:13 +0930 Tim via users
wrote:
> On Tue, 2019-06-04 at 20:40 -0500, Ranjan Maitra wrote:
> > Yes, it is a hardware RAID. The BIOS is very confusing but it does
> > not say anything in there (anymore).
>
> Hardware RAID *relies* on the hardware. If you lose the
On Tue, 2019-06-04 at 20:40 -0500, Ranjan Maitra wrote:
> Yes, it is a hardware RAID. The BIOS is very confusing but it does
> not say anything in there (anymore).
Hardware RAID *relies* on the hardware. If you lose the hardware, you
lose access to your files. So, a motherboard dying can make
Once upon a time, stan via users said:
> I'm not sure that the issue is in dracut, since it is systemd that
> prints the final messages. But, this is still something I will
> implement, just in case.
Check SELinux - rsync doesn't copy that IIRC, so you may need to force a
relabel. You can
On 6/4/19 6:40 PM, Ranjan Maitra wrote:
On Tue, 4 Jun 2019 18:24:42 -0700 Samuel Sieb wrote:
On 6/4/19 5:45 PM, Ranjan Maitra wrote:
On Tue, 4 Jun 2019 10:27:24 -0700 Samuel Sieb wrote:
On 6/4/19 8:20 AM, Ranjan Maitra wrote:
However, the machine now does not come up. All I get is the
On Tue, 4 Jun 2019 19:48:58 + (UTC)
3603060...@txt.att.net wrote:
> Try adding the kernel configuration boot option "printk.devkmsg=on"
> and reboot your computer.
When I tried that, dracut went to the next item in the menu for some
reason. I also tried ignore_loglevel and
On 6/1/19 5:27 AM, Garry T. Williams wrote:
On Friday, May 31, 2019 11:05:20 PM EDT Tim via users wrote:
On Fri, 2019-05-31 at 17:18 -0400, Garry Williams wrote:
But, of course, the issue is why this happens in the first place.
Does your ISP insert a transparent proxy between you and the
On Tue, 4 Jun 2019 18:49:29 -0500
Roger Heflin wrote:
> I would check these modules in dracut: dracut --list-modules, some of
> them are rescue and debug and a few other modules may help.
>
> The tools may allow you to get a prompt inside the boot when it fails
> and/or give you some tools to
On Tue, 4 Jun 2019 18:24:42 -0700 Samuel Sieb wrote:
> On 6/4/19 5:45 PM, Ranjan Maitra wrote:
> > On Tue, 4 Jun 2019 10:27:24 -0700 Samuel Sieb wrote:
> >
> >> On 6/4/19 8:20 AM, Ranjan Maitra wrote:
> >>> However, the machine now does not come up. All I get is the splash screen
> >>> 120GB
On 6/4/19 5:45 PM, Ranjan Maitra wrote:
On Tue, 4 Jun 2019 10:27:24 -0700 Samuel Sieb wrote:
On 6/4/19 8:20 AM, Ranjan Maitra wrote:
However, the machine now does not come up. All I get is the splash screen 120GB drive
"Offline"
I assume this is from the firmware? I don't understand why
Hi,
Thanks!
On Tue, 4 Jun 2019 10:27:24 -0700 Samuel Sieb wrote:
> On 6/4/19 8:20 AM, Ranjan Maitra wrote:
> > However, the machine now does not come up. All I get is the splash screen
> > 120GB drive "Offline"
>
> I assume this is from the firmware? I don't understand why it would be
>
I would check these modules in dracut: dracut --list-modules, some of
them are rescue and debug and a few other modules may help.
The tools may allow you to get a prompt inside the boot when it fails
and/or give you some tools to do some debugging.
On Tue, Jun 4, 2019 at 1:09 PM stan via users
On Tue, 2019-06-04 at 20:14 +0200, Patrick Dupre wrote:
> Hello,
>
> It is say:
> You can test your stick using QEMU.
> qemu -hda /dev/sdX -m 1024 -vga std
> I installed qemu (dnf install qemu).
> Then
> qemu -hda /dev/sdc -m 1024 -vga std
>
> bash: qemu: command not found...
>
> What I am
On 6/4/19 2:08 PM, Patrick Dupre wrote:
Where did you see that message? The man page suggests using a partition
In my opinion, this is ambiguous:
livecd-iso-to-disk Fedora-Workstation-Live-x86_64-30-1.1.iso /dev/sdX
in
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
I use a completely different way to boot from USB. I followed
(mostly) the instructions here (and things it points at) and
have a bootable USB stick which contains several ISO images
and can boot them from grub:
https://wiki.archlinux.org/index.php/Multiboot_USB_drive
On 6/4/19 1:06 PM, Tom H wrote:
On Tue, Jun 4, 2019 at 7:14 PM Patrick Dupre wrote:
It is say:
You can test your stick using QEMU.
qemu -hda /dev/sdX -m 1024 -vga std
I installed qemu (dnf install qemu). Then
qemu -hda /dev/sdc -m 1024 -vga std
bash: qemu: command not found...
On Tue, Jun 4, 2019 at 7:14 PM Patrick Dupre wrote:
>
> It is say:
> You can test your stick using QEMU.
> qemu -hda /dev/sdX -m 1024 -vga std
>
> I installed qemu (dnf install qemu). Then
> qemu -hda /dev/sdc -m 1024 -vga std
>
> bash: qemu: command not found...
qemu-system-x86_64 (for x86_64)
Try adding the kernel configuration boot option "printk.devkmsg=on" and reboot
your computer.
-Original Message-
From:
Sent: Tue, 4 Jun 2019 11:08:25 -0700
To: 3603060...@txt.att.net
Subject: Re: Cloning of existing fedora install failing at switch root. D
>On Tue, 4 Jun 2019
On 6/4/19 11:06 AM, Patrick Dupre wrote:
Something strange to me: it is said:
Fedora Media Writer destroys all data on the USB stick. If you need a
non-destructive write method (to preserve existing data on your USB stick) or
support for 'data persistence', you can use the livecd-iso-to-disk
dnf install qemu
Last metadata expiration check: 1:35:33 ago on Tue 04 Jun 2019 07:22:21 PM CEST.
Package qemu-2:2.11.2-5.fc28.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!
===
On 2019-06-04 2:14 p.m., Patrick Dupre wrote:
> Hello,
>
> It is say:
> You can test your stick using QEMU.
> qemu -hda /dev/sdX -m 1024 -vga std
> I installed qemu (dnf install qemu).
> Then
> qemu -hda /dev/sdc -m 1024 -vga std
>
> bash: qemu: command not found...
>
> What I am doing wrong?
>
On Tue, 4 Jun 2019 16:52:18 - (UTC)
Beartooth wrote:
> BQ1 (Big Question 1) If I were to remove all of KDE, how
> would I do it? Find KDE in dnfdragora and follow my nose?? I had
> thought I could command "dnf remove kde" or "dnf remove KDE," and
> then go through the resulting list
On 05/06/2019 02:06, Patrick Dupre wrote:
> Hello,
>
> Something strange to me: it is said:
> Fedora Media Writer destroys all data on the USB stick. If you need a
> non-destructive write method (to preserve existing data on your USB stick) or
> support for 'data persistence', you can use the
Hello,
It is say:
You can test your stick using QEMU.
qemu -hda /dev/sdX -m 1024 -vga std
I installed qemu (dnf install qemu).
Then
qemu -hda /dev/sdc -m 1024 -vga std
bash: qemu: command not found...
What I am doing wrong?
Thank.
On Tue, 4 Jun 2019 12:37:04 -0500
Roger Heflin wrote:
> Did you check the kernel command line in grub.cfg to see what root= is
> set to? That is the only place I know specifically references what
> to look for on the switch root.
Yep, converted all the old UUIDs for boot and root to the new
Hello,
Something strange to me: it is said:
Fedora Media Writer destroys all data on the USB stick. If you need a
non-destructive write method (to preserve existing data on your USB stick) or
support for 'data persistence', you can use the livecd-iso-to-disk utility on
Fedora.
Then,
On 05/06/2019 00:52, Beartooth wrote:
> I run Mate under F30. I assume Mate calls a lot of Gnome code
> (most or all of what Gnome3 didn't change). So I never worry about any
> new app bringing Gnome stuff with it.
>
> Until recently, I also made minor but important use of Konqueror
Did you check the kernel command line in grub.cfg to see what root= is
set to? That is the only place I know specifically references what
to look for on the switch root.
On Tue, Jun 4, 2019 at 10:41 AM stan wrote:
>
> Hi,
> I'm trying to clone an existing Fedora install, just a / partition and
On 6/4/19 8:20 AM, Ranjan Maitra wrote:
However, the machine now does not come up. All I get is the splash screen 120GB drive
"Offline"
I assume this is from the firmware? I don't understand why it would be
telling you it's offline though. "Splash screen"? What does it mean by
"offline"?
I run Mate under F30. I assume Mate calls a lot of Gnome code
(most or all of what Gnome3 didn't change). So I never worry about any
new app bringing Gnome stuff with it.
Until recently, I also made minor but important use of Konqueror
and K3B; I've noticed, when sometimes
Hi,
I'm trying to clone an existing Fedora install, just a / partition and
a /boot partition, both ext4. I use rsync,
# rsync -C -x -u -a -v -A -X /mnt/old/ /mnt/new
to clone both partitions from a running Fedora.
I then clean up the /etc/fstab and /boot/grub2/grub.cfg by changing the
UUIDs of
Hi,
My apologies for the OT nature of this post.
I have a Dell T5810 which has a SSD drive that is 2 x 60gb stripped to 120Gb.
(ONe was a raid version of the other.) This has /, /boot, /usr/local and swap
as partitions.
I also have three 2TB (SATA, non-SSD) hard drives (one that is raid of
On Mon, Jun 3, 2019 at 11:55 PM wrote:
> See comment inline…
>
>
>
>
>
> Met vriendelijke groet,
>
> *Hans Witvliet, J, Ing., DMO/OPS/I/APH, Kennis Team Opensource*
>
> *Coldenhovelaan 1 Maasland 3531RC Coldehovelaan 1, kamer B213*
>
>
>
> *From:* Jack Craig [mailto:jack.craig.ap...@gmail.com]
>
See comment inline…
Met vriendelijke groet,
Hans Witvliet, J, Ing., DMO/OPS/I/APH, Kennis Team Opensource
Coldenhovelaan 1 Maasland 3531RC Coldehovelaan 1, kamer B213
From: Jack Craig [mailto:jack.craig.ap...@gmail.com]
Sent: maandag 3 juni 2019 20:11
To: Community support for Fedora users
my goal in pursuing openvpn was to learn about VPNs and how they work.
openvpn was perfect for that. however, as a fine gentleman pointed me at
wireguard, so openvpn uninstall!
it's the only sane, opensource option...
thx again to all that replied, jackc...
On Mon, Jun 3, 2019 at 11:05 PM
On Tue, Jun 04, 2019 at 02:31:38 +,
j.witvl...@mindef.nl wrote:
Also it lacks encapsulation; essential for punching restrictive firewalls.
That doesn't need to be built in to the encrytion tunnel and is probably
best to use a seperate tunnel to make your traffic look like https, http,
41 matches
Mail list logo
