[ leaf-Bering uClibc-1507965 ] script to install to a hard disk

[SourceForge.net]

Bering uClibc item #1507965, was opened at 2006-06-18 12:06
Message generated for change (Comment added) made by ken_yap
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=676165&aid=1507965&group_id=13751

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Ken Yap (ken_yap)
Assigned to: Nobody/Anonymous (nobody)
Summary: script to install to a hard disk

Initial Comment:
I found that after I wrote these scripts, I don't
currently have the time to play with Bering. I would
like to try out the IPv6 modules, which is why I wrote
this.

So I'm uploading the scripts and documentation I
developed for whomever is interested.

----------------------------------------------------------------------

>Comment By: Ken Yap (ken_yap)
Date: 2006-06-20 11:46

Message:
Logged In: YES
user_id=23461

Ok, I've uploaded a new README and INSTALL where everything
refers to Bering-uClibc.

As for package maintenance and configuration backup, these
are issues that would have to be addressed. What I wrote is
a HD installer, not a package manager or backup manager. I
wrote it for one user, me. I don't know when/if I'll get
back to hacking on Bering in the near future. It turned out
that my broadband connection really needs a Pentium to keep
up with the data rate so I installed IPCop.

So as I wrote, the stuff here is as-is and might be useful
for somebody wanting to experiment with Bering on a HD
without having to make a floppy or a flash disk whenever
some package needs to be added.

----------------------------------------------------------------------

Comment By: KP Kirchdörfer (kapeka)
Date: 2006-06-20 06:03

Message:
Logged In: YES
user_id=204664

A few questions...

You don't "backup" the packages - in fact there no packages
any longer?

What about new packages and updated packages? How can a
user handle this?

What about filesystem integrity checks?

I'd also like you to review the docs and make shure that
you write Bering-uClibc if you mean Bering-uClibc :)
- Bering is a different and outdated version.

TIA
kp

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=676165&aid=1507965&group_id=13751


_______________________________________________
leaf-auto mailing list
leaf-auto@...
https://lists.sourceforge.net/lists/listinfo/leaf-auto