Hi,
Since finding the equivalent functions to fork() and wait() in bash is
difficult and requires workarounds I am choosing another interpreted
language: Perl.
Is Perl OK?
Edward
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi
Le 15/06/2016 18:57, Edward Bartolo a écrit :
Hi,
I am saying the child and parent at not the same at the point fork()
executes for the following reasons taken from "man 2 fork".
Quote taken from "man 2 fork": (Please not the*except*)
<<
The new process, referred to as the child, is an
Hi,
I am saying the child and parent at not the same at the point fork()
executes for the following reasons taken from "man 2 fork".
Quote taken from "man 2 fork": (Please not the *except*)
<<
The new process, referred to as the child, is an exact
duplicate of the
calling process
Le 14/06/2016 19:24, Edward Bartolo a écrit :
To me fork() looks much more than simply a function that does
some processing returning a result as it looks more like an
instruction directed at the kernel scheduler to split the process into
a parent and child that are not equal in all respects.
In python you can definitely fork/wait as I have done it, and I have also
made an init entirely in Python 3 :P.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
On Wed, Jun 15, 2016 at 06:21:36AM +0200, Edward Bartolo wrote:
> Hi,
>
> Before I give up writing Felker's C code in bash, can I use another
> interpreted language that has more probability of having wait(int*)
> and fork()?
Perl will do it. There excellent introductory books
available for free
Hi,
Before I give up writing Felker's C code in bash, can I use another
interpreted language that has more probability of having wait(int*)
and fork()?
Edward
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo
On Tue, 14 Jun 2016 22:21:00 +0200, Edward Bartolo wrote:
> Irrwahn wrote:
> << apparently simply content with
> writing bad code >>
>
> Bad code is not good for anyone let alone as an init. What I am doing
> it experimenting so that I further understand which lines of the code
> play the central
Hi,
Irrwahn wrote:
<< apparently simply content with
writing bad code >>
Bad code is not good for anyone let alone as an init. What I am doing
it experimenting so that I further understand which lines of the code
play the central roles and which lines play auxiliary roles. In my
almost fifty year
[Afer the fact I notice this has become a rather wordy
message, mainly due to my difficulties to express myself
clearly in plain English; please ignore at at will.]
On Tue, 14 Jun 2016 14:14:15 -0400, Steve Litt wrote:
> You and I have a difference of beliefs concerning learning. You believe
>
On Tue, 14 Jun 2016 17:35:52 +0200
Irrwahn wrote:
> At the moment, at least to me, it unfortunately looks like he
> refuses to learn _anything_ of what he's being told, up to the
> point I am beginning to have doubts he's not simply trolling.
I can assure you he's not trolling, because I do
Hi,
KatolaZ wrote:
<<
but when somebody writes to a ML asking for suggestions on a
topic I usually assume that s/he really wants to receive some
information on that topic
>>
Thanks to this mailing thread, I now understand what fork() actually
does. To me fork() looks much more than simply a funct
On Tue, Jun 14, 2016 at 10:59:05AM -0400, Steve Litt wrote:
>
> I think Edward's being sucked into a vortex of basics at lightning
> speed, and within a couple weeks will know as much about the basics
> necessary for Felker PID1 as you do (which would be twice what I know,
> I found your explanatio
On Tue, Jun 14, 2016 at 10:59:05AM -0400, Steve Litt wrote:
> On Tue, 14 Jun 2016 15:50:37 +0200
> Irrwahn wrote:
>
> > We could play this game day in, day out for months or even
> > years, without having you grasp the basics necessary to
> > fully understand the implications of even moderately
On Tue, 14 Jun 2016 10:59:05 -0400, Steve Litt wrote:
> On Tue, 14 Jun 2016 15:50:37 +0200
> Irrwahn wrote:
>
>> We could play this game day in, day out for months or even
>> years, without having you grasp the basics necessary to
>> fully understand the implications of even moderately
>> soph
On Tue, 14 Jun 2016 15:51:23 +0200, Edward Bartolo wrote:
> Hi,
>
> I am trying to implement a small shell script to serve as an init but
> I am failing to find C equivalent functions to wait(int) and
> fork(void). These two functions are essential to create an init as
> zombies have to be somehow
On Tue, 14 Jun 2016 15:50:37 +0200
Irrwahn wrote:
> We could play this game day in, day out for months or even
> years, without having you grasp the basics necessary to
> fully understand the implications of even moderately
> sophisticated C programs.
This discussion is getting theoretical,
On Tue, 14 Jun 2016 15:51:23 +0200
Edward Bartolo wrote:
> Hi,
>
> I am trying to implement a small shell script to serve as an init but
> I am failing to find C equivalent functions to wait(int) and
> fork(void). These two functions are essential to create an init as
> zombies have to be someho
Edward, please comment the daylights out of it. Your shellscript might
be used for education, proof of concept, and propaganda for years to
come. If your shellscript had existed in the fall of 2014, I would have
tried it before I tried Felker.
SteveT
On Tue, 14 Jun 2016 13:16:03 +0200
Edward Bart
On Tue, 14 Jun 2016 13:08:59 +0200, Edward Bartolo wrote:
[...]
> Now I would like to ask what is the need of the fork() call in
> Felker's code. Yes, I know, it creates a child that continues
> execution just after the fork call.
[...]
> I checked with XFCE4 loaded how many instances of felker2.b
Hi,
I am trying to implement a small shell script to serve as an init but
I am failing to find C equivalent functions to wait(int) and
fork(void). These two functions are essential to create an init as
zombies have to be somehow reaped. In a shell script I can append & to
a statement to make it ru
Hi,
Since Felker's minimal init as coded in C works, I will now try to
implement it in /bin/sh script, hopefully.
If it works as intended, I will post the resulting script.
Edward
On 14/06/2016, Edward Bartolo wrote:
> Hi,
>
> I wrote a small shell script, nothing special, mind you, that calls
Hi,
I wrote a small shell script, nothing special, mind you, that calls rc
S and then rc 2 if rc S is successful. With Felker's minimal init,
which I edited to call my script version, I was able to load a useable
XFCE4 session through which I am sending this email.
I am attaching both Felker's C
On Tue, Jun 14, 2016 at 12:13:12PM +0200, Irrwahn wrote:
[cut]
>
> Well, I was thinking about being able to shutdown or
> reboot the machine by sending signals to PID1. I am
> however aware it's debatable if that can still be
> considered a sane concept in the 21st century.
>
> And TBH, sta
On Tue, 14 Jun 2016 11:20:25 +0200, Edward Bartolo wrote:
> On 14/06/2016, Irrwahn wrote:
>> On Tue, 14 Jun 2016 10:47:02 +0200, Edward Bartolo wrote:
>>> With some code editing to load a shell using the command system(), I
>>> finally am using Felker's minimal init.
[...]
>> Now, for a little
Hi,
On 14/06/2016, Irrwahn wrote:
> On Tue, 14 Jun 2016 10:47:02 +0200, Edward Bartolo wrote:
>> Hi,
>>
>> With some code editing to load a shell using the command system(), I
>> finally am using Felker's minimal init. In fact, I am posting this
>> through XFCE4 using Felker's minimal init.
>>
>
On Tue, 14 Jun 2016 09:33:59 +0200, Irrwahn Grausewitz wrote:
[Sorry for piggy-backing on my own post here.]
Just for the fun of it, here's a more elaborate discussion
of Felker's minimal init code:
> #define _XOPEN_SOURCE 700
> #include
> #include
Add
#include
here to satisfy the compi
On Tue, 14 Jun 2016 08:54:12 +0200
Edward Bartolo wrote:
> According to my logic the endless loops should be at the
> end rather than at the middle of the code.
You need to write several programs using fork(). After a call to
fork(), there are two copies of that same program running, the main
d
Le 14/06/2016 10:11, Steve Litt a écrit :
>With all the due respect, anyone can put a few lines in a shell script
>or in a C code to create two devices and call rc. But we should be
>honest and tell Bartolo, and anybody else willing to go down this
>path, that this is not exactly "making a custom
On Tue, 14 Jun 2016 08:54:12 +0200
Edward Bartolo wrote:
> Hi,
>
> I downloaded and compiled Felker's minimal init but found it didn't
> work. Examining the code it seems that the website had been
> vandalised. According to my logic the endless loops should be at the
> end rather than at the mid
On Tue, 14 Jun 2016 05:44:27 +0100
KatolaZ wrote:
> On Mon, Jun 13, 2016 at 09:37:11PM -0400, Steve Litt wrote:
>
> [cut]
>
> >
> > Right now, Felker's PID1 is the acknowledged "Hello World" PID1.
> > But as I remember you have to add an #include to get it to work with
> > mainstream Linuxes,
Le 14/06/2016 08:54, Edward Bartolo a écrit :
Hi,
I downloaded and compiled Felker's minimal init but found it didn't
work. Examining the code it seems that the website had been
vandalised. According to my logic the endless loops should be at the
end rather than at the middle of the code. Furthe
On Tue, 14 Jun 2016 08:54:12 +0200, Edward Bartolo wrote:
> Hi,
>
> I downloaded and compiled Felker's minimal init but found it didn't
> work. Examining the code it seems that the website had been
> vandalised.
Assuming you are referring to the code quoted below:
No, it's the correct version,
Hi,
I downloaded and compiled Felker's minimal init but found it didn't
work. Examining the code it seems that the website had been
vandalised. According to my logic the endless loops should be at the
end rather than at the middle of the code. Furthermore, the code seems
to first block signals the
On Mon, 13 Jun 2016 21:37:11 -0400, Steve Litt wrote:
> On Mon, 13 Jun 2016 22:49:27 +0200
> Irrwahn wrote:
[...]
>> I'm probably missing something important here, so I have
>> to ask: What would be the point in replacing an easily
>> comprehensible, self-contained and statically linked piece
On Mon, Jun 13, 2016 at 09:37:11PM -0400, Steve Litt wrote:
[cut]
>
> Right now, Felker's PID1 is the acknowledged "Hello World" PID1. But as
> I remember you have to add an #include to get it to work with
> mainstream Linuxes, you have to get it to compile, and it's just not as
> understandable
On Mon, 13 Jun 2016 22:49:27 +0200
Irrwahn wrote:
> On Mon, 13 Jun 2016 15:47:49 -0400, Steve Litt wrote:
> [...]
> > Then I'd write a shellscript workalike for Suckless Init. In my
> > opinion, once you've done that, you should publicize it like the
> > Autumn leaves, because you've done a serv
On Mon, 13 Jun 2016 11:02:12 +0200
Didier Kryn wrote:
> Le 13/06/2016 08:16, Edward Bartolo a écrit :
> > Hi,
> >
> > This is a question about implementing a minimal OS initiator. If
> > DNG's admins/mods deem this email is misplaced please delete it or
> > ignore it.
> >
> > Till now, I impleme
On Mon, 13 Jun 2016 10:19:43 +0200
Tomasz Torcz wrote:
> On Mon, Jun 13, 2016 at 08:16:44AM +0200, Edward Bartolo wrote:
> > Hi,
> >
> > This is a question about implementing a minimal OS initiator. If
> > DNG's admins/mods deem this email is misplaced please delete it or
> > ignore it.
>
>
On Mon, 13 Jun 2016 23:49:45 +0200, Didier Kryn wrote:
> Le 13/06/2016 22:49, Irrwahn a écrit :
[...]
>> I'm probably missing something important here, so I have
>> to ask: What would be the point in replacing an easily
>> comprehensible, self-contained and statically linked piece
>> of code[1] by
Le 13/06/2016 22:49, Irrwahn a écrit :
On Mon, 13 Jun 2016 15:47:49 -0400, Steve Litt wrote:
[...]
Then I'd write a shellscript workalike for Suckless Init. In my
opinion, once you've done that, you should publicize it like the Autumn
leaves, because you've done a service to all of Linuxdom, and
On Mon, 13 Jun 2016 15:47:49 -0400, Steve Litt wrote:
[...]
> Then I'd write a shellscript workalike for Suckless Init. In my
> opinion, once you've done that, you should publicize it like the Autumn
> leaves, because you've done a service to all of Linuxdom, and you've
> especially done a service
On Mon, 13 Jun 2016 08:16:44 +0200
Edward Bartolo wrote:
> Hi,
>
> This is a question about implementing a minimal OS initiator. If
> DNG's admins/mods deem this email is misplaced please delete it or
> ignore it.
>
> Till now, I implemented a little OS initiator that calls "/bin/bash"
> and t
Hi,
Many thanks for your replies especially for:
https://felipec.wordpress.com/2013/11/04/init/
Edward
On 13/06/2016, Didier Kryn wrote:
> Le 13/06/2016 08:16, Edward Bartolo a écrit :
>> Hi,
>>
>> This is a question about implementing a minimal OS initiator. If
>> DNG's admins/mods deem thi
Le 13/06/2016 08:16, Edward Bartolo a écrit :
Hi,
This is a question about implementing a minimal OS initiator. If
DNG's admins/mods deem this email is misplaced please delete it or
ignore it.
Till now, I implemented a little OS initiator that calls "/bin/bash"
and then enters an infinite whil
On 13/06/16 16:19, Tomasz Torcz wrote:
On Mon, Jun 13, 2016 at 08:16:44AM +0200, Edward Bartolo wrote:
Hi,
This is a question about implementing a minimal OS initiator. If
DNG's admins/mods deem this email is misplaced please delete it or
ignore it.
If you really want to create yet another
On Mon, Jun 13, 2016 at 08:16:44AM +0200, Edward Bartolo wrote:
> Hi,
>
> This is a question about implementing a minimal OS initiator. If
> DNG's admins/mods deem this email is misplaced please delete it or
> ignore it.
If you really want to create yet another init, I can recommend this
simpl
On 13/06/16 15:29, KatolaZ wrote:
If I can provide my 2 cents to the discusion, before writing a new
init you should have studied and understood very well one of the
existing ones, and what should happen behind the scenes from the
moment your kernel is decompressed to the appearance of a login
t
On Mon, Jun 13, 2016 at 08:16:44AM +0200, Edward Bartolo wrote:
> Hi,
>
> This is a question about implementing a minimal OS initiator. If
> DNG's admins/mods deem this email is misplaced please delete it or
> ignore it.
>
> Till now, I implemented a little OS initiator that calls "/bin/bash"
>
49 matches
Mail list logo
