(old)Puppy Linux Discussion Forum

What is this? I'm not supposed to be building a Quirky, I thought I was building a "Jessie_Puppy".

is be spent the last few days riding the intercity metro bus to get around, some what concerned about the lack of front teeth seen on the riders nearby. Kinda a rough ride and lots of metal bars at teeth level.

Ted Dog wrote: is be spent the last few days riding the intercity metro bus to get around, some what concerned about the lack of front teeth seen on the riders nearby. Kinda a rough ride and lots of metal bars at teeth level.

Hi, Ted.

Someone got his front teeth kicked while using woof-CE on the intercity
bus? Jo no comprendo.

What's the relationship with the current thread, please?

BFN.

musher0

I used is be in my on topic post which is like local street talk..

Back on to topic, Devuan naming for puppy version could be based on minor planet 10504 - Doga


Yo no sé espanol

Ted Dog wrote:I used is be in my on topic post which is like local street talk..

Back on to topic, Devuan naming for puppy version could be based on minor planet 10504 - Doga

Yo no sé espanol

No, I don't know espanol, it's just something we say in these French parts
when something looks very weird and we really don't understand.

Devuan appears to be a fork of Debian dating back this Spring.
Title from -- https://ixquick.com/do/search?q=Devuan&l=francais --
> systemd row ends with Debian getting forked • The Register
Devuan, a planet? I wouldn't know.

Thanks for keeping me company. I'm getting cross-eyed watching this
woof-CE thing download stuff.

BFN.

musher0

Forty minutes into it: "processing gawk", which is a slow poke compared to
other awks, mawk, for ex. But what can you do? TWYL.

I'm on libpcap something or other.... This is apparently a long process but I think it'll be fun once all the downloading is complete.

A short detour through linguistics, here, for musher0 and Ted Dog... and anyone else interested (or bored ).

"Yo no comprendo" (J = 'H' sound, not 'Y' sound, in Spanish) is "I do not know".

For the record, the way Spanish works you can actually drop the 'yo' -- "No comprendo" and "Yo no comprendo" are functionally identical, because the way the verb ('comprender', to know) is conjugated, it actually incorporates the subject of the sentence ('yo' is first person singular -- that is to say, I/me).

"Yo no sé espanol" (or "No sé espanol") is another way of writing the same thing, although the 'n' in 'español' really does need the tilde (~) over it. That indicates a 'nya' sort of sound, rather than a 'na' sort of sound. While I'm here I'll note that the accent (an acute -- going the other way it would be a grave (pronounced "grahv" not "grayv") over the 'e' in 'sé' is to indicate that the emphasis is on the first syllable. In Spanish, default emphasis is on the second syllable.

For the record, the infinitive form of 'sé' is 'saber' (sah-BEHR). 'Ser', as it turns out, is actually the infinitive form of 'is', which (I have heard) is an irregular verb in every single language on Earth.

Mind you I'm six years out of college and either ten or ten-and-a-half out of my Spanish course... so if I've got all this wrong and I'm talking out my admittedly overly-padded posterior -- someone please correct me!

<HIGH FIVES starhawk> going off topic with gusto... muy muy gusto ¤

how much space does a working environment need.

Ted Dog wrote: how much space does a working environment need.

10 GB should be comfortable.

01micko wrote:

Ted Dog wrote: how much space does a working environment need.

10 GB should be comfortable.

When I run woof-CE on my most powerful laptop, I run it inside a 4GB tmpfs and it's good enough. Running it from RAM makes 2createpackages much faster.

By the way: I haven't mentioned it - some configurations won't produce a Puppy that boots or works afterwards. The Ubuntu Trusty configuration works for sure, though - that's why I recommend newcomers to use it before they do wild things with woof-CE.

@ Ted Dog -- I was simply trying to help out, since I felt I could. Would you have preferred that I had not?

Iguleder wrote:(...)

By the way: I haven't mentioned it - some configurations won't produce a Puppy that boots or works afterwards. (...)

Very funny. (Since I'm almost done with the Devuan Jessie Pup...)
Now he tells us...

Ok. Woof-CE is now squishing me a "puduan-6" Puppy, not Debian, not
Devuan! Puduan. (Probably the name of an unknown planet... in ref. to
Ted's remark earlier.) Should I or ?

Nah, MusherO was giving me a hard time on a minor off topic and then you post such an opus, I thought you were being ironic with your post. So high five your understated humor. I it was not a ironic of topic post then no hugh 5
Sadly looks like he is busy builting a possible non working or booting experience. Still holding out my attempt at WolfCE till more landmines are cleared. STILL need a working WolfCE build-ed distro recommendation for a build environment. Turns out my two presets are not WolfCE based.

@musher0

Devuan, Debian, Ubuntu, Trisquel (from Iguleder's fork) and to a degree Slackware should all build fine.

We should probably put in a mechanism that detects if config files for a certain distro haven't been touched for an arbitrary amount of time (say 100 days?) and pop a warning that there may be certain failures.

Mageia, Arch and T2 haven't been touched for quite a while.

musher0 wrote:Now he tells us...

You should have read the first post carefully. I don't like this hostile attitude.

01micko wrote:Devuan, Debian, Ubuntu, Trisquel (from Iguleder's fork) and to a degree Slackware should all build fine.

All Trisquel support is in woof-CE. My fork has only the files under woof-distro (the package list, etc').

01micko wrote:We should probably put in a mechanism that detects if config files for a certain distro haven't been touched for an arbitrary amount of time (say 100 days?) and pop a warning that there may be certain failures.

I want this solution to be git rm. Configuration files for unsupported or old distros should be deleted. And yes, if we don't actively support Magiea, T2 and other distros that code should be removed. Less code - less bugs.

Ok has T2 ever been built? that is where I was heading in my learning trip with WolfCE. could be my SECOND try after a Slacko64 try.

Hello again.

At the build iso question, I answered "(space)ENTER", but it still went
ahead with burning. Although the script said: "type any character then
Enter if you don't want to burn."

I thought (space) was a valid ASCII character!

Luckily I'm a character too, and my dvd was unusable.
(Don't look for any relevance, there isn't any!)

The script also warned me that Bacon dev was not in the devx, with some
instructions how to include it. A bit late now, I'd say! while it's
squishing the devx.

This is lots of fun!

musher0

Ted Dog wrote:Ok has T2 ever been built? that is where I was heading in my learning trip with WolfCE. could be my SECOND try after a Slacko64 try.

That was Barry's. If you wanted to leverage Barry's latest T2 packages you could point the repos to Barry's quirky repo (x86 or x86_64) but there would need to be changes in all the setup scripts to accommodate T2_64.

So, learn woof-ce, build a slacko64, then keep your fork updated, make changes for T2, build it, break it, rebuild it, repeat and then push (issue pull request) the result.