On Thu, 2020-03-12 at 18:22 -0600, home user wrote:
> a vague memory that on my work station, booting from a USB stick
> only works from one or two specific ports, which take USB-2 (not USB-
> 3) sticks. So I re-did the mediawriter, this time writing the
> download to a USB-2 stick. Then I put th
Neil Thompson:
> I generally wait a month or so before upgrading, just to make sure
> that everything on the additional repos is sorted out.
sixpack13:
> sorted out from whom ?
>
> you're screw if everybody waits.
While there's a point in your rebuttle, the reality is that not
everybody waits.
On 3/12/20 8:08 PM, Neil Thompson wrote:
Ralf,
With all due respect (i.e. none) I don't think your opinion is really
necessary here - you've made your feelings clear over the last long while
and I have to wonder what the heck you're still doing here if you hate the
whole thing so much. Surely t
On 13.03.20 08:20, Tim via users wrote:
...
While there's a point in your rebuttle, the reality is that not
everybody waits. Those with the confidence or debugging skills do wade
in, straight away.
On the other hand, there are plenty of users without debugging skills,
and there's little useful
People,
In the olden days I used to just edit the grub conf file and delete
these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet"
grubby --update-kernel=ALL --remove-args="rhgb"
does not make any difference to the boot infor
On 13.03.20 17:10, Philip Rhoades wrote:
People,
In the olden days I used to just edit the grub conf file and delete
these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet"
grubby --update-kernel=ALL --remove-args="rhgb"
do
On Fri, 13 Mar 2020 at 10:21, sixpack13 wrote:
> On 13.03.20 08:20, Tim via users wrote:
> ...
> >
> > While there's a point in your rebuttle, the reality is that not
> > everybody waits. Those with the confidence or debugging skills do wade
> > in, straight away.
> >
> > On the other hand, ther
I'm packaging pylint for python2 on centos8 and it builds fine but will not
install.
(Yes I know python2 is end of life - working on it)
mock is used to do the builds.
Here is what happens with I do the dnf install:
# dnf install -y ods-python-pylint
Last metadata expiration check: 0:19:59 ago
(On Thu, 2020-03-12 at 6:22 PM, I wrote)
> Tomorrow, I'll stick it to my workstation again,
> and try to do something "rooty", and report.
Tried it. After booting up off the stick, I had to do "su -" to do
anything "rooty". But I notice that even then, I could not see much of
anything in the
Barry Scott wrote:
> I'm packaging pylint for python2 on centos8 and it builds fine but will not
> install.
> (Yes I know python2 is end of life - working on it)
At least on EL8, python2 will be supported for a number of
years still. Obviously, moving to python3 is still the wise
plan. :)
> moc
On Sat, 14 Mar 2020 03:10:04 +1100
Philip Rhoades wrote:
> In the olden days I used to just edit the grub conf file and delete
> these args manually - now I am supposed to use grubby but doing this:
You're on olden days 2. Now you need to use grub2-editenv to
edit the kernelopts variable that ap
On Sat, 14 Mar 2020 03:10:04 +1100
Philip Rhoades wrote:
> People,
>
> In the olden days I used to just edit the grub conf file and delete
> these args manually - now I am supposed to use grubby but doing this:
>
>grubby --update-kernel=ALL --remove-args="quiet"
>grubby --update-kernel
On Fri, 13 Mar 2020 10:49:46 -0600
home user wrote:
> Tried it. After booting up off the stick, I had to do "su -" to do
> anything "rooty". But I notice that even then, I could not see much
> of anything in the workstation itself. For example, whether I do a
> journalctl or use the logs too
> On 13 Mar 2020, at 17:33, Todd Zullinger wrote:
>
> Barry Scott wrote:
>> I'm packaging pylint for python2 on centos8 and it builds fine but will not
>> install.
>> (Yes I know python2 is end of life - working on it)
>
> At least on EL8, python2 will be supported for a number of
> years sti
On 3/13/20 9:49 AM, home user wrote:
I used mediawriter. I don't see how simply using dd could work. I see
that, using mediawriter puts only one file into my Downloads directory,
but 5 top-level directories end up on my stick (was new/empty
beforehand). That suggests that mediawriter did mor
Barry Scott wrote:
>> On 13 Mar 2020, at 17:33, Todd Zullinger wrote:
>>
>> I would guess it's from a shebang in one of the scripts
>> within the package. But I don't know what's in the
>> ods-python-pylint package so I can only guess.
>
> I fixed up all the shebangs to be #!/usr/bin/python2.7
On 2020-03-14 05:12, Tom Horsley wrote:
On Sat, 14 Mar 2020 03:10:04 +1100
Philip Rhoades wrote:
In the olden days I used to just edit the grub conf file and delete
these args manually - now I am supposed to use grubby but doing this:
You're on olden days 2. Now you need to use grub2-editenv
On 2020-03-14 05:13, stan wrote:
On Sat, 14 Mar 2020 03:10:04 +1100
Philip Rhoades wrote:
People,
In the olden days I used to just edit the grub conf file and delete
these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet"
g
On 2020-03-14 03:21, sixpack13 wrote:
On 13.03.20 17:10, Philip Rhoades wrote:
People,
In the olden days I used to just edit the grub conf file and delete
these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet"
grubby --upd
On Sat, 14 Mar 2020 08:59:12 +1100
Philip Rhoades wrote:
> Did that but I still don't get the verbose boot . .
Sounds an awful lot like you're booting something different
than you think you're booting. That's the only idea I have left.
___
users mailing
On 13.03.20 22:59, Philip Rhoades wrote:
...
[ -d /sys/firmware/efi/efivars ] && sudo grub2-mkconfig -o
/boot/efi/EFI/fedora/grub.cfg || sudo grub2-mkconfig -o
/boot/grub2/grub.cfg
...
Did that but I still don't get the verbose boot . .
then check after an addional run of the above "...gru
On 13.03.20 23:03, Tom Horsley wrote:
On Sat, 14 Mar 2020 08:59:12 +1100
Philip Rhoades wrote:
Did that but I still don't get the verbose boot . .
Sounds an awful lot like you're booting something different
than you think you're booting. That's the only idea I have left.
...
+1
--
sixpack13
(On Fri, 13 Mar 2020 12:20 PM, Stan wrote)
> So, you have to mount the installed image someplace, and
> then either cd there or chroot there, in order to do
> anything to the installed OS. I vaguely recall that
> /mnt/sysimage used to be used for this automatically. e.g.
> mount /dev/sd1 /mnt/sysi
(On 3/13/20 2:44 PM, Samuel wrote)
> It opens up the iso and puts the files...
ok. Now I understand. Thank-you, Samuel.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora C
On 3/13/20 5:49 PM, home user wrote:
This might be easier if we make this more concrete. So let's suppose I
want to do
"journalctl"
or
"less /var/log/dnf"
After booting up the live image and doing the "su -", what do I do?
In general, it's better to use "sudo -i" instead. "su" requires you t
Tim:
>> it's entirely possible that some motherboards can't boot from some
>> USB connectors at all, and some could be user-configured that way
home user:
> In my case, I think the problem is trying to boot from the USB-3
> ports, not writing to the USB-3 port.
Just out of curiosity, have you be
26 matches
Mail list logo
