![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
piranhahad the first power outage of the season, and it was long; 6+ hours. got to burn some candles and make tea on the camp stove.
thanks to the UPSs, everything shut down cleanly. but when the power finally came back up, aegis didn't. got an error message from LILO i had never seen before: "EBDA is big: kernel setup stack overlaps LILO second stage."
it really sucks when the gateway goes down, because it runs both the connection to the outside as also the inside network. and it's been a while since i last needed to connect another system to the ADSL. telus permits us two MAC addresses, but of course the second system was still set to my laptop, which no longer has a functioning screen. i wasn't looking forward to figuring out how to change the second MAC address without having net access (it involves finding a working modem and the right dialup numbers). but good news, telus has actually spiffed up its network, and as soon as one connects, one gets an IP address within a local network, and they pop up the registration website for the MAC addresses. this is so much better than it used to be. i should remember to write them with my compliments.
so now i am on drynwyn connected to the ADSL and finding out what i can do about the LILO problem. this is a good time for that rescue floppy. i actually have one, yay. well, i had one. it seems to have gone bad just sitting around for more than a year without being used. the slightly older rescue floppy is also bad. clearly my sysadmin skills need some upgrading; i should build rescue CDs, since we only have one floppy drive left anyway, and floppies are really old tech now.
that's giving me the opportunity to learn about the mac's capabilities in the CD burning department. so far i've burned one that's not bootable, and have figured out that i need to use disk utility instead. alright. now downloading somebody else's rescue image.
the main problem with running debian on our gateway has turned out to be that things don't go wrong often enough, and i therefore don't get a lot of practice solving problems, and that means i have to do research every time. i guess it's back to documenting everything in detail, and in hardcopy this time.
thanks to the UPSs, everything shut down cleanly. but when the power finally came back up, aegis didn't. got an error message from LILO i had never seen before: "EBDA is big: kernel setup stack overlaps LILO second stage."
it really sucks when the gateway goes down, because it runs both the connection to the outside as also the inside network. and it's been a while since i last needed to connect another system to the ADSL. telus permits us two MAC addresses, but of course the second system was still set to my laptop, which no longer has a functioning screen. i wasn't looking forward to figuring out how to change the second MAC address without having net access (it involves finding a working modem and the right dialup numbers). but good news, telus has actually spiffed up its network, and as soon as one connects, one gets an IP address within a local network, and they pop up the registration website for the MAC addresses. this is so much better than it used to be. i should remember to write them with my compliments.
so now i am on drynwyn connected to the ADSL and finding out what i can do about the LILO problem. this is a good time for that rescue floppy. i actually have one, yay. well, i had one. it seems to have gone bad just sitting around for more than a year without being used. the slightly older rescue floppy is also bad. clearly my sysadmin skills need some upgrading; i should build rescue CDs, since we only have one floppy drive left anyway, and floppies are really old tech now.
that's giving me the opportunity to learn about the mac's capabilities in the CD burning department. so far i've burned one that's not bootable, and have figured out that i need to use disk utility instead. alright. now downloading somebody else's rescue image.
the main problem with running debian on our gateway has turned out to be that things don't go wrong often enough, and i therefore don't get a lot of practice solving problems, and that means i have to do research every time. i guess it's back to documenting everything in detail, and in hardcopy this time.