maxlinux-devel — The Developers mailing list for InceptionOS

Re: [Maxlinux-devel] inceptionos.org

[Terry C. <te...@do...>]

Enrico Kern <ph...@h0...> Said:

> ok i think thats a fine place.. but what do u want to host instead a 
> redirect to sf? We have all, mailinglist, space, shells,, and the best is 
> that All Developer have access to the files not only a few persons. In 
> some cases i prefer the outside sf hosting (i dont like sf so much). But 
> we need resources, the package team has about 10GB of packages, we need a 
> "fast" ftp for this. Have you traffic limits on your host? I connect a 
> server direct for ftp use next week but i have problems with the harddisk 
> capacities *need harddisk* ;)

The machine inceptionos.org points to at the moment has 26 gig free, with
another 20 avaliable elsewhere, so space isn't an issue TBH. There's no
traffic limits.

FYI - it's actually a Cobalt RaQ 4r.

> I would say, setup mailinglist, cvs, ftp and give some people or all 
> developers access. and we should move.. what do you mean kelledin? I am 
> only a little developer, no maintainer its your right ;)

There'll be no problems setting up any of the above, but I'll leave
the discussion open for a while before doing so...
-- 
Terry Churchill	:	http://www.doc-linux.co.uk/

If it doesn't work, force it. If it breaks, it needed replacing anyway.

Re: [Maxlinux-devel] inceptionos.org

[Enrico K. <ph...@h0...>]

Hi ,

ok i think thats a fine place.. but what do u want to host instead a 
redirect to sf? We have all, mailinglist, space, shells,, and the best is 
that All Developer have access to the files not only a few persons. In 
some cases i prefer the outside sf hosting (i dont like sf so much). But 
we need resources, the package team has about 10GB of packages, we need a 
"fast" ftp for this. Have you traffic limits on your host? I connect a 
server direct for ftp use next week but i have problems with the harddisk 
capacities *need harddisk* ;)

I would say, setup mailinglist, cvs, ftp and give some people or all 
developers access. and we should move.. what do you mean kelledin? I am 
only a little developer, no maintainer its your right ;)


enrico

 On Tue, 20 Aug 
2002, Terry Churchill wrote:

> Hi,
> 
> Following an email conversation with Michael Lauzon last week I
> offered to register & host the inceptionos.org domain.
> 
> This has now been completed. I've setup hosting on one of
> my servers, with a 10mbit connection.
> 
> So - where do we go from here?
> 
> HTH
> -- 
> Terry Churchill	:	http://www.doc-linux.co.uk/
> 
> One distinguishing characteristic of BOFHen is attention deficit disorder.
> Put me in front of something boring and I can find a near-infinite number
> of really creative ways to bugger off.
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Maxlinux-devel mailing list
> Max...@li...
> https://lists.sourceforge.net/lists/listinfo/maxlinux-devel
> 

[Maxlinux-devel] inceptionos.org

[Terry C. <te...@do...>]

Hi,

Following an email conversation with Michael Lauzon last week I
offered to register & host the inceptionos.org domain.

This has now been completed. I've setup hosting on one of
my servers, with a 10mbit connection.

So - where do we go from here?

HTH
-- 
Terry Churchill	:	http://www.doc-linux.co.uk/

One distinguishing characteristic of BOFHen is attention deficit disorder.
Put me in front of something boring and I can find a near-infinite number
of really creative ways to bugger off.

Re: [Maxlinux-devel] Ok we doing! (fwd)

[Kelledin <kel...@sk...>]

On Monday 19 August 2002 03:39 am, Enrico Kern wrote:
> InceptionOS should handle .deb and .rpm packages?! Howto make
> without getting in Trouble of deinstall/install and depencies
> from packages, do we need a central index or somewhat?

Right now, we're mainly focused on rpm.  We might switch to deb,=20
but at this point it seems unlikely--all our packages will=20
probably stay in .rpm format.  The full extent of our deb=20
support will probably just extend to giving users the apt=20
toolset and letting them do what they want with it--basically=20
support debs the same way slackware supports rpms.

> And do you think we should basicaly include the pre-emptive
> patch? The window handling is a bit better and also this
> brings some more enhancements.

Definitely a good idea. :)  I might not have mentioned this, but=20
the linux-2.4.18-1 tarball comes with the preemption patch.  I=20
may tweak the preemption patch a bit, though; currently it works=20
great, but spews useless notices in my syslogs whenever=20
processes exit.

I may also include Ingo Molnar's O(1) scheduler, assuming I can=20
get it to play nice with the preempt patch.  Last time I tried=20
that, it caused my kernel to crap all over the place. =3D(

--
Kelledin
"If a server crashes in a server farm and no one pings it, does=20
it still cost four figures to fix?"

[Maxlinux-devel] Ok we doing! (fwd)

[Enrico K. <ph...@h0...>]

Hi Team ;)

Also i read your summary kelledin and started development on a simple 
dialog-based installationsystem (like the slackware setup). Currently it 
boots from cd and includes all i486 RPMS, it doesnt work correctly yet but 
i still work on it. For partitioning i use the standard fdisk, i think i 
need 5 days to show you a good working example.. should this be fine i 
port in c (but i find dialog and shellbased it easier to modify later also 
for GUI use). As you can see i downloaded only the 486 Packages, this 
packages are about 2,2GB and lies on my 100MBit/s host, for traffic 
reasons i dont make this public now, but i got a new dedicated system 
within the next 2 weeks where we setup a entire package-mirror i think.

Two Question,

InceptionOS should handle .deb and .rpm packages?! Howto make without 
getting in Trouble of deinstall/install and depencies from packages, do we 
need a central index or somewhat?

And do you think we should basicaly include the pre-emptive patch? The 
window handling is a bit better and also this brings some more 
enhancements.


Excuse my bad english ;)

Enrico

 -------------------------------------------------------
H Zero Seven - Unix/Linux Development and Research Team
http://www.h07.org

Re: [Maxlinux-devel] Homepage!

[Kelledin <kel...@sk...>]

On Monday 19 August 2002 02:38 am, Enrico Kern wrote:
> Sorry for this step without permission of you but i changed
> the Homepage, take a look @ maxlinux.sf.net
>
> Enrico

Sweet, I like it. :)  I don't know if Michael will take issue=20
about the sudden change, but I don't mind too much.

Only change I'd make to the homepage appearance at the moment is=20
to stick the SourceForge logo on there somewhere.  Details about=20
this little pseudo-requirement are at

http://sourceforge.net/docman/display_doc.php?docid=3D4297&group_id=3D1

(I call it a pseudo-requirement because SourceForge seems to be=20
pretty lax on enforcing it).

Also, if this isn't already done, news posts might be best=20
handled by a weblog driving a MySQL backend.  That will make it=20
easier for us to post news, and possibly gather user comments as=20
well.  One thing I've noticed about SourceForge is that people=20
who are "just passing through" a project's homepage often won't=20
actually go to the forums if they want to comment.

--=20
Kelledin
"If a server crashes in a server farm and no one pings it, does=20
it still cost four figures to fix?"

[Maxlinux-devel] Homepage!

[Enrico K. <ph...@h0...>]

Sorry for this step without permission of you but i changed the Homepage, 
take a look @ maxlinux.sf.net

Enrico

-------------------------------------------------------
H Zero Seven - Unix/Linux Development and Research Team
http://www.h07.org

Re: [Maxlinux-devel] Overview

[Kelledin <kel...@sk...>]

On Saturday 17 August 2002 10:56 am, Enrico Kern wrote:
> Hi,
>
> can anyone give me a full summary about the current
> development-Distribution? What does work e.g what stuff do we
> have. Also i think anyone should write a paper and describe
> the setup-procedur.. The only think i see on the ftp are those
> RPMS and the basedir.tgz not more.

basedirs.tar.bz2 is a rudimentary tarball of the system base
directories (/usr, /tmp, /boot, /opt, /home, and so on) as
specified by the FHS.  It also has a few rudimentary config
files (like /etc/passwd and /etc/group).

The kernel tarball (linux-2.4.18-1.tar.gz) is the current kernel
I've built everything against.  There's no "default kernel
config" yet, so you'd have to customize that kernel for whatever
system you have.  I'm assuming that's no problem for any of us.
;)

The RPMs provided are enough to build a usable desktop, primarily=20
KDE based, as well as several other optional apps and services. =20
Every one of the RPMs there should have all dependencies=20
satisfied by other RPMs in the download set.  Basically, the=20
RPMs are what I'm using for my own systems here--my desktop has=20
fully up-to-date, Athlon-optimized RPMs, and most of my servers=20
are using older revisions of those RPMs. All the latest=20
revisions appear to be quite stable, but it needs more testing=20
before we can declare it to be fully stable.

The following instructions are a work-in-progress.  They could=20
probably stand to be a bit more user-friendly, but they're a=20
start.  Suggestions are always welcome.

The things you'd have to do to set up a Linux distro with these=20
files:

1) Compile a new kernel on your base system (your SuSE, or=20
slackware, or redhat system) from the 2.4.18-1 tarball and boot=20
the system from that kernel.  Give it all the necessary features=20
you want.

2) Prepare a new partition and mount it as if you were going to=20
install a fresh distro on it.  That includes partitioning,=20
mkfs'ing, untarring basedirs.tar.bz2 within the new partition's=20
root (cd /my/new/system/root; tar -xvyfp=20
/path/to/basedirs.tar.bz2), and setting up default mount points=20
in /etc/fstab.  SGI XFS, reiserfs, ext2, and ext3 are all=20
currently supported.  Currently I'm partial to using XFS as the=20
default filesystem, but it shouldn't matter what you use at this=20
point.

3) cd to /dev in the InceptionOS base directory and run=20
"./MAKEDEV -v generic"

4) Create necessary config files in the new partition,
primarily /etc/passwd, /etc/group, /etc/shadow, /etc/fstab,
/etc/hosts, /etc/resolv.conf, /var/run/utmp, /var/run/btmp,
/var/log/wtmp, and /var/log/lastlog, and /boot/grub/menu.lst
files.  The /etc/passwd and /etc/group file in basedirs.tar.bz2
is slightly outdated; I've attached some example files similar to=20
the passwd and group files I'm currently using.

5) Look through the set of RPMs and figure out which ones you
want to install.

6) Install the RPMs.  This can be done with commands like "rpm=20
-Uvh --root /my/new/system/root".  If you specify all the RPMs=20
on a single rpm -Uvh command line, rpm *should* sort out their=20
dependencies and their necessary install order, and install them=20
all in one shot (assuming all dependencies are satisfied).  You=20
may find it easier to install them one by one.  It's basically=20
like a LinuxFromScratch install, except you're using RPMs=20
instead of compiling from source. ;)

Most (all?) of the RPMs should take care of making necessary=20
/etc/ld.so.conf entries, but none of them will make /etc/passwd=20
entries.  If you're using the /etc/passwd and /etc/group files=20
I've provided, then this should be no problem, as all necessary=20
passwd entries are provided already.  perllocal.pod entries=20
(made by installed perl modules) will also be taken care of=20
automatically.

7) chroot to the IOS system root.  cd to /dev and run ./MAKEDEV=20
-v generic again (this makes sure the owner/group of devices is=20
in sync with the IOS /etc/passwd and /etc/group files).  Note=20
that MAKEDEV may not create all the devices you need; you may=20
need to create extra device inodes for partitions beyond=20
/dev/[hs]d[abcd]8, /dev/{random,urandom}, and others.  The file=20
/usr/src/linux/Documentation/devices.txt should tell you the=20
proper inode numbers to pass to mknod.  It also won't create=20
ALSA device files/directories; you'll need to get a copy of=20
alsa-driver-0.9.0rc<whatever> source, run ./configure, and then=20
run ./snddevices to get those.  The alsa-driver SRPM provides a=20
suitable source tarball.

8) run /usr/sbin/pwconv within your IOS chroot to get an=20
/etc/shadow file.  Then set the root password and any other=20
passwords you feel are necessary.

9) Install a kernel on your new system and set up a boot loader=20
(preferably grub) to load the new system.  It's advisable to use=20
a separate bootdisk for booting the develepment InceptionOS.

It should be noted that if you're using SGI XFS, you *cannot*=20
install the bootloader's boot record on the superblock of an XFS=20
filesystem.  This would not only fail to install, it would chew=20
up an XFS filesystem and force you to run xfs-repair on it=20
(guess who found this out the hard way =3D/).

10) In the SRPMS directory, look for files *cb.src.rpm.  These=20
are "custom build" source RPMs--they need to be rebuilt (via=20
"rpm --rebuild") to match whatever funky custom-compiled kernel=20
you have.  These SRPMs are not guaranteed to have precompiled=20
counterparts; if they do, you should dispense with those=20
precompiled counterparts and "rpm --rebuild" the SRPMs yourself=20
within the IOS chroot.

11) Boot into your new system and start having fun. :)

--=20
Kelledin
"If a server crashes in a server farm and no one pings it, does=20
it still cost four figures to fix?"

[Maxlinux-devel] Overview

[Enrico K. <ph...@h0...>]

Hi,

can anyone give me a full summary about the current 
development-Distribution? What does work e.g what stuff do we have. Also i 
think anyone should write a paper and describe the setup-procedur.. The 
only think i see on the ftp are those RPMS and the basedir.tgz not more. 

Currently i download the i486 RPM s to start development of the 
setup-procedure. Also i setup a mirror or dev-ftp for us (100MBit) i tell 
you more information about this later because i need informations first :)

Enrico

-------------------------------------------------------
H Zero Seven - Unix/Linux Development and Research Team
http://www.h07.org

Re: [Maxlinux-devel] test--success!

[Kelledin <kel...@sk...>]

On Saturday 17 August 2002 05:57 am, Enrico Kern wrote:
> test
> -------------------------------------------------------
> H Zero Seven - Unix/Linux Development and Research Team
> http://www.h07.org
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same
> old cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390
> _______________________________________________
> Maxlinux-devel mailing list
> Max...@li...
> https://lists.sourceforge.net/lists/listinfo/maxlinux-devel

w00t, test successful. :) Perhaps we'll hear from our fearless=20
leader soon...I just notified him about the mailing list a few=20
minutes ago.

--=20
Kelledin
"If a server crashes in a server farm and no one pings it, does=20
it still cost four figures to fix?"

[Maxlinux-devel] test

[Enrico K. <ph...@h0...>]

test
-------------------------------------------------------
H Zero Seven - Unix/Linux Development and Research Team
http://www.h07.org