DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi: I have just installed Debian Etch (that is, Debian version 4). When the system finishes booting, I find myself in the GUI. From what file is the GUI launched? I'd like to set things such that it is me who lauches the GUI and not the system after booting. Thanks
I already had set the default runlevel to 3, then to 4 and 5, but in all of them the GUI was forced. Then I saw, in the boot messages on the console, the service is named gdm. So I went to /etc/rc2.d and following instructions in that directory's README, I renamed S21gdm to K79gdm (100 - 21 = 79). Now I am booted in the virtual terminal #1, as I wanted.
@Randicus: it's the only one I have. Anyways, theres a lot of things I must learn, one of them how the init scripts work and, for that, the simpler the better.
This will make it last about as long as Debian 7 unless that gets this support too.
If you are worried about some antique hardware that you may using for this I am on a Dell Latitude laptop right now, running Debian 7 (Wheezy) just fine. This box has no wifi capability but does have both DSL and Dial up connection built in. If it runs on here it will probably run on what you have.
You may, if you have a good connection want to try a Squeeze or Wheezy netinstall image. This gives you just enough system to boot to the tty prompt and finish your install, as you want to, from there.
I generally end up with a tty prompt login at the end of doing that because I forget to install any DM. Sometimes I don't bother as they all have irritating features.
Distribution: Debian Wheezy, Jessie, Sid/Experimental, playing with LFS.
Posts: 2,900
Rep:
Quote:
Originally Posted by stf92
Hi: I have just installed Debian Etch (that is, Debian version 4).
If you are just learning Linux my advice would be to get Wheezy and install it. There would be very few, if any, good reasons to use an unsupported version while accessing the internet.
Quote:
Originally Posted by stf92
When the system finishes booting, I find myself in the GUI. From what file is the GUI launched? I'd like to set things such that it is me who lauches the GUI and not the system after booting. Thanks
Widget pretty well has it covered, just uninstall the login manager and you will get the prompt as soon as the machine is ready to operate afer you login at the cli prompt. If you want a gui after this just type
Quote:
startx
to start the gui.
Having said that, you should really consider downloading wheezy, or even squeeze as widget pointed out.
May I ask why you want to use such an old release? Enquiring minds want to know.
One of the reasons: I wanted to make a simple audio recording, under slackware 14,last version of the slackware disto, by way of
Code:
amixer -c 0 sset Line 0, 100%,100% mute capt
arecord -f CD -D hwplug:0,0 > someaudiofile.wav
and it didn't work. When this had always worked in previous versions of slackware. Now, I repeated the test under etch, with a positive result. So, if I install a newer version of Debian, who guatanties me the procedure has not increased in complexity. Why to have to learn everything anew when what I already knew suffices to do the job? As another example, when I first ran my newly installed slackware 14.0 linux OS, in the middle of the booting process the fonts changed to something that had to be read with a looking glass. If they had wanted to make the letters smaller they wouldn't be able to do it. So I had to spend several days to find out how I could use the system with the normal size fonts! It is likely that a thing like this won't bother you, because sure enough you work in a terminal in the GUI. Well, I do not usually work in the GUI, and cant fix things by just pressing a button. These are just two examples among tens and tens.
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628
Rep:
Quote:
Originally Posted by stf92
One of the reasons: I wanted to make a simple audio recording, under slackware 14,last version of the slackware disto, by way of
Code:
amixer -c 0 sset Line 0, 100%,100% mute capt
arecord -f CD -D hwplug:0,0 > someaudiofile.wav
and it didn't work. When this had always worked in previous versions of slackware. Now, I repeated the test under etch, with a positive result. So, if I install a newer version of Debian, who guatanties me the procedure has not increased in complexity. Why to have to learn everything anew when what I already knew suffices to do the job? As another example, when I first ran my newly installed slackware 14.0 linux OS, in the middle of the booting process the fonts changed to something that had to be read with a looking glass. If they had wanted to make the letters smaller they wouldn't be able to do it. So I had to spend several days to find out how I could use the system with the normal size fonts! It is likely that a thing like this won't bother you, because sure enough you work in a terminal in the GUI. Well, I do not usually work in the GUI, and cant fix things by just pressing a button. These are just two examples among tens and tens.
All of that is reasonable.
The only problem is that Etch is not supported and is therefore not secure. This is our concern.
It is, in fact, your box. If you want to run Etch that is your choice.
It is, however, not responcible for us not to question that choice.
Seems like that command should work to me too. That could be checked in just about any distro before installing by simply running the Live Session from a Live CD/DVD and trying the command out.
This would boot you to the gui DE. I have never tried to boot a Live session to the tty. Seems like that should be able to be done. I may have to play with that someday.
Well thank you, widget. I have made up my mind to install etch revision 0 (4.0_r0) just to familiarize myselt with debian. I have already found many things I like in it.
The thing is that I only have CD 1, out of a set of 21. Most probably only a few more will do. First, I'd like to do the installation in the way I am used to: from CDs or DVDs, which means to get the DVD images for 4.0_r0. But this seems to be more difficult than I had forseen. In http://cdimage.debian.org/mirror/cdi...e/4.0_r0/i386/ I am presented with this directory:
You must keep in mind that while these antique images are hosted on a Debian server that the project is actually done by individuals on their own. They may have lost some of the package cd/dvd images to time.
simply because it is newer and the archive may be more complete. As it is also the latest of the Debian 4 series it will present you with packages that have all the bug fixes for the life of that version. Up to the day the images were released.
As for how to download any of them you will have to read that first link I posted. Scanning that looks like it explains the process pretty thoroughly.
I looked for jigdo in the Wheezy repo using the Synaptic installed on here and found the package jigdo-file with this description;
Quote:
Download Debian CD images from any Debian mirror
Using the jigdo-lite script contained in this package, you can use
your nearest "regular" Debian mirror to download Debian CD images,
instead of having to use one of the few, slow, overloaded mirrors
that offer the images as direct HTTP or FTP downloads. See
<http://www.debian.org/CD/jigdo-cd/> for details.
Jigsaw Download, or short jigdo, is a scheme developed primarily to
make it easy to distribute huge filesystem images (e.g. CD (ISO9660)
or DVD (UDF) images) over the internet, but it could also be used for
other data which is awkward to handle due to its size, like
audio/video files or large software packages.
jigdo tries to ensure that the large file is downloaded in small
parts which can be stored on different servers. People who want to
download the image do so by telling the jigdo download tool to
process one ".jigdo" file; using it, jigdo downloads the parts and
reassembles the image. jigdo-file is used to prepare the files for
download.
Seeing how this may not be available for you there are instructions on the download page for getting jigdo-lite from the homepage.
which described as a mini-how too. Doesn't look real mini to me but looks to have a lot of good information.
I hope you keep us up to date on this. I have wondered about jigdo but my usual install is from netinstall images that I just do a straight download of (for Debian 7 32bit that was 277 MB).
Just put the number 3 at the end of the kernel line like in my
/boot/grub/menu.lst since Etch uses legacy grub like I do.
You should have a /boot/grub/menu.lst also.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.