On Fri, 2 Aug 2024, Tim Woodall wrote:
# Reading through this now I'm not absolutely sure that those hoops I
# jump throught to sign the repo are needed...
Just confirmed the gpg stuff is not needed
# Not sure why I have that proxy bit in here either. I think I'm
# installing from a file re
arch amd64 --unpack-tarball
/tmp/debs.tar.gz stable /mnt
which installs the base pkgs however debs.tar.gz holds other deb files which I
want to install when within the chroot.
I looked at the /mnt after the initial deployment and I see that there are
files that might help me in /var/cache/apt/arc
ebs.tar.gz stable /mnt
which installs the base pkgs however debs.tar.gz holds other deb files which I
want to install when within the chroot.
I looked at the /mnt after the initial deployment and I see that there are
files that might help me in /var/cache/apt/archives/ and /var/lib/apt/lists/
On 05/02/2024 17:40, Dmitry wrote:
> It would not work with secure boot
Yes.
But secure boot is usually turned off. It is a standard advice during
Linux installation.
That advice may be standard for distributions that do not provide signed
shim and grub. Likely it is applicable for Arch an
On Mon, 2024-02-05 at 17:40 +0700, Dmitry wrote:
>
> But secure boot is usually turned off. It is a standard advice during
> Linux
> installation.
>
Will probably be increasingly common though, I've got a Microsoft
Surface Laptop that works fine with Debian, but if you switch off
secure boot, it
> It would not work with secure boot
Yes.
But secure boot is usually turned off. It is a standard advice during Linux
installation.
sudo -i
Thank you!
I am unsure what UUID you mean.
At Manjaro:
grubx64.efi is at the sdb1 - EFI vfat /dev/sdb1
grub.cfg is at the sdb2 - crypto_LUKS /dev/sdb2
grubx64.efi contains data UUID=""a8...b7" of /dev/sdb2 which is
TYPE="crypto_LUKS".
`blkid` output:
/dev/sdb2: UUID="a8...b7" T
On 03/02/2024 22:32, Dmitry wrote:
2. sudo bash
sudo -i
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
I am unsure what UUID you mean.
Summary: GRUB installation not only involves configuration of text
files, but
also it i
Tim Woodall composed on 2024-02-03 21:25 (UTC):
> Max Nikulin wrote:
>> It seems secure boot is disabled in your case, so I am wondering why you do
>> not boot xen.efi directly.
> Because the NVRAM is extremely tempremental.
Not in my experience. I recognized long ago that WRT non-removable m
On Sat, 3 Feb 2024, Max Nikulin wrote:
It seems secure boot is disabled in your case, so I am wondering why you do
not boot xen.efi directly.
Because the NVRAM is extremely tempremental. Most updates fail, or
worse, corrupt it to the point it's hard to get anything to boot.
Additionally, the
Main question is resolved.
GRUB knows how to reach grub.cfg because grubx64.efi binary has the UUID and
path to grub configurations.
1. sudo blkid;
2. sudo bash
3. cd /boot/efi/EFI/Mangaro
4. strings grubx64.efi
5. And at the output of strings there is UUID and /boot/grub.
Summary: GRUB insta
On 03/02/2024 02:15, Tim Woodall wrote:
$ cat /boot/efi/EFI/XEN/xen.cfg
[...]
I'd be interested if there's a way to tell grubx64.efi to look for a
particular partition UUID.
An example of such grub.cfg from EFI/debian has been posted already in
this thread
https://lists.debian.org/msgid-sea
On 03/02/2024 02:51, Thomas Schmitt wrote:
Max Nikulin wrote:
Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi)
to the ESP partition on the USB stick.
The /EFI/boot directory of a bootable Debian ISO usually does not contain
the full GRUB equipment for EFI. Important parts of an
On 02/02/24 at 15:12, Dmitry wrote:
Going to read carefully.
https://www.debian.org/releases/buster/amd64/ch04s03.en.html
Interesting that Buster has more documentation than current release.
Nope, maybe you gave a quick read, the release notes of the current
release ¹ are exhaustive. If y
you're doing.
I join this statement. :))
Do you want a normal changeable Debian system installation or do you want
a Live system with its immutable core and maybe some partition where you
can store files ?
(Just curiosity of mine. Possibly i could not help much with chroot
questions anyway.)
Have a nice day :)
Thomas
On Thu, 1 Feb 2024, Marco Moock wrote:
Am 01.02.2024 um 19:20:01 Uhr schrieb Tim Woodall:
$ cat /boot/efi/EFI/XEN/xen.cfg
[global]
default=debian
[debian]
options=console=vga smt=true
kernel=vmlinuz root=/dev/mapper/vg--dirac-root ro quiet
ramdisk=initrd.img
menuentry "Xen EFI NVME" {
On Sat, Feb 03, 2024 at 01:17:05AM +0700, Dmitry wrote:
> > Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
> ESP partition on the USB stick.
>
> As I understand right now `dd` command applied to a device will copy all
> information including partitions table. Thus:
Actua
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
Yep. `dd` copy partitions table. Amazing.
```
dd will simply recreate the old partition scheme, as it is a bitwise copy &
applies no 'intelligence' to the operation.
```
https://askubunt
> Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
As I understand right now `dd` command applied to a device will copy all
information including partitions table. Thus:
dd if=debian-xx.iso of=/dev/sdb bs=4M status=progress; sync
Would
On Fri 02 Feb 2024 at 21:12:30 (+0700), Dmitry wrote:
> Going to read carefully.
>
> https://www.debian.org/releases/buster/amd64/ch04s03.en.html
>
> Interesting that Buster has more documentation than current release.
It appears the balance has now been spun off into a wiki page, at
https://
On 02/02/2024 21:06, Dmitry wrote:
Need additional research what to do with a FlashStick with several
partitions to make a LiveCD from it.
Just copy files from LiveCD (it should have EFI/Boot/bootx64.efi) to the
ESP partition on the USB stick.
Going to read carefully.
https://www.debian.org/releases/buster/amd64/ch04s03.en.html
Interesting that Buster has more documentation than current release.
> Do you want to install the OS on it?
Eventually no, I do not want OS on the Flash Stick.
The Flash Stick is only a testing place. I want OS at the SSD.
Now I am wondering how to prepare the Flash Stick to write LiveImage on it.
Because I already created a GPT table on that Flash and use deboo
Am 02.02.2024 schrieb Dmitry :
> I want OS at the SSD.
Then the ESP should be on that SSD too.
Max Nikulin schrieb:
On a *removable* drive EFI/Boot/bootx64.efi (that is actually
/usr/lib/shim/shimx64.efi.signed that loads grubx64.efi) may allow to
boot without modification of boot entries in NVRAM.
Yes, UEFI can (and must be able) to boot from a device without a boot
entry in the UEFI. O
On 02/02/2024 01:46, Dmitry wrote:
3. Now I want to boot using that Flash.
1. ESP is a partition that stores GRUB Binary. /boot/EFI/Name/grub64.eif
On a *removable* drive EFI/Boot/bootx64.efi (that is actually
/usr/lib/shim/shimx64.efi.signed that loads grubx64.efi) may allow to
boot without
Am 01.02.2024 um 19:20:01 Uhr schrieb Tim Woodall:
> $ cat /boot/efi/EFI/XEN/xen.cfg
> [global]
> default=debian
>
> [debian]
> options=console=vga smt=true
> kernel=vmlinuz root=/dev/mapper/vg--dirac-root ro quiet
> ramdisk=initrd.img
>
>
> menuentry "Xen EFI NVME" {
> insmod part_gpt
>
On Thu, 1 Feb 2024, Marco Moock wrote:
Am 02.02.2024 um 01:46:06 Uhr schrieb Dmitry:
2. ==>BAM<== some how that binary knows the system partition.
That information is on the EFI partition, where the GRUB bootloader
binary also resides.
root@ryz:/boot/efi/EFI# cat /boot/efi/EFI/debian/grub.c
1
mount /dev/vg-uefi-boot/root /mnt/image/
debootstrap --variant=minbase stretch /mnt/image ftp://einstein/debian/
mount -o bind /proc /mnt/image/proc
mount -o bind /dev /mnt/image/dev
mount -o bind /sys /mnt/image/sys
chroot /mnt/image </etc/hostname
cat </etc/fstab
# /etc/fstab
Am 02.02.2024 um 01:46:06 Uhr schrieb Dmitry:
> 2. ==>BAM<== some how that binary knows the system partition.
That information is on the EFI partition, where the GRUB bootloader
binary also resides.
root@ryz:/boot/efi/EFI# cat /boot/efi/EFI/debian/grub.cfg
search.fs_uuid 5b8b669d-xyz root hd0,gp
Hi Tim. The community is so kind.
So.
> I'm not exactly sure what you're doing.
Understand how GRUB works, to boot myself.
1. Trying to install Debian on the Flash.
2. Use it by the Debootstrap.
3. Now I want to boot using that Flash.
Looks like a caught the thread.
1. ESP is a partition tha
Am 02.02.2024 um 00:09:56 Uhr schrieb Dmitry:
> I made experiments with a FlashDrive, and create GPT there,
> if I want to use standard Debian Image how I should partition that
> flash drive (MBR, GPT)?
Do you want to install the OS on it?
For the partition table, I recommend GPT.
Do you want an
Huge thanks.
Your message starts the understanding.
And as well give a plenty of texts to read.
> EFI/debian/grub.cfg on the EFI System Partition contains filesystem UUID
where grub files reside.
All parts are simple But when compounding them together become messy.
In the Manjaro:
/boot/EFI/M
On Thu, 1 Feb 2024, Dmitry wrote:
Greetings!
After:
1. Creating GPT table and GPT partition with fdisk.
2. Copy data with a debootstrap.
3. Chroot into newly creating system.
I need to prepare that system for booting.
1. Install Kernel.
2. Install GRUB and Configure.
3. Add changes to UEFI to
> Why don't you use the normal setup?
Spend a lot of time on research, it would be nice to finish.
I made experiments with a FlashDrive, and create GPT there,
if I want to use standard Debian Image how I should partition that
flash drive (MBR, GPT)?
> Do you need a special configuration here or
On 01/02/2024 22:54, Marco Moock wrote:
Am 01.02.2024 schrieb Dmitry:
Use gdisk for that.
You can create an EFI partition there.
Choose Type EFI (EF00), 100MB.
Format it with FAT32.
550MiB is recommended in "Preparing your ESP"
http://www.rodsbooks.com/linux-uefi/#installing
see also
https://w
Am 01.02.2024 schrieb Dmitry :
Why don't you use the normal setup?
It does many tasks for you.
> After:
> 1. Creating GPT table and GPT partition with fdisk.
Use gdisk for that.
You can create an EFI partition there.
Choose Type EFI (EF00), 100MB.
Format it with FAT32.
> And at the point two (I
Greetings!
After:
1. Creating GPT table and GPT partition with fdisk.
2. Copy data with a debootstrap.
3. Chroot into newly creating system.
I need to prepare that system for booting.
1. Install Kernel.
2. Install GRUB and Configure.
3. Add changes to UEFI to start booting.
And at the point
On Sun, Jun 18, 2023 at 5:03 AM Mario Marietto wrote:
>
> [...]
> I've debootstrapped jessie on Ubuntu 14.04 with this command :
>
> debootstrap --foreign --arch=armhf jessie jessie-armhf
> http://archive.debian.org/debian
>
> and it worked ok,but when I try t
On Sun, 18 Jun 2023, Mario Marietto wrote:
Hello.
with qemu works,but I thought that it was better to avoid the usage of
qemu.
I'm a bit puzzled what you're trying to do.
if you want to chroot on an amd64 machine then you have to use something
like qemu to emulate the armhf proc
I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
but I see the file bash within the d
uuid1...
I: Extracting mount...
I: Extracting util-linux...
I: Extracting liblzma5...
I: Extracting zlib1g...
I: Running command: chroot stretch-armel /debootstrap/debootstrap
--second-stage
I: Keyring file not available at
/usr/share/keyrings/debian-archive-keyring.gpg; switching to https mi
qemu-user to emulate armhf.
yes,I've fixed the error by using qemu-debootstrap,but I tried to use
debootstrap because qemu-debootstrap gives some errors when I update the
chroot environment.
On Sun, Jun 18, 2023 at 1:01 PM Eduardo M KALINOWSKI <
edua...@kalinowski.com.br> wrote:
>
bian.org/debian>
and it worked ok,but when I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
bian.org/debian>
and it worked ok,but when I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
Hello.
Maybe a little problem for you,but a bigger problem for me. I've
debootstrapped jessie on Ubuntu 14.04 with this command :
debootstrap --foreign --arch=armhf jessie jessie-armhf
http://archive.debian.org/debian
and it worked ok,but when I try to chroot within it :
root@marietto-Z8
ed
> > x32 is not available when I attempted to setup a chroot with
> > debootstrap:
> >
> > $ debootstrap --arch=x32 --keyring
> > /usr/share/keyrings/debian-archive-keyring.gpg \
> > --variant=buildd --exclude=debfoster unstable debian-x32
> > http://ftp
On 2022-11-29 11:24 -0500, Jeffrey Walton wrote:
> I'm running a Debian Unstable machine. I use it for Chroots. I noticed
> x32 is not available when I attempted to setup a chroot with
> debootstrap:
>
> $ debootstrap --arch=x32 --keyring
> /usr/share/keyrings/deb
On Tue, Nov 29, 2022 at 11:24:42AM -0500, Jeffrey Walton wrote:
> Hi Everyone,
>
> I'm running a Debian Unstable machine. I use it for Chroots. I noticed
> x32 is not available when I attempted to setup a chroot with
> debootstrap:
>
> $ debootstrap --arch=x32 --key
Hi Everyone,
I'm running a Debian Unstable machine. I use it for Chroots. I noticed
x32 is not available when I attempted to setup a chroot with
debootstrap:
$ debootstrap --arch=x32 --keyring
/usr/share/keyrings/debian-archive-keyring.gpg \
--variant=buildd --exclude=debfoster unstable d
ad the idea, to boot the ISO in a chroot environment, then
> > upgrade the booted ISO via apt, and at last save the updated livesystem as
> > an ISO-file again.
>
> This might give you the desired data content or not. I could imagine
> stumblestones but have no experience
Hi,
Hans wrote:
> I had the idea, to boot the ISO in a chroot environment, then
> upgrade the booted ISO via apt, and at last save the updated livesystem as
> an ISO-file again.
This might give you the desired data content or not. I could imagine
stumblestones but have no experience wit
in a chroot environment, then
upgrade the booted ISO via apt, and at last save the updated livesystem as an
ISO-file again.
Is this possible?
I want to spare and shorten the time for download, unpacking, installing,
configuring and ISO-creating of the whole system, as I believe, doing as I
; Thanks. I saw that there are some bug-reports and that development is
> active. Maybe it makes sense to do a bug-report, because from my point
> of view it is easy to reproduce (no need to bother with ARM yet, I
> just tried the "basic" invocation to create a stable
Linux-Fan writes:
Jonas Smedegaard writes:
[...]
Being such a simple invocation, I thought I must have made some rather
obvious mistake, because my command very much follows the manpage. I had
thought that the complex part would only come afterwards :)
I recommend to read section "MODES" i
configfiles of an
officially installed one.
Thanks. I saw that there are some bug-reports and that development is
active. Maybe it makes sense to do a bug-report, because from my point of
view it is easy to reproduce (no need to bother with ARM yet, I just tried
the "basic" invoca
rap` and tried the most simple of invocations:
>
> ~~~
> $ mmdebstrap stable test.tar
> I: automatically chosen mode: fakechroot
> I: chroot architecture amd64 is equal to the host's architecture
> I: using /tmp/mmdebstrap.r10cMA6wAV as tempdir
> I: running apt-get update
mode: fakechroot
I: chroot architecture amd64 is equal to the host's architecture
I: using /tmp/mmdebstrap.r10cMA6wAV as tempdir
I: running apt-get update...
done
I: downloading packages with apt...
done
I: extracting archives...
done
/usr/sbin/chroot: cannot change root directory to
At the moment the chrooted rsyslog instance use bind mounted
/run/systemd/notify.
It is causing the Veeam backup fail.
Anyone how to make it working without bind mounting notify file into chroot?
Is there some way to let systemd create and listen on another "notify"
socket?
Opened bug report at mainstream.
https://github.com/systemd/systemd/issues/12498
On Tue, May 7, 2019 at 12:17 PM Peter Viskup wrote:
> It is related to systemd processing of chroot, as with commenting the User
> setting, the service start up successfully.
>
> Want to mimic the st
It is related to systemd processing of chroot, as with commenting the User
setting, the service start up successfully.
Want to mimic the startup of the service in init script on Debian8 (which
is running fine):
~# start-stop-daemon --start --quiet --pidfile
"/srv/inst/var/run/rsyslog
On Tue, May 07, 2019 at 11:08:38AM +0200, Peter Viskup wrote:
> Running Debian9 with systemd 241-3~bpo9+1 from backports.
> Having trouble to start rsyslog service in chroot jail using the systemd
> service file with RootDirectory and User settings.
> Setting AmbientCapabilities=CA
Running Debian9 with systemd 241-3~bpo9+1 from backports.
Having trouble to start rsyslog service in chroot jail using the systemd
service file with RootDirectory and User settings.
Setting AmbientCapabilities=CAP_SYS_CHROOT does not help and still getting
following errors:
rsyslog-chroot
On Mon, Apr 15, 2019 at 05:05:53PM +0200, Markus Schönhaber wrote:
> Tomas, 15.4.2019 16:38 +0200:
>
> > --chroot-mode=schroot|sudo|autopkgtest
> > Select the desired chroot mode. Four values are possible:
> > schroot [...], sudo [...] and autopkgtest [...]
>
Tomas, 15.4.2019 16:38 +0200:
> --chroot-mode=schroot|sudo|autopkgtest
> Select the desired chroot mode. Four values are possible:
> schroot [...], sudo [...] and autopkgtest [...]
Out of curiosity: am I missing something or are there only three of the
"Four values"
chroot, but can use other methods. From
sbuild's man page:
--chroot-mode=schroot|sudo|autopkgtest
Select the desired chroot mode. Four values are possible:
schroot (the default), sudo (which uses sudo to execute
chroot in a directory from /etc/sbuild/chroot or ./chroot)
and
On Mon, Apr 15, 2019 at 02:30:33PM +0300, Alexei Fedotov wrote:
it seems schroot package is somehow missed in my repository, I will
look into it.
schroot is merely recommended by sbuild, and not depended upon by it:
presumably sbuild can be used in some other way without schroot. When
you insta
2:23 PM Georgi Naplatanov wrote:
> >
> > On 4/15/19 2:02 PM, Alexei Fedotov wrote:
> > > Hello,
> > > I've installed sbuild ver 0.73.0-4 and tried creating chroot environment
> > >
> > > I used the following command and get an error.
> > &g
] Start using Apache Openmeetings today, http://openmeetings.apache.org/
On Mon, Apr 15, 2019 at 2:23 PM Georgi Naplatanov wrote:
>
> On 4/15/19 2:02 PM, Alexei Fedotov wrote:
> > Hello,
> > I've installed sbuild ver 0.73.0-4 and tried creating chroot environment
> >
>
On 4/15/19 2:02 PM, Alexei Fedotov wrote:
> Hello,
> I've installed sbuild ver 0.73.0-4 and tried creating chroot environment
>
> I used the following command and get an error.
>
> devops@devops:~/git/docker.io$ sudo sbuild-createchroot
> --include=eatmydata,ccache,gn
Hello,
I've installed sbuild ver 0.73.0-4 and tried creating chroot environment
I used the following command and get an error.
devops@devops:~/git/docker.io$ sudo sbuild-createchroot
--include=eatmydata,ccache,gnupg unstable
/srv/chroot/unstable-amd64-sbuild http://deb.debian.org/debian
t strange. Are your client/server programs
> compatible?
>
> Peter
>
It seem to be a problem with /usr/bin/rssh login shell. If the use has
/bin/bash it works fine. So i hope it is not possible to breaking out of
chroot jail.
basti writes:
> On 28.03.19 08:21, Peter Wiersig wrote:
>> basti writes:
> Try scp:
>
> /usr/sbin/sshd -d -p
>
> Starting session: command for alice from 2.206.185.146 port 45296 id 0
So that reads as if all is fine, but then the next line indicates that
the client has terminated the connec
ng the script, so that the
> syslogd listens to the ./dev/log in the chroot?
>
> Peter
>
I have done it with the script.
For sftp it dosed matter if syslogd has a socket or not it work's also.
SFTP is working for now. scp still doesn't.
basti writes:
>
> Files inside chroot:
>
> /home/user# find ./
> ./
> ./bin
> ./bin/ls
> ./bin/date
> ./bin/bash
> ./.ssh
> ./.ssh/authorized_keys
> ./lib
> ./lib/x86_64-linux-gnu
> ./lib/x86_64-linux-gnu/libattr.so.1
> ./lib/x86_64-linux-gnu/libncu
On 28.03.19 08:21, Peter Wiersig wrote:
> basti writes:
>
>> sftp -vv u...@example.com
>> Transferred: sent 2508, received 2260 bytes, in 0.2 seconds
>> Bytes per second: sent 15924.1, received 14349.5
>> debug1: Exit status 1
>> Connection closed
>>
>>
>> scp -vv u...@example.com:/foo /tmp
>> Tr
basti writes:
> sftp -vv u...@example.com
> Transferred: sent 2508, received 2260 bytes, in 0.2 seconds
> Bytes per second: sent 15924.1, received 14349.5
> debug1: Exit status 1
> Connection closed
>
>
> scp -vv u...@example.com:/foo /tmp
> Transferred: sent 2508, received 2304 bytes, in 0.2 sec
hello,
i try ro setup a chroot jail with rssh.
the jail seem to work if I set /bin/bash as shell.
(I get a prompt and can ls inside chroot)
When I set /usr/bin/rssh as login shell i get:
ssh u...@example.com
This account is restricted by rssh.
Allowed commands: scp sftp rsync
sftp -vv u
send me a binary which does work on my
Jessie system, but, never-the-less, I plan to start experimenting with either
a chroot or VM environment to run either sid or a recent Ubuntu release so
that I can compile / build the binary myself.
The machine I want to do this on does not have any unallocated
On 12/8/18 9:21 AM, rhkra...@gmail.com wrote:
On Saturday, December 08, 2018 02:59:15 AM Alexander V. Makartsev wrote:
You are over-complicating things.
I can believe that ;-)
You can build chroot in just a
separate folder using debootstrap.
Ahh, ok, then that is almost surely what I'l
On 08.12.2018 19:21, rhkra...@gmail.com wrote:
> Ahh, ok, then that is almost surely what I'll try at least at first.
>
> Looking ahead, if I later want to experiment with real VMs, do they need to
> be
> on separate partitions or can they also just be in separate folders?
>
> And if they can be
On Sat, Dec 08, 2018 at 09:21:33AM -0500, rhkra...@gmail.com wrote:
>
> Looking ahead, if I later want to experiment with real VMs, do they need to
> be
> on separate partitions or can they also just be in separate folders?
>
Every VM solution that I can think of supports using disk image files
On Saturday, December 08, 2018 02:59:15 AM Alexander V. Makartsev wrote:
> You are over-complicating things.
I can believe that ;-)
> You can build chroot in just a
> separate folder using debootstrap.
Ahh, ok, then that is almost surely what I'll try at least at first.
Looki
programmer has been able to send me a binary which does work on my
> Jessie system, but, never-the-less, I plan to start experimenting with either
> a chroot or VM environment to run either sid or a recent Ubuntu release so
> that I can compile / build the binary myself.
>
> The mac
Hi,
On Fri, Dec 07, 2018 at 10:36:43PM -0500, rhkra...@gmail.com wrote:
> One of the partitions I could free up is 16 GB, the other is 54 GB -- I'd
> rather free up and use the smaller one, but I'm wondering if that will be big
> enough?
I would be amazed if 16GB wasn't enough. All you'll be do
ystem, but, never-the-less, I plan to start experimenting with either
a chroot or VM environment to run either sid or a recent Ubuntu release so
that I can compile / build the binary myself.
The machine I want to do this on does not have any unallocated partitions /
disk space. There are two
On 12/2/18 2:41 PM, Tommi Höynälänmaa wrote:
> I have just installed sid to a chroot. Locales don't work even though I have
> installed package locales. Scandinavian letters are not displayed and guile
> gives the following warning:
>
> ---cut here---
>
> guile:
I have just installed sid to a chroot. Locales don't work even though I
have installed package locales. Scandinavian letters are not displayed
and guile gives the following warning:
---cut here---
guile: warning: failed to install locale
warning: failed to install locale: Invalid arg
ollowing description:
"debootstick is used to generate a bootable image from a Debian or
Ubuntu chroot environment (such as one generated with debootstrap,
docker export, etc.).
This image should then be copied to a USB stick or disk and used to
boot any amd64 machine (BIOS- or UEFI-based).
The
On 03/05/2017, Sam Kuper wrote:
> [...] I then exit the `chroot`, and my trouble begins. I find that I can
> unmount `/mnt/dev` and `/mnt/proc`, **but not `/mnt/sys`**. The latter
> refuses to unmount because it contains `/mnt/sys/fs/cgroup/systemd`,
> which the system for some reas
tch is running from the source drive,
I mount the target ZFS root (`/`) filesystem at `/mnt`. I then
recursively bind:
- `/dev` to `/mnt/dev`
- `/proc` to `/mnt/proc`
- `/sys` to `/mnt/sys`.
I then chroot into `/mnt`.
(In the future, when I am chrooted into `/mnt`, I intend to run
`update-init
Hello, I am trying to include the debian installer (or an alternative, if
any) in a live cd I am creating myself, the problem is, I have no idea how
to set it up nor could I find any relevant information on the internet or
wiki. All I know is that I need to have debian-installer-launcher installed
ed in systemd. From a cursory glance, you can
take getty@.service, clone it to, say chroot-getty@.service, and modify
it to run the getty in your chroot, then enable and start
chroot-getty@tty8.service.
Thank you very much, Robert.
How to execute another login process in a different vi
Good morning, thank you very much for the help of the attached document.
You can tell me how it's done
with systemd in debian 8.3
Thank you very much, Robert.
How to execute another login process in a different virtual terminal, where
To enter the chroot directly. And run X and GNOME in
Quick follow-up.
1) CHROOT DISABLED = WORKS
In my configuration /etc/php5/fpm/pool.d/mywebsite.conf I disabled chroot
`# chroot=/var/www/mywebsite`
In /lib/systemd/system/php5-fpm.service I enabled `PrivateTmp=true` to the
`[Service]` section.
I ran `systemctl daemon-reload` and `service
Hi guys,
I am trying to teach myself how to setup a nginx and chrooted php-fpm
environment in Debian 8.
I specifically want to ask a question on the tmp-directory for the php-fpm
chroot.
So I chrooted the PHP-FPM pool worker who is handling my PHP website into
/var/www/mywebsite.
### /etc
I have problem with debian server. After upgrade it not start and end with info
/sbin/init �餿: QRU�4���̀]ZY� :
So I start the box with Live Debian Jessie CD and try to chroot.
I mount hard disk in /mnt and proc sys and dev in proper places as
instructed on net.
After chroot /mnt /bin
better than nothing,
though.
> E.g. I often need something like this when running inside
> a chroot and always have trouble finding the clean&easy way to do it
> (IIUC dpkg should figure out on its own that it's running in a chroot,
> but it doesn't seem to work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 22, 2016 at 09:36:57AM -0400, Haines Brown wrote:
> On Fri, Apr 22, 2016 at 10:36:36AM +0100, Karl E. Jorgensen wrote:
>
> > > # LANG=C.UTF8 /usr/sbin/chroot /mnt/debinst /bin/bash
> > > /usr/sbin/chroot: fai
On Fri, Apr 22, 2016 at 10:36:36AM +0100, Karl E. Jorgensen wrote:
> > # LANG=C.UTF8 /usr/sbin/chroot /mnt/debinst /bin/bash
> > /usr/sbin/chroot: failed to run command `/bin/bash': No such file or
> > directory
> >
> > /usr/bin/chroot exists. So d
1 - 100 of 795 matches
Mail list logo
