By mistake I removed administration privileges from my account
under kde, which is the only account that had it. Removing the privilege
has removed my account from sudoers. Is the only course of action I have
to get it back to reinstall F29 and then upgrage to F31?
On 12/1/20 04:18, Doug H. wrote:
> On Sat, 2020-01-11 at 23:54 +1100, Stephen Morris wrote:
>> By mistake I removed administration privileges from my
>> under kde, which is the only account that had it. Removing the
>> has removed my account from sudoers. Is the only course of action I
>> to get it back to reinstall F29 and then upgrage to F31?
> Nope, lots of simpler methods...
> 1. Of course, if you have the root password you can give your user
> 2. Boot to a maintenance CD and set a root password.
I don't have the root account enabled and I don't have a maintenance CD
for F31 as it was an upgrade from F30, which was an upgrade from F29.
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct:
>> List Guidelines:
>> List Archives:
On Sat, Jan 11, 2020 at 7:15
> PM Samuel Sieb <samuel(a)sieb.net> wrote:
>> On 1/11/20 9:14 AM, Patrick O'Callaghan wrote:
>>> On Sat, 2020-01-11 at 23:18 +1030, Tim via users wrote:
>>>> On Fri, 2020-01-10 at 09:25 -0600, Ranjan Maitra wrote:
>>>>> the printing is largely of documents, but the printer sits for a
>>>>> while doing nothing. I guess laser is the way to go then? What are
>>>>> goog suggestions then?
Look around for a used HP laser printer. I am using an HP1320 which I
bought in May, 2005 for about $550 including an extra cartridge and tax.
HP cartridges are expensive! I have no idea how many cartridges I have
gone through, probably over a dozen, and it is as good as the day I
bought it. Drivers are included with cups or hplip. The bare HP1320
needs a ~$30 network print server if you want to network it, otherwise a
If you want print/fax/scan, then one of the all in ones or 'MFP'. I have
an HP3055 which I purchased in 2006 (to replace the fax machine which
had died). I mainly use it for scanning now. It has builtin network
capability. Again, the drivers are included in your basic install of
cups or hplip.
A good one will probably cost you $50-$75. Off-brand cartridges cost
about that. ATM there is an HP P2015d for sale used on kijiji.ca in the
Toronto area for $80Cdn. Physically it looks exactly like the HP1320 and
has duplex capability. So... $60US???
I happen to like HP printers, but Brother printers do the same thing and
are just about as dependable and long-lived. I've had Brother printers
too. The best scanner I have ever used is a Brother ADS-1000. Once did
over 650 pages in one continuous pass!
It would seem that "something" happened to the file(s) that provide
RJ45 Ethernet connectivity maybe as far back as F29. I can get a WiFi
connection, but not an RJ45 eth0 DHCP connection. This happens in my
home and at a nearby computer store, so it's not my DHCP server.
When booted up to WiFi, connecting an RJ45 Ethernet cable shuts down
the existing WiFi port (normal), but never comes up with a DHCP address
for the eth0 port. The network icon just loops forever. When I
disconnect the RJ45 cable, WiFi connectivity resumes after 5-10
The problem has persisted since upgrades to both F30 and F31. I'm
guessing the best way to fix the problem is a fresh install of whatever
packages provide eth0 connectivity. I'm at a loss to know what those
packages are, and if there are any hidden potholes/landmines with
simply using dnf to first remove then to install them from scratch.
If it matters, I'm using the mate v1.22.2 desktop. Here are all the
*mate* packages I have installed:
# rpm -qa | grep mate | sort
Some detailed guideance would be much appreciated.
Incidentally, I have appended " net.ifnames=0" to the
GRUB_CMDLINE_LINUX= line and rebuilt the initramfs to revert back to
classic eth0 nomenclature for the RJ45 Ethernet port. I can't stand the
new naming convention. :-)
Fairview Heights, IL
Currently, the From: field on any emails I send to Fedora lists gets
"Benjamin Lowry via users <users(a)lists.fedoraproject.org>"
How do I turn this behavior off? I'm fine with my real address getting
scraped by spambots or whatever. -ben
> By mistake I removed administration privileges from my account
> under kde, which is the only account that had it. Removing the privilege
> has removed my account from sudoers. Is the only course of action I have
> to get it back to reinstall F29 and then upgrage to F31?
Use the procedure below to add yourself back to sudoers
I recently purchased a new computer. My old computer had Fedora 31
installed on an M.SATA drive. My new computer did not have an M.SATA
slot. I could have added one via a PCIe card, but decided against it.
I've been using Linux since RH8 days as my sole workstation. I've migrated
OSes from hard drive to hard drive many times. In the old days I'd do a
fresh install and then copy /home and try to reinstall all the apps I had
installed. It was a big PITA.
Even updates used to be problematic in the early days of Fedora... ;)
I hate migrating to a new computer. It can take a long time to get
everything set up just the way you want it. I've done migrations with dd
before, but there are always little issues with getting the new drive to
boot properly, copying directories that shouldn't be, etc. It works, but
it takes a bit of tweaking to make it work.
Today I had my best OS migration ever. It appears that everything came
across to the new drive perfectly, with just about zero hassle. In fact,
tonight I am forgetting that I'm operating on a new machine, except it is
twice as fast... :)
Here is how I did the migration:
Step #1 Create a Live USB of the same version as the old (source) machine.
Step #2 Boot the Live USB on the new (target) machine and install Fedora.
Step #3 Boot the newly installed OS on the target machine and run dnf
update. If you install a user, make it different from any on the source
Step #4 Run dnf update on the old (source) machine.
Both machines should now have the same OS vintage. You can double check
this by making sure both are running the same kernel.
Step #5 cp /etc/fstab on the target machine to somewhere safe, just in
Step #6 Reboot the target machine with the Live USB.
Step #7 The target machine is now running the LiveUSB OS. Find the drive
partitions for swap, root (/), boot (/boot) and home (/home) for the new
drive on the new machine. Nautilus displays them as "Other locations..."
or something like that. They probably won't be mounted.
You'll need device handles for each partition on the new drive so that they
can be mounted. Ie /dev/sda1, etc.
The new OS drive on my new machine was an M.2 NVMe drive. It was
formatted into 4 partitions /dev/dm-0 (swap), /dev/dm-1 (home), /dev/dm-2
(root) and /dev/dm-3 (boot) by the live install process.
Step #8 create a mount point and mount the root partition on the new machine
# mount /dev/<root partition device>... drive
Step #9 mount the home partition to drive/home so that it looks like it
does on a regular Linux system.
mount /dev/<home partition> home
At this point /mnt/drive should look like the root of a regular Linux
system, ie home, usr, bin, var... etc. The home partition on the new
drive will be mounted to /mnt/drive/home. You should cd into it just to
DO NOT MOUNT THE ROOT PARTITION !
Step #9 use rsync to copy all the relevant files from the source computer
to the mounted directory structure.
From /mnt/drive, issue the following command:
sudo rsync -aHxv --numeric-ids --progress root@<sourceComputerIP>:/*
/mnt/drive --exclude=/dev --exclude=/proc --exclude=/sys --exclude=/tmp
This command will copy all the relevant files from the source machine to
the directory structure we just made on the target hard drive.
Depending on how much you have installed on the source computer, this will
take a while. Make sure that both the network interfaces are operating as
fast as they can.
I saw file transfer speeds of 100 MB/sec for large files on 2 machines
networked with 1000 Mb/sec NICs. Small files don't reach that speed. The
CPU usage on the source machine ran at 25-30% on a quad core i7.
BTW, the source machine must be set up to allow root logins to ssh for this
to work. The commands on the source machine to enable this are:
Find the commented like for PermitRoot and set it to: PermitRootLogin yes
#systemctl restart sshd.service
If you forget to run rsync from /mnt/drive and do it from / or specify the
target directory as /, you'll install the files on the Live USB file
structure instead of the target drive, thus messing it up ! No biggie,
just rebuild the Live USB and do this step over.
Step #10 Verify that /mnt/drive/etc/fstab is still in tact and the same as
what it was prior to the rsync operation. If not, replace
/mnt/drive/etc/fstab with the fstab file that was set aside. Do not copy
the backup fstab file to /etc/fstab as that points to the Live USB OS ! It
must be copied to /mnt/drive/etc/fstab.
(It took me several times to complete my clone drive because I kept
forgetting that the root of my target fs was /mnt/drive and thus I messed
up my Live USB drive a couple times.)
Step #11. Reboot the target computer using the new drive OS. We didn't
touch the /boot partition, so it should boot right up. However, the drive
partitions got written to outside of the OS, so they will be checked. This
can take a bit of time. Press ESC to watch this go on.
Once the boot process is complete, SELinux won't be happy and some of the
partitions will probably mount as read only.
To fix this problem, open a console session and issue the following
statement and reboot the computer.
#shutdown -r now
When the target computer reboots, a message will appear:
"Warning - SELinux targeted policy relabel is required....
It will start relabelling things. When it is done you should have an exact
clone of the install you had on the source computer.
The only potential issue I know of with this method is that the grub kernel
list doesn't match the kernels installed. Thus if you look in /boot there
will only be the kernels that were installed during the live install
process. But if you use dnf list kernel, you'll see the kernels that were
installed on the source machine. If this bothers you, use dnf to
uninstall and reinstall the kernels you want. Reinstalling the kernels
will enter them into grub properly. This problem will also take care of
itself over time as new kernels are installed via dnf update.
The only thing that didn't work exactly as it did on my source computer was
Eclipse and I"m not sure that had anything to do with the cloning.
I hope this helps someone.