iccaros

Linux Experts
  • Content Count

    1292
  • Joined

  • Last visited

Posts posted by iccaros

  1. gentoo is a great project.. but do you want this to be a project?? Don't get me wrong.. I use lots of linux distros and my main one is gentoo but in this case fedora 3 may be your best choice fro fast install and now good support for (fedora core 1 was just Red Hat 9) and fedora 2 was very unstable..

    but with 3 I think it would be a fast install..

    now Back to Gentoo.. through portage it has everything .. but you must understand what hardware the laptop has in order to set it up.. a good thing to do if you are going to build gentoo is boot a knoppix CD and run lsmod to get a list of the modules you will need. this way when you build yoru kernel you will know what needs loaded. you can also build from knoppix .. just follow the handbook.

    another trick is to do a lspci to list the hardware the linux kernel detects.. this will also let you see the chipsets the equipment is using and some times that makes it easyer to find drivers..

    good luck on the project..

  2. yes memory is a big problem.. BSD would probaly run better (I have it runing in 16 megs ) but I also have distcc for gcc. distcc woudl allow you to compile on other computers but use that one for linking and config. if you look at the thinstation.sourceforge.org site. they have boot floppies that may help.

    here is how distcc helps..

    I have 3 xboxes running linux.. (totaly leagal as Linux is not pireted software....)

    it took 23 hours to compile mythfrontend on the first one.. I tried distcc. have distcc connectiong to the two other xboxs and one amd2800 xp. it took 4 hours this time to compile it and dvd:rip together.

    the specs for the xbox are 64 megs of ram shared with video.. I have about 32 megs free at any given time. when compiling with out distcc compiling takes all the memory it has.. with distcc it uses about 8 megs..

  3. I have to say while linux can run well on a machine with your specs.. a easy distobution was not made with you in mind. they are made for people with new dells and stuff.

    slackware is easy to install just has no gui.. it has an install program but you move your curser insted of your mouse. it is compiled for 486 systems. as for an x system you would be looking at tiny X (DSL runs that )

    try dsl if that does not work let us knwo And I 'll go through slackware asn see what optinos you need.

  4. ok ipv4 is what you are probaly are using now (4 octects ip address something like 192.168.1.1)

    each number before a period is called an octect as its is made up of 8 binary numbers. like 255 is bainary 11111111 and 128 is 10000000 ... IPV6 is going to add 2 more octects to make the address look like this ... 192.168.1.1.1 this way they will have more address. IPV6 already has the option of IPV4 over IPV6 which will make your current address of 192.168.1.1 look like this on a IPV6 192.168.1.1.0.0 so it will still work.

    for BSD:

    I would like to use dummynet as it isa network flow controller like nistnet is for linux. but nistnet requires an old kernel and at least a 200 mhz machine.. my router boards have 133 mhz 486 level processers ... so I need all the power BSD gives to older equipment.

    what we do with it is test systems as if they are going to be put on slow links like satellite that can have up to 150 ms delay between each hope. With this box we can test how VoIP or video will act over the links.

    here are the boards..

    http://www.soekris.com/net4501.htm

  5. im looking at adding one of the following to my distrobution.. of course I am deciding on a 100% rebuild and I have not decided how I am going to build the base yet (linux from scratch or Gentoo)

    Smart Package manager:

    http://zorked.net/smart/doc/README.html

    this woudl be really cool if some one added pass through portage support. Then if it cought on all Linux versions could use the same package manager (at least the same tool name and look and feel)

    SWARET

    http://sourceforge.net/projects/swaret or http://swaret.sourceforge.net/index.php

    swaret lets you keep your Slackware system up to date. It functions similarly to apt-get, the Debian package manager.

  6. their are a lot of problems with SP2 and the reason companys like SAIC, lockhead martin, BAE, Verizon have put put staments to not upgrade to SP2. Their is a lot of software that is broken with SP2 and some of the fixes break connections to older exchange server. It woudl be nice if everyone could afford to upgrade the hardware and software for these servers.. its just way too cost prohibative to do so this fast..

  7. it was a serious post.. It is a crime to use anothers registration number.. having a CD means nothing..you can get them from MS for $5 with no license.

    their is no way to change your registration number once entered in to XP that number is the base pair at which your system SID and PKI keys are generated. You have to reinstall .. their is a way using the windows tool for creating images of a install to change your sid.. its called newsid and its put out by Microsoft. This along with sysprep keeps your current information (programs installed) but clears out users and make you re-enter your serial number. ( so at this time you can put your number in)

    read that 3 times.. if you used EFS to encrypt folders or files you must..must un encrypt them before you do this.. also any thing in users home folders will be gone when this is done.

    Sysprep is a tool designed for corporate system administrators, OEMs, and others who need to deploy the Windows® XP operating system on multiple computers. After performing the initial setup steps on a single system, you can run Sysprep to prepare the sample computer for cloning.

    To use Sysprep as part of the disk duplication process, the following requirements must be met:

    •

    The master installation and the destination computers must have compatible hardware abstraction layers (HALs). For example, HAL APIC and HAL MPs (multiprocessor systems) are compatible, whereas HAL PIC (Programmable Interrupt Controller) is not compatible with either HAL APIC or HAL MPs.

    •

    The mass–storage controllers (IDE or SCSI) must be identical between the reference and destination computers.

    •

    Plug and Play devices such as modems, sound cards, network cards, video cards, and so on, do not have to be the same. However, any device drivers not included in Drivers.cab should be included in the master installation before you run Sysprep. Alternatively, make sure the uninstalled drivers are available on the destination computer at first run, so Plug and Play can detect and install the drivers.

    •

    Third–party software or disk–duplicating hardware devices are required. These products create binary images of a computer’s hard disk, and they either duplicate the image to another hard disk or store the image in a file on a separate disk.

    •

    The size of the destination computer’s hard disk must be at least the same size as the hard disk of the master installation. If the destination computer has a larger hard disk, the difference is not included in the primary partition. However, you can use the ExtendOemPartition entry in the Sysprep.inf file to extend the primary partition if it was formatted to use the NTFS file system.

    Note If the reference and destination computers have different BIOS versions, you should test the process first to ensure success. When using Sysprep for Disk Duplication, Sysprep modifies the local computer Security ID (SID) so that it is unique to each computer.

    How to prepare a master installation for cloning

    1.

    Install Windows XP on a master computer. As a best practice, Microsoft recommends that Windows XP be installed from a distribution folder by using an answer file to help ensure consistency in configuring the master installation, so that iterative builds can be created and tested more readily. See Unattend.txt for information about automating Windows Setup using an answer file.

    2.

    Log on to the computer as an administrator.

    3.

    (Optional) Install and customize applications, such as Microsoft Office, Internet Explorer favorite items, and so on.

    4.

    (Optional) Install any device drivers not included in Drivers.cab and not installed by the answer file.

    5.

    (Optional) Run audit tests.

    6.

    (Optional) If you want, create a Sysprep.inf file manually or with the aid of Setup Manager. This file is used to further customize each computer for the user and helps to set the amount of information for which the user will be prompted during Mini–Setup.

    7.

    Run Sysprep.exe. Make sure that both the Sysprep.exe and Setupcl.exe files exist together in the %systemdrive%\Sysprep folder on the local hard disk. When used, the Sysprep.inf also needs to be in the same folder or on a floppy disk that is inserted when the Windows boot menu appears.

    Important If Setupcl.exe is not in the same directory as Sysprep.exe, Sysprep will not work.

    8.

    If the computer is ACPI–compliant, the computer will shut down by itself. If not, a dialog box appears stating that it is safe to shut down the computer.

    9.

    Take out the system drive and follow the steps for duplicating the system on other computers. You must have special equipment or software for duplicating hard disks.

    After a duplicated hard disk is inserted into a computer, when the user turns the computer on, the following occurs:

    1.

    Plug and Play detection occurs – this takes approximately three minutes.

    2.

    Mini–Setup prompts users to:

    •

    Accept the EULA.

    •

    Specify their name and organization.

    •

    Join a domain or a workgroup.

    •

    Specify regional options information.

    •

    Specify TAPI information.

    •

    Specify the networking protocols and services to install.

    Note If a Sysprep.inf file was used when running Sysprep.exe, only the dialog boxes omitted in the .inf file are presented to the user. If display settings are omitted, the default settings are used instead.

    3.

    The local Sysprep folder containing Sysprep.exe and Sysprep.inf in %systemdrive% is deleted.

    4.

    The computer restarts and a logon prompt displays.

    Top of page

  8. http://www.denverpost.com/Stories/0,1413,3...2735094,00.html

    2 points the story touches on but misses in my openion...

    1) the Linux and Mac OSX boxes needed no updates to be secure..

    2) if windows is taken over in 18 then you do not even have time to install SP2 for a new system. before being taken over..

    I do think MS is doing better in the secuering the OS but this is only becase of presser by compatition from linux/bsa/and Mac OSX

  9. its loads all native (ones that come with the cd) from the initrd.ing file and the only modules that would reside on root are ones you install which would not be upgraded if I had a kernel upgrade package. so you would have to upgrade them. The same things happens with Fedora.. say you go to ntfs on linux site and downlioad the RPM to install support. your reboot and you have ntfs support. you upgrade your kernel through up2date or yum your ntfs woudl stop working.. (this is diffrent since ntfs support is not part of the kernel) you would have to go get the rpm made for your new kernel.

    since the fedora team or most distributers don't care if you add things .. they so don't care if their updates break what you added.

  10. if you are building a distro you have a boot device but you have no ideal where the user is going to put their root partition. you could write a scripts or part of the install program that changes the boot loader to point to hte installed root. but why .. this make it more simple..

    IT really works well with thin clients where you have a kernel and a initrd.ing that is your root partition. this way you store these two files on a newtwork share and use DHCP to point to them .. and all systems can boot from one kernel and one initrd.ing. to upgrade you just replace the two files. and all of your clients are upgraded at the same time.

    as for you modules .. when you use a initrd.ing your modules are not updated on the root partition or even their (I have ot check this one)

    I know when Red Hat does a Kernel upgrade or you add something to the kernel you only upgrade the kernel and the initrd.ing.

    I see no advantage to a normal desktop user using gentoo. I know genkernel uses it.. but I have never gotten a genkernel to boot.

  11. their are two ways of looking at it.

    why would a distrabution like Red Hat use it?

    why would you use it.

    the initrd.ing is stored at the same place your kernel is. it comtains al your modules.. and normaly you make everything a moduel if you use it. the advantage is you know where it is. you can load teh modules with out knowing where root is. great for live cd or install cd, or a PXE boot for thin clients.

    so Red Hat and gang (including me on my distro) use it because its a known location so the system can boot. the last thing that happens in a boot is the unmounting of initrd.ing and change rooting to your drive.

    if they did not use it root would have to be hda1 or soemthing on all computers.

    also its makes upgrade simple.. compile a kernel create a initrd.ing file and ditribute both together. if they did not they would have to write all the new modules for every kernel upgrade to the root partation. this leaves room for error and is slower.

    now you.. their is no advantage for you to use it. you know where root is and can write that to your grub.conf or lilo.conf file..

    you put root in your fstab and your root is not changing because that install is not going from computer to computer.

    did I explain it well?

  12. "is this the same version I tried? Did you fully remove the harddrive installer, or just not reccomend people use it?"

    its almost the same .. no crossover office or MS office like the Proof of consecpt.. added some software. I hope I fixed some memory issues.

    The harddrive script is their and has been improved but I still don't like it.. I would sugesst people not install it on a system with windows or anything else for that matter. I don't trust my skills yet to say I know its will not mess up anything..

    so why is it still their..

    Well say you have vmware or a free system.. you would like to build your own cd with your software.. remove some ..add some..

    install the cd..

    download my scripts (the original slax scripts will not work with my cd)

    copy the scripts to /tmp

    type tar -zxvf iccaros-live-linux-scripts.tar.gz

    cd to teh new folder

    type ./runme.sh

    this will create a licecd.iso in your /tmp folder..

    now your on yoru way to create any linux cd you would like

    I will have a full write up inhte next few weeks.. I have finals at school and I still work so I will do my best to meet that tiem frame.