* [gentoo-user] Re: gentoo
[not found] <200412051508.59017.dlw@hei.net>
@ 2004-12-06 0:24 ` Gabriel M. Beddingfield
2004-12-06 5:14 ` Ow Mun Heng
0 siblings, 1 reply; 12+ messages in thread
From: Gabriel M. Beddingfield @ 2004-12-06 0:24 UTC (permalink / raw
To: Don, gentoo-user
On Sunday 05 December 2004 05:08 pm, you wrote:
> My apologies for sending this to you but
> I accidently deleted your e-mail in gentoo.users.
It's allright. I like getting a CC, actually.
> [root@hei don]# mount -t proc none /mnt/gentoo/proc
> [root@hei don]# chroot /mnt/gentoo /bin/bash
> bash-2.05b# env-update
>
> >>> Regenerating /etc/ld.so.cache...
>
> bash-2.05b# source /etc/profile
> hei / # cd /mnt/gentoo
> bash: cd: /mnt/gentoo: No such file or directory
> hei / # cd /gentoo
> bash: cd: /gentoo: No such file or directory
> hei / #
> /mnt/gentoo is /dev/hdb5 so I know its there.
> I can open it with a file manager.
> I'm installing gentoo from a konsole in MDK.
> Could that be the problem?
>
> I get the same thing.
> Don
short answer: You were doing fine. There is no error. Proceed with
the next step ('emerge --sync').
LONG answer:
You were doing just fine until you did 'cd /mnt/gentoo'. What are you
trying to do? Why not just take the next step? (Next step: 'emerge
--sync')
What you are seeing is *not* an error. When you say
'chroot /mnt/gentoo /bin/bash' the computer *essentially* does this:
1. cd /mnt/gentoo
2. make /mnt/gentoo to be /
3. Run bash as the shell... as if you had booted into gentoo
with /mnt/gentoo as your root directory (/).
4. All this only effects the konsole session you are running.
/mnt/gentoo will no longer exist. If it did exist, then it means you
messed up.
Suppose I did the following:
# ls /
foo bar bat
# ls /mnt/gentoo
alpha beta delta
# ls /mnt/gentoo/mnt/gentoo
do re mi
# chroot /mnt/gentoo /bin/bash
# ls
alpha beta delta
# ls /
alpha beta delta
# ls /mnt/gentoo
do re me
Do you get it? In your case, there is no /mnt/gentoo/mnt/gentoo, so
when you chroot, the directory /mnt/gentoo no longer exists.
GOOD LUCK!
--
G a b r i e l M . B e d d i n g f i e l d
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: gentoo
2004-12-06 0:24 ` [gentoo-user] Re: gentoo Gabriel M. Beddingfield
@ 2004-12-06 5:14 ` Ow Mun Heng
0 siblings, 0 replies; 12+ messages in thread
From: Ow Mun Heng @ 2004-12-06 5:14 UTC (permalink / raw
To: gentoo-user
On Mon, 2004-12-06 at 08:24, Gabriel M. Beddingfield wrote:
> On Sunday 05 December 2004 05:08 pm, you wrote:
> > [root@hei don]# mount -t proc none /mnt/gentoo/proc
> > [root@hei don]# chroot /mnt/gentoo /bin/bash
> > bash-2.05b# env-update
> >
> > >>> Regenerating /etc/ld.so.cache...
> >
> > bash-2.05b# source /etc/profile
> > hei / # cd /mnt/gentoo
> > bash: cd: /mnt/gentoo: No such file or directory
> > hei / # cd /gentoo
> > bash: cd: /gentoo: No such file or directory
> > hei / #
> What you are seeing is *not* an error. When you say
> 'chroot /mnt/gentoo /bin/bash' the computer *essentially* does this:
>
> 1. cd /mnt/gentoo
> 2. make /mnt/gentoo to be /
> 3. Run bash as the shell... as if you had booted into gentoo
> with /mnt/gentoo as your root directory (/).
> 4. All this only effects the konsole session you are running.
>
> /mnt/gentoo will no longer exist. If it did exist, then it means you
> messed up.
If you _really_ want to be sure, I can't remember, but if you got
virtual Termnal #2 (Alt-F2), and you've changed the root password, go to
Term #2, log in as root, and cd /mnt/gentoo. I betcha it's there. :-)
Ps : Greets to Gabriel Beddingfield. (any relation to Daniel
Beddingfield?? hehe..)
--
Ow Mun Heng
Gentoo/Linux on D600 1.4Ghz
Neuromancer 13:12:52 up 3:55, 6 users, 0.23, 0.49, 0.44
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-user] Re: gentoo
2014-09-16 4:29 [gentoo-user] gentoo Joseph
@ 2014-09-16 14:18 ` James
2014-09-16 15:02 ` Joseph
0 siblings, 1 reply; 12+ messages in thread
From: James @ 2014-09-16 14:18 UTC (permalink / raw
To: gentoo-user
Joseph <syscon780 <at> gmail.com> writes:
>
> After recent emerge I get few blockers, that I don't know what to do
> with it My box has not been updated for 3-months :-/
Joseph,
The problems with perl updates are not new. It was discussed on this
list quite a bit the last few months. If your update cycle is more than
a few weeks, you are going to miss the relevant discussions on gentoo-user
that solve most of your issues; so maybe update your system weekly_ish?
(and browse gentoo-user).
> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
" eselect python list "
will show your current active version of python. Most all (stable) systems
have a version 2 (2.7) and version 3 (3.3) installed. I'm not
sure why your system did not upgrade 3.1 to 3.3, during the course
of routine upgrades. Also run:
"python-updater"
after compiling new or removing old version of
python. python is system *critical* so be cautious when performing
install/removal admin tasks on python.
hth,
James
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: gentoo
2014-09-16 14:18 ` [gentoo-user] gentoo James
@ 2014-09-16 15:02 ` Joseph
2014-09-16 15:57 ` J. Roeleveld
0 siblings, 1 reply; 12+ messages in thread
From: Joseph @ 2014-09-16 15:02 UTC (permalink / raw
To: gentoo-user
On 09/16/14 14:18, James wrote:
>Joseph <syscon780 <at> gmail.com> writes:
>
>>
>> After recent emerge I get few blockers, that I don't know what to do
>> with it My box has not been updated for 3-months :-/
>
>Joseph,
>
>The problems with perl updates are not new. It was discussed on this
>list quite a bit the last few months. If your update cycle is more than
>a few weeks, you are going to miss the relevant discussions on gentoo-user
>that solve most of your issues; so maybe update your system weekly_ish?
>(and browse gentoo-user).
>
>> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>
>" eselect python list "
>
>will show your current active version of python. Most all (stable) systems
>have a version 2 (2.7) and version 3 (3.3) installed. I'm not
>sure why your system did not upgrade 3.1 to 3.3, during the course
>of routine upgrades. Also run:
>
>"python-updater"
>
>after compiling new or removing old version of
>python. python is system *critical* so be cautious when performing
>install/removal admin tasks on python.
>
>
>
>hth,
>James
Good suggestion.
Running:
# eselect python list
# eselect python set (put number for python:3.3)
# emerge -C dev-lang/python:3.1
# python updater
solved all the problems.
I was at python:3.3 but for some reason or another (mostly my fault) I did not unmerged python:3.1
When it comes to upgrading be-weekly maybe but from my experience, when I was doing it more often, occasionally, I ended up with a broken system that was caused by new
packages.
I have 4-boxes at home and two boxes at a remote location. So the boxes at home get upgraded first, I wait a week, just to make sure every program works and
then I upgrade one box on a remote location, wait one week again and upgrade the second box (the backup) in the remote location.
So doing it even every second week would be too often for this routine.
The boxes are "rsync" to one local box.
--
Joseph
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: gentoo
2014-09-16 15:02 ` Joseph
@ 2014-09-16 15:57 ` J. Roeleveld
2014-09-16 18:05 ` Joseph
0 siblings, 1 reply; 12+ messages in thread
From: J. Roeleveld @ 2014-09-16 15:57 UTC (permalink / raw
To: gentoo-user
On 16 September 2014 17:02:43 CEST, Joseph <syscon780@gmail.com> wrote:
>On 09/16/14 14:18, James wrote:
>>Joseph <syscon780 <at> gmail.com> writes:
>>
>>>
>>> After recent emerge I get few blockers, that I don't know what to do
>>> with it My box has not been updated for 3-months :-/
>>
>>Joseph,
>>
>>The problems with perl updates are not new. It was discussed on this
>>list quite a bit the last few months. If your update cycle is more
>than
>>a few weeks, you are going to miss the relevant discussions on
>gentoo-user
>>that solve most of your issues; so maybe update your system
>weekly_ish?
>>(and browse gentoo-user).
>>
>>> emerge: there are no ebuilds to satisfy "dev-lang/python:3.1".
>>
>>" eselect python list "
>>
>>will show your current active version of python. Most all (stable)
>systems
>>have a version 2 (2.7) and version 3 (3.3) installed. I'm not
>>sure why your system did not upgrade 3.1 to 3.3, during the course
>>of routine upgrades. Also run:
>>
>>"python-updater"
>>
>>after compiling new or removing old version of
>>python. python is system *critical* so be cautious when performing
>>install/removal admin tasks on python.
>>
>>
>>
>>hth,
>>James
>
>Good suggestion.
>Running:
># eselect python list
># eselect python set (put number for python:3.3)
># emerge -C dev-lang/python:3.1
># python updater
>
>solved all the problems.
>I was at python:3.3 but for some reason or another (mostly my fault) I
>did not unmerged python:3.1
>
>When it comes to upgrading be-weekly maybe but from my experience, when
>I was doing it more often, occasionally, I ended up with a broken
>system that was caused by new
>packages.
>I have 4-boxes at home and two boxes at a remote location. So the
>boxes at home get upgraded first, I wait a week, just to make sure
>every program works and
>then I upgrade one box on a remote location, wait one week again and
>upgrade the second box (the backup) in the remote location.
>So doing it even every second week would be too often for this routine.
>
>The boxes are "rsync" to one local box.
I am starting to wonder.
How exactly do you upgrade the other machines?
Copying the entire filesystem?
--
Joost
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: gentoo
2014-09-16 15:57 ` J. Roeleveld
@ 2014-09-16 18:05 ` Joseph
2014-09-16 19:11 ` Alan McKinnon
2014-09-16 19:58 ` James
0 siblings, 2 replies; 12+ messages in thread
From: Joseph @ 2014-09-16 18:05 UTC (permalink / raw
To: gentoo-user
On 09/16/14 17:57, J. Roeleveld wrote:
[snip]
>>
>>solved all the problems.
>>I was at python:3.3 but for some reason or another (mostly my fault) I
>>did not unmerged python:3.1
>>
>>When it comes to upgrading be-weekly maybe but from my experience, when
>>I was doing it more often, occasionally, I ended up with a broken
>>system that was caused by new
>>packages.
>>I have 4-boxes at home and two boxes at a remote location. So the
>>boxes at home get upgraded first, I wait a week, just to make sure
>>every program works and
>>then I upgrade one box on a remote location, wait one week again and
>>upgrade the second box (the backup) in the remote location.
>>So doing it even every second week would be too often for this routine.
>>
>>The boxes are "rsync" to one local box.
>
>I am starting to wonder.
>How exactly do you upgrade the other machines?
>Copying the entire filesystem?
I rsync one local server and all other machine are rsync to it.
My main idea is trying not to introduce to many newer versions packages as in the past I've notice that that could cause the problem.
The is no need for sarcasm. I basically do what works and I do learn from my experience (sometimes :-/).
--
Joseph
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: gentoo
2014-09-16 18:05 ` Joseph
@ 2014-09-16 19:11 ` Alan McKinnon
2014-09-16 19:38 ` Joseph
2014-09-16 19:58 ` James
1 sibling, 1 reply; 12+ messages in thread
From: Alan McKinnon @ 2014-09-16 19:11 UTC (permalink / raw
To: gentoo-user
On 16/09/2014 20:05, Joseph wrote:
> On 09/16/14 17:57, J. Roeleveld wrote:
> [snip]
>>>
>>> solved all the problems.
>>> I was at python:3.3 but for some reason or another (mostly my fault) I
>>> did not unmerged python:3.1
>>>
>>> When it comes to upgrading be-weekly maybe but from my experience, when
>>> I was doing it more often, occasionally, I ended up with a broken
>>> system that was caused by new
>>> packages.
>>> I have 4-boxes at home and two boxes at a remote location. So the
>>> boxes at home get upgraded first, I wait a week, just to make sure
>>> every program works and
>>> then I upgrade one box on a remote location, wait one week again and
>>> upgrade the second box (the backup) in the remote location.
>>> So doing it even every second week would be too often for this routine.
>>>
>>> The boxes are "rsync" to one local box.
>>
>> I am starting to wonder.
>> How exactly do you upgrade the other machines?
>> Copying the entire filesystem?
>
> I rsync one local server and all other machine are rsync to it.
*what* do you rsync? Not whihc machine rsyncs to what, he's asking what
files and directories exactly do you rsync?
> My main idea is trying not to introduce to many newer versions packages
> as in the past I've notice that that could cause the problem.
>
> The is no need for sarcasm. I basically do what works and I do learn
> from my experience (sometimes :-/).
>
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: gentoo
2014-09-16 19:11 ` Alan McKinnon
@ 2014-09-16 19:38 ` Joseph
0 siblings, 0 replies; 12+ messages in thread
From: Joseph @ 2014-09-16 19:38 UTC (permalink / raw
To: gentoo-user
On 09/16/14 21:11, Alan McKinnon wrote:
>On 16/09/2014 20:05, Joseph wrote:
>> On 09/16/14 17:57, J. Roeleveld wrote:
>> [snip]
>>>>
>>>> solved all the problems.
>>>> I was at python:3.3 but for some reason or another (mostly my fault) I
>>>> did not unmerged python:3.1
>>>>
>>>> When it comes to upgrading be-weekly maybe but from my experience, when
>>>> I was doing it more often, occasionally, I ended up with a broken
>>>> system that was caused by new
>>>> packages.
>>>> I have 4-boxes at home and two boxes at a remote location. So the
>>>> boxes at home get upgraded first, I wait a week, just to make sure
>>>> every program works and
>>>> then I upgrade one box on a remote location, wait one week again and
>>>> upgrade the second box (the backup) in the remote location.
>>>> So doing it even every second week would be too often for this routine.
>>>>
>>>> The boxes are "rsync" to one local box.
>>>
>>> I am starting to wonder.
>>> How exactly do you upgrade the other machines?
>>> Copying the entire filesystem?
>>
>> I rsync one local server and all other machine are rsync to it.
>
>
>*what* do you rsync? Not whihc machine rsyncs to what, he's asking what
>files and directories exactly do you rsync?
I "rsync" only portage, nothing else on the main server.
Other boxes are arsyning to:
SYNC="rsync://10.0.0.103/gentoo-portage"
10.0.0.103 is running "rsyncd"
Upgrade is as usual.
--
Joseph
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-user] Re: gentoo
2014-09-16 18:05 ` Joseph
2014-09-16 19:11 ` Alan McKinnon
@ 2014-09-16 19:58 ` James
2014-09-16 20:23 ` Joseph
1 sibling, 1 reply; 12+ messages in thread
From: James @ 2014-09-16 19:58 UTC (permalink / raw
To: gentoo-user
Joseph <syscon780 <at> gmail.com> writes:
> >I am starting to wonder.
> >How exactly do you upgrade the other machines?
> I rsync one local server and all other machine are rsync to it.
> My main idea is trying not to introduce to many newer versions packages
> as in the past I've notice that that could cause the problem.
> The is no need for sarcasm. I basically do what works and I do
> learn from my experience (sometimes :-/).
Joseph,
Folks that work on precise computer problems are often "raw" with
one another. "Sarcasm" is an ointment that soothes the pain
of running Gentoo. Verbal abuse develops "thick skin" and most
here on Gentoo User have "thick skin", imho. Devs on this
list often question the gentoo-user base to ferret out if they
need to modify docs, codes or semantics at Gentoo, or if the user
needs. Sometime it does resemble a court room.
"Alan's school of admin abuse" type of treatment to motivate
an excellent user base is not uncommon.
That said, the amount of questions and bandwidth you have incurred
on this group, does warrant administrative incursion into you
admin policies, imho. Maybe, just maybe, folks actually care
that you are wisely successful with Gentoo?
For example since you are distributing, you really need to keep
binaries packages on at least one system. I nuked python, some
years ago. It was only the files on another similar system that
prevent me form a new installation of the system.
Besides, I rather think you are being "groomed" to become a gentoo
dev, so you can abuse the rest of of (gentoo users) commoners?
hth,
James
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: gentoo
2014-09-16 19:58 ` James
@ 2014-09-16 20:23 ` Joseph
2014-09-16 20:42 ` Alan McKinnon
2014-09-16 21:28 ` James
0 siblings, 2 replies; 12+ messages in thread
From: Joseph @ 2014-09-16 20:23 UTC (permalink / raw
To: gentoo-user
On 09/16/14 19:58, James wrote:
[snip]
>
>Folks that work on precise computer problems are often "raw" with
>one another. "Sarcasm" is an ointment that soothes the pain
>of running Gentoo. Verbal abuse develops "thick skin" and most
>here on Gentoo User have "thick skin", imho. Devs on this
>list often question the gentoo-user base to ferret out if they
>need to modify docs, codes or semantics at Gentoo, or if the user
>needs. Sometime it does resemble a court room.
>
> "Alan's school of admin abuse" type of treatment to motivate
>an excellent user base is not uncommon.
>
>That said, the amount of questions and bandwidth you have incurred
>on this group, does warrant administrative incursion into you
>admin policies, imho. Maybe, just maybe, folks actually care
>that you are wisely successful with Gentoo?
>
>For example since you are distributing, you really need to keep
>binaries packages on at least one system. I nuked python, some
>years ago. It was only the files on another similar system that
>prevent me form a new installation of the system.
>
>Besides, I rather think you are being "groomed" to become a gentoo
>dev, so you can abuse the rest of of (gentoo users) commoners?
>
>
>hth,
>James
Thank for suggestions, yes I usually keep the binaries for as long as I have enough room on "/" :-)
If I'm short on space I periodically nuke them. I've manged to keep the system going for the last 10-years
and keep my own help-file.txt (notes) how to solve certain problem (but not all :-/)
I sometime clean the distribution files with this command (I'm sure there might be a better way).
-----------------
cd /usr/portage/distfiles
and run this command:
(emerge -epf world 2>&1 | perl -ne '$f=join("\n", m@\w://[^\s]+/([^\s]+)@g); print "$f\n" if $f' | sort -u; ls -f) | sort | uniq -c | perl -ane 'print "$F[1]\n" if
$F[0]==1 && -f $F[1]' | xargs rm -f
------------------
Regarding keeping the binaries, I'll need to learn how to install compiled binaries from another box. Never, had a chance to do it yet.
--
Joseph
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: gentoo
2014-09-16 20:23 ` Joseph
@ 2014-09-16 20:42 ` Alan McKinnon
2014-09-16 21:28 ` James
1 sibling, 0 replies; 12+ messages in thread
From: Alan McKinnon @ 2014-09-16 20:42 UTC (permalink / raw
To: gentoo-user
On 16/09/2014 22:23, Joseph wrote:
> On 09/16/14 19:58, James wrote:
> [snip]
>>
>> Folks that work on precise computer problems are often "raw" with
>> one another. "Sarcasm" is an ointment that soothes the pain
>> of running Gentoo. Verbal abuse develops "thick skin" and most
>> here on Gentoo User have "thick skin", imho. Devs on this
>> list often question the gentoo-user base to ferret out if they
>> need to modify docs, codes or semantics at Gentoo, or if the user
>> needs. Sometime it does resemble a court room.
>>
>> "Alan's school of admin abuse" type of treatment to motivate
>> an excellent user base is not uncommon.
>>
>> That said, the amount of questions and bandwidth you have incurred
>> on this group, does warrant administrative incursion into you
>> admin policies, imho. Maybe, just maybe, folks actually care
>> that you are wisely successful with Gentoo?
>>
>> For example since you are distributing, you really need to keep
>> binaries packages on at least one system. I nuked python, some
>> years ago. It was only the files on another similar system that
>> prevent me form a new installation of the system.
>>
>> Besides, I rather think you are being "groomed" to become a gentoo
>> dev, so you can abuse the rest of of (gentoo users) commoners?
>>
>>
>> hth,
>> James
>
> Thank for suggestions, yes I usually keep the binaries for as long as I
> have enough room on "/" :-)
> If I'm short on space I periodically nuke them. I've manged to keep the
> system going for the last 10-years
> and keep my own help-file.txt (notes) how to solve certain problem (but
> not all :-/)
>
> I sometime clean the distribution files with this command (I'm sure
> there might be a better way).
> -----------------
> cd /usr/portage/distfiles
>
> and run this command:
> (emerge -epf world 2>&1 | perl -ne '$f=join("\n",
> m@\w://[^\s]+/([^\s]+)@g); print "$f\n" if $f' | sort -u; ls -f) | sort
> | uniq -c | perl -ane 'print "$F[1]\n" if $F[0]==1 && -f $F[1]' | xargs
> rm -f
eclean (in package gentoolkit)
> ------------------
>
> Regarding keeping the binaries, I'll need to learn how to install
> compiled binaries from another box. Never, had a chance to do it yet.
scp/rsync/whatever from one source to $PKGDIR on dest then
emerge -k (or -K depending if you want to fall back to regular compile
from source or not)
or, nfs mount $PKGDIR on the source to $PKGDIR on the dest machine and
you don't have to scp/rysnc
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-user] Re: gentoo
2014-09-16 20:23 ` Joseph
2014-09-16 20:42 ` Alan McKinnon
@ 2014-09-16 21:28 ` James
1 sibling, 0 replies; 12+ messages in thread
From: James @ 2014-09-16 21:28 UTC (permalink / raw
To: gentoo-user
Joseph <syscon780 <at> gmail.com> writes:
> Regarding keeping the binaries, I'll need to learn how to install
> compiled binaries from another box.
> Never, had a chance to do it yet.
DIRT simple (general scheme; ymmv).
Look at the working system. Determine where the binaries go, symlinks
etc etc.
"scp" the file(s) over to the damaged box (ip addresss/filepath to ip
address/filepath.
Sometimes you have to do other things (source a file, nuke/reinstate
a symlink etc etc.
That's all I've had to do on similar CPU_arch machines.
I try and keep profiles and use flags similar and put
other use flag in package specific locations.
scp is my buddy!
hth,
James
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2014-09-16 21:29 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <200412051508.59017.dlw@hei.net>
2004-12-06 0:24 ` [gentoo-user] Re: gentoo Gabriel M. Beddingfield
2004-12-06 5:14 ` Ow Mun Heng
2014-09-16 4:29 [gentoo-user] gentoo Joseph
2014-09-16 14:18 ` [gentoo-user] gentoo James
2014-09-16 15:02 ` Joseph
2014-09-16 15:57 ` J. Roeleveld
2014-09-16 18:05 ` Joseph
2014-09-16 19:11 ` Alan McKinnon
2014-09-16 19:38 ` Joseph
2014-09-16 19:58 ` James
2014-09-16 20:23 ` Joseph
2014-09-16 20:42 ` Alan McKinnon
2014-09-16 21:28 ` James
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox