On 7/4/24 6:14 PM, Tide Ka via users wrote:
On 7/5/24 08:58, Samuel Sieb wrote:
The writing is finished when dd exits, but the drive might keep
flashing briefly after that. Or maybe the drive has some internal
caching that it doesn't advertise (that would be very bad).
Won't there be any
On 7/5/24 08:58, Samuel Sieb wrote:
The writing is finished when dd exits, but the drive might keep flashing
briefly after that. Or maybe the drive has some internal caching that
it doesn't advertise (that would be very bad).
Won't there be any kernel cache, so `sync` command is their for
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable to ignore the windows partition)
That (dual-boot) is based upon anaconda's behaviour. Basically it is
about telling
On 7/4/24 2:16 PM, Tim via users wrote:
You know, I'd like to try installing Fedora 40 (MATE spin), but found
it almost impossible. The downloaded ISO couldn't be booted, whether
DD'd to a flashdrive, or burnt to a DVD. The UEFI motherboard is
ASRock B250M Pro4 (circa 2018), not running in any
On 7/4/24 16:30, Mike Wright wrote:
--> EFI EXPLAINED <--
I just found this collection of pages about EFI. If you learn all of
this you will know more about EFI than all but a miniscule percentage of
humanity.
https://www.rodsbooks.com/efi-bootloaders/index.html
--
Hi,
On Thu, Jul 4, 2024 at 7:36 PM Tim via users
wrote:
> Tim:
> >> Why are you trying to write log files into your homespace?
>
> Alex:
> > It's a legacy system (think webalizer era), but there are also
> > multiple virtual hosts and it makes it easier to keep them segmented.
> > The document
Tim:
>> Why are you trying to write log files into your homespace?
Alex:
> It's a legacy system (think webalizer era), but there are also
> multiple virtual hosts and it makes it easier to keep them segmented.
> The document root is in /home/httpd/www.mysite.com/html.
>
> There's not enough
On 7/4/24 11:37, Tim via users wrote:
If you install other OSs, they should do something similar. You'd have
something like:
... EFI/debian
... EFI/fedora
Which should keep all the OSs separate from each other.
If you wanted dual booting different versions of Fedora, without one
>
>
> > I've just upgraded from fedora38 to fedora39 and directly to fedora40
> > and now apache won't start:
> >
> > (30)Read-only file system: AH00091: httpd: could not open error log
> > file /home/httpd/www.mysite.com/logs/error_log.
> > AH00015: Unable to open logs
> >
> > It has something to
On Thu, 2024-07-04 at 16:31 -0400, Alex wrote:
> I've just upgraded from fedora38 to fedora39 and directly to fedora40
> and now apache won't start:
>
> (30)Read-only file system: AH00091: httpd: could not open error log
> file /home/httpd/www.mysite.com/logs/error_log.
> AH00015: Unable to open
On Thu, Jul 4, 2024 at 4:48 PM Alex wrote:
>
> I've just upgraded from fedora38 to fedora39 and directly to fedora40 and now
> apache won't start:
>
> (30)Read-only file system: AH00091: httpd: could not open error log file
> /home/httpd/www.mysite.com/logs/error_log.
> AH00015: Unable to open
On 7/4/24 2:25 PM, Tim via users wrote:
And for what it's worth, on the newly installed Fedora 40 (after a
fight and half), it's not mounted on /boot/efi, but inside it (like my
CentOS example did).
i.e. /boot/efi/EFI/fedora
That's a clean install, so it does that itself.
We could have
Tim:
> > EFI is its own partition, that will be mounted inside /boot when Linux
> > boots. I'm not actually sure why that decision was made, I don't see
> > why we couldn't have just had /EFI. I suppose someone wanted to hide
> > all the boot things in /boot. On this PC, it's wierdly nested, so
I succeeded in the end, but this is a story about an annoying amount of
pain that shouldn't have been necessary...
You know, I'd like to try installing Fedora 40 (MATE spin), but found
it almost impossible. The downloaded ISO couldn't be booted, whether
DD'd to a flashdrive, or burnt to a
I wouldn't focus on filesystem, but on selinux.
Jul 4, 2024 22:32:47 Alex :
> Hi,
>
> I've just upgraded from fedora38 to fedora39 and directly to fedora40 and now
> apache won't start:
>
> (30)Read-only file system: AH00091: httpd: could not open error log file
>
On 7/4/24 11:37 AM, Tim via users wrote:
EFI is its own partition, that will be mounted inside /boot when Linux
boots. I'm not actually sure why that decision was made, I don't see
why we couldn't have just had /EFI. I suppose someone wanted to hide
all the boot things in /boot. On this PC,
Hi,
I've just upgraded from fedora38 to fedora39 and directly to fedora40 and
now apache won't start:
(30)Read-only file system: AH00091: httpd: could not open error log file
/home/httpd/www.mysite.com/logs/error_log.
AH00015: Unable to open logs
It has something to do with /home, as it seems
On 6/28/24 11:25 AM, Jeffrey Walton wrote:
Another one to avoid: cheap SSDs with duplicate serial numbers. Some
manufacturers repeat (clone?) serial numbers, and when you try to use
them in a RAID configuration, things go badly. A fellow on a Ubuntu
list struggled for months because of it.
On 6/26/24 2:45 PM, richard emberson wrote:
With fedora 6.8.8-300.fc40.x86_64 thunderbird packaged contained
/bin/thunderbird-wayland.
With fedora 6.9.5-200.fc40.x86_64 the thunderbird package 115.12.1 does
not contain /bin/thunderbird-wayland
dnf search thunderbird
===
Mike Wright:
> > I *think* that there can be only one /boot/efi partition on a disk.
François Patte:
> So how can we proceed when you want a dual (fedora/fedora,
> fedora/debian, fedora.ubuntu) boot on the same disk?
The idea is there is just one boot/efi on a system (even if you have
On 7/4/24 09:29, François Patte wrote:
Le 2024-07-04 18:18, Mike Wright a écrit :
On 7/4/24 09:09, François Patte wrote:
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable
Le 2024-07-04 18:18, Mike Wright a écrit :
On 7/4/24 09:09, François Patte wrote:
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable to ignore the windows partition)
I
On 7/4/24 09:09, François Patte wrote:
Should I understand that if you have a windows installation on a disk
with some (big) space left, you cannot install f40 as a dual boot
system? (because anaconda is unable to ignore the windows partition)
I *think* that there can be only one /boot/efi
Le 2024-07-04 16:51, Tide Ka via users a écrit :
Hello:
1-It seems (for me) that anaconda takes into accompt the sd[ab]1,2
partitions and does not accept the BIOS boot config and I can't say to
anaconda to ignore these partitions: it rejects /boot (because not
/boot/efi) and rejects /
Hello:
1-It seems (for me) that anaconda takes into accompt the sd[ab]1,2
partitions and does not accept the BIOS boot config and I can't say to
anaconda to ignore these partitions: it rejects /boot (because not
/boot/efi) and rejects / because lvm on RAID1 array.
For this question I think
Hi Viktor,
thanks a lot for testing and finding that. I did not catch that.
Thanks for the support. I will try to use the recreated instance.
Kind regards,
Ralf
Am Do., 4. Juli 2024 um 14:08 Uhr schrieb Viktor Ashirov <
vashi...@redhat.com>:
> Hi Ralf,
>
>
> On Thu, Jul 4, 2024 at 1:43 PM Ralf
Bonjour,
I am stuck trying to installe f40 on my computer.
I have 4 disks, 2 SSD and 2 HDD.
On the SSDs run a fedora 36 install *which I want to keep untill the f40
will be installed and configured.*
On the SSDs 2 partitions:
1) sda1 sdb1, 1Gb RAID1 array as /boot for the f36 install
2)
Hi Ralf,
On Thu, Jul 4, 2024 at 1:43 PM Ralf Spenneberg
wrote:
> I will recreate the instance. Meanwhile here is the log
>
I don't see errors in your log.
I tried to reproduce your issue by copying /etc/dirsrv and
/var/lib/dirsrv/slapd-localhost from EL7 to EL9 and on startup I see in the
Ok. Recreating the instance apparently solves the problem. And the hash
migration works as well.
Thanks a lot.
Am Do., 4. Juli 2024 um 13:43 Uhr schrieb Ralf Spenneberg <
rspenneb...@gmail.com>:
> I will recreate the instance. Meanwhile here is the log
>
> Kind regards,
> Ralf
>
>
> Am Do., 4.
I will recreate the instance. Meanwhile here is the log
Kind regards,
Ralf
Am Do., 4. Juli 2024 um 13:24 Uhr schrieb Viktor Ashirov <
vashi...@redhat.com>:
> Hi Ralf,
>
> On Thu, Jul 4, 2024 at 12:54 PM Ralf Spenneberg
> wrote:
>
>> Hi Viktor,
>>
>> I do not see any errors. I attached the log
Hi Ralf,
On Thu, Jul 4, 2024 at 12:54 PM Ralf Spenneberg
wrote:
> Hi Viktor,
>
> I do not see any errors. I attached the log but nothing stands out to me.
>
I don't see the log attached, could you please send it again?
>
> It was not a fresh instance but the migrated instance.
>
> Then I
On 7/4/24 12:54, Ralf Spenneberg wrote:
Hi Viktor,
I do not see any errors. I attached the log but nothing stands out to me.
It was not a fresh instance but the migrated instance.
Then I removed the database:
dsconf -D "cn=Directory Manager" -W ldap://localhost backend delete
spenneberg_net
Hi Viktor,
I do not see any errors. I attached the log but nothing stands out to me.
It was not a fresh instance but the migrated instance.
Then I removed the database:
dsconf -D "cn=Directory Manager" -W ldap://localhost backend delete
spenneberg_net --do-it
Deleting Backend
Hi Ralf,
On Thu, Jul 4, 2024 at 11:29 AM Ralf Spenneberg
wrote:
> Hi Viktor,
> thanks a lot for the suggestion.
> So I did an export of the old tree running on 1.3.11 using db2dif:
> db2ldif -s "dc=xxx,dc=net" -a /tmp/userRoot.ldif
> And I did an import in the new tree running on 2.4:
>
Is it
Hi Viktor,
thanks a lot for the suggestion.
So I did an export of the old tree running on 1.3.11 using db2dif:
db2ldif -s "dc=xxx,dc=net" -a /tmp/userRoot.ldif
And I did an import in the new tree running on 2.4:
dsconf -D "cn=Directory Manager" -W ldap://localhost backend import
dc=...,dc=net
> On 3 Jul 2024, at 21:47, Tim Evans wrote:
>
> DNS is the auto-gobbledegook F40 uses, which point the system to itself.
The resolv.conf file is created on each boot.
Configure how dns works with the /etc/systemd/resolve.conf and networkmanager
to ignore the search from dhcp. Then it will
36 matches
Mail list logo
