>
> On Sat, 01 Jun 2024 20:35:35 +0200 Patrick Dupre via users wrote:
>
> > Should I run
> > grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
> > and not
> > grub2-mkconfig -o /boot/grub2/grub.cfg.
> > ?
>
> No: since a few fedora versions, /boot/efi/EFI/fedora/grub.cfg
> simply redirect to /boot/g
Patrick Dupre via users writes:
Hello,
To update a system installed on a specific partition that way?
(after dnf update --refresh)
mount /dev/sdx /mnt/linux
chroot /mnt/linux
dnf system-upgrade download --releasever=40
A bunch of other stuff will likely need to be mounted.
Pretty much
On Sat, 01 Jun 2024 20:35:35 +0200 Patrick Dupre via users wrote:
> Should I run
> grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
> and not
> grub2-mkconfig -o /boot/grub2/grub.cfg.
> ?
No: since a few fedora versions, /boot/efi/EFI/fedora/grub.cfg
simply redirect to /boot/grub2/grub.cfg.
Can y
Should I run
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
and not
grub2-mkconfig -o /boot/grub2/grub.cfg.
?
> To: users@lists.fedoraproject.org
> Cc: "Community support for Fedora users" ,
> "Patrick Dupre"
> Subject: Re: chroot
>
> Currently I am hes
On Sat, 01 Jun 2024 14:16:41 -0400 Go Canes wrote:
> On Sat, Jun 1, 2024 at 2:02 PM wrote:
>> On Sat, 01 Jun 2024 13:12:49 -0400 Go Canes wrote:
>> > dnf has "--installroot=". Requires absolute path. No idea if
>> > it works with system-upgrade.
>> I don't see this option in its man page, but
Currently I am hesitating to do chroot
The point is the following
running
grub2-mkconfig
I get
Found Fedora Linux 38 (Thirty Eight) on /dev/sdc4
but
efibootmgr
does not the distribution
and
grub2 does not show it
In addition at boot EFI does not offer me the option to boot to this sdc4
On Sat, 01 Jun 2024 20:02:09 +0200 francis.montag...@inria.fr wrote:
> On Sat, 01 Jun 2024 13:12:49 -0400 Go Canes wrote:
>> On Sat, Jun 1, 2024 at 11:34 AM Patrick Dupre via users
>> wrote:
>>> To update a system installed on a specific partition that way?
>>> mount /dev/sdx /mnt/linux
Beware,
On Sat, Jun 1, 2024 at 2:02 PM wrote:
> On Sat, 01 Jun 2024 13:12:49 -0400 Go Canes wrote:
> > dnf has "--installroot=". Requires absolute path. No idea if
> > it works with system-upgrade.
>
> I don't see this option in its man page, but since the goal if not to
> upgrade the current system, b
Hi.
On Sat, 01 Jun 2024 13:12:49 -0400 Go Canes wrote:
> On Sat, Jun 1, 2024 at 11:34 AM Patrick Dupre via users
> wrote:
>> To update a system installed on a specific partition that way?
>> (after dnf update --refresh)
>> mount /dev/sdx /mnt/linux
>> chroot /m
On Sat, Jun 1, 2024 at 11:34 AM Patrick Dupre via users
wrote:
> To update a system installed on a specific partition that way?
> (after dnf update --refresh)
> mount /dev/sdx /mnt/linux
> chroot /mnt/linux
> dnf system-upgrade download --releasever=40
dnf has "--inst
you need to add these mounts to allow full function under a rescue
boot+mnt+chroot.
mount -o bind /proc /mnt/linux/proc
mount -o bind /sys /mnt/linux/sys
mount -o bind /dev /mnt/linux/dev
mount -o bind /dev/pts /mnt/linux/dev/pts
Typed from memory. I have done way too many live cd rescue boots
On Sat, 1 Jun 2024 17:33:19 +0200
Patrick Dupre via users wrote:
> Hello,
>
> To update a system installed on a specific partition that way?
> (after dnf update --refresh)
> mount /dev/sdx /mnt/linux
> chroot /mnt/linux
> dnf system-upgrade download --releasever=40
I wo
Hello,
To update a system installed on a specific partition that way?
(after dnf update --refresh)
mount /dev/sdx /mnt/linux
chroot /mnt/linux
dnf system-upgrade download --releasever=40
Thanks
===
Patrick DUPRÉ
orian Rosse.
From: Dorian ROSSE
Sent: Wednesday, June 21, 2023 10:21:57 AM
To: Community support for Fedora users
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the b
ROSSE.
From: Dorian ROSSE
Sent: Tuesday, June 20, 2023 11:50:38 AM
To: Community support for Fedora users
Subject: RE: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the button
star
Hello ever
__
De : Dorian ROSSE
Envoyé : lundi 5 juin 2023 17:39
À : Community support for Fedora users
Objet : Re: blkid fully broken too chroot has losen sense in addition fstab has
received an update not smart and luckily locate works with type the button star
Dear Eyal,
After have tried mount without option
users@lists.fedoraproject.org
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the button
star
Hi Dorian,
On 05/06/2023 18.39, Dorian ROSSE wrote:
> Hello everybody and the team fedora,
>
>
-
*From:* Dorian ROSSE
*Sent:* Friday, June 2, 2023 9:18:54 AM
*To:* Community support for Fedora users
*Subject:* Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works w
r@localhost-live ~]$ sudo mount -o /dev/sda5 /boot/efi
mount: /boot/efi: impossible de trouver UUID=9a71295a.
have an interesting week,
regards.
Dorian Rosse.
From: Dorian ROSSE
Sent: Friday, June 2, 2023 9:18:54 AM
To: Community support for Fedora users
S
Rosse.
From: Dorian ROSSE
Sent: Tuesday, May 30, 2023 1:40:17 PM
To: Community support for Fedora users
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has received an update not smart and luckily locate works with type the button
star
Hello everybody and the
Hello everybody and the team fedora,
chroot has gotten little sense in addition but get the error regular /bin/bash
no such files or directory also because with RPM find two programs can't be
found i have tried with dnf install but curl get error six can't resolve host
fedora howeve
Hello everybody and the team fedora,
This steps chroot is backed about the problems of sense although i have
installed successfully the dependancies asked by the line of command below this
explaining in addition below i type the happening of shell of the problems of
chroot so i success this
Hello everybody and the team fedora,
This steps chroot has gotten sense but unfortunately now i can't download from
RPM find because wget doesn't understand the host so i need that because chroot
is broken about the Bash in /bin/bash who need many depandencies too blkid is
again
I don't care about your story so i am here for the IT
Dorian Rosse.
From: John Pilkington
Sent: Thursday, May 18, 2023 10:40:08 PM
To: users@lists.fedoraproject.org
Subject: Re: blkid fully broken too chroot has losen sense in addition fstab
has receiv
On 18/05/2023 20:49, Mike Wright wrote:
On 5/18/23 05:21, Dorian ROSSE wrote:
Hello everybody and the team fedora,
blkid fully broken too chroot has losen sense in addition fstab has
received an update not smart so it has losen a lot of part and luckily
locate works without type the button
On 5/18/23 05:21, Dorian ROSSE wrote:
Hello everybody and the team fedora,
blkid fully broken too chroot has losen sense in addition fstab has received an
update not smart so it has losen a lot of part and luckily locate works without
type the button star finally thanks you in advance to
Dorian ROSSE composed on 2023-05-18 12:21 (UTC):
> blkid fully broken too chroot has losen sense in addition fstab has received
> an update not smart so it has losen a lot of part and luckily locate works
> without type the button star finally thanks you in advance to repair whole,
Pl
Hello everybody and the team fedora,
blkid fully broken too chroot has losen sense in addition fstab has received an
update not smart so it has losen a lot of part and luckily locate works without
type the button star finally thanks you in advance to repair whole,
Have a nice week,
Regards
stop userspace based services which do
not communicate with hardware or with Fedora Linux kernel in chroot?
Or unfortunately, I must receive sad reality, that I can not control
services at all in chroot mode?
Thanks to VNC protocol, Tigervnc and Orca and Pulseaudio for Termux, it
is really
On 6/29/21 8:10 PM, ToddAndMargo via users wrote:
0) backup your zone tables (3+), named.confg. named.root.key files
0) backup your zone tables (3+), named.config,
named.root.key, named.local files
___
users mailing list -- users@lists.fedoraproje
Greshko wrote:
and
[root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/
/var/named/slaves/
/var/named/chroot/var/named/slaves/:
2415417 greshko.com.zone
/var/named/slaves/:
2415417 greshko.com.zone
Can I talk you out of a?
# stat /var/named/slaves/ | grep Inode
# stat /var
Greshko wrote:
and
[root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named/slaves/
/var/named/chroot/var/named/slaves/:
2415417 greshko.com.zone
/var/named/slaves/:
2415417 greshko.com.zone
Can I talk you out of a?
# stat /var/named/slaves/ | grep Inode
# stat /var
/named/chroot/var/named/slaves/
/var/named/slaves/
/var/named/chroot/var/named/slaves/:
2415417 greshko.com.zone
/var/named/slaves/:
2415417 greshko.com.zone
Can I talk you out of a?
# stat /var/named/slaves/ | grep Inode
# stat /var/named/chroot/var/named/slaves/ | grep Inode
On 28/06/2021 10:26, ToddAndMargo via users wrote:
On 6/27/21 7:13 PM, Ed Greshko wrote:
On 28/06/2021 10:07, ToddAndMargo via users wrote:
On 6/27/21 6:47 PM, Ed Greshko wrote:
On 28/06/2021 09:44, Ed Greshko wrote:
and
[root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named
On 28/06/2021 10:26, ToddAndMargo via users wrote:
On 6/27/21 7:13 PM, Ed Greshko wrote:
On 28/06/2021 10:07, ToddAndMargo via users wrote:
On 6/27/21 6:47 PM, Ed Greshko wrote:
On 28/06/2021 09:44, Ed Greshko wrote:
and
[root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named
On 6/27/21 7:13 PM, Ed Greshko wrote:
On 28/06/2021 10:07, ToddAndMargo via users wrote:
On 6/27/21 6:47 PM, Ed Greshko wrote:
On 28/06/2021 09:44, Ed Greshko wrote:
and
[root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/
/var/named/slaves/
/var/named/chroot/var/named/slaves
On 28/06/2021 10:07, ToddAndMargo via users wrote:
On 6/27/21 6:47 PM, Ed Greshko wrote:
On 28/06/2021 09:44, Ed Greshko wrote:
and
[root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named/slaves/
/var/named/chroot/var/named/slaves/:
2415417 greshko.com.zone
/var/named/slaves
via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical
at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.root and
wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.root and
named.root.key:
Hang on... If you&#x
On 6/27/21 5:34 PM, Ed Greshko wrote:
On 28/06/2021 06:40, ToddAndMargo via users wrote:
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward
On 28/06/2021 06:40, ToddAndMargo via users wrote:
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
> I am trying to clean up my bind-chroot forward and reverse files.
>
> The goal is to have bind-chroot do its thing by duplicating
> these two files over into
> /var/named/chroot/var/named/slaves/
> with th
Hi All,
Fedora 34
bind-chroot-9.16.16-1.fc34.x86_64
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with
On 6/17/21 9:47 PM, Tim via users wrote:
Tim:
I think if you want to modify *anything* in the zone files, you'll
first need to stop the service then delete their journal files,
before editing them.
Chris Adams:
Or just freeze/thaw them - no need to stop the server, and you should
never delete
Tim:
>> I think if you want to modify *anything* in the zone files, you'll
>> first need to stop the service then delete their journal files,
>> before editing them.
Chris Adams:
> Or just freeze/thaw them - no need to stop the server, and you should
> never delete the journal files.
I can't reme
On 6/16/21 10:45 PM, Ed Greshko wrote:
On 17/06/2021 13:41, Todd Chester via users wrote:
On 6/16/21 10:27 PM, Ed Greshko wrote:
Everything running just fine and the named-chroot service still shows
"enabled".
Every time I have upgraded Fedora to a new release,
I have had to &quo
On 17/06/2021 13:41, Todd Chester via users wrote:
On 6/16/21 10:27 PM, Ed Greshko wrote:
Everything running just fine and the named-chroot service still shows "enabled".
Every time I have upgraded Fedora to a new release,
I have had to "enable" named-chroot. If I ever
f
On 6/16/21 10:27 PM, Ed Greshko wrote:
Everything running just fine and the named-chroot service still shows
"enabled".
Every time I have upgraded Fedora to a new release,
I have had to "enable" named-chroot. If I ever
figure it out, I will definitely get back.
-9.16 source for f33. I had named-chroot enabled, and
running.
I then did "dnf update *rpm" in a directory containing the new version.
I then did "systemctl restart named-chroot".
So I have...
[egreshko@f33x ~]$ cat /etc/fedora-release
Fedora release 33 (Thirty Three)
[egre
Once upon a time, Tim via users said:
> I think if you want to modify *anything* in the zone files, you'll
> first need to stop the service then delete their journal files, before
> editing them.
Or just freeze/thaw them - no need to stop the server, and you should
never delete the journal files.
On Wed, 2021-06-16 at 12:15 -0700, ToddAndMargo via users wrote:
> I have been know to delete them at times, but
> I don't remember why. Maybe because I wanted to
> advance the serial manually.
I think if you want to modify *anything* in the zone files, you'll
first need to stop the service then
On 6/16/21 12:10 PM, Ed Greshko wrote:
On 17/06/2021 02:59, ToddAndMargo via users wrote:
On 6/16/21 11:52 AM, Ed Greshko wrote:
On 17/06/2021 02:25, ToddAndMargo via users wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused with bind/named)
You can see the
On 17/06/2021 02:59, ToddAndMargo via users wrote:
On 6/16/21 11:52 AM, Ed Greshko wrote:
On 17/06/2021 02:25, ToddAndMargo via users wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused
with bind/named)
You can see the mounts after starting named-chroot.
Hi
On 6/16/21 11:52 AM, Ed Greshko wrote:
On 17/06/2021 02:25, ToddAndMargo via users wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused with bind/named)
You can see the mounts after starting named-chroot.
Hi Ed,
Is this the case with your zone files in the
On 17/06/2021 02:25, ToddAndMargo via users wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused
with bind/named)
You can see the mounts after starting named-chroot.
Hi Ed,
Is this the case with your zone files in the
chroot directory too?
Yes.
--
Remind
On 6/15/21 2:30 PM, Ed Greshko wrote:
named-chroot-setup.service performs a series of bind-mounts (not be confused with bind/named)
You can see the mounts after starting named-chroot.
Hi Ed,
Is this the case with your zone files in the
chroot directory too?
-T
A fun double check
On 6/15/21 8:03 PM, Ed Greshko wrote:
In other words, help them to help you by reproducing it and collecting as much relevant
data.
If I ever get it figured out, I will report back
___
users mailing list -- users@lists.fedoraproject.org
To unsubscri
On 16/06/2021 11:02, ToddAndMargo via users wrote:
On 6/15/21 7:50 PM, Ed Greshko wrote:
On 16/06/2021 10:47, Ed Greshko wrote:
And you can see these are not different files.
I *mean* "are not the same file".
Oh I screwed up a bunch. What did I post
four revisions?
My "mistake" was tyin
On 16/06/2021 11:01, ToddAndMargo via users wrote:
On 6/15/21 7:54 PM, Ed Greshko wrote:
On 16/06/2021 10:49, ToddAndMargo via users wrote:
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
On 6/15/21 7:50 PM, Ed Greshko wrote:
On 16/06/2021 10:47, Ed Greshko wrote:
And you can see these are not different files.
I *mean* "are not the same file".
Oh I screwed up a bunch. What did I post
four revisions?
___
users mailing list -- user
On 6/15/21 7:54 PM, Ed Greshko wrote:
On 16/06/2021 10:49, ToddAndMargo via users wrote:
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following b
On 16/06/2021 10:49, ToddAndMargo via users wrote:
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following bug I posted
on 2021-06-14:
Well, t
On 16/06/2021 10:47, Ed Greshko wrote:
And you can see these are not different files.
I *mean* "are not the same file".
--
Remind me to ignore comments which aren't germane to the thread.
___
users mailing list -- users@lists.fedoraproject.org
To uns
On 6/15/21 7:00 PM, Ed Greshko wrote:
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following bug I posted
on 2021-06-14:
Well, that didn't happen all my cases of upgrades. So, I d
On 16/06/2021 09:55, ToddAndMargo via users wrote:
Hm. I screwed up pretty good. I will do this again.
I believe you've made mistakes in other areas.
I believe you've added files, with named stopped in (for example)
/var/named/chroot/etc.
This is a normal running named-chr
On 6/15/21 6:57 PM, ToddAndMargo via users wrote:
On 6/14/21 10:00 PM, ToddAndMargo via users wrote:
Hi All,
Thank you all for the enormous help in me getting bind-chroot
working after upgrading to Fedora 34. Here are my notes.
Hope this helps someone else.
-T
I hope this is the last time
On 15/06/2021 13:00, ToddAndMargo via users wrote:
Bind-chroot upgrade from FC3 to FC34 disables the service breaking a server
https://bugzilla.redhat.com/show_bug.cgi?id=1972000
Since that BZ lacks much in the area of detail why don't you:
1. Install F33 in VM.
2. Configure a named-c
On 16/06/2021 09:57, ToddAndMargo via users wrote:
2) in their "ultimate wisdom", the rpm maintainers disabled
the service after upgrading it. See the following bug I posted
on 2021-06-14:
Well, that didn't happen all my cases of upgrades. So, I doubt that was done by
the maintainers.
On 6/14/21 10:00 PM, ToddAndMargo via users wrote:
Hi All,
Thank you all for the enormous help in me getting bind-chroot
working after upgrading to Fedora 34. Here are my notes.
Hope this helps someone else.
-T
Here are my revised, revised note. Ed had to
straighten me out on some boo
On 6/15/21 2:30 PM, Ed Greshko wrote:
On 16/06/2021 03:54, ToddAndMargo via users wrote:
3) the new version of bind-chroot enables "dns security validation" by
default.
Make sure you do not have two `named.root.key` kicking around. One in
/etc/named.root.key
On 16/06/2021 03:54, ToddAndMargo via users wrote:
3) the new version of bind-chroot enables "dns security validation" by default.
Make sure you do not have two `named.root.key` kicking around. One in
/etc/named.root.key
and one in
/var/named/chroot/etc/named.roo
On 6/14/21 10:00 PM, ToddAndMargo via users wrote:
Hi All,
Thank you all for the enormous help in me getting bind-chroot
working after upgrading to Fedora 34. Here are my notes.
Hope this helps someone else.
-T
Well, if at first you don't succeed, revise! See
changes to named.roo
On 6/14/21 11:21 PM, Samuel Sieb wrote:
On 2021-06-14 10:00 p.m., ToddAndMargo via users wrote:
# systemctl enable named-chroot.service
# systemctl start named-chroot.service
In case you didn't know, "enable --now" will enable and also start the
service and "disable --now" wi
On 2021-06-14 10:00 p.m., ToddAndMargo via users wrote:
# systemctl enable named-chroot.service
# systemctl start named-chroot.service
In case you didn't know, "enable --now" will enable and also start the
service and "disable --now" will disable and stop it.
Hi All,
Thank you all for the enormous help in me getting bind-chroot
working after upgrading to Fedora 34. Here are my notes.
Hope this helps someone else.
-T
Broken bind-chroot repair after upgrading to Fedora 34:
# means root
$ means user
1) temporary workaround so you can surf the
On Fri, 27 Jul 2018 13:20:34 +0200
Patrick Dupre wrote:
> Why I cannot make a chroot?
Because chroot only does the one disk, but a operational
system requires stuff like /dev and /proc.
Here's the critical bits of the chroot script I use
to make a chroot functional:
mount --b
Hello,
After I cloned (cp -a /root1 /root2).
I boot on /root1 (because I am unable to boot on /boot2).
and run
chroot /boot2 (after monting the partition), but I get:
Error, do this: mount -t proc proc /proc
/bin/basename: missing operand
Try '/bin/basename --help' for more informat
On 17-08-31 14:43:10, Rick Stevens wrote:
On 08/31/2017 11:14 AM, Tony Nelson wrote:
> On 17-08-31 12:41:09, Mike Wright wrote:
>
>> How about using "env": env PATH="new_path" chroot /some_dir
>>
>> Wouldn't this preempt the passed PATH, prof
On 17-08-31 11:34:21, Kevin Cummings wrote:
On 08/30/17 15:16, Tony Nelson wrote:
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin should be a link to /usr/bin. is /usr/b
On 08/31/2017 11:14 AM, Tony Nelson wrote:
> On 17-08-31 12:41:09, Mike Wright wrote:
>
>> How about using "env": env PATH="new_path" chroot /some_dir
>>
>> Wouldn't this preempt the passed PATH, profile, bashrc, and the dot
>> fil
On 17-08-31 12:41:09, Mike Wright wrote:
How about using "env": env PATH="new_path" chroot /some_dir
Wouldn't this preempt the passed PATH, profile, bashrc, and the dot
files? If so, chroot could be defined as an alias to "env ...
chroot" and thereb
On 17-08-31 12:18:38, Tom H wrote:
On Wed, Aug 30, 2017 at 3:16 PM, Tony Nelson
wrote:
>
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
> this could happen; I would think that PATH is set
On 08/31/2017 09:41 AM, Mike Wright wrote:
> On 08/31/2017 09:26 AM, Rick Stevens wrote:
>> On 08/31/2017 08:34 AM, Kevin Cummings wrote:
>>> On 08/30/17 15:16, Tony Nelson wrote:
>>>> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
>>>>
On 08/31/2017 09:26 AM, Rick Stevens wrote:
On 08/31/2017 08:34 AM, Kevin Cummings wrote:
On 08/30/17 15:16, Tony Nelson wrote:
I have an old CentOS5 that I chroot into. On my old f20 box, PATH
included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin s
On 08/31/2017 08:34 AM, Kevin Cummings wrote:
> On 08/30/17 15:16, Tony Nelson wrote:
>> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
>> included /bin, but now on f26 it does not. I don't understand how
>
> For a while now, /bin should be a link to
On Thu, Aug 31, 2017 at 11:34 AM, Kevin Cummings
wrote:
> On 08/30/17 15:16, Tony Nelson wrote:
>>
>> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
>> included /bin, but now on f26 it does not. I don't understand how
>
> For a while now, /bin
On Wed, Aug 30, 2017 at 3:16 PM, Tony Nelson
wrote:
>
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
> this could happen; I would think that PATH is set inside the chroot
> by the shell. H
On 08/30/17 15:16, Tony Nelson wrote:
> I have an old CentOS5 that I chroot into. On my old f20 box, PATH
> included /bin, but now on f26 it does not. I don't understand how
For a while now, /bin should be a link to /usr/bin. is /usr/bin in the
PATH?
> this could happen; I wo
I have an old CentOS5 that I chroot into. On my old f20 box, PATH
included /bin, but now on f26 it does not. I don't understand how
this could happen; I would think that PATH is set inside the chroot
by the shell. How does PATH get set? I see how it is modified and
have fixed my
On 07/17/2016 07:23 AM, Tom H wrote:
but you'd be better off using
systemd-nspawn -D /path/to/chroot_dir
Good contribution Tom. I'd never heard of it before. Very powerful.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedo
Thank,
mount -t proc proc /path/to/chroot_dir/proc
chroot
works fine
but
systemd-nspawn -D /path/to/chroot_dir
provides:
Failed to determine whether the unified cgroups hierarchy is used: No such file
or directory
then,
Spawning container linux on /mnt/linux.
Press ^] three times within 1s to
On Sun, Jul 17, 2016 at 9:55 AM, Patrick Dupre wrote:
>
> I wanted to make a chroot, and I get:
>
> Error, do this: mount -t proc proc /proc
> /bin/basename: missing operand
> Try '/bin/basename --help' for more information.
Not enough info. What's calling ba
Hello,
I wanted to make a chroot, and I get:
Error, do this: mount -t proc proc /proc
/bin/basename: missing operand
Try '/bin/basename --help' for more information.
In the past, chroot was a working command (at least to make
to check). Does it not work properly anymore ?
Thank for
On 04/22/2015 12:58 AM, Cameron Simpson wrote:
On 21Apr2015 20:47, jd1008 wrote:
Now that chroot works, I am having a problem
with running gui apps.
For example running firefox, I get
(process:10281): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' faile
On 21Apr2015 20:47, jd1008 wrote:
Now that chroot works, I am having a problem
with running gui apps.
For example running firefox, I get
(process:10281): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
(firefox:10281): GnomeUI-WARNING **: While con
On 04/21/2015 04:51 PM, Cameron Simpson wrote:
On 21Apr2015 15:34, jd1008 wrote:
As root, I ran
chroot --userspec=user2:user2 /home/user2
chroot: failed to run command ‘/bin/bash’: Permission denied
The dir /home/user2 has in it
all the *bin and *lib (links) and usr/*bin and usr/*lib files
On 04/21/2015 04:51 PM, Cameron Simpson wrote:
On 21Apr2015 15:34, jd1008 wrote:
As root, I ran
chroot --userspec=user2:user2 /home/user2
chroot: failed to run command ‘/bin/bash’: Permission denied
The dir /home/user2 has in it
all the *bin and *lib (links) and usr/*bin and usr/*lib files
1 - 100 of 130 matches
Mail list logo
