I need some opinions, from the more experienced people.
I want my antix to have icewm, and no fluxbox.
Would it be better to install core, and add stuff, or install full, and remove fluxbox?
Is it really worth thinking about?? or am I just being awkward?
-
Posts: 765
- Joined: 27 Dec 2011
-
Posts: 112
- Joined: 18 Apr 2009
#2
Why not just remove fluxbox from the options in the login window? Soon you'll forget that your system even has the fluxbox libraries on it!
-
Posts: 4,164
- Joined: 20 Feb 2009
#3
I did the opposite and kept fluxbox and ditched icewm in full iso 8.5 install. I just removed Icewm using synaptic package manager. Deleted ~/.icewm folder. Edited my ~/.xinitrc to start fluxbox only. That is how I did it.
Actually. Icewm and Fluxbox do not take up a lot of installed space to make a difference in uninstalling either one so chrishall57 suggestion is actually a very good one also. That way you have a fallback Window manager in case you need it. Choice is always good. Especially when the choice is weightless.
Actually. Icewm and Fluxbox do not take up a lot of installed space to make a difference in uninstalling either one so chrishall57 suggestion is actually a very good one also. That way you have a fallback Window manager in case you need it. Choice is always good. Especially when the choice is weightless.
To me. You are being awkward, Just leave things be, if Icewm is default login in slim anyways. Don't remove the fluxbox options. You may need them down the road. Not enough bloat there to make any difference.Is it really worth thinking about?? or am I just being awkward?
-
Posts: 765
- Joined: 27 Dec 2011
#4
I guess you are right, it is not big enough to worry about.
Thanks! both of you!
Thanks! both of you!
-
Posts: 609
- Joined: 02 Jun 2008
#5
if you want to save some space on antix, here are some tips post18498.html#p18498
-
Posts: 765
- Joined: 27 Dec 2011
#6
Yes! Thanks!
It is not really that I have to save space, but I just don't like stuff I won't use, cluttering up my system, and"brain".
I have no idea how many times I have made some settings, and find out I made them in fluxbox, which I don't use.
Yep, I might have to read the little letters and stuff, when I mess with things, or get some glasses, maybe.
There are some things in your list of things to do that helps, without limiting my options later... Great!
Now, I have a new issue to figure out...
Kristian- gone searching...
It is not really that I have to save space, but I just don't like stuff I won't use, cluttering up my system, and"brain".
I have no idea how many times I have made some settings, and find out I made them in fluxbox, which I don't use.
Yep, I might have to read the little letters and stuff, when I mess with things, or get some glasses, maybe.
There are some things in your list of things to do that helps, without limiting my options later... Great!
Now, I have a new issue to figure out...
Kristian- gone searching...
-
Posts: 765
- Joined: 27 Dec 2011
#7
heh, well....
I thought I would take a new look at fluxbox, so I put base on a stick...
Uuh, And now I can't connect to the internet, I tried wireless, and wired.
I tried ceni, and...rutilt.
Is there any way I can put wicd on the stick? My machine seems to like wicd, but have never had problems connecting with ceni either.
Any other ideas?
Edit
Ok, so now the wireless works...for some reason... __{{emoticon}}__ __{{emoticon}}__
I thought I would take a new look at fluxbox, so I put base on a stick...
Uuh, And now I can't connect to the internet, I tried wireless, and wired.
I tried ceni, and...rutilt.
Is there any way I can put wicd on the stick? My machine seems to like wicd, but have never had problems connecting with ceni either.
Any other ideas?
Edit
Ok, so now the wireless works...for some reason... __{{emoticon}}__ __{{emoticon}}__
-
Posts: 765
- Joined: 27 Dec 2011
#8
Yep, I have messed something up again, but the thing still works.
For some reason, while booting, I get a: dhcpdiscover eth0.....blablablah.
A few seconds, and it tries again.After a few of those, it goes to try: dchpdiscover wlan0...blablah...
What makes that happen?
It works just fine, but it is annoying to have +20 seconds added to the boot time __{{emoticon}}__
I use wicd to connect, btw.
And an other thing... I installed the 3.2.2 kernel, and it works fine, as far as I know.
Now, how do I set grub to use that kernel as default?
Here you see my menu.lst:
Now, what should I move where? __{{emoticon}}__
For some reason, while booting, I get a: dhcpdiscover eth0.....blablablah.
A few seconds, and it tries again.After a few of those, it goes to try: dchpdiscover wlan0...blablah...
What makes that happen?
It works just fine, but it is annoying to have +20 seconds added to the boot time __{{emoticon}}__
I use wicd to connect, btw.
And an other thing... I installed the 3.2.2 kernel, and it works fine, as far as I know.
Now, how do I set grub to use that kernel as default?
Here you see my menu.lst:
Code: Select all
timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1
gfxmenu /boot/grub/message
title antiX at sda1, kernel 2.6.36-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.36-1-mepis-smp root=/dev/sda1 nomce quiet nosplash nouveau.modeset=0 vga=normal
initrd /boot/initrd.img-2.6.36-1-mepis-smp
boot
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=8085f4e1-5f09-4bc4-8035-1186544007dd ro
# kopt_2_6=root=UUID=8085f4e1-5f09-4bc4-8035-1186544007dd ro nosplash quiet nouveau.modeset=0
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(init-3) 3
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Debian GNU/Linux, kernel 3.2.2-antix.2-486-smp
root (hd0,0)
kernel /boot/vmlinuz-3.2.2-antix.2-486-smp root=UUID=8085f4e1-5f09-4bc4-8035-1186544007dd ro
initrd /boot/initrd.img-3.2.2-antix.2-486-smp
title Debian GNU/Linux, kernel 3.2.2-antix.2-486-smp (init-3)
root (hd0,0)
kernel /boot/vmlinuz-3.2.2-antix.2-486-smp root=UUID=8085f4e1-5f09-4bc4-8035-1186544007dd ro 3
initrd /boot/initrd.img-3.2.2-antix.2-486-smp
title Debian GNU/Linux, kernel 2.6.36-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.36-1-mepis-smp root=UUID=8085f4e1-5f09-4bc4-8035-1186544007dd ro nosplash quiet nouveau.modeset=0
initrd /boot/initrd.img-2.6.36-1-mepis-smp
title Debian GNU/Linux, kernel 2.6.36-1-mepis-smp (init-3)
root (hd0,0)
kernel /boot/vmlinuz-2.6.36-1-mepis-smp root=UUID=8085f4e1-5f09-4bc4-8035-1186544007dd ro nosplash quiet nouveau.modeset=0 3
initrd /boot/initrd.img-2.6.36-1-mepis-smp
title Debian GNU/Linux, kernel memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
### END DEBIAN AUTOMAGIC KERNELS LIST
-
Posts: 279
- Joined: 17 Oct 2009
#9
delete these lines:
In your menu.lst, right after the entry:rust collector wrote: Now, what should I move where? __{{emoticon}}__
Code: Select all
gfxmenu /boot/grub/message
Code: Select all
title antiX at sda1, kernel 2.6.36-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.36-1-mepis-smp root=/dev/sda1 nomce quiet nosplash nouveau.modeset=0 vga=normal
initrd /boot/initrd.img-2.6.36-1-mepis-smp
boot
-
Posts: 765
- Joined: 27 Dec 2011
#10
Thanks!
It works great now!
I am thinking that when I have that removed, it will boot the first of the kernels listed after:
## ## End Default Options ##
And
### END DEBIAN AUTOMAGIC KERNELS LIST
Is that right???
It works great now!
I am thinking that when I have that removed, it will boot the first of the kernels listed after:
## ## End Default Options ##
And
### END DEBIAN AUTOMAGIC KERNELS LIST
Is that right???
-
Posts: 279
- Joined: 17 Oct 2009
#11
You can remove unused kernels by running the smxi script and when you do it will remove the entiries for that kernel in your menu.lst
That is correct. You can cut & paste the entries around to suit your preference.rust collector wrote: I am thinking that when I have that removed, it will boot the first of the kernels listed after:
## ## End Default Options ##
You can remove unused kernels by running the smxi script and when you do it will remove the entiries for that kernel in your menu.lst
-
Posts: 765
- Joined: 27 Dec 2011
#12
Aah! ok, Thanks again!
-
Posts: 765
- Joined: 27 Dec 2011
#13
So, I think I have the dhcpdiscover thing fixed, for now...
I went to /etc/network/interfaces and commented out 2 lines:
auto eth0
iface eth0 inet dhcp
It has been ok since that, now I just have to find out what else I broke doing that.
I don't use wired networks anyway, so...if it don't work, I won't know.
I went to /etc/network/interfaces and commented out 2 lines:
auto eth0
iface eth0 inet dhcp
It has been ok since that, now I just have to find out what else I broke doing that.
I don't use wired networks anyway, so...if it don't work, I won't know.
-
Posts: 765
- Joined: 27 Dec 2011
#14
Is there any way to make the sound louder?
I have the mixer set to max...
Is there anything that can"pre-boost" the volume before the mixer (or after, I guess)
When I used vlc, it was ok, but I think it needs a bit more now, using moc,or lxmusic (xmms2)
I have the mixer set to max...
Is there anything that can"pre-boost" the volume before the mixer (or after, I guess)
When I used vlc, it was ok, but I think it needs a bit more now, using moc,or lxmusic (xmms2)
-
Posts: 112
- Joined: 18 Apr 2009
#15
Open the mixer, make sure PCI and Master are set to max. Should give you the max volume.