* [libre-riscv-dev] dns entries for talos server & server maintenance
@ 2020-05-22 21:21 Jacob Lifshay
2020-05-22 22:54 ` Luke Kenneth Casson Leighton
0 siblings, 1 reply; 6+ messages in thread
From: Jacob Lifshay @ 2020-05-22 21:21 UTC (permalink / raw)
To: Libre-RISCV General Development
to make it easier to connect to without having to remember the IP
address, I think we should add a dns entry for the talos server, I'd
suggest talos1.libre-soc.org. As a reminder, the IP address is
23.155.224.75
Also, someone forgot to enable automatic updates, so I updated the
software manually. Sorry if that broke something.
The server needs to be rebooted to use the new kernel that got
installed, so, Luke, I'll let you do that since you have stuff running
on it.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [libre-riscv-dev] dns entries for talos server & server maintenance
2020-05-22 21:21 [libre-riscv-dev] dns entries for talos server & server maintenance Jacob Lifshay
@ 2020-05-22 22:54 ` Luke Kenneth Casson Leighton
2020-05-22 23:01 ` Luke Kenneth Casson Leighton
0 siblings, 1 reply; 6+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-05-22 22:54 UTC (permalink / raw)
To: Libre-RISCV General Development
On Fri, May 22, 2020 at 10:21 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> to make it easier to connect to without having to remember the IP
> address, I think we should add a dns entry for the talos server, I'd
> suggest talos1.libre-soc.org. As a reminder, the IP address is
> 23.155.224.75
good idea.
> Also, someone forgot to enable automatic updates,
no, it was not "forgotten" - the absolute last thing we need is
"automatically introduced problems", particularly if - especially as -
the setup is using debian/testing.
debian/stable and "production" servers with carefully pre-planned
setups, or "toys" where nobody else is relying on it, or "your own
personal machine" is absolutely fine to enable potentially-damaging
"automatic updates".
> so I updated the
> software manually. Sorry if that broke something.
yes please don't do that without consulting everyone, first.
to give you some idea: the notification schedule that servers used to
be on at Imperial College was 90 days advance warning of softtware
updates, and one year for a reboot.
> The server needs to be rebooted to use the new kernel that got
> installed,
which is precisely why you don't "upgrade" a server, especially
without notice or discussion. we are now critically dependent on that
machine having 100% uninterrupted power.
if there is a power-outage in the data centre that causes an
unscheduled reboot, resulting in that machine going down, and we are
critically reliant on it for testing at the time, someone has to drop
everything they're doing, scramble to look up the procedure for
logging in to the virtual console, and then work out how to recover
the machine.
> so, Luke, I'll let you do that since you have stuff running
> on it.
no, i'm not going to reboot it, because if it doesn't come back up
someone has to spend the time recovering it.
lesson learned: never "upgrade" servers without consulting people, ok?
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [libre-riscv-dev] dns entries for talos server & server maintenance
2020-05-22 22:54 ` Luke Kenneth Casson Leighton
@ 2020-05-22 23:01 ` Luke Kenneth Casson Leighton
2020-05-22 23:06 ` Luke Kenneth Casson Leighton
2020-05-23 1:08 ` Jacob Lifshay
0 siblings, 2 replies; 6+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-05-22 23:01 UTC (permalink / raw)
To: Libre-RISCV General Development
just logged in: yes it's definitely running debian/testing: *really* -
don't ever do an "apt-get dist-upgrade" or any form of automated
upgrade on a debian/testing system, ever.
the only thing that should ever be done on a debian/testing system is
to see if an "apt-get install {package}" will try to replace, upgrade
or remove any packages, to TERMINATE that and CAREFULLY review the
list of package alterations.
given that this is a shared server that is also a critical resource,
that process involves consulting everyone who may be affected, ok?
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [libre-riscv-dev] dns entries for talos server & server maintenance
2020-05-22 23:01 ` Luke Kenneth Casson Leighton
@ 2020-05-22 23:06 ` Luke Kenneth Casson Leighton
2020-05-23 1:08 ` Jacob Lifshay
1 sibling, 0 replies; 6+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-05-22 23:06 UTC (permalink / raw)
To: Libre-RISCV General Development
the good news is, you prompted me to log in and add michael's ssh key
to the machine. he also needs to run some tests.
it's ssh -p922 mtnolan@talos1.libre-soc.org, michael.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [libre-riscv-dev] dns entries for talos server & server maintenance
2020-05-22 23:01 ` Luke Kenneth Casson Leighton
2020-05-22 23:06 ` Luke Kenneth Casson Leighton
@ 2020-05-23 1:08 ` Jacob Lifshay
2020-05-23 2:46 ` Luke Kenneth Casson Leighton
1 sibling, 1 reply; 6+ messages in thread
From: Jacob Lifshay @ 2020-05-23 1:08 UTC (permalink / raw)
To: Libre-RISCV General Development
On Fri, May 22, 2020 at 4:02 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> just logged in: yes it's definitely running debian/testing: *really* -
> don't ever do an "apt-get dist-upgrade" or any form of automated
> upgrade on a debian/testing system, ever.
Ok, sorry. I saw stable in the apt lists and assumed it was on debian
stable. Also, the debian security source isn't working for some reason
(missing file? got a 404), so that source didn't work.
So, the list of changes is in /var/log/apt/term.log I think.
>
> the only thing that should ever be done on a debian/testing system is
> to see if an "apt-get install {package}" will try to replace, upgrade
> or remove any packages, to TERMINATE that and CAREFULLY review the
> list of package alterations.
>
> given that this is a shared server that is also a critical resource,
> that process involves consulting everyone who may be affected, ok?
Ok.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [libre-riscv-dev] dns entries for talos server & server maintenance
2020-05-23 1:08 ` Jacob Lifshay
@ 2020-05-23 2:46 ` Luke Kenneth Casson Leighton
0 siblings, 0 replies; 6+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-05-23 2:46 UTC (permalink / raw)
To: Libre-RISCV General Development
On Saturday, May 23, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Fri, May 22, 2020 at 4:02 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> >
> > just logged in: yes it's definitely running debian/testing: *really* -
> > don't ever do an "apt-get dist-upgrade" or any form of automated
> > upgrade on a debian/testing system, ever.
>
> Ok, sorry. I saw stable in the apt lists and assumed it was on debian
> stable.
the list is amalgamated, including from /etc/apt/sources.list.d so it is
necessary to really really pay attention and read every line.
the way debian works is that unless apt pinning is active, the highest
lexicographically named version of a package is picked.
so with stable *and* testing in the list, and no apt pin preferences file,
testing gets picked... unless a testing package has not been built.
>
> Also, the debian security source isn't working for some reason
> (missing file? got a 404), so that source didn't work.
either it doesn't actually exist or it is spelled wrong.
>
> So, the list of changes is in /var/log/apt/term.log I think.
> >
> > the only thing that should ever be done on a debian/testing system is
> > to see if an "apt-get install {package}" will try to replace, upgrade
> > or remove any packages, to TERMINATE that and CAREFULLY review the
> > list of package alterations.
> >
> > given that this is a shared server that is also a critical resource,
> > that process involves consulting everyone who may be affected, ok?
>
> Ok.
>
> Jacob
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, back to index
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-22 21:21 [libre-riscv-dev] dns entries for talos server & server maintenance Jacob Lifshay
2020-05-22 22:54 ` Luke Kenneth Casson Leighton
2020-05-22 23:01 ` Luke Kenneth Casson Leighton
2020-05-22 23:06 ` Luke Kenneth Casson Leighton
2020-05-23 1:08 ` Jacob Lifshay
2020-05-23 2:46 ` Luke Kenneth Casson Leighton
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git