Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.ai.shells > #292 > unrolled thread

AI success story

Started byCreon <creon@creon.earth>
First post2025-04-27 04:26 +0000
Last post2025-04-30 19:27 -0700
Articles 9 — 5 participants

Back to article view | Back to comp.ai.shells


Contents

  AI success story Creon <creon@creon.earth> - 2025-04-27 04:26 +0000
    Re: AI success story Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-04-27 05:03 +0000
      Re: AI success story David <BoaterDave@hotmail.co.uk> - 2025-04-27 06:58 +0100
        Re: AI success story Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-04-27 15:32 +0000
          Re: AI success story % <pursent100@gmail.com> - 2025-04-27 08:34 -0700
            Re: AI success story Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-04-27 16:06 +0000
    Re: AI success story % <pursent100@gmail.com> - 2025-04-27 07:59 -0700
    Re: AI success story vallor <vallor@cultnix.org> - 2025-05-01 01:12 +0000
      Re: AI success story % <pursent100@gmail.com> - 2025-04-30 19:27 -0700

#292 — AI success story

FromCreon <creon@creon.earth>
Date2025-04-27 04:26 +0000
SubjectAI success story
Message-ID<m75pv3Fc894U3@mid.individual.net>
Actually had a success story with AI to share.

Using ChatGPT, regarding Linux, I was able to give it my current 
output of "ifconfig -a" and have it generate an accurate netplan
yaml file for network configuration -- which worked.

Then I had it add some policy routing, which also worked.

I did this to renumber three servers.  The only snag was when
I went to reconfigure the Red Hat-based server...it was so
old, it didn't support Red Hat's more modern network configuration
scriptlets.  So I had ChatGPT walk me through writing a script
to do the configuration, then set up a systemd unit file to run
the script when the networking service started.  All done.

I was pleasantly surprised at how accurate ChatGPT was with
its configuration directives, scripting, and unit file setup.

-- 
-c System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.14.4 Release: Mint 22.1 Mem: 258G
   "Anything will fit if you push hard enough"

[toc] | [next] | [standalone]


#293

FromBrock McNuggets <brock.mcnuggets@gmail.com>
Date2025-04-27 05:03 +0000
Message-ID<680dbabe$0$19$882e4bbb@reader.netnews.com>
In reply to#292
On Apr 26, 2025 at 9:26:11 PM MST, "Creon" wrote
<m75pv3Fc894U3@mid.individual.net>:

> Actually had a success story with AI to share.
> 
> Using ChatGPT, regarding Linux, I was able to give it my current
> output of "ifconfig -a" and have it generate an accurate netplan
> yaml file for network configuration -- which worked.
> 
> Then I had it add some policy routing, which also worked.
> 
> I did this to renumber three servers.  The only snag was when
> I went to reconfigure the Red Hat-based server...it was so
> old, it didn't support Red Hat's more modern network configuration
> scriptlets.  So I had ChatGPT walk me through writing a script
> to do the configuration, then set up a systemd unit file to run
> the script when the networking service started.  All done.
> 
> I was pleasantly surprised at how accurate ChatGPT was with
> its configuration directives, scripting, and unit file setup.

Thanks for sharing.

I also had some success today... decided to see if I could use it to make an
alternative lookup for Message IDs. I had to fiddle a bit and it still does
error handling poorly, but got this:

https://jmp.sh/im88Qhhh

Happy to have it as a tool.


-- 
It's impossible for someone who is at war with themselves to be at peace with you.

[toc] | [prev] | [next] | [standalone]


#294

FromDavid <BoaterDave@hotmail.co.uk>
Date2025-04-27 06:58 +0100
Message-ID<m75vd3Fdm1dU1@mid.individual.net>
In reply to#293
On 27/04/2025 06:03, Brock McNuggets wrote:
> On Apr 26, 2025 at 9:26:11 PM MST, "Creon" wrote
> <m75pv3Fc894U3@mid.individual.net>:
> 
>> Actually had a success story with AI to share.
>>
>> Using ChatGPT, regarding Linux, I was able to give it my current
>> output of "ifconfig -a" and have it generate an accurate netplan
>> yaml file for network configuration -- which worked.
>>
>> Then I had it add some policy routing, which also worked.
>>
>> I did this to renumber three servers.  The only snag was when
>> I went to reconfigure the Red Hat-based server...it was so
>> old, it didn't support Red Hat's more modern network configuration
>> scriptlets.  So I had ChatGPT walk me through writing a script
>> to do the configuration, then set up a systemd unit file to run
>> the script when the networking service started.  All done.
>>
>> I was pleasantly surprised at how accurate ChatGPT was with
>> its configuration directives, scripting, and unit file setup.
> 
> Thanks for sharing.
> 
> I also had some success today... decided to see if I could use it to make an
> alternative lookup for Message IDs. I had to fiddle a bit and it still does
> error handling poorly, but got this:
> 
> https://jmp.sh/im88Qhhh
> 
> Happy to have it as a tool.

Can you make it into an App available to all - through the Apple App Store?

[toc] | [prev] | [next] | [standalone]


#296

FromBrock McNuggets <brock.mcnuggets@gmail.com>
Date2025-04-27 15:32 +0000
Message-ID<680e4e03$9$4265$882e4bbb@reader.netnews.com>
In reply to#294
On Apr 26, 2025 at 10:58:59 PM MST, "David" wrote
<m75vd3Fdm1dU1@mid.individual.net>:

> On 27/04/2025 06:03, Brock McNuggets wrote:
>> On Apr 26, 2025 at 9:26:11 PM MST, "Creon" wrote
>> <m75pv3Fc894U3@mid.individual.net>:
>> 
>>> Actually had a success story with AI to share.
>>> 
>>> Using ChatGPT, regarding Linux, I was able to give it my current
>>> output of "ifconfig -a" and have it generate an accurate netplan
>>> yaml file for network configuration -- which worked.
>>> 
>>> Then I had it add some policy routing, which also worked.
>>> 
>>> I did this to renumber three servers.  The only snag was when
>>> I went to reconfigure the Red Hat-based server...it was so
>>> old, it didn't support Red Hat's more modern network configuration
>>> scriptlets.  So I had ChatGPT walk me through writing a script
>>> to do the configuration, then set up a systemd unit file to run
>>> the script when the networking service started.  All done.
>>> 
>>> I was pleasantly surprised at how accurate ChatGPT was with
>>> its configuration directives, scripting, and unit file setup.
>> 
>> Thanks for sharing.
>> 
>> I also had some success today... decided to see if I could use it to make an
>> alternative lookup for Message IDs. I had to fiddle a bit and it still does
>> error handling poorly, but got this:
>> 
>> https://jmp.sh/im88Qhhh
>> 
>> Happy to have it as a tool.
> 
> Can you make it into an App available to all - through the Apple App Store?

I could not. Or at least not at its current stage... though maybe I could post
the code so others can do it.


-- 
It's impossible for someone who is at war with themselves to be at peace with you.

[toc] | [prev] | [next] | [standalone]


#297

From% <pursent100@gmail.com>
Date2025-04-27 08:34 -0700
Message-ID<IqGcnbJYxLUd05P1nZ2dnZfqnPEAAAAA@giganews.com>
In reply to#296
Brock McNuggets wrote:
> On Apr 26, 2025 at 10:58:59 PM MST, "David" wrote
> <m75vd3Fdm1dU1@mid.individual.net>:
> 
>> On 27/04/2025 06:03, Brock McNuggets wrote:
>>> On Apr 26, 2025 at 9:26:11 PM MST, "Creon" wrote
>>> <m75pv3Fc894U3@mid.individual.net>:
>>>
>>>> Actually had a success story with AI to share.
>>>>
>>>> Using ChatGPT, regarding Linux, I was able to give it my current
>>>> output of "ifconfig -a" and have it generate an accurate netplan
>>>> yaml file for network configuration -- which worked.
>>>>
>>>> Then I had it add some policy routing, which also worked.
>>>>
>>>> I did this to renumber three servers.  The only snag was when
>>>> I went to reconfigure the Red Hat-based server...it was so
>>>> old, it didn't support Red Hat's more modern network configuration
>>>> scriptlets.  So I had ChatGPT walk me through writing a script
>>>> to do the configuration, then set up a systemd unit file to run
>>>> the script when the networking service started.  All done.
>>>>
>>>> I was pleasantly surprised at how accurate ChatGPT was with
>>>> its configuration directives, scripting, and unit file setup.
>>>
>>> Thanks for sharing.
>>>
>>> I also had some success today... decided to see if I could use it to make an
>>> alternative lookup for Message IDs. I had to fiddle a bit and it still does
>>> error handling poorly, but got this:
>>>
>>> https://jmp.sh/im88Qhhh
>>>
>>> Happy to have it as a tool.
>>
>> Can you make it into an App available to all - through the Apple App Store?
> 
> I could not. Or at least not at its current stage... though maybe I could post
> the code so others can do it.
> 
> 
don't forget the chicken foot

[toc] | [prev] | [next] | [standalone]


#298

FromBrock McNuggets <brock.mcnuggets@gmail.com>
Date2025-04-27 16:06 +0000
Message-ID<680e55eb$16$18$882e4bbb@reader.netnews.com>
In reply to#297
On Apr 27, 2025 at 8:34:19 AM MST, "%" wrote
<IqGcnbJYxLUd05P1nZ2dnZfqnPEAAAAA@giganews.com>:

> Brock McNuggets wrote:
>> On Apr 26, 2025 at 10:58:59 PM MST, "David" wrote
>> <m75vd3Fdm1dU1@mid.individual.net>:
>> 
>>> On 27/04/2025 06:03, Brock McNuggets wrote:
>>>> On Apr 26, 2025 at 9:26:11 PM MST, "Creon" wrote
>>>> <m75pv3Fc894U3@mid.individual.net>:
>>>> 
>>>>> Actually had a success story with AI to share.
>>>>> 
>>>>> Using ChatGPT, regarding Linux, I was able to give it my current
>>>>> output of "ifconfig -a" and have it generate an accurate netplan
>>>>> yaml file for network configuration -- which worked.
>>>>> 
>>>>> Then I had it add some policy routing, which also worked.
>>>>> 
>>>>> I did this to renumber three servers.  The only snag was when
>>>>> I went to reconfigure the Red Hat-based server...it was so
>>>>> old, it didn't support Red Hat's more modern network configuration
>>>>> scriptlets.  So I had ChatGPT walk me through writing a script
>>>>> to do the configuration, then set up a systemd unit file to run
>>>>> the script when the networking service started.  All done.
>>>>> 
>>>>> I was pleasantly surprised at how accurate ChatGPT was with
>>>>> its configuration directives, scripting, and unit file setup.
>>>> 
>>>> Thanks for sharing.
>>>> 
>>>> I also had some success today... decided to see if I could use it to make an
>>>> alternative lookup for Message IDs. I had to fiddle a bit and it still does
>>>> error handling poorly, but got this:
>>>> 
>>>> https://jmp.sh/im88Qhhh
>>>> 
>>>> Happy to have it as a tool.
>>> 
>>> Can you make it into an App available to all - through the Apple App Store?
>> 
>> I could not. Or at least not at its current stage... though maybe I could post
>> the code so others can do it.
>> 
>> 
> don't forget the chicken foot

Never! It’s the secret ingredient for world peace and perfect scrambled eggs.

-- 
It's impossible for someone who is at war with themselves to be at peace with you.

[toc] | [prev] | [next] | [standalone]


#295

From% <pursent100@gmail.com>
Date2025-04-27 07:59 -0700
Message-ID<3QednTlAFaXL25P1nZ2dnZfqn_idnZ2d@giganews.com>
In reply to#292
Creon wrote:
> Actually had a success story with AI to share.
> 
> Using ChatGPT, regarding Linux, I was able to give it my current
> output of "ifconfig -a" and have it generate an accurate netplan
> yaml file for network configuration -- which worked.
> 
> Then I had it add some policy routing, which also worked.
> 
> I did this to renumber three servers.  The only snag was when
> I went to reconfigure the Red Hat-based server...it was so
> old, it didn't support Red Hat's more modern network configuration
> scriptlets.  So I had ChatGPT walk me through writing a script
> to do the configuration, then set up a systemd unit file to run
> the script when the networking service started.  All done.
> 
> I was pleasantly surprised at how accurate ChatGPT was with
> its configuration directives, scripting, and unit file setup.
> 

 > On Sat, 26 Apr 2025 15:08:25 -0700, % wrote:
 >
 >> .
 >>
 >> what i did from high atop my whistler home
 >
 > You gave the population of your local town, so I was able
 > to triangulate on where you are.
 >
 > I don't want to post it though, but it's further up the
 > Sea-to-Sky Highway from Whistler.
 >
 > You _say_ it's a "tourist trap", but there does appear to
 > be a lot to do and see there.  I'm also intrigued by
 > the geothermal plant and capacitor station.
 >
go ahead tell anything about where i live ,
tell everything you can just be ready to prove it's true

[toc] | [prev] | [next] | [standalone]


#299

Fromvallor <vallor@cultnix.org>
Date2025-05-01 01:12 +0000
Message-ID<vuuhq4$m7pb$2@dont-email.me>
In reply to#292
On 27 Apr 2025 04:26:11 GMT, Creon <creon@creon.earth> wrote in
<m75pv3Fc894U3@mid.individual.net>:

> Actually had a success story with AI to share.
> 
> Using ChatGPT, regarding Linux, I was able to give it my current output
> of "ifconfig -a" and have it generate an accurate netplan yaml file for
> network configuration -- which worked.
> 
> Then I had it add some policy routing, which also worked.
> 
> I did this to renumber three servers.  The only snag was when I went to
> reconfigure the Red Hat-based server...it was so old, it didn't support
> Red Hat's more modern network configuration scriptlets.  So I had
> ChatGPT walk me through writing a script to do the configuration, then
> set up a systemd unit file to run the script when the networking service
> started.  All done.
> 
> I was pleasantly surprised at how accurate ChatGPT was with its
> configuration directives, scripting, and unit file setup.

Here is the netplan yaml file, with IP addresses anonymized:

network:
  version: 2
  renderer: networkd

  ethernets:
    eth0:
      match:
        macaddress: 00:11:22:33:44:55
      set-name: eth0
      addresses:
        - 192.0.2.10/29         # Source IP 1
        - 198.51.100.10/28      # Source IP 2
      dhcp4: no
      dhcp6: no
      ipv6-link-local: [auto]

      routing-policy:
        - from: 192.0.2.10
          table: 100
        - from: 198.51.100.10
          table: 200

      routes:
        # Table 100 for 192.0.2.10
        - to: 0.0.0.0/0
          via: 192.0.2.1
          table: 100
          metric: 100
        - to: 192.0.2.0/29
          scope: link
          table: 100

        # Table 200 for 198.51.100.10
        - to: 0.0.0.0/0
          via: 198.51.100.1
          table: 200
          metric: 200
        - to: 198.51.100.0/28
          scope: link
          table: 200

        # Fallback default route
        - to: 0.0.0.0/0
          via: 198.51.100.1
          metric: 500

    eth1:
      match:
        macaddress: 00:11:22:33:44:66
      set-name: eth1
      addresses:
        - 10.0.0.10/24
      dhcp4: no
      dhcp6: no
      routes:
        - to: 10.0.0.0/24
          scope: link

-- 
-v

[toc] | [prev] | [next] | [standalone]


#300

From% <pursent100@gmail.com>
Date2025-04-30 19:27 -0700
Message-ID<43WdnZljzpOZQY_1nZ2dnZfqnPadnZ2d@giganews.com>
In reply to#299
vallor wrote:
> On 27 Apr 2025 04:26:11 GMT, Creon <creon@creon.earth> wrote in
> <m75pv3Fc894U3@mid.individual.net>:
> 
>> Actually had a success story with AI to share.
>>
>> Using ChatGPT, regarding Linux, I was able to give it my current output
>> of "ifconfig -a" and have it generate an accurate netplan yaml file for
>> network configuration -- which worked.
>>
>> Then I had it add some policy routing, which also worked.
>>
>> I did this to renumber three servers.  The only snag was when I went to
>> reconfigure the Red Hat-based server...it was so old, it didn't support
>> Red Hat's more modern network configuration scriptlets.  So I had
>> ChatGPT walk me through writing a script to do the configuration, then
>> set up a systemd unit file to run the script when the networking service
>> started.  All done.
>>
>> I was pleasantly surprised at how accurate ChatGPT was with its
>> configuration directives, scripting, and unit file setup.
> 
> Here is the netplan yaml file, with IP addresses anonymized:
> 
> network:
>    version: 2
>    renderer: networkd
> 
>    ethernets:
>      eth0:
>        match:
>          macaddress: 00:11:22:33:44:55
>        set-name: eth0
>        addresses:
>          - 192.0.2.10/29         # Source IP 1
>          - 198.51.100.10/28      # Source IP 2
>        dhcp4: no
>        dhcp6: no
>        ipv6-link-local: [auto]
> 
>        routing-policy:
>          - from: 192.0.2.10
>            table: 100
>          - from: 198.51.100.10
>            table: 200
> 
>        routes:
>          # Table 100 for 192.0.2.10
>          - to: 0.0.0.0/0
>            via: 192.0.2.1
>            table: 100
>            metric: 100
>          - to: 192.0.2.0/29
>            scope: link
>            table: 100
> 
>          # Table 200 for 198.51.100.10
>          - to: 0.0.0.0/0
>            via: 198.51.100.1
>            table: 200
>            metric: 200
>          - to: 198.51.100.0/28
>            scope: link
>            table: 200
> 
>          # Fallback default route
>          - to: 0.0.0.0/0
>            via: 198.51.100.1
>            metric: 500
> 
>      eth1:
>        match:
>          macaddress: 00:11:22:33:44:66
>        set-name: eth1
>        addresses:
>          - 10.0.0.10/24
>        dhcp4: no
>        dhcp6: no
>        routes:
>          - to: 10.0.0.0/24
>            scope: link
> 
troll

[toc] | [prev] | [standalone]


Back to top | Article view | comp.ai.shells


csiph-web