bobs-devel — Developer mailing list

Re: [Bobs-devel] redisigned screen prototypes

[Rene <re...@gr...>]

Looks good to me.

Rene

On Mon, 2002-07-22 at 09:04, Joe zacky wrote:
> I added a couple of user access maintenance pages, one by user, the 
> other by server. I'm also using an include file for the header (and php 
> to allow the include) and the stylesheet. Not all the buttons go where 
> they would go for real, so you might get a little confused.
> 
> If you think it looks okay, I'll start on the real thing. Please let me 
> know what you think. I'm not completely happy with it, so feel free to 
> make suggestions.
> 
> Joe
> ----
> 

Administrator Login
BOBS administrator password: 

[Bobs-devel] redisigned screen prototypes

[Joe z. <jz...@at...>]

I added a couple of user access maintenance pages, one by user, the 
other by server. I'm also using an include file for the header (and php 
to allow the include) and the stylesheet. Not all the buttons go where 
they would go for real, so you might get a little confused.

If you think it looks okay, I'll start on the real thing. Please let me 
know what you think. I'm not completely happy with it, so feel free to 
make suggestions.

Joe

Re: [Bobs-devel] database status

[Rene <re...@gr...>]

Ok.. I'll update the cvs soon. Maybe even today.

I implemented the format using ranges. It was almost too easy.. I also
removed some of the old stuff and plan to remove a lot more.

-Rene


On Sun, 2002-07-21 at 08:57, Joe zacky wrote:
> I don't know. I haven't examined BOBS database at all. I have no idea.
> 
> Rene Rask wrote:
> 
> >The problem here is that I don't know how many entries a file have in the
> >databases. Not a good thing.
> >
> >I was thinking about assigning ranges to the files instead.
> >example. file number 1 has the range 000-099, number 2 has the range 100-199
> >That would make it easy to fetch needed values and files don't have to
> >have the same amount of entries.
> >
> >Let me know what you think.. I would like to do it right this time :)
> >
> >-Rene
> >
> >
> >  
> >
> >>I finally got the database to behave properly.
> >>
> >>The size of the database is much smaller than I wrote last time.
> >>I've got an 11 MB text file which is converted into an 18 MB database.
> >>
> >>I've arranged the databases this way:
> >>
> >>fileindex.db
> >>keys are in this format: <"incrementing-number" dash "data-type">
> >>Data-type are things like path, name and size.
> >>
> >>example:
> >>	0000000-00 => pathname
> >>	0000001-01 => filename
> >>	0000002-02 => date
> >>	0000003-03 => size of file
> >>	0000004-00 => pathname
> >>	0000005-01 => filename
> >>	0000006-02 => date
> >>	0000007-03 => size of file
> >>
> >>More data-types can be added. The only limitation at the moment is that
> >>all files must have all data-types. So if I add a new data-type to one
> >>file I need to add that to the rest as well. I can however be empty
> >>values on the files that don't need it, but they key must be there.
> >>
> >>
> >>dirindex.db has entries in this format:
> >>The key is the full path
> >>The value is the index range in fileindex.db
> >>example:
> >>	path/to/somewhere => 300-312
> >>	some/other/path/1 => 313-544
> >>
> >>The databases are generated when the backup is run.
> >>I also managed to generate the dirtree at the same time.
> >>That is saved as a serialized object and loaded when the users wishes to
> >>browse the files. That saves about 6 seconds of loading time on some of
> >>my backups.
> >>
> >>
> >>You said that you have some experience with these simple databases.
> >>Please let me know if you think there a better ways to do this.
> >>Then I can correct it before I continue.
> >>
> >>-Rene
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This sf.net email is sponsored by:ThinkGeek
> >>Welcome to geek heaven.
> >>http://thinkgeek.com/sf
> >>_______________________________________________
> >>Bobs-devel mailing list
> >>Bob...@li...
> >>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>    
> >>
> >
> >
> >
> >
> >
> >-------------------------------------------------------
> >This sf.net email is sponsored by:ThinkGeek
> >Welcome to geek heaven.
> >http://thinkgeek.com/sf
> >_______________________________________________
> >Bobs-devel mailing list
> >Bob...@li...
> >https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >
> >  
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

Re: [Bobs-devel] database status

[Joe z. <jz...@at...>]

I don't know. I haven't examined BOBS database at all. I have no idea.

Rene Rask wrote:

>The problem here is that I don't know how many entries a file have in the
>databases. Not a good thing.
>
>I was thinking about assigning ranges to the files instead.
>example. file number 1 has the range 000-099, number 2 has the range 100-199
>That would make it easy to fetch needed values and files don't have to
>have the same amount of entries.
>
>Let me know what you think.. I would like to do it right this time :)
>
>-Rene
>
>
>  
>
>>I finally got the database to behave properly.
>>
>>The size of the database is much smaller than I wrote last time.
>>I've got an 11 MB text file which is converted into an 18 MB database.
>>
>>I've arranged the databases this way:
>>
>>fileindex.db
>>keys are in this format: <"incrementing-number" dash "data-type">
>>Data-type are things like path, name and size.
>>
>>example:
>>	0000000-00 => pathname
>>	0000001-01 => filename
>>	0000002-02 => date
>>	0000003-03 => size of file
>>	0000004-00 => pathname
>>	0000005-01 => filename
>>	0000006-02 => date
>>	0000007-03 => size of file
>>
>>More data-types can be added. The only limitation at the moment is that
>>all files must have all data-types. So if I add a new data-type to one
>>file I need to add that to the rest as well. I can however be empty
>>values on the files that don't need it, but they key must be there.
>>
>>
>>dirindex.db has entries in this format:
>>The key is the full path
>>The value is the index range in fileindex.db
>>example:
>>	path/to/somewhere => 300-312
>>	some/other/path/1 => 313-544
>>
>>The databases are generated when the backup is run.
>>I also managed to generate the dirtree at the same time.
>>That is saved as a serialized object and loaded when the users wishes to
>>browse the files. That saves about 6 seconds of loading time on some of
>>my backups.
>>
>>
>>You said that you have some experience with these simple databases.
>>Please let me know if you think there a better ways to do this.
>>Then I can correct it before I continue.
>>
>>-Rene
>>
>>
>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by:ThinkGeek
>>Welcome to geek heaven.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>Bobs-devel mailing list
>>Bob...@li...
>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>    
>>
>
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Bobs-devel mailing list
>Bob...@li...
>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>
>  
>

Re: [Bobs-devel] database status

[Rene R. <re...@gr...>]

The problem here is that I don't know how many entries a file have in the
databases. Not a good thing.

I was thinking about assigning ranges to the files instead.
example. file number 1 has the range 000-099, number 2 has the range 100-199
That would make it easy to fetch needed values and files don't have to
have the same amount of entries.

Let me know what you think.. I would like to do it right this time :)

-Rene


> I finally got the database to behave properly.
>
> The size of the database is much smaller than I wrote last time.
> I've got an 11 MB text file which is converted into an 18 MB database.
>
> I've arranged the databases this way:
>
> fileindex.db
> keys are in this format: <"incrementing-number" dash "data-type">
> Data-type are things like path, name and size.
>
> example:
> 	0000000-00 => pathname
> 	0000001-01 => filename
> 	0000002-02 => date
> 	0000003-03 => size of file
> 	0000004-00 => pathname
> 	0000005-01 => filename
> 	0000006-02 => date
> 	0000007-03 => size of file
>
> More data-types can be added. The only limitation at the moment is that
> all files must have all data-types. So if I add a new data-type to one
> file I need to add that to the rest as well. I can however be empty
> values on the files that don't need it, but they key must be there.
>
>
> dirindex.db has entries in this format:
> The key is the full path
> The value is the index range in fileindex.db
> example:
> 	path/to/somewhere => 300-312
> 	some/other/path/1 => 313-544
>
> The databases are generated when the backup is run.
> I also managed to generate the dirtree at the same time.
> That is saved as a serialized object and loaded when the users wishes to
> browse the files. That saves about 6 seconds of loading time on some of
> my backups.
>
>
> You said that you have some experience with these simple databases.
> Please let me know if you think there a better ways to do this.
> Then I can correct it before I continue.
>
> -Rene
>
>
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

[Bobs-devel] database status

[Rene <re...@gr...>]

I finally got the database to behave properly.

The size of the database is much smaller than I wrote last time.
I've got an 11 MB text file which is converted into an 18 MB database.

I've arranged the databases this way:

fileindex.db
keys are in this format: <"incrementing-number" dash "data-type">
Data-type are things like path, name and size.

example:
	0000000-00 => pathname
	0000001-01 => filename
	0000002-02 => date
	0000003-03 => size of file
	0000004-00 => pathname
	0000005-01 => filename
	0000006-02 => date
	0000007-03 => size of file

More data-types can be added. The only limitation at the moment is that
all files must have all data-types. So if I add a new data-type to one
file I need to add that to the rest as well. I can however be empty
values on the files that don't need it, but they key must be there.


dirindex.db has entries in this format:
The key is the full path
The value is the index range in fileindex.db
example:
	path/to/somewhere => 300-312
	some/other/path/1 => 313-544

The databases are generated when the backup is run.
I also managed to generate the dirtree at the same time.
That is saved as a serialized object and loaded when the users wishes to
browse the files. That saves about 6 seconds of loading time on some of
my backups.


You said that you have some experience with these simple databases.
Please let me know if you think there a better ways to do this.
Then I can correct it before I continue.

-Rene

Re: [Bobs-devel] Re: prototype screens

[Rene <re...@gr...>]

By looking at your screens I thought that was what you had planned. :)
Yes, seperate file for userlists. (these can have encrypted passwords).

A seperate file is nice if we want to make some kind of "import users
from someplace" script.


-Rene


On Fri, 2002-07-19 at 06:53, Joe zacky wrote:
> But where would I get the names of the unauthorized users? The user 
> could be any name we make up. It doesn't even have to be a real login 
> account on any machine.
> 
> If we might do user groups, the authorized user database should be in a 
> separate file, not the server config. I'll plan on making it a separate 
> file, in case we use groups, and because I think it will be easier to 
> manage anyway.
> 
> Rene wrote:
> 
> >Very nice.. I'm impressed.
> >
> >A trick to make add users nicer could be like this:
> >
> >
> >Authorized users		Unathorized Users
> >-----------------		-----------------
> >| Joe		|   --------	| Moe		|
> >| Fred		|  |add user|	| Bill		|
> >| Tim		|   --------	| Dr.Evil	|
> >|		|		|		|
> >|		|  -----------	|		|
> >|		| |remove user|	|		|
> >|		|  -----------	|		|
> >-----------------		-----------------
> >
> >Another neat little feature would be user groups.
> >
> >
> >-Rene
> >
> >
> >
> >  
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

[Bobs-devel] Re: prototype screens

[Joe z. <jz...@at...>]

But where would I get the names of the unauthorized users? The user 
could be any name we make up. It doesn't even have to be a real login 
account on any machine.

If we might do user groups, the authorized user database should be in a 
separate file, not the server config. I'll plan on making it a separate 
file, in case we use groups, and because I think it will be easier to 
manage anyway.

Rene wrote:

>Very nice.. I'm impressed.
>
>A trick to make add users nicer could be like this:
>
>
>Authorized users		Unathorized Users
>-----------------		-----------------
>| Joe		|   --------	| Moe		|
>| Fred		|  |add user|	| Bill		|
>| Tim		|   --------	| Dr.Evil	|
>|		|		|		|
>|		|  -----------	|		|
>|		| |remove user|	|		|
>|		|  -----------	|		|
>-----------------		-----------------
>
>Another neat little feature would be user groups.
>
>
>-Rene
>
>
>
>  
>

Re: [Bobs-devel] small update

[Joe z. <jz...@at...>]

I'm good at planning interfaces and stuff like that at work, when I can 
take the time to do all the research and planning and I'm familiar with 
the application.  At home it's hard to discipline myself to do all the 
planning I should. It's a lot of work, and oftentimes it takes a 
complete redesign after the first attempt, and after it's been used for 
a while, to smooth out the problems. Perhaps after I finally get into 
some of the code I can be of help. So far I've just been working on the 
makefile and the screen design.

Joe

Rene wrote:

>I've been working some more on the character issue in filenames.
>
>What I've got so far:
>1. Index files are now correctly parsed into the new format.
>Speciel characters are handled.
>2. It's possible to browse tbe files in bobs. Both current and
>incremental.
>3. Files can be added to the restore list.
>
>
>What I still need to work on:
>1. Browsable restore lists.
>2. Deleting from the restore list.
>3. Restoring files.
>4. Searching files.
>
>When I get this working I commit it to the cvs.
>
>I'm considering changing the layout of the files so functions for
>special types of operations can be put in separate files. Much like
>plugins.. But I think it'll have to wait till this is working again.
>
>Are you good at structuring things like a plugins API?
>I'm horrible at planning these things, so I always end up doing it over
>and over again until I get it right.
>
>Rene
>
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by: Jabber - The world's fastest growing 
>real-time communications platform! Don't just IM. Build it in! 
>http://www.jabber.com/osdn/xim
>_______________________________________________
>Bobs-devel mailing list
>Bob...@li...
>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>
>  
>

Re: [Bobs-devel] file index issue again

[Rene <re...@gr...>]

Cool.

I actually think db3 is a little slower than grep, but not when
comparing against min_size,max_size,name and possibly path. Which is
what we need.

I'll go redesign bobs (for the 5th time ;)


Rene


btw: I just bought a new home server and I'm messing with it right now.
Just as a warning if you get a bounce or I don't reply to an email that
was lost.



On Thu, 2002-07-18 at 08:46, Joe zacky wrote:
> I think it's a great idea. I used db3 in a couple c programs in linux. 
> It's a standard linux database. I don't doubt that it's much faster than 
> a text file. I just checked my RedHat 7.3 php options and it did come 
> with "--with-db3" compiled in.
> 
> I'm working on what the screens will look like in the new admin 
> interface. I'm creating prototypes in plain html. I'll send them to you 
> when I'm done, to get your opinion.
> 
> Joe
> 
> Rene wrote:
> 
> >I've been looking at the file index structure. 
> >
> >Maybe using flat files wasn't such a Great Idea(tm) in the long run.
> >I've done some research into using db3 (sleepycat software) instead.
> >Results are nice. It's a really simple database and fairly quick as
> >well.
> >
> >I did a test in which I searched for files larger than x bytes, smaller
> >than y bytes and contains the string "ab" in its name.
> >It took less than 4 seconds to parse the database. That was with ~130000
> >files.
> >Each files has 4 entries "path","name","date" and "size"
> >
> >The db file is 38 MB in size. The index file I used to fill the database
> >is only 13 MB in size.
> >
> >But the search speed is really amazing compared to the way bobs do it.
> >
> >I tested this on a athlon 1800+ SMP computer. (it only uses on cpu for
> >searching)
> >
> >Check this link for more information.
> >http://dk.php.net/manual/en/ref.dba.php
> >
> >Redhat 7.2 and 7.3 ships php with db3 enabled.
> >
> >
> >To make it completely useable there would have to be at least to
> >databases for each share. One for the files and one for the dirs.
> >In the dirs database the should be a reference to which index numbers
> >that dir has in the file database.
> >eg.
> >index 0 = /somedir/at/some/path/
> >index 1 = 1000-1304
> >which would indicate that there are 304 files in this dir and they are
> >located between index 1000 and index 1304 in the file database.
> >
> >This is needed for a really fast search which is needed when we display
> >files in the browser.
> >
> >This way a share with 15000 dirs should take less than 1 second to
> >display a file list in the browser.
> >
> >The real feature is that this is a 1000 times easier to handle in php.
> >
> >
> >Let me know what you think.
> >Is it a good idea to use it?
> >
> >-Rene
> >
> >
> >
> >-------------------------------------------------------
> >This sf.net email is sponsored by:ThinkGeek
> >Welcome to geek heaven.
> >http://thinkgeek.com/sf
> >_______________________________________________
> >Bobs-devel mailing list
> >Bob...@li...
> >https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >
> >  
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

Re: [Bobs-devel] file index issue again

[Joe z. <jz...@at...>]

I think it's a great idea. I used db3 in a couple c programs in linux. 
It's a standard linux database. I don't doubt that it's much faster than 
a text file. I just checked my RedHat 7.3 php options and it did come 
with "--with-db3" compiled in.

I'm working on what the screens will look like in the new admin 
interface. I'm creating prototypes in plain html. I'll send them to you 
when I'm done, to get your opinion.

Joe

Rene wrote:

>I've been looking at the file index structure. 
>
>Maybe using flat files wasn't such a Great Idea(tm) in the long run.
>I've done some research into using db3 (sleepycat software) instead.
>Results are nice. It's a really simple database and fairly quick as
>well.
>
>I did a test in which I searched for files larger than x bytes, smaller
>than y bytes and contains the string "ab" in its name.
>It took less than 4 seconds to parse the database. That was with ~130000
>files.
>Each files has 4 entries "path","name","date" and "size"
>
>The db file is 38 MB in size. The index file I used to fill the database
>is only 13 MB in size.
>
>But the search speed is really amazing compared to the way bobs do it.
>
>I tested this on a athlon 1800+ SMP computer. (it only uses on cpu for
>searching)
>
>Check this link for more information.
>http://dk.php.net/manual/en/ref.dba.php
>
>Redhat 7.2 and 7.3 ships php with db3 enabled.
>
>
>To make it completely useable there would have to be at least to
>databases for each share. One for the files and one for the dirs.
>In the dirs database the should be a reference to which index numbers
>that dir has in the file database.
>eg.
>index 0 = /somedir/at/some/path/
>index 1 = 1000-1304
>which would indicate that there are 304 files in this dir and they are
>located between index 1000 and index 1304 in the file database.
>
>This is needed for a really fast search which is needed when we display
>files in the browser.
>
>This way a share with 15000 dirs should take less than 1 second to
>display a file list in the browser.
>
>The real feature is that this is a 1000 times easier to handle in php.
>
>
>Let me know what you think.
>Is it a good idea to use it?
>
>-Rene
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Bobs-devel mailing list
>Bob...@li...
>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>
>  
>

[Bobs-devel] file index issue again

[Rene <re...@gr...>]

I've been looking at the file index structure. 

Maybe using flat files wasn't such a Great Idea(tm) in the long run.
I've done some research into using db3 (sleepycat software) instead.
Results are nice. It's a really simple database and fairly quick as
well.

I did a test in which I searched for files larger than x bytes, smaller
than y bytes and contains the string "ab" in its name.
It took less than 4 seconds to parse the database. That was with ~130000
files.
Each files has 4 entries "path","name","date" and "size"

The db file is 38 MB in size. The index file I used to fill the database
is only 13 MB in size.

But the search speed is really amazing compared to the way bobs do it.

I tested this on a athlon 1800+ SMP computer. (it only uses on cpu for
searching)

Check this link for more information.
http://dk.php.net/manual/en/ref.dba.php

Redhat 7.2 and 7.3 ships php with db3 enabled.


To make it completely useable there would have to be at least to
databases for each share. One for the files and one for the dirs.
In the dirs database the should be a reference to which index numbers
that dir has in the file database.
eg.
index 0 = /somedir/at/some/path/
index 1 = 1000-1304
which would indicate that there are 304 files in this dir and they are
located between index 1000 and index 1304 in the file database.

This is needed for a really fast search which is needed when we display
files in the browser.

This way a share with 15000 dirs should take less than 1 second to
display a file list in the browser.

The real feature is that this is a 1000 times easier to handle in php.


Let me know what you think.
Is it a good idea to use it?

-Rene

[Bobs-devel] small update

[Rene <re...@gr...>]

I've been working some more on the character issue in filenames.

What I've got so far:
1. Index files are now correctly parsed into the new format.
Speciel characters are handled.
2. It's possible to browse tbe files in bobs. Both current and
incremental.
3. Files can be added to the restore list.


What I still need to work on:
1. Browsable restore lists.
2. Deleting from the restore list.
3. Restoring files.
4. Searching files.

When I get this working I commit it to the cvs.

I'm considering changing the layout of the files so functions for
special types of operations can be put in separate files. Much like
plugins.. But I think it'll have to wait till this is working again.

Are you good at structuring things like a plugins API?
I'm horrible at planning these things, so I always end up doing it over
and over again until I get it right.

Rene

Re: [Bobs-devel] admin config: php class or ini file?

[Rene <re...@gr...>]

On Mon, 2002-07-15 at 09:26, Joe zacky wrote:
> I've been looking hard at your suggestions and code this weekend. I'm 
> very impressed with your ini parsing to create html pages in 
> class_config, and class_tree.php.
> 
> I see what you want to do by converting the ini file to php, but I don't 
> understand the "depends" part of it:
> 
> $server_defs["nfs_share"]["depends"]["value"]["0"]      = "nfs";
> $server_defs["nfs_share"]["depends"]["value"]["1"]      = "nfs";
> $server_defs["nfs_share"]["depends"]["rule"]["0"]       = "0:TRUE";
> $server_defs["nfs_share"]["depends"]["rule"]["1"]       = "1:TRUE";

These two lines are the names of the rules

$server_defs["nfs_share"]["depends"]["name"]["0"] = "backup_method";
$server_defs["nfs_share"]["depends"]["name"]["1"] = "restore_method";

the "value" of the rule is that is must be == "nfs"

the ruleset states that rule number 0 must be TRUE
or rule number 1 must be TRUE

For rule number 0 to be true the value of $backup_method must be ==
"nfs"

A more complex rule could be:

$server_defs["nfs_share"]["depends"]["rule"]["0"] = "0:TRUE|1:FALSE";
The correct settings for this rule would be:
$backup_method = "nfs"
$restore_method = "anything but nfs"


The reason I proposed a php file instead of the ini file is that to ini
file must be parsed and then the data in it must be parsed.
Ini files are not as flexible as php. This is especially true with
arrays.

> But I don't know if I can turn this line
> 
>     depends = "$backup_method == nfs || $restore_method == nfs"
> 
> into an executable statement that will return TRUE or FALSE.
> 
> Do you think it can work? Think it's a good idea?

It would not be that hard to do. The eval() function can do this.
My concern with ini files is that every time add a special settings, we
will need to parse that setting on its own. That adds complexity to the
code. 
I initially found ini files to be easy to work with. But as bobs has
progressed and more options are added, the complexity increases and I
don't think that is going to stop soon.

I can imagine a small set of commands doing the same as is being done
now by a complex set of commands.

I would go for the php method and then add the ini parser at a later if
it seems like a good idea to use it.

Please let me know what you work out.
-Rene





> 
> I'll work on rewriting admin.php and class_config.php. It will be a  
> worthy challenge with my limited php experience, and it's only the two 
> files affected, so I'm pretty safe.
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

[Bobs-devel] admin config: php class or ini file?

[Joe z. <jz...@at...>]

I've been looking hard at your suggestions and code this weekend. I'm 
very impressed with your ini parsing to create html pages in 
class_config, and class_tree.php.

I see what you want to do by converting the ini file to php, but I don't 
understand the "depends" part of it:

$server_defs["nfs_share"]["depends"]["value"]["0"]      = "nfs";
$server_defs["nfs_share"]["depends"]["value"]["1"]      = "nfs";
$server_defs["nfs_share"]["depends"]["rule"]["0"]       = "0:TRUE";
$server_defs["nfs_share"]["depends"]["rule"]["1"]       = "1:TRUE";

I'm thinking we could still use an ini file. If I pass a second 
parameter of TRUE to the parse_ini_file() function, I could use an ini 
file like this to put the variables into a two-dimensional array:

---- begin example ---

[active]
type = choice
description = "Should I create backups from this server"

[login]
type = text
description = "Users login name"

[password]
type = encrypted
description = "Users password"

[server]
type = text
description = "The servers network name"

[server_ip]
type = ip
description = "The servers ip address"

[share]
type = text
description = "The descriptive name of the share"

[nfs_share]
type = path
description = "The path the nfs share is mounted under"
depends = "$backup_method == nfs || $restore_method == nfs"

[smb_share]
type = text
description = "The name of the smb share"
depends = "$backup_method == smb || $restore_method == smb"

[rsync_share]
type = text
description = "The name of the rsync share"
depends = "$backup_method == rsync"

[backup_method]
type  = list    <-- (note: this will be a new data type for a drop-down 
list)
description = "What should I use for making backups"
list = "nfs,rsync,smb"

[restore_method]
type = list
description = "What should I use for restoring files"
list = "nfs,smb"

[compress]
type = choice
description = "Compress incremental files?"

[incrementals]
type = number
description = "How many incrementals to keep ( 0 = infinite )"

[run_days]
type = number
description = "Which days to backup. ( 0 = monday, 1 = tuesday .. 
etc)" = "The servers network name"

---- end example ---

But I don't know if I can turn this line

    depends = "$backup_method == nfs || $restore_method == nfs"

into an executable statement that will return TRUE or FALSE.

Do you think it can work? Think it's a good idea?

I'll work on rewriting admin.php and class_config.php. It will be a  
worthy challenge with my limited php experience, and it's only the two 
files affected, so I'm pretty safe.

[Bobs-devel] config editor suggestions

[Rene <re...@gr...>]

Hi Joe.

This is my suggestion to a new configuration editor.
This should ensure that options that are not used are not displayed.
eg. nfs_share should not be display if backup_method and restore_method
are "smb"

Feel free to change, disregard or extend it.

The changes to admin.php looked nice.

-Rene

New functions in class_config (a lot of the old stuff could then be
removed):

make_server($server_defs)
	creates the basic empty configuration for a new server
	store the result in "$this->config" in class_config
	stores$server_defs in $this->server_defs for use in other functions.
(like check_rules)

check_rules ($name)
	check option "$name" to see if if passes the rules.
	returns TRUE or FALSE
	
edit_server ($config_from_admin.pgp)
	for each option in $this->config (also empty ones) it calls
check_rules()
	If TRUE it passes the option to html_parse_option($name)
	returns html

html_parse_option ($name)
	checks the type of the option and parses it into an html format for
editing.
	returns hmtl
	



-- sample of added lines to config.php ----

$server_defs["backup_method"]["name"]           = "backup_method";
$server_defs["backup_method"]["type"]           = "list";
$server_defs["backup_method"]["desc"]           = "What method do you
wish to use for making backups";
$server_defs["backup_method"]["list"]["0"]      = "rsync";
$server_defs["backup_method"]["list"]["1"]      = "nfs";
$server_defs["backup_method"]["list"]["2"]      = "smb";

$server_defs["restore_method"]["name"]          = "restore_method";
$server_defs["restore_method"]["type"]          = "list";
$server_defs["restore_method"]["desc"]          = "What method do you
wish to use for restoring files";
$server_defs["restore_method"]["list"]["0"]     = "nfs";
$server_defs["restore_method"]["list"]["1"]     = "smb";

$server_defs["smb_share"]["name"]                       = "smb_share";
$server_defs["smb_share"]["type"]                       = "text";
$server_defs["smb_share"]["desc"]                       = "Name of the
smb share to use";
$server_defs["smb_share"]["depends"]["name"]["0"]       =
"backup_method";
$server_defs["smb_share"]["depends"]["name"]["1"]       =
"restore_method";
$server_defs["smb_share"]["depends"]["value"]["0"]      = "smb";
$server_defs["smb_share"]["depends"]["value"]["1"]      = "smb";
$server_defs["smb_share"]["depends"]["rule"]["0"]       = "0:TRUE";
$server_defs["smb_share"]["depends"]["rule"]["1"]       = "1:TRUE";

$server_defs["smb_share"]["name"]                       = "nfs_share";
$server_defs["nfs_share"]["type"]                       = "path";
$server_defs["nfs_share"]["desc"]                       = "Path of the
nfs share to use";
$server_defs["nfs_share"]["depends"]["name"]["0"]       =
"backup_method";
$server_defs["nfs_share"]["depends"]["name"]["1"]       =
"restore_method";
$server_defs["nfs_share"]["depends"]["value"]["0"]      = "nfs";
$server_defs["nfs_share"]["depends"]["value"]["1"]      = "nfs";
$server_defs["nfs_share"]["depends"]["rule"]["0"]       = "0:TRUE";
$server_defs["nfs_share"]["depends"]["rule"]["1"]       = "1:TRUE";

Re: [Bobs-devel] filename problems

[Rene <re...@gr...>]

On Sun, 2002-07-14 at 04:10, Joe zacky wrote:
> I don't understand where these filenames with embedded newlines are 
> coming from? I haven't ever seen a filename with an embedded newline. Is 
> this a problem in class_restore.php?


It breaks some things. And I know that it is not an illegal filename.
I'm just trying to make sure that bobs does not break.
But right now there should only be _very_ few names that will break
bobs.

> 
> I'm planning to look at the configuration editor admin.php tonight to 
> see if I can figure out what needs to be reworked. Please keep in mind 
> I'm not familiar with the functioning of the php pages and classes 
> you've written, so it takes me a while to get my head into it. More 
> specifics on what I should work on would help, like which files or 
> classes, what should change on admin.php, etc.
>
Well. I don't really know what to do with admin.php.
I would probably tear it apart and start over.
It's not as good as I would like it. 
Basically it needs to handle several types of configuration setups.

A better way to do it would be to introduce configuration options as
needed. eg. a user selects "smb share" and "static ip" as options. Then
the following options show up: "servername" "ip address" Smb share name"
"login" "password".


1. Handling and checking of options. 
2. A way of linking options. eg. smb_share depends on backup_type=smb

admin.php and class_config are the only php related to configuration so
don't be afraid of breaking stuff.

I looked at the server.definitions.ini and been trying to figure out how
to make a better editor. 
I think we should drop the file and go with a php file instead. That way
we could use arrays to hold the information we need. Like type, name,
descriptions, selection lists and what depends on what.

example definitions array
[smb_share][type] = text
[smb_share][desc] = "name of smb share"
[smb_share][help] = "more detail about this option ......"
[smb_share][depend][name][0] = "backup_method"
[smb_share][depend][name][1] = "restore_method"
[smb_share][depend][value][0] = "smb"
[smb_share][depend][value][1] = "smb"

so if $backup_method or $restore_method has a value of "smb" we should
display this option.
In case of options depending on more than on value we could add
something like this.

[smb_share][depend][rule][0] = "0|TRUE:1|TRUE"
where the "0" refers to "[smb_share][depend][name][0]" which is
"backup_method"
and TRUE means that this dependency must be satisfied

multiple rules could be made that way and if one of them match a
configuration then the options will be displayed.

So most of class_config could be redone in a much nicer way than the
hacks I put in there.

Another thing people might want is a user login list which is not the
same as the server/share login..

Hope I'm making sense here..



Rene



> I hope I can get some stuff done this weekend. It's over 100 degrees 
> here (37.7 celsius), and I'm still lazy from vacationing.
> 
> Joe
> 
> Rene wrote:
> 
> >Damn filenames...
> >
> >Filenames including newlines will not work properly. That much is sure.
> >
> >I'm going examine possible solutions, like use a NULL as an end-of-line
> >seperator. I read somewhere that NULL's aren't accepted by shell
> >programs like grep so that might be a problem.
> >Maybe maybe an end-of-line marker like "///FF" would work if NULL is not
> >usefull.
> >
> >What is your opinion about using flat text files instead of databases?
> >Any suggestion on better ways to do it?
> >
> >Rene
> >
> >
> >On Sat, 2002-07-13 at 18:11, Rene Rask wrote:
> >  
> >
> >>I've finally been able to get some useful results.
> >>
> >>This is not a perfect solution as far as I can see.
> >>
> >>Basically it involves changing the $IFS value in bash to be a newline.
> >>And changing it to the original value after use.
> >>
> >>The problem is (or will be) that filenames cannot contain newlines.
> >>I might be able to escape newlines in filenames.
> >>
> >>Anyway. This solution is better than the old one so I'm going to update 
> >>the cvs with it.
> >>
> >>I'll see if I can test the newline problem and find a solution.
> >>
> >>
> >>Rene
> >>
> >>
> >>
> >>Joe zacky wrote:
> >>    
> >>
> >>>Have you tried escaping single quotes like this, where $filename is the 
> >>>variable containing the name of the file:
> >>>    \'$filename\'
> >>>
> >>>Joe
> >>>
> >>>Rene Rask wrote:
> >>>
> >>>      
> >>>
> >>>>The names are quoted. I've tried both double and single quoting.
> >>>>If I can get bash to accept the names as "literal" instead of "glob" it
> >>>>should solve the problem.
> >>>>
> >>>>A name like "some name^Mtest" does not behave well.
> >>>>Only working solution I've found was this way:
> >>>>$'some name^Mtest'
> >>>>But I can't figure out how that is useful in a script.
> >>>>
> >>>>
> >>>>I'll keep trying.
> >>>>
> >>>>-Rene
> >>>>
> >>>>
> >>>>On Fri, 2002-07-12 at 07:26, Joe zacky wrote:
> >>>> 
> >>>>
> >>>>        
> >>>>
> >>>>>Rene Rask wrote:
> >>>>>
> >>>>>   
> >>>>>
> >>>>>          
> >>>>>
> >>>>>>I've been looking into the filename problems.
> >>>>>>
> >>>>>>It seems to me that escaping filenames in PHP will ony lead to a 
> >>>>>>constant headache (which is not what I need right now ;)
> >>>>>>
> >>>>>>I've found a few Bash tricks that look really promising but I haven't 
> >>>>>>cracked the problem yet. I'm able to make Bash escape a filename with 
> >>>>>>weird characters in it. But I'm still not able to do it with input 
> >>>>>>            
> >>>>>>
> >>>>>>from a list.
> >>>>>          
> >>>>>
> >>>>>>When (if?) I get this working we should be able to stop worrying about 
> >>>>>>filenames.
> >>>>>>If you know any Bash experts please ask if they can help.
> >>>>>>
> >>>>>>-Rene
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>-------------------------------------------------------
> >>>>>>This sf.net email is sponsored by:ThinkGeek
> >>>>>>Two, two, TWO treats in one.
> >>>>>>http://thinkgeek.com/sf
> >>>>>>_______________________________________________
> >>>>>>Bobs-devel mailing list
> >>>>>>Bob...@li...
> >>>>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>>>>>
> >>>>>>     
> >>>>>>
> >>>>>>            
> >>>>>>
> >>>>>Have you tried "quoting the filenames?" That also works in bash.
> >>>>>
> >>>>>
> >>>>>
> >>>>>-------------------------------------------------------
> >>>>>This sf.net email is sponsored by:ThinkGeek
> >>>>>Gadgets, caffeine, t-shirts, fun stuff.
> >>>>>http://thinkgeek.com/sf
> >>>>>_______________________________________________
> >>>>>Bobs-devel mailing list
> >>>>>Bob...@li...
> >>>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>>>>   
> >>>>>
> >>>>>          
> >>>>>
> >>>>
> >>>>
> >>>>-------------------------------------------------------
> >>>>This sf.net email is sponsored by:ThinkGeek
> >>>>Gadgets, caffeine, t-shirts, fun stuff.
> >>>>http://thinkgeek.com/sf
> >>>>_______________________________________________
> >>>>Bobs-devel mailing list
> >>>>Bob...@li...
> >>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>>>
> >>>> 
> >>>>
> >>>>        
> >>>>
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This sf.net email is sponsored by:ThinkGeek
> >>Welcome to geek heaven.
> >>http://thinkgeek.com/sf
> >>_______________________________________________
> >>Bobs-devel mailing list
> >>Bob...@li...
> >>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>    
> >>
> >
> >
> >
> >
> >-------------------------------------------------------
> >This sf.net email is sponsored by:ThinkGeek
> >Welcome to geek heaven.
> >http://thinkgeek.com/sf
> >_______________________________________________
> >Bobs-devel mailing list
> >Bob...@li...
> >https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >
> >  
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

[Bobs-devel] admin cosmetics

[Joe z. <jz...@at...>]

I made some cosmetic changes to admin.php. Mostly, I added page 
headings. I also added a "delete" button, but it does the same as "edit" 
for now. I want to add some drop-down lists for selecting smb/nsf/rsync, 
but it's late and I want to play some Half-Life.

You'll notice in the "Administrator Login" section of admin.php that I 
added some newlines "\n" to the echo output, and escaped some of the 
quotes (\"). If you select "view source" in your browser the newlines 
make it much more readable. I didn't add them to the other sections of 
admin.php because I would like your opinion, you might think it makes 
the source harder to read.

I also added a table border variable for testing. Turning it on makes it 
easier to arrange the table elements.

Let me know what you think.

Joe

[Bobs-devel] smb backup/restore

[Joe z. <jz...@at...>]

I just tested the smb backup and restore...it works! I got confused 
about the passwords. Wasn't sure if the passwords were for the user to 
login to bobs or for the smb share.

Re: [Bobs-devel] filename problems

[Joe z. <jz...@at...>]

I don't understand where these filenames with embedded newlines are 
coming from? I haven't ever seen a filename with an embedded newline. Is 
this a problem in class_restore.php?

I'm planning to look at the configuration editor admin.php tonight to 
see if I can figure out what needs to be reworked. Please keep in mind 
I'm not familiar with the functioning of the php pages and classes 
you've written, so it takes me a while to get my head into it. More 
specifics on what I should work on would help, like which files or 
classes, what should change on admin.php, etc.

I hope I can get some stuff done this weekend. It's over 100 degrees 
here (37.7 celsius), and I'm still lazy from vacationing.

Joe

Rene wrote:

>Damn filenames...
>
>Filenames including newlines will not work properly. That much is sure.
>
>I'm going examine possible solutions, like use a NULL as an end-of-line
>seperator. I read somewhere that NULL's aren't accepted by shell
>programs like grep so that might be a problem.
>Maybe maybe an end-of-line marker like "///FF" would work if NULL is not
>usefull.
>
>What is your opinion about using flat text files instead of databases?
>Any suggestion on better ways to do it?
>
>Rene
>
>
>On Sat, 2002-07-13 at 18:11, Rene Rask wrote:
>  
>
>>I've finally been able to get some useful results.
>>
>>This is not a perfect solution as far as I can see.
>>
>>Basically it involves changing the $IFS value in bash to be a newline.
>>And changing it to the original value after use.
>>
>>The problem is (or will be) that filenames cannot contain newlines.
>>I might be able to escape newlines in filenames.
>>
>>Anyway. This solution is better than the old one so I'm going to update 
>>the cvs with it.
>>
>>I'll see if I can test the newline problem and find a solution.
>>
>>
>>Rene
>>
>>
>>
>>Joe zacky wrote:
>>    
>>
>>>Have you tried escaping single quotes like this, where $filename is the 
>>>variable containing the name of the file:
>>>    \'$filename\'
>>>
>>>Joe
>>>
>>>Rene Rask wrote:
>>>
>>>      
>>>
>>>>The names are quoted. I've tried both double and single quoting.
>>>>If I can get bash to accept the names as "literal" instead of "glob" it
>>>>should solve the problem.
>>>>
>>>>A name like "some name^Mtest" does not behave well.
>>>>Only working solution I've found was this way:
>>>>$'some name^Mtest'
>>>>But I can't figure out how that is useful in a script.
>>>>
>>>>
>>>>I'll keep trying.
>>>>
>>>>-Rene
>>>>
>>>>
>>>>On Fri, 2002-07-12 at 07:26, Joe zacky wrote:
>>>> 
>>>>
>>>>        
>>>>
>>>>>Rene Rask wrote:
>>>>>
>>>>>   
>>>>>
>>>>>          
>>>>>
>>>>>>I've been looking into the filename problems.
>>>>>>
>>>>>>It seems to me that escaping filenames in PHP will ony lead to a 
>>>>>>constant headache (which is not what I need right now ;)
>>>>>>
>>>>>>I've found a few Bash tricks that look really promising but I haven't 
>>>>>>cracked the problem yet. I'm able to make Bash escape a filename with 
>>>>>>weird characters in it. But I'm still not able to do it with input 
>>>>>>            
>>>>>>
>>>>>>from a list.
>>>>>          
>>>>>
>>>>>>When (if?) I get this working we should be able to stop worrying about 
>>>>>>filenames.
>>>>>>If you know any Bash experts please ask if they can help.
>>>>>>
>>>>>>-Rene
>>>>>>
>>>>>>
>>>>>>
>>>>>>-------------------------------------------------------
>>>>>>This sf.net email is sponsored by:ThinkGeek
>>>>>>Two, two, TWO treats in one.
>>>>>>http://thinkgeek.com/sf
>>>>>>_______________________________________________
>>>>>>Bobs-devel mailing list
>>>>>>Bob...@li...
>>>>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>>>>>
>>>>>>     
>>>>>>
>>>>>>            
>>>>>>
>>>>>Have you tried "quoting the filenames?" That also works in bash.
>>>>>
>>>>>
>>>>>
>>>>>-------------------------------------------------------
>>>>>This sf.net email is sponsored by:ThinkGeek
>>>>>Gadgets, caffeine, t-shirts, fun stuff.
>>>>>http://thinkgeek.com/sf
>>>>>_______________________________________________
>>>>>Bobs-devel mailing list
>>>>>Bob...@li...
>>>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>>>>   
>>>>>
>>>>>          
>>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This sf.net email is sponsored by:ThinkGeek
>>>>Gadgets, caffeine, t-shirts, fun stuff.
>>>>http://thinkgeek.com/sf
>>>>_______________________________________________
>>>>Bobs-devel mailing list
>>>>Bob...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>>>
>>>> 
>>>>
>>>>        
>>>>
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by:ThinkGeek
>>Welcome to geek heaven.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>Bobs-devel mailing list
>>Bob...@li...
>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>    
>>
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Bobs-devel mailing list
>Bob...@li...
>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>
>  
>

Re: [Bobs-devel] filename problems

[Rene <re...@gr...>]

Damn filenames...

Filenames including newlines will not work properly. That much is sure.

I'm going examine possible solutions, like use a NULL as an end-of-line
seperator. I read somewhere that NULL's aren't accepted by shell
programs like grep so that might be a problem.
Maybe maybe an end-of-line marker like "///FF" would work if NULL is not
usefull.

What is your opinion about using flat text files instead of databases?
Any suggestion on better ways to do it?

Rene


On Sat, 2002-07-13 at 18:11, Rene Rask wrote:
> 
> I've finally been able to get some useful results.
> 
> This is not a perfect solution as far as I can see.
> 
> Basically it involves changing the $IFS value in bash to be a newline.
> And changing it to the original value after use.
> 
> The problem is (or will be) that filenames cannot contain newlines.
> I might be able to escape newlines in filenames.
> 
> Anyway. This solution is better than the old one so I'm going to update 
> the cvs with it.
> 
> I'll see if I can test the newline problem and find a solution.
> 
> 
> Rene
> 
> 
> 
> Joe zacky wrote:
> > Have you tried escaping single quotes like this, where $filename is the 
> > variable containing the name of the file:
> >     \'$filename\'
> > 
> > Joe
> > 
> > Rene Rask wrote:
> > 
> >>The names are quoted. I've tried both double and single quoting.
> >>If I can get bash to accept the names as "literal" instead of "glob" it
> >>should solve the problem.
> >>
> >>A name like "some name^Mtest" does not behave well.
> >>Only working solution I've found was this way:
> >>$'some name^Mtest'
> >>But I can't figure out how that is useful in a script.
> >>
> >>
> >>I'll keep trying.
> >>
> >>-Rene
> >>
> >>
> >>On Fri, 2002-07-12 at 07:26, Joe zacky wrote:
> >>  
> >>
> >>>Rene Rask wrote:
> >>>
> >>>    
> >>>
> >>>>I've been looking into the filename problems.
> >>>>
> >>>>It seems to me that escaping filenames in PHP will ony lead to a 
> >>>>constant headache (which is not what I need right now ;)
> >>>>
> >>>>I've found a few Bash tricks that look really promising but I haven't 
> >>>>cracked the problem yet. I'm able to make Bash escape a filename with 
> >>>>weird characters in it. But I'm still not able to do it with input 
> >>>>from a list.
> >>>>When (if?) I get this working we should be able to stop worrying about 
> >>>>filenames.
> >>>>If you know any Bash experts please ask if they can help.
> >>>>
> >>>>-Rene
> >>>>
> >>>>
> >>>>
> >>>>-------------------------------------------------------
> >>>>This sf.net email is sponsored by:ThinkGeek
> >>>>Two, two, TWO treats in one.
> >>>>http://thinkgeek.com/sf
> >>>>_______________________________________________
> >>>>Bobs-devel mailing list
> >>>>Bob...@li...
> >>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>>>
> >>>>      
> >>>>
> >>>Have you tried "quoting the filenames?" That also works in bash.
> >>>
> >>>
> >>>
> >>>-------------------------------------------------------
> >>>This sf.net email is sponsored by:ThinkGeek
> >>>Gadgets, caffeine, t-shirts, fun stuff.
> >>>http://thinkgeek.com/sf
> >>>_______________________________________________
> >>>Bobs-devel mailing list
> >>>Bob...@li...
> >>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>>    
> >>>
> >>
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This sf.net email is sponsored by:ThinkGeek
> >>Gadgets, caffeine, t-shirts, fun stuff.
> >>http://thinkgeek.com/sf
> >>_______________________________________________
> >>Bobs-devel mailing list
> >>Bob...@li...
> >>https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >>
> >>  
> >>
> > 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

Re: [Bobs-devel] filename problems

[Rene R. <re...@gr...>]

I've finally been able to get some useful results.

This is not a perfect solution as far as I can see.

Basically it involves changing the $IFS value in bash to be a newline.
And changing it to the original value after use.

The problem is (or will be) that filenames cannot contain newlines.
I might be able to escape newlines in filenames.

Anyway. This solution is better than the old one so I'm going to update 
the cvs with it.

I'll see if I can test the newline problem and find a solution.


Rene



Joe zacky wrote:
> Have you tried escaping single quotes like this, where $filename is the 
> variable containing the name of the file:
>     \'$filename\'
> 
> Joe
> 
> Rene Rask wrote:
> 
>>The names are quoted. I've tried both double and single quoting.
>>If I can get bash to accept the names as "literal" instead of "glob" it
>>should solve the problem.
>>
>>A name like "some name^Mtest" does not behave well.
>>Only working solution I've found was this way:
>>$'some name^Mtest'
>>But I can't figure out how that is useful in a script.
>>
>>
>>I'll keep trying.
>>
>>-Rene
>>
>>
>>On Fri, 2002-07-12 at 07:26, Joe zacky wrote:
>>  
>>
>>>Rene Rask wrote:
>>>
>>>    
>>>
>>>>I've been looking into the filename problems.
>>>>
>>>>It seems to me that escaping filenames in PHP will ony lead to a 
>>>>constant headache (which is not what I need right now ;)
>>>>
>>>>I've found a few Bash tricks that look really promising but I haven't 
>>>>cracked the problem yet. I'm able to make Bash escape a filename with 
>>>>weird characters in it. But I'm still not able to do it with input 
>>>>from a list.
>>>>When (if?) I get this working we should be able to stop worrying about 
>>>>filenames.
>>>>If you know any Bash experts please ask if they can help.
>>>>
>>>>-Rene
>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This sf.net email is sponsored by:ThinkGeek
>>>>Two, two, TWO treats in one.
>>>>http://thinkgeek.com/sf
>>>>_______________________________________________
>>>>Bobs-devel mailing list
>>>>Bob...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>>>
>>>>      
>>>>
>>>Have you tried "quoting the filenames?" That also works in bash.
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This sf.net email is sponsored by:ThinkGeek
>>>Gadgets, caffeine, t-shirts, fun stuff.
>>>http://thinkgeek.com/sf
>>>_______________________________________________
>>>Bobs-devel mailing list
>>>Bob...@li...
>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>>    
>>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by:ThinkGeek
>>Gadgets, caffeine, t-shirts, fun stuff.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>Bobs-devel mailing list
>>Bob...@li...
>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>
>>  
>>
> 

Re: [Bobs-devel] filename problems

[Joe z. <jz...@at...>]

Have you tried escaping single quotes like this, where $filename is the 
variable containing the name of the file:
    \'$filename\'

Joe

Rene Rask wrote:

>The names are quoted. I've tried both double and single quoting.
>If I can get bash to accept the names as "literal" instead of "glob" it
>should solve the problem.
>
>A name like "some name^Mtest" does not behave well.
>Only working solution I've found was this way:
>$'some name^Mtest'
>But I can't figure out how that is useful in a script.
>
>
>I'll keep trying.
>
>-Rene
>
>
>On Fri, 2002-07-12 at 07:26, Joe zacky wrote:
>  
>
>>Rene Rask wrote:
>>
>>    
>>
>>>I've been looking into the filename problems.
>>>
>>>It seems to me that escaping filenames in PHP will ony lead to a 
>>>constant headache (which is not what I need right now ;)
>>>
>>>I've found a few Bash tricks that look really promising but I haven't 
>>>cracked the problem yet. I'm able to make Bash escape a filename with 
>>>weird characters in it. But I'm still not able to do it with input 
>>>from a list.
>>>When (if?) I get this working we should be able to stop worrying about 
>>>filenames.
>>>If you know any Bash experts please ask if they can help.
>>>
>>>-Rene
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This sf.net email is sponsored by:ThinkGeek
>>>Two, two, TWO treats in one.
>>>http://thinkgeek.com/sf
>>>_______________________________________________
>>>Bobs-devel mailing list
>>>Bob...@li...
>>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>>
>>>      
>>>
>>Have you tried "quoting the filenames?" That also works in bash.
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by:ThinkGeek
>>Gadgets, caffeine, t-shirts, fun stuff.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>Bobs-devel mailing list
>>Bob...@li...
>>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>>    
>>
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Gadgets, caffeine, t-shirts, fun stuff.
>http://thinkgeek.com/sf
>_______________________________________________
>Bobs-devel mailing list
>Bob...@li...
>https://lists.sourceforge.net/lists/listinfo/bobs-devel
>
>  
>

Re: [Bobs-devel] filename problems

[Rene R. <re...@gr...>]

The names are quoted. I've tried both double and single quoting.
If I can get bash to accept the names as "literal" instead of "glob" it
should solve the problem.

A name like "some name^Mtest" does not behave well.
Only working solution I've found was this way:
$'some name^Mtest'
But I can't figure out how that is useful in a script.


I'll keep trying.

-Rene


On Fri, 2002-07-12 at 07:26, Joe zacky wrote:
> Rene Rask wrote:
> 
> > I've been looking into the filename problems.
> >
> > It seems to me that escaping filenames in PHP will ony lead to a 
> > constant headache (which is not what I need right now ;)
> >
> > I've found a few Bash tricks that look really promising but I haven't 
> > cracked the problem yet. I'm able to make Bash escape a filename with 
> > weird characters in it. But I'm still not able to do it with input 
> > from a list.
> > When (if?) I get this working we should be able to stop worrying about 
> > filenames.
> > If you know any Bash experts please ask if they can help.
> >
> > -Rene
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Two, two, TWO treats in one.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Bobs-devel mailing list
> > Bob...@li...
> > https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >
> Have you tried "quoting the filenames?" That also works in bash.
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Gadgets, caffeine, t-shirts, fun stuff.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel

Re: [Bobs-devel] filename problems

[Joe z. <jz...@at...>]

Rene Rask wrote:

> I've been looking into the filename problems.
>
> It seems to me that escaping filenames in PHP will ony lead to a 
> constant headache (which is not what I need right now ;)
>
> I've found a few Bash tricks that look really promising but I haven't 
> cracked the problem yet. I'm able to make Bash escape a filename with 
> weird characters in it. But I'm still not able to do it with input 
> from a list.
> When (if?) I get this working we should be able to stop worrying about 
> filenames.
> If you know any Bash experts please ask if they can help.
>
> -Rene
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Two, two, TWO treats in one.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel
>
Have you tried "quoting the filenames?" That also works in bash.