Menu
▾
▴
astlinux-devel — The AstLinux development environment, compilation, etc
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
(41) |
Apr
(35) |
May
(18) |
Jun
(5) |
Jul
(4) |
Aug
(37) |
Sep
(9) |
Oct
(20) |
Nov
(50) |
Dec
(217) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(212) |
Feb
(76) |
Mar
(113) |
Apr
(88) |
May
(130) |
Jun
(54) |
Jul
(208) |
Aug
(223) |
Sep
(112) |
Oct
(63) |
Nov
(131) |
Dec
(103) |
| 2010 |
Jan
(247) |
Feb
(130) |
Mar
(43) |
Apr
(92) |
May
(40) |
Jun
(43) |
Jul
(43) |
Aug
(80) |
Sep
(44) |
Oct
(74) |
Nov
(21) |
Dec
(46) |
| 2011 |
Jan
(36) |
Feb
(11) |
Mar
(21) |
Apr
(33) |
May
(4) |
Jun
(12) |
Jul
(5) |
Aug
(20) |
Sep
|
Oct
(64) |
Nov
(26) |
Dec
(71) |
| 2012 |
Jan
(13) |
Feb
(24) |
Mar
(11) |
Apr
(2) |
May
(10) |
Jun
(5) |
Jul
(13) |
Aug
(7) |
Sep
(26) |
Oct
(22) |
Nov
(17) |
Dec
(16) |
| 2013 |
Jan
(6) |
Feb
(6) |
Mar
(6) |
Apr
(8) |
May
(20) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(18) |
Oct
(3) |
Nov
(14) |
Dec
(33) |
| 2014 |
Jan
(26) |
Feb
(6) |
Mar
(69) |
Apr
(10) |
May
|
Jun
(8) |
Jul
(18) |
Aug
(22) |
Sep
(19) |
Oct
(17) |
Nov
|
Dec
(4) |
| 2015 |
Jan
(14) |
Feb
(18) |
Mar
|
Apr
|
May
(26) |
Jun
(8) |
Jul
(9) |
Aug
(10) |
Sep
(15) |
Oct
(2) |
Nov
(30) |
Dec
(33) |
| 2016 |
Jan
(1) |
Feb
(24) |
Mar
(19) |
Apr
(1) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(20) |
Oct
(5) |
Nov
(14) |
Dec
(4) |
| 2017 |
Jan
(15) |
Feb
(35) |
Mar
(10) |
Apr
(9) |
May
(14) |
Jun
(33) |
Jul
(1) |
Aug
(27) |
Sep
(7) |
Oct
|
Nov
(10) |
Dec
(15) |
| 2018 |
Jan
(29) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(8) |
Sep
(11) |
Oct
(22) |
Nov
(9) |
Dec
(13) |
| 2019 |
Jan
(1) |
Feb
(7) |
Mar
(3) |
Apr
(21) |
May
(34) |
Jun
(36) |
Jul
(18) |
Aug
(17) |
Sep
(19) |
Oct
(8) |
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
(29) |
May
(50) |
Jun
(8) |
Jul
(2) |
Aug
(10) |
Sep
(1) |
Oct
(7) |
Nov
(9) |
Dec
(19) |
| 2021 |
Jan
(2) |
Feb
(9) |
Mar
(6) |
Apr
(21) |
May
(13) |
Jun
(11) |
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
(26) |
Nov
(2) |
Dec
(16) |
| 2022 |
Jan
(8) |
Feb
(7) |
Mar
(1) |
Apr
(13) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
(2) |
Feb
(3) |
Mar
(16) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(13) |
Sep
(8) |
Oct
(6) |
Nov
(4) |
Dec
|
| 2024 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(11) |
May
(1) |
Jun
(9) |
Jul
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Lonnie A. <li...@lo...> - 2021-04-01 21:17:37
|
I said "... genx86_64-serial board does *not* have ...", not sure if that was clear from your reply. Lonnie > On Apr 1, 2021, at 4:00 PM, Michael Knill <mic...@ip...> wrote: > > That will do it! Thanks all. > > Regards > Michael Knill > > On 2/4/21, 7:41 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > The genx86_64-serial board does not have a kernel built for HyperV. > > Lonnie > > >> On Apr 1, 2021, at 3:29 PM, Michael Knill <mic...@ip...> wrote: >> >> Yes maybe broken was a bit harsh and I agree that it will not preclude us from using Azure as it's a nice to have only. >> Pretty sure that a Serial Console is the only option for Azure (believe it or not). >> >> So are there enough differences between the genx86_64-vm and genx86_64-serial board types to not use the serial board type in Azure assuming its built in HyperV? >> >> Regards >> Michael Knill >> >> On 2/4/21, 12:09 am, "Lonnie Abelbeck" <li...@lo...> wrote: >> >> Hi Michael, >> >> "broken" seems a bit harsh, possibly I did not explain this missing-feature properly ... >> >> AstLinux 1.3.10 through 1.4.2 ignores any user edits to the /etc/inittab file, rather it always uses the default /etc/inittab file. >> >> Among other things, the /etc/inittab sets: >> >> 1) A serial console at 115200 baud for the genx86_64-serial board type. >> >> 2) A video console for genx86_64 and genx86_64-vm board types. >> >> The default /etc/inittab is what most users want, which is generated according to the board type. >> >> >> There are a couple special cases where editing the /etc/inittab via unionfs is desired: >> >> 3) Set the serial console baud rate to something other than 115200 baud (setconsole-speed-tty). >> >> 4) Add a serial console for a genx86_64 or genx86_64-vm board type. >> >> For over 9 months this missing-feature was not noticed, so #3 or #4 must not be commonly used. I have a serial console added to a Linode VM, but haven't used it in 9 months ... so I did not notice. >> >> Michael, I'm happy you noticed :-) The project thanks you. >> >> Like David hinted to, I find it hard to believe an Azure VM does not support a web-based video console (ex. noVNC). Possibly the lacking of #4 is not a blocker for you ? >> >> Lonnie >> >> >> >>> On Apr 1, 2021, at 12:35 AM, Michael Knill <mic...@ip...> wrote: >>> >>> Bummer. Thanks Lonnie. We will need to wait for the next release and hope we don't break it in the meantime! >>> I haven’t checked but is the serial board type broken as well? If not then could I build it with this? >>> >>> Regards >>> Michael Knill >>> >>> On 1/4/21, 2:54 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >>> >>> Hi Michael, >>> >>> I committed a fix in the upstream repo: >>> >>> https://github.com/astlinux-project/astlinux/commit/79576e557d0d18b10d452e6c9211c4379f7e68f9 >>> >>> A side-effect to the FUSE unionfs switch left any changes to /etc/inittab ignored since ASTURW is now mounted after >>> the initrd runs, and the initrd calls /sbin/init. >>> >>> This would also fix issues where the serial console baud rate was not the default 115200 by using the setconsole-speed-tty command. >>> >>> Michael, the bad news for you, implementing the new initrd image would not be easy using the older AstLinux 1.3.10, barring building you own image. >>> >>> Someone could build a AstLinux 1.3.10 initrd.img with this fix (common across all board types), but packaging it would be somewhat tedious. >>> >>> Lonnie >>> >>> >>> >>> >>>> On Mar 31, 2021, at 3:29 PM, Lonnie Abelbeck <li...@lo...> wrote: >>>> >>>> Hi Michael, >>>> >>>> Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ... >>>> >>>> linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color >>>> getty: setsid: Operation not permitted >>>> >>>> Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script. >>>> >>>> Let me do some testing and think about how to fix this. Hopefully. >>>> >>>> Lonnie >>>> >>>> >>>> >>>>> On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote: >>>>> >>>>> Hi Group >>>>> >>>>> In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again. >>>>> One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output. >>>>> I am using the 1.3.10 VM image. >>>>> >>>>> Any ideas? Has something changed in 1.3.10? >>>>> >>>>> Regards >>>>> Michael Knill >>>>> >>>>> On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote: >>>>> >>>>> Yay serial console is now working. >>>>> Thanks for that. I figured it would be easy. >>>>> >>>>> Regards >>>>> Michael Knill >>>>> >>>>> On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote: >>>>> >>>>> Hi Michael, >>>>> >>>>> Great to hear ! >>>>> >>>>> If their serial setup is anything similar to Linode's >>>>> >>>>> https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode >>>>> >>>>> Search for "Out-of-Band Console Access" >>>>> >>>>> Basically a simple edit of the /etc/inittab file. >>>>> >>>>> >>>>>> Also would you like me to write up an article for the build process? >>>>> >>>>> Is it pretty straight-forward? sure, any helpful documentation is great. >>>>> >>>>> Lonnie >>>>> >>>>> >>>>> >>>>>> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote: >>>>>> >>>>>> Hi Guys >>>>>> >>>>>> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back. >>>>>> >>>>>> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up? >>>>>> >>>>>> Also would you like me to write up an article for the build process? >>>>>> >>>>>> Thanks >>>>>> >>>>>> Regards >>>>>> Michael Knill >>>>>> _______________________________________________ >>>>>> Astlinux-devel mailing list >>>>>> Ast...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Astlinux-devel mailing list >>>>> Ast...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>>>> >>>>> >>>>> _______________________________________________ >>>>> Astlinux-devel mailing list >>>>> Ast...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>>>> >>>>> >>>>> _______________________________________________ >>>>> Astlinux-devel mailing list >>>>> Ast...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>>> >>>> >>>> >>>> _______________________________________________ >>>> Astlinux-devel mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2021-04-01 21:00:35
|
That will do it! Thanks all.
Regards
Michael Knill
On 2/4/21, 7:41 am, "Lonnie Abelbeck" <li...@lo...> wrote:
The genx86_64-serial board does not have a kernel built for HyperV.
Lonnie
> On Apr 1, 2021, at 3:29 PM, Michael Knill <mic...@ip...> wrote:
>
> Yes maybe broken was a bit harsh and I agree that it will not preclude us from using Azure as it's a nice to have only.
> Pretty sure that a Serial Console is the only option for Azure (believe it or not).
>
> So are there enough differences between the genx86_64-vm and genx86_64-serial board types to not use the serial board type in Azure assuming its built in HyperV?
>
> Regards
> Michael Knill
>
> On 2/4/21, 12:09 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>
> Hi Michael,
>
> "broken" seems a bit harsh, possibly I did not explain this missing-feature properly ...
>
> AstLinux 1.3.10 through 1.4.2 ignores any user edits to the /etc/inittab file, rather it always uses the default /etc/inittab file.
>
> Among other things, the /etc/inittab sets:
>
> 1) A serial console at 115200 baud for the genx86_64-serial board type.
>
> 2) A video console for genx86_64 and genx86_64-vm board types.
>
> The default /etc/inittab is what most users want, which is generated according to the board type.
>
>
> There are a couple special cases where editing the /etc/inittab via unionfs is desired:
>
> 3) Set the serial console baud rate to something other than 115200 baud (setconsole-speed-tty).
>
> 4) Add a serial console for a genx86_64 or genx86_64-vm board type.
>
> For over 9 months this missing-feature was not noticed, so #3 or #4 must not be commonly used. I have a serial console added to a Linode VM, but haven't used it in 9 months ... so I did not notice.
>
> Michael, I'm happy you noticed :-) The project thanks you.
>
> Like David hinted to, I find it hard to believe an Azure VM does not support a web-based video console (ex. noVNC). Possibly the lacking of #4 is not a blocker for you ?
>
> Lonnie
>
>
>
>> On Apr 1, 2021, at 12:35 AM, Michael Knill <mic...@ip...> wrote:
>>
>> Bummer. Thanks Lonnie. We will need to wait for the next release and hope we don't break it in the meantime!
>> I haven’t checked but is the serial board type broken as well? If not then could I build it with this?
>>
>> Regards
>> Michael Knill
>>
>> On 1/4/21, 2:54 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
>>
>> Hi Michael,
>>
>> I committed a fix in the upstream repo:
>>
>> https://github.com/astlinux-project/astlinux/commit/79576e557d0d18b10d452e6c9211c4379f7e68f9
>>
>> A side-effect to the FUSE unionfs switch left any changes to /etc/inittab ignored since ASTURW is now mounted after
>> the initrd runs, and the initrd calls /sbin/init.
>>
>> This would also fix issues where the serial console baud rate was not the default 115200 by using the setconsole-speed-tty command.
>>
>> Michael, the bad news for you, implementing the new initrd image would not be easy using the older AstLinux 1.3.10, barring building you own image.
>>
>> Someone could build a AstLinux 1.3.10 initrd.img with this fix (common across all board types), but packaging it would be somewhat tedious.
>>
>> Lonnie
>>
>>
>>
>>
>>> On Mar 31, 2021, at 3:29 PM, Lonnie Abelbeck <li...@lo...> wrote:
>>>
>>> Hi Michael,
>>>
>>> Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ...
>>>
>>> linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color
>>> getty: setsid: Operation not permitted
>>>
>>> Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script.
>>>
>>> Let me do some testing and think about how to fix this. Hopefully.
>>>
>>> Lonnie
>>>
>>>
>>>
>>>> On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote:
>>>>
>>>> Hi Group
>>>>
>>>> In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again.
>>>> One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output.
>>>> I am using the 1.3.10 VM image.
>>>>
>>>> Any ideas? Has something changed in 1.3.10?
>>>>
>>>> Regards
>>>> Michael Knill
>>>>
>>>> On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote:
>>>>
>>>> Yay serial console is now working.
>>>> Thanks for that. I figured it would be easy.
>>>>
>>>> Regards
>>>> Michael Knill
>>>>
>>>> On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> Great to hear !
>>>>
>>>> If their serial setup is anything similar to Linode's
>>>>
>>>> https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode
>>>>
>>>> Search for "Out-of-Band Console Access"
>>>>
>>>> Basically a simple edit of the /etc/inittab file.
>>>>
>>>>
>>>>> Also would you like me to write up an article for the build process?
>>>>
>>>> Is it pretty straight-forward? sure, any helpful documentation is great.
>>>>
>>>> Lonnie
>>>>
>>>>
>>>>
>>>>> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote:
>>>>>
>>>>> Hi Guys
>>>>>
>>>>> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back.
>>>>>
>>>>> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up?
>>>>>
>>>>> Also would you like me to write up an article for the build process?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Regards
>>>>> Michael Knill
>>>>> _______________________________________________
>>>>> Astlinux-devel mailing list
>>>>> Ast...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Astlinux-devel mailing list
>>>> Ast...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>>
>>>>
>>>> _______________________________________________
>>>> Astlinux-devel mailing list
>>>> Ast...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>>
>>>>
>>>> _______________________________________________
>>>> Astlinux-devel mailing list
>>>> Ast...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>
>>>
>>>
>>> _______________________________________________
>>> Astlinux-devel mailing list
>>> Ast...@li...
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>>
>>
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>>
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2021-04-01 20:41:07
|
The genx86_64-serial board does not have a kernel built for HyperV. Lonnie > On Apr 1, 2021, at 3:29 PM, Michael Knill <mic...@ip...> wrote: > > Yes maybe broken was a bit harsh and I agree that it will not preclude us from using Azure as it's a nice to have only. > Pretty sure that a Serial Console is the only option for Azure (believe it or not). > > So are there enough differences between the genx86_64-vm and genx86_64-serial board types to not use the serial board type in Azure assuming its built in HyperV? > > Regards > Michael Knill > > On 2/4/21, 12:09 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > "broken" seems a bit harsh, possibly I did not explain this missing-feature properly ... > > AstLinux 1.3.10 through 1.4.2 ignores any user edits to the /etc/inittab file, rather it always uses the default /etc/inittab file. > > Among other things, the /etc/inittab sets: > > 1) A serial console at 115200 baud for the genx86_64-serial board type. > > 2) A video console for genx86_64 and genx86_64-vm board types. > > The default /etc/inittab is what most users want, which is generated according to the board type. > > > There are a couple special cases where editing the /etc/inittab via unionfs is desired: > > 3) Set the serial console baud rate to something other than 115200 baud (setconsole-speed-tty). > > 4) Add a serial console for a genx86_64 or genx86_64-vm board type. > > For over 9 months this missing-feature was not noticed, so #3 or #4 must not be commonly used. I have a serial console added to a Linode VM, but haven't used it in 9 months ... so I did not notice. > > Michael, I'm happy you noticed :-) The project thanks you. > > Like David hinted to, I find it hard to believe an Azure VM does not support a web-based video console (ex. noVNC). Possibly the lacking of #4 is not a blocker for you ? > > Lonnie > > > >> On Apr 1, 2021, at 12:35 AM, Michael Knill <mic...@ip...> wrote: >> >> Bummer. Thanks Lonnie. We will need to wait for the next release and hope we don't break it in the meantime! >> I haven’t checked but is the serial board type broken as well? If not then could I build it with this? >> >> Regards >> Michael Knill >> >> On 1/4/21, 2:54 pm, "Lonnie Abelbeck" <li...@lo...> wrote: >> >> Hi Michael, >> >> I committed a fix in the upstream repo: >> >> https://github.com/astlinux-project/astlinux/commit/79576e557d0d18b10d452e6c9211c4379f7e68f9 >> >> A side-effect to the FUSE unionfs switch left any changes to /etc/inittab ignored since ASTURW is now mounted after >> the initrd runs, and the initrd calls /sbin/init. >> >> This would also fix issues where the serial console baud rate was not the default 115200 by using the setconsole-speed-tty command. >> >> Michael, the bad news for you, implementing the new initrd image would not be easy using the older AstLinux 1.3.10, barring building you own image. >> >> Someone could build a AstLinux 1.3.10 initrd.img with this fix (common across all board types), but packaging it would be somewhat tedious. >> >> Lonnie >> >> >> >> >>> On Mar 31, 2021, at 3:29 PM, Lonnie Abelbeck <li...@lo...> wrote: >>> >>> Hi Michael, >>> >>> Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ... >>> >>> linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color >>> getty: setsid: Operation not permitted >>> >>> Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script. >>> >>> Let me do some testing and think about how to fix this. Hopefully. >>> >>> Lonnie >>> >>> >>> >>>> On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Hi Group >>>> >>>> In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again. >>>> One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output. >>>> I am using the 1.3.10 VM image. >>>> >>>> Any ideas? Has something changed in 1.3.10? >>>> >>>> Regards >>>> Michael Knill >>>> >>>> On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote: >>>> >>>> Yay serial console is now working. >>>> Thanks for that. I figured it would be easy. >>>> >>>> Regards >>>> Michael Knill >>>> >>>> On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote: >>>> >>>> Hi Michael, >>>> >>>> Great to hear ! >>>> >>>> If their serial setup is anything similar to Linode's >>>> >>>> https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode >>>> >>>> Search for "Out-of-Band Console Access" >>>> >>>> Basically a simple edit of the /etc/inittab file. >>>> >>>> >>>>> Also would you like me to write up an article for the build process? >>>> >>>> Is it pretty straight-forward? sure, any helpful documentation is great. >>>> >>>> Lonnie >>>> >>>> >>>> >>>>> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote: >>>>> >>>>> Hi Guys >>>>> >>>>> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back. >>>>> >>>>> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up? >>>>> >>>>> Also would you like me to write up an article for the build process? >>>>> >>>>> Thanks >>>>> >>>>> Regards >>>>> Michael Knill >>>>> _______________________________________________ >>>>> Astlinux-devel mailing list >>>>> Ast...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>>> >>>> >>>> >>>> _______________________________________________ >>>> Astlinux-devel mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>>> >>>> >>>> _______________________________________________ >>>> Astlinux-devel mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>>> >>>> >>>> _______________________________________________ >>>> Astlinux-devel mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2021-04-01 20:30:00
|
Yes maybe broken was a bit harsh and I agree that it will not preclude us from using Azure as it's a nice to have only.
Pretty sure that a Serial Console is the only option for Azure (believe it or not).
So are there enough differences between the genx86_64-vm and genx86_64-serial board types to not use the serial board type in Azure assuming its built in HyperV?
Regards
Michael Knill
On 2/4/21, 12:09 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Michael,
"broken" seems a bit harsh, possibly I did not explain this missing-feature properly ...
AstLinux 1.3.10 through 1.4.2 ignores any user edits to the /etc/inittab file, rather it always uses the default /etc/inittab file.
Among other things, the /etc/inittab sets:
1) A serial console at 115200 baud for the genx86_64-serial board type.
2) A video console for genx86_64 and genx86_64-vm board types.
The default /etc/inittab is what most users want, which is generated according to the board type.
There are a couple special cases where editing the /etc/inittab via unionfs is desired:
3) Set the serial console baud rate to something other than 115200 baud (setconsole-speed-tty).
4) Add a serial console for a genx86_64 or genx86_64-vm board type.
For over 9 months this missing-feature was not noticed, so #3 or #4 must not be commonly used. I have a serial console added to a Linode VM, but haven't used it in 9 months ... so I did not notice.
Michael, I'm happy you noticed :-) The project thanks you.
Like David hinted to, I find it hard to believe an Azure VM does not support a web-based video console (ex. noVNC). Possibly the lacking of #4 is not a blocker for you ?
Lonnie
> On Apr 1, 2021, at 12:35 AM, Michael Knill <mic...@ip...> wrote:
>
> Bummer. Thanks Lonnie. We will need to wait for the next release and hope we don't break it in the meantime!
> I haven’t checked but is the serial board type broken as well? If not then could I build it with this?
>
> Regards
> Michael Knill
>
> On 1/4/21, 2:54 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
>
> Hi Michael,
>
> I committed a fix in the upstream repo:
>
> https://github.com/astlinux-project/astlinux/commit/79576e557d0d18b10d452e6c9211c4379f7e68f9
>
> A side-effect to the FUSE unionfs switch left any changes to /etc/inittab ignored since ASTURW is now mounted after
> the initrd runs, and the initrd calls /sbin/init.
>
> This would also fix issues where the serial console baud rate was not the default 115200 by using the setconsole-speed-tty command.
>
> Michael, the bad news for you, implementing the new initrd image would not be easy using the older AstLinux 1.3.10, barring building you own image.
>
> Someone could build a AstLinux 1.3.10 initrd.img with this fix (common across all board types), but packaging it would be somewhat tedious.
>
> Lonnie
>
>
>
>
>> On Mar 31, 2021, at 3:29 PM, Lonnie Abelbeck <li...@lo...> wrote:
>>
>> Hi Michael,
>>
>> Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ...
>>
>> linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color
>> getty: setsid: Operation not permitted
>>
>> Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script.
>>
>> Let me do some testing and think about how to fix this. Hopefully.
>>
>> Lonnie
>>
>>
>>
>>> On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote:
>>>
>>> Hi Group
>>>
>>> In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again.
>>> One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output.
>>> I am using the 1.3.10 VM image.
>>>
>>> Any ideas? Has something changed in 1.3.10?
>>>
>>> Regards
>>> Michael Knill
>>>
>>> On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote:
>>>
>>> Yay serial console is now working.
>>> Thanks for that. I figured it would be easy.
>>>
>>> Regards
>>> Michael Knill
>>>
>>> On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>>>
>>> Hi Michael,
>>>
>>> Great to hear !
>>>
>>> If their serial setup is anything similar to Linode's
>>>
>>> https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode
>>>
>>> Search for "Out-of-Band Console Access"
>>>
>>> Basically a simple edit of the /etc/inittab file.
>>>
>>>
>>>> Also would you like me to write up an article for the build process?
>>>
>>> Is it pretty straight-forward? sure, any helpful documentation is great.
>>>
>>> Lonnie
>>>
>>>
>>>
>>>> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote:
>>>>
>>>> Hi Guys
>>>>
>>>> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back.
>>>>
>>>> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up?
>>>>
>>>> Also would you like me to write up an article for the build process?
>>>>
>>>> Thanks
>>>>
>>>> Regards
>>>> Michael Knill
>>>> _______________________________________________
>>>> Astlinux-devel mailing list
>>>> Ast...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>
>>>
>>>
>>> _______________________________________________
>>> Astlinux-devel mailing list
>>> Ast...@li...
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>
>>>
>>> _______________________________________________
>>> Astlinux-devel mailing list
>>> Ast...@li...
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>>
>>>
>>> _______________________________________________
>>> Astlinux-devel mailing list
>>> Ast...@li...
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>>
>>
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2021-04-01 13:09:08
|
Hi Michael, "broken" seems a bit harsh, possibly I did not explain this missing-feature properly ... AstLinux 1.3.10 through 1.4.2 ignores any user edits to the /etc/inittab file, rather it always uses the default /etc/inittab file. Among other things, the /etc/inittab sets: 1) A serial console at 115200 baud for the genx86_64-serial board type. 2) A video console for genx86_64 and genx86_64-vm board types. The default /etc/inittab is what most users want, which is generated according to the board type. There are a couple special cases where editing the /etc/inittab via unionfs is desired: 3) Set the serial console baud rate to something other than 115200 baud (setconsole-speed-tty). 4) Add a serial console for a genx86_64 or genx86_64-vm board type. For over 9 months this missing-feature was not noticed, so #3 or #4 must not be commonly used. I have a serial console added to a Linode VM, but haven't used it in 9 months ... so I did not notice. Michael, I'm happy you noticed :-) The project thanks you. Like David hinted to, I find it hard to believe an Azure VM does not support a web-based video console (ex. noVNC). Possibly the lacking of #4 is not a blocker for you ? Lonnie > On Apr 1, 2021, at 12:35 AM, Michael Knill <mic...@ip...> wrote: > > Bummer. Thanks Lonnie. We will need to wait for the next release and hope we don't break it in the meantime! > I haven’t checked but is the serial board type broken as well? If not then could I build it with this? > > Regards > Michael Knill > > On 1/4/21, 2:54 pm, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > I committed a fix in the upstream repo: > > https://github.com/astlinux-project/astlinux/commit/79576e557d0d18b10d452e6c9211c4379f7e68f9 > > A side-effect to the FUSE unionfs switch left any changes to /etc/inittab ignored since ASTURW is now mounted after > the initrd runs, and the initrd calls /sbin/init. > > This would also fix issues where the serial console baud rate was not the default 115200 by using the setconsole-speed-tty command. > > Michael, the bad news for you, implementing the new initrd image would not be easy using the older AstLinux 1.3.10, barring building you own image. > > Someone could build a AstLinux 1.3.10 initrd.img with this fix (common across all board types), but packaging it would be somewhat tedious. > > Lonnie > > > > >> On Mar 31, 2021, at 3:29 PM, Lonnie Abelbeck <li...@lo...> wrote: >> >> Hi Michael, >> >> Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ... >> >> linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color >> getty: setsid: Operation not permitted >> >> Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script. >> >> Let me do some testing and think about how to fix this. Hopefully. >> >> Lonnie >> >> >> >>> On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi Group >>> >>> In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again. >>> One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output. >>> I am using the 1.3.10 VM image. >>> >>> Any ideas? Has something changed in 1.3.10? >>> >>> Regards >>> Michael Knill >>> >>> On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote: >>> >>> Yay serial console is now working. >>> Thanks for that. I figured it would be easy. >>> >>> Regards >>> Michael Knill >>> >>> On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote: >>> >>> Hi Michael, >>> >>> Great to hear ! >>> >>> If their serial setup is anything similar to Linode's >>> >>> https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode >>> >>> Search for "Out-of-Band Console Access" >>> >>> Basically a simple edit of the /etc/inittab file. >>> >>> >>>> Also would you like me to write up an article for the build process? >>> >>> Is it pretty straight-forward? sure, any helpful documentation is great. >>> >>> Lonnie >>> >>> >>> >>>> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Hi Guys >>>> >>>> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back. >>>> >>>> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up? >>>> >>>> Also would you like me to write up an article for the build process? >>>> >>>> Thanks >>>> >>>> Regards >>>> Michael Knill >>>> _______________________________________________ >>>> Astlinux-devel mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <li...@mk...> - 2021-04-01 09:45:24
|
Hi Michael, the serial console worked fine for me: ---- Mar 31 21:30:54 pbx-nf9hg daemon.notice vnstatd[2171]: Monitoring (1): eth0 (1000 Mbit) Mar 31 19:30:56 pbx-nf9hg daemon.info : starting pid 2326, tty '/dev/console': '/sbin/getty -L 115200 /dev/ttyS0 vt100' ---- > Am 01.04.2021 um 07:35 schrieb Michael Knill <mic...@ip...>: > > Bummer. Thanks Lonnie. We will need to wait for the next release and hope we don't break it in the meantime! > I haven’t checked but is the serial board type broken as well? If not then could I build it with this? > > Regards > Michael Knill > > On 1/4/21, 2:54 pm, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > I committed a fix in the upstream repo: > > https://github.com/astlinux-project/astlinux/commit/79576e557d0d18b10d452e6c9211c4379f7e68f9 > > A side-effect to the FUSE unionfs switch left any changes to /etc/inittab ignored since ASTURW is now mounted after > the initrd runs, and the initrd calls /sbin/init. > > This would also fix issues where the serial console baud rate was not the default 115200 by using the setconsole-speed-tty command. > > Michael, the bad news for you, implementing the new initrd image would not be easy using the older AstLinux 1.3.10, barring building you own image. > > Someone could build a AstLinux 1.3.10 initrd.img with this fix (common across all board types), but packaging it would be somewhat tedious. > > Lonnie > > > > >> On Mar 31, 2021, at 3:29 PM, Lonnie Abelbeck <li...@lo...> wrote: >> >> Hi Michael, >> >> Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ... >> >> linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color >> getty: setsid: Operation not permitted >> >> Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script. >> >> Let me do some testing and think about how to fix this. Hopefully. >> >> Lonnie >> >> >> >>> On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi Group >>> >>> In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again. >>> One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output. >>> I am using the 1.3.10 VM image. >>> >>> Any ideas? Has something changed in 1.3.10? >>> >>> Regards >>> Michael Knill >>> >>> On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote: >>> >>> Yay serial console is now working. >>> Thanks for that. I figured it would be easy. >>> >>> Regards >>> Michael Knill >>> >>> On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote: >>> >>> Hi Michael, >>> >>> Great to hear ! >>> >>> If their serial setup is anything similar to Linode's >>> >>> https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode >>> >>> Search for "Out-of-Band Console Access" >>> >>> Basically a simple edit of the /etc/inittab file. >>> >>> >>>> Also would you like me to write up an article for the build process? >>> >>> Is it pretty straight-forward? sure, any helpful documentation is great. >>> >>> Lonnie >>> >>> >>> >>>> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote: >>>> >>>> Hi Guys >>>> >>>> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back. >>>> >>>> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up? >>>> >>>> Also would you like me to write up an article for the build process? >>>> >>>> Thanks >>>> >>>> Regards >>>> Michael Knill >>>> _______________________________________________ >>>> Astlinux-devel mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel Freundliche Grüße Michael Keuter -- Michael Keuter mk solutions August-Bebel-Straße 65 21029 Hamburg Tel. 040-41493636 Fax 040-41493637 Email: mk...@mk... Web: http://www.mksolutions.info Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2021-04-01 05:35:59
|
Bummer. Thanks Lonnie. We will need to wait for the next release and hope we don't break it in the meantime!
I haven’t checked but is the serial board type broken as well? If not then could I build it with this?
Regards
Michael Knill
On 1/4/21, 2:54 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Michael,
I committed a fix in the upstream repo:
https://github.com/astlinux-project/astlinux/commit/79576e557d0d18b10d452e6c9211c4379f7e68f9
A side-effect to the FUSE unionfs switch left any changes to /etc/inittab ignored since ASTURW is now mounted after
the initrd runs, and the initrd calls /sbin/init.
This would also fix issues where the serial console baud rate was not the default 115200 by using the setconsole-speed-tty command.
Michael, the bad news for you, implementing the new initrd image would not be easy using the older AstLinux 1.3.10, barring building you own image.
Someone could build a AstLinux 1.3.10 initrd.img with this fix (common across all board types), but packaging it would be somewhat tedious.
Lonnie
> On Mar 31, 2021, at 3:29 PM, Lonnie Abelbeck <li...@lo...> wrote:
>
> Hi Michael,
>
> Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ...
>
> linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color
> getty: setsid: Operation not permitted
>
> Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script.
>
> Let me do some testing and think about how to fix this. Hopefully.
>
> Lonnie
>
>
>
>> On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote:
>>
>> Hi Group
>>
>> In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again.
>> One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output.
>> I am using the 1.3.10 VM image.
>>
>> Any ideas? Has something changed in 1.3.10?
>>
>> Regards
>> Michael Knill
>>
>> On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote:
>>
>> Yay serial console is now working.
>> Thanks for that. I figured it would be easy.
>>
>> Regards
>> Michael Knill
>>
>> On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>>
>> Hi Michael,
>>
>> Great to hear !
>>
>> If their serial setup is anything similar to Linode's
>>
>> https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode
>>
>> Search for "Out-of-Band Console Access"
>>
>> Basically a simple edit of the /etc/inittab file.
>>
>>
>>> Also would you like me to write up an article for the build process?
>>
>> Is it pretty straight-forward? sure, any helpful documentation is great.
>>
>> Lonnie
>>
>>
>>
>>> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote:
>>>
>>> Hi Guys
>>>
>>> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back.
>>>
>>> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up?
>>>
>>> Also would you like me to write up an article for the build process?
>>>
>>> Thanks
>>>
>>> Regards
>>> Michael Knill
>>> _______________________________________________
>>> Astlinux-devel mailing list
>>> Ast...@li...
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>>
>>
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>>
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>>
>>
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2021-04-01 03:53:57
|
Hi Michael, I committed a fix in the upstream repo: https://github.com/astlinux-project/astlinux/commit/79576e557d0d18b10d452e6c9211c4379f7e68f9 A side-effect to the FUSE unionfs switch left any changes to /etc/inittab ignored since ASTURW is now mounted after the initrd runs, and the initrd calls /sbin/init. This would also fix issues where the serial console baud rate was not the default 115200 by using the setconsole-speed-tty command. Michael, the bad news for you, implementing the new initrd image would not be easy using the older AstLinux 1.3.10, barring building you own image. Someone could build a AstLinux 1.3.10 initrd.img with this fix (common across all board types), but packaging it would be somewhat tedious. Lonnie > On Mar 31, 2021, at 3:29 PM, Lonnie Abelbeck <li...@lo...> wrote: > > Hi Michael, > > Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ... > > linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color > getty: setsid: Operation not permitted > > Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script. > > Let me do some testing and think about how to fix this. Hopefully. > > Lonnie > > > >> On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote: >> >> Hi Group >> >> In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again. >> One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output. >> I am using the 1.3.10 VM image. >> >> Any ideas? Has something changed in 1.3.10? >> >> Regards >> Michael Knill >> >> On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote: >> >> Yay serial console is now working. >> Thanks for that. I figured it would be easy. >> >> Regards >> Michael Knill >> >> On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote: >> >> Hi Michael, >> >> Great to hear ! >> >> If their serial setup is anything similar to Linode's >> >> https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode >> >> Search for "Out-of-Band Console Access" >> >> Basically a simple edit of the /etc/inittab file. >> >> >>> Also would you like me to write up an article for the build process? >> >> Is it pretty straight-forward? sure, any helpful documentation is great. >> >> Lonnie >> >> >> >>> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi Guys >>> >>> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back. >>> >>> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up? >>> >>> Also would you like me to write up an article for the build process? >>> >>> Thanks >>> >>> Regards >>> Michael Knill >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2021-03-31 20:46:12
|
I agree but I'm pretty sure that Azure only supports a serial console, not a standard one.
Regards
Michael Knill
From: David Kerr <da...@ke...>
Reply to: AstLinux Developers Mailing List <ast...@li...>
Date: Thursday, 1 April 2021 at 7:38 am
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] Astlinux on Azure
So, I guess my question is why you need the serial console? I have been running astlinux in a VM for years and one of the benefits is not needing to use the serial console.
David.
On Wed, Mar 31, 2021 at 3:27 PM Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
Hi Group
In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again.
One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output.
I am using the 1.3.10 VM image.
Any ideas? Has something changed in 1.3.10?
Regards
Michael Knill
On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...<mailto:mic...@ip...>> wrote:
Yay serial console is now working.
Thanks for that. I figured it would be easy.
Regards
Michael Knill
On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote:
Hi Michael,
Great to hear !
If their serial setup is anything similar to Linode's
https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode
Search for "Out-of-Band Console Access"
Basically a simple edit of the /etc/inittab file.
> Also would you like me to write up an article for the build process?
Is it pretty straight-forward? sure, any helpful documentation is great.
Lonnie
> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
>
> Hi Guys
>
> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back.
>
> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up?
>
> Also would you like me to write up an article for the build process?
>
> Thanks
>
> Regards
> Michael Knill
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...<mailto:Ast...@li...>
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: David K. <da...@ke...> - 2021-03-31 20:38:04
|
So, I guess my question is why you need the serial console? I have been running astlinux in a VM for years and one of the benefits is not needing to use the serial console. David. On Wed, Mar 31, 2021 at 3:27 PM Michael Knill < mic...@ip...> wrote: > Hi Group > > In my search to find a reliable cloud provider, I'm now going to be > putting a number of Astlinux boxes in Azure. We have now fully documented > the process so will get an article up once tested again. > One thing we cant get going but did previously is the Serial Console. I > changed the "Out-of-Band Console Access" as per the Linode article below > but it still doesn't work e.g. it connects to the tty but no output. > I am using the 1.3.10 VM image. > > Any ideas? Has something changed in 1.3.10? > > Regards > Michael Knill > > On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> > wrote: > > Yay serial console is now working. > Thanks for that. I figured it would be easy. > > Regards > Michael Knill > > On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> > wrote: > > Hi Michael, > > Great to hear ! > > If their serial setup is anything similar to Linode's > > https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode > > Search for "Out-of-Band Console Access" > > Basically a simple edit of the /etc/inittab file. > > > > Also would you like me to write up an article for the build > process? > > Is it pretty straight-forward? sure, any helpful documentation is > great. > > Lonnie > > > > > On Apr 15, 2020, at 6:25 PM, Michael Knill < > mic...@ip...> wrote: > > > > Hi Guys > > > > I have put my office Astlinux system on Azure to test it out. > Seems to be working fine. I will let it run for a week or so to see how it > goes and report back. > > > > One annoying thing is that Azure is looking for a serial console > but I have installed the vm board type. Is there any way I can set this up? > > > > Also would you like me to write up an article for the build > process? > > > > Thanks > > > > Regards > > Michael Knill > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |
|
From: Lonnie A. <li...@lo...> - 2021-03-31 20:30:13
|
Hi Michael, Hmmm, I have an issue with linode's lish as well, no ttyS0 getty, and manually trying to start it ... linode ~ # /sbin/getty -L 19200 /dev/ttyS0 xterm-color getty: setsid: Operation not permitted Ok, this could be related to the change from kernel unionfs to FUSE unionfs in AstLinux 1.3.10 . It looks like any changes to /etc/inittab via FUSE unionfs are setup after "/sbin/init" which is called via the initrd /linuxrc script. Let me do some testing and think about how to fix this. Hopefully. Lonnie > On Mar 31, 2021, at 2:26 PM, Michael Knill <mic...@ip...> wrote: > > Hi Group > > In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again. > One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output. > I am using the 1.3.10 VM image. > > Any ideas? Has something changed in 1.3.10? > > Regards > Michael Knill > > On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote: > > Yay serial console is now working. > Thanks for that. I figured it would be easy. > > Regards > Michael Knill > > On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Michael, > > Great to hear ! > > If their serial setup is anything similar to Linode's > > https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode > > Search for "Out-of-Band Console Access" > > Basically a simple edit of the /etc/inittab file. > > >> Also would you like me to write up an article for the build process? > > Is it pretty straight-forward? sure, any helpful documentation is great. > > Lonnie > > > >> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote: >> >> Hi Guys >> >> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back. >> >> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up? >> >> Also would you like me to write up an article for the build process? >> >> Thanks >> >> Regards >> Michael Knill >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2021-03-31 19:27:00
|
Hi Group
In my search to find a reliable cloud provider, I'm now going to be putting a number of Astlinux boxes in Azure. We have now fully documented the process so will get an article up once tested again.
One thing we cant get going but did previously is the Serial Console. I changed the "Out-of-Band Console Access" as per the Linode article below but it still doesn't work e.g. it connects to the tty but no output.
I am using the 1.3.10 VM image.
Any ideas? Has something changed in 1.3.10?
Regards
Michael Knill
On 16/4/20, 11:48 am, "Michael Knill" <mic...@ip...> wrote:
Yay serial console is now working.
Thanks for that. I figured it would be easy.
Regards
Michael Knill
On 16/4/20, 9:38 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Michael,
Great to hear !
If their serial setup is anything similar to Linode's
https://doc.astlinux-project.org/userdoc:hosted_guest_vm_linode
Search for "Out-of-Band Console Access"
Basically a simple edit of the /etc/inittab file.
> Also would you like me to write up an article for the build process?
Is it pretty straight-forward? sure, any helpful documentation is great.
Lonnie
> On Apr 15, 2020, at 6:25 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi Guys
>
> I have put my office Astlinux system on Azure to test it out. Seems to be working fine. I will let it run for a week or so to see how it goes and report back.
>
> One annoying thing is that Azure is looking for a serial console but I have installed the vm board type. Is there any way I can set this up?
>
> Also would you like me to write up an article for the build process?
>
> Thanks
>
> Regards
> Michael Knill
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2021-03-11 19:21:18
|
Announcing AstLinux Release: 1.4.2 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.4.2 Highlights: * Asterisk Versions: 13.29.2, 13.38.2, 16.16.2 * Linux Kernel 4.19.177, security and bug fixes * ipsec-tools (racoon) package has been removed. * OpenSSL, version bump to 1.1.1j, security fixes * OpenVPN, version bump to 2.4.10 * WireGuard VPN, module 1.0.20210219 (version bump), tools 1.0.20210223 (version bump) * dnsmasq, version 2.84, patch: upstream DNS retries regression fix * unbound, version bump to 1.13.1 * sudo, version bump to 1.8.32, security fixes * zabbix, version bump to 4.0.29 * vnStat, new package, version 2.6, interface counter history is saved to /mnt/kd/vnstat/vnstat.db every hour. Enabled by default to keep a log of network traffic for external interface(s). No sniffing of traffic is performed. New rc.conf variable VNSTAT_ENABLE can be set to "no" to disable. * Web Interface, added vnStat tab, available to "admin/staff" users. Hidden by default in Prefs tab. * All Asterisk versions now have sRTP replay protection, new rtp.conf config option: srtpreplayprotection=yes This new rtp.conf option is enabled by default. Buggy SIP user agents may require srtpreplayprotection=no if audio issues occur with sRTP streams. * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.4.2/docs/ChangeLog.txt All users are encouraged to upgrade, read the ChangeLog for the details. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2021-03-05 13:26:17
|
Release Candidate1 pre-1.4.2, please report any issues, ASAP. Due to many security fixes, Asterisk (pjsip), sRTP replay protection, et al., we plan on releasing AstLinux 1.4.2 sooner than the typical 3-4 month release cycle. ** IMPORTANT NOTICE -- The ipsec-tools (racoon) support in AstLinux has been removed. The development of ipsec-tools has been ABANDONED. The Network tab -> VPN Type: "IPsec Peers" and "IPsec Mobile" in the web interface has been removed. The AstLinux Team suggests using either WireGuard or OpenVPN for your VPN needs, but if IPsec is required for compatibility reasons the Network tab -> VPN Type: "IPsec strongSwan" should be able to do what you want, albeit in a less than ideal text based configuration. More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 4.19.177 (version bump), security and bug fixes -- ipsec-tools (racoon) package has been removed. More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan -- OpenSSL, version bump to 1.1.1j, security fixes -- OpenVPN, version bump to 2.4.10 -- WireGuard VPN, module 1.0.20210219 (version bump), tools 1.0.20210223 (version bump) -- unbound, version bump to 1.13.1 -- zabbix, version bump to 4.0.29 -- vnStat, new package, version 2.6, interface counter history is saved to /mnt/kd/vnstat/vnstat.db every hour. Enabled by default to keep a log of network traffic for external interface(s). No sniffing of traffic is performed. New rc.conf variable VNSTAT_ENABLE can be set to "no" to disable. -- Web Interface, added vnStat tab, available to "admin/staff" users. Hidden by default in Prefs tab. -- Asterisk 13.29.2 ('13se' no change) Older than latest Asterisk 13.x version but more tested, built --without-pjproject -- Asterisk 13.38.2 (version bump) and 16.16.2 (version bump) -- Note: All Asterisk versions now have sRTP replay protection, new rtp.conf config option: srtpreplayprotection=yes This new rtp.conf option is enabled by default. Buggy SIP user agents may require srtpreplayprotection=no if audio issues occur with sRTP streams. -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2021-02-26 13:49:55
|
Announcing AstLinux Pre-Release: astlinux-1.4-5067-7a9a8c Due to many security fixes, Asterisk (pjsip), sRTP replay protection, et al., we plan on releasing AstLinux 1.4.2 sooner than the typical 3-4 month release cycle. Please test this pre-release, to be followed by a release-candidate and AstLinux 1.4.2 in the next couple weeks. ** IMPORTANT NOTICE -- The ipsec-tools (racoon) support in AstLinux has been removed. The development of ipsec-tools has been ABANDONED. The Network tab -> VPN Type: "IPsec Peers" and "IPsec Mobile" in the web interface has been removed. The AstLinux Team suggests using either WireGuard or OpenVPN for your VPN needs, but if IPsec is required for compatibility reasons the Network tab -> VPN Type: "IPsec strongSwan" should be able to do what you want, albeit in a less than ideal text based configuration. More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 4.19.177 (version bump), security and bug fixes -- ipsec-tools (racoon) package has been removed. More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan -- OpenSSL, version bump to 1.1.1j, security fixes -- OpenVPN, version bump to 2.4.10 -- WireGuard VPN, module 1.0.20210219 (version bump), tools 1.0.20210223 (version bump) -- unbound, version bump to 1.13.1 -- zabbix, version bump to 4.0.29 -- vnStat, new package, version 2.6, interface counter history is saved to /mnt/kd/vnstat/vnstat.db every hour. Enabled by default to keep a log of network traffic for external interface(s). No sniffing of traffic is performed. New rc.conf variable VNSTAT_ENABLE can be set to "no" to disable. -- Web Interface, added vnStat tab, available to "admin/staff" users. Hidden by default in Prefs tab. -- Asterisk 13.29.2 ('13se' no change) Older than latest Asterisk 13.x version but more tested, built --without-pjproject -- Asterisk 13.38.2 (version bump) and 16.16.1 (version bump) -- Note: All Asterisk versions now have sRTP replay protection, new rtp.conf config option: srtpreplayprotection=yes This new rtp.conf option is enabled by default. Buggy SIP user agents may require srtpreplayprotection=no if audio issues occur with sRTP streams. -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2021-02-15 21:22:21
|
> On Feb 15, 2021, at 3:06 PM, Michael Keuter <li...@mk...> wrote: > > > >> Am 15.02.2021 um 15:12 schrieb Lonnie Abelbeck <li...@lo...>: >> >> Hi Devs, >> >> For many years I thought AstLinux should install a basic, functional Asterisk configuration (extensions.conf and sip.conf) possibly with voicemail and a few features. >> >> Whenever I though about this in the past, my head started to hurt and found something else on the TODO list. :-) >> >> Given the maturity of Asterisk 13/16, and most everyone (particularly beginners) will use SIP phones and an internet SIP provider, maybe now is a good time to consider AstLinux installing a default set of configs ? >> >> Should the config use pjsip ? >> >> Possibly something exists on GitHub. >> >> Not sure what our goals should be, start the brainstorming ... >> >> Lonnie > > Digium started the same approach a few years ago: > > https://github.com/asterisk/asterisk/tree/master/configs/basic-pbx > > Maybe that could be a starting point for what you want … > > Michael Thanks Michael, this is included in the asterisk source! I never knew about this. We can take a look at it, simplest we could include this under /stat/ somewhere. Or just a URL link in the docs. Lonnie |
|
From: Michael K. <li...@mk...> - 2021-02-15 21:07:12
|
> Am 15.02.2021 um 15:12 schrieb Lonnie Abelbeck <li...@lo...>: > > Hi Devs, > > For many years I thought AstLinux should install a basic, functional Asterisk configuration (extensions.conf and sip.conf) possibly with voicemail and a few features. > > Whenever I though about this in the past, my head started to hurt and found something else on the TODO list. :-) > > Given the maturity of Asterisk 13/16, and most everyone (particularly beginners) will use SIP phones and an internet SIP provider, maybe now is a good time to consider AstLinux installing a default set of configs ? > > Should the config use pjsip ? > > Possibly something exists on GitHub. > > Not sure what our goals should be, start the brainstorming ... > > Lonnie Digium started the same approach a few years ago: https://github.com/asterisk/asterisk/tree/master/configs/basic-pbx Maybe that could be a starting point for what you want … Michael http://www.mksolutions.info |
|
From: The C. K. <eld...@ya...> - 2021-02-15 20:58:12
|
maybe you leave astlinux as it is in form but make a default set of configs and a mechanism for loading them that a NooB could load in? so if someone wanted a standard SOHO set up you would have a packaged set that they could upload to their astlinux box and go.. whereas anyone else who likes it in current form can just use it and program it low level..
there are a lot of asterisk GUI projects and various products based on asterisk that have GUI's, astlinux doesnt necessarily have to follow in that same pathway.
On Monday, February 15, 2021, 2:19:07 PM CST, Michael Knill <mic...@ip...> wrote:
Hi Lonnie
Although its really not going to affect me as I have all my own configs anyway, I'm wondering what you see as the advantages of doing this would be?
One thing it will do is change the forum from just being about Astlinux to now including Asterisk. I'm not sure this is a good thing but that may just be me!
I think another issue is that the Astlinux UI is very generic providing flexibility to do whatever you want. I'm concerned that we will begin to lose this by adding Asterisk configuration and changing the UI to match.
That all being said, I realise that the Astlinux project is relatively exclusive because of the steep learning curve and that may be a good thing for me but not for the community as a whole.
Maybe it should be created as a separate add in or expansion pack opening it up to many possibilities? You could have different add ins to do different things.
My 2c worth.
Regards
Michael Knill
On 16/2/21, 1:12 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Devs,
For many years I thought AstLinux should install a basic, functional Asterisk configuration (extensions.conf and sip.conf) possibly with voicemail and a few features.
Whenever I though about this in the past, my head started to hurt and found something else on the TODO list. :-)
Given the maturity of Asterisk 13/16, and most everyone (particularly beginners) will use SIP phones and an internet SIP provider, maybe now is a good time to consider AstLinux installing a default set of configs ?
Should the config use pjsip ?
Possibly something exists on GitHub.
Not sure what our goals should be, start the brainstorming ...
Lonnie
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2021-02-15 20:32:56
|
Hi Michael, I was not suggesting any changes to web interface and not suggesting offering Asterisk support. Again just brainstorming, if the default config could offer a very basic "home" PBX such that a beginner had a starting point to build upon ... would that be better than the current default Asterisk extensions.conf ? Lonnie > On Feb 15, 2021, at 1:43 PM, Michael Knill <mic...@ip...> wrote: > > Hi Lonnie > > Although its really not going to affect me as I have all my own configs anyway, I'm wondering what you see as the advantages of doing this would be? > One thing it will do is change the forum from just being about Astlinux to now including Asterisk. I'm not sure this is a good thing but that may just be me! > I think another issue is that the Astlinux UI is very generic providing flexibility to do whatever you want. I'm concerned that we will begin to lose this by adding Asterisk configuration and changing the UI to match. > > That all being said, I realise that the Astlinux project is relatively exclusive because of the steep learning curve and that may be a good thing for me but not for the community as a whole. > > Maybe it should be created as a separate add in or expansion pack opening it up to many possibilities? You could have different add ins to do different things. > > My 2c worth. > > Regards > Michael Knill > > On 16/2/21, 1:12 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Hi Devs, > > For many years I thought AstLinux should install a basic, functional Asterisk configuration (extensions.conf and sip.conf) possibly with voicemail and a few features. > > Whenever I though about this in the past, my head started to hurt and found something else on the TODO list. :-) > > Given the maturity of Asterisk 13/16, and most everyone (particularly beginners) will use SIP phones and an internet SIP provider, maybe now is a good time to consider AstLinux installing a default set of configs ? > > Should the config use pjsip ? > > Possibly something exists on GitHub. > > Not sure what our goals should be, start the brainstorming ... > > Lonnie > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Michael K. <mic...@ip...> - 2021-02-15 20:18:56
|
Hi Lonnie
Although its really not going to affect me as I have all my own configs anyway, I'm wondering what you see as the advantages of doing this would be?
One thing it will do is change the forum from just being about Astlinux to now including Asterisk. I'm not sure this is a good thing but that may just be me!
I think another issue is that the Astlinux UI is very generic providing flexibility to do whatever you want. I'm concerned that we will begin to lose this by adding Asterisk configuration and changing the UI to match.
That all being said, I realise that the Astlinux project is relatively exclusive because of the steep learning curve and that may be a good thing for me but not for the community as a whole.
Maybe it should be created as a separate add in or expansion pack opening it up to many possibilities? You could have different add ins to do different things.
My 2c worth.
Regards
Michael Knill
On 16/2/21, 1:12 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Devs,
For many years I thought AstLinux should install a basic, functional Asterisk configuration (extensions.conf and sip.conf) possibly with voicemail and a few features.
Whenever I though about this in the past, my head started to hurt and found something else on the TODO list. :-)
Given the maturity of Asterisk 13/16, and most everyone (particularly beginners) will use SIP phones and an internet SIP provider, maybe now is a good time to consider AstLinux installing a default set of configs ?
Should the config use pjsip ?
Possibly something exists on GitHub.
Not sure what our goals should be, start the brainstorming ...
Lonnie
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Lonnie A. <li...@lo...> - 2021-02-15 14:12:35
|
Hi Devs, For many years I thought AstLinux should install a basic, functional Asterisk configuration (extensions.conf and sip.conf) possibly with voicemail and a few features. Whenever I though about this in the past, my head started to hurt and found something else on the TODO list. :-) Given the maturity of Asterisk 13/16, and most everyone (particularly beginners) will use SIP phones and an internet SIP provider, maybe now is a good time to consider AstLinux installing a default set of configs ? Should the config use pjsip ? Possibly something exists on GitHub. Not sure what our goals should be, start the brainstorming ... Lonnie |
|
From: Lonnie A. <li...@lo...> - 2021-02-13 13:56:35
|
Announcing AstLinux Pre-Release: astlinux-1.4-5042-8873c9 ** IMPORTANT NOTICE -- The ipsec-tools (racoon) support in AstLinux has been removed. The development of ipsec-tools has been ABANDONED. The Network tab -> VPN Type: "IPsec Peers" and "IPsec Mobile" in the web interface has been removed. The AstLinux Team suggests using either WireGuard or OpenVPN for your VPN needs, but if IPsec is required for compatibility reasons the Network tab -> VPN Type: "IPsec strongSwan" should be able to do what you want, albeit in a less than ideal text based configuration. More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 4.19.175 (version bump), security and bug fixes -- ipsec-tools (racoon) package has been removed. More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan -- OpenVPN, version bump to 2.4.10 -- unbound, version bump to 1.13.1 -- zabbix, version bump to 4.0.28 -- vnStat, new package, version 2.6, interface counter history is saved to /mnt/kd/vnstat/vnstat.db every hour. Enabled by default to keep a log of network traffic for external interface(s). No sniffing of traffic is performed. New rc.conf variable VNSTAT_ENABLE can be set to "no" to disable. -- Web Interface, added vnStat tab, available to "admin/staff" users. Hidden by default in Prefs tab. -- Asterisk 13.29.2 ('13se' no change) Older than latest Asterisk 13.x version but more tested, built --without-pjproject -- Asterisk 13.38.1 (no change) and 16.16.0 (version bump) -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2021-02-02 22:31:42
|
Announcing AstLinux Release: 1.4.1 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.4.1 Highlights: * Asterisk Versions: 13.29.2, 13.38.1, 16.15.1 * Linux Kernel 4.19.167, security and bug fixes * RUNNIX, version bump to runnix-0.6.3, with Linux Kernel 4.19.167, kexec 2.0.21 * OpenSSL, version bump to 1.1.1i, security fix * WireGuard VPN, module 1.0.20210124 (version bump), tools 1.0.20200827 (no change) * dnsmasq, version bump to 2.84, important security fixes * getdns/stubby, remove package, replace getdns/stubby with unbound for DNS-over-TLS * unbound, version bump to 1.13.0 * PPPoE client, reimplement using the latest pppd 2.4.9 pppoe kernel driver and our custom scripts * rng-tools, jitterentropy version bump to 3.0.1 (2x improved performance on APU systems) * sudo, critical security fix * sngrep, version bump to 1.4.8 * zabbix, version bump to 4.0.27 * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.4.1/docs/ChangeLog.txt All users are encouraged to upgrade. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2021-01-26 21:59:20
|
Release Candidate1 pre-1.4.1, please report any issues, ASAP. The next AstLinux version will be 1.4.1, most notably switching to the Linux kernel 4.19.x LTS series. ** IMPORTANT NOTICE -- The ipsec-tools (racoon) support in AstLinux is deprecated, and will be removed in the near future. The development of ipsec-tools has been ABANDONED. The Network tab -> VPN Type: "IPsec Peers" and "IPsec Mobile" is the web interface configuration for ipsec-tools. The AstLinux Team suggests using either WireGuard or OpenVPN for your VPN needs, but if IPsec is required for compatibility reasons the Network tab -> VPN Type: "IPsec strongSwan" should be able to do what you want, albeit in a less than ideal text based configuration. More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 4.19.167 (version bump), security and bug fixes -- RUNNIX, version bump to runnix-0.6.3, with Linux Kernel 4.19.167, kexec 2.0.21 -- OpenSSL, version bump to 1.1.1i, security fix: CVE-2020-1971 -- WireGuard VPN, module 1.0.20210124 (version bump), tools 1.0.20200827 (no change) -- libcurl (curl) version bump to 7.74.0, security fixes: CVE-2020-8284, CVE-2020-8285, CVE-2020-8286 -- dnsmasq, version bump to 2.84, security fixes: CVE-2020-25684, CVE-2020-25685, CVE-2020-25686 -- getdns/stubby, remove package, replace getdns/stubby with unbound for DNS-over-TLS -- unbound, version bump to 1.13.0 -- PPPoE client, reimplement using the latest pppd 2.4.9 pppoe kernel driver and our custom scripts -- rng-tools, jitterentropy version bump to 3.0.1 (2x improved performance on APU systems) -- miniupnpd, version 2.1, add Debian security fixes: CVE-2019-12107, CVE-2019-12108 CVE-2019-12109, CVE-2019-12110, CVE-2019-12111 -- sngrep, version bump to 1.4.8 -- Monit, version bump to 5.27.2 -- zabbix, version bump to 4.0.27 -- Asterisk 13.29.2 ('13se' no change) Older than latest Asterisk 13.x version but more tested, built --without-pjproject -- Asterisk 13.38.1 (version bump) and 16.15.1 (version bump) -- Add support for directory /var/spool/asterisk/outgoing_tmp for call file staging. -- Add support for persistent /mnt/kd/call-file/ directory for certain tmpfs spool directories. If the directory /mnt/kd/call-file/ exists, the following symlinks will automatically occur: == /var/spool/asterisk/outgoing -> /mnt/kd/call-file/outgoing == /var/spool/asterisk/outgoing_tmp -> /mnt/kd/call-file/outgoing_tmp == /var/spool/asterisk/outgoing_done -> /mnt/kd/call-file/outgoing_done -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2021-01-09 15:58:01
|
Announcing AstLinux Pre-Release: astlinux-1.4-4972-3bdfa6 ** Request for Testing This pre-release reimplements the PPPoE client using the latest pppd 2.4.9 pppoe kernel driver and our custom scripts. The PPPoE client has always been an issue for the AstLinux devs since testing is an issue. Michael Keuter and Lonnie were able to independently use the pppoe-server software and build a PPPoE test environment between two AstLinux boxes. We now need testing with actual ISPs requiring PPPoE. So if you use PPPoE, be certain you test this pre-release while having local access, such that if anything goes wrong you can "Revert to Previous" and get back working. Test by restarting PPPoE a few time in a row, rebooting a couple times, looking for errors (grep pppd /var/log/messages). Please report any issues (and successes) with this change. ** IMPORTANT NOTICE -- The ipsec-tools (racoon) support in AstLinux is deprecated, and will be removed in the near future. The development of ipsec-tools has been ABANDONED. The Network tab -> VPN Type: "IPsec Peers" and "IPsec Mobile" is the web interface configuration for ipsec-tools. The AstLinux Team suggests using either WireGuard or OpenVPN for your VPN needs, but if IPsec is required for compatibility reasons the Network tab -> VPN Type: "IPsec strongSwan" should be able to do what you want, albeit in a less than ideal text based configuration. More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 4.19.160 (version bump), security and bug fixes -- OpenSSL, version bump to 1.1.1i, security fix: CVE-2020-1971 -- WireGuard VPN, module 1.0.20201221 (version bump), tools 1.0.20200827 (no change) -- libcurl (curl) version bump to 7.74.0, security fixes: CVE-2020-8284, CVE-2020-8285, CVE-2020-8286 -- getdns/stubby, remove package, replace getdns/stubby with unbound for DNS-over-TLS -- unbound, version bump to 1.13.0 -- rng-tools, jitterentropy version bump to 3.0.0 (2x improved performance on APU systems) -- miniupnpd, version 2.1, add Debian security fixes: CVE-2019-12107, CVE-2019-12108 CVE-2019-12109, CVE-2019-12110, CVE-2019-12111 -- sngrep, version bump to 1.4.8 -- Monit, version bump to 5.27.1 -- zabbix, version bump to 4.0.27 -- Asterisk 13.29.2 ('13se' no change) Older than latest Asterisk 13.x version but more tested, built --without-pjproject -- Asterisk 13.38.1 (version bump) and 16.15.1 (version bump) -- Add support for directory /var/spool/asterisk/outgoing_tmp for call file staging. -- Add support for persistent /mnt/kd/call-file/ directory for certain tmpfs spool directories. If the directory /mnt/kd/call-file/ exists, the following symlinks will automatically occur: == /var/spool/asterisk/outgoing -> /mnt/kd/call-file/outgoing == /var/spool/asterisk/outgoing_tmp -> /mnt/kd/call-file/outgoing_tmp == /var/spool/asterisk/outgoing_done -> /mnt/kd/call-file/outgoing_done -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html AstLinux Team |
28 messages has been excluded from this view by a project administrator.
