date:20200407

Thanks

On Tue, Apr 7, 2020 at 10:58 PM Samuel Sieb  wrote:

> On 4/7/20 4:58 AM, Sreyan Chakravarty wrote:
> > I though Fedora KDE was an official image, are you saying that its not ?
>
> I don't see how that relates to what I said.  The official images are
> only released once for each release.  There are unofficial respins done
> for the workstation live, but only that one.  It's only 6 months between
> releases, so there's not much point doing respins for everything anyway.
>
> > On Tue, Apr 7, 2020 at 2:13 PM Samuel Sieb  > > wrote:
> >
> > On 4/6/20 9:52 PM, Sreyan Chakravarty wrote:
> >  > Well I tried that it told me that I did not have enough space.
> >  >
> >  > The easiest option is use a distro which uses the updated
> version. I
> >  > have no clue why Fedora a distro that lives on the bleeding edge
> > does
> >  > not update its ISO images.
> >
> > Because releasing new official images requires running the whole QA
> > process on them and QA is busy working on the next release.  There
> are
> > unofficial respins that are done regularly for the workstation live
> > image though.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>


-- 
Regards,
Sreyan Chakravarty
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

sort of Rawhide related

2020-04-07 Thread David

I am a novice user of Fedora Rawhide.

Today, I did a fresh new clean install ( on an cheap old SSD ) of Rawhide
as my only operating system.

I used the nightly compose finder, and chose "Workstation live"
for X86_64, using the last good iso "20200325."

This was probably my 5th time to install Rawhide
on hardware in the past year or two.

I have been using Xfce in Rawhide for over 3 months, and I was
biased against it from the start, so I can not give a fair review.   Fedora
Xfce
just seemed so 2016, even in Rawhide.

The final straw was that Firefox 75 is coming out soon ( with better
wayland improvements ), and I missed wayland. Xfce probably
won't get wayland for a long time.   Right ?

I use a lot of gnome apps ( but in flatpaks ).

One of the first things I do after an install, is play FreeCell in
Aisleriot Solitaire to see if I "feel anything," as I have played this
game about 1,000 times ( maybe 10,000, LOL ! )

Anyways, I updated the packages, turned on the available 3rd party
repo, installed flathub,powered off, installed flatpak of Aisleriot,
rebooted,
just to test reboot, and then played
a game, and here I am. I installed htop ( fc32 ) and, it all looks good
from here.   I surfed the web, watched YouTube.

All is nominal and functional from that perspective.

LibreOffice preinstalled. Utility apps are already all grouped together
so that looks nice.

I am sending this email using this new install.

David Locklear
Novice Rawhide User 0.0.0.5 (  inside joke )

System:  ASUS Mini-ITX Intel i5-3470 with 16 GB of DDR3 at ~ 1,000 MHz
( approximately 5 years old, or more )
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry

2020-04-07 Thread Ed Greshko

On 2020-04-08 07:27, Cameron Simpson wrote:
> On 07Apr2020 07:07, Terry Barnaby  wrote:
>> 01 23 * * 1 root /src/bbackup/bbackup-beam
> [...]
>
> 1:23am. Do not the timezone shifts happen at 2am (avoids horrible day changes 
> if it happened at 12am). So 1:23am can happen twice if 2am steps back to 1am.
>
> Our summer time just ended here. Might a similar shift have happened for you?

Well, except that the format of the crontab is

Minute  Hour Day-of-Month .

:-)

-- 
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry

2020-04-07 Thread Cameron Simpson


On 07Apr2020 07:07, Terry Barnaby  wrote:

01 23 * * 1 root /src/bbackup/bbackup-beam

[...]

1:23am. Do not the timezone shifts happen at 2am (avoids horrible day 
changes if it happened at 12am). So 1:23am can happen twice if 2am steps 
back to 1am.


Our summer time just ended here. Might a similar shift have happened for 
you?


Cheers,
Cameron Simpson 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: remind

2020-04-07 Thread Bob Goodwin




On 2020-04-07 17:29, David A. De Graaf wrote:

What's happened to the remind and tkremind packages?

I just discovered, to my horror, they're not available in Fedora 31.
I'm going to have to contend with a lot of unhappy birthday celebrants. 

°
Just download and install from the remind web page. It works for me as 
it always  has ...


--
Bob Goodwin - Zuni, Virginia,
Fedora Linux-31 XFCE
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: remind

2020-04-07 Thread Tom Horsley

On Tue, 7 Apr 2020 17:29:15 -0400
David A. De Graaf wrote:

> I just discovered, to my horror, they're not available in Fedora 31.
> I'm going to have to contend with a lot of unhappy birthday celebrants.

I never knew they ever appeared in the repos. I've been compiling
remind from source for every new release for years (never used
tkremind). I have it pop up reminders with a silly Qt app:

https://tomhorsley.com/software/qtmess/qtmess.html
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: remind

2020-04-07 Thread Jerry James

On Tue, Apr 7, 2020 at 3:30 PM David A. De Graaf  wrote:
> What's happened to the remind and tkremind packages?

To find out what happened to packages that get retired, you can visit
a URL of the form https://src.fedoraproject.org/rpms/remind (with the
package name the final component).  In this case, it shows that the
package was orphaned for 6+ weeks; i.e., the maintainer stepped down
and nobody took over the package.

If you're interested in maintaining it, visit
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers
--
Jerry James
http://www.jamezone.org/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

remind

2020-04-07 Thread David A. De Graaf


What's happened to the remind and tkremind packages?

I just discovered, to my horror, they're not available in Fedora 31.
I'm going to have to contend with a lot of unhappy birthday celebrants.

--
David A. De GraafDATIX, Inc.Hendersonville, NC
d...@datix.us www.datix.us
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: EXTERNAL: Re: alacarte in fc32

2020-04-07 Thread Patrick Dupre

menulibre ?


> > On 4/7/20 3:08 AM, Saša Janiška wrote:
> >> Hello,
> >>
> >> what has happened with Alacarte (menu editor for GNOME) in fc32?
> >>
> >> Will it become available eventually?
> >
> > No, it was retired.
> What takes it's place?
> > ___
> > users mailing list -- users@lists.fedoraproject.org
> > To unsubscribe send an email to users-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> 
> 
> -- 
> Roger Wells, P.E.
> leidos
> 221 Third St
> Newport, RI 02840
> 401-847-4210 (voice)
> 401-849-1585 (fax)
> roger.k.we...@leidos.com
> 
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Anaconda question

2020-04-07 Thread Kevin Fenzi

On Tue, Apr 07, 2020 at 02:07:08AM -0400, David wrote:
> Once a user gets their computer running on Fedora, is there
> any reason to keep anaconda and its associated dependencies ?

Nope

> Is there any reason to delete it ?

A slight amount of disk space I suppose. 

> Is there any reason to update it everytime it updates ?

Not really. 

kevin


signature.asc
Description: PGP signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry


On 4/7/20 3:21 AM, Terry Barnaby wrote:

On 07/04/2020 09:03, Samuel Sieb wrote:

On 4/6/20 11:07 PM, Terry Barnaby wrote:
This system has been in use for 10 years or more on various Fedora 
versions. However about 18 months ago I have seen a problem where 
cron will start two backups with identical start times occasionally.


I have had to add a file lock system in the bbackup-beam to cope with 
this.


Any idea on why cron might start the same job off twice at the same 
time ? Could there be a time change issue with chronyd ?


Have you checked the logs to see when the jobs were started and if 
there are any relevant messages?

___


Yes, there is nothing unusual in /var/log/cron:

/var/log/messages


Are you not using the journal?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Custom ISO won't boot to Fedora

2020-04-07 Thread Thomas Schmitt

Hi,

i wrote:
> The resulting ISO will grow by the size of the whole ISO directory tree
> and the size of the data files which get added.

Clarification:
"size of the whole ISO directory tree" means the size of the meta-data,
not the size of the data files in the tree.
The meta-data in Fedora-Workstation-Live-x86_64-31-1.9.iso are very small,
because there are very few files in the tree.

Adding a text file of a few hundred bytes yielded a growth of 393216 bytes.

Have a nice day :)

Thomas
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: EXTERNAL: Re: alacarte in fc32

2020-04-07 Thread Jerry James

On Tue, Apr 7, 2020 at 11:32 AM Wells, Roger K. via users
 wrote:
> What takes it's place?

Possibly nothing.  It was retired due to lack of a maintainer.  If
anybody would like to bring it back, see point 4 here:
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers
-- 
Jerry James
http://www.jamezone.org/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: EXTERNAL: Re: alacarte in fc32

2020-04-07 Thread Wells, Roger K. via users

On 4/7/20 1:25 PM, Samuel Sieb wrote:
> On 4/7/20 3:08 AM, Saša Janiška wrote:
>> Hello,
>>
>> what has happened with Alacarte (menu editor for GNOME) in fc32?
>>
>> Will it become available eventually?
>
> No, it was retired.
What takes it's place?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


-- 
Roger Wells, P.E.
leidos
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.we...@leidos.com

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: LVM Merge hangs at 100%

On 4/7/20 4:58 AM, Sreyan Chakravarty wrote:

I though Fedora KDE was an official image, are you saying that its not ?

I don't see how that relates to what I said.  The official images are 
only released once for each release.  There are unofficial respins done 
for the workstation live, but only that one.  It's only 6 months between 
releases, so there's not much point doing respins for everything anyway.

On Tue, Apr 7, 2020 at 2:13 PM Samuel Sieb > wrote:

On 4/6/20 9:52 PM, Sreyan Chakravarty wrote:
 > Well I tried that it told me that I did not have enough space.
 >
 > The easiest option is use a distro which uses the updated version. I
 > have no clue why Fedora a distro that lives on the bleeding edge
does
 > not update its ISO images.

Because releasing new official images requires running the whole QA
process on them and QA is busy working on the next release.  There are
unofficial respins that are done regularly for the workstation live
image though.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Custom ISO won't boot to Fedora

2020-04-07 Thread Thomas Schmitt

Hi,

Sreyan Chakravarty wrote:
> If someone asked you to create a custom Fedora ISO that you could use in
> VirtualBox/DVD/USB, what would you do ?

(As first i'd try what you did: Build a new ISO from the mounted original.
 Then i'd try whether the original works in the test situation.
 Then i'd invest an unpredictable amount of time digging for reasons why
 my ISO does not work while the original works.)

Then i'd add the file by multi-session to a copy of the original ISO

  cp Fedora-Workstation-Live-x86_64-31-1.9.iso test.iso

  file_or_tree_on_disk="$HOME"/my_file
  path_in_iso=/my_file

  xorriso -dev test.iso \
  -boot_image any keep \
  -map "$file_or_tree_on_disk" "$path_in_iso"

(These xorriso commands are documented in man xorriso, as they are part
 of the native non-emulated command mode. See below for your question
 about the emulated options.)

Afterwards test.iso should contain the same files as the original ISO
plus the file or tree given by "$HOME"/my_file as file or tree with the
path /my_file.
The boot equipment is supposed to stay unchanged.

The resulting ISO will grow by the size of the whole ISO directory tree
and the size of the data files which get added.

Of course any distro can impose arbitrary demands on how a file in an ISO
has to be announced in some list file in the ISO, or equipped with some
crytographic signature.
A few plain data files and directories, which have no role in the official
boot process, should not demand much announcement ... i hope.

---

> But here is the problem, the ISO booted and displayed all the memory
> options. So something weird is happening there.

Yes. The weirdness is probably in ISOLINUX or (if you can navigate in the
menu) in the start-up of Linux kernel and initrd.

Did you verify that the original ISO works as expected ?

> I have mailed the guys on the ISOLINUX mailing list but I will probably not
> get a reply.

There's hardly anybody at home any more.

> What I could make out was that the
> livecd-tools for Fedora itself make use of a genisoimage like program called
> xorriso.

xorriso (where i am developer) has an emulation mode which takes many
options of program mkisofs. genisoimage is a fork of mkisofs from 2006,
beefed up by boot capabilities which Debian needed. Most of them are
available in xorriso, too.

> >   xorriso -indev "$orig" -report_el_torito plain -report_system_area plain

> I could not understand these commands at all. If its alright with you, would
> you mind adding some more details ?

The shown xorriso run is for inspection of the boot entry points of ISOs,
regardless which program made them.

We see the El Torito Catalog which PC-BIOS and EFI look up when the ISO
is presented to them on CD, DVD, or BD medium. The one of your custom
ISO will only have two entries.

Since you see the ISOLINUX menu, your test boots via catalog entry 1,
which marks the first 2048 bytes of file /isolinux/isolinux.bin. The entry
stems from mkisofs/genisoimage/xorrisofs option -b. The program determines
the block address of isolinux.bin in the ISO and writes this number into
the El Torito Catalog and into the boot-info-table inside isolinux.bin.
So isolinux.bin will get selected for being started by PC-BIOS compatible
firmware, which has no clue of ISO 9660 as filesystem.
isolinux.bin knows how to read ISO 9660 filesystems and thus can load
the menu configuration file, which it then displays.

The MBR partition table would be of interest if EFI firmware in non-legacy
mode would boot. But in this case you would see a GRUB menu, which comes
from software inside the FAT filesystem image /images/efiboot.img.
xorriso shows that this image is exposed as MBR partition of type EF, so
that EFI firmwares knows where to look for /EFI/BOOT/BOOTX64.EFI or
/EFI/BOOT/BOOTIA32.EFI.

> I could not find these options listed in the xorriso man page so I don't
> understand what you are referring to.

The man page of the mkisofs emulation is shown by

  man xorrisofs

Many of the options are compatible with mkisofs and genisoimage. Some are
special to xorriso.

Have a nice day :)

Thomas
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: alacarte in fc32


On 4/7/20 3:08 AM, Saša Janiška wrote:

Hello,

what has happened with Alacarte (menu editor for GNOME) in fc32?

Will it become available eventually?


No, it was retired.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Custom ISO won't boot to Fedora

> Hi,
> So i assume you see an ISOLINUX menu with the labels you expect from your
> isolinux.cfg file. (If not, then this would make much more sense to me,
> though.)
> 
> Since i assume that your "." directory was the mounted original ISO
> or a copy of the mounted file tree of that ISO, the difference can only
> be in the non-file data blocks of the ISO.
> 
> 
> 
> This creates boot records for booting via PC-BIOS and EFI from DVD, but
> not from USB stick or hard disk. A run of program isohybrid --uefi would
> equip the ISO by MBR code and GPT partition table which marks efiboot.img
> as EFI System Partition.

Wow, you have given me a lot of information, most of which i am having trouble 
understanding because it way too advanced.

So basically what you are saying is my image given the parameters is not 
bootable from USB, but is bootable from DVD/CD. 
But here is the problem, the ISO booted and displayed all the memory options. 
So something weird is happening there.

I have mailed the guys on the ISOLINUX mailing list but I will probably not get 
a reply. 

> Whatever it should boot from (virtual) DVD via PC-BIOS compatible firmware.
> And if you see an ISOLINUX menu, then it booted indeed.

Yeah this is the weird part.

> It is probably my software which packed up as ISO what Fedora's software
> has prepared on hard disk. In the past i encountered livecd-tools as
> producer of Fedora images.
> 
> livecd-tools uses the mkisofs emulation mode of xorriso by the link name
> "xorrisofs" in program
> 
>   https://github.com/livecd-tools/livecd-tools/blob/master/imgcreate/live.py
> 

I could not understand what all this is. What I could make out was that the 
livecd-tools for Fedora itself make use of a genisoimage like program called 
xorriso.  The documentation is so complicated I could not figure out how to use 
it.

> The xorrisofs arguments in live.py would match what can be seen in the ISO.
> The run:
> 
>   orig=Fedora-Workstation-Live-x86_64-31-1.9.iso
> 
>   xorriso -indev "$orig" -report_el_torito plain -report_system_area plain
> 
> shows that it has equipment for booting via PC-BIOS or EFI from DVD or
> from USB-stick:
> 
>   Preparer Id  : XORRISO-1.5.0 2018.09.15.133001, LIBISOBURN-1.5.0, 
> LIBISOFS-1.5.0,
> LIBBURN-1.5.0
>   ...
>   El Torito images   :   N  Pltf  B   Emul  Ld_seg  Hdpt  Ldsiz LBA
>   El Torito boot img :   1  BIOS  y   none  0x  0x00  4   16852
>   El Torito boot img :   2  UEFI  y   none  0x  0x00  21716  43
>   El Torito boot img :   3  UEFI  y   none  0x  0x00  455205472
>   El Torito img path :   1  /isolinux/isolinux.bin
>   El Torito img opts :   1  boot-info-table isohybrid-suitable
>   El Torito img path :   2  /images/efiboot.img
>   El Torito img path :   3  /images/macboot.img
>   ...
>   System area summary: MBR isohybrid cyl-align-off GPT
>   ...
>   MBR partition table:   N Status  TypeStart   Blocks
>   MBR partition  :   1   0x80  0x000  3768320
>   MBR partition  :   2   0x00  0xef  17221716
>   MBR partition  :   3   0x00  0x002188845520
>   MBR partition path :   2  /images/efiboot.img
>   MBR partition path :   3  /images/macboot.img
> 

I could not understand these commands at all. If its alright with you, would 
you mind adding some more details ?

>   -V 'Fedora-WS-Live-31-1-9'
>   --modification-date='2019102323212900'
>   -isohybrid-mbr
> --interval:local_fs:0s-15s:zero_mbrpt,zero_gpt:'Fedora-Workstation-Live-x86_64-31-1.9.iso'
>   -partition_cyl_align off
>   -partition_offset 0
>   --mbr-force-bootable
>   -iso_mbr_part_type 0x00
>   -c '/isolinux/boot.cat'
>   -b '/isolinux/isolinux.bin'
>   -no-emul-boot
>   -boot-load-size 4
>   -boot-info-table
>   -eltorito-alt-boot
>   -e '/images/efiboot.img'
>   -no-emul-boot
>   -boot-load-size 21716
>   -isohybrid-gpt-basdat
>   -eltorito-alt-boot
>   -e '/images/macboot.img'
>   -no-emul-boot
>   -boot-load-size 45520
>   -isohybrid-gpt-hfsplus

I could not find these options listed in the xorriso man page so I don't 
understand what you are referring to.

> But this all does not explain why ISOLINUX could get stuck in its menu.
> I am not an expert for bootloaders or initrds, but rather their neighbor.
> So i cannot even guess what goes wrong.
> 

The most important question I would ask you is:

If someone asked you to create a custom Fedora ISO that you could use in 
VirtualBox/DVD/USB, what would you do ? 

Please note, I mean "custom" as in it should contain some extra files that are 
not part of the stock ISO. For example, in this case it is my Kickstart file.

What would you do ?

Thanks again.

Regards,
Sreyan Chakravarty
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guide

Re: Anaconda question

2020-04-07 Thread stan via users

On Tue, 7 Apr 2020 02:07:08 -0400
David  wrote:

My opinions.

> Once a user gets their computer running on Fedora, is there
> any reason to keep anaconda and its associated dependencies ?

No.  Not anaconda as it is for installing fedora, but some of its
dependencies might be used by other programs you do want around.  As I
found below, there were no dependencies when I tried to remove it.

> 
> Is there any reason to delete it ?

No.  It doesn't take much disk, and the effort to delete it is effort.
I just tried it, and there were no dependencies, and the space saved
showed as zero.

> Is there any reason to update it everytime it updates ?

No, but in the grand scheme of updates, this is hardly noticeable.  One
firefox or office-libre update probably does for a lifetime of anaconda
updates.  If space or download bandwidth is critical for you, and you
are of Ben Franklin's persuasion, and believe a penny saved is a penny
earned, then your answer would be yes. Or, if your philosophy is 'just
take care of the pennies, and the dollars take care of themselves', you
would answer yes.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Custom ISO won't boot to Fedora

2020-04-07 Thread Thomas Schmitt

Hi,

Sreyan Chakravarty wrote here:
> Its stuck at the bootmenu.

and at sysli...@syslinux.org:
> Unfortunately when I boot and press enter nothing happens.

So i assume you see an ISOLINUX menu with the labels you expect from your
isolinux.cfg file. (If not, then this would make much more sense to me,
though.)

Since i assume that your "." directory was the mounted original ISO
or a copy of the mounted file tree of that ISO, the difference can only
be in the non-file data blocks of the ISO.

> genisoimage ... -b isolinux/isolinux.bin -c isolinux/boot.cat
> -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot
> -e images/efiboot.img -no-emul-boot

This creates boot records for booting via PC-BIOS and EFI from DVD, but
not from USB stick or hard disk. A run of program isohybrid --uefi would
equip the ISO by MBR code and GPT partition table which marks efiboot.img
as EFI System Partition.

Whatever it should boot from (virtual) DVD via PC-BIOS compatible firmware.
And if you see an ISOLINUX menu, then it booted indeed.

> If anyone knows how the official images are compiled please let me know.

It is probably my software which packed up as ISO what Fedora's software
has prepared on hard disk. In the past i encountered livecd-tools as
producer of Fedora images.

livecd-tools uses the mkisofs emulation mode of xorriso by the link name
"xorrisofs" in program

https://github.com/livecd-tools/livecd-tools/blob/master/imgcreate/live.py

The xorrisofs arguments in live.py would match what can be seen in the ISO.
The run:

orig=Fedora-Workstation-Live-x86_64-31-1.9.iso

xorriso -indev "$orig" -report_el_torito plain -report_system_area plain

shows that it has equipment for booting via PC-BIOS or EFI from DVD or
from USB-stick:

Preparer Id : XORRISO-1.5.0 2018.09.15.133001, LIBISOBURN-1.5.0,
LIBISOFS-1.5.0, LIBBURN-1.5.0
...
El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA
El Torito boot img : 1 BIOS y none 0x 0x00 4 16852
El Torito boot img : 2 UEFI y none 0x 0x00 21716 43
El Torito boot img : 3 UEFI y none 0x 0x00 455205472
El Torito img path : 1 /isolinux/isolinux.bin
El Torito img opts : 1 boot-info-table isohybrid-suitable
El Torito img path : 2 /images/efiboot.img
El Torito img path : 3 /images/macboot.img
...
System area summary: MBR isohybrid cyl-align-off GPT
...
MBR partition table: N Status TypeStart Blocks
MBR partition : 1 0x80 0x000 3768320
MBR partition : 2 0x00 0xef 17221716
MBR partition : 3 0x00 0x002188845520
MBR partition path : 2 /images/efiboot.img
MBR partition path : 3 /images/macboot.img

(Only of interest if the machine is an old Mac:
The file /images/macboot.img is advertised by El Torito and MBR partition
table, but not by an Apple Partition Map, as was done in
Fedora-Workstation-Live-x86_64-29-1.2.iso. This advertising would be
created by xorrisofs option -isohybrid-apm-hfsplus which does the same
as isohybrid's option --mac.)

Let's assume, that livecd-tools would not be the right guess and thus
could not tell the used xorrisofs arguments.
xorriso can guess the boot related options for a replaying xorrisofs run
from the ISO image:

xorriso -indev "$orig" -report_el_torito as_mkisofs

-V 'Fedora-WS-Live-31-1-9'
--modification-date='2019102323212900'
-isohybrid-mbr
--interval:local_fs:0s-15s:zero_mbrpt,zero_gpt:'Fedora-Workstation-Live-x86_64-31-1.9.iso'
-partition_cyl_align off
-partition_offset 0
--mbr-force-bootable
-iso_mbr_part_type 0x00
-c '/isolinux/boot.cat'
-b '/isolinux/isolinux.bin'
-no-emul-boot
-boot-load-size 4
-boot-info-table
-eltorito-alt-boot
-e '/images/efiboot.img'
-no-emul-boot
-boot-load-size 21716
-isohybrid-gpt-basdat
-eltorito-alt-boot
-e '/images/macboot.img'
-no-emul-boot
-boot-load-size 45520
-isohybrid-gpt-hfsplus

Some of them are automatic consequences of the others and may have been
omitted when the ISO was made:
-partition_cyl_align off
-partition_offset 0
--mbr-force-bootable
-iso_mbr_part_type 0x00

Whether
-V 'Fedora-WS-Live-31-1-9'
--modification-date='2019102323212900'
are significant depends on the software in the ISO. The isolinux.cfg
refers to the -V text. grub-mrescue refers to the date as UUID.

The option -isohybrid-mbr gets as parameter a disk file path with an
isohybrid MBR template (isohdpfx.bin) or the lengthy --interval:...
string which tells it to pick a template from the original ISO image's
start.
One could harvest it manually and submit its path as argument:

dd if=Fedora-Workstation-Live-x86_64-29-1.2.iso
bs=1 count=446 \ of=/tmp/isohdpfx.bin

xorrisofs \
...
-isohybrid-mbr /tmp/isohdpfx.bin \

Re: Virtual Box not loading vboxdrv on Clean install of Fedora 31

2020-04-07 Thread Bob Marcan

On Mon, 6 Apr 2020 16:22:20 -0300
Fernando Cassia  wrote:

> On Sat, Apr 4, 2020, 15:32 Bob Marcan  wrote:
> > Is there any particular reason you don't use KVM?
> > It is Linux native virtualization.  

> Look, we're here to make Virtualbox better. Not to encourage users to stop
> using it.
> 
> Thanks for your understanding.
> 
> FC

OK. 
Are you Oracle employee involved in development of VirtualBox? :-)

BM
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry


On 07/04/2020 13:06, Iosif Fettich wrote:

Hi Terry,


Yes, there is nothing unusual in /var/log/cron:

Apr  6 22:01:01 beam CROND[651585]: (root) CMD (run-parts 
/etc/cron.hourly)

[...]


/var/log/messages

Feb 24 23:00:03 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.214 
from 00:25:b3:e6:a9:18 via enp4s0

[...]


In the backup log:

Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn 
/data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt 
/data/backup at Mon  6 Apr 23:01:01 BST 2020

[...]

Maybe irrelevant, but just mentioning: the log extract from 
/var/log/messages is dated Feb 24, whereas the other two are dated 
Apr  6.


Best regards,

Iosif

Yes, missed that. I searched back for 23:01:00 and missed the fact that 
it was the wrong month. There was even less of interest in 
/var/log/messages around Apr  6 23:01:00, just some DHCP requests.


Terry
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Custom ISO won't boot to Fedora

If anyone knows how the official images are compiled please let me know.

On Tue, Apr 7, 2020 at 5:23 PM Sreyan Chakravarty 
wrote:

> I am unable to boot the custom ISO I have created.
>
> I have just created a Custom ISO from the Fedora Live ISO using the
> following command:
>
> genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset
> "Fedora-WS-Live-31-1-9" -A "CDLABEL=Fedora-WS-Live-31-1-9" -b
> isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size
> 4 -boot-info-table -eltorito-alt-boot -e images/efiboot.img -no-emul-boot
> -o ../Fedora_Custom.iso .
>
> But I can't for the life of me figure out why I can't get the Live ISO to
> boot. Its stuck at the bootmenu.
>
> This is the directory structure for my custom ISO:
>
> [sreyan@localhost Fedora_ISO]$ tree .
> .
> ├── anaconda-ks.cfg
> ├── EFI
> │   └── BOOT
> │   ├── BOOT.conf
> │   ├── BOOTIA32.EFI
> │   ├── BOOTX64.EFI
> │   ├── fonts
> │   │   └── unicode.pf2
> │   ├── grub.cfg
> │   ├── grubia32.efi
> │   ├── grubx64.efi
> │   ├── mmia32.efi
> │   └── mmx64.efi
> ├── images
> │   ├── efiboot.img
> │   ├── macboot.img
> │   └── pxeboot
> │   ├── initrd.img
> │   └── vmlinuz
> ├── isolinux
> │   ├── boot.cat
> │   ├── boot.msg
> │   ├── grub.conf
> │   ├── initrd.img
> │   ├── isolinux.bin
> │   ├── isolinux.cfg
> │   ├── ldlinux.c32
> │   ├── libcom32.c32
> │   ├── libutil.c32
> │   ├── memtest
> │   ├── splash.png
> │   ├── vesamenu.c32
> │   └── vmlinuz
> └── LiveOS
> └── squashfs.img
>
> 7 directories, 28 files
>
> And this is for the original:
>
> [sreyan@localhost Fedora-WS-Live-31-1-9]$ tree .
> .
> ├── EFI
> │   └── BOOT
> │   ├── BOOT.conf
> │   ├── BOOTIA32.EFI
> │   ├── BOOTX64.EFI
> │   ├── fonts
> │   │   └── unicode.pf2
> │   ├── grub.cfg
> │   ├── grubia32.efi
> │   ├── grubx64.efi
> │   ├── mmia32.efi
> │   └── mmx64.efi
> ├── images
> │   ├── efiboot.img
> │   ├── macboot.img
> │   └── pxeboot
> │   ├── initrd.img
> │   └── vmlinuz
> ├── isolinux
> │   ├── boot.cat
> │   ├── boot.msg
> │   ├── grub.conf
> │   ├── initrd.img
> │   ├── isolinux.bin
> │   ├── isolinux.cfg
> │   ├── ldlinux.c32
> │   ├── libcom32.c32
> │   ├── libutil.c32
> │   ├── memtest
> │   ├── splash.png
> │   ├── vesamenu.c32
> │   └── vmlinuz
> └── LiveOS
> └── squashfs.img
>
> 7 directories, 27 files
> --
>
> As you can see there is no difference except for the Kickstart file which
> I am not even using in isolinux.cfg
>
> This is the output of isolinux.cfg:
>
> default vesamenu.c32
> timeout 600
>
> display boot.msg
>
> # Clear the screen when exiting the menu, instead of leaving the menu
> displayed.
> # For vesamenu, this means the graphical background is still displayed
> without
> # the menu itself for as long as the screen remains in graphics mode.
> menu clear
> menu background splash.png
> menu title Fedora-Workstation-Live 31
> menu vshift 8
> menu rows 18
> menu margin 8
> #menu hidden
> menu helpmsgrow 15
> menu tabmsgrow 13
>
> # Border Area
> menu color border * # # none
>
> # Selected item
> menu color sel 0 # # none
>
> # Title bar
> menu color title 0 #ff7ba3d0 # none
>
> # Press [Tab] message
> menu color tabmsg 0 #ff3a6496 # none
>
> # Unselected menu item
> menu color unsel 0 #84b8 # none
>
> # Selected hotkey
> menu color hotsel 0 #84b8 # none
>
> # Unselected hotkey
> menu color hotkey 0 # # none
>
> # Help text
> menu color help 0 # # none
>
> # A scrollbar of some type? Not sure.
> menu color scrollbar 0 # #ff355594 none
>
> # Timeout msg
> menu color timeout 0 # # none
> menu color timeout_msg 0 # # none
>
> # Command prompt text
> menu color cmdmark 0 #84b8 # none
> menu color cmdline 0 # # none
>
> # Do not display the actual menu unless the user presses a key. All that
> is displayed is a timeout message.
>
> menu tabmsg Press Tab for full configuration options on menu items.
>
> menu separator # insert an empty line
> menu separator # insert an empty line
>
> label linux
>   menu label ^Start Fedora-Workstation-Live 31
>   kernel vmlinuz
>   append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9
>  rd.live.image quiet
>
> label check
>   menu label Test this ^media & start Fedora-Workstation-Live 31
>   menu default
>   kernel vmlinuz
>   append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9
>  rd.live.image rd.live.check quiet
>
> menu separator # insert an empty line
>
> # utilities submenu
> menu begin ^Troubleshooting
>   menu title Troubleshooting
>
> label vesa
>   menu indent count 5
>   menu label Start Fedora-Workstation-Live 31 in ^basic graphics mode
>   text help
> Try this option out if you're having trouble starting
> Fedora-Workstation-Live 31.
>   endtext
>   kernel vmlinuz
>   app

Re: Display Manager question

2020-04-07 Thread Rex Dieter

David wrote:

> Last week, I replaced the file "default.png" in my background directory,
> and was delightfully enjoying a new custom backsplash, instead of the new
> fancy
> one that Fedora has ( light color blue with some rectangular glass cluster
> ).
> 
> In my recent update yesterday, something replaced my custom backsplash
> with the old default.png.
> 
> Why would an update do that ?

The package that owns that file was updated.

-- Rex
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry


Hi Terry,


Yes, there is nothing unusual in /var/log/cron:

Apr  6 22:01:01 beam CROND[651585]: (root) CMD (run-parts /etc/cron.hourly)

[...]


/var/log/messages

Feb 24 23:00:03 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.214 from 
00:25:b3:e6:a9:18 via enp4s0

[...]


In the backup log:

Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn /data/www 
/data/vwt /data/www /data1/kvm /data/database /data/vwt /data/backup at Mon  6 
Apr 23:01:01 BST 2020

[...]

Maybe irrelevant, but just mentioning: the log extract from 
/var/log/messages is dated Feb 24, whereas the other two are dated Apr  6.


Best regards,

Iosif___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: LVM Merge hangs at 100%

I though Fedora KDE was an official image, are you saying that its not ?

On Tue, Apr 7, 2020 at 2:13 PM Samuel Sieb  wrote:

> On 4/6/20 9:52 PM, Sreyan Chakravarty wrote:
> > Well I tried that it told me that I did not have enough space.
> >
> > The easiest option is use a distro which uses the updated version. I
> > have no clue why Fedora a distro that lives on the bleeding edge does
> > not update its ISO images.
>
> Because releasing new official images requires running the whole QA
> process on them and QA is busy working on the next release.  There are
> unofficial respins that are done regularly for the workstation live
> image though.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
>


-- 
Regards,
Sreyan Chakravarty
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Custom ISO won't boot to Fedora

I am unable to boot the custom ISO I have created.

I have just created a Custom ISO from the Fedora Live ISO using the
following command:

genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset
"Fedora-WS-Live-31-1-9" -A "CDLABEL=Fedora-WS-Live-31-1-9" -b
isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4
-boot-info-table -eltorito-alt-boot -e images/efiboot.img -no-emul-boot -o
../Fedora_Custom.iso .

But I can't for the life of me figure out why I can't get the Live ISO to
boot. Its stuck at the bootmenu.

This is the directory structure for my custom ISO:

[sreyan@localhost Fedora_ISO]$ tree .
.
├── anaconda-ks.cfg
├── EFI
│   └── BOOT
│   ├── BOOT.conf
│   ├── BOOTIA32.EFI
│   ├── BOOTX64.EFI
│   ├── fonts
│   │   └── unicode.pf2
│   ├── grub.cfg
│   ├── grubia32.efi
│   ├── grubx64.efi
│   ├── mmia32.efi
│   └── mmx64.efi
├── images
│   ├── efiboot.img
│   ├── macboot.img
│   └── pxeboot
│   ├── initrd.img
│   └── vmlinuz
├── isolinux
│   ├── boot.cat
│   ├── boot.msg
│   ├── grub.conf
│   ├── initrd.img
│   ├── isolinux.bin
│   ├── isolinux.cfg
│   ├── ldlinux.c32
│   ├── libcom32.c32
│   ├── libutil.c32
│   ├── memtest
│   ├── splash.png
│   ├── vesamenu.c32
│   └── vmlinuz
└── LiveOS
└── squashfs.img

7 directories, 28 files

And this is for the original:

[sreyan@localhost Fedora-WS-Live-31-1-9]$ tree .
.
├── EFI
│   └── BOOT
│   ├── BOOT.conf
│   ├── BOOTIA32.EFI
│   ├── BOOTX64.EFI
│   ├── fonts
│   │   └── unicode.pf2
│   ├── grub.cfg
│   ├── grubia32.efi
│   ├── grubx64.efi
│   ├── mmia32.efi
│   └── mmx64.efi
├── images
│   ├── efiboot.img
│   ├── macboot.img
│   └── pxeboot
│   ├── initrd.img
│   └── vmlinuz
├── isolinux
│   ├── boot.cat
│   ├── boot.msg
│   ├── grub.conf
│   ├── initrd.img
│   ├── isolinux.bin
│   ├── isolinux.cfg
│   ├── ldlinux.c32
│   ├── libcom32.c32
│   ├── libutil.c32
│   ├── memtest
│   ├── splash.png
│   ├── vesamenu.c32
│   └── vmlinuz
└── LiveOS
└── squashfs.img

7 directories, 27 files
-- 

As you can see there is no difference except for the Kickstart file which I
am not even using in isolinux.cfg

This is the output of isolinux.cfg:

default vesamenu.c32
timeout 600

display boot.msg

# Clear the screen when exiting the menu, instead of leaving the menu
displayed.
# For vesamenu, this means the graphical background is still displayed
without
# the menu itself for as long as the screen remains in graphics mode.
menu clear
menu background splash.png
menu title Fedora-Workstation-Live 31
menu vshift 8
menu rows 18
menu margin 8
#menu hidden
menu helpmsgrow 15
menu tabmsgrow 13

# Border Area
menu color border * # # none

# Selected item
menu color sel 0 # # none

# Title bar
menu color title 0 #ff7ba3d0 # none

# Press [Tab] message
menu color tabmsg 0 #ff3a6496 # none

# Unselected menu item
menu color unsel 0 #84b8 # none

# Selected hotkey
menu color hotsel 0 #84b8 # none

# Unselected hotkey
menu color hotkey 0 # # none

# Help text
menu color help 0 # # none

# A scrollbar of some type? Not sure.
menu color scrollbar 0 # #ff355594 none

# Timeout msg
menu color timeout 0 # # none
menu color timeout_msg 0 # # none

# Command prompt text
menu color cmdmark 0 #84b8 # none
menu color cmdline 0 # # none

# Do not display the actual menu unless the user presses a key. All that is
displayed is a timeout message.

menu tabmsg Press Tab for full configuration options on menu items.

menu separator # insert an empty line
menu separator # insert an empty line

label linux
  menu label ^Start Fedora-Workstation-Live 31
  kernel vmlinuz
  append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9
 rd.live.image quiet

label check
  menu label Test this ^media & start Fedora-Workstation-Live 31
  menu default
  kernel vmlinuz
  append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9
 rd.live.image rd.live.check quiet

menu separator # insert an empty line

# utilities submenu
menu begin ^Troubleshooting
  menu title Troubleshooting

label vesa
  menu indent count 5
  menu label Start Fedora-Workstation-Live 31 in ^basic graphics mode
  text help
Try this option out if you're having trouble starting
Fedora-Workstation-Live 31.
  endtext
  kernel vmlinuz
  append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9
 rd.live.image nomodeset quiet

label memtest
  menu label Run a ^memory test
  text help
If your system is having issues, a problem with your
system's memory may be the cause. Use this utility to
see if the memory is working correctly.
  endtext
  kernel memtest

menu separator # insert an empty line

label local
  menu label Boot from ^local drive
  localboot 0x

menu separator # insert an empty line
men

Re: Cron sometimes starts two jobs from the same crontab entry


Hi Terry,

The bbackup-beam shell script is pretty basic and I can't see how this could 
have an issue like this.


Googling on similar issues finds some hits where the cause were two 
running cron daemons, e.g. 
https://stackoverflow.com/questions/1004764/why-is-this-cron-entry-executed-twice


I tend to believe it's not the cron entry by itself, but something n the 
environment.


I'm curious what you'll find.

Best rergards,

Iosif
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry


Hi Terry,


 I have assumed the system time is always UTC synchronised using chronyd. The
 servers user code is running under the GMT timezone. I was wondering if the
 tweaking of the time by chronyd could cause this issue, but I would have
 thought this situation would have been handled by crond if this could happen
 and I have seen this issue about 4 times in a year, so it is not a totally
 sporadic event.


grep-ing my /var/log/messages brings up entries like

Apr  5 08:16:43 localhost chronyd[900]: System clock wrong by 1.516625 seconds, 
adjustment started
Apr  5 08:16:43 localhost chronyd[900]: System clock was stepped by 1.516625 
seconds

Maybe you have some similar adjustements or bigger on the system?

One second off hitting exactly the moment your crontab scripts start could be 
an explanation to 'double starts', although it seems rather improbable to have 
that happen that often.


If you still have some logs around from the last time it happened, maybe you 
can check if there is a connection between such adjustemnts and the 
double-starters.


Otherwise, checking if such adjustements are happening often per day or just 
once in weeks might be a next step to do in order to track down the issue.


Best regards,

Iosif

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry


On 07/04/2020 09:03, Samuel Sieb wrote:

On 4/6/20 11:07 PM, Terry Barnaby wrote:
This system has been in use for 10 years or more on various Fedora 
versions. However about 18 months ago I have seen a problem where 
cron will start two backups with identical start times occasionally.


I have had to add a file lock system in the bbackup-beam to cope with 
this.


Any idea on why cron might start the same job off twice at the same 
time ? Could there be a time change issue with chronyd ?


Have you checked the logs to see when the jobs were started and if 
there are any relevant messages?

___


Yes, there is nothing unusual in /var/log/cron:

Apr  6 22:01:01 beam CROND[651585]: (root) CMD (run-parts /etc/cron.hourly)
Apr  6 22:01:01 beam run-parts[651585]: (/etc/cron.hourly) starting 0anacron
Apr  6 22:01:01 beam run-parts[651585]: (/etc/cron.hourly) finished 0anacron
Apr  6 23:01:01 beam CROND[652722]: (root) CMD (/src/bbackup/bbackup-beam)
Apr  6 23:01:01 beam CROND[652721]: (root) CMD (run-parts /etc/cron.hourly)
Apr  6 23:01:01 beam run-parts[652721]: (/etc/cron.hourly) starting 0anacron
Apr  6 23:01:01 beam CROND[652720]: (root) CMDOUT (Waking up 
70:85:c2:0f:68:07...)

Apr  6 23:01:01 beam run-parts[652721]: (/etc/cron.hourly) finished 0anacron
Apr  6 23:01:21 beam CROND[652720]: (root) CMDOUT (Starting Backup)

I do note that /etc/cron.hourly is performed at a minute past the hour 
as well though ...


/var/log/messages

Feb 24 23:00:03 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.214 from 
00:25:b3:e6:a9:18 via enp4s0
Feb 24 23:00:03 beam dhcpd[1743]: DHCPACK on 192.168.201.214 to 
00:25:b3:e6:a9:18 via enp4s0

Feb 24 23:00:05 beam systemd[1]: Starting system activity accounting tool...
Feb 24 23:00:05 beam systemd[1]: sysstat-collect.service: Succeeded.
Feb 24 23:00:05 beam systemd[1]: Started system activity accounting tool.
Feb 24 23:00:05 beam audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=sysstat-collect comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 23:00:05 beam audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=sysstat-collect comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 23:00:41 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.241 from 
70:85:c2:0f:68:07 via enp4s0
Feb 24 23:00:41 beam dhcpd[1743]: DHCPACK on 192.168.201.241 to 
70:85:c2:0f:68:07 via enp4s0
Feb 24 23:00:59 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.26 from 
84:1b:5e:70:2a:c9 via enp4s0
Feb 24 23:00:59 beam dhcpd[1743]: DHCPACK on 192.168.201.26 to 
84:1b:5e:70:2a:c9 via enp4s0
Feb 24 23:01:01 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.250 from 
4c:60:de:e4:29:2d via enp4s0
Feb 24 23:01:01 beam dhcpd[1743]: DHCPACK on 192.168.201.250 to 
4c:60:de:e4:29:2d via enp4s0
Feb 24 23:01:20 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.28 from 
00:50:c2:e2:f0:db via enp4s0
Feb 24 23:01:20 beam dhcpd[1743]: DHCPACK on 192.168.201.28 to 
00:50:c2:e2:f0:db via enp4s0
Feb 24 23:01:32 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.8 from 
00:d8:61:a0:a4:06 via enp4s0
Feb 24 23:01:32 beam dhcpd[1743]: DHCPACK on 192.168.201.8 to 
00:d8:61:a0:a4:06 via enp4s0
Feb 24 23:02:21 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.214 from 
00:25:b3:e6:a9:18 via enp4s0
Feb 24 23:02:21 beam dhcpd[1743]: DHCPACK on 192.168.201.214 to 
00:25:b3:e6:a9:18 via enp4s0
Feb 24 23:03:10 beam dhcpd[1743]: DHCPREQUEST for 192.168.201.241 from 
70:85:c2:0f:68:07 via enp4s0


In the backup log:

Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn 
/data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt 
/data/backup at Mon  6 Apr 23:01:01 BST 2020
Bbackup / /usr/beam /home /src /srcOld /dist /opt /scratch /data/svn 
/data/www /data/vwt /data/www /data1/kvm /data/database /data/vwt 
/data/backup at Mon  6 Apr 23:01:01 BST 2020

Backup aborted as locked by another backup
Bbackup completed status: 0 at Tue  7 Apr 11:12:00 BST 2020

The bbackup-beam shell script is pretty basic and I can't see how this 
could have an issue like this.


The same system has been running since 2009 without any issues. This 
problem started happening around Fedora27 or perhaps Fedora29 I think.


Terry
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

alacarte in fc32

2020-04-07 Thread Saša Janiška

Hello,

what has happened with Alacarte (menu editor for GNOME) in fc32?

Will it become available eventually?


Sincerely,
Gour

-- 
As a blazing fire turns firewood to ashes, O Arjuna, so does the
fire of knowledge burn to ashes all reactions to material activities.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry


On 07/04/2020 09:25, Iosif Fettich wrote:

Hi,


On 2020-04-07 14:07, Terry Barnaby wrote:
I have a simple backup system that starts off a backup once per 
night during the weekdays. There is a crontab file in /etc/cron.d 
with the following entries:


 


# Beam Bbackup cron setup   Backup to ...
 


#
# Min Hour Day Month WeekDay

# Perform incremental backup to every work day
01 23 * * 1 root /src/bbackup/bbackup-beam
01 23 * * 2 root /src/bbackup/bbackup-beam
01 23 * * 3 root /src/bbackup/bbackup-beam
01 23 * * 4 root /src/bbackup/bbackup-beam
01 23 * * 5 root /src/bbackup/bbackup-beam

This system has been in use for 10 years or more on various Fedora 
versions. However about 18 months ago I have seen a problem where 
cron will start two backups with identical start times occasionally.


I have had to add a file lock system in the bbackup-beam to cope 
with this.


Any idea on why cron might start the same job off twice at the same 
time ? Could there be a time change issue with chronyd ?


Are you sure that the jobs you saw started *twice*...?

If one of the jobs would not finish till next launch time, maybe just 
hanging around due to some error, you'll end up with multiple jobs out 
there, despite the fact that they started days apart.


Another possible issue might be the daylight saving time. If you're 
using a non-UTC timezone, there are datetimes that repeat or that are 
missing. 23:01 seems not to be among them, but what do I know...


Same thing might happen if there are periodical bigger time 
adjustements (NTP, manual, ...).


If it happens more than once that the system time is 23:01, launching 
the script each time is not only legit, but actually mandatory.


Best regards,

Iosif Fettich

I am pretty sure two jobs are started at the same time. The backup 
script. that is run. writes some logging text to a log file with the 
datetime it started. I see two entries with the same datetime and 
without the file lock the backups get messed up due to two operating at 
once. This "fault" has happened about 4 times in the last year.


I have assumed the system time is always UTC synchronised using chronyd. 
The servers user code is running under the GMT timezone. I was wondering 
if the tweaking of the time by chronyd could cause this issue, but I 
would have thought this situation would have been handled by crond if 
this could happen and I have seen this issue about 4 times in a year, so 
it is not a totally sporadic event.


Terry

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: LVM Merge hangs at 100%


On 4/6/20 9:52 PM, Sreyan Chakravarty wrote:

Well I tried that it told me that I did not have enough space.

The easiest option is use a distro which uses the updated version. I 
have no clue why Fedora a distro that lives on the bleeding edge does 
not update its ISO images.


Because releasing new official images requires running the whole QA 
process on them and QA is busy working on the next release.  There are 
unofficial respins that are done regularly for the workstation live 
image though.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry


Hi,


On 2020-04-07 14:07, Terry Barnaby wrote:

I have a simple backup system that starts off a backup once per night during 
the weekdays. There is a crontab file in /etc/cron.d with the following entries:


# Beam Bbackup cron setup   Backup to ...

#
# Min Hour Day Month WeekDay

# Perform incremental backup to every work day
01 23 * * 1 root /src/bbackup/bbackup-beam
01 23 * * 2 root /src/bbackup/bbackup-beam
01 23 * * 3 root /src/bbackup/bbackup-beam
01 23 * * 4 root /src/bbackup/bbackup-beam
01 23 * * 5 root /src/bbackup/bbackup-beam

This system has been in use for 10 years or more on various Fedora versions. 
However about 18 months ago I have seen a problem where cron will start two 
backups with identical start times occasionally.

I have had to add a file lock system in the bbackup-beam to cope with this.

Any idea on why cron might start the same job off twice at the same time ? 
Could there be a time change issue with chronyd ?


Are you sure that the jobs you saw started *twice*...?

If one of the jobs would not finish till next launch time, maybe just 
hanging around due to some error, you'll end up with multiple jobs out 
there, despite the fact that they started days apart.


Another possible issue might be the daylight saving time. If you're using 
a non-UTC timezone, there are datetimes that repeat or that are missing. 
23:01 seems not to be among them, but what do I know...


Same thing might happen if there are periodical bigger time adjustements 
(NTP, manual, ...).


If it happens more than once that the system time is 23:01, launching the 
script each time is not only legit, but actually mandatory.


Best regards,

Iosif Fettich___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry


On 4/6/20 11:07 PM, Terry Barnaby wrote:
This system has been in use for 10 years or more on various Fedora 
versions. However about 18 months ago I have seen a problem where cron 
will start two backups with identical start times occasionally.


I have had to add a file lock system in the bbackup-beam to cope with this.

Any idea on why cron might start the same job off twice at the same time 
? Could there be a time change issue with chronyd ?


Have you checked the logs to see when the jobs were started and if there 
are any relevant messages?

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: Cron sometimes starts two jobs from the same crontab entry