Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 09 Dec 2018, 22:09
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
corepup/mcorepup users can ask fig questions here
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [9 Posts]  
Author Message
nosystemdthanks

Joined: 03 May 2018
Posts: 537

PostPosted: Fri 20 Jul 2018, 00:26    Post subject:  corepup/mcorepup users can ask fig questions here  

ive used mostly debian for years-- /etc/rc.local is or pre-systemd, was the primary place to put startup items that run without xorg.

i would think that most people would find /etc/rc.local on /dev/sda1, but you should never assume, right?

so basically i want to know which partitions people would find their own /etc/rc.local or /etc/rc.d or whatever on. preferably listed in order of likelihood (sda1, sdb1, sda2)

i normally assume its going to be on sda1, sdb1, sda2, or sdb2.

so if theres more i should include, tell me. i probably wont include more than a couple in addition to those.

even if you think it is, this is not a debian question. its a whatever-distro-you-use most question.

i dont use debian these days, i only mentioned it because when i say "/etc/rc.local" i might actually mean the equivalent of "/etc/rc.local" in puppy, or the distro you use.

_________________
the end of the distro war, and the distro https://ptpb.pw/OnBT

Last edited by nosystemdthanks on Tue 31 Jul 2018, 20:54; edited 4 times in total
Back to top
View user's profile Send private message Visit poster's website 
wiak

Joined: 11 Dec 2007
Posts: 1012
Location: not Bulgaria

PostPosted: Fri 20 Jul 2018, 07:48    Post subject:  

I'm not sure what 'Puppy Project' this is about or if it is about full or frugal installs, but I think you will be limiting your project significantly if designed for sda1 or 2 or sdb1 or 2 only. My own system, for years, stores most distributions I use (frugal installs) on /dev/sda5 but sometimes I put some on /dev/sda6 or /dev/sda7 (the last partition I have on my machine). As far as usb installs are concerned, that would usually refer to /dev/sdb (but not alway since several usb ports on here and I often partition usb drives into 3 partitions (reserving the first as fat32 and the rest as linux format of one sort or the other).

One reason why sda1 or even sda2 are often not used for Linux is that the computers come with manufacturer installed Windoze, on ntfs partitions, and quite often the first three partitions are used by manufacturers for system related files. On my HP, Windoze was manufacturer installed to /dev/sda2, /dev/sda1 was used for Windoze boot system files and /dev/sda3 for HP System Diagnostics. That's quite a typical arrangement for HP machines - or at least I've seen it before several times. I thus use extended partitions so next user partition is /dev/sda5, because I prefer to use ext3 or ext4 rather than frugal install alongside Windoze on ntfs.

Since I don't know what your question/project is about all of this post may be irrelevant...

wiak
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 13146
Location: Gatineau (Qc), Canada

PostPosted: Fri 20 Jul 2018, 08:32    Post subject:  

Euh... nosystemdthanks?

On Puppy, it does not matter, because /etc/rc.d/rc.local is within the main
Puppy sfs. Now this main Puppy sfs, as you will remember (??) Wink , can
be on any partition, even on a CD or DVD. Puppy doesn't care about these
things!

Same goes for /etc/init.d, where you can store scripts that you want
started as early as possible during the boot provess; e.g. start_lxrandr.

Laughing May i suggest that you stick with Puppy for longer periods at a time?
All those fancy alien distros you've been studying are turning your
head!!! Laughing (No offense intended. This is a joke!)

Wink BFN.

_________________
musher0
~~~~~~~~~~
Je suis né pour aimer et non pas pour haïr. (Sophocle) /
I was born to love and not to hate. (Sophocles)
Back to top
View user's profile Send private message 
nosystemdthanks

Joined: 03 May 2018
Posts: 537

PostPosted: Fri 20 Jul 2018, 09:40    Post subject:  

musher, im only referring to full installed versions. cd and even frugal wouldnt count (trust me, most distros would allow /etc/rc.local on a cd)

however, youre both right. im just going to have to come up with a way to make it more flexible. i was thinking about that while shaving (dont worry, i use an electric, so its a bit safer to design software at the same time.)

as to why this is in puppy projects, may not be obvious how this belongs here, though it will likely become easier to tell. im going to reuse this thread with a different title. thank you both.

_________________
the end of the distro war, and the distro https://ptpb.pw/OnBT
Back to top
View user's profile Send private message Visit poster's website 
rufwoof

Joined: 24 Feb 2014
Posts: 2706

PostPosted: Fri 20 Jul 2018, 10:59    Post subject:  

Under / on the first partition, of finite size. i.e. in accordance with OpenBSD's slicing (partitioning) and default file ownerships (along with process ownerships) - which are likely the best authoritive guide. This is the slicing of my single disk OBSD that were the defaults created during installation ...
Code:

  a:          2097152               64  4.2BSD   2048 16384 12958 # /
  b:          4160640          2097216    swap                    # none
  c:        625142448                0  unused                   
  d:          8388608          6257856  4.2BSD   2048 16384 12958 # /tmp
  e:         15661312         14646464  4.2BSD   2048 16384 12958 # /var
  f:          4194304         30307776  4.2BSD   2048 16384 12958 # /usr
  g:          2097152         34502080  4.2BSD   2048 16384 12958 # /usr/X11R6
  h:         20971520         36599232  4.2BSD   2048 16384 12958 # /usr/local
  i:          4194304         57570752  4.2BSD   2048 16384 12958 # /usr/src
  j:         12582912         61765056  4.2BSD   2048 16384 12958 # /usr/obj
  k:        550789376         74347968  4.2BSD   4096 32768 26062 # /home

Unused c slice is just the whole disk - typically used if you want to dd copy the whole HDD. Not seeing /etc within that indicates that /etc is under /

For systems such as Puppy .... immaterial, as many of the file/folder permissions will have been casually set. As are the process ownerships. So pretty much irrelevant where /etc/rc.conf might be located.

For security and making updates easier, OpenBSD leaves /etc/rc.conf unchanged and records all changes in /etc/rc.local.conf instead.

_________________
( ͡° ͜ʖ ͡°) :wq

Last edited by rufwoof on Fri 20 Jul 2018, 11:06; edited 1 time in total
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1547

PostPosted: Fri 20 Jul 2018, 11:00    Post subject:  

I have a full install of puppy on sda4, which is ext4 and 20GB. The reason for this is the recovery stuff for Windows is on sda1 (5GB fat32 partition) and it complains if you put the ntfs on anything but sda2 when doing a factory reset for XP. The machine has 1GB ram so on sda3 I have a linux-swap partition (though it seems I could have just used a swap-file on sda4 too, maybe next time).
Back to top
View user's profile Send private message 
nosystemdthanks

Joined: 03 May 2018
Posts: 537

PostPosted: Fri 20 Jul 2018, 17:45    Post subject:  

definitely going to go flexible with this. i was hoping to avoid that, but only with unrealistic notions of a convention as much as i thought.

thanks for the replies. this thread will likely be reused for related questions. a that point i will rename the title.

i want to add a setting for rc.local to be remastered as a profile. even if youre not following what im doing, basically youd just add rclocal-sda1 and it would load rclocal from sda1.

its really no extra trouble to make it slightly more clever and be able to get any partition from after the rclocal- part.

it was one of those trying to follow a thing that is actually very easy to work around things. so if you have rc.local on sdd4/etc/rc.local you can say rclocal-sdd4 or even sdd4/etc/rc.d/rc.local if you put it somewhere else.

_________________
the end of the distro war, and the distro https://ptpb.pw/OnBT
Back to top
View user's profile Send private message Visit poster's website 
nosystemdthanks

Joined: 03 May 2018
Posts: 537

PostPosted: Thu 26 Jul 2018, 18:31    Post subject: Re: corepup/puppy/debian LICENSE question: favourite license  

most people dont like software licenses, that doesnt bother me. without copyright, we might not need software licenses.

i dont think copyright is all bad, and when it gets too restrictive it definitely isnt all good.

most free software advocates prefer "copyleft" licenses. i would too, if copyright terms were 5 to 15 years long-- rather than life of the author + 75 years. but the copyright term in most or all countries, has never gotten shorter unless it went from "perpetual" to limited.

for most things, i use a cc0 public domain dedication. its gpl-compatible, and pretty much lets you do "wtf you want" like the wtfpl does.

if you use code that was released under the cc0, and youre trying to figure out if youve "complied with it" then you probably have! it doesnt get simpler than that.

there are arguments that can be made for both permissive and copyleft licenses.

the bsd community tends to hate and resist copyleft like the gpl, i get it, i understand.

i dont feel as strongly about that. the gpl has its place, but i tend to license things in a way that is friendly to the bsd community, just because i like cc0.

i expect different people to feel differently about this. in fact i expect most to say "i dont care, i wish i didnt have to care about it."

or "i dont have to care about it because i just work on puppy, and its under whatever licenses puppy uses."

feel free to say it doesnt matter to you-- thats useful data as well-- but i am mostly asking to find out from people that do have some preference.

_________________
the end of the distro war, and the distro https://ptpb.pw/OnBT
Back to top
View user's profile Send private message Visit poster's website 
nosystemdthanks

Joined: 03 May 2018
Posts: 537

PostPosted: Tue 31 Jul 2018, 21:13    Post subject: Re: corepup/mcorepup users can ask fig questions here  

to avoid too many corepup threads, i created this one to have the subject changed from time to time, but all the subjects are related to corepup. the corepup thread is large and the mcorepup thread is mostly for a peripheral effort, right now this thread is for explaning the language that mcorepup is made with: fig.

some basics include-- how to run shell code:

now "echo 'this is shell code' | grep 'shell code' --color=always" ; shell



like most lines in fig, the code goes left-to-right, "now" is a variable. the middle part is a string, and "shell" is a command to run the code.

nearly all lines of fig begin with a variable. the exceptions are lines that use commands that dont share a line. these are generally commands that start functions, loops, conditionals-- and a few commands that change the mode of the language.

"textmode" forces graphics commands to run in the term window, even if pygame (used for graphics) is installed. if pygame isnt present, textmode becomes the default.

but most commands share a line with a variable on the left.

so this line:

p "hello" ucase left 2 plus "y" print

or with optional syntax:

p = "hello" | ucase | left 2 | plus "y" | print



shows you the loose relationship between how fig works and how shell languages work.

unlike smalltalk, which is left-to-right except for parentheses, there is no way to change the left-to-right pattern in fig. you can group lines into functions:

function ucaseleft (what, howmany)
now = what ; ucase
text = now ; left howmany ; return text
fig

p = "hello" | ucaseleft p 2 | plus "y" | print



conditionals are simple:

ifequal y p
now "y and p are equal" print
else
now "y and p differ" print
fig

"fig" is like unindenting in python. you can also use: "wend, next, resume" but think of "fig" like "fi" in the shell.

fig has no native command names with only two letters, each name has at least 3 (all the one and two-letter abbreviations are yours.)

now ; cls



to create an array, you can use split:

now "hello there hey" split now " "

or use the arr command:

now "hello" arr
now plus "there"
now plus "hey"
now print

these are python lists, if you use python.



setting the left variable zeros the variable.

p print # prints 0

p 5 # sets p to 5
p print # prints 0

p 5 print # prints 5

except for arrays, because they might hold and manage a lot of information:

p 5 arr
p print # prints [5]

_________________
the end of the distro war, and the distro https://ptpb.pw/OnBT
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 1 [9 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0574s ][ Queries: 12 (0.0123s) ][ GZIP on ]