Then there's the Trusted User Repositories (tur.berlios.de). Read everyithg on there to get an idea of what they're about.
Then there's incoming. Incoming is just an ftp directory that people can upload submitted packages (in a certain format) for acceptance into the TURs and, later, into extra.
]]>1 other thing thou im a little confused about, how do i get access to or use these dev repo's? im alittle confused by this *theres bits of software in each repo id like to use* anyone?pretty please?
]]>anyway thanks for all your help
and thank you
]]>Yes you have to set up fstab & some config files but hey no problem 8)
Gentoo install with Gnome took me some 12 hours ouch.... :-(
Arch install & set up a lot less of a headache once X starts away you go....
Welcome to Arch .....
Mr Green
]]>also ive seen references to logjam on the board but it doesnt seem to be there anymore, has it been removed?
all i need to do now is setup sound yay
]]>*not comparing to gentoo here* im using it on my gentoo box on my desktop and it works fine, udev that is, i think ill leave it for abit thou and yea it is a replacement of devfsd
that is good but ymmv compared to another person. my point is that i would not expect it too soon because they have to make sure as well as they can that switching to udev will allow all users to still be functional.
in what way easier? i've always had multiple kernels to boot into you know different patch sets etc, not being boasting here, just wondered what differences it would make?
well for example if you have a /usr/src/linux that would be altered when a new kernel upgrade comes down the pipe. it has nothing to do with running multilple kernels it has everything to do with keeping /usr/src/ and other such thing in the condition you want them not how some package wants them.
i hope this makes sense it is management thing.
also ive got another question does arch use rc-update, ie adding runtime stuff such as xdm etc ?
no that is a gentoo thing i believe. rc files are rarely changed and adding some runtime daemon to one of the scripts is all done manually normally.
]]>in what way easier? i've always had multiple kernels to boot into you know different patch sets etc, not being boasting here, just wondered what differences it would make?
also ive got another question does arch use rc-update, ie adding runtime stuff such as xdm etc ?
]]>i wouldn't expect it for a bit
as for udev and devfs coexisting ..... i would expect a system to blowup quickly. as far as i know udev is/will be a replacement for devfs.
EDIT:
BTW once you have your kernel installed and stable i suggest removing any stock kernel you have installed. it will make things easier.
also another thing i've remembered, where is arch with udev? i use it currently with my desktop and it works very well *ive had no problems so far* but with arch would it cause major problems with devfsd?
wow everyone is so nice here
]]>As Mr Green said you can do it by using the arch system.
Just few suggestion
Just go to /usr/var/abs and run abs
after the command has done you will see many dirs one of this should be kernels.
Go there and you find kernel26, enter it
here you find PKGBUILD and config files.
If you do a more of the PKGBUILD you will see that everithing is done like a script. config is th classical config file for the kernel and is copied in the appropiate dir before compiling.
Once you start the makepkg command at first it verify build dep then it start to download the kernel.
After the download it will unpack in src (under the current dir) the sources then it start to compile.
Now you can press ctrl-c to interrupt the process.
Go to kernel dir under src and chage configuration as always, commandline, gui interface or the way you prefer.
Once you are happy with it copy the newly created config file and overwrite the one with the package, delete src dir and run makepkg again. Do not worry the tar.gz with the sorce is in the cache, no need to download it again.
At this point wait untill the end and you will find a file named kernel26-2.6.x.pkg.tar.gz if everithing went fine.
then run
pacman -Ac kernel26-2.6.x.pkg.tar.gz
This will install the new kernel, off-course you still have to configure your grub/lilo.
Test the kernel and see if you are satisfied with it, if not start again and change configuration.
Why should I go trou makepkg and pacman when I can do it directly?
Yes you can compile it directly. the advantage to go by pacman is that it keep track of the file in the package, so if you change idea and decide to compile in something that before was a moduel it will be removed from the system by pacman.
To get poweroff on the laptop and in general on any pc add this to you lilo/grub configuration as kernel parameter.
apm=on apm=power-off
If you have an ide cdwriter add also
hdc=ide-scsi
Last thing to get ful screen during text bootup add
vga=0x305
or you can just install the non arch way. using abs though will allow you to make a nice neat little package out of your kernel that is easier to remove after.
either way you do it i suggest that you do leave the full source (linux-2.6.2) directory in /usr/src/ instead of the default arch one. .... well if you have a nvidia card that is.
]]>There is a config file in kernel26 dir....under abs....once abs is run as root you can take a look at it in the kernel26 dir.....
Have fun...
Mr Green