Wed, 28 Jul 2021 08:14:12 -0400
Jonathan Billings kirjoitti:
> So, I guess it's "No worries".
>
Tnx, releasing beer for that...
Jarmo
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproj
On Wed, Jul 28, 2021 at 01:31:07PM +0300, jarmo wrote:
> Now what makes me wonder, why this:
> kernel-headers-5.13.3-200.fc34.x86_64
> is different than all other KERNEL versions?
The kernel-headers package no longer tracks the version of the kernel
installed. This bit me a while back because I wa
On 28/07/2021 18:31, jarmo wrote:
Just checked KERNEL related, what installed into
my desktop, I found:
[root@oh1mrr oh1mrr]# rpm -qa | grep kernel
kernel-srpm-macros-1.0-4.fc34.noarch
libreport-plugin-kerneloops-2.15.2-2.fc34.x86_64
abrt-addon-kerneloops-2.14.6-3.fc34.x86_64
kernel-core-5.12.15
Just checked KERNEL related, what installed into
my desktop, I found:
[root@oh1mrr oh1mrr]# rpm -qa | grep kernel
kernel-srpm-macros-1.0-4.fc34.noarch
libreport-plugin-kerneloops-2.15.2-2.fc34.x86_64
abrt-addon-kerneloops-2.14.6-3.fc34.x86_64
kernel-core-5.12.15-300.fc34.x86_64
kernel-modules-5.12
Sam Varshavchik:
Is anyone running XFCE seeing Thunar being very confused when booting
kernel 5.0.5? Mine no longer automounts my removable usb storage mp3
player. As a consolation prize, of sorts, Thunar informs me that /boot,
/home, /sys, and the like, are removable volumes, and shows a
Mon, 08 Apr 2019 17:41:40 -0400
Sam Varshavchik kirjoitti:
> Is anyone running XFCE seeing Thunar being very confused when booting
Yesterday updated and now can't log in.
Seem that login screen is halted, no can do :)
Was so late, have to investigate later.
It's a Lenovo T61 lap
Is anyone running XFCE seeing Thunar being very confused when booting kernel
5.0.5? Mine no longer automounts my removable usb storage mp3 player. As a
consolation prize, of sorts, Thunar informs me that /boot, /home, /sys, and
the like, are removable volumes, and shows a folder icon for
On 02/05/14 16:33, Robert P. J. Day wrote:
> On Wed, 5 Feb 2014, Ed Greshko wrote:
>
>> On 02/05/14 05:22, Robert P. J. Day wrote:
>>> just digging into systemd (so be prepared for several potentially
>>> silly questions), and i was playing with some variations of listing
>>> systemctl services,
On Wed, 5 Feb 2014, Ed Greshko wrote:
> On 02/05/14 05:22, Robert P. J. Day wrote:
> > just digging into systemd (so be prepared for several potentially
> > silly questions), and i was playing with some variations of listing
> > systemctl services, and i ran:
> >
> > # systemctl list-units -t ta
On 02/05/14 05:22, Robert P. J. Day wrote:
> just digging into systemd (so be prepared for several potentially
> silly questions), and i was playing with some variations of listing
> systemctl services, and i ran:
>
> # systemctl list-units -t target --all
>
> and everything looked fine other tha
just digging into systemd (so be prepared for several potentially
silly questions), and i was playing with some variations of listing
systemctl services, and i ran:
# systemctl list-units -t target --all
and everything looked fine other than this line:
syslog.target not-found inactiv
On 14.11.2011, Smith, Herb wrote:
> With the changes that are introduced in FC16 (specifically
> the UID and GID numbering and the disk label changes) I
> was wondering if using PreUpgrade is preferred.
After reading about problems with grub and uid/gid here, I would
suggest doing a fresh i
All,
I have been using Fedora since back in the RedHat 8 days. Here of late, when
updates come out I have typically just downloaded the DVD and done an Upgrade
of an existing installation and I have had great success with that. I have not
used PreUpgrade and I'm not clear on what the advantag
On Sun, 04 Sep 2011 21:04:19 -0500
Michael Cronenworth wrote:
> Anaconda will not have any alignment issues. They were solved several
> releases ago.
Thanks for the info. I'm always tempted to overthink things
(especially when I'm waiting for parts to arrive and have
time on my hands to make com
On 09/04/2011 07:38 PM, Tom Horsley wrote:
> So, if I do all that, what is the process like to get
> fedora 15 installed on such a drive? Fedora 15 hasn't
> gone to grub2, so I don't know if the f15 grub understands
> and new magical uefi style boot procedure (I know I
> certainly don't, I merely h
So, my old system died, and in a typical overkill fashion,
I decided to put a new one together with all the latest
and greatest hardware.
The motherboard I ordered (ASUS P8H67-V rev 3) has a UEFI
bios, and support for sata 6G/s drives. Continuing the
overkill theme, I also ordered a SSD disk that
On Sun, Jan 9, 2011 at 5:26 PM, Tim wrote:
Options for stanzas are read from within them, top to bottom. In this
> case, the first one sets the password, the second line halts further
> processing until the password is entered. Once entered, it would
> process the next two commands.
>
* *I di
On 01/09/2011 02:18 PM, Tim wrote:
> 13.2.10 password
>
>
> -- Command: password [`--md5'] passwd [new-config-file]
>
Well it seems to have changed in F14 which is different.
...
Thus, GRUB provides a "password" feature, so that only administrators
can start the interacti
Parshwa Murdia:
>>> password --md5 $differentpassword
Genes MailLists:
>Is -md5 documented ? When I check info grub I see
>
> password --encrypted
>
> where grub-crypt is suggested to be used to encrypt.
>
> grub-crypt indeed has an md5 option tho sha-512 seems to be the default.
Yes,
On 01/09/2011 06:56 AM, Tim wrote:
>>
>> password --md5 $differentpassword
>>
>
Is -md5 documented ? When I check info grub I see
password --encrypted
where grub-crypt is suggested to be used to encrypt.
grub-crypt indeed has an md5 option tho sha-512 seems to be the default.
(f14
On Sun, 2011-01-09 at 11:56 +0100, Parshwa Murdia wrote:
> But if a different password is required, we should enter it above the
> line
>
> title Memtest86+ (2.11)
>
> so that it looks:
>
> password --md5 $differentpassword
>
> title Memtest86+ (2.11)
>lock
>root (hd0,1)
>
On Sun, Jan 9, 2011 at 10:04 AM, Tim wrote:
#boot=/dev/sda
> default=0
> timeout=5
> splashimage=(hd0,1)/grub/splash.xpm.gz
> password --md5 $supercalifragilistic.
>
> title Fedora (2.6.27.25-78.2.56.fc9.i686)
>lock
>root (hd0,1)
>kernel /vmlinuz-2.6.27.25-78.2.56.fc9.i686
On Sun, 2011-01-09 at 19:34 +1030, Tim wrote:
> In the grub.conf file, when there's a password and lock command above
> all the boot choices, they'll need to enter the password before they
> can do anything (pick a choice, temporarily edit what grub will do).
> It's where you place the lock command
On Sun, 2011-01-09 at 13:32 +0530, Parshwa Murdia wrote:
> which are just below the name of the OS in
> the /boot/grub/grub.conf file):-
>
> password --md5 $1$X58Kw/$v71Qlprzt8f4U9uOu46nk0
> lock
>
> and after that I press 'b' to boot without entering the encrypted
> password during the booting
hi,
As someone earlier let me know about the encrypting of passwords, I did the
following:
after becoming the root, used the command:
md5crypt
to get the encrypted string of passwords for using in /boot/grub/grub.conf
This is the password which is NOT the password of the user who logs-in. But
w
/dev/sde puts the boot loader on /dev/sde .
And I'm totally Confused, how can this hard drive be at /dev/sde.
the hard drive also has Windows 7 as /dev/sda . Can someone explain how
all this is working.
--
users mailing list
users@lists.fedoraproject.org
To unsubscr
26 matches
Mail list logo
