LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-16-2009, 05:55 PM   #481
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Original Poster
Rep: Reputation: 70

Quote:
Originally Posted by Woodsman View Post
Thanks for noticing.

I vaguely recall once upon a time submitting the idea to Pat. I could try again.
Sounds great

Quote:
Originally Posted by Woodsman View Post
Thanks for noticing.
The Zenwalk people adopted the idea after I wrote about my experiences with release 4.4.1.

The way I have the scripts colorized is easily disabled by editing one line in a config file. Some people could care less about colorized scripts and disabling is necessary. Some additional work is needed, however. Currently my color scheme works great with a black background only. Some people prefer white or transparent xterms. The config file should contain alternate color schemes for such people. I probably could add the Zenwalk color scheme for transparent xterms, which is what the Zenwalk folks use.
VectorLinux also has their own version which is similar. I do like their use of the "echoc" command which takes a second arg for the color of the text to display. That function could use the switch to determine if colors are used and if so, which color configuration.
 
Old 03-17-2009, 08:10 AM   #482
AGer
Member
 
Registered: Oct 2007
Distribution: Slackware current
Posts: 136
Blog Entries: 22

Rep: Reputation: 19
In search for common needs

Quote:
Originally Posted by mRgOBLIN View Post
Thanks to AlienBob it's already there but you just have to feed some info at the boot prompt.

........

Again it's mostly there but you just have to either edit the initrd yourself or be there to give the parameters... we can't do this as everyones needs are different.
Yes, it is mostly there. Manually entering boot parameters is too complicated and it is also necessary to manually install the key to have a secure shell from the very start, so it is either modifying initrd, or Slax, or whatever. For me and for now it is sufficient to know that this is not hard to do.

The idea was to allow for completely unattended remotely controlled installation out of the box, that is, without burning new installation media, just adding some additional one.

When originally posting, I thought no distro does that. Now, after trying to formulate the idea better, I see that Slax does exactly that. Email somebody the changes file and the link to download the standard Slax - and you are all set to create a remotely managed server, Slackware or not.

Thus, what I wanted was actually the Slax "changes file" feature implemented with the Slackware installer. This would help everyone who wants to modify initrd in any way (just not having to burn any media is good) but with Slax already existing I agree this is not worth the effort.

BTW, thanks for comments!
 
Old 03-17-2009, 02:00 PM   #483
mbvo
Member
 
Registered: May 2006
Location: the land of confusion
Distribution: slackware-current
Posts: 220

Rep: Reputation: 31
I don't know if theres a reason for grub legacy to still be in /extra when grub2 is available, also i'd love to see slackware move from lilo to grub. I use grub because of the command line option that lilo doesnt offer and because it can boot kernels from any partition not just the root partition.

anyway if you feel like checking it out my grub2 slackbuild is at http://landofconfusion.comze.com/grub-1.96-i486-1.tgz and the source is at http://landofconfusion.comze.com/grub2.tar.gz

i couldnt get grubconfig in the package because it doesnt seem to like the fact that there's no /usr/sbin/grub. And I'm not sure if its just my computer or if the package could use recompiling somehow but grub-install took 10-15 min and the update-grub took 30 min.
 
Old 03-19-2009, 02:56 AM   #484
sahko
Senior Member
 
Registered: Sep 2008
Distribution: Slackware
Posts: 1,041

Rep: Reputation: Disabled
The new linux logo http://torvalds-family.blogspot.com/.../new-logo.html when 2.6.29 hits current
 
Old 03-19-2009, 03:16 AM   #485
dora
Member
 
Registered: Jan 2004
Location: Switzerland
Distribution: Linux Mint 11, Knoppix 6.7
Posts: 141

Rep: Reputation: 15
Quote:
Originally Posted by sahko View Post
The new linux logo http://torvalds-family.blogspot.com/.../new-logo.html when 2.6.29 hits current
Yeekkk!!! what an ugly little thing...
Linus always seems to have a great time each year in down underland. What next?
 
Old 03-19-2009, 05:21 AM   #486
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,049
Blog Entries: 52

Rep: Reputation: Disabled
Here's the real thing, without the penguin beak:

http://en.wikipedia.org/wiki/Tasmanian_Devil

Cute little critter, ain't it?
 
Old 03-19-2009, 10:57 PM   #487
salemboot
Member
 
Registered: Mar 2007
Location: America
Distribution: Linux
Posts: 159

Rep: Reputation: 36
Master Build Script
That topic got left too soon. That is a great idea.

You definitely need to document the dependencies though. Somebody is doing something to that nature now.
There has to be a build plan written down somewhere. Perhaps they even have a script.
Maybe the inner circle has a copy of this.

I know I have notes written down for building glibc, gcc, and Xorg.

Possible reasons for a master build script:
1. Automate a recompile for your architecture (Xeon / i686 / 64 bit)
2. Package up your build of the system for your home network.

List could grow.


Also,

Where do you file bug reports for Slackware? Info@Slackware.com ?

That's a bit like telling somebody to leave a message on your answering machine.

So another wish for Slackware 13 is to have a bug report page, similar to Debian's / Fedora for example.

This would allow for the creation of a proper procedure.

Task could be assigned, you'd have more visibility of the problem.

* Bug Kde KSnapshot Segfault
* Status --//-- Assigned to AlienBob
* State --//-- InProc
--------------
Fowarded to KDE Dev for review


L 8 R
 
Old 03-20-2009, 12:22 AM   #488
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
Originally Posted by salemboot View Post

Also,

Where do you file bug reports for Slackware? Info@Slackware.com ?

That's a bit like telling somebody to leave a message on your answering machine.

So another wish for Slackware 13 is to have a bug report page, similar to Debian's / Fedora for example.

This would allow for the creation of a proper procedure.

Task could be assigned, you'd have more visibility of the problem.

* Bug Kde KSnapshot Segfault
* Status --//-- Assigned to AlienBob
* State --//-- InProc
--------------
Fowarded to KDE Dev for review


L 8 R
If you have a genuine reproducible bug and are running the stock kernel with all stock slackware packages then feel free to email Pat directly.

You are in the very best place to submit bugs right here on LQ.

The slackware team all keep a very close eye on the forums here and deal with issues as they arise.

Although each person does tend to concentrate on certain areas, we do not assign tasks to individuals but would rather attack each problem as a team.

We think the current procedure is proper thanks
 
Old 03-20-2009, 01:43 AM   #489
sahko
Senior Member
 
Registered: Sep 2008
Distribution: Slackware
Posts: 1,041

Rep: Reputation: Disabled
Quote:
Originally Posted by salemboot View Post
Master Build Script
That topic got left too soon. That is a great idea.

You definitely need to document the dependencies though. Somebody is doing something to that nature now.
There has to be a build plan written down somewhere. Perhaps they even have a script.
Maybe the inner circle has a copy of this.

I know I have notes written down for building glibc, gcc, and Xorg.

Possible reasons for a master build script:
1. Automate a recompile for your architecture (Xeon / i686 / 64 bit)
2. Package up your build of the system for your home network.

List could grow.
The build script is a very bad idea, in maintainance terms.
An example is the latest GCC 4.3 update in current.
I bet many packages in Slackware dont build with that version of GCC.
Providing patches just for that is a waste of time.
Slackware is a 100% binary distribution.

Noone is preventing you from doing all that yourself.
Documenting dependencies doesnt even require scripting skills.
I say go for it. If you lead the way maybe others who feel the same as you will follow.

Quote:
Also,

Where do you file bug reports for Slackware? Info@Slackware.com ?

That's a bit like telling somebody to leave a message on your answering machine.

So another wish for Slackware 13 is to have a bug report page, similar to Debian's / Fedora for example.

This would allow for the creation of a proper procedure.

Task could be assigned, you'd have more visibility of the problem.

* Bug Kde KSnapshot Segfault
* Status --//-- Assigned to AlienBob
* State --//-- InProc
--------------
Fowarded to KDE Dev for review


L 8 R
I used to feel the same about this too until some point.
I had even asked Alien Bob in the IRC once about it. This involves a more open development. Not gonna happen any time soon.
FWIW with the size of Slackware i no longer think there is a need for a bug tracker. As others have pointed out, LQ and info@slackware.com is adecuate.
Your example with KDE sucks, because KDE has a bug tracker. Whats the use in letting Alien Bob know about it? Its a waste of his time..
Hes just a Slackware packager, not a KDE developer.

Last edited by sahko; 03-20-2009 at 01:48 AM.
 
Old 03-20-2009, 09:33 AM   #490
arfon
Member
 
Registered: Apr 2004
Location: Texas - Dang, it's hot!
Distribution: Slackware, Slackware64, Slax, CentOS (when I have to)
Posts: 132

Rep: Reputation: Disabled
I want to see Slackware released on floppies again... I miss making the bare.i boot and color.gz root floppies.
 
Old 03-20-2009, 10:52 AM   #491
GazL
Senior Member
 
Registered: May 2008
Posts: 3,447

Rep: Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975Reputation: 975
Quote:
Originally Posted by arfon View Post
I want to see Slackware released on floppies again... I miss making the bare.i boot and color.gz root floppies.
lol, Don't forget to download them over a v32 modem too for that authentic taste.
 
Old 03-20-2009, 12:21 PM   #492
Anonymo
Member
 
Registered: Dec 2004
Location: The Woodlands, Texas
Distribution: Slackware, Archlinux, CentOS
Posts: 184

Rep: Reputation: 27
Quote:
Originally Posted by GazL View Post
lol, Don't forget to download them over a v32 modem too for that authentic taste.
That's why I cap my dsl at 52k
 
Old 03-20-2009, 01:14 PM   #493
ErV
Senior Member
 
Registered: Mar 2007
Location: Russia
Distribution: Slackware 12.2
Posts: 1,202
Blog Entries: 3

Rep: Reputation: 62
Quote:
Originally Posted by salemboot View Post
You definitely need to document the dependencies though. Somebody is doing something to that nature now.
This can be avoided if you use technique I mentioned before, but:

Quote:
Originally Posted by salemboot View Post
1. Automate a recompile for your architecture (Xeon / i686 / 64 bit)
It won't correctly handle recompile. Only clean build from scratch.
 
Old 03-20-2009, 02:01 PM   #494
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,200

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Quote:
Originally Posted by GazL View Post
lol, Don't forget to download them over a v32 modem too for that authentic taste.
Ha-ha, good one! I've been modem-free for quite a few years. I still remember my crappy old 28.8 modem.......****shudder****
 
Old 03-20-2009, 03:22 PM   #495
C-Sniper
Member
 
Registered: Dec 2006
Distribution: Slackware
Posts: 507

Rep: Reputation: 33
Quote:
Originally Posted by hitest View Post
Ha-ha, good one! I've been modem-free for quite a few years. I still remember my crappy old 28.8 modem.......****shudder****
only 28.8?
try a 1200bit modem.
 
  


Reply

Tags
cd, live


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware future? coyctecm Slackware 12 02-01-2006 10:03 PM
Future of Slackware kratunko Slackware 30 08-12-2005 12:31 PM
Slackware features? rusty_slacker Slackware 49 12-02-2004 04:45 AM
what are the features of the new slackware 9? ethanchic Slackware 2 09-27-2002 06:15 PM


All times are GMT -5. The time now is 08:45 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration